11 Upgrading From Converged Application Server Release 4.0 to Converged Application Server Release 5.0

This chapter describes how to upgrade Oracle Communications Converged Application Server from Release 4.0 to Release 5.0.

About the Upgrade Process
Step 1: Install Software and Prepare the Domain
Step 2: Upgrade Version 4.0 Domain Artifacts

About the Upgrade Process

Upgrading a Converged Application Server 4.0 domain to a Converged Application Server 5.0 domain involves these basic steps:

Manually editing the config.xml file to specify the custom resources required by Converged Application Server 5.0.
Manually upgrading Converged Application Server 4.0 resources and sipserver.xml and diameter.xml configuration files to use the new Converged Application Server 5.0 schemas.

The sections that follow describe these steps in more detail, and reference the Oracle WebLogic Server 11g documentation where appropriate.

Step 1: Install Software and Prepare the Domain

Begin by installing the Converged Application Server 5.0 software into a new Oracle home directory on your Administration Server machine. See Converged Application Server Installation Guide for instructions.

You will need to know the new installation directory as well as the domain directory for your existing Converged Application Server 4.0 installation to complete the upgrade.

In the next section, you will upgrade the existing domain configuration and domain scripts to function with WebLogic Server 11g release 1 patch set 2, upon which Converged Application Server is based. Before doing so, prepare the Converged Application Server 4.0 domain by doing the following:

Read the documentation on compatibility with previous releases in Oracle Fusion Middleware Upgrade Guide for Oracle WebLogic Server 11g Release 1 (10.3.3) to determine whether any feature affects the non-SIP components of your applications. Make any necessary changes before upgrading.
Read "Porting Existing Applications to Converged Application Server" in Converged Application Server SIP Application Development Guide to determine whether any feature affects the SIP components of your applications. Make any necessary changes before upgrading.
Shut down all Managed Servers (engine and SIP data tier servers) in your domain, leaving only the Administration Server running.
Back up all of the following items:
- Deployed applications. Make a backup of each SIP, Java EE, or Diameter application installed in the domain.
- Domain configuration data. Make a backup of the full domain directory, which contains the /config subdirectory.
- Custom startup scripts. On each machine that hosts an engine or SIP data tier server, backup any custom startup scripts that you use to start server instances.
Shut down the Administration Server.

Step 2: Upgrade Version 4.0 Domain Artifacts

After making all backups described in "Step 1: Install Software and Prepare the Domain", follow these steps to manually upgrade the 4.0 domain artifacts.

Update all script files in the /bin subdirectory of the 4.0 domain directory to point to the Converged Application Server 5.0 installation. Specifically:
1. In the setDomainEnv.sh script, do the following.
  
  Note:
  In the following settings, replace any instance of CAS50_home with the path to the directory where Converged Application Server 5.0 is installed.
  - Update the WL_HOME definition to point to the Converged Application Server 5.0 WebLogic Server directory. For example:
    
    WL_HOME="CAS50_home/wlserver_10.3"
  - After WL_HOME, add and export a definition for WLSS_HOME. This variable should point to the Converged Application Server 5.0 WebLogic Server SIP directory. For example:
```
WLSS_HOME="${WL_HOME}/sip"
export WLSS_HOME
```
  - Update the BEA_JAVA_HOME definition to point to the Converged Application Server 5.0 JRockit directory. For example:
    
    BEA_JAVA_HOME="CAS50_home/jrockit_160_17_R28.0.0-677"
  - If you use the Sun JVM, update the SUN_JAVA_HOME definition to point to the Converged Application Server 5.0 Sun JVM directory. For example:
    
    SUN_JAVA_HOME="CAS50_home/jdk_160_18"
  - Update the JAVA_HOME definition to point to the Java directory of the version of Java to use to start WebLogic Server.
  - Look for the following line:
```
. ${WL_HOME}/common/bin/commEnv.sh
```
    Directly before this line, add the following lines:
```
SIP_ENABLED="true"
export SIP_ENABLED
```
  - Locate and delete the following line. (The WlssCommEnv.sh script does not exist in Converged Application Server 5.0):
```
.${WLSS_HOME}/common/bin/wlssCommEnv.sh
```
2. In any script that includes the CLASSPATH definition, update CLASSPATH to remove path information that is no longer required, such as patch file information that applies only to Converged Application Server 4.0.
3. In the startManagedWebLogic.sh script, if the JAVA_OPTIONS entry specifies the -Dweblogic.security.SSL.trustedCAKeyStore option, update the value to use the new Converged Application Server cacerts file path.
On each server machine, update any custom startup scripts to use the new Converged Application Server 5.0 software installation.
If you developed any Beehive applications, upgrade them separately. See the information on upgrading Beehive applications in the discussion on Beehive integration in the BEA WebLogic Server 10.0 documentation.