Skip Headers
Oracle® Fusion Middleware Upgrade Guide for Oracle Enterprise Repository
11g Release 1 (11.1.1.4.0)

Part Number E15746-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

1 Upgrading Oracle Enterprise Repository

This chapter provides an overview of the upgrade process tasks and requirements when upgrading from Oracle Enterprise Repository 10g Release 3 (10.3) and ALER 3.x versions. Use the following links for additional instructions specific to your application server.

This chapter contains the following sections:

1.1 Upgrade from Oracle Enterprise Repository 10g R3 to 11g R1

You can upgrade from Oracle Enterprise Repository 10.3 to Oracle Enterprise Repository 11g R1. This section contains the following topics:

1.1.1 Upgrade Process

To upgrade from Oracle Enterprise Repository 10.3 to Oracle Enterprise Repository 11g, perform the following steps:

  1. Backup the existing Oracle Enterprise Repository database.

  2. Encrypt clear text passwords within the existing database.properties and ldap.properties files by using the Oracle Enterprise Repository diagnostic tool.

    • Also, encrypt the activemq.xml and EndPointEventSubscription.xml files that contain the password properties and are found at the oer-app/WEB-INF/classes directory.

    • If you are upgrading from ALER 3.x, then change the <sub:uri> element in the EndPointEventSubscription.xml file, which represents the service URI for the supported server, to the following

      uncomment the following line:

      <sub:uri>albpmServices/aler_engine/ws/StatusChangeEndpointServiceListener</sub:uri>

      and comment the following line:

      <sub:uri>fuegoServices/ws/StatusChangeEndpointServiceListener</sub:uri>

    • Encrypt the passwords in the workflow.xml, which can be found at <Oracle_Home>\obpm\enterprise\server\aler_engine, and then backup this file.

  3. Backup existing Oracle Enterprise Repository application deployment:

    • It is recommended that you backup the entire <BEA_HOME>. This backup is necessary for some post-installation tasks, in addition to the application server upgrade.

    • For clustered deployments, each node of the cluster should be separately backed up as all nodes must have Oracle Enterprise Repository upgraded. For more information, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Repository.

  4. Verify required platforms and version information (including JDBC Driver version support), using Table 1-1, which describes the supported JDBC Driver file names for Oracle Enterprise Repository 11g and, also its mapping to the appropriate application server.

    Table 1-1 Oracle Enterprise Repository 11g Supported JDBC Driver Information

    App Server JDK Version Oracle JDBC Oracle Driver Version UDB JDBC UDB Driver Version SQL Server JDBC SQL Driver Version

    1.5.x

    ojdbc5.jar

    11.1.0.7.0-Production

    db2jcc.jar

    db2jcc_license_cu.jar

    db2jcc4.jar

    3.50.152

    sqljdbc4.jar

    2.0.1803.100

    1.6.x

    ojdbc6.jar

    11.1.0.7.0-Production

    db2jcc.jar

    db2jcc_license_cu.jar

    db2jcc4.jar

    3.50.152

    sqljdbc4.jar

    2.0.1803.100


    Note:

    A patch would be required for AIX, which would be available in tools/solutions as a zip file that can be dropped on the server.
  5. Uninstall Oracle Enterprise Repository 10.3.

  6. Run the Oracle Enterprise Repository 11g product installer.

    Note:

    Run the database configuration assistant at the end of the Oracle Enterprise Repository installer process.

    For more information about running the product installer, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Repository.

  7. Restore the Oracle Enterprise Repository backup files from the previous Oracle Enterprise Repository deployment to the newly installed Oracle Enterprise Repository 11g version, including:

    • The Oracle Enterprise Repository property files

      If you are using LDAP, then confirm that the Enable LDAP Login option is set to True and verify the LDAP Configuration settings. If you are using OracleApplication Server Single Sign-On (OracleAS Single Sign-On), then confirm that the Enable Advanced Container Login option is set to True and verify the Advanced Container Configuration settings. If your LDAP or OracleAS Single Sign-On configurations are not set correctly, then you will not be able to authenticate with the Oracle Enterprise Repository application.

      The property value for the LDAP authentication feature is:

      enterprise.authentication.ldap.enabled=true
      

      For Container Managed Authentication:

      enterprise.authentication.container.enabled=true
      enterprise.authentication.container.synchroles.enabled=true/false (depending on customer need)
      

      For OracleAS Single Sign-On:

      enterprise.authentication.advancedcontainer.enabled=true
      

      These properties should be enabled (as appropriate) and saved within the oer/WEB-INF/classes/enterprise.properties file.

    • Any custom files, such as custom home pages, images, XSLT templates, upload files, and any other customer-related files.

    Note:

  8. Start your application server.

  9. Verify the application deployment using Oracle Enterprise Repository diagnostics. For more information about enabling the Oracle Enterprise Repository diagnostics tools, see Section 2.6.3, "Enable the Oracle Enterprise Repository Diagnostics Tool".

