This chapter provides instructions for upgrading to Oracle Communications Evolved Communications Application Server (OCECAS) from an earlier version.
Follow the instructions in this section to upgrade from OCECAS 7.0 to 7.1. You need to collect this information beforehand:
The database user passwords for users that own database tables.
The username and password for the runtime domain, administrator, administration domain, and SDC management domain.
The management domain location.
This task includes running scripts to replace each of the domains and start their node managers.
To Upgrade OCECAS from 7.0 to 7.1
Install OCECAS 7.1 on every machine that it was previously installed on.
See "Installing OCECAS" for details.
If your OCECAS system runs the database, runtime domain, managed server domain, administration server domain, or SDC management domain on a different machine, copy the scripts directory to each of those systems with these commands:
$ cd Middleware_home/wlserver/csp/installation/ $ tar -czvf /tmp/scripts.tgz scripts $ scp /tmp/scripts.tgz user@machine:/tmp
Where Middleware_home is the name of the directory where you installed OCECAS (also known as the OCECAS home directory), and machine is the name of the system running the database or domain, and user is the user name of the user to access the system.
Make sure the path Middleware_home/wlserver/csp/installation is available on each system. If it is not, create it using the following command:
mkdir -p Middleware_home/wlserver/csp/installation
Extract scripts into this location using this command:
tar -xvf /tmp/scripts.tgz -C Middleware_home/wlserver/csp/installation/
On the system running the database, run the database upgrade script:
$ cd Middleware_home/wlserver/csp/installation/scripts
$ ./upgrade-mgmt-db.sh
you are prompted for passwords for the database table owners
On each system running the runtime domain, run the runtime update script:
$ cd Middleware_home/wlserver/csp/installation/scripts
$ ./upgrade-runtime-domain.sh
you are prompted for the administrative username and password
On each system that runs the runtime domain, run the runtime domain startup script:
$ cd Middleware_home/wlserver/csp/installation/scripts
$ ./start-runtime-domain.sh
you are prompted for the administrative user and password
On each system running the managed server, run the managed server upgrade script:
$ cd Middleware_home/wlserver/csp/installation/scripts $ ./upgrade-mgmt-server.sh you are prompted for the management domain path
On the system running the Administration server for the SDC management domain, run the SDC configuration script:
$ cd Middleware_home/wlserver/csp/installation/scripts $ ./upgrade-sdc-admin-server.sh you are prompted for the admin user and password.
This script restarts the Administration server and management server so that the new changes take effect.
After running the upgrade scripts, return to the Oracle Installer UI, untick the domain configuration checkbox and click Finish.
This section lists items you need to check or change after upgrading.
The 7.1 version of OCECAS requires that you use secure socket layer-compliant ports to communicate between the Session Design Center and the managed server that deploys it. Using SSL between OCECAS servers is a good general security practice. See ”About OCECAS Security” in Oracle Communications Evolved Application Server Security Guide for information.
All changes to OCECAS are visible in the Session Design Center in the OCECAS change set.
In many cases where you altered a default control flow, it fails to compile after the upgrade. In this case, click the pencil icon for each control flow and confirm that your previous changes appear as being removed. You have these options:
To revert to your last version of the control flow, simply click the revert button on each control flow. This overwrites the updated version of the control flow
Manually merge your version with the new version. Make a copy of the new change set, revert the original to your last version and manually merge the two.