Documents

Www Rittmanmead Com 2008 04 Migration Obiee Projects Between

Description
Www Rittmanmead Com 2008 04 Migration Obiee Projects Between
Categories
Published
of 12
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
Share
Transcript
  pdfcrowd.comopen in browserPRO version Are you a developer? Try out the HTML to PDF API HomeAboutCareersClientsConsultingTrainingSupportArticlesBlog Migrating OBIEE Projects Between DEV and PROD Environments  April 28th, 2008 by Mark Rittman One of the clients I’m working with this week wants to go through how OBIEE environments are migrated from oneenvironment to another. They are working on a solution for their organization where a team of developers put together aninitial first cut of the repository and web catalog, and then at various points from then onwards they will either completelyrefresh the production environment using what’s in development, or more usually they’ll take an element of what’s indevelopment, say an individual subject area, set of fact and dimension tables or a set of dashboards or reports, and deploythose as a “patch” in to production.When working with OBIEE, my understanding is that you can have one BI Server per physical/virtual server, which canconnect to one or more repositories, though only one of them is the “default”. You also normally then set up one BIPresentation Server instance which connects through to the default repository for the corresponding BI Server. In reality thismeans that each OBIEE environment consists of one BI Server and one Presentation server on the same physical server (together usually with an installation of BI Publisher, configured to use BI Server security), or in some cases the BI Server andBI Presentation Server might be split onto different physical servers, and possibly further clustered on to more server s if theexpected load is high.You can, it should be noted, set up additional Presentation Servers on the same physical server, each of them connectingthrough to the same BI Server  but with different “default” repositories, which gives you a way to create your DEV, PROD andother environments on the same physical server (if it’s a beefy Unix box, for example). However this is a fairly complex task(see this blog posting  by Borkur) and it’s usually easier to have a simple pairing of one BI Server, one Presentation Server (plus the BI Publisher, Delivers etc servers) per environment with all of these contained on their own physical server. The restof the migration steps in this posting therefore assume that you’ve got each environment set up in this straightf orward way, with OBIEE already installed on each server and a single installation of BI Administrator that can connect to both of them.When you think about migrating an OBIEE environment, there are four main things you’ll want to move across:1. The BI Server repository, which contains the enterprise semantic layer, variables, security settings (including users andgroups if you use RPD-based security) and connection pool settings through to the physical data sources. The contents Search the blogRecent Posts  Analytics with Kibana andElasticsearch through Hadoop –part 3 – Visualising the data inKibana Analytics with Kibana andElasticsearch through Hadoop –part 2 – Getting data intoElasticsearch Analytics with Kibana andElasticsearch through Hadoop –part 1 – IntroductionUKOUG Partner of the Year  AwardsOracle BI Cloud Service for SaaS Application Reporting Part 1:Integrating BICS toSalesforce.com using REST APIs Top Posts OBIEE 11g Security Week :Managing Application Roles andPolicies, and Managing SecurityMigrations and DeploymentsUpgrading OBIEE to 11.1.1.7OBIEE 11gR1 : Architecture andUse of WebLogic Server OBIEE 11g Security Week :Connecting to Active Directory,and Obtainin Grou Membershi  pdfcrowd.comopen in browserPRO version Are you a developer? Try out the HTML to PDF API of the repository are normally contained with a single RPD file contained in the %ORACLEBI/%server/Repositorydirectory, with %ORACLEBI% being determined by the SAROOTDIR environment variable and the current RPD in use(only one can be online at any one time per installation of OBIEE) being determined by the%ORACLEBI%/server/config/NQSConfig.INI file.2. The BI Presentation Server web catalog, which contains the reports, dashboards, prompts, ibots and so on, together with a separate set of users and roles (usually propagated from the BI Server repository) and their permissions on theweb catalog objects. Unlike the BI Server repository, the web catalog is stored in a set of XML files, one per web catalogobject organized into folders, plus an ATR file per folder that contains permissions on the objects within them. The filesthat make up the web catalog are held in the %ORACLEBIDATA%/web/catalog directory, with %ORACLEBIDATA%being determined by the SADATADIR environment variable.3. Connections through to physical datasources, held on the server containing the BI Server, which when working in anOracle environment are usually contained in a single TNSNAMES.ORA file. The connection pool settings in the BIServer repository references the connections in this file.4. The BI Publisher Report Catalog, which contains the XDO files that define the BI Publisher reports. It is assumed that BIPublisher is configured to use BI Server security or LDAP security, therefore the users and groups in the BI Publisher OC4J container will not need to be migrated. This catalog is normally found in the %ORACLEBI%xmlp/XMLP/Reportsdirectory.Note that this list isn’t exhaustive – if you know of anything else that needs migrating (perhaps to do with Disconnected Analytics, perhaps the configuration files for the Presentation Server) let me know by adding a comment to this posting.In a typical customer situation, the environment migration lifecycle looks something like this: Step 1 : Initial Development (“First Cut”)  All development of the repository and web catalog initially happens in DEV. At some point, the initial work is complete and theDEV environment is ready to be copied into PROD (or TEST, or whatever) Step 2 : First Deployment to Production The initial creation of the PROD BI Server repository is done through copying the DEV RPD file in to the PROD environment.Copying across the entire RPD file will bring across all subject areas, physical models, presentation models, securitysettings, users and groups (if RPD security is used), variables and so on. If your OBIEE server does not have aTNSNAMES.ORA file on it to connect to the source database, you will need to copy this across from the DEV server as well.You can either copy this repository “interactively” by using the filesystem explorer application and cut and paste, or you canscript the copy using a batch or shell script. If you need to make changes to the repository “en-route” to the PRODenvironment, you can instead of copying the repository “whole”, export it into a UDML text file using the using the nQUDMLGen.exe  utility within the %ORACLEBI/server/bin directory, alter any settings that you need to change using a perlscript for example, and then import the amended text file into a new, blank PROD repository using the nQUDMLExec.exe   from Database Tables Analytics with Kibana andElasticsearch through Hadoop -part 3 - Visualising the data inKibana Random Posts Introduction to the BI Apps11.1.1.7.1 - Release OverviewInstalling obi-metrics-agent,Graphite, and collectlMDS XML versus MUDE Part 4:Simple Multi-Branch DevelopmentRittman Mead at ODTUGKScope'14, SeattleEnd-to-End ODI12c ETL on OracleBig Data Appliance Pt.3 : Enhancewith Oracle Reference Data viaSqoop, and CKMs Tags 11g   Big Data Appliance BIP   BI Publisher    dw  em12c Endeca   exalytics extremebi   git goldengate hadoop   Hive   init.d  install linux   MDS XML   monitoringnew features   nqcmd   OBIA obiee   odi   odi12c opatch   Oracle   Oracle BI Applications   oracle dataintegrator    OracleEndeca   Oracle EndecaInformation Discovery  owb performance   Real Time  pdfcrowd.comopen in browserPRO version Are you a developer? Try out the HTML to PDF API . , automating changes to connection pool settings using UDML during a migration.The corresponding Web Catalog is migrated by copying the contents of the %ORACLEBIDATA%/web/catalog directory to thecorresponding directory on the production server. This directory contains top-level folders for Delivers and Answers/Dashboard contents, like this:With each top-level folder then containing sub-folders and then individual file pairs for each web catalog item, like this: Decisions   replication ReportService RTD  runReport sampleapp   screen   scripting security  startup testing training   XML  pdfcrowd.comopen in browserPRO version Are you a developer? Try out the HTML to PDF API The BI Publisher report catalog is migrated by copying the contents of the %ORACLEBI%/xmlp/XMLP/Reports directory andthe %ORACLEBI%/xmlp/XMLP/users directories over to the production BI Publisher environment.In all cases, the RPD file, the contents of the Web Catalog files, any UDML files and BI Publisher report files can be stored ina version control system to create versioned releases of your project metadata. 3. Subsequent Full Refreshes of Production If production ever needs to be fully refreshed with what is in development, then the above process can be repeated. Notehowever that ordinarily, any reports or customizations that happened in the production environment (including users’ customdashboards) will be overwritten using this process; these can however be preserved if the sub-folders below the%ORACLEBIDATA%/web/catalog/ web_catalog_name /root/users`are saved before being overwritten by the DEV web catalogfiles, and then copied back after the migration takes place.
Search
Tags
Related Search
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks