This chapter describes the post-installation steps that you must perform after installing Oracle Enterprise Repository.
This chapter includes the following sections:
Start the Administration Server and Log Into the Oracle Enterprise Repository Web-based Console
Use the Oracle Enterprise Repository Diagnostics Testing Tool
After configuring your application server, follow these steps to start your application server and log in to the Oracle Enterprise Repository web-based console.
Start the Administration Server. See Section 3.3.1, "Starting the Administration Server".
Start the Oracle Enterprise Repository managed server. See Section 3.3.2, "Starting the Managed Server".
Point your browser to the Oracle Enterprise Repository application.
For example: http://myserver.domainname.com:7101/oer/
On the login screen, enter admin for the Username and weblogic1 for the Password. This is the default administrative account installed with Oracle Enterprise Repository. You are forced to change the default Administrator password on the first successful login to the Oracle Enterprise Repository web application. You can change the default password through the Administration tab in Oracle Enterprise Repository at a later time.
Note:
If your organization requires a user name and password each time you log in to Oracle Enterprise Repository, clear the Enable Automatic Login option.Click Login.
The Login Stats dialog displays a welcome message that includes the date and time of your login.
Click Close.
For more information about using the Oracle Enterprise Repository console, see the Oracle Fusion Middleware Developer's Guide for Oracle Enterprise Repository.
The Diagnostics tool allows testing and troubleshooting of certain aspects of Oracle Enterprise Repository, including testing for:
Checking Product Version Information
Servlet Functionality
Required Libraries
Database Connectivity
List System Paths
Run Pre-Compile Servlet
The Oracle Enterprise Repository diagnostic tools are available only when using an application server JVM parameter for security reasons. To enable the Oracle Enterprise Repository diagnostics features, use the following parameter:
-DdiagPagesEnabled=true
This parameter can be added to the application server's environment in various ways. For WebLogic Server, edit the ORACLE_HOME/user_projects/domains/DOMAIN_NAME/bin/setStartupEnv.sh or *.cmd file and add -DdiagPagesEnabled=true to the EXTRA_JAVA_PROPERITES="${EXTRA_JAVA_PROPERTIES} line in this file. Restart the Oracle Enterprise Repository managed server.
To launch the Diagnostics tool, navigate to the http://host_name/oer/diag/index.jsp page of the Oracle Enterprise Repository console. For more information, see "Password Encryption" in the Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Repository.
Prior to importing the Oracle Enterprise Repository Policy Management solution pack, you must enable the system settings for policy management to ensure that the policies are applied correctly.
For more information about the system settings that must be enabled before importing the policy management solution pack, see "Enable the Policy Management System Settings" in Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Repository.
Oracle bundles base sample data for users to help you get started using the Enterprise Repository. Additionally, depending upon the edition of Oracle Enterprise Repository that you purchased, you can also import supplemental Solution Packs. These supplemental Solution Packs are located with your installation under the <FMW_HOME>/oer/modules/tools/solutions/ folder. Table 6-1 describes the available Solution Packs for Oracle Enterprise Repository 12c.
Table 6-1 Oracle Enterprise Repository Solution Packs
| Solution Pack | File Name | Description |
|---|---|---|
|
12.1.3.0.0-Policy-Management-Solution-Pack.zip |
Install this Solution Pack to use policy management features with Oracle Enterprise Repository. |
|
|
Harvester Solution Pack |
12.1.3.0.0-OER-Harvester-Solution-Pack.zip |
Install this Solution Pack to use Business Process Management Workflows, the Harvester, or the Oracle Registry Repository Exchange Utility, which exchanges data between Oracle Enterprise Repository and Oracle Service Registry. |
Note:
For information about installing Oracle Enterprise Repository Solution Packs, see "Import Export Tool" in Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Repository.Testing the Oracle Enterprise Repository installation involves a number of tasks that ensure the proper operation of initial Oracle Enterprise Repository features and functions.
Asset submission is performed on the Oracle Enterprise Repository Assets page.
In the Assets panel, click Submit an Asset.
In the Asset Submission dialog, complete the following fields:
Asset Name
Version
Type
Description
URL: enter the file location (for example, http:/www.example.com/repository/)
Click Submit to submit the asset to the registrar.
Note:
Attempts to save as asset without first completing all required data fields results in a warning message. A confirmation message indicates the asset was successfully submitted to the Oracle Enterprise Repository registrar.Click Close.
For more information, see Oracle Fusion Middleware User's Guide for Oracle Enterprise Repository.
The asset acceptance process is performed by the Oracle Enterprise Repository registrar using the Asset Editor. The registrar makes decisions about an asset based on company requirements. To accept and assign an asset means that the registrar accepts the asset and assigns it to another person to shepherd it through the remainder of the registration process.
On the Assets page, click the Edit/Manage Assets option to launch the Asset Editor.
Expand the Submitted folder in the Assets tree.
Expand the Pending folder and open the asset submitted in Submit an Asset.
For the purposes of this exercise, click Accept.
The asset moves to the Under Review folder in the tree, and also appears in each of the workflow folders under the asset. The workflow folders correspond to tabs in the Asset Editor.
For more information, see Oracle Fusion Middleware User's Guide for Oracle Enterprise Repository.
The asset acceptance process is performed by the Oracle Enterprise Repository registrar using the Asset Editor.
On the Overview, Support, Technical, and Tests tabs, complete the remaining information, including the notification email, licensing information, and support contacts as appropriate.
Note:
The notification email automatically sends notification to the email address when the asset is downloaded/selected for use. The asset can be moved from its original location to the storage repository on this tab.Click Approve on a tab. The tab label changes color and the Approve button changes to Unapprove.
Click the Taxonomy tab.
Assign the asset to the appropriate categories and/or domains.
Note:
Categories and domains are configurable. For more information, see Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Repository.Enter any keywords and classify the asset into one of five categories:
Raw: No assurance of quality or completeness.
Educational: To be used for educational purposes only. The asset may not be complete in terms of documentation, test results, or other information.
Approved: Approved for use by the registrar
Recommended: Successfully used on at least one project.
Mandated: Must be used whenever the functionality it provides is needed. (This is especially relevant for web services that access customer data, process payments, and so on.)
Click Approve.
The tab label changes color, and the Approve button changes to Unapprove.
Click the Documentation tab.
When all of the documentation requirements are met, click Approve.
Continue the approval process for each of the remaining tabs.
On the Administration tab, click Register to complete the registration process, or click Assign to assign the asset to someone else.
Click Save to save changes in the File menu.
The asset is moved to the Registered folder and each action (approval of tabs, field value updates) are also recorded in the Audit log found on the asset's Administration Tab.
For more information, see Oracle Fusion Middleware User's Guide for Oracle Enterprise Repository.
Complete the process by searching for the newly registered asset you created.
On the Assets page, use the Search option to locate the asset.
The asset should appear in the list in the upper frame of the main Assets page, indicating that the XML data stored as a BLOB is correctly loaded in the database.
Click the asset to open the asset detail in the lower frame of main page.
The system setting, cmee.jws.pass-all-cookies, must be enabled to ensure the proper functioning of the Asset Editor. To enable this system setting, perform the following tasks:
On the Admin page, click System Settings.
Enter cmee.jws.pass-all-cookies in the Enable New System Setting field, and then click Enable.
Click Save when finished.
The optional Export to API Catalog feature patch allows you to export API assets from Oracle Enterprise Repository directly into a running Oracle API Catalog instance.
Note:
The Export to API Catalog feature requires the 12.1.3 versions of Oracle Enterprise Repository and Oracle API Catalog.You must also have imported the API asset type from the OER 12.1.3 Harvester Solution Pack. See Section 6.3 for more information.
To install the Export to API Catalog feature patch:
Acquire the zip file for bug number 20191036 from My Oracle Support. Extract the contents of the patch file to a local directory.
Stop all running Oracle Enterprise Repository servers.
Follow the instructions in the patch's README.txt file to apply the patch.
Edit the oac.xml file, copied to the <Middleware_Home>/user_projects/domains/<oer_domain>/config_oer directory during the installation process, to point to running Oracle API Catalog instances to which you want to export API assets. The following example displays a sample oac.xml file with three API Catalog servers after configuration.
<?xml version="1.0" ?>
<oac-servers>
<oac-server>
<name>Production</name>
<uri>http://01.example.com:8111/oac</uri>
<username>admin</username>
<password>password</password>
</oac-server>
<oac-server>
<name>Development</name>
<uri>http://02.example.com:8111/oac</uri>
<username>admin</username>
<password>password</password>
</oac-server>
<oac-server>
<name>Staging</name>
<uri>http://03.example.com:8111/oac</uri>
<username>admin</username>
<password>password</password>
</oac-server>
</oac-servers>
Use the encrypt.sh/encrypt.bat utility, as described in "Export to API Catalog Configuration File" in Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Repository, to encrypt the passwords in the oac.xml file.
Start all Oracle Enterprise Repository servers.
The Export to API Catalog feature is now available. See "Exporting API Assets to API Catalog" in Oracle Fusion Middleware Developer's Guide for Oracle Enterprise Repository for information about using this feature.
Refer to the following documents for information about Using Oracle Enterprise Repository:
Oracle Fusion Middleware Concepts Guide for Oracle Enterprise Repository
Oracle Fusion Middleware Upgrade Guide for Oracle Enterprise Repository
Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Repository
Oracle Fusion Middleware Developer's Guide for Oracle Enterprise Repository