This release of UIM supports the direct upgrade path from release 7.4.1 and above to release 8.0.0.

After the upgrade is complete, cartridges must be migrated to the new release of UIM using the Design Studio Cartridge Migration Tool. It is possible that migrated cartridges contain minor compilation errors that prevent them from building and deploying. If a cartridge fails to build, open it in Design Studio and correct any compilation errors.

Pre-upgrade tasks must be performed while the UIM WebLogic Server is inactive.

These pre-upgrade tasks apply if your old version of UIM is version 7.4.1 and above. Perform the following pre-upgrade tasks:

1. Back up the UIM and MDS databases. See "Unified Inventory Management System Administration Overview" in UIM System Administrator's Guide for more information.

2. Back up the UIM WebLogic Server domain. See the WebLogic Server documentation for more information.

   Note:

   Verify that the file/folder being backed up meets the file size or pathname length requirements for the backup utility being used. For example, the maximum pathname length for the tar application is 256 characters.

3. If the old version of your UIM user interface was customized, back up the changes.

   Caution:

   UIM does not maintain backward compatibility for the user interface. If the old version of your UIM user interface was customized and you do not back up the changes, you will lose them. (You will re-apply the changes when performing the post-upgrade tasks.)

4. Before upgrading the domain, perform a backup by copying the directories that contain Fusion Middleware files. You can do this by archiving and compressing the source Oracle home and the Administration Server domain. Do the following:

   1. Shut down all processes in the Oracle home. For example, shut down the Managed Servers, the Administration Server, and any system components.

   2. Back up the Oracle home (ORACLE_HOME) on all hosts. For example:

      (UNIX) tar -cf oracle_home_backup_062015.tar ORACLE_HOME/*
      (Windows) jar cMf oracle_home_backup_0462015.jar ORACLE_HOME\*
      

   3. Back up the Administration Server domain separately. This backs up Java components and any system components in the domain.

      (UNIX) tar -cf domain_home_backup_062015.tar DOMAIN_HOME/*(Windows) jar cMf domain_home_backup_062015.jar DOMAIN_HOME\*
      

5. Start the WebLogic Administration Server and open the WebLogic Console.

6. On the left side Domain Structure Panel, select the services and then go to Data Sources.

7. Locate all WLSSchemaDataSource. In the connection pool for each WLSSchemaDataSource, change the user name from <PREFIX>_WLS_RUNTIME to <PREFIX>_WLS and save your changes.

8. If Mapviewer is installed in your existing domain: then follow the below steps:

   1. Delete the Mapviewer template from domain-info.xml file in $WLS_Domain/init-info location:

      < xtension-template-ref name=”Oracle MapViewer” version=”12.2.1.4.0” location=”$INFRA_ORACLE_HOME$/oracle_common/common/templates/wls/oracle.mapviewer_template.jar” symbol=”oracle.mapviewer_12.2.1.4.0/oracle_common_ORACLE_HOME”/>
      <install-comp-ref name=”oracle.mapviewer” version=”12.2.1.4.0” symbol=”oracle.mapviewer_12.2.1.4.0/oracle_common_ORACLE_HOME” product_home=”$INFRA_ORACLE_HOME$/oracle_common”/>
      

   2. Undeploy Mapviewer components from WebLogic console:

      <app-deployment>
          <name>mapviewer</name>
          <target>cl1</target>
          <module-type>ear</module-type>
          <source-path>/scratch/Oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.mapviewer/mapviewer.ear</source-path>
          <deployment-order>500</deployment-order>
          <security-dd-model>DDOnly</security-dd-model>
          <staging-mode>nostage</staging-mode>
        </app-deployment>
      	  <app-deployment>
          <name>mapviewer-1</name>
          <target>cl1</target>
          <module-type>ear</module-type>
          <source-path>/scratch/Oracle/Middleware/mapviewer.ear</source-path>
          <security-dd-model>DDOnly</security-dd-model>
          <staging-mode>nostage</staging-mode>
          <plan-staging-mode xsi:nil=”true”></plan-staging-mode>
          <cache-in-app-directory>false</cache-in-app-directory>
        </app-deployment>
      

9. Stop the UIM domain servers.

10. Run the readiness check before proceeding:

    1. Navigate to MW_HOME/oracle_common/upgrade/bin/.

       Where MW_HOME is the directory in which Oracle Fusion Middleware 14.1.2 is installed. This directory contains the Upgrade Assistant (UA) tool, which you use to upgrade the schema.

    2. Launch the UA tool with readiness flag:

       ./ua -readiness

       The Welcome screen appears.

    3. Click Next.

       The Upgrade Type screen appears.

    4. Select Domain based, provide the domain directory, and click Next.

    5. Verify Database Type and Connect String details that are autopopulated.

    6. In DBA User Name, enter the database administrator user name.

    7. In DBA Password, enter the password for the administrator user.

    8. Click Connect.

       If the provided details are valid, you can proceed.

    9. In the Schema User Name list, the OPSS schema for the current WebLogic domain is autopopulated. As the order is not fixed, the schema can be different from OPSS such as UMS or STB. Ensure only the schema for the current domain is present.

       All details are autopopulated for the schemas.

    10. Verify the details and click Next.

    11. If the password is missing or the schema details are missing (<DOMAIN NAME>_ instead of <DOMAIN_NAME>_UMS), add the corresponding details and proceed.

        The Summary screen appears. The readiness check will begin.

    12. If everything is green, proceed with the upgrade.

11. Upgrade the UIM RCU Schemas:

    1. Navigate to MW_HOME/oracle_common/upgrade/bin/

       where MW_HOME is the directory in which Oracle Fusion Middleware 14.1.2 is installed.

    2. Launch the UA tool to upgrade the schema.

       ./ua

       The Welcome screen appears.

    3. Click Next.

       The Upgrade Type screen appears.

    4. Select Individually Selected Schemas, and click Next.

       The Available Components screen appears, which enables you to select components to upgrade. Select the components that are present in the WebLogic domain.

    5. Click Next.

       The Domain directory screen appears.

    6. Select the domain directory for upgrade, and click Next.

       The Prerequisites screen appears.

    7. Confirm that the database backup is complete by selecting the All affected servers are down, All affected data is backed up, Database version is certified by Oracle for Fusion Middleware upgrade, and Certification and system requirements have been met check boxes, and click Next.

       The OPSS Schema screen appears.

       Note:

       The schemas (IAU, STB, OPSS, WLS, and MDS) may appear in different sequence after step 7g.

    8. From the Database Type list, select the database type.

    9. In Connect String, enter the hostname:portnumber/SID string.

       Note:

       For a clustered environment, the hostname:portnumber/SID must specify the primary Oracle RAC node.

    10. In DBA User Name, enter the database administrator user name.

    11. In DBA Password, enter the password for the administrator user.

    12. Click Connect.

        If the provided details are valid, the Schema User Name and Schema Password fields become enabled.

    13. From the Schema User Name list, select the OPSS schema for the current WebLogic domain.

    14. In Schema Password, enter the database password, and click Next.

    15. Verify the details and click Next.

    16. If the password is missing or the schema details are missing (<DOMAIN NAME>_ instead of <DOMAIN_NAME>_UMS), add the corresponding details and proceed.

        The Summary screen appears. The readiness check will begin.

    17. Click Next.

        The Upgrade Summary screen appears.

    18. Verify the details of the services to be upgraded and click Upgrade.

        The Upgrading Components screen appears. You can monitor the progress of the upgrade from this screen.

    19. After the upgrade completes, click Next.

        The Upgrade Success screen appears.

    20. Verify that the upgrade was successful and click Close.

12. Reconfigure the WebLogic domains using the Fusion Middleware Reconfiguration Wizard, which you open using the following command:

    ./MW_Home/oracle_common/common/bin/reconfig.sh
    

    1. On the Select Domain screen, from the Existing Domain Location list, select the UIM domain that you want to upgrade and click Next.

       The Reconfiguration Setup Progress screen appears, displaying the progress of the reconfiguration setup process.

    2. Click Next.

       The Domain Mode and JDK screen appears.

       The domain mode cannot be changed during reconfiguration. It is inherited from the original domain.

    3. Select the JDK option and browse to the folder (JAVA_HOME) where the JDK is installed and click Next.

       Ensure that you have installed the correct version of the JDK. See "UIM Software Compatibility" in UIM Compatibility Matrix for more information.

       The Database Configuration Type screen appears.

    4. Select the RCU Data option, complete the required fields, and then click Get RCU Configuration, which retrieves the schema information.

       You select the RCU Data option to connect to the database to retrieve schema information for all schemas that are included in the domain.

    5. Click Next. If you are using RAC Database, select WLS Runtime Schema and Convert to RAC multi data source option. Then provide the details for RAC Database. Do the same for other schemas and proceed.

    6. Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.

       The Advanced Configuration screen appears.

    7. Select Administration Server and then select the other categories for which you want to perform advanced configuration and click Next.

       The Administration Server screen appears.

       For each category you select, the appropriate configuration screen appears that allows you to perform advanced configuration.

    8. Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.

    9. On the Deployments Targeting screen, under Targets, select the oracle.communications.inventory application and then click the left arrow, which moves the application to the Deployments section.

    10. On the Deployments Targeting screen, under Deployments, select Library, and then under Targets, select the server or cluster, and then click the right arrow, which moves all the libraries to the targeted server or cluster for deployment.

    11. Click Next.

        The Services Targeting screen appears.

    12. Under Services, select all the services, and then under Targets, select the server or cluster, and then click the right arrow, which moves the services to the targeted server or cluster for deployment.

    13. Click Next until the Configuration Summary screen appears.

    14. Review the detailed configuration settings of the domain and click Reconfig.

        The Reconfiguration Progress screen appears, which displays the progress of the reconfiguration process.

        After the reconfiguration process completes, the Reconfiguration Success screen appears.

    15. Click Finish.

        See Oracle Fusion Middleware documentation for more information.

13. Upgrade the WebLogic domain configurations by doing the following:

    1. Navigate to the MW_Home/oracle_common/upgrade/bin/ua directory.

       This directory contains the Fusion Middleware Upgrade Assistant 14.1.2, which you use to upgrade the WebLogic domain configurations.

    2. Launch the Fusion Middleware Upgrade Assistant.

       The Welcome screen appears.

    3. Click Next.

    4. Select All Configurations used by a domain, and in the Domain Directory field, select the WebLogic domain directory you want to upgrade, and then click Next.

       The Prerequisites screen appears.

    5. Confirm that the database backup is complete by selecting the All affected data is backed up, Database version is certified by Oracle for Fusion Middleware upgrade, and Certification and system requirements have been met check boxes, and click Next.

    6. Navigate through the different screens by clicking Next on each screen and specifying your settings as necessary.

    7. On the Upgrade Success screen, verify that the upgrade was successful and click Close.

       See Oracle Fusion Middleware documentation for more information.

14. Upgrade the Oracle Database software. See "Database Software Changes" for more information.

    See the Oracle Database documentation for information on upgrading the database software to a newer version.

15. Apply any required Oracle Database patches.

    See "UIM Software Compatibility" in UIM Compatibility Matrix for more information on the Oracle Database patches.

    See the Oracle Database documentation for information on applying patches to the database.

16. Upgrade the UIM database schema by performing the following steps:

    WARNING:

    Data can change when you upgrade the UIM database schema.

    1. Create two temporary directories, temp_dir and temp_dir_schema.

    2. Download the UIM software for your operating system from the Oracle software delivery website and save it to temp_dir.

    3. From the ZIP file, extract the ora_uim_dbtools.jar file into temp_dir_schema.

       The ora_uim_dbtools.jar file is located in the root of the downloaded ZIP file.

    4. In temp_dir_schema, open the ora_uim_dbtools.jar file and extract the contents into temp_dir_schema.

       Note:

       For dbtools to work, you must have both the ora_uim_dbtools.jar file itself, and its extracted contents, in the temp_dir_schema directory.

    5. Open the temp_dir_schema/config/databases.xml file in an editor, where will you see the following:

       <db:database name="SID">
           <db:driver>oracle.jdbc.driver.OracleDriver</db:driver>
           <db:connectionUrlString>
               jdbc:oracle:thin:@DBHostName:port:SID
           </db:connectionUrlString>  
           <db:schemaComparison fromSchema="UIM_701"
               fromFile="\\filepath\dist\scripts\create.sql" toSchema="UIM_710" 
               toFile="\\filepath\dist\scripts\create.sql">
           </db:schemaComparison>
       </db:database>
       

       Modify the <db:database> element name attribute value (SID in the above XML) to be the SID value of the database you are upgrading.

       Modify the <db:connectionUrlString> element value (DBHostName:port:SID in the above XML) to be the database you are upgrading.

       Note:

       For a clustered environment, the DBHostName:port:SID must specify the primary Oracle RAC node.

       For a pluggable database (PDB), specify <db:connectionUrlString> in the following format:

       jdbc:oracle:thin:@DBHostName:port/SID

    6. Grant the execute permission for the runDB.sh script.

    7. Run the DB upgrade with the following command:

       runDB.sh DBTOOLS_PATH JAVA_HOME upgrade
       

       where DBTOOLS_PATH is the directory location of the ora_uimdbtools.jar file, and where JAVA_HOME is the directory location of your Java installation (up to the jdk/bin directory).

       For example:

       ./runDB.sh /home/uimdev/download/dbupgrade/temp_dir_schema 
       /usr/jdk21.0.6_patch/bin upgrade
        

       where patch is the version of your JDK. You will be prompted to enter the database SID, and the UIM DB userid and password for the DB you want to migrate.

       You will also be prompted to enter upgrade to confirm that an upgrade is to be performed on the database.

       Note:

       The database contains tables that record if a script has been run against the database and if the script can be re-run. If the script has been previously run and it has been identified as Not re-runnable, the message Update has already run displays next to the script name in the DbVersionController.log file.

       The following is an example of the DbVersionController.log file:

       1/11/17 6:34:22 AM PST: Applying Framework Update: sqlfrmwrk - Success
       1/11/17 6:34:22 AM PST: Applying Framework Update: sqlfrmwrk1 - Success
       1/11/17 6:34:22 AM PST: Applying Framework Update: sqlfrmwrk2 - Success
       1/11/17 6:34:22 AM PST: 
       1/11/17 6:34:22 AM PST: 
       1/11/17 6:34:22 AM PST: DbVersionController Completed Wednesday, January 11, 2017 6:34:22 AM PST
       

       View the DbVersionController.log file to verify that all the scripts were successful or have already been run.

17. If the domain names or managed server names for the old WebLogic domain and the new WebLogic domain are different, then delete the records from the UIM database schema tables named WL_LLR_servername.

    For example, if there were two managed servers (uim_ms1 and uim_ms2) from the previous UIM release, you would need to delete the records from the following tables:

    WL_LLR_UIM_MS1 and WL_LLR_UIM_MS2

18. Restart all the servers, including the Administration server, using the following command:

    ./startUIM.sh

19. In the managed server start-up log, exceptions can be observed that are related to jax-rs and inventory.ear. Managed server will be in ADMIN state. Therefore, manually undeploy these from WebLogic console or remove jax-rs and inventory.ear entries from config.xml file.

20. Stop the servers, clear tmp, clear cache of admin and managed servers, and start the servers.

This section assumes you have already performed the pre-upgrade steps appropriate for the release of UIM from which you are upgrading. This section also assumes you have downloaded the software pack to temp_dir.

Perform the following tasks to upgrade UIM.

These post-upgrade tasks apply if your old version of UIM is version 7.4.1, or above. Complete all of the following post-upgrade tasks after upgrading UIM, if necessary:

1. Verify that the upgrade process completed successfully before performing the remaining post-upgrade tasks. See "Verifying the Unified Inventory Management Installation" for more information.

2. If the old version of your UIM user interface was customized, apply the changes to the new version of UIM. (You backed up these changes when performing the pre-upgrade tasks.)

3. Install the new version of Design Studio. See the Design Studio documentation for more information.

   Oracle recommends installing the new version of Design Studio along side the old version of Design Studio so that you can migrate custom cartridges to the new version more easily.

4. Deploy all the 8.0.0 base cartridges into the upgraded UIM environment. For information on base cartridges, see "Overview" in UIM Cartridge Guide.

5. Redeploy any custom cartridges and cartridge packs, after migrating and compiling the cartridges and cartridge packs using Design Studio. See the Design Studio documentation for more information.

6. Repackage the 8.0.0 custom.ear file by doing the following, regardless of whether any custom code needs to be added:

   1. In the Oracle WebLogic Server Administration Console, undeploy the existing 7.4.x custom.ear or 7.x custom.ear file.

   2. Make a backup copy of the 8.0.0 custom.ear file located in the UIM_Home/app/8_0_0 directory.

   3. Extract the contents of the 8.0.0 custom.ear file to a temporary directory, such as tempDirCustom.

   4. Copy any custom code from 7.x custom.ear to 8.0.0 custom.ear (which is extracted to tempDirCustom).

   5. Repackage the 8.0.0 custom.ear file with the upgraded content in the tempDirCustom directory.

   6. Copy the upgraded and repackaged custom.ear file to the UIM_Home/app/8_0_0 directory.

      Note:

      You will deploy the repackaged custom.ear file in a later post-upgrade step, after you have restarted the WebLogic Server.

7. For cluster server upgrades, increase the Stuck Thread Max Time value of each server from 600 to 1200:

   1. Log in to the WebLogic Server Administration Console.

   2. In the left section, under Domain Structure, expand Environment.

   3. Click Servers.

      The Summary of Servers page appears.

   4. Click the link for each managed server.

      The Settings for ManagedServer page appears, where ManagedServer is the name of the managed server you selected.

   5. Click the Configuration tab.

   6. Click the Tuning sub-tab.

   7. In Stuck Thread Max Time, change the value from 600 to 1200.

   8. Click Save.

8. Deploy the custom.ear file by running the following command:

   java -cp MW_Home/wlserver/server/lib/weblogic.jar weblogic.Deployer -adminurl t3://ServerName:Port -user UserName -password Password -deploy Domain_Home/UIM/app/uimVersion/custom.ear -targets ServerName -name custom -plan Domain_Home/UIM/app/plan/Plan.xml
   

   where:

   • MW_Home is the directory in which the Oracle Fusion Middleware 14.1.2 products are installed.

   • Domain_Home is the directory containing the configuration for the domain into which UIM is installed.

   • ServerName is the name of the Administration Server machine.

   • Port is the Administration Server port number.

   • UserName is the user name with which you connect to the Administration server.

   • Password is the password for the Administration server.

   • name is the name of the file. This value defaults to the base name of the deployment file or directory.

   • targets is the administration server name or cluster server name.

   • uimVersion is the directory of the UIM release version.

9. UIM replaces the system-config.properties file during the upgrade process. If you do not back up the changes you made in the system-config.properties file, you will lose them; however, you must re-apply those changes after upgrading UIM.