Moving Oracle BI EE to an Existing Production Environment When New Hardware Is

21-90 Oracle Fusion Middleware Administrators Guide ■ Task 5, Move Oracle Business Intelligence Discoverer to the New Production Environment Task 1 Move the Database, Middleware Home and Perform the Initial Configuration To move the database, Middleware home, and perform the initial configuration: 1. Move or create the database and the schemas, as described in Section 21.3.2 . 2. Move the Middleware home and binary files, as described in Section 21.3.3 . 3. Configure the components, as described in the Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer. For Oracle Portal, this includes installing Oracle Internet Directory and Oracle Single Sign-On Release 10.1.3.4. For Oracle Portal, specify the credentials to connect to Oracle Internet Directory at the Configure Components screen. Task 2 Move Oracle Portal to the New Production Environment To move the Oracle Portal configuration to a new production environment: 1. Create a transport set on the test instance that contains the list of page groups to be moved. For information about creating a transport set, see Creating Transport Sets in the Oracle Fusion Middleware Administrators Guide for Oracle Portal. 2. Export the data from the test environment, as described in Exporting Data in the Oracle Fusion Middleware Administrators Guide for Oracle Portal. 3. On the production environment, create a database link to the test environment, as described in Creating a Database Link in the Oracle Fusion Middleware Administrators Guide for Oracle Portal. 4. Before moving data from a source portal you must first register the portal. Once registered, the source portal can be selected and used to specify the data source in the Transport Sets. See Register a Source Portal in the Oracle Fusion Middleware Administrators Guide for Oracle Portal. 5. Before importing your objects, the contents of the transport set must first be moved to the transport set tables on the target system. You do this by acquiring the transport set from the test environment, using the registered database link described in Step 1. For information about acquiring the transport set, see Moving Data to the Target System in the Oracle Fusion Middleware Administrators Guide for Oracle Portal. 6. Import the data, as described in Import in Oracle Portal in the Oracle Fusion Middleware Administrators Guide for Oracle Portal. 7. Move users and groups from the LDAP directory in the test environment to the LDAP directory in the production environment, as described in Migrating Users and Groups in the Oracle Fusion Middleware Administrators Guide for Oracle Portal. 8. Import the external applications list using the SSOMig utility: a. Run ssomig in export mode on the test environment. The command creates a dump file. For example: ssomig -export -s orasso -p orasso_schema_password -c tns_alias_for_sso_schema -log_d directory_where_dump_needs_to_be_created -log_f ssomig.log -d ssomig.dmp Moving from a Test to a Production Environment 21-91 b. Run ssomig in import mode on the production environment, specifying the dump file created in the previous step. For example: ssomig -import -overwrite -s orasso -p orasso_schema_password -c tns_alias_for_sso_schema -d ssomig.dmp -log_d directory_where_dump_is_located -discoforce 9. For the following files, copy any customizations that you want to maintain from the test environment file to the production environment file: DOMAIN_HOMEconfigfmwconfigserversWLS_ PORTALapplicationsportalconfigurationportal_plsql.conf DOMAIN_HOMEconfigfmwconfigserversWLS_ PORTALapplicationsportalconfigurationportal_dads.conf DOMAIN_HOMEconfigfmwconfigserversWLS_ PORTALapplicationsportalconfigurationappConfig.xml 10. If you modified any configuration files, restart the Managed Server WLS_ PORTAL. Note that when Oracle WebCenter or Oracle Portal is moved from test to production using export and import, portlet customizations are included in transport set. You do not need to take any additional steps. Task 3 Move Oracle Forms Services to the New Production Environment To move Oracle Forms Services to a new production environment: 1. Stop the processes running in the Oracle instance and stop the Managed Servers in the production environment, using the following commands: ORACLE_INSTANCEbinopmnctl stopall DOMAIN_NAMEbinstopManagedWebLogic.sh managed_server_name admin_url username password 2. Copy the Oracle Forms Services application files FMX, MMX, and PLX from the test environment to the production environment. The location of the files may be specified in the Forms environment configuration file, default.env. Note that if the files are in a shared network location, you do not need to copy them to the production environment. Instead, add the location to the default.env file. 3. Move the application-related data from the test environment to a database in the production environment using database migration tools. 4. Create entries in the SQLNet configuration files to refer to the database in the production environment. 5. Forms applications have single sign-on user names and passwords mapped to the database connect strings. This information is stored in Oracle Internet Directory. Move the Forms RAD data from Oracle Internet Directory in the test environment to Oracle Internet Directory in the production environment. See Step 3 in Task 1, Move Oracle Internet Directory to an Existing Production Environment in Section 21.4.1 . 6. Copy any customizations in the following files that you want to maintain from the test environment file to the production environment file: