| Oracle® Communications ASAP Installation Guide Release 7.2 E18878-04 |
|
 Previous |
 Next |
This chapter provides instructions for Oracle Communications ASAP post-installation tasks.
To configure the asap_home/conf/ASAP.cfg file (where ASAP_home is the location of your ASAP server installation directory) to take advantage of the Oracle real application cluster (RAC) system functionality and transparent application failover (TAF), use the following procedure:
Using a text editor, open the ASAP.cfg file in the ASAP_home/config/ directory.
Configure the entries in ASAP.cfg listed in Table 9-1.
Table 9-1 ASAP.cfg Entries
| Entry | Description |
|---|---|
|
DB_RETRY_NUMBER |
Specify the number of times you want ASAP to retry the connection when the connection to the database fails. For example, |
|
DB_RETRY_INTERVAL |
Specify the interval (in seconds) between attempts for establishing the connection. For example, |
The following are reliability related configuration parameters in the ASAP.cfg file:
# ASAP Availability Enhancement Parameters DB_RETRY_NUMBER = 5 # Manual Retry count on loss of DB Connection DB_RETRY_INTERVAL = 1 # Sleep period between each manual retry on loss of DB connection USE_OCI_EVENTS = 1 # Activates OCI_EVENTS on OCI Environment
For information about troubleshooting ASAP, see the ASAP System Administrator's Guide.
This section describes the following procedures related to installing and testing a cartridge:
To download the a cartridge:
Go to the My Oracle Support Web site:
On your workstation, create a repository directory with a name of your choice.
Download the cartridge to a temporary directory.
Extract the TAR file.
tar xvf TAR_file.tar
The directory structure should look like the following:
repository_directory /README.txt /installCartridge /uninstallCartridge /SAR_file.sar
This is the minimum required structure. You can enhance this directory structure with additional directories.
There are two ways of installing a cartridge:
Before installing a cartridge, ensure that ASAP is running.
To start ASAP:
Start ASAP:
start_asap_sys -d
Verify that the WebLogic instance for this ASAP environment is running.
The ASAP System Administrator's Guide contains more information on starting the ASAP server, the ASAP Daemon, and the WebLogic Server.
The installCartridge script executes the following tasks:
Configures the cartridge-specific NE using the Service Activation Configuration Tool (SACT).
Deploys the cartridge service model (only if the cartridge service model is not yet deployed) using the Service Activation Deployment Tool (SADT).
Copies the cartridge-specific JAR files to the ASAP environment.
Using the PostDeploySarFile script:
Searches for and invokes the SarPatch script inside a SAR file.
Searches for and populates all SQL files whose name has no undeploy_ prefix.
Searches for all .tst work order files and load the work order defined in them.
For information about the SACT refer to the ASAP Server Configuration Guide. For more information about SADT and the PostDeploySarFile, refer to the ASAP Cartridge Development Guide.
|
Note: Before deploying an XML file for the first time, ensure that the ASAP_home/SYBASE/interface file exists. |
To install the cartridge:
Run the ASAP_home/samples/DIT/scripts/installCartridge script.
installCartridge SAR_file.sar
Where SAR_file is the name of your SAR file.
The script prompts you for the values of the following WebLogic login parameters:
WebLogic Hostname
WebLogic HTTP Port
WebLogic Login User ID
WebLogic Login Password
The script loads the NEP-NE configuration and the CSDL-ASDL configuration to the SARM database, and loads sample work orders to the SRP database. The script also copies the cartridge-specific jar files to the ASAP environment.
Add ${ASAP_BASE}/lib/studio_2_6_0.jar to the CLASSPATH in the JInterpreter file under $ASAP_BASE/programs directory.
Restart ASAP to upload the cartridge configuration into ASAP.
Ensure ASAP and WebLogic Server are started and running. For more information on using Design Studio with ASAP, see Design Studio Help for ASAP.
To install a cartridge using Design Studio:
From the File menu, select Import, then select Activation Archive (SAR) under Studio Wizards to import the SAR file. Browse for the path of the SAR file and click Finish.
Create a new Service Activation Project.
Define a new NE Entity based on the NE Template contained in the cartridge provided by Oracle.
Ensure that the primary pool of the newly created NE is different from the NE template primary pool. You can modify it, if necessary.
Ensure that the test work order provided with the cartridge targets the newly defined NE. If not, then modify the test work orders file(s).
Create a new Activation Environment Project from the Studio menu. See Studio documentation for more information.
Create Activation Environment inside the Activation Environment Project and configure the Connection Details tab with your Environment ID, Activation version, and WebLogic data.
Connect to your environment using the Connect button.
Select the Cartridge tab of the Activation Environment and click Add to add your projects to the environment. The cartridge and the newly created Service Activation should appear in the Cartridges list.
Deploy the NetworkActivation (NA) cartridge provided by Oracle. (No NE information is to be deployed with this cartridge, therefore it is not necessary to deploy the NEP map info).
Deploy the Service Activation (SA) project as follows:
On the Cartridge tab, select the necessary SA cartridge and click Deploy.
Select the NEP Map tab of the Activation Environment. Select the required NEP server from Network Element Processors. See Studio documentation for more information.
Select the SA cartridge from the Network Element Processor Map and click Deploy.
Verify the SADT console to confirm the installation.
Go to ASAP environment.
Add ${ASAP_BASE}/lib/studio_2_6_0.jar to the CLASSPATH in the JInterpreter file under $ASAP_BASE/programs directory.
Restart ASAP in order to start working with the cartridge.
To install an ASAP cartridge to an ASAP environment that has been distributed over several UNIX machines:
Install the cartridge to the master ASAP environment as described in "Installing a Cartridge Using Scripts" or "Installing a Cartridge Using Studio".
Archive the following files and folders:
ASAP_home/Environment_Profile
ASAP_home/config/ASAP.cfg
ASAP_home/SYBASE/interfaces
ASAP_home/lib/
ASAP_home/install/cwallet.sso
ASAP_home/ASAP.properties
ASAP_home/programs/JInterpreter
For example:
zip -r Masterfile.zip Environment_Profile config/ASAP.cfg SYBASE/interfaces lib/ install/cwallet.sso ASAP.properties programs/JInterpreter
Copy the archive to the ASAP_home directory in your slave environment, using FTP for example.
From the slave ASAP environment extract the archive.
unzip Masterfile.zip replace config/ASAP.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: A
This procedure assumes that you have set up a remote NEP server to act as a backup in the event that he local NEP server fails.
To redirect work orders to the remote backup NEP server:
Install ASAP with a distributed remote NEP server as described in "Installing ASAP Across Multiple UNIX Machines".
Create a cartridge that is mapped to the local NEP.
Deploy the cartridge to the master environment and the slave environment as described in "Installing a Cartridge to a Distributed ASAP Environment". In this scenario, after deploying the cartridge, the remote NEP does not need to be running.
Create an SACT XML file that you can use to remap the work order from the local NEP server to the remote NEP server. For example:
<element name="MSLV-TELNET-HOST">
<vendor>MSLV</vendor>
<technology>TELNET</technology>
<softwareLoad>1-0</softwareLoad>
<nepServerName>NEP_Server</nepServerName>
<primaryPool>MSLVPOOL</primaryPool>
<maximumConnections>10</maximumConnections>
<dropTimeout>2</dropTimeout>
<spawnThreshold>4</spawnThreshold>
<killThreshold>2</killThreshold>
<routingElement name="MSLV-TELNET-HOST">
<atomicService/>
</routingElement>
Where NEP_Server can is the name of the remote backup NEP server.
If the local NEP server fails, run SACT with the NEP backup server XML file to update the SARM database with the new routing information.
Restart the ASAP server.
stop_asap_sys -d start_asap_sys -d
When the local NEP server become available again, repeat steps 4 to 6 using the NEP_Server name of the local NEP server.
Certain install files are created during installation and contains information about which components were installed into an ASAP environment. They are stored under $HOME/InstallShield/... and are referred to by the installer when the ASAP environment is subsequently upgraded.
You should backup of the $HOME/InstallShield/directory for each ASAP installation you perform. Ensure that you are able to identify which ASAP version and EFix number the backed updirectory is associated with.
Note that the $HOME/InstallShield/ directory can be overwritten by a subsequent install if:
You have more than one ASAP environment installed on one machine
These installations share the same $HOME location
The $HOME location is different than the $ASAP_BASE location
Perform the following tasks if you are using Oracle Database 11g with NLS_CHARACTERSET WE8ISO8859P15.
To enable ASAP to function with the NLS_CHARACTERSET WE8ISO8859P15
After you install the ASAP server software, you must copy the Oracle 11g version of orai18n.jar from WLS_home/Oracle/Middleware/wlserver_10.3/server/ext/jdbc/oracle/11g to ASAP_home/JLIB.
ASAP_home is the location of your ASAP server installation directory, and WLS_home is the directory containing the WebLogic Server software.
Add WLS_home/Oracle/Middleware/wlserver_10.3/server/ext/jdbc/oracle/11g/orai18n.jar to the CLASSPATH for WebLogic Server
Add PRE_CLASSPATH in WLS_domain_home/bin/setDomainEnv.sh.
WLS_domain_home is the directory containing your WebLogic Server domain.
Clear the PRE_CLASSPATH in case an application template wants to set it before the larger PRE_CLASSPATH is invoked as shown below:
PRE_CLASSPATH="" export PRE_CLASSPATH PRE_CLASSPATH="$WL_HOME/Oracle/Middleware/wlserver_10.3/server/ext/jdbc/oracle/11g/orai18n.jar" export PRE_CLASSPATH
After installing or before upgrading ASAP, create a backup of the ASAP environment, WebLogic domain, and ASAP schemas. These backups can be used to recover from system or upgrade failures.
Ensure that you have installed the zip and unzip utility (or a similar utility such as tar) before you start the backup procedures.
The Oracle database server provides the impdp and expdp utilities to import and export database schemas.
|
Note: While backing up ASAP, you must shutdown ASAP and the ASAP WebLogic domain. Do not start these backup procedures until the status for all work orders indicate Completed, Cancelled, or Failed, and no work order status indicates in Loading, Initial, or in progress. The Oracle database server must be running.To minimize service outage while you upgrade, perform the backup during off-peak hours. |
To create a backup of the ASAP environment, use the following procedure:
Source the ASAP_home/Environment_Profile.
. ./Environment_Profile
Shut down ASAP.
stop_asap_sys -d
From the directory that contains ASAP_home, use the zip utility to generate an ASAP backup file:
zip -r ASAP720_BACKUP.zip ASAP_home
Store the backup file in a safe location.
To create a backup of the WebLogic Server:
Shutdown the WebLogic Server using the Domain_home/bin/stopWeblogic.sh script or from the WebLogic GUI.
./stopWeblogic.sh
From the directory that contains the Domain_home folder, use the zip utility to generate an WebLogic Domain backup file.
zip -r WLDOMAIN_BACKUP.zip WeblogicDomain
|
Note: It is also good practice to backup the WebLogic Server software located at BEA_home. |
Store the backup file in a safe location.
To create a backup of the ASAP Database:
Ensure that your database is running.
Source the ASAP Environment_Profile in the ASAP_home folder.
. ./Environment_Profile
Use the following command to generate a backup file for the Control, Admin, SARM, NEP, and SRP servers, where password is the database system admin password and filename is the name you want to give your DMP file.
expdp system/password SCHEMAS=$CTRL_USER,$SARM_USER,$ADM_USER,$NEP_USER,$SRP_USER DUMPFILE=filename.dmp
|
Note: You can find the location for the DMP file at the end of the output from this command. For example:
Dump file set for SYSTEM.SYS_EXPORT_SCHEMA_01 is:
/path/dpdump/filename.dmp
Where path is the path to the dpdump directory. If the database is co-resident with ASAP, you must log in with a database user account to access the file. If the database is on a different UNIX machine, you must log into the UNIX machine with a database user account to access the file. |
|
 Copyright © 2005, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|