OBIEE Code Migration Techniques

OBIEE Code Migration Techniques

Migration techniques for OBIEE components (RPD etc) into various test and production environments

           Dev  to  Integration to Production  best practices around code migration activities 

         RPD  Deployment  OBIEE 1og vs OBIEE 11g

OBIEE 10g	OBIEE 11g
This was performed by copying it from source (Dev)region and pasting it to respective environmentsbased on the request (DevQA-Prod).                                                   Change it instanceconfig.xml and NQSConfig.ini file then restart.	·     It is deployed through Enterprise Manager     http://host:7001/em         Navigation:BusinessIntelligence       Coreapplication>Deployment key in the RPD Credentials

RPD  Deployment  Best Practices \Migration Techniques.

Back up the entire RPD in source and target environments

•      RPD .
•      Catalog.

If the developers in Development Team are still updating the RPD notify them to make changes
 accordingly then ,once they are done with it take a quick backup of code to be moved
 (RPD & Web catalog)

Production  code Drop:At my prior client there were multiple development teams associated
 with clients different  business to avoid the code drop suggested  respective day with particular
 team provided them the template which contains the  before and after changes to the Catalog
 and  Subject Areas to be added \Deleted\ ADF Components deployment (score cards\gantt 
charts) developers have to fill that out send \upload the RPD & Web catalog  to the the 
Configuration Management Team .

Action Item for the Configuration Management Team\Administrators.

•     Notify the respective teams that  the system will not be available as part of the code drop .
•      It is usually done after hours  .
•    Launch the BI Administration Tool from the  Administrator’s machine make sure that the 
• connection pools are set properly in the source environment  RPD  change the data source name and
• password open the RPD always in Online Mode.

•          Perform the Consistency check (ctrl+k) save the RPD
•        Back up the entire RPD in source and target environments (RPD &Catalog) tar \zip it with  current date stamp.
•       Deploy RPD through EM  ONLINE MODE
•          Check RPD VERSIONING before and after deployment
•            Stop only the opmnctl services  and  start all
•          Either  STOP OPMCTL  FIRST 
•         Validate the new RPD Sequence in prod environment
•         Validate the Dashboards\Reports & Catalog (Folders) 
•         Make sure permissions are set after the code deployment.

Note:The Application Development team should always open the RPD in offline Mode 

CATALOG

Moving the catalog across the environment can be done in two ways

•  Enterprise Manager
•  Catalog Manager
•  Archive only Shared folders  not user folders if you do so there would be an crash of security .
•  To avoid overwrite rename the old folder and archive, delete the it . 

This we can do in multiple ways

•  Check if the request is to move Complete catalog or Few subject areas.
•     Check whether DEV & PRODUCTION Users are same  if it is “Yes”
•     Validate if the Users have Permissions to create ADHOC Reports if it is” Yes”.
•      Users have permissions .

Disadvantage\Issue: Moving the entire catalog with users having permission will overwrite the existing folders 
and  security there are chances  of getting crash.

As a best practice in OBIEE 11g always Archive \Unarchive the folders that needs to be moved from Dev-QA-Stag-Prod there 
are two ways to deal with it  .

• Login through EM 
•   Launch the Catalog Manager
• To Connect to Enterprise Manager (EM) you should have the  ADMIN /SUPER USER permissions.
• Login to the Dashboard –click on Catalog--- >Admin view

Mode :Offline  via  catalog  manager  identify the folder from source archive it   and  logon to em in prod \unarchive in target
  make sure to perform only the folders under Shared folders  not user folders

Multiuser Development environment(MUDE): Diff teams working on same RPD they have to go with
 checkin & checkout as this will avoid confusion and help the team in re-doing the activity.

MUDE Major Drawbacks:This has been determined after a POC at my prior client

• Improper checkin & checkout \lock out issue: