DBA

http://www.obieefans.com/create-environment-patch-environmentalization/ Create Environment Patch (Environmentalization) Posted by root on 27 March, 2012No comments yetThis item was filled under [ OBIEE MISC ] During RPD migrations we constantly need to change metadata for the target environment such as physical connection pool(s) and LDAP source(s). To do this manually is time consuming and open for error. Thus, there needs to be a way to script or automate this process. This document will address the automated solution using what is termed in OBI as the patching process. The first migration from Dev->Test, Dev->Prod, or source->target will need to be done manually. Meaning, the RPD that is ready to be migrated to the target environment will need to have its physical connections and LDAP source(s) manually changed for that target environment. That would be done using the BI Admin Tool in offline mode. After which, we can test our changes to ensure that the connections and

http://blogs.devhorizon.com/reza/2008/10/20/say-goodbye-to-iis-say-hello-to-httpsys/ Say Goodbye to IIS, Say Hello to HTTP.SYS! With all the issues IIS caused in the previous versions of SSRS, specially to configure it to interact with other applications (such as SharePoint) hosted in IIS , in SSRS 2008, Microsoft made a major architectural shift to move toward to a *real* Single Service Architecture that would eliminate dependency on IIS. You no longer require having IIS installed on the RS box and, even nicer; you don’t have to install SQL on that RS box! Well, let me rephrase what I just said above. SSRS doesn’t require IIS to function, but this only applies when you configure it in native mode. In integrated mode and since you have to join the SSRS machine to the farm, you have to install SharePoint WFE components on RS machine and this means dependency on IIS, but again that’s the dependency SharePoint has on IIS , not SSRS! This shifting architectural decision took care of two ve