This chapter describes how to upgrade your existing Oracle Communications ASAP system to ASAP release 7.3. It also includes information about new features, any impact that these new features have with respect to the operation of ASAP, and instructions on how to recover from a failed upgrade.
In this chapter, the ASAP release running on your production or development system is called the old release. The release you are upgrading to is called the new release.
Upgrading to ASAP 7.3 consists of the following process:
Planning the upgrade
Implementing and testing the upgrade on a development test system
Preparing to upgrade a production system
Implementing and testing the upgrade on the production system
The upgrade process includes these tasks:
Updating the Oracle database and client
Updating the WebLogic Server and domain
Updating the ASAP software
Implement new features
For current patch information, see "Patch Requirements." For current release information, see "ASAP System Requirements."
To plan your upgrade, review the following tasks:
Your upgrade team should include the following team members:
A database administrator to manage the database upgrade and tune the database
A system integrator to handle new and existing ASAP customizations
A system administrator to manage the WebLogic Server and ASAP software upgrade
A UNIX administrator to manage accounts, network setup, and IP configurations
You should identify who might be affected by the upgrade. For example:
You might need to give your customer service representatives (CSRs) who send work orders to ASAP advanced notice of any system downtime.
Tell your system administrators in advance about any changes to the system architecture (for example, Oracle database, client, or WebLogic Server upgrades).
Train CSR, cartridge developers, or system integrators on any new ASAP functionality that the upgrade may provide that would have an impact on their role.
Notify Oracle so that Oracle can help you anticipate and avoid problems. Technical support might have additional information about upgrading ASAP or information specific to your implementation.
You might need to make changes to your current system to accommodate additional or modified functionality in the new ASAP release. For example, if the release provides new security functionality, additional system configuration steps may be required.
For more information, see "Upgrade Impacts from ASAP 7.2 or ASAP 7.2.0.x to ASAP 7.3."
This is an important consideration because work order processing might be suspended as a result of upgrading ASAP.
The best way to determine how long the database upgrade will take is to run the upgrade on a test system that contains a duplicate of the data in your production system (see "Creating Test Environments").
In general, it takes longer to upgrade large databases with large tables.
While upgrading ASAP, you must shutdown ASAP and the ASAP WebLogic Server domain. Do not start the upgrade procedure until the status for all work orders indicates Completed and no work order status indicates in Loading, Initial, or in progress.
To minimize service outage while you upgrade, perform the upgrade during off-peak hours.
To test the upgrade process, create a test environment. Use this environment to do the following:
Test the upgrade process and its results.
Compare the default behavior of the old and new ASAP releases.
Determine what customizations you made in the old ASAP release. Any customized ASAP clients and servers (SRP or NEP) or application that provides a programmatic integration with ASAP (using of the APIs described in the Developer's Reference Guide) should be identified.
For more information on creating a test environment from an existing ASAP environment, see "Creating a Test Environment from an Existing Environment."
When testing your upgraded ASAP system, verify that:
The database tables are installed.
The data in database tables is correct.
All IP addresses and ports are correct.
The WebLogic Server starts.
The SARM starts.
The SRP starts.
The NEPs start.
Users and user permissions are correct.
Cartridges are imported correctly.
No changes need to be made to existing cartridges.
No changes need to be made to the SRT.
Work orders are being processed correctly.
NEs are properly provisioned.
When you create a new Oracle Communications ASAP environment, dynamic ASAP data is created automatically. However, if you want to create a new environment that is identical to an existing environment, you must copy the data from the existing ASAP static tables to the new environment.
You may want to create additional identical environments for comparison testing.
If you want to move your static data from one database to another, you must first save the data in a flat file and then load the data into the new database. If the data used for the static tables is already stored within flat files, then simply load the data into the tables. All the static data tables are listed by component following these procedures.
To save tables to files (Oracle):
The ora_dump_sql script copies the table data to a file named TABLE NAME.sql, where TABLE NAME is the name of the table in uppercase characters. If there is more than one table, the script creates a separate file for each one.
In a UNIX operating system, type the command line:
ora_dump_sql [-d|-n|-t] user ID/password [table name]
where [-d|-n|-t] are options that apply to reinserting the data as follows:
d – Deletes and replaces with new rows
t – Truncates table first
n – Inserts new rows, no deletions
user ID and password are your user ID and password for the appropriate component
[table name] is the name of the static table. If you do not specify a table, the script takes all tables for the user and copies them to separate files.
To load data into tables:
In a UNIX, type the command line:
sqlplus user_name/password filename
where:
user_name and password are your user name and password for the appropriate component
filename is the name of the file where the static data is stored
tbl_alarm_center
tbl_appl_proc
tbl_classA_secu
tbl_classB_secu
tbl_code_list
tbl_component
tbl_db_threshold
tbl_event_type
tbl_fs_threshold
tbl_name_value_pair
tbl_system_alarm
tbl_unid
This section explains any important system changes introduced by an upgrade.
New features and new functionality are described in the ASAP Release Notes.
ASAP 7.3 supports Oracle WebLogic Server 12c. To upgrade your WebLogic Server, you must also upgrade your JDK to the version specified in "Software Requirements."
ASAP 7.3 supports Oracle Database Server 12c. You need to upgrade Oracle Database Server to the version specified in "Software Requirements."
ASAP 7.3 supports Oracle Database Client 11g and 12c. You need to install only one version of the client. See "Software Requirements" for more information.
There are no schema changes for various possible upgrades between ASAP 7.2 and ASAP 7.3.
Table 11-1 describes the upgrade methods for ASAP software component upgrade methods.
Table 11-1 ASAP Software Component Upgrade Methods
| Software | Upgrade Method | Description |
|---|---|---|
|
Oracle database |
In-place or out-of-place (during the database installation, using dbua after installing the database, or using the expdp and impdp utilities) |
You can either upgrade your existing ASAP database when you install the new version of the database software, or run Oracle_home/bin/dbua after you have installed the new database software. You can also create a new database and use the expdp or impdp utilities to import the old database into the new one. You may perform an in-place upgrade (into the same Oracle_home) or an out-of-place upgrade (into a separate Oracle_home). You may also upgrade your database from a single instance Oracle Database to an Oracle RAC database. Refer to the Oracle Database Upgrade Guide for recommendations and procedures. In either case, Oracle recommends that you back up your database before the upgrade. For Database backup and restore procedure, please refer to "Creating a Backup of the ASAP Schemas" and "Rolling Back the ASAP Database." |
|
Oracle client |
New installation. |
Install a new version of the Oracle client when you upgrade your database. Download and install the software as described in "Downloading and Installing the Oracle Client Software." |
|
Oracle WebLogic Server |
In-place (using reconfig.sh script) |
Locate the Oracle WebLogic Server software distribution file on the Oracle software delivery website. The WebLogic Server distribution file is located with the ASAP software components. Also download and install the version of Java for the operating system you are using for your WebLogic Server software. See "Software Requirements" for Java version requirements for your platform. Run Middleware_home/oracle_common/common/bin/ reconfig.sh to activate the WebLogic Server Reconfiguration Wizard. |
|
ASAP software |
In-place (using the ASAP installer with the vpd.properties file from the old installation) |
Run the ASAP installer after you have upgraded all other ASAP software components. The ASAP installer will reference the vpd.properties file from the previous installation to upgrade your ASAP software. Download the ASAP installation files as describe in "Downloading the ASAP Installation Files." |
Caution:
Before you start the upgrade procedure, you must backup your WebLogic Server domain, ASAP, and Oracle database (see "Creating a Backup of ASAP, WebLogic Domain, and ASAP Schemas"). The upgrade process for these software components is in-place, meaning the upgrades are applied to the existing software. If the upgrade fails, you must use these backups to roll back your upgrades (see "About Rolling Back ASAP").To upgrade from ASAP 7.2 or ASAP 7.2.0.x to ASAP 7.3:
Ensure that your current ASAP server is running.
Upgrade the Oracle Database and Client to the appropriate release (see Table 11-1).
Caution:
It is very important that you read and follow the Oracle Database Upgrade Guide to ensure that your database instance is successfully upgraded.Open a service request (SR) in My Oracle Support with the Oracle Database team for database upgrade problems.
Log in with the same user ID that you used to install the old version of WebLogic Server.
Download the new versions of ASAP, WebLogic Server, and Java for your platform from the Oracle software delivery website:
See "Software Requirements" for more information.
Unzip the WebLogic Server zip file.
Install the WebLogic Server software.
Upgrade ASAP WebLogic Server domain to the new version.
Note:
For information about performing an upgrade of the WebLogic Server domain, see the Installation Guide for your version of the WebLogic Server documentation.For upgrades of ASAP, Oracle recommends that you run the WebLogic Reconfiguration Wizard on the older WebLogic Server domain to upgrade it to the newer version of WebLogic Server.
For information about the correct JDK required for your WebLogic Server, see "Software Requirements."
Do one of the following in the domain_home/lib directory:
Remove the jconn2.jar file from the directory.
Change the name of the jconn2.jar file to jconn2.jar.bak.
Perform the procedures described in the "Configuring, Backing Up, and Starting WebLogic Before Installing ASAP."
Start the WebLogic Server domain for ASAP.
Note:
During the upgrade, if you receive an error similar to the following example in WebLogic Server Administration Console after the domain restarts, you can ignore this error and proceed with the upgrade.<BEA-149205> <Failed to initialize the application "SRI3.RPCDataSource" due to error weblogic.application.ModuleException: weblogic.common.resourcepool.ResourceSystemException: Cannot load driver class com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource for datasource 'SRI3.RPCDataSource'.
Log in with the same user ID that you used to install the old version of ASAP.
Source ASAP_home/Environment_Profile from the old version of ASAP.
. ./Environment_Profile
Untar the new version of the ASAP software that you downloaded to a folder of your choice.
(Optional) If the WebLogic Server and ASAP are installed on separate machines, do the following:
Export the AWK_CMD variable:
On Solaris and AIX, export the variable with nawk:
export AWK_CMD=nawk
Where the WebLogic Server and domain are installed, run the following script:
./asap730.wl.resource.update.sh
Run the following script:
chmod u+x /asap_utils/asap730.wl.resource.update.sh ./asap_utils/asap730.wl.resource.update.sh
This script performs the following tasks:
Validates the WebLogic Server version
Updates the config.xml, jdbc/, jms/ resource files in the new WebLogic Server domain
Updates the JNDI names from 7.2 or 7.2.0.x to the 7.3 names
Un-deploys the asap$ENV_ID.ear, cartridge_management_ws.ear, SecurityServices.ear, srt$ENV_ID.ear, removing the old 7.2 or 7.2.0.x WebLogic Server content for ASAP.
Note:
Customizations related to these EAR files are not removed by this script. The customizations remains in ASAP 7.3 WebLogic Server domain.Restart the WebLogic Server domain.
Shut down the current ASAP servers.
stop_asap_sys -d
Copy and unzip the InstallShield backup you created when you installed the old version of ASAP into the $HOME directory for your UNIX user account for ASAP.
The installer must pick up all the information collected by the old installation contained in the InstallShield file. Certain install files including the vpd.properties file were created during the old installation and contain information about the components installed in an ASAP environment. The install files are stored under ~/InstallShield/Universal/common/Gen1/_vpddb directory. You must ensure that ASAP 7.3 installer refers to the existing vpd.properties file.
In a terminal new session, do the following:
Log in with the same user ID that you used to install the old version of ASAP.
Using the console, export the following variables:
export ORACLE_HOME=Oracle_client_home
export PATH=$PATH:$ORACLE_HOME/bin
Update the path for the $ORACLE_HOME variable in the ASAP_home/Environment_Profile file in the old version of ASAP.
export ORACLE_HOME=Oracle_client_home
Note:
Do not source the $ASAP_BASE/Environment_Profile file.Export $TNS_ADMIN to the directory where the tnsnames.ora file is located (if required) using the following command:
export TNS_ADMIN=tnsnames_file_directory_location
Run the installer for the new version of ASAP (see "Installing ASAP").
Note:
Some of the steps listed in the GUI installation do not appear when upgrading ASAP.Also, during the upgrade, WebLogic Server may throw the following error message, which can be ignored:
<ERROR> <network.Element> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <Unset routing element :WL_Domain:name=System/UA77/ApplicationType/ServiceActivation/Application/1-0; 7-3;ASAP/Comp/routingElement/TORONTO-,type=routingElement> javax.management.InstanceNotFoundException: WL_Domain:name=System/UA77/ApplicationType/ServiceActivation/Application/1-0;7-3;ASAP/Comp/routingElement/TORONTO-,type=routingElement
Open ASAP_home/Environment_Profile and update the following environment variables:
Update export DSQUERY="Oracle_SID" Update exportVERSION="\\\"Build_Number\\\""
where Oracle_SID is the SID for the Oracle Database, and Build_number is the ASAP software build number.
Re-install the SRT components (if required) after ASAP installs. See Service Request Translator User's Guide for more information.
Note:
If you are using different databases that are running on different hosts, you must do the following:Update the DB_CONNECT details in the ASAP.Properties file after you have completed the upgrade procedure.
If these databases have different SIDs, update the DSQUERY value in the Environment_Profile.
Update the database details in WebLogic Server, in the connection pool URL for the following data sources: SARMDataSource, ADMDataSource, NEPDataSource, CTRLDataSource, and SRPDataSource. For more information about changing these details, see WebLogic Server documentation.
The following sections describe additional upgrade procedures required if you are upgrading from a single Oracle database instance to an Oracle RAC database instance.
To upgrade the Oracle Database and ASAP Servers:
Upgrade the single instance database (see Table 11-1).
Upgrade ASAP as described in "Upgrading from ASAP 7.2 or ASAP 7.2.0.x to ASAP 7.3."
Stop ASAP.
Migrate the upgraded single instance database to an Oracle RAC database. For instructions, see the Oracle Database documentation.
After upgrading ASAP and migrating the ASAP Oracle database content to an Oracle RAC database, you must delete the original WebLogic data sources that connected to the single database instance and create new WebLogic data sources as listed in Table 11-2. Each Oracle RAC database requires a single generic data source that are both members of a common multi data source.
Table 11-2 ASAP Data Source Migration
| Original Data Source Name and JNDI Name | New Data Source Name and JNDI Name |
|---|---|
|
envid.ADMDataSource System.envid.ApplicationType.ServiceActivation. |
Generic data sources:
Multi Data Source: envid.ADMDataSourcenew System.envid.ApplicationType.ServiceActivation.Application.1-0;7-3;ASAP.Comp.ADMDataSource |
|
envid.CTRLDataSource System.envid.ApplicationType.ServiceActivation. |
Generic data sources:
Multi Data Source: envid.CTRLDataSource System.envid.ApplicationType.ServiceActivation. |
|
envid.NEPDataSource System.envid.ApplicationType.ServiceActivation. |
Generic data sources:
Multi Data Source: envid.NEPDataSource System.envid.ApplicationType.ServiceActivation. |
|
envid.SARMDataSource System.envid.ApplicationType.ServiceActivation. |
Generic data sources:
Multi data source: envid.SARMDataSource System.envid.ApplicationType.ServiceActivation. |
|
envid.SRPDataSource System.envid.ApplicationType.ServiceActivation. |
Generic data sources:
Multi data source: envid.SRPDataSource System.envid.ApplicationType.ServiceActivation. |
Table 11-3 Additional Settings for Generic Data Sources
| Field | Tab | ADM Data Source Value | SARM/NEP/SRP/CTRL Data Source Value |
|---|---|---|---|
|
Row Prefetch Enabled |
General |
Enabled |
Enabled |
|
Row Prefetch Size |
General |
200 |
200 |
|
Driver Class Name |
Connection Pool |
oracle.jdbc.driver.OracleDriver |
oracle.jdbc.driver.OracleDriver |
|
Initial Capacity |
Connection Pool |
1 |
3 |
|
Maximum Capacity |
Connection Pool |
5 |
25 |
|
Capacity Increment |
Connection Pool |
1 |
3 |
|
Test Connections On Reserve |
Connection Pool |
Enabled |
Enabled |
|
Test Frequency |
Connection Pool |
0 |
0 |
|
Shrink Frequency |
Connection Pool |
0 |
0 |
|
Remove Infected Connections Enabled |
Connection Pool |
Disabled |
Disabled |
To create new generic and multi data sources to an Oracle RAC database:
Log into the WebLogic Server.
The WebLogic Server Administration Console appears.
Click Deployments.
Select all Deployments
Click Stop.
Click Force Stop Now.
Expand Services.
Click Database Sources.
Select all the original data sources listed in Table 11-2 except for the Admin data source. Do not select the RPC data source.
Click Delete.
You must create a generic data source for each Oracle RAC database. Click New.
Click Generic Data Source.
The Create a New JDBC Data Source screen appears.
In the Name field, add the first new data source name listed in Table 11-2. For example, envid.ADMDataSource-1.
In the JNDI Name field, add the first new JNDI name listed in Table 11-2. For example, System.envid.ApplicationType.ServiceActivation.Application.1-0;7-3;ASAP.Comp.ADMDataSource-1.
From the Database Type list, select Oracle.
Click Next.
From Database Drive list, select Oracle Driver for RAC Service-Instance connections; Version 10: and later.
Click Next.
Click Next.
Do the following:
In the Service Name field, enter the service name of the Oracle RAC database you want this data source to connect to.
In the Database Name field, enter the database name for the Oracle RAC database you want this data source to connect to.
In the Hostname field, enter the host name for the Oracle RAC database you want this data source to connect to.
in the Port field, enter the port number for the Oracle RAC database you want this data source to connect to.
Enter the Database User Name for the Schema you want to create a data source for.
Enter the Password for the ASAP schema you want to create a data source for.
Confirm the Password for the ASAP schema you want to create a data source for.
Click Next.
Edit the URL field as follows:
jdbc:oracle:thin:@//ip_address:port/service_name
where ip_address, port, and service_name are the IP address, port number, and service name for an Oracle RAC database.
Click Test Configuration.
Do the following:
If the test succeed, click Next.
If the test did not succeed, review the steps in this procedure and check for configuration errors.
In the Select Targets section, select Admin if ASAP is installed in a single Admin server or Managed Server if ASAP is installed with an Admin server and a managed server.
Click Finish.
Select the created data source.
On the Transaction tab, deselect the Supports Global Transactions check box.
Click Save.
Repeat steps 6 to 28 for the second new data source name listed in Table 11-2. For example, envid.ADMDataSource-2 System.envid.ApplicationType.ServiceActivation.Application.1-0;7-3;ASAP.Comp.ADMDataSource-2.
You must create a multi data source for Oracle RAC that references these two data sources. Click New.
Click Multi Data Source.
In the Name field, enter the multi data source name listed in Table 11-2.
In the JNDI Name field, enter the multi data source JNDI name listed in Table 11-2.
From the Algorithm Type list, select Failover.
Click Next.
In the Select Targets section, select Admin if ASAP is installed in a single Admin server or Managed Server if ASAP is installed with an Admin server and a managed server. The target server should be the same one used for the original data sources.
Click Next.
Click Next.
From the Data Source Available section, select the two generic data sources that correspond to the multi data source node you are creating.
Click the right arrow to choose them.
Click Finish.
Repeat steps 6 to 41 for all remaining generic and multi data sources listed in Table 11-2.
Update the newly created generic data source values using the values shown in Table 11-3.
Click Services.
Click Persistent Stores.
Click envid.JMSJDBCStore.
In the Target list, do one of the following:
Select AdminServer if ASAP is installed on a single administration server.
Select ManagedServer if ASAP is installed on an administration server with one or more managed servers.
In the Data Source field, select the new multi data source for the Admin server. This step only applies to the Admin Server. All other servers used JDBC. The target server should be the same one used for the original data sources.
Click Save.
Click Database Sources.
Select the old Admin data source.
Click Delete.
Restart the WebLogic server.
Log into the WebLogic server.
The WebLogic Server Administration Console appears.
Click Deployments.
Select all Deployments
Click Start.
Select Service All Requests.
To configure the ASAP environment for the Oracle RAC database:
From the ASAP environment, source the ASAP_home/Environment_Profile.
Open the Environment_Profile with a text editor.
Search for DSQUERY.
Change the value for DSQUERY to the new Oracle RAC database service name.
Save the Environment_Profile.
Open ASAP_home/ASAP.properties with a text editor.
Change the values for DB_CONNECT to the new Oracle RAC database tnsnames.ora DB_CONNECT values.
Add the RACDB_CONNECT_STR parameter and set it to the Oracle RAC database connection string. This connection string repeats the IP addresses and port numbers for the Oracle RAC databases listed in the tnsnames.ora file in a different format. For example:
RACDB_CONNECT_STR=host1:port:servicename,host2:port:servicename
Where host1 and host2 are the name or IP address of your Oracle RAC databases, port is the port number for the Oracle RAC databases, and servicename is the service name for the Oracle RAC databases.
Restart ASAP.
To upgrade ASAP server stored procedures:
Change to the $ASAP_BASE/isql directory for the new version of ASAP:
cd $ASAP_BASE/isql
Run the following commands to upgrade the stored procedures:
sqlplus $SARM_USER/sarm_db_password < sarm_procs.sql sqlplus $SARM_USER/sarm_db_password < oca_sarm_procs.sql sqlplus $CTRL_USER/control_db_password < control_procs.sql sqlplus $ADM_USER/admin_db_password < admin_procs.sql sqlplus $ADM_USER/admin_db_password < aims_procs.sql sqlplus $ADM_USER/admin_db_password < oca_admin_procs.sql sqlplus $SRP_USER/srp_db_password < srp_emul_procs.sql sqlplus $NEP_USER/nep_db_password < asc_nep_procs.sql
Check the upgraded database object status as follows:
$ASAP_BASE/db_migration/oracle_from_asap_ver_to_asap_versionL /scripts/check_db_obj_status.ksh
The status of all database objects should be VALID. For example:
$ASAP_BASE/db_migration/oracle_from_asap_ver_to_asap_versionL /scripts/check_db_obj_status.ksh -U $SRP_USER -P srp_db_password
You can roll back to a previous version of ASAP by using the backup files that you created after you installed ASAP or before you started an upgrade (see "Creating a Backup of ASAP, WebLogic Domain, and ASAP Schemas").
If you are restoring a backup created on one machine to a different machine, ensure the following:
The new machine name must be identical to the old machine name.
The new user accounts and permissions should be identical to the old user accounts and permissions.
The IP addresses for the new box must be updated in the ASAP environment, WebLogic Server domain, and ASAP database servers.
Ensure that you have installed the zip and unzip utility before you start the roll back procedures for the ASAP environment and WebLogic Server Domain.
The Oracle Database Server provides the impdp and expdp utilities to import and export database schemas.
To roll back the ASAP environment, use the following procedure.
From the directory that contains the old ASAP_home folder, use the unzip utility to unzip an ASAP backup file.
unzip ASAP720_BACKUP.zip
To roll back the WebLogic Server domain, use the following procedure:
From the directory that contains the old domain_home folder, use the unzip utility to unzip a WebLogic Server domain backup file.
unzip WLDOMAIN_BACKUP.zip
To roll back the ASAP Database, use the following procedure:
Source the ASAP Environment_Profile in the ASAP_home folder (where ASAP_home is the location of your ASAP server installation directory).
. ./Environment_Profile
Drop all database users, if you are importing your database back into an environment where those users were already created.
Log into your database using /as sysdba for the user-name.
Enter the following commands to drop the ASAP users:
drop user admenvid cascade; drop user sarmenvid cascade; drop user ctrlenvid cascade; drop user nepenvid cascade; drop user srpenvid cascade;
Where envid is the environment ID for your ASAP instance.
Log out of your database.
exit
Use the following command to restore the backup file for the Control, Admin, SARM, NEP, and SRP servers. Where password is the database system admin password and filename is the name that you gave your DMP file when you created the backup (see "Creating a Backup of the ASAP Schemas").
impdp system/password SCHEMAS=$CTRL_USER,$SARM_USER,$ADM_USER,$NEP_USER,$SRP_USER DUMPFILE=filename.dmp