Moving Oracle Real-Time Decisions to a New Production Environment

Moving from a Test to a Production Environment 21-93 For the Forms utilities-specific configuration wrapper shell scripts, replace any occurrences of the Oracle home and Oracle instance with the details for the production environment. 8. Start the components in the instance and start the Managed Server, using the following commands: ORACLE_INSTANCEbinopmnctl startall DOMAIN_NAMEbinstartManagedWebLogic.sh managed_server_name admin_url 9. If you made customizations to the Forms Java EE application .ear file, such as overriding the default Forms servlet access URL, custom deploy the Forms Java EE application .ear file and create servlet aliases similar to test environment in the Forms Java EE application web.xml file. Task 4 Move Oracle Reports to the New Production Environment To move Oracle Reports to the production environment: 1. For the following Oracle Reports Server configuration files, merge changes made from the test environment to the production environment files. Note that you cannot just copy the files from the test environment to the production environment, because they may have environment-specific information such as Oracle home and Oracle instance names or locations and port numbers. Forms utilities-specific configuration wrapper shell scripts UNIX: ORACLE_INSTANCEbinfrmbld.sh ORACLE_INSTANCEbinfrmcmp.sh ORACLE_INSTANCEbinfrmplsqlconv.sh ORACLE_INSTANCEbinfrmxmlsg.sh ORACLE_INSTANCEbinfrmcmp_batch.sh ORACLE_INSTANCEbinfrmf2xml.sh ORACLE_INSTANCEbinfrmxml2f.sh ORACLE_INSTANCEbinfrmxmlv.sh Windows: ORACLE_HOME\bin\frmbld.bat ORACLE_HOME\bin\frmcmp.bat ORACLE_INSTANCE\bin\frmplsqlconv.bat ORACLE_INSTANCE\bin\frmxmlsg.bat ORACLE_INSTANCE\bin\frmcmp_batch.bat ORACLE_INSTANCE\bin\frmf2xml.bat ORACLE_INSTANCE\bin\frmxml2f.bat ORACLE_INSTANCE\bin\frmxmlv.bat Type of File Location Reports standalone server configuration ORACLE_INSTANCEconfigReportsServerComponentserver_ namerwserver.conf ORACLE_INSTANCEconfigReportsServerserver_namejdbcpds.conf ORACLE_INSTANCEconfigReportsServerserver_namexmlpds.conf ORACLE_INSTANCEconfigReportsServerserver_nametextpds.conf ORACLE_INSTANCEconfigReportsServerserver_namerwnetwork.conf ORACLE_INSTANCEconfigReportsServerserver_namecomponent-logs.xml ORACLE_INSTANCEconfigReportsServerserver_namelogging.xml Type of File Location 21-94 Oracle Fusion Middleware Administrators Guide 2. For the following Oracle Fusion Middleware configuration files, which are related to Oracle Reports Server configuration files, merge changes made from the test environment to the production environment files. Note that you cannot just copy the files from the test environment to the production environment, because they may have environment-specific information such as Oracle home and Oracle instance names or locations and port numbers. Reports in-process server and servlet configuration DOMAIN_HOMEconfigfmwconfigserversserver_nameapplicationsreports_ versionconfigurationcgicmd.dat DOMAIN_HOMEconfigfmwconfigserversserver_nameapplicationsreports_ versionconfigurationrwservlet.properties DOMAIN_HOMEconfigfmwconfigserversserver_nameapplicationsreports_ versionconfigurationrwserver.conf DOMAIN_HOMEconfigfmwconfigserversserver_nameapplicationsreports_ versionconfigurationjdbcpds.conf DOMAIN_HOMEconfigfmwconfigserversserver_nameapplicationsreports_ versionconfigurationxmlpds.conf DOMAIN_HOMEconfigfmwconfigserversserver_nameapplicationsreports_ versionconfigurationtextpds.conf DOMAIN_HOMEconfigfmwconfigserversserver_nameapplicationsreports_ versionconfigurationrwnetwork.conf DOMAIN_HOMEconfigfmwconfigserversserver_nameapplicationsreports_ versionconfigurationlogging.xml DOMAIN_HOMEconfigfmwconfigserversserver_nameapplicationsreports_ versionconfigurationlogmetadata.xml DOMAIN_HOMEconfigfmwconfigserversserver_nameapplicationsreports_ versionconfigurationjazn-data.xml Reports Tools configuration ORACLE_INSTANCEconfigReportsToolsrwbuilder.conf ORACLE_INSTANCEconfigReportsToolsrwnetwork.conf ORACLE_INSTANCEconfigReportsToolsjdbcpds.conf ORACLE_INSTANCEconfigReportsToolsxmlpds.conf ORACLE_INSTANCEconfigReportsToolstextpds.conf ORACLE_INSTANCEconfigReportsToolscomponent-logs.xml ORACLE_INSTANCEconfigReportsToolslogging.xml Reports Bridge configuration ORACLE_INSTANCEconfigReportsBridgebridge_namerwbridge.conf ORACLE_INSTANCEconfigReportsBridgebridge_namerwnetwork.conf ORACLE_INSTANCEconfigReportsBridgebridge_namecomponent-logs.xml ORACLE_INSTANCEconfigReportsBridgebridge_nameloggin.xml Reports shell scripts UNIX ORACLE_INSTANCEconfigreportsbinrw.sh Windows ORACLE_INSTANCE\config\reports\bin\rw.bat UNIX ORACLE_INSTANCEconfigreportsbinreports.sh Windows ORACLE_INSTANCE\config\reports\bin\reports.bat UNIX ORACLE_INSTANCEconfigreportsbinnamingservice.sh Windows ORACLE_INSTANCE\config\reports\bin\namingservice.bat Type of File Location JPS configuration DOMAIN_HOMEconfigfmwconfigjps-config.xml DOMAIN_HOMEconfigfmwconfigjps-config-jse.xml DOMAIN_HOMEconfigfmwconfigsystem-jazn-data.xml Type of File Location Moving from a Test to a Production Environment 21-95 3. If you created additional Oracle Reports Server component instances in the test environment, create these in the production environment using opmnctl. 4. For resources related to Oracle Reports Server, take the following actions: ■ Copy any fonts used in the test environment from the directory specified by environment variable REPORTS_FONT_DIRECTORY to production environment. By default, they are in ORACLE_INSTANCEreportsfonts. ■ Move the Common UNIX Printing System CUPS printing configuration to the production environment, if applicable. For more information about using CUPS with Oracle Reports, see Enhanced Printing on Linux Using CUPS in the Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services. 5. For Reports definition files and data tables, take the following actions: ■ Copy the reports files, such as RDF, JSP, REP, and XML files, used in the test environment to the production environment. ■ Deploy JSP Web reports to the production environment in the following location: DOMAIN_HOMEserversWLS_REPORTSstagereportsreportsweb.war ■ Move Reports-specific data tables that are referred to in the RDF files to the database in the production environment using database migration tools, such as the Oracle Database export and import utilities. 6. For Reports job-related configuration files, take the following actions: ■ Copy Reports Server cache files to the following location in the production environment: ORACLE_INSTANCEreportscache ■ For Reports scheduled job information, copy the server data server_name.dat file to the following location in production environment: ORACLE_INSTANCEreportsserver Note that because the server name is generated automatically when it is created and the .dat file is named with the server name, the name of the .dat file differs between the test environment and the production environment. Depending on whether it is a standalone server or an in-process server, the name takes one of the following forms: ReportsServer_hostname_instanceName Forms and Reports common files Font setup, aliasing, subsetting, embedding: ORACLE_INSTANCEconfigFRComponentfrcommonguicommontkadminUifont.ali Printer configuration UNIX only: ORACLE_INSTANCEconfigFRComponentfrcommonguicommontkadminuiprint.txt Toolkit configuration, encoding UNIX only: ORACLE_ INSTANCEconfigFRComponentfrcommonguicommontkadminuTk2Motif.rgb PPD files UNIX only: ORACLE_INSTANCEconfigFRComponentfrcommonguicommontkadminPPD AFM files UNIX only: ORACLE_INSTANCEconfigFRComponentfrcommonguicommontkadminAFM Type of File Location 21-96 Oracle Fusion Middleware Administrators Guide rep_wls_reports_hostname_instanceName Change the name of the file to reflect the host name and Oracle instance name in the production environment. 7. If the job repository or job status repository is configured in the database, you must create the same schemas in the production environment database and move the data: a. Use the following script: ORACLE_HOMEreportsadminsqlrw_job_repos.sql b. Move any data from the test database for the schemas RW_JOBS, RW_ SERVER_JOB_QUEUE, and RW_SERVER_QUEUE to production database using database migration tools, such as the Oracle Database export and import utilities. 8. Move any user and reports server security policy information. See Securing Oracle Reports in the Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services. 9. If you use Oracle Internet Directory as the identity and policy store, 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 . 10. If you used JAZN-XML-based identity and policy store in the test environment, move them to the LDAP in the production environment. You can use the WLST command migrateSecurityStore, as described in Migrating Policies with the Command migrateSecurityStore in the Oracle Fusion Middleware Application Security Guide. 11. Migrate the credential store, using the WLST command migrateSecurityStore, as described in Migrating Credentials with the Command migrateSecurityStore in the Oracle Fusion Middleware Application Security Guide. 12. Move any database proxy users to the production database using database cloning tools. 13. If any Reports plug-ins are registered, copy the corresponding .jar files to the production environment and add the path to the files to the environment variable REPORTS_CLASSPATH. Task 5 Move Oracle Business Intelligence Discoverer to the New Production Environment To move Oracle BI Discoverer to the new production environment: 1. If you have modified the default user preferences, copy the following files from the test environment to the production environment: ORACLE_INSTANCEconfigPreferenceServerdisco-comp-name.reg_key.dc ORACLE_INSTANCEconfigPreferenceServerdisco-comp-namepref.txt ORACLE_INSTANCEconfigPreferenceServerdisco-comp-namedefaults.txt 2. If you have changed the Oracle BI Discoverer settings, copy following files from the test environment to the production environment: DOMAIN_HOMEconfigfmwconfigserversWLS_DISCOapplicationsdiscoverer_ 11.1.1.3.0configurationconfiguration.xml