Upgrading Oracle Communications MetaSolv Solution

Upgrade Impacts

When upgrading to MSS 8.0, you must consider the following upgrade impacts:

Database Software Changes

The MSS database upgrade and installation files enable you to get the database to the current MSS GA level. The MSS.R8_0_DBBaseInstall.zip script sets up the database structure and the MSS.R8_0x.byyy_DBInstall.zip script installs the MSS 8.0 database.

The following are the supported database upgrade paths:

If you are currently at MSS 6.0.x , MSS 6.2.x, or MSS 6.3.x, you are required to extract and run only the MSS.R8_0_x.byyy_DBInstall.zip script.
If you are installing MSS 8.0 for the first time, you must first extract and run the MSS.R8_0_DBBaseInstall.zip script, and then extract and run the MSS.R8_0_x.byyy_DBInstall.zip script.

WebLogic Server Changes

If you are installing MSS 8.0 for the first time, or if you are upgrading from MSS 6.0.x, MSS 6.2.x, or MSS 6.3.0, you must do a full installation of Oracle WebLogic Server and the application server. If you are upgrading from MSS 6.3.1, you can use the Reconfiguration Wizard to upgrade the WebLogic domain.

MSS Application Server Upgrade Process

The high-level application server upgrade process is described below:

Undeploy MSS 8.0-related applications.
Install MSS 8.0.
Install/deploy MSS 8.0-related applications.
Update/restore configuration files.

Downloading the Maintenance Release or Patch Software

Software for MSS patches is downloaded from the My Oracle Support website. For information on downloading product software, see "Downloading the Installation Files".

Download the file for the appropriate patch you are installing. The following bullet shows how the download link for the file appears on the Oracle software delivery website.

MSS.RreleaseNumber.bbuild_AppServerInstaller: This file contains an installer for application server machines where releaseNumber is the MSS software release version and build is the build number. The files it installs on the application server include both the application server software and the client software, which is distributed from the application server. An example filename is in the following format:
```
MSS.R8.0.0_b1_AppServerInstaller.jar
```

Installing a Maintenance Release or Patch on the Database

Your database must be at least at the 8.0 release level to install a 8.0.x maintenance release or patch. See "Setting Up The MSS Database" for steps on how to upgrade the database to MSS 8.0.x. Then, follow the steps in this chapter to apply a subsequent maintenance release or patch.

To learn about database changes included in a given release, see MetaSolv Solution Database Change Reference. This document can be downloaded from the Oracle software delivery website.

Figure 8-1 shows the upgrade path for the database.

Figure 8-1 MSS Database Upgrade Path

Description of "Figure 8-1 MSS Database Upgrade Path"

Note:

Before upgrading your database to MSS 8.0.x, ensure that you grant the SELECT ON privileges to ASAP user ID by running the following GRANT statement using a user ID other than ASAP (for example, SYS) that has database administrator privileges:

GRANT SELECT ON sys.user$ TO asap WITH GRANT OPTION;

Extracting the MSS Database Scripts

Extracting the contents of the MSS.R8_0_x.byyy_DBInstall.zip file copies SQL scripts, procs, and reports to a directory you choose on a client machine or on the database server. Figure 8-2 shows the directory structure that results from the extract, based on the paths specified in the ZIP file.

Figure 8-2 Structure of Database Upgrade File

Description of "Figure 8-2 Structure of Database Upgrade File"

The MSS database scripts reside in the MSS.R8_0_x.byyy_DBInstall.zip file (where yyy is the build number). This zip file contains database scripts used to upgrade an existing MSS 6.0.2 or higher database to MSS 8.0.

To extract the MSS database scripts to the database server machine:

Locate and select the MSS.R8_0_x.byyy_DBInstall.zip file.
Right-click the file, select Open With, then select WinZip Executable.
From the main menu bar, select Actions and then select Select All.
From the main menu bar, select Actions and then select Extract.
Browse to the directory to which you want to extract the database scripts. Oracle recommends extracting the scripts to a directory on your database server.

To successfully install a maintenance release or patch on the database, you must run the two following primary SQL files:

pfixSQL_Master located in the prodfixsql directory
master located in the procs directory.

All 8.0 maintenance releases carry cumulative changes from previous maintenance releases. That means you only have to run the pfixSQL_Master and master SQL files for the maintenance release you are installing to get all changes since the 6.0.2 GA release.

Updating the Database by Running SQL Scripts

The prodfixsql directory has a number of SQL scripts that update your database.

To update the database:

Change your Start in: directory to the location where you want the audit logs to appear and connect (from that location) to SQL*Plus using the ASAP user ID.
At the prompt, enter:
```
@driveletter:installation_directory/prodfixsql/pfixSQL_Master.sql
```
The SQL scripts run against the database and make the appropriate changes for the maintenance release or patch. When the prompt reappears, the contents of the prodfixsql directory where the SQL files were stored have been applied.
Verify that the contents of the prodfixsql directory have been applied to your database correctly, review the log file for each prodfixsql file that was applied.

The log files reside in the Start in: directory. Search the files in the directory for ORA-.
Open the dm_rprt.txt file and look for processes that have passed, failed, or not run.

If you find processes that failed or did not run, contact Oracle Global Customer Support.

Granting Required Privileges for ASAP

This is a one time task. Ignore this step if it has been run already. You can verify this by querying DM tables (dm_procedure_run, dm_procedure, dm_process, and dm_procedure_error).

Before updating the stored procedures, ensure that you run the 30056241.sql using SYS user with sysdba privileges.

@driveletter:installation_directory/prodfixsql/30056241.sql

Updating Stored Procedures

Use SQL*Plus to apply the contents of the install_directory\procs directory to the database. These steps update the stored procedures for your database.

To update stored procedures:

Set the current directory to:
```
drive_letter:\install_directory\procs
```
Connect to SQL*Plus using the ASAP user ID.
At the prompt, enter:
```
spool master.log
@master
```
The stored procedures have been applied when the <SQL> prompt reappears.
Enter:
```
spool offrun
```

Running Reports

The mdl_upd directory contains SQL files that include any modifications to the database structure in a service pack. To apply these updates to the reports, copy the contents of this directory into either the db/inst_80 or db/upg_80 directory. After applying the files in the prodfixsql directory, you can validate the database structure by running the mdl_upd_cur.sql or mdl_upd_cmp.sql file, or both. These processes provide the reports mdl_upd_cur.txt and mdl_upd_cmp.txt identical to the mdl_cur.sql and mdl_cmp.sql files. See MetaSolv Solution System Administrator's Guide for more information on reports.

Note:

This task is not required. If you choose not to apply updates to the reports before you run them, extra database objects can appear in the reports.

Upgrading the MSS Application Server

The installer JAR file for the application server portion of MSS is the same for both maintenance release and patch installations. Download the installer for the appropriate platform and the appropriate upgrade type (maintenance release or patch) from the Oracle software delivery website.

See "Downloading the Maintenance Release or Patch Software" for more information on the JAR file name.

Installation Options for the Application Server

Oracle recommends the following for the application server installation of the MSS 8.0 release and patches:

First time installing or upgrading the MSS 8.0 release stream: Select the MSS 8.0 Full Installation option in the application installer. Significant changes were made in the WebLogic Server configuration for these maintenance releases, and using the full installation guarantees that all changes are installed on your machine. Refer to "Installing and Deploying MetaSolv Solution on a Single Server" or "Installing and Deploying MetaSolv Solution on a Clustered Server" to install the latest version of MSS.

The files in the following directories (under the MSLV_Home/server_name/appserver directory) are updated if you select the Full Installation option and it will be necessary to backup the following files and directories:
- bin
- cab
- classes
- config
- samples
- samples/customExtensions
- utils
Patches and Subsequent Maintenance Releases: Select the MSS 8.0 Upgrade option when you install a patch or subsequent maintenance release. Review the ReadMe file and manually apply any required configuration changes.

The following application server configuration files are updated if you select the Upgrade option and it will be necessary to backup these files:
- jmaster.ini
- lerg.ini
- loggingconfig.xml
- mslvloggingconfig.xml
- npasplit.ini
- mss.ini
- mss_util.ini
The following files are not updated if you select the Upgrade option:
- Application server start up files:
  - startMSLVmanaged.sh or startMSLVmanaged.cmd
  - startMSLVsingle.sh or startMSLVsingle.cmd
  - startservername.sh or startservername.cmd
- Gateway configuration files
  - gateway.ini
  - integration.xml
- WebLogic Server configuration parameters
- JacORB configuration parameters
Upgrade from MSS 6.3.1: If you are upgrading from MSS 6.3.1, you can utilize the Reconfiguration Wizard to upgrade any WebLogic domain that was originally created with Oracle WebLogic Server.

When employing this wizard to reconfigure your WebLogic Server domain, the following items are automatically updated, depending on the specific applications within the domain:
- WLS core infrastructure
- Domain version
After you upgrade the WebLogic domain, you have to manually update the following files in single and cluster server upgrades:
- startMSLVorb.sh
- orb.properties
- metasolv.properties
- startMSLVsingle.sh or startMSLVsingle.cmd (for single server upgrade)
- startAdminServer.sh or startAdminServer.cmd (for cluster server upgrade)
- startProxyServer.sh or startProxyServer.cmd (for cluster server upgrade)
- startMSLVmanaged.sh or startMSLVmanaged.cmd (for cluster server upgrade)
- startservername.sh or startservername.cmd
  
  For example, startmslv01.sh.
- stopservername.sh or stopservername.cmd
  
  For example, stopmslv01.sh.
- stopProxyAndAdmin.sh or stopProxyAndAdmin.cmd (for cluster server upgrade)
- Config.xml

Single Server Upgrade Basic Steps

To upgrade the single server:

Prepare for the upgrade. This includes downloading files and collecting information.
Install /Deploy MSS 8.0.
Complete post-upgrade tasks.
1. (Optional) Tune the server.
2. (Optional) Make changes to the configuration files.

Single Server Upgrade

Follow the procedures in this section to upgrade the server.

Note:

You will need to manually modify the loggingconfig.xml and the integration.xml files or you will receive an error on your appserver console. Additionally, if using custom extensions, you will need to manually modify the gateway.ini file. For information on custom extensions, see MetaSolv Solution Custom Extensions Developer's Reference.
When upgrading from 6.3.1.587 or earlier, re-encrypt the passwords in the gateway.ini file which had an underlying password length greater than 8 characters prior to the upgrade. See "Copying Encrypted Passwords to gateway.ini" in System Administrator's Guide on how to copy the encrypted passwords to the gateway.ini file. All configuration changes to the gateway.ini file require a restart of the AppServer.

Preparing for the Upgrade

The highlighted sections of Figure 8-3 show the steps for preparing for the upgrade.

Figure 8-3 Preparing for the Upgrade

Description of "Figure 8-3 Preparing for the Upgrade"

To prepare for the upgrade:

Download the MSS upgrade (either a maintenance release or a patch) from the Oracle software delivery website.
FTP the MSS upgrade file to the target server machine.
Complete the appropriate single server worksheets in Appendix C.
Archive the MSLV_Home and MW_Home directories and save the archive file to a temporary directory.

Undeploy Previously Installed Applications

The highlighted sections of Figure 8-4 show the steps for undeploying previously installed applications.

Figure 8-4 Undeploying Applications

Description of "Figure 8-4 Undeploying Applications"

To undeploy previously installed applications:

Start the WebLogic Server and log in to the WebLogic Remote Console.
To undeploy the application, do the following:
1. In the Monitoring Tree, click Deployments and then click Application Management.
2. Click the check box for nur.ear.
3. Click Stop and select Force Stop Now.
4. Click Delete.
5. Click Yes to delete the deployment.
6. Click Shopping Cart, and then click Commit Changes, which activates these changes.
Repeat step 2 for each application that is to be deleted, refer to the following list:
- asrXX.ear (if deployed)
- custom Web Service EAR (if deployed)
- MSS_WebService.ear

Installing the Upgrade

The highlighted sections of Figure 8-5 show the steps for installing the upgrade.

Figure 8-5 Installing the Upgrade

Description of "Figure 8-5 Installing the Upgrade"

To install the upgrade, do the following:

From the directory where the maintenance release or patch file was downloaded, enter the following command:
```
java -jar MSS.RreleaseNumber.bbuild_AppServerInstaller.jar
```
where releaseNumber is the MSS software release version and build is the build number. For example:
```
java -jar MSS.R8_0_0.b74_AppServerInstaller.jar
```
The Select MetaSolv home directory window appears.

From the Look In list, click the down arrow and select a directory in which the installer files can be stored and used during the installation process, then click Select.

A directory named installer is automatically created in the selected directory. Oracle recommends choosing your MSLV_Home directory for this task.

The installer auto-launches the installation process by invoking setup.sh (UNIX/Linux) or setup.cmd (Windows) in the MSLV_Home/installer directory.

Worksheet references and example values:

Field name

Worksheet reference number

Example value

File Name

(MSLV_Home)

COMM-0090

/opt/m80Single/single

The Oracle Communications MetaSolv Solution Installation window appears.

Click Next.

The Oracle Communications MetaSolv Solution Installation - Choose Install Type window appears.
Select Upgrade and click Next.

The Oracle Communications MetaSolv Solution Installation - Upgrade Select Server window appears.
In the MetaSolv Home field, enter the path and name of the MetaSolv home directory or click Browse to navigate to the directory.

All the remaining fields (except the Pass field) are auto-populated with the values you specified during full installation.

In the Pass field, enter the password for the administration server.

Worksheet references and example values:

Field name	Worksheet reference number	Example value
Admin Host	Admin-0250	srvrchscal
Port#	Admin-0260, Admin-0270	7001 (HTTP port), 7002 (HTTPS port)
User ID	COMM-0020	weblogic
Pass	COMM-0030	Specify the Administration server password.

Click Connect.

The installer queries the Admin Host machine and returns with values you entered during the configuration of the WebLogic domain. This process can take a few moments.

If the domain does not have a JAX-WS template applied, then the following message is displayed:
```
Please update the domain with the required JAX-WS Extension template and restart the installation.
```
Exit the installer and upgrade the domain by applying the WebLogic Advanced Web Services for JAX-WS Extension template and optionally the WebLogic JAX-WS SOAP/JMS Extension template. Retry the installation again after selecting the appropriate template(s):
- WebLogic Advanced Web Services for JAX-WS Extension Template (Required)
- WebLogic JAX-WS SOAP/JMS Extension Template (Optional)
The Oracle Communications MetaSolv Solution Installation window appears with the domain and any servers in the domain appearing in the left pane.
Select the server in the left pane.
Click Install.

The Installation Summary window appears.
After the installation completes, the Installation Complete window appears.

The installer installs the appropriate MSS files to the server. When the files are installed, the location of the startup file created for the server is displayed.

Note:

Do not exit the installer.
Note the location of the startup file for the application server, then minimize the installer window.
Shut down the server, and restart it using the custom script installed by the installer and listed on the window.

To start the servers, navigate to the mslvdomain directory. At the command prompt, enter the command:

For UNIX/Linux:
```
startmslv01.sh
```
For Windows:
```
startmslv01.cmd 
```
To shut down the servers, navigate to the mslvdomain directory. At the command prompt, enter the command:

For Unix/Linux:
```
stopmslv01.sh
```
For Windows:
```
stopmslv01.cmd
```
Note:

To start or stop the administration server and managed servers (in a cluster environment) using the SSL port, you must add an s after http in the ADMIN_URL argument in the startup/stop server scripts for the administration server and for each managed server. For example:
```
https://host_name:admin_sslport
```
Start the WebLogic Remote Console.

You can monitor the deployment from the console. To check the servers, click Servers in Environment in the Monitoring Tree in the Console.

Deploying the Application

The highlighted sections of Figure 8-6 show the steps for deploying the upgrade.

Figure 8-6 Deploying the Application

Description of "Figure 8-6 Deploying the Application"

To deploy the upgrade, do the following:

After the startup commands have been run and the application server has been started, maximize the installer window and click Deploy Application.

The Oracle Communications MetaSolv Solution Installation window appears listing the server you can select for deployment.

This process can take a few moments. If the server is not started, a status appears on the window indicating the installer is waiting for the server to be in running mode. When the server is in running mode, you can begin the deployment.
Select a server in the Target Servers list box, and click Deploy.

The deployment process begins. You can follow the progress of the deployment by viewing the text that appears in the right pane of the installation window.

When the deployment is complete, the Deployment Completed window appears.
Click OK.
Click Exit.

The Exit? window appears.
Click OK to exit.
Continue with the steps in "Completing Post-Upgrade Tasks".

Completing Post-Upgrade Tasks

The highlighted sections of Figure 8-7 show the steps for completing post-upgrade tasks.

Figure 8-7 Completing Post-Upgrade Tasks

Description of "Figure 8-7 Completing Post-Upgrade Tasks"

To complete the post-upgrade tasks, do the following:

Tune the Oracle WebLogic Server.

See "Tuning Servers For Performance" for information on tuning.
Shut down the Oracle WebLogic Server and update the following files:
- gateway.ini file.
- integration.xml file.
- loggingconfig.xml
- mslvloggingconfig.xml
See "Configuration Files" for more information.
Start the Oracle WebLogic Server.
Run TBSGraphicsLoad.exe from a client workstation to load specific graphics to the database. See "Loading New and Updated Graphics to the Database" for more information.
Re-install ASR, if required.

Clustered Server Upgrade Basic Steps

To upgrade the clustered server:

Prepare for the upgrade, which includes downloading files and collecting information.
Install and deploy MSS 8.0.
Complete the post-upgrade tasks.

Clustered Server Upgrade

Follow the procedures in this section to upgrade the clustered servers.

Preparing for the Upgrade

The highlighted sections of Figure 8-8 show the steps for preparing for the upgrade.

Figure 8-8 Preparing for the Upgrade

Description of "Figure 8-8 Preparing for the Upgrade"

To prepare for the upgrade:

Download the MSS upgrade (either a maintenance release or a patch) from the Oracle software delivery website.
FTP the MSS upgrade file to the target server machine.
Complete the appropriate single server worksheets in Appendix C.
Archive the MSLV_Home and MW_Home directories, on the administration server and all clustered servers, and save the archive files to a temporary directory.

Undeploy Previously Installed Applications

The highlighted sections of Figure 8-9 show the steps for undeploying previously installed applications.

Figure 8-9 Undeploying Applications

Description of "Figure 8-9 Undeploying Applications"

To undeploy previously installed applications:

Start the WebLogic Server and log in to the WebLogic Server Remote Console.
Verify that all the clustered servers are running. In the Monitoring Tree, expand Environment and click Servers.
To undeploy the application, do the following:
1. In the Monitoring Tree, click Deployments and then click Application Management.
2. Click the check box for nur.ear (or cluster-nur.ear).
3. Click Stop and select Force Stop Now.
4. Click Delete.
5. Click Yes to delete the deployment.
6. Click Shopping Cart, and then click Commit Changes, which activates these changes.
Repeat step 3 for each application that is to be deleted, refer to the following list:
- asrXX.ear (if deployed)
- Custom Web Service EAR
- MSS_WebService.ear

Installing the Upgrade

The highlighted sections of Figure 8-10 show the steps for installing the upgrade.

Figure 8-10 Installing the Upgrade

Description of "Figure 8-10 Installing the Upgrade"

To install the upgrade, do the following:

For each clustered server, from the directory where the maintenance release or patch file was downloaded, enter the following command:
```
java -jar MSS.RreleaseNumber.bbuild_AppServerInstaller.jar
```
where releaseNumber is the MSS software release version and build is the build number. For example:
```
java -jar MSS.R8_0_0.b74_AppServerInstaller.jar
```
The Select MetaSolv home directory window appears.

From the Look In list, click the down arrow and select a directory in which the installer files can be stored and used during the installation process, then click Select.

A directory named installer is automatically created in the selected directory. Oracle recommends choosing your MSLV_Home directory for this task.

