Move Between Environments Using the Oracle WebLogic Scripting Tool

Moving from a test to a production environment 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.

You can also use snapshots to move between environments in Oracle Analytics Server instead of using the Oracle WebLogic Scripting Tool. See Take Snapshots and Restore.

Prerequisites:

You must have file system (offline) permissions.
Service instance deployments A and B must exist in different domains.
Model Administration Tool (the data model), Answers (the Presentation Catalog), Fusion Middleware Control (security), or Oracle WebLogic Scripting Tool. You only need these tools if you want to make changes to metadata.

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 data sources 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 updated metadata from one system to another after it's been tested (no users in common, different data source 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)

Optional: If you want to preserve existing user production service instance folders, use the runcat archive command against production to save user folders.
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 the service instance with key ssi, to /u01/exportDir/ssi.bar.
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.
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:

The PROD service instance metadata is replaced with TEST metadata.
Any content created directly in the PROD service instance is replaced or lost.
No configuration is changed on the domain hosting the PROD service instance.
No metadata or configuration is changed on the domain hosting the TEST service instance.