10 Verifying the ASAP Installation
This chapter describes how to verify that Oracle Communications ASAP is installed correctly.
Checking the State of all Installed Components
You can verify that ASAP is installed by checking the state of all installed components.
To check the state of all installed components:
-
Log in to the WebLogic Server Administration Console.
-
In the left panel, in the Domain Structure section, click Deployments.
The Summary of Deployments page appears.
-
Ensure that the managed server is running.
-
If ASAP is installed successfully, the following deployments appear in the Active state:
-
asapenvid (where envid is the environment ID for the ASAP instance)
-
cartridge_management_ws
-
SecurityServices
-
Testing the ASAP Server Installation
The ASAP Server installation provides a Demonstration Service Activation Model named POTS Service Activation Model cartridge. You can use the sample model to test the ASAP installation.
To test the ASAP Server installation, start ASAP and send sample work orders to the sample activation cartridge.
It is also recommended that you restart the WebLogic Server before testing the ASAP installation.
To test the installation:
-
From ASAP_home, source the Environment_Profile file:
. ./Environment_Profile
-
(Optional) Set the TNS_ADMIN variable to the location of your tnsname.ora. This step is only required if the Oracle_home/network/admin/tnsnames.ora file does not contain the ASAP database information.
-
Start ASAP using the following command:
start_asap_sys -d
-
From the UNIX prompt, enter:
status
A list of the ASAP servers that are running is displayed.
-
Locate the appropriate executable and enter it at the UNIX command prompt.
Refer to the README file for Nortel_DMS_POTS.sar cartridge for instructions on running ASAP.
The sample model POTS Service Activation Model is installed at $ASAP_BASE/samples/sadt/DemoInstall/Nortel/DMS/POTS/.
-
Run the following commands to install the sample cartridge:
asapd -start -d -host DAEMON_HOST -port DAEMON_PORT installCartridge $ASAP_BASE/activationModels/Nortel_DMS_POTS.sar
-
To verify that work orders are executing, enter asap_utils.
-
When prompted, enter the password to the control server.
-
When prompted, enter 1 to view the service requests in the SARM database. The WO_STAT column displays the status of the work orders.
The expected results when running in loopback mode are listed below. (If not in loopback mode, the results vary depending upon your specific configuration.)
-
Success (104)
-
Failure (253)
-
In Progress (103)
-
Note:
If ASAP fails to start, check if the sample cartridge is installed properly and check the logs for more information.Testing a Cartridge Installation
To test a cartridge installation, you need to know about the network element, services, and basic activation configuration. You may need to perform adjustments to provision a service for a specific NE, network, or connectivity configuration.
You can test the cartridge installation using one of the following methods:
-
Loopback Mode: Does not actually connect to or send commands to the NE.
-
Live Mode: Connects to and sends commands to a live NE.
Configuring Loopback and Live Mode Parameters
Set the following variables to test the cartridge in loopback or live testing modes.
Loopback Mode:
Set the parameter listed in Table 10-1 to test the cartridge in loopback mode.
Table 10-1 Loopback Mode Parameter Settings
Configuration Variable | Parameter Settings | Location |
---|---|---|
LOOPBACK_ON |
1 (default setting) |
ASAP_home/config/ASAP.cfg |
Live Mode:
Set the parameter listed in Table 10-2 to test the cartridge in live mode.
Table 10-2 Live Mode Parameter Settings
Configuration Variable | Parameter Settings | Location |
---|---|---|
LOOPBACK_ON |
0 |
ASAP_home/config/ASAP.cfg |
Mapping the NE_Cartridge_name_HOST.xml file to NEP Servers
To modify the NE_Cartridge_name_HOST.xml file:
-
Create a new source directory with a name of your choice.
mkdir New_source_directory
-
Copy SAR_file.sar to this new source directory.
cp SAR_file.sar ./New_source_directory
-
Change directory to New_source_directory.
cd New_source_directory
-
Un-jar SAR_file.sar. This extracts the contents of the sar file.
jar xvf SAR_file.sar
-
Edit New_source_directory/NE_Cartridge_name_HOST.xml to map the file to the NEP servers.
-
Create a new sar file at the New_source_directory level.
CreateSar $PWD
-
Uninstall the cartridge using SAR_file.sar.
-
After you uninstall the cartridge, rename the sar file, so you have a backup copy.
-
Copy the new sar file from New_source_directory.
-
Reinstall the cartridge.
Testing the Installation
The following procedure describes the steps required to test the cartridge installation in loopback mode. We recommend that you perform the initial cartridge installation test in loopback mode.
To test the cartridge installation in loopback mode:
-
Stop ASAP by entering the following command at the UNIX prompt:
stop_asap_sys -d
-
Ensure loopback mode is on. See "Configuring Loopback and Live Mode Parameters" for a description of how to set the loopback parameter to On.
-
Start ASAP by entering:
start_asap_sys -d
-
Send the sample work orders using the JMS client. See "Sticky and Non-Sticky Requests Supported by Order Balancer"ASAP System Administrator's guide for more information.
-
Verify the status of the sample work orders by entering:
asap_utils -d l
All successful work orders return to 104 state.
To view the sample work orders provided with the cartridge, refer to the cartridge source.
Viewing the Sample Work Orders
You find the sample work orders under the sample_wo directory in the SAR file. The following procedure describes how to view the sample work orders.
To view the sample work orders:
-
Create a repository directory, copy the SAR file to the new directory, and un-jar the SAR file, as described in Step 1 through Step 4 in "Mapping the NE_Cartridge_name_HOST.xml file to NEP Servers."
-
Locate and view the sample work order files.