The installer automatically starts the installation process by invoking setup.sh (UNIX/Linux) or setup.cmd (Windows) in the MSLV_Home/installer directory.

Worksheet reference and example value:

Field name	Worksheet reference number	Example value
File Name (MSLV_Home)	COMM-0090	/opt/m80Single/single

The Oracle Communications MetaSolv Solution Installation window appears.

Click Next.

The Oracle Communications MetaSolv Solution Installation - Choose Install Type window appears.
Select Upgrade and click Next.

The Oracle Communications MetaSolv Solution Installation - Upgrade Select Server window appears.
In the MetaSolv Home field, enter the path and name of the MetaSolv home directory or click Browse to navigate to the directory.

All the remaining fields (except the Pass field) are auto-populated with the values you specified during full installation.

In the Pass field, enter the password for the administration server.

Worksheet references and example values:

Field name	Worksheet reference number	Example value
Admin Host	Admin-0250	srvrchscal
Port#	Admin-0260, Admin-0270	7001 (HTTP port), 7002 (HTTPS port)
User ID	COMM-0020	weblogic
Pass	COMM-0030	Specify the Administration server password.

Click Connect.

The installer queries the Admin Host machine and returns with values you entered during the configuration of the WebLogic domain. This process can take a few moments.

If the domain does not have a JAX-WS template applied, then the following message is displayed:
```
Please update the domain with the required JAX-WS Extension template and restart the installation.
```
Exit the installer and upgrade the domain by applying the WebLogic Advanced Web Services for JAX-WS Extension template and optionally the WebLogic JAX-WS SOAP/JMS Extension template. Retry the installation again after selecting the appropriate template(s):
- WebLogic Advanced Web Services for JAX-WS Extension Template (Required)
- WebLogic JAX-WS SOAP/JMS Extension Template (Optional)
The Oracle Communications MetaSolv Solution Installation window appears with the domain and any servers in the domain appearing in the left pane.
Select the server in the left pane.
Click Install.

The Installation Summary window appears.
After the installation completes, the Installation Complete window appears.

The installer installs the appropriate MSS files to the server. When the files are installed, the location of the startup file created for the server is displayed.

Note:

Do not exit the installer.
Note the location of the startup file for the application server, then minimize the installer window.
Repeat steps 1 through 11 for all clustered server machines.
Shut down the administration server, and restart it using the custom script installed by the installer and listed on the window.

To start the servers, navigate to the mslvdomain directory. At the command prompt, enter the command:
- For UNIX/Linux:
```
startmslv01.sh
```
- For Windows
```
startmslv01.cmd
```
To shut down the servers, navigate to the mslvdomain directory. At the command prompt, enter the command:
- For UNIX/Linux:
```
stopmslv01.sh
```
- For Windows
```
stopmslv01.cmd
```
Note:

To start or stop the administration server and managed servers (in a cluster environment) using the SSL port, you must add an s after http in the ADMIN_URL argument in the startup/stop server scripts for the administration server and for each managed server. For example:
```
https://host_name:admin_sslport
```
Start the WebLogic Server Remote Console.

You can monitor the deployment from the console. To check the servers, click Servers in Environment in the Monitoring Tree in the Console.
Restart all the clustered servers using the custom scripts installed by the installer and listed on the window.
Verify that all the clustered servers are running.
1. To check the servers, click Servers in Environment in the Monitoring Tree in the Console.

Deploying the Application

The highlighted sections of Figure 8-11 show the steps for deploying the upgrade.

Figure 8-11 Deploying the Application

Description of "Figure 8-11 Deploying the Application"

To deploy the upgrade, do the following:

After the startup commands have been run and the application server has been started, maximize the installer window and click Deploy Application.

The Oracle Communications MetaSolv Solution Installation window appears listing the server you can select for deployment.

This process can take a few moments. If the server is not started, a status appears on the window indicating the installer is waiting for the server to be in running mode. When the server is in running mode, you can begin the deployment.
Select a server in the Target Servers list box, and click Deploy.

The deployment process begins. You can follow the progress of the deployment by viewing the text that appears in the right pane of the installation window.