Note:

No database operations are required for this upgrade.

1.1.2 Tomcat Application Upgrade

Note:

Tomcat is no longer supported in Oracle Enterprise Repository 11g Release 1 (11.1.1.4.0). You may upgrade on Tomcat at your own risk. It is suggested that you move to a supported Application Server as soon as reasonible. For a complete list of supported servers, see http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

These instructions enable you to upgrade from Oracle Enterprise Repository 10.3 to Oracle Enterprise Repository 11g on Tomcat using the Oracle Products installation program.

This section contains the following topics:

1.1.2.1 Prerequisites

To upgrade from ALER 3.x or Oracle Enterprise Repository 10.3 to Oracle Enterprise Repository 11g on Tomcat, you must ensure you have the following prerequisites:

  • Refer to the password encryption requirements section before performing upgrade steps. For more information, see Section 2.6.4, "Creating Encrypted Passwords".

  • Refer to the Supported Configurations list for the most recent information regarding your application server version.

  • Ensure that the application server is stopped.

  • If the installed application server version is no longer supported by Oracle Enterprise Repository, or the application server has been upgraded to a newer version, then perform the application upgrade instructions for the application server side.

  • The directory where Tomcat is installed on your system is referenced in these instructions as CATALINA_HOME.

  • The web application context that is being upgraded is referenced in these instructions as CATALINA_HOME/webapps/oer.

  • The web content context that is being upgraded is referenced in these instructions as CATALINA_HOME/webapps/oer-web.

  • If BPM is in use, then ensure that you backup the BPM Database.

  • Backup the existing Oracle Enterprise Repository database

1.1.2.2 Create an Oracle Enterprise Repository Temp Directory

On the Tomcat server, create a directory named oer_temp. This directory contains the backup copies of the current Oracle Enterprise Repository application. This also serves as a temporary location for properties files, JDBC drivers, and any customized Oracle Enterprise Repository items (home.jsp for example) that are required for the new application.

1.1.2.3 Back Up the Current Oracle Enterprise Repository Webapps

Navigate to the Tomcat installation location CATALINA_HOME/webapps and copy the existing oer and oer-web application directories into the oer_temp directory.

1.1.2.4 Uninstall AquaLogic Enterprise Repository 3.x or Oracle Enterprise Repository 10.3

Use the Oracle Enterprise Repository 10.3 Installer to remove all components of the previous release. For more information, see "Uninstalling the Software" in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Repository.

1.1.2.5 Run the Oracle Products Installation Program

To run the Oracle Products Installation program, perform the following steps:

  1. When prompted for the Tomcat (Catalina) Home directory, supply the directory where Tomcat has been installed.

  2. When prompted for the Repository application name, you can use the same application name that the previous deployment had used.

  3. When prompted for the Port number, use the same port number that the previous deployment had used.

  4. If you encounter a "One or more installation directories are not empty. Proceed with installation?" message, then select YES. This is applicable only when re-installing the same version.

The installer overwrites the existing deployment with the new files, thus preserving any additional custom files (such as an upload repository directory, custom home pages.). However, if you select No, then the exisiting deployment is saved to a new context path and the application content is stored in a new directory.

1.1.2.6 Post-Installation Instructions

After the Oracle Enterprise Repository installation is completed, and you have selected to use the Generic Application Server option, then you are left with a $MIDDLEWARE_HOME/repository111/generic directory.You will find the EAR file containing the Oracle Enterprise Repository application within this directory. This file and the contained WAR files have to be unzipped into the CATALINA_HOME/webapps directory then renamed to match the previous ALER/OER context name.

1.1.2.7 Restore the Oracle Enterprise Repository Back Up Files

