This chapter describes optional post upgrade tasks when upgrading from Oracle Enterprise Repository 11g to 12c.
This chapter contains the following sections:
Section 2.1, "Configuring Oracle Enterprise Repository Reports"
Section 2.4, "Upgrade Oracle Enterprise Repository Workflows"
This section provides an overview of the Business Intelligence (BI) Publisher and the process of installing it.
You must install and configure Oracle Business Intelligence Publisher to use reports in OER, which are available on the Oracle Enterprise Repository reports page.
If BI Publisher is used only with Oracle Enterprise Repository, then the Oracle Enterprise Repository pre-configured BI Publisher content is used. The Basic type of BI Publisher installation is recommended.
Oracle Enterprise Repository includes a collection of pre-configured BI Publisher content. This content needs to be deployed and configured before running any Oracle Enterprise Repository reports.
For more information about deploying Oracle Enterprise Repository pre-configured BI Publisher content, see "Configuring BI Publisher Enterprise Server" in the Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Repository.
You must edit the CustomReports.xml file, as mentioned in the steps below:
Navigate to the /WEB-INF/config/reports/ directory in the OER domain.
Open the customreports.xml file in a text editor.
Edit the meta-tags for report name, display name, description, and external to reference a custom report.
An installation of Oracle Enterprise Repository 11g may have several customizations that are unique to that installation. These are not limited to, but may include:
Open API programs written against the REX interface
Endpoint Event Subscriptions
Application Properties Moved to Database
The Diagnostics tool allows testing and troubleshooting of certain aspects of Oracle Enterprise Repository application. This section contains the following topics:
In Oracle Enterprise Repository, the Diagnostics page is disabled, by default. Navigate to http://host_name:port/application_name/diag/index.jsp (replace host_name with the appropriate location).
When you open the Diagnostics page in the default mode, the following message is displayed:
Diag pages are currently disabled. Please contact your Oracle Enterprise Repository Administrator.
To enable the Diagnostics page, perform the following steps:
Navigate to FMW_HOME/user_projects/domains/DOMAIN_NAME/bin/.
Edit setStartupEnv.sh or setStartupEnv.cmd before starting the Oracle Enterprise Repository server.
Set the -DdiagPagesEnabled JVM property to true in the EXTRA_JAVA_PROPERITES="${EXTRA_JAVA_PROPERTIES} line in this file.
Restart the Oracle Enterprise Repository server.
It is recommended to only enable when necessary and disable once the system is running without any issues.
Oracle Enterprise Repository 12c is now deployed. It is recommended that you test the installation using the Oracle Enterprise Repository Diagnostics page. The recommended tests are:
Product Version Information
Test Required Libraries
Test Database
To launch the Oracle Enterprise Repository Diagnostics tool, navigate to
http://host_name:port_number/application_name/diag/index.jsp
In addition to the Diagnostics Home and Oracle Enterprise Repository links, the left sidebar of the Diagnostics tool includes links to several tests that can be run to check your installation of Oracle Enterprise Repository. Click any of these links to display the available tests in the main pane of the Diagnostics tool.
Generic Web App
Installation Tests
Product Version Information
Provides information on the installed version of the Oracle Enterprise Repository, the version of the installed Oracle Enterprise Repository database, upgrade dates, and the maintenance mode setting for the database.
Snoop Servlet
Provides an output listing of all cookies, headers, CGI-Variables, Servlet Context Attributes, Session information and Session values set as a part of the request to the application server.
Test Required Libraries
Provides information about the application server's configuration regarding required JAR library files, installed XML parsers, and the presence of the minimally required Oracle Enterprise Repository properties files.
Run Active Diagnostic Test
Runs a JUnit test against the installed Oracle Enterprise Repository application. Many of these tests are required to allow Oracle Enterprise Repository to build and parse XML data.
Test Database
Provides insight into the JDBC driver functionality, including the number of database side functions that are expected to be supported. Also tests the connection string set in the database.properties file, provides additional information regarding the version of the JDBC driver, and may also indicate deficiencies within the database tables.
List System Paths
Lists the pathways (local and absolute URLs) configured within the cmee.properties file and, also those stored within the database. Also helps to indicate why some parts of the application deployment function while others do not (such as images not loading).
Tools
JSP Precompiler
Forces the application server to perform an immediate JIT compile of JSP pages within the Oracle Enterprise Repository application. This process greatly improves the performance of page loads if performed after each application server restart
Encrypt Strings for Passwords
Performs a Hash on a clear-text password string supplied in the text field. This feature is used for encrypting passwords to be stored within application properties files. This tool should not be used to encrypt user passwords. Contact Oracle Support for the proper procedure to update a password in the database.
Oracle Enterprise Repository Tests
Runtime - Configuration
List Enabled System Settings
Lists all values set in the Oracle Enterprise Repository database and, also those set in properties files.
Edit System Paths
Allows an administrator to make permanent changes to the cmee.properties file on the application server.
Runtime - Assets
List Types
Produces XML output that describes all Asset Types stored within the Oracle Enterprise Repository database.
Edit Asset Custom Data
Allows a registrar to modify XML data contained within an asset in the event that an asset's metadata is otherwise uneditable. Do not use this tool unless specifically directed by Oracle Support personnel.
Get XML: Show Type ID
Produces the XML description of a specific Asset Type based on the unique ID of the Asset Type record.
Get XML: Type ID As String
Produces the XML description of a specific Asset Type based on the unique ID of the Asset Type record as one continuous string.
Get XML: Type XML Schema
This tool produces the XML schema of a specific Asset Type based on the unique ID of the Asset Type record.
Get XML: Type XML Schema as String
This tool produces the XML schema of a specific Asset Type based on the unique ID of the Asset Type record as one continuous string.
Get XML: Asset ID
- Produces the XML data of an Asset based on the unique ID of the Asset.
- The include extended metadata option produces additional information related to Policies and other data.
Get XML: Asset ID as String
Produces the XML data of an Asset based on the unique ID of the Asset as one continuous string.
Runtime - Security
Optional Tests
SOAP Services
Test the SOAP URL for Rex API service using
http://server:port/oer_app_name/service/FlashlineRegistry?wsdl
This process produces the Oracle Enterprise Repository Web Service WSDL file.
Logging Options
To access the Oracle Enterprise Repository login page, click the Oracle Enterprise Repository link in the sidebar of the Diagnostics page.
To activate the debugging mode for the current session, click the turning logging on link in the main pane.
Oracle Enterprise Repository 12c requires that all cleartext passwords are encrypted.
See "Password Encryption" in the Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Repository for information about generating encrypted passwords.
To check the product version information, perform the following steps:
Click Installation Tests under Generic Web App.
Click Product Version Information in the main pane.
A new browser window opens to display information on the internal product version, database schema version, and information about the most recent upgrade/install.
To test the servlet functionality in Oracle Enterprise Repository, perform the following steps:
Click Installation Tests under Generic Web App.
Click Snoop Servlet in the main pane.
A new browser window opens to display information on the parameters passed from the Web client to server.
To test the required libraries, perform the following steps:
Click Installation Tests under Generic Web App.
Click Test Required Libraries in the main pane.
A new browser window opens to display information on the property files and system properties essential to proper functionality.
To test the database connectivity in Oracle Enterprise Repository, perform the following steps:
Click Installation Tests under Generic Web App.
Click Test Database in the main pane.
A new browser window opens to display information on container access, the availability of JDBC drivers and the presence of important Oracle Enterprise Repository data tables.
To list the system paths in Oracle Enterprise Repository, perform the following steps:
Click Installation Tests under Generic Web App.
Click List System Paths in the main pane.
A new browser window opens to display all Oracle Enterprise Repository paths.
To run the pre-compiler servlet, perform the following steps:
Click Tools under Generic Web App.
Click JSP Precompiler in the main pane.
A new browser window opens to display a list of system JSPs that have been pre-compiled for speedier first time access.
Note:
This servlet produces errors within the error log; reset logs before starting the application server.The additional Diagnostics testing tool functionality includes:
Testing browser redirection compatibility to both a standard URL or local file.
Listing all enabled Oracle Enterprise Repository Settings.
Listing all Types in the system.
Displaying XML for a specific Type (both editor and viewer).
Displaying xml for a specific asset.
Clustering Status shows a list of all nodes in the cluster.
Ensure that client browser and JRE installations have appropriately supported versions for Oracle Enterprise Repository.
The Oracle Enterprise Repository 12c contains new and updated express workflows that require an installed instance of Oracle SOA Suite and Oracle BPM Suite, both version 11.1.1.7 or higher. Workflows created in older versions of OER may not be compatible with this release.
See "Configuring Oracle Enterprise Repository Express Workflows" in Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Repository for more information.