When the deployment is complete, the Deployment Completed window appears.
Click OK.
Click Exit.

The Exit? window appears.
Click OK to exit.
From the WebLogic Server Remote Console, modify the cluster address by performing the following:
1. From the Domain Structure tree, expand Environment and click Clusters.
2. Click the cluster name.
  
  The Configuration tab and the General tab are selected by default.
3. Change the SSL port for the cluster address to a DNS entry containing all clustered servers' listening IP addresses. All clustered servers in the production environment should listen on the same port. If not, navigate to Servers, select each clustered server, click the Configuration tab followed by the General tab, and change the Listen Port. Modify the JNDI URL in the gateway.ini file for each clustered server.
Continue with the steps in "Completing Post-Upgrade Tasks".

Completing Post-Upgrade Tasks

The highlighted sections of Figure 8-12 show the steps for completing post-upgrade tasks.

Figure 8-12 Completing Post-Upgrade Tasks

Description of "Figure 8-12 Completing Post-Upgrade Tasks"

To complete the post-upgrade tasks, do the following:

Tune the Oracle WebLogic Server.
See "Tuning Servers For Performance" for information on tuning.
Start the WebLogic Remote Console and go to Environment, click Clusters, and then click the cluster.
Change the cluster address to the DNS host name.

Note:

Do not use the comma-separated list of single address host names or IP addresses in a production environment. These can be used in a development or test environment
Shut down the Oracle WebLogic Server and update the following files:
- gateway.ini file.
- integration.xml file.
- loggingconfig.xml
- mslvloggingconfig.xml
See "Configuration Files" for more information.
Restart all cluster managed servers.
Run TBSGraphicsLoad.exe from a client workstation to load specific graphics to the database. See "Loading New and Updated Graphics to the Database" for more information.
Re-install ASR, if required.

Upgrading from MSS 6.3.1

You can upgrade from MSS 6.3.1 to MSS 8.0 using the Reconfiguration Wizard to upgrade any WebLogic domain that was created with Oracle WebLogic Server.

Note:

You must upgrade the domain on every computer in the application environment.

The following are the prerequisites for reconfiguring the WebLogic domain:

Undeploy all the MSS deployments (nur.ear, cluster-nur.ear, and so on) and custom deployments if any.
Shutdown all the MSS 6.3.1 active servers.

To use the Reconfiguration Wizard to reconfigure WebLogic Server domains,see "Reconfiugring WebLogic Domains" in Upgrading Oracle WebLogic Server.

After you reconfigure the WebLogic Server domain, it may be necessary to perform tasks such as re-applying customizations to startup scripts, verifying file permissions, and more.

Reapplying Customizations in the Startup Server Scripts

You must update the customizations that are done in the MSS files as they are not updated by reconfiguring the WebLogic domain.

Note:

You must reapply the customizations on every server in the cluster server upgrade.

Change JDK8 to JDK21 certificate in orb.properties and config.xml.

orb.properties:

jacorb.security.keystore=/path/to/your/JDK21/identity.jks
jacorb.security.keystore_password=

config.xml:

<server>    
<name>your_server_name</name>    
<key-stores>CUSTOM_IDENTITY_AND_CUSTOM_TRUST</key-stores>    
<custom-identity-key-store-file-name>/path/to/your/JDK21/custom_identity.jks</custom-identity-key-store-file-name>    
<custom-identity-key-store-type>JKS</custom-identity-key-store-type>    
<custom-identity-key-store-pass-phrase-encrypted>{AES}encrypted_passphrase_here</custom-identity-key-store-pass-phrase-encrypted> 
<custom-trust-key-store-file-name>/path/to/your/JDK21/TrustStore.jks</custom-trust-key-store-file-name>    
<custom-trust-key-store-type>JKS</custom-trust-key-store-type>    
<custom-trust-key-store-pass-phrase>{AES}encrypted_passphrase_here</custom-trust-key-store-pass-phrase>
</server>

