10 Upgrading WebLogic SIP Server 3.x to Converged Application Server 4.0

This chapter describes the steps for upgrading WebLogic SIP Server version 3.0 or 3.1 to Oracle Communications Converged Application Server version 4.0.

Note:

If you are using WebLogic SIP Server version 2.2, first follow the instructions in Upgrading a WebLogic SIP Server 2.2 Configuration to Version 3.1 in the WebLogic SIP Server 3.1 documentation. Then use the instructions in the following sections to upgrade to Converged Application Server 4.0.

• About the Upgrade Process

• Step 1: Install Software and Prepare Domain

• Step 2: Upgrade Version 3.x Domain Artifacts

About the Upgrade Process

Upgrading a WebLogic SIP Server 3.x domain to a Converged Application Server 4.0 domain involves these basic steps:

• Manually editing the config.xml file to specify the custom resources required by Converged Application Server 4.0.

• Manually upgrading WebLogic SIP Server configuration files (sipserver.xml and diameter.xml) and resources to use the new Converged Application Server 4.0 schemas.

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

Step 1: Install Software and Prepare Domain

Begin by installing the Converged Application Server 4.0 software into a new Oracle home directory on your Administration Server machine. See the 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 WebLogic SIP Server 3.x installation to complete the upgrade.

In the next section, you will upgrade the existing domain configuration and domain scripts to function with Oracle WebLogic Server 10g release 3, upon which Converged Application Server is based. Before doing so, prepare the WebLogic SIP Server 3.x domain by doing the following:

1. Review Compatibility with Previous Releases in the Oracle WebLogic Server 10g release 3 documentation to determine whether any feature affects the non-SIP components of your applications. Make any necessary changes before upgrading.

2. Read the discussion on porting existing applications to Converged Application Server in Developing SIP Applications in the Converged Application Server 4.0 documentation to determine whether any feature affects the SIP components of your applications. Make any necessary changes before upgrading.

3. Shut down all Managed Servers in your domain (engine and SIP data tier servers), leaving only the Administration Server running.

4. 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.

5. Shut down the Administration Server.

Step 2: Upgrade Version 3.x Domain Artifacts

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

1. Update all script files in the /bin subdirectory of the 3.x domain directory to point to the Converged Application Server 4.0 installation. Specifically:

   1. In the setDomainEnv.sh script, look for the following line:

      . ${WL_HOME}/common/bin/commEnv.sh
      

      Directly after this line, add the following lines to define the new WLSS_HOME environment variable required in Converged Application Server 4.0:

      WLSS_HOME="path_to_cas_home"
      export WLSS_HOME
      . ${WLSS_HOME}/common/bin/wlssCommEnv.sh
      

      Replace path_to_cas_home with the path to which you installed the Converged Application Server 4.0 software (for example, ~/bea/wlcserver_10.3).

   2. Set BEA_JAVA_HOME, JAVA_HOME, and WL_HOME to variables to point to appropriate Converged Application Server 4.0 installed directories. Note that in Converged Application Server 4.0, WL_HOME and WLSS_HOME define two different directories (for example, ~/bea/wlserver_10.3 and ~/bea/wlcserver_10.3).

   3. If you use the Sun JVM, update SUN_JAVA_HOME to use the Sun JVM installed with Converged Application Server 4.0.

   4. Update the CLASSPATH definition in any script that includes it, to remove path information that is no longer required, such as patch file information that applies only to WebLogic SIP Server 3.x.

   5. If the JAVA_OPTIONS entry specifies the -Dweblogic.security.SSL.trustedCAKeyStore option, update the value to use the new Converged Application Server 4.0 cacerts file path.

2. On each server machine, update any custom startup scripts to use the new Converged Application Server 4.0 software installation.

3. 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. Be aware that WebLogic SIP Server 3.x was based on WebLogic Server version 9.2, while Converged Application Server 4.0 is based on Oracle WebLogic Server 10g release 3.