Moving Between Environments

Moving from a test to a production environment in 12.2.1 applies solely to metadata (content, data model and authorization).

To move from a test environment to a production environment you would typically develop and test applications in a test environment and then roll out the test applications (and optionally test data), in the production environment on the same operating system. This can also include moving from a single to a multiple computer environment.

Assumptions

• You must have file system (offline) permissions.
• Commands can be run offline only.
• Command is read-only for export (source system is unchanged).

Prerequisites

• Uses WLST scripting.

  See Using the WebLogic Scripting Tool (WLST).

• BI deployments A and B service instances exist in different domains.
• Changes will have been made to BI deployment A service instance.
• Admintool (datamodel), Answers (catalog), Fusion Middleware Control (security), or WLST. These tools are only required if you want to make changes to metadata.
• Command is read-only.

To move from a test to a production environment:

The following options are available:

• export all

  You might use this option for example, if all users and datasources are the same between two systems.

• export without user folder content

  You might use this option as part of user acceptance testing, where test users have different content but access to the same data sources (although with different data access)

• export without connection pool credentials

  You might use this option if all you need to do is to move upgraded metadata from one system to another after it has been tested (no users in common, different datasource security).

To support these options the export command has optional parameters to export user folder content, or connection pool credentials as follows:

exportServiceInstance(domainHome, serviceInstanceKey, workDir, exportDir, applicationName=None, applicationDesc=None, applicationVersion=None, includeCatalogRuntimeInfo=false, includeCredentials=None)

1. (Optional) If you want to preserve existing user production Service Instance folders, use the runcat archive command against production to save user folders.
2. Run the exportServiceInstance command to export the TEST service instance to a BAR file (with or without User folders and connection credentials).

   For example:

   exportServiceInstance('/u01/Oracle/Middleware/Oracle_Home/user_projects/domains/bi', 'ssi', '/u01/workDir', '/u01/exportDir', applicationName=None, applicationDesc=None, applicationVersion=None, includeCatalogRuntimeInfo=false, includeCredentials=None)
   

   This example exports service instance with key ssi, to /u01/exportDir/ssi.bar.

3. Run the importServiceInstance command to import the exported TEST BAR file into the PROD service instance.

   importServiceInstance('/u01/Oracle/Middleware/Oracle_Home/user_projects/domains/bi','ssi','/u01/exportDir/ssi.bar')
   

   This example imports the BAR file /u01/exportDir/ssi.bar into the service instance with key ssi.

4. If you used the runcat archive command in step 1, you can now use the runcat unarchive command to put production user folders back in place.

Post Conditions:

• PROD Service Instance metadata will be replaced with TEST metadata.
• To restate, any content created directly in PROD Service Instance will be replaced or lost.
• No configuration is changed on domain hosting PROD Service Instance
• No metadata or configuration is changed on domain hosting TEST Service Instance.