In the metasolv.properties file:
- Update the keystore_location to the JDK21 certificate.
- Update bea_home_dir to MW_HOME WebLogic 14.1.2 path.
In starMSLVorb.sh:
- Update BEA_HOME variable with MW_HOME of WebLogic 14.1.2.
- Update JAVA_HOME variable with JDK21 path.
In startAdminServer.sh or startAdminServer.cmd, add a slash '/' at the end of the values for the BEA_HOME and DOMAIN_NAME parameters.
In startProxyServer.sh or startProxyServer.cmd:
- Add a slash '/' at the end of the value for the BEA_HOME parameter.
- Update the SERVER_NAME to the proxy server name. For example, SERVER_NAME = mslvProxyServer.
- Ensure that the port address is correct in the ADMIN_URL parameter.
In startservername.sh or startservername.cmd:
- Add a slash '/' at the end of the value for the DOMAIN_HOME parameter.
- Update the SERVER_NAME to the manages server name. For example, SERVER_NAME = mslv01.
- Ensure that the port address is correct in the ADMIN_URL parameter.
In startMSLVmanaged.sh or startMSLVmanaged.cmd, remove the -d64 argument in the MEM_ARGS parameter.

In stopProxyAndAdmin.sh or stopProxyAndAdmin.cmd:

Remove the following JAVA_OPTIONS parameters:

JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.SSL.ignoreHostnameVerification=true" 
export JAVA_OPTIONS 
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.SSL.trustedCAKeyStore=/path/to/trust.jks"
export JAVA_OPTIONS

Add the following:

if [ -z "$1" ] ; then
    echo "Custom Certificate PassPhrase not provided."
    echo "Usage: $0 <CustomTrustKeyStorePassPhrase>"
    exit
fi
passPhrase="$1" 
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.SSL.ignoreHostnameVerification=true"  
export JAVA_OPTIONS 
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.TrustKeyStore=CustomTrust"
export JAVA_OPTIONS 
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.CustomTrustKeyStoreFileName=/path/to/jdk21/trust.jks"
export JAVA_OPTIONS 
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.CustomTrustKeyStoreType=jks"
export JAVA_OPTIONS 
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.CustomTrustKeyStorePassPhrase=${passPhrase}"
export JAVA_OPTIONS

Add a slash '/' at the end of the value for the BEA_HOME and DOMAIN_NAME parameters.
Ensure that the port address is correct in the ADMIN_URL parameter.

Rename tbs.ini and tbs_util.ini to mss.ini and mss_util.ini in the /appserver/config directory.

After you make the necessary changes, follow the steps:

Restart all the servers.
Upgrade to the latest version of MSS application.
Update the database by running SQL scripts. See "Updating the Database by Running SQL Scripts" for running the pfixSQL_Master.
Update the stored procedures. See "Updating Stored Procedures" to update the stored procedures for your database.
Verify the Database by running the Database (DB) Health Utility. See "Verifying the Database" to run the DB Health utility.

Updating Client Workstations

If you are manually installing and updating client workstations, a maintenance release or patch update to the workstation needs to be done manually the first time a user logs on to MSS after the maintenance release or patch has been installed on the application server.

You can also use the PowerClient to install and update the MSS client automatically for a maintenance release or a patch update.

8 Upgrading Oracle Communications MetaSolv Solution

Upgrade Impacts

Database Software Changes

WebLogic Server Changes

MSS Application Server Upgrade Process

Downloading the Maintenance Release or Patch Software

Installing a Maintenance Release or Patch on the Database

Extracting the MSS Database Scripts

Updating the Database by Running SQL Scripts

Granting Required Privileges for ASAP

Updating Stored Procedures

Running Reports

Upgrading the MSS Application Server

Installation Options for the Application Server

Single Server Upgrade Basic Steps

Single Server Upgrade

Preparing for the Upgrade

Undeploy Previously Installed Applications

Installing the Upgrade

Deploying the Application

Completing Post-Upgrade Tasks

Clustered Server Upgrade Basic Steps

Clustered Server Upgrade

Preparing for the Upgrade

Undeploy Previously Installed Applications

Installing the Upgrade

Deploying the Application

Completing Post-Upgrade Tasks

Upgrading from MSS 6.3.1

Reapplying Customizations in the Startup Server Scripts

Updating Client Workstations