To restore the Oracle Enterprise Repository backup files from Tomcat to your Oracle Enterprise Repository 11g deployment, perform the following steps:

  1. Navigate to the oer_temp directory.

  2. Edit the oer_temp/oer/WEB-INF/classes/enterprise.properties file by adding the following properties to the end of the file:

    enterprise.authentication.ldap.enabled=true
    enterprise.authentication.container.enabled=true
    enterprise.authentication.advancedcontainer.enabled=true
    
  3. Copy the oer_temp/oer/WEB-INF/classes/*.xml files to the OER_DEPLOYMENT_DIRECTORY/oer/WEB-INF/classes directory. This action overwrites the XML files that are a part of the new install.

  4. Copy the oer_temp/oer/WEB-INF/classes/*.properties files to the OER_DEPLOYMENT_DIRECTORY/oer/WEB-INF/classes directory. This action overwrites the properties files that are a part of the new install.

  5. Copy the supported JDBC Driver jar files to the OER_DEPLOYMENT_DIRECTORY/oer/WEB-INF/lib directory.

  6. Copy the oer_temp/oer/custom/home.jsp (and/or all of the custom home pages) to the OER_DEPLOYMENT_DIRECTORY/oer/custom directory. This overwrites the existing home.jsp file that is part of the new install. In addition, copy any custom images that were included in the custom home page(s) to the appropriate directory.

  7. If you are using any custom Type icons, then copy the files from the oer_temp/oer-web/images/tree/enterprise/asset directory to the OER_DEPLOYMENT_DIRECTORY/oer-web/images/tree/enterprise/assets directory.

  8. If custom reports were created, then see Section 2.1, "Migrating Custom Reports".

  9. Copy/Move the Upload Repository directory (normally found in oer_temp/oer/custom/upload) into the new OER_DEPLOYMENT_DIR/oer/custom installation directory.

1.1.2.8 Start Application Server

If you are using LDAP, then confirm that the Enable LDAP Login option is set to True and verify the LDAP Configuration settings. If you are using OracleAS Single Sign-On, then confirm that the Enable Advanced Container Login option is set to True and verify the Advanced Container Configuration settings. If your LDAP or OracleAS Single Sign-On configurations are not set correctly, then you will not be able to authenticate with the Oracle Enterprise Repository application.

  1. Navigate to the application server's JSP cache directory and delete the cache for the ALER/Oracle Enterprise Repository application.

  2. Start the generic application server.

Note:

For more information about performing encryption for passwords, see Section 2.6.4, "Creating Encrypted Passwords".

1.1.2.9 Test the Application

Oracle Enterprise Repository is now deployed. It is recommended that you test the installation using the Oracle Enterprise Repository Diagnostics page and the recommended tests are as follows:

  1. On the Oracle Enterprise Repository Diagnostics page

    • Product Version Information

    • Test Required Libraries

    • Test Database

  2. If you are unable to access the Oracle Enterprise Repository login page or application, or if you see an error message of some kind, it may be possible that the db.password property in the database.properties file was not encrypted. Check the cmee.log file for any messages that explains this behaviour.

For more information about enabling the Oracle Enterprise Repository diagnostics tools, see Section 2.6.3, "Enable the Oracle Enterprise Repository Diagnostics Tool".

1.1.3 WebLogic Server Application Upgrade

These instructions enable you to upgrade from ALER 3.x to Oracle Enterprise Repository 10.3 on WebLogic Server using the Oracle Enterprise Repository 11g Release 1 (11.1.1.4.0) installation program.

This section contains the following topics:

1.1.3.1 Prerequisites

To upgrade from ALER 3.x or Oracle Enterprise Repository 10.3 to Oracle Enterprise Repository 11g on WebLogic Server, you must ensure you have the following prerequisites:

  • Oracle Enterprise Repository 11g requires WebLogic Server 11g. If the currently installed Oracle Enterprise Repository application is not running on the required version, then upgrade the application server or install the supported version of WebLogic Server into a separate Oracle Home directory.

  • It is assumed that the Oracle Enterprise Repository domain is installed within the default location of BEA_HOME/user_projects/domains/applications/<domain_name>/applications/oer_XXX/oer_app. If the Oracle Enterprise Repository domain is installed in a different location, then make the appropriate adjustments to these instructions.

  • Refer to the password encryption requirements section before performing upgrade steps. For more information, see Section 2.6.4, "Creating Encrypted Passwords".

  • Stop the WebLogic server before performing these steps.

  • If BPM is in use, then ensure that you backup the BPM Database.

  • Backup the existing Oracle Enterprise Repository database

1.1.3.2 Create Oracle Enterprise Repository Temp Directory

To create an Oracle Enterprise Repository temp directory:

On WebLogic Server, create a directory named oer_temp. This directory is used to backup the current Oracle Enterprise Repository application. This location is used as a temporary location for properties files, JDBC drivers, and any customized Oracle Enterprise Repository items (home.jsp, for example) that are necessary for the new application.

1.1.3.3 Back Up the Current ALER Webapps

Back-up the current Oracle Enterprise Repository domain by navigating to the BEA_HOME/user_projects/domains/applications/<domain_name>/applications/oer_XXX/oer_app directory and copy the oer-app and oer-web directories to the oer_temp directory.

Note:

The Oracle Product installer provides an application template to create a or extend an existing domain with the Oracle Enterprise Repository 11g application. Therefore, the existing domain is no longer used.

1.1.3.4 Remove Current Oracle Enterprise Repository Installation Files

Caution:

Perform this step only after completing backup of the directory, as described in Section 1.1.3.3, "Back Up the Current ALER Webapps".

If you wish to use the same domain name, then rename /remove the current Oracle Enterprise Repository domain. For example, BEA_HOME/user_projects/domains/<domain_name> to BEA_HOME/user_projects/domains/old_<domain_name>.

1.1.3.5 Uninstall ALER 3.x/Oracle Enterprise Repository 10.3

Use the ALER 3.x or Oracle Enterprise Repository 10.3 removal tool to remove all components of the previous release. For more information, see "Uninstalling the Software" in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Repository.

1.1.3.6 Run the Oracle Enterprise Repository Installation Program

To run the Oracle Enterprise Repository Installation program, perform the following steps:

  1. When prompted for the Middleware Home directory, supply the directory where the WebLogic Server 11g is installed.

  2. When prompted for the Fully qualified server name, supply the fully qualified host name of the server that this domain is being installed on.

  3. When prompted for the Repository application name, you can use the same application name that the previous deployment had used.

  4. When prompted for the Port number, you can use the same port number that the previous deployment had used.

1.1.3.6.1 Oracle Enterprise Repository Database Installation

When the installer prompts for database installation, choose the option to NOT configure the database.

1.1.3.7 Post-Installation Instructions

The Oracle Enterprise Repository application is now distributed as a bundled WLS application domain template. To deploy the Oracle Enterprise Repository application template, perform the following tasks:

  1. Start the WLS Domain Configuration Wizard using BEA_HOME/wlserver_10.3/common/bin/config.sh or .cmd

  2. Create a new WebLogic Domain, and then click Next.

  3. Choose Generate a domain configured automatically to support the following products. Check Oracle Enterprise Repository 11.1.1.x.x, and then click Next.

  4. Enter an appropriate domain name. Use the default locations for the domain and application locations unless you are experienced with these types of definitions. Click Next.

  5. Supply the Appropriate user credentials required to start/stop the domain processes, and then click Next.

  6. Select the appropriate JDK and production mode (defaults to JRockit JDK in production mode) for this domain, and then click Next.

  7. There is no need to modify the optional configuration elements if Oracle Enterprise Repository is a standalone domain (not extending an existing domain - recommended). Click Next.

  8. Review the configuration information for this new Oracle Enterprise Repository domain, and then click the Create button.

The Oracle Enterprise Repository application is deployed within the newly created domain in the directories specified in step 4. This directory path is referenced later to restore existing property and JDBC Driver files.

1.1.3.8 Restore the Oracle Enterprise Repository Back Up Files

To restore the Oracle Enterprise Repository backup files from WebLogic to your Oracle Enterprise Repository 11g deployment, perform the following steps:

  1. Navigate to the oer_temp directory.

  2. Edit the oer_temp/oer/WEB-INF/classes/enterprise.properties file by adding the following properties to the end of the file:

    enterprise.authentication.ldap.enabled=true
    enterprise.authentication.container.enabled=true
    enterprise.authentication.advancedcontainer.enabled=true
    
  3. Copy the oer_temp/oer-app/WEB-INF/classes/*.xml files to the BEA_HOME/user_projects/applications/<domain>/oer_11.1.1.x.x/applications/oer-app/WEB-INF/classes directory. This action overwrites the XML files that are a part of the new install.

  4. Copy the oer_temp/oer-app/WEB-INF/classes/*.properties files to the BEA_HOME/user_projects/applications/<domain>/oer_11.1.1.x.x/applications/oer-app/WEB-INF/classes directory. This action overwrites the .properties files that are a part of the new install. If a .properties file exists in the new deployment, and does not exist in the backup, then this may indicate a "Move Setting to Database" operation in the past. These .properties files should be deleted from the upgraded instance. For more information about moving settings to database, see Section 2.3.2, "Move Settings to Database".

  5. Copy the oer_temp/oer/custom/home.jsp (and/or all of the custom home pages) to the BEA_HOME/user_projects/applications/<domain>/oer_11.1.1.x.x/applications/oer-app/custom directory. This overwrites the existing home.jsp file that is part of the new install. In addition, copy any custom images that were included in the custom home page(s) to the appropriate directory.

  6. If using any custom Type icons, copy the files from the oer_temp/oer-web/images/tree/enterprise/asset directory to the BEA_HOME/user_projects/applications/<domain>/oer_11.1.1.x.x/applications/oer-web/images/tree/enterprise/asset directory.

  7. If custom reports were created, see the Section 2.1, "Migrating Custom Reports" section.

  8. Copy/Move the Upload Repository directory (normally found in oer_temp/oer/custom/upload) into the new BEA_HOME/user_projects/applications/<domain>/oer_11.1.1.x.x/applications/oer-app/custom/upload installation directory.

1.1.3.9 Start WebLogic Server

If you are using LDAP, then confirm that the Enable LDAP Login option is set to True and verify the LDAP Configuration settings. If you are using OracleAS Single Sign-On, then confirm that the Enable Advanced Container Login option is set to True and verify the Advanced Container Configuration settings. If your LDAP or OracleAS Single Sign-On configurations are not set correctly, then you will not be able to authenticate with the Oracle Enterprise Repository application.

  1. Start the WebLogic Administration Server (required to be running before the Oracle Enterprise Repository managed server can be started):

    BEA_HOME/user_projects/domains/<domain>/startWebLogic.sh or *.cmd

  2. Start the Oracle Enterprise Repository Managed Server:

    BEA_HOME/user_projects/domains/<domain>/bin/startManagedWebLogic.sh oer_server1 http://localhost:7001

1.1.3.10 Test the Application

Oracle Enterprise Repository 11g is now deployed. It is recommended that you test the installation using the Oracle Enterprise Repository Diagnostics page and the recommended tests are:

  1. On the Oracle Enterprise Repository Diagnostics page

    • Product Version Information

    • Test Required Libraries

    • Test Database

  2. Update the following Oracle Enterprise Repository properties that reference the application server file system paths:

    cmee.asset.xml.paths.export-destination

    cmee.asset.xml.paths.xsl-source

    cmee.asset.xml.paths.out-destination

    cmee.server.paths.upload

    cmee.extframework.export.tempfile

    Additional properties that are effected by the deployment of Oracle Enterprise Repository are:

    cmee.server.paths.upload-registrar

    The application server based FTP, HTTP, HTTPS and SMB/CIFS artifact store definitions are also effected by the change in paths based on the WLS application template configuration process.

    Ensure you take a special note of these types of artifact stores and update the configurations appropriately.

  3. If you are unable to access the Oracle Enterprise Repository login page or application, or if you see an error message of some kind, it may be possible that the db.password property in the database.properties file was not encrypted. Check the cmee.log file for any messages that explains this behaviour.

For more information about enabling the Oracle Enterprise Repository diagnostics tools, see Section 2.6.3, "Enable the Oracle Enterprise Repository Diagnostics Tool".

1.1.4 WebSphere Application Upgrade

These instructions enable you to upgrade from Oracle Enterprise Repository 10.3 to Oracle Enterprise Repository 11g on WebSphere using the Oracle Products installation program. These instructions assume use of the Application Server profile type. For other profile types, modify the configuration according to your environment's requirements.

This section contains the following topics:

1.1.4.1 Prerequisites

To upgrade from Oracle Enterprise Repository 10.3 to Oracle Enterprise Repository 11g on WebSphere, you must ensure you have the following prerequisites:

  • When using WebSphere 6.1.0.5 with Oracle 11g database server, ensure that you use the ojdbc5.jar JDBC driver for Oracle Database servers to maintain compatibility with the IBM WebSphere 1.5.x JDK.

  • Oracle Enterprise Repository requires WebSphere version 6.1.0.5. If the currently installed Oracle Enterprise Repository application is not running on the required version, then upgrade the application server as appropriate.

  • The current deployment directory containing the Oracle Enterprise Repository application is referred to as oer_current (this directory normally is located in the following directory:

    WAS_HOME/AppServer/profiles/AppSrv01/installedApps/localhostNode01Cell/installedApps/oer.ear.

  • Once the upgrade process is complete, the Oracle Enterprise Repository property files, XML files, and JDBC driver files are located within a new BEA_HOME/repositoryXXX/websphere directory.

  • Backup the existing ALER database

1.1.4.2 Create Oracle Enterprise Repository Temp Directory

On the WebSphere server, create a directory named oer_temp. This directory contains backups of the current Oracle Enterprise Repository application properties files, JDBC drivers, and any customized Oracle Enterprise Repository items (home.jsp for example) that are necessary for the new application.

1.1.4.3 Back Up the Current Oracle Enterprise Repository Webapps

To back up the current Oracle Enterprise Repository webapps, perform the following steps:

  1. Copy the contents of the current OER_HOME shared library directory contents to the oer_temp directory. The oer_temp directory should then contain all of the original Oracle Enterprise Repository properties files, XML files, and your current JDBC driver JAR files.

  2. Edit the oer_temp/oer/WEB-INF/classes/enterprise.properties file by adding the following properties to the end of the file:

    enterprise.authentication.ldap.enabled=true
    enterprise.authentication.container.enabled=true
    enterprise.authentication.advancedcontainer.enabled=true
    
  3. Refer to the password encryption requirements section before performing upgrade steps. For more information, see Section 2.6.4, "Creating Encrypted Passwords".

  4. If you have a customized Oracle Enterprise Repository home page, navigate to the oer_current/oer-app.war/custom directory and copy the home.jsp file to the oer_temp directory. If you have used the Role or Department based home pages, then copy those files from the directory that is indicated within the oer_current/oer-app.war/WEB-INF/classes/homepages.xml file.

  5. Copy any custom images that are used in the custom home page file(s) to the oer_temp directory.

  6. If you have any custom Asset Type icons, navigate to the oer_current/oer-web.war/images/tree/enterprise/asset directory and copy the images to the oer_temp directory.

  7. Optionally, copy all XSLT templates from the PDF Printing web-application to the oer_temp directory. This web application is bundled directly into the core of the Oracle Enterprise Repository product.

  8. Copy any additional files or directories that were included or modified from the base Oracle Enterprise Repository installation into the oer_temp directory.

1.1.4.4 Remove Current ALER/OER Installation Files

To remove the current Oracle Enterprise Repository installation files, perform the following steps:

  1. Start the WebSphere 6.1.0.5 Administrative Console.

  2. Expand the Applications -> Enterprise Applications folder and select the ALER/OER option.

  3. Click Stop.

  4. Select the ALER/OER option.

  5. Click Uninstall.

  6. Select the ALER/OER option.

  7. Click Remove.

  8. Repeat the above steps to remove the PDF Printing web-application (if present). This feature has been bundled within the Oracle Enterprise Repository base application.

  9. Save the changes to the Master Configuration when prompted.

  10. Stop WebSphere Server.

  11. Associate Shared Libraries with Oracle Enterprise Repository 11g, as follows:

    1. Expand the Applications, Enterprise Applications folder and click the Oracle Enterprise Repository 11g installation.

    2. Choose the Shared Library References link.

    3. Select the oer-app.war application.

    4. Click the Reference Shared Libraries button.

    5. Select the appropriate shared library definitions.

    6. Click the Right Arrow button to move the definitions to the selected box on the right.

    7. Click OK to save the selected references.

    Edit the path of the existing Oracle Enterprise Repository shared library containing the property files. The new path for this library is BEA_HOME/repository111/websphere.

    The existing property files are copied into this location once the Oracle Enterprise Repository 11g installation is completed.

Note:

For more information about configuring workflows, see Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository.

1.1.4.5 Uninstall Oracle Enterprise Repository 10.3

Use the Oracle Enterprise Repository 10.3 Installer to remove all components of the previous release. For more information, see "Uninstalling the Software" in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Repository.

1.1.4.6 Run the Oracle Enterprise Repository Installation Program

To run the Oracle Products Installation program, perform the following steps:

  1. When prompted for the Repository application name, use the same application name that the previous deployment had used.

  2. When prompted for the Port number, use the same port number that the previous deployment had used.

    The Oracle Products installer generates a deployable EAR file, thus allowing you to quickly and easily install the updated version of the application directly from the application server's file system. It also creates and deploys the Oracle Enterprise Repository Workflow application components appropriately.

1.1.4.7 Install New Application Files

To install new application files in Oracle Enterprise Repository, perform the following steps:

  1. Start WebSphere Server.

  2. Start the WebSphere Administrative Console.

  3. Expand the Applications -> Enterprise Applications folder and click Install.

  4. Choose the option to select a Remote Filesystem (this option is relative to the application server), browse to the BEA_HOME/repository111/websphere directory, and select the oer.ear file.

  5. Select the Prompt me only when additional information is required option and click Next to continue.

  6. On the Select Installation Options page, click Next to continue after making the appropriate changes.

  7. On the Map modules to servers page, click Next to continue after making the appropriate changes.

  8. On the Map virtual hosts for Web modules page, click Next after making the appropriate changes.

  9. On the Deployment summary page, click Finish to deploy the EAR file.

    Note:

    This process may take several minutes.
  10. After the installation is finished, the Application installed successfully message is displayed.

  11. Click Save to Master Configuration when prompted.

  12. Stop WebSphere Server.

1.1.4.8 Restore the Oracle Enterprise Repository Back Up Files

These steps modify files deployed by the newly installed version of Oracle Enterprise Repository with files from the backup and the previously installed version.

  1. If you have a customized Oracle Enterprise Repository home page(s), use the Update feature of WebSphere to replace the deployed custom/home.jsp file with the customized version of home.jsp in the backup.

  2. Copy any custom images that may be part of the home.jsp file to the appropriate directory.

  3. If you use custom asset icon images, then use the Update feature.

  4. If custom reports were created, then see the Section 2.1, "Migrating Custom Reports" section.

  5. If additional files were included or modified in the original Oracle Enterprise Repository install, consult Oracle Technical Support for assistance with inclusion of these additions into Oracle Enterprise Repository 10.3.

  6. Copy all previous property files from the oer_temp to the BEA_HOME/repository111/websphere directory.

  7. Copy all previous XML files from the oer_temp to the BEA_HOME/repository111/websphere directory.

  8. Copy the currently supported JDBC Driver files into the BEA_HOME/repository111/websphere directory.

1.1.4.9 Start WebSphere

If you are using LDAP, then confirm that the Enable LDAP Login option is set to True and verify the LDAP Configuration settings. If you are using OracleAS Single Sign-On, then confirm that the Enable Advanced Container Login option is set to True and verify the Advanced Container Configuration settings. If your LDAP or OracleAS Single Sign-On configurations are not set correctly, then you will not be able to authenticate with the Oracle Enterprise Repository application.

  1. Navigate to the WebSphere_HOME/AppServer/temp/ directory and delete the cache for the Oracle Enterprise Repository application.

  2. Restart WebSphere.

1.1.4.10 Test the Application

Oracle Enterprise Repository is now deployed. It is recommended that you test the installation using the Oracle Enterprise Repository Diagnostics page and the recommended tests are as follows:

  1. On the Oracle Enterprise Repository Diagnostics page

    • Product Version Information

    • Test Required Libraries

    • Test Database

  2. Update the following Oracle Enterprise Repository properties that reference the application server file system paths:

    cmee.asset.xml.paths.export-destination

    cmee.asset.xml.paths.xsl-source

    cmee.asset.xml.paths.out-destination

    cmee.server.paths.upload

    cmee.extframework.export.tempfile

    Additional properties that are effected by the deployment of Oracle Enterprise Repository are:

    cmee.server.paths.upload-registrar

    The application server based FTP, HTTP, HTTPS and SMB/CIFS artifact store definitions are also effected by the change in paths based on the WLS application template configuration process.

    Ensure you take a special note of these types of artifact stores and update the configurations appropriately.

  3. If you are unable to access the Oracle Enterprise Repository login page or application, or if you see an error message of some kind, it may be possible that the db.password property in the database.properties file was not encrypted. Check the cmee.log file for any messages that explains this behaviour.

1.1.5 Migrating Your Custom Assets

Note:

The following instructions apply to generic services that are manually created in Oracle Enterprise Repository 10g or ALER 3.x, with standard artifacts specified by WSDL. These instructions do not pertain to services automatically harvested from other sources through Oracle Enterprise Repository integrations.

You can migrate your custom assets using any of the following methods:

Migrating Customized Asset Types

Oracle Enterprise Repository comes with numerous out-of-the-box asset types that can be modified and extended, or used to create new custom asset types. This section describes how these asset types are migrated to Oracle Enterprise Repository 11g.

  • New Asset Types - If you created your own custom asset types, then these are left intact when upgrading to 11g.

  • Asset Type Extensions - If you extended standard out-of the box asset types, then these are left intact when upgrading to 11g.

  • Oracle Enterprise Repository 11g Solution Pack - The Oracle Enterprise Repository 11g Harvester uses an updated Solution pack. The Solution pack modifies some of the asset types in Oracle Enterprise Repository. All asset type modifications are additive and all new elements are added to the bottom of the tabs in the Asset Editor.

Migrating Manually Created Services Instances

In Oracle Enterprise Repository 11g, assets are harvested throughout the lifecycle. Once a run time implementation has been harvested into Oracle Enterprise Repository, the repository's workflow process the implementation according to the governance rules and practices established by the organization. As the implementation moves throughout the lifecycle, from testing, through staging, and into production, the enterprise repository promotes the services and endpoints to a service registry in each lifecycle environment.

Services harvested at design-time provide early visibility into service production, but these services cannot be reused through JDeveloper until they have been deployed. Similarly, services without a concrete endpoint and hosted WSDL cannot be promoted to Oracle Service Registry.

If you want to consume Oracle Enterprise Repository assets from JDeveloper and/or move assets from Oracle Enterprise Repository to Oracle Service Registry so that run time tooling can automatically detect changes, then the following process is recommended:

  • Asset Type Required

    For instances of services to be migrated properly to the new 11g model, the Oracle Enterprise Repository 10g R3 asset type that you must use is <Service>. In Oracle Enterprise Repository 10g, the <Service> type is available both in Base Data and the Harvester Solution Pack. In ALER 3.x, it is available in Base Data and the Introspection Solution Pack. To ensure that you have the right Type, the UUID is:

    <Service> af6ee48a-4c10-11dc-ac31-7de68f5ca4a1

    While it is possible (with more advanced migration tool configuration) to migrate assets of any asset type or other types called "Service", then it is recommended that you use the original Service asset type from Oracle with the proper UUID. This ensures that you have the right asset Type in 11g, so that you can take advantage of Oracle Enterprise Repository functionality that is dependent on the Service asset Type.

  • Remote Artifact Hosting Required

    The migration tool runs the Harvester on any valid WSDL that is referenced remotely on HTTP, HTTPS, or FTP sites by the Service assets being migrated. The references to XSDs found in WSDL must also be valid URIs, and hosted remotely from the system on which the migration tool is being run.

    Only HTTP/HTTPS and FTP are supported for remote hosting of these artifacts. Services with artifacts hosted locally or elsewhere does not migrate with good results.

    There are no specific instructions on setting up hosted artifacts, as long as that the remote file store can make the artifacts accessible through a valid URI. You should follow instructions for the product that you are using for the remote file store.

  • Concrete WSDL Preferred

    If concrete WSDL is attached to the Service, then interface and endpoint assets are created on migration. If abstract WSDL is attached, then interface assets are created without endpoint assets. It is highly recommended that remotely hosted artifacts include concrete WSDL with endpoints for lifecycle use cases. For example, if endpoints are not present, services and artifacts are visible in the repository, but services are neither consumable in Oracle SOA Suite/JDeveloper, nor do they publish to the Service Registry until they are re-harvested with endpoints.

  • Service Reference to Artifacts

    The FileInfo element on the Service asset is the correct place to manually add the URI artifact reference to the remotely hosted service WSDL.

    There is no need to add multiple FileInfo entries for each service. Only the top-level WSDL is required to be referenced in FileInfo, because the Harvester used by the migration tool automatically parses WSDL and looks for import/Ref to get all the other referenced artifacts such as other WSDL/XSDs.

    Note:

    If you have ALER and have not yet upgraded to Oracle Enterprise Repository, then the URI references to the remotely hosted WSDL artifacts (per instructions above) should be inserted in the same place that the artifacts would have been referenced after ALER WSDL introspection.

    ALER WSDL introspection is a legacy feature and no longer available in Oracle Enterprise Repository. For best results in an upgrade, any previously introspected artifact references should be deleted from the Service before the Oracle Enterprise Repository 11g upgrade, with references to remotely hosted artifacts manually inserted in their place. If this procedure is not followed, then the previously introspected WSDL is still available from Oracle Enterprise Repository, but certain important use cases are not supported, for example services are not consumable in Oracle SOA Suite/JDeveloper or published to the Service Registry until the concrete WSDL is re-harvested in Oracle Enterprise Repository 11g.

1.2 Upgrade Oracle Enterprise Repository Workflows

It is highly recommended that the currently delivered workflows be deployed instead of using the versions delivered in a previous release. The previous version of workflows are not supported with Oracle Enterprise Repository 11g.

The Oracle Enterprise Repository version 11g contains new and updated workflows that require the use of Oracle BPM Enterprise version 10.3.1. The earlier versions of the Oracle Enterprise Repository had been delivered with a run time edition of OBPM 10g R3. The currently delivered version of the workflows are incompatible with the OBPM 10g R3 engine and, therefore, requires a new installation of OBPM Enterprise version 10.3.1 or upgrading existing OBPM installation to version 10.3.1 using BPM or upgrading existing OBPM installation to version 10.3.1 using Standard BPM upgrade procedure.

1.2.1 Upgrading Existing Oracle Enterprise Repository Workflows

You can upgrade existing Oracle Enterprise Repository workflows and these workflows contain all of the Oracle Enterprise Repository workflow processes in addition to new processes surrounding UDDI operations. If customized workflows have been deployed for use with Oracle Enterprise Repository, then it is recommended that these customizations be upgraded using OBPM 10.3 studio.

If is recommended that you regenerate workflow.xml after Oracle Enterprise Repository 11g is deployed. This ensures that generated workflow.xml contains correct metadata, for example, categorizations, users. Once generated, it should be updated for correct registrar credentials and correct Oracle Enterprise Repository URL. Lastly, it should be updated for any custom event wiring, which is a manual step. It is also recommended that you thoroughly test it before deployment.

For information about installation of the workflows within OBPM 10.3, see Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository.

Note:

The deployment of custom or customized workflows is outside the scope of this document.