Configuration Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Upgrading WebLogic SIP Server 3.x to Oracle Communications Converged Application Server

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 version 3.1 documentation. The use the instructions in the following sections to upgrade to Oracle Communications Converged Application Server.

The following sections provide instructions for upgrading WebLogic SIP Server version 3.0 or 3.1 to Oracle Communications Converged Application Server:

 

About the Upgrade Process

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

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 Oracle Communications Converged Application Server software into a new BEA home directory on your Administration Server machine. You will need the new software installation as well as the domain directory for your existing WebLogic SIP Server 3.x installation to complete the upgrade. See the Installation Guide for instructions.

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 Oracle Communications 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. Review Porting Existing Applications to Oracle Communications Converged Application Server in Developing SIP Applications 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 on page A-2, 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 Oracle Communications Converged Application Server installation. Specifically:
    1. In the setDomainEnv.sh script, look for the following line:
      2. . ${WL_HOME}/common/bin/commEnv.sh

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

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

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

    2. Set BEA_JAVA_HOME, JAVA_HOME, and WL_HOME to the new values. Note that in Oracle Communications Converged Application Server version 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 Oracle Communications Converged Application Server version 4.0.
    4. Update the CLASSPATH definition in any script 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 Oracle Communications Converged Application Server cacerts file path.
  2. On each server machine, update any custom startup scripts to use the new Oracle Communications Converged Application Server software installation.
  3. If you developed any Beehive applications, upgrade them separately as described in Upgrade Paths in Beehive Integration in BEA WebLogic Server. Keep in mind that WebLogic SIP Server 3.x was based on WebLogic Server version 9.2, while Oracle Communications Converged Application Server is based on Oracle WebLogic Server 10g Release 3.

  Back to Top       Previous  Next