This chapter explains how to upgrade your existing system to the latest release of Oracle Communications Unified Inventory Management (UIM).
In this chapter, the release you are upgrading from is called the old release. The release you are upgrading to is called the new release.
Upgrading to a new release of UIM consists of the following tasks:
Planning the upgrade
Performing the pre-upgrade tasks
Upgrading UIM
Performing the post-upgrade tasks
Depending on the components affected by the upgrade, your upgrade team may include the following:
A database administrator, to manage the database upgrade and tune the database.
A system integrator, to handle new and existing customizations.
A system administrator, to manage the WebLogic Server and UIM software upgrade.
A UNIX administrator, to manage accounts, network setup, and IP configurations.
Identify who might be affected by the upgrade. For example:
You might need to give your system administrators and UIM users notice of any system downtime.
Tell your system administrators in advance about any changes to the system architecture (for example, Oracle database, client, or WebLogic Server upgrades).
Train your administrators, users, cartridge developers, or system integrators on new functionality introduced by the upgrade that has an impact on their role.
You might need to make changes to your system after the upgrade is complete to accommodate new or modified features or functionality. For example, if the new release provides new security functionality, additional system configuration steps may be required. See "Upgrade Impacts" for more information.
The best way to estimate the duration of an upgrade is to perform the upgrade procedure on a test system with a copy of the production data. See "Testing the Upgrade in a Test Environment" for more information.
It is not necessary to shut down UIM or the UIM WebLogic Server domain before an upgrade. However, you must ensure that UIM is not running any operations.
Oracle recommends scheduling your upgrade during non-peak hours to minimize the disruption to your operations.
Oracle recommends running the upgrade procedure on a test system with a copy of your production data before upgrading your production system. Test the upgrade by doing the following:
Successfully completing all the pre-upgrade, upgrade, and post-upgrade tasks.
Comparing the default behavior between the old and the new releases.
Recreating any custom configurations and extensions.
Confirming that all new behavior and functionality works.
Ensuring that the database tables are properly installed.
Ensuring that the database data is correct.
Starting the WebLogic Server domain.
Ensuring that users and user permissions are correct.
Ensuring that productized and custom cartridges build and deploy properly.
Logging into UIM and verifying the version number of installed components.
This section explains any important system changes introduced by an upgrade.
New features and new functionality are described in UIM Release Notes.
When upgrading to a new release of UIM, you may need to address the following upgrade impacts:
If upgrading from:
UIM 7.2.x: You must upgrade your version of Application Development Runtime (and apply applicable patches), and install Repository Creation Utility.
UIM 7.3.x: You must upgrade your version of Application Development Runtime (and apply applicable patches).
See "Software Requirements" for version information regarding Oracle Fusion Middleware Application Development Runtime (and applicable patches) and Repository Creation Utility.
This section applies to all supported upgrade paths.
This version of UIM requires an updated version of the Java Development Kit (JDK). Regardless of the UIM release from which you are upgrading, you must update the JDK version. See "Software Requirements" for version information regarding Sun Hotspot (JDK) for Linux or Solaris.
If upgrading from:
UIM 7.2.x: You must upgrade your version of WebLogic Server and apply applicable patches.
UIM 7.3.x: You must upgrade your version of WebLogic Server and apply applicable patches.
See "Software Requirements" for version information regarding Oracle WebLogic Server Enterprise Edition and applicable patches.
This section applies to all supported upgrade paths.
The new version of UIM supports the same Oracle Database software version as the old version of UIM, but you do need to apply applicable patches. See "Software Requirements" for more information.
If you decide to upgrade to a new version of the Oracle Database software, you must also update your database client software.
This section applies to all supported upgrade paths.
The new version of UIM requires an updated database schema. Regardless of the UIM release from which you are upgrading, and regardless of whether you opt to upgrade the Oracle Database software, you must update the database schema.
The Oracle Application Installer updates all the UIM components.
You must upgrade your version of Oracle Communications Design Studio.
See "Software Requirements" for version information regarding Design Studio.
Design Studio can be set up before or after you upgrade UIM. See the Design Studio installation documentation for more information. Rather than upgrading Design Studio, install the new version and keep the old version until after you have finished upgrading UIM.
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.
The Oracle Universal Installer updates the localization pack to be compatible with the new release of UIM, however any new fields and labels introduced in the new release are not localized. Edit the localization pack for the new fields and labels.
This section details the upgrade procedures to upgrade UIM:
From release 7.2.0 to release 7.3.5 by doing the following tasks:
From release 7.2.x (except 7.2.0) to release 7.3.5 (where 7.2.x is 7.2.2, 7.2.3, 7.2.4, or 7.2.5) by doing the following tasks:
From release 7.3.x to release 7.3.5 (where 7.3.x is 7.3.0, 7.3.1, 7.3.2, 7.3.3 or 7.3.4) by doing the following tasks:
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.2.0. Perform the following pre-upgrade tasks:
Back up the UIM and MDS databases. See UIM System Administrator's Guide for more information.
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.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.)Stop the UIM Domain Servers.
Upgrade Fusion Middleware to 11g PS6 (11.1.1.7.0) and apply applicable patches.
Upgrade the UIM MDS Schema by performing the following steps:
Navigate to the MW_Home/oracle_common/bin directory.
This directory contains the Patch Set Assistant (PSA) tool, which you use to upgrade the schema.
Launch the PSA tool to upgrade the schema.
The Welcome screen appears.
Click Next.
The Select Component screen appears.
Select the Oracle Metadata Services check box, and click Next.
The Prerequisites screen appears.
Confirm that the database backup is complete by selecting the Database backup completed and Database version is certified by Oracle for Fusion Middleware upgrade check boxes, and click Next.
The MDS Schema screen appears.
From the Database Type list, select the database type.
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.In DBA User Name, enter the database administrator user name.
In DBA Password, enter the password for the user name you provided in DBA User Name.
Click Connect.
If the provided details are valid, the Schema User Name and Schema Password fields become enabled.
From the Schema User Name list, select the UIM MDS schema.
In Schema Password, enter the database password, and click Next.
The Examine screen appears.
Click Next.
The Upgrade Summary screen appears.
Verify the details of the Oracle Metadata services to be upgraded and click Upgrade.
The Upgrading Components screen appears. You can monitor the progress of the upgrade from this screen.
After the upgrade completes, click Next.
The Upgrade Success screen appears.
Verify that the upgrade was successful and click Close.
Restart the WebLogic server.
Back up the folder Domain_Home/config/fmwconfig.
Copy $WLS_Domain/config/fmwconfig/audit-store.xml from another PS6 domain.
Open the jps-config.xml file in a text editor.
Scroll down to the serviceInstance entry.
Change the value of the entries for the audit serviceInstance, as shown in this example:
<serviceInstance name="audit" provider="audit.provider" location="./audit-store.xml">
<property name="audit.filterPreset" value="None"/>
<property name="audit.maxDirSize" value="0"/>
<property name="audit.maxFileSize" value="104857600"/>
<property name="audit.loader.jndi" value="jdbc/AuditDB"/>
<property name="audit.loader.interval" value="15"/>
<property name="audit.loader.repositoryType" value="File"/>
<property name="auditstore.type" value="file"/>
</serviceInstance>
Restart the Administration Server. The log will display errors for the jps_mbeans.xml file.
Copy the jps_mbeans.xml file from the MW_Home/oracle_common/modules/oracle.jps_11.1.1/domain_config/mbeans directory to the $WLS_Domain/config/fmwconfig/mbeans directory.
Restart the Administration Server.
Continue with step 4 in "Pre-Upgrade Tasks for Release 7.2.x".
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.2.x (for example 7.2.2, 7.2.3, 7.2.4, or 7.2.5). But if your old release of UIM is 7.2.0, ensure you have completed the section "Pre-Upgrade Tasks for Release 7.2.0" before completing this section.
Perform the following pre-upgrade tasks:
Back up the UIM and MDS databases. See UIM System Administrator's Guide for more information.
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.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.)Create the Oracle Platform Security Services (OPSS) schema and Audit Services (IAU) schema using Fusion Middleware Repository Creation Utility (RCU). See "Creating the Database (MetaData) Schema for UIM" for more information.
When creating the OPSS schema, ensure that on the Select Components screen, you select Select an Existing Prefix, and then from the list, select the prefix that you used to create the MDS schema during the previous installation.
See Oracle Fusion Middleware Repository Creation Utility User's Guide for more information.
Tune the authorization properties on the OPSS schema. Set the -Djps.subject.cache.key Java system property to 5.
See Oracle Fusion Middleware Performance and Tuning Guide for more information.
Create datasources for OPSS (jdbc/opssDataSource) and for Audit Services (jdbc/AuditDB) by doing the following:
Log in to the WebLogic server Administration Console using the Administrator credentials.
Click Lock & Edit.
In the Domain Structure tree, expand Services and then click Data Sources.
The Summary of JDBC Data Sources page appears.
Click New and select Generic Data Source.
The JDBC Data Sources Properties page appears.
In the Name and JNDI Name fields, enter the required information; from the Database Type list, select an option, and then click Next.
From the Database Driver list, select Oracle's Driver (Thin) for Instance connections; Versions 9.0.1 and later.
Note:
For information about creating multi data sources for Oracle Real Application Clusters (RAC) database, see the following website:http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/wls/11g/WLS_11g_RAC_multi/WLS_RAC_MULTI.htm
Click Next.
The Transaction Options Page appears.
Deselect the Supports Global Transactions check box and click Next.
The Connection Properties page appears.
In the Database Name, Host Name, Port, Database User Name, Password, and Confirm Password fields, enter the database details of the OPSS schema, and then click Next.
The Test Database Connection page appears.
Review the connection parameters and click Test Configuration.
If you receive database connection errors, ensure that you have specified the JDBC URL in the following format:
jdbc:oracle:thin:@//DB_HostName:DB_Port/DB_ServiceName
where:
DB_HostName is the database host name
DB_Port is the database port number
DB_ServiceName is the database service name or system ID
If the test is successful, click Next.
The Select Targets page appears.
Select the servers or clusters on which you want to deploy the data source and click Finish.
The Summary of JDBC Data Sources page appears.
Verify that the newly created data source is listed under the Data Sources table.
In the Change Center of the Administration Console, click Activate Changes, which activates these changes.
See the Oracle WebLogic Server documentation for more information.
From MW_Home/oracle_common/common/bin, run the reassociateSecurityStore script in online mode:
./wlst.sh connect() reassociateSecurityStore(domain="<domain_name>",datasourcename="jdbc/opssDataSource", servertype="DB_ORACLE",jpsroot="cn=jdbcRootNode")
From MW_Home/oracle_common/common/bin, run the setAuditRepository script:
setAuditRepository(switchToDB='true',dataSourceName='jdbc/AuditDB',interval='16')
Run getAuditRepository() and verify the following output:
JNDI Name: jdbc/AuditDB Interval: 16 Repository Type: DB
Stop the UIM Domain Servers.
Upgrade the Fusion Middleware Application Development Runtime:
If you are upgrading from UIM 7.2.0 through UIM 7.3.4, upgrade your version of Fusion Middleware Application Development Runtime and apply any required patches.
See "Software Requirements" for version information regarding Fusion Middleware Application Development Runtime and any applicable patches.
Upgrade the UIM MDS Schema:
Navigate to MW_HOME/oracle_common/upgrade/bin/ua
where MW_HOME is the directory in which Oracle Fusion Middleware is installed.
This directory contains the Upgrade Assistant (UA) tool, which you use to upgrade the schema.
Launch the UA tool to upgrade the schema.
The Welcome screen appears.
Click Next.
The Schemas screen appears.
Select All Schemas Used By a Domain, and select the domain directory for the upgrade and click Next.
The Components List screen appears showing the component choices to upgrade.
Oracle Audit Services Oracle Platform Security Services Oracle Metadata Services Oracle Weblogic Server
Click Next.
The Prerequisites screen appears.
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, Certification and system requirements have been met, and Oracle Platform and Security Services repository is not a file based store check boxes, and click Next.
The IAU Schema screen appears.
From the Database Type list, select the database type.
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.In DBA User Name, enter the database administrator user name.
In DBA Password, enter the password for the administrator user.
Click Connect.
If the provided details are valid, the Schema User Name and Schema Password fields become enabled.
From the Schema User Name list, select the IAU schema.
In Schema Password, enter the database password, and click Next.
The OPSS Schema screen appears.
Verify the details of the OPSS schema and click Next.
The MDS Schema screen appears.
Verify the details of the MDS schema and click Next.
Note:
For a clustered environment, the hostname:portnumber/SID must specify the primary Oracle RAC node.The Examine screen appears.
Click Next.
The Upgrade Summary screen appears.
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.
After the upgrade completes, click Next.
The Upgrade Success screen appears.
Verify that the upgrade was successful and click Close.
Create the Common Infrastructure Services (STB) schema using the Fusion Middleware RCU, which you open using the following command:
./MW_Home/oracle_common/bin/rcu
See Oracle Fusion Middleware Repository Creation Utility User's Guide for more information.
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:
Shut down all processes in the Oracle home. For example, shut down the Managed Servers, the Administration Server, and any system components.
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\*
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\*
Reconfigure the WebLogic domains using the Fusion Middleware Reconfiguration Wizard, which you open using the following command:
./MW_Home/wlserver/common/bin/reconfig.sh
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.
Click Next.
The Domain Mode and JDK screen appears.
The domain mode cannot be changed during reconfiguration. It is inherited from the original domain.
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 "Software Requirements" for more information.
The Database Configuration Type screen appears.
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.
Click Next.
Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.
On the Node Manager screen, under the Node Manager Type area, select Manual Node Manager Setup and click Next.
The Advanced Configuration screen appears.
Select the categories for which you want to perform advanced configuration and click Next.
For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration.
Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.
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.
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.
Click Next.
The Services Targeting screen appears.
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.
Click Next until the Configuration Summary screen appears.
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.
Click Finish.
See Oracle Fusion Middleware documentation for more information.
Upgrade the WebLogic domain configurations by doing the following:
Navigate to the MW_Home/oracle_common/upgrade/bin/ua directory.
This directory contains the Fusion Middleware Upgrade Assistant 12c, which you use to upgrade the WebLogic domain configurations.
Launch the Fusion Middleware Upgrade Assistant.
The Welcome screen appears.
Click Next.
Select WebLogic Component Configurations, and in the Domain Directory field, select the WebLogic domain directory you want to upgrade, and then click Next.
The Prerequisites screen appears.
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.
Navigate through the different screens by clicking Next on each screen and specifying your settings as necessary.
On the Upgrade Success screen, verify that the upgrade was successful and click Close.
See Oracle Fusion Middleware documentation for more information.
If UIM is installed in a WebLogic cluster domain, open the WL_DOMAIN/config/config.xml file and change the JD persistent store and UIM persistent store targets to managed server migratables.
See "Installing and Configuring Oracle WebLogic Server" for more information.
Start the UIM Administration Server. If this is a clustered server environment, start the cluster member servers.
Ensure that all the deployed applications are active, otherwise you will need to manually update each application and then make each application active.
(Optional) Import the UIM 7.2.x database schema from the old database to the new database, if you created a separate database (as opposed to an in-place database upgrade).
See the Oracle Database documentation for more information on the import/export utilities.
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.)(Optional) 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.
If you upgraded your Oracle Database Software, import the old data to the new database using the import data pump (impdp) utility.
See the Oracle Database documentation for information on the impdp utility.
Apply any required Oracle Database patches.
See "Software Requirements" for more information on the Oracle Database patches.
See the Oracle Database documentation for information on applying patches to the database.
Upgrade the UIM database schema by performing the following steps:
Create two temporary directories, temp_dir and temp_dir_schema.
Download the UIM software for your operating system from the Oracle software delivery website and save it to temp_dir.
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.
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.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
Grant the execute permission for the runDB.sh script.
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/jdk1.8.0_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/9/17 1:19:22 AM PST: log file = /scratch/NSRM_QA/Builds/UIM/735/logs/DbVersionController.log 1/9/17 1:19:22 AM PST: 1/9/17 1:19:24 AM PST: Applying Framework Update: sqlfrmwrk - Success 1/9/17 1:19:24 AM PST: Applying Framework Update: sqlfrmwrk1 - Success 1/9/17 1:19:24 AM PST: Applying Framework Update: sqlfrmwrk2 - Success 1/9/17 1:19:24 AM PST: 1/9/17 1:19:24 AM PST: B19271096 - Start 1/9/17 1:19:28 AM PST: B19271096 - 3388 Milliseconds 1/9/17 1:19:28 AM PST: B19271096 - Ended Successfully . . . 1/9/17 1:19:33 AM PST: Successfully completed migration scripts for release 7.3.0.0.0. 1/9/17 1:19:33 AM PST: B21264052 - Start 1/9/17 1:19:33 AM PST: B21264052 - 37 Milliseconds 1/9/17 1:19:33 AM PST: B21264052 - Ended Successfully . . . 1/9/17 1:19:34 AM PST: Successfully completed migration scripts for release 7.3.1.0.0. . . . 1/9/17 1:26:00 AM PST: Successfully completed migration scripts for release 7.3.3.0.0. . . . 1/9/17 1:26:01 AM PST: Successfully completed migration scripts for release 7.3.4.0.0. 1/9/17 1:26:01 AM PST: DbVersionController Completed Monday, January 9, 2017 1:26:01 AM PST ---------------------------------------------------------------------
View the DbVersionController.log file to verify that all the scripts were successful or have already been run.
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
Restart the WebLogic server.
If you installed MapViewer, delete the old version of MapViewer currently deployed in the domain:
Log in to the WebLogic Server Administration Console, and click on Lock & Edit button.
On the Home page, under Domain Structure, click the Deployments link.
The Summary of Deployments page appears.
Click the Control tab (within Deployments), and select the check box for the oracle.communications.inventory.mapviewer application and click Stop, and then select Force Stop Now.
A confirmation message appears.
Click Yes.
Click the Configuration tab, and select the check box for the oracle.communications.inventory.mapviewer application and click Delete.
A confirmation message appears.
Click Yes.
In the Change Center area of the Administration Console, click Activate Changes, which activates these changes.
Stop the UIM domain servers.
(Optional) Install the new version of MapViewer if you are choosing to use this software feature.
For information about installing and deploying MapViewer on the WebLogic server, see the following discussion in Fusion Middleware User's Guide for Oracle MapViewer:
(Optional) Update the existing WebLogic domain for MapViewer using the Fusion Middleware Configuration Wizard, with the following command:
./MW_Home/oracle_common/common/bin/config.sh
On the Select Domain screen, select the update an existing domain option and from the Existing Domain Location list, select the UIM domain that you want to upgrade and click Next.
The Domain Template screen appears.
Select Oracle MapViewer - 12.2.1.2.0 [oracle_common].
Click Next.
Navigate through different screens by clicking Next on each screen and specify your setting as necessary.
In the Advance Configuration screen, select Deployments and Services. Click Next.
The Deployments Targeting screen appears.
From Deployments, select the MapViewer application and then with the right arrow, target the MapViewer application to both Cluster and the Admin server.
The Services Targeting screen appears.
Click Next.
On the Configuration Summary screen, click Update to finish the upgrade.
Start the UIM domain servers.
You can now access the newly deployed MapViewer 12c application at the following URL (if you installed MapViewer):
http://ServerName:Port/mapviewer/
where:
ServerName is the application server used by UIM.
Port is the port used by UIM.
Note:
If you do not delete the older version of MapViewer before deploying the new version, and then restart the UIM domain server, the new MapViewer is started by default and the status of the older version changes to Failed.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.3.x. Perform the following pre-upgrade tasks:
Back up the UIM and MDS databases. See UIM System Administrator's Guide for more information.
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.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.)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:
Shut down all processes in the Oracle home. For example, shut down the Managed Servers, the Administration Server, and any system components.
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\*
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\*
Upgrade the Fusion Middleware Application Development Runtime to 12.2.1.2 (Weblogic Server, Infrastructure, MapViewer). MapViewer is optional software.
If you are upgrading from UIM Release 7.3.0 and you are using the MapViewer software, delete the older version of MapViewer currently deployed in the WebLogic domain by performing the following steps:
Log in to the WebLogic Server Administration Console.
On the Home page, under Domain Structure, click the Deployments link.
The Summary of Deployments page appears.
Select the check box for the oracle.communications.inventory.mapviewer application, and click Stop, and then select Force Stop Now.
A confirmation message appears.
Click Yes.
Select the check box for the oracle.communications.inventory.mapviewer application and click Delete.
A confirmation message appears.
Click Yes.
In the Change Center of the Administration Console, click Activate Changes, which activates these changes.
Stop the UIM domain servers.
Upgrade the UIM MDS Schema:
Navigate to MW_HOME/oracle_common/upgrade/bin/ua
where MW_HOME is the directory in which Oracle Fusion Middleware is installed.
This directory contains the Upgrade Assistant (UA) tool, which you use to upgrade the schema.
Launch the UA tool to upgrade the schema.
The Welcome screen appears.
Click Next.
The All Schemas screen appears.
Select All Schemas Used By a Domain, and select the domain directory for the upgrade, and click Next.
The Components List screen appears showing the Components to be upgraded:
Oracle Audit Services Oracle Platform Security Services Oracle Metadata Services Common Infrastructure Services
Click Next.
The Prerequisites screen appears.
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 IAU Schema screen appears.
From the Database Type list, select the database type.
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.In DBA User Name, enter the database administrator user name.
In DBA Password, enter the password for the administrator user.
Click Connect.
If the provided details are valid, the Schema User Name and Schema Password fields become enabled.
From the Schema User Name list, select the IAU schema.
In Schema Password, enter the database password, and click Next.
The OPSS Schema screen appears.
Verify the details of the OPSS schema and click Next.
The MDS Schema screen appears.
Verify the details of the MDS schema and click Next.
Note:
For a clustered environment, the hostname:portnumber/SID must specify the primary Oracle RAC node.The Examine screen appears and may show that the Common Infrastructure Services upgrade is not necessary.
Click Next.
The Upgrade Summary screen appears.
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.
After the upgrade completes, click Next.
The Upgrade Success screen appears.
Verify that the upgrade was successful and click Close.
(Optional) Install the new version of MapViewer. See "Software Requirements" for software version information.
For information about installing MapViewer on the WebLogic server, see the following discussion in Fusion Middleware User's Guide for Oracle MapViewer:
(Optional) If you are upgrading from UIM Release 7.3.0 (and you performed step 6), update the existing WebLogic domain for MapViewer using the Fusion Middleware Configuration Wizard, with the following command:
./MW_Home/oracle_common/common/bin/config.sh
On the Select Domain screen, select the update an existing domain option and from the Existing Domain Location list, select the UIM domain that you want to upgrade and click Next.
The Domain Template screen appears.
Select Oracle MapViewer - 12.2.1.2.0 [oracle_common].
Click Next.
Navigate through different screens by clicking Next on each screen and specify your setting as necessary.
On the Configuration Summary screen, click Update to finish the upgrade.
Start the UIM domain servers.
You can now access the newly deployed MapViewer 12c application at the following URL:
http://ServerName:Port/mapviewer/
where:
ServerName is the application server used by UIM.
Port is the port used by UIM.
Note:
If you do not delete the older version of MapViewer before deploying the new version, and then restart the UIM domain server, the new MapViewer is started by default and the status of the older version changes to Failed.Reconfigure the WebLogic domains using the Fusion Middleware Reconfiguration Wizard, which you open using the following command:
./MW_Home/wlserver/common/bin/reconfig.sh
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.
Click Next.
The Domain Mode and JDK screen appears.
The domain mode cannot be changed during reconfiguration. It is inherited from the original domain.
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 "Software Requirements" for more information.
The Database Configuration Type screen appears.
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.
Click Next.
Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.
On the Node Manager screen, under the Node Manager Type area, select Manual Node Manager Setup and click Next.
The Advanced Configuration screen appears.
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.
In the Server Groups list, select MAPVIEWER-MAN-SVR and JRF-MAN-SVR groups and click Next.(If you did not install the MapViewer software both of these entries are not available.)
For each category you selected in the previous step, the appropriate configuration screen is displayed to allow you to perform advanced configuration.
Navigate through the different screens by clicking Next on each screen and specify your settings as necessary.
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.
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.
Click Next.
The Services Targeting screen appears.
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.
Click Next until the Configuration Summary screen appears.
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.
Click Finish.
See Oracle Fusion Middleware documentation for more information.
Upgrade the WebLogic domain configurations by doing the following:
Navigate to the MW_Home/oracle_common/upgrade/bin/ua directory.
This directory contains the Fusion Middleware Upgrade Assistant 12c, which you use to upgrade the WebLogic domain configurations.
Launch the Fusion Middleware Upgrade Assistant.
The Welcome screen appears.
Click Next.
Select WebLogic Component Configurations, and in the Domain Directory field, select the WebLogic domain directory you want to upgrade, and then click Next.
The Prerequisites screen appears.
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.
Navigate through the different screens by clicking Next on each screen and specifying your settings as necessary.
On the Upgrade Success screen, verify that the upgrade was successful and click Close.
See Oracle Fusion Middleware documentation for more information.
(Optional) 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.
If you upgraded your Oracle Database Software, import the old data to the new database using the import data pump (impdp) utility.
See the Oracle Database documentation for information on the impdp utility.
Apply any required Oracle Database patches.
See "Software Requirements" for more information on the Oracle Database patches.
See the Oracle Database documentation for information on applying patches to the database.
Upgrade the UIM database schema by performing the following steps:
Create two temporary directories, temp_dir and temp_dir_schema.
Download the UIM software for your operating system from the Oracle software delivery website and save it to temp_dir.
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.
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.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
Grant the execute permission for the runDB.sh script.
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/jdk1.8.0_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.
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
Restart the WebLogic server.
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.
These upgrade tasks apply if your old version of UIM is version 7.2.x or 7.3.x. Perform the following tasks to upgrade UIM:
Navigate to the temp_dir directory and extract the contents of the downloaded software pack:
unzip -xvf Software_Pack.zip
The extracted software pack has the following structure:
uim/Disk1/install/
Navigate to the temp_dir/uim/Disk1/install/ directory, and run the following command to start the installer:
./runInstaller -jreloc jre_Path
where jre_Path is the JRE location.
Ensure that you have installed the correct version of the JRE. See "Software Requirements" for more information.
The installer Welcome screen appears.
Click Next.
In the Select Installation Type screen, select Complete, and click Next.
The Specify Home Details screen appears.
Do the following:
In Name, enter, browse to, or confirm the name of the folder that contains the installation files for the old version of UIM.
In Path, enter, browse to, or confirm the directory where the folder specified in the Name field is located.
Click Next.
The installer scans the specified directory and folder.
The installer displays a warning message if it detects a pre-existing installation of UIM.
Click Yes to acknowledge the message.
The WebLogic Administration Server Connection Information screen appears.
Do the following:
In Host Name, enter the Listen address of the Administration server (IP address or the host name of the host machine).
In Port Number, enter the Administration server port number.
In User Name, enter the user name with which you connected to the Administration Server.
Note:
This user should belong to the WebLogic Server Administrator's group.In Password, enter the password for the user name you provided in User Name.
Click Next.
The WebLogic Server/Cluster Selection screen appears.
Note:
In the following steps, the WebLogic Server should be running.Select the same target WebLogic server or cluster of servers belonging to the WebLogic Server domain to upgrade, and click Next.
If you are upgrading a cluster of servers, the Cluster Member Server Selection screen appears, where you can select a cluster member for UIM to install or upgrade.
The Database Type Selection screen appears.
Select the same database type that is used by your old UIM installation:
If your old installation is connected to a standalone database, select Standard Oracle 12c Enterprise Database and click Next.
The Database Connection Information screen appears.
Do the following:
Verify that the retrieved field values are correct, and click Next.
In Password, enter the database server password for the user name you provided in User Name.
Click Next.
If your old installation is connected to an Oracle RAC database, select Oracle 12c Real Application Cluster Database and click Next.
The Oracle RAC DB for MDS screen appears.
Do the following:
Verify that the retrieved field values are correct, and click Next.
In Password, enter the database server password for the user name you provided in User Name.
Click Next.
The Oracle RAC DB Nodes Connection Information screen appears.
Do the following:
Verify that the retrieved field values are correct, and click Next.
In Password, enter the database server password for the user name you provided in User Name.
Click Next.
The MDS Schema Information screen appears.
Enter the MDS Schema information by doing the following:
In Host Name, enter the IP address or host name of the machine where the database server is installed.
In Port Number, enter the port number with which the installer will connect to the database server.
In User Name, enter the user name for the MDS schema.
In Password, enter the password for the user name you provided in User Name.
In Service Name, enter the service name for that uniquely identifies your database on the system.
Click Next.
The Database Connection Information screen appears.
Provide the database user name and password, and click Next.
Caution:
You must use the same user name and password that you provided when you set up the database schema using the Repository Creation Utility (RCU).The user must have the following privileges: CATALOG, CONNECT, Create User, Create Session, Grant Any Privilege, Grant Any Role, Select Any Table, Select any Dictionary.
See "Creating the Database (MetaData) Schema for UIM" for more information.
The UIM database schema creation screen appears.
Enter the UIM database schema information, by doing the following:
In User Name, enter the user name for the Unified Inventory Management schema.
In Password, enter the password for the user name you provided in User Name.
In System Tablespace, enter the name for the permanent tablespace.
In Temp Tablespace, enter the name for the temporary tablespace.
Click Next.
The Security Provider Selection screen appears.
Select the security provider you want to use, and click Next.
The CMWS User Information screen appears.
Enter the CMWS User information, by doing the following:
In User Name, enter the user name for the CMWS user.
In Password, enter the password for the user name you provided in User Name.
In Confirm Password, enter the password again.
Click Next.
A warning message appears because the ”cmwsuser” already exists.
Click OK to acknowledge the message.
The UIM Administrator user creation (Optional) screen appears.
Enter the UIM User information, by doing the following:
In User Name, enter the user name for the UIM user.
In Password, define a password for the UIM user.
Note:
The UIM user password can be a maximum of 12 letters long, and should contain at least one numeric value and one capital letter. For example, Weblogic123.Also, the user name must not be part of the password.
In Confirm Password, enter the password again.
Click Next.
A warning message appears because ”uimuser” already exists.
Click OK to acknowledge the message.
The Do you want to create the UIM file store or JDBC store? screen appears.
Select the same type of store you selected when UIM was initially installed, and click Next.
The SSL enable Information screen appears.
Select whether or not to enable SSL. If you select Yes, enter the Port number. Click Next.
The MapViewer information or a Summary screen appears.
In the URL field, enter the URL for MapViewer if you installed MapViewer.
Click Next.
The Summary screen appears.
Review the selections you have made in the preceding screens, and click Install.
The Install screen appears.
You can view the installation progress.
On successful installation of Unified Inventory Management, the End of Installation screen appears.
Perform the post-upgrade tasks. See "Post-Upgrade Tasks" for more information.
These post-upgrade tasks apply if your old version of UIM is version 7.2.x or 7.3.x. Complete all of the following post-upgrade tasks after upgrading UIM, if necessary:
Verify that the upgrade process completed successfully before performing the remaining post-upgrade tasks. See "Verifying the Unified Inventory Management Installation" for more information.
If your UIM system is set up using Oracle RAC, and runs on multiple systems or across networks, update and re-enable cache coordination. See "Configuring Ehcache for the Cluster" for more information.
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.)
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.
Deploy all the 7.3.x base cartridges into the upgraded UIM environment. For information on base cartridges, see UIM Cartridge Guide.
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.
Install and configure the AspectJ libraries. To do this:
Download the aspectj-1.8.9.jar library from the following website:
http://www.eclipse.org/downloads/download.php?file=/tools/aspectj
Manually extract the aspectj-1.8.9.jar file to a temporary folder (aspectj-1.8.9), enter the following command:
java -jar aspectj-1.8.9.jar
Note:
Ensure that the AspectJ files (aspectjweaver.jar, aspectjrt.jar, and aspectjtools.jar) have execute permissions.Copy the aspectjweaver.jar file from the aspectj-1.8.9/lib folder to the UIM_Home/lib folder.
Note:
The following step is required if dynamic extensibility (for custom extension points) is to be used.Copy the aspectjrt.jar and aspectjtools.jar files from the aspectj-1.8.9/lib folder to the UIM_Home/lib folder.
Repackage the 7.3.5 custom.ear file by doing the following, regardless of whether any custom code needs to be added:
In the Oracle WebLogic Server Administration Console, undeploy the existing 7.3.x custom.ear file.
Make a backup copy of the 7.3.5 custom.ear file located in the UIM_Home/app/7_3_5 directory.
Extract the contents of the 7.3.5 custom.ear file to a temporary directory, such as tempDirCustom.
Copy any custom code from 7.3.x custom.ear to 7.3.5 custom.ear (which is extracted to tempDirCustom).
Repackage the 7.3.5 custom.ear file with the upgraded content in the tempDirCustom directory.
Copy the upgraded and repackaged custom.ear file to the UIM_Home/app/7_3_5 directory.
Note:
You will deploy the repackaged custom.ear file in a later post-upgrade step, after you have restarted the WebLogic server.For cluster server upgrades, increase the Stuck Thread Max Time value of each server from 600 to 1200:
Login to the WebLogic Server Administration Console.
In the left section, under Domain Structure, expand Environment.
Click Servers.
The Summary of Servers page appears.
Click the link for each managed server.
The Settings for ManagedServer page appears, where ManagedServer is the name of the managed server you selected.
Click the Configuration tab.
Click the Tuning sub-tab.
In Stuck Thread Max Time, change the value from 600 to 1200.
Click Save.
For clustered server upgrades, configure the WebLogic Server proxy timeout value:
Navigate to and open the Domain_Home/apps/OracleProxy4_cluster1_uim_proxy/WEB-INF/web.xml file.
Add the following parameter to the web.xml file:
<init-param>
<param-name>WLIOTimeoutSecs</param-name>
<param-value>1800</param-value>
</init-param>
Save and close the web.xml file.
Restart the WebLogic server.
If upgrading from UIM 7.2.0, convert logical devices from UIM 7.2.0 to UIM 7.2.4. (In UIM 7.2.2, logical devices were enhanced to define rate codes; so, if upgrading from UIM 7.2.2 or 7.2.3, logical devices are already converted.) To convert logical devices, execute the ruleset CONVERT_LD_SR1_TO_SR2, by giving it a list of associated Logical Device specifications. The list of Logical Device specifications is passed to the ruleset via a text file. For example, if you text file contains the following specifications:
Analog Telephony Adapter
IP Phone
Data Networking Device
Then all the Logical Device instances that have those respective specifications will be converted.
To execute the ruleset, perform the following:
Create a text file and list all the Logical Device Specifications for which you want to upgrade. You should list one specification per line.
Login to UIM and from the Tasks menu select the link Execute Rule.
From the Ruleset dropdown menu, select CONVERT_LD_SR1_TO_SR2.
Using the Browse button, select the text file that contains the list of Logical Devices to be converted.
Click the Process button (upper-right corner of the UIM UI) to start the conversion.
Restart the WebLogic server.
If there is a large number of Logical Device instances per Logical Device specifications, then the conversion process should be split into multiple executions.
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 12c 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.
If you upgraded from UIM 7.3.0, define the UIM data source for MapViewer 12c if you installed MapViewer. See "Defining the Map Data Source" for more information.
If the installer fails to successfully upgrade UIM, you must manually restore the WebLogic server domain, the database schema, and the database domain. See UIM System Administrator's Guide for more information about restoring the database. See the WebLogic Server documentation for more information about restoring the WebLogic Server domain.