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:

1. Log in to the WebLogic Administration console.

2. In the left panel, in the Domain Structure section, click Deployments.

   The Summary of Deployments page appears.

3. Ensure that the managed server is running.

4. 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 several Demonstration Service Activation Models. If you have selected any of these models during the installation process, you can use them to test your ASAP installation.

Note: Oracle recommends that you read the Demonstration Service Activation Model README file of the Service Activation Model you chose to install during the ASAP installation. The ATM/FR, 3G Wireless and IP VPN Service Activation Models require additional configuration.

To test the ASAP Server installation, start ASAP and send sample work orders to the Demonstration Service Activation Model.

It is also recommended that you restart the WebLogic Server before testing the ASAP installation.

There are four Demonstration Service Activation Models in the ASAP server installer.

To test the installation:

1. From ASAP_home, source the Environment_Profile file:

   . ./Environment_Profile
   

2. (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.

3. Start ASAP using the following command (see Table 10-1 for argument details):

   start_asap_sys -d
   

4. From the UNIX prompt, enter:

   status
   

   A list of the ASAP servers that are running is displayed.

5. Using Table 10-1, locate the appropriate executable and enter it at the UNIX command prompt. The executables vary, depending on the activation cartridges you chose during the installation process.

   Refer to the README file for each Demonstration Service Activation Model for instructions on running ASAP using each model.

   Table 10-1 Service Activation Model Executables

   Demonstration Service Activation Model	Installation Path	ExecutableFoot 1
   ATM/FR Service Activation Model	$ASAP_BASE/samples/sadt/ATM_FR/Nortel/PASSPORT_3_0/	run_suite $SRP ctrl_password ALL_ATM or run_suite $SRP ctrl_password ALL_FR
   3G Wireless Service Activation Model	$ASAP_BASE/samples/sadt/3G_Wireless/Nortel/HLR_PS_3_0/	run_suite $SRP ctrl_password ALL_3GWL
   POTS Service Activation Model	$ASAP_BASE/samples/sadt/DemoInstall/Nortel/DMS/POTS/	run_suite $SRP ctrl_password ALL_POTS
   IP VPN Service Activation Model	$ASAP_BASE/samples/sadt/IPVPN/Nortel/SHASTA_2_5/	run_suite $SRP ctrl_password ALL_IPVPN

   
   

   ^Footnote 1 Where ctrl_password is the password for the control server.

6. To verify that work orders are executing, enter asap_utils.

7. When prompted, enter the password to the control server.

8. When prompted, enter 1 to view the service requests in the SARM database. The WO_STAT column displays the status of the work orders.

   Expect a combination of 104 (success),103 (in progress), 253 (failure) and 255 (translation failure). Some work orders may intentionally fail. The expected results are listed below.

   • ATM/FR Service Activation Model – The expected results for every work order is success (104).

   • 3G Wireless Service Activation Model – The expected results for every work order is success (104).

   • POTS Service Activation Model – 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): POTS-1, POTS-2, RAW-1, and TRUNK-1

     • Failure (253): POTS-3, POTS-4, and CTX-1

     • In Progress (103): POTS-5

   • IP VPN Service Activation Model – The expected results for every work order is success (104).

9. Use the test suite script run_suite to test the operation of ASAP in the current environment. The test suite uses an SRP emulator to send work orders through ASAP. You can then check work order status using the Order Control Application (OCA) or the ASAP utility script asap_utils.

   If the password is set with the same value as the user name, then the run_suite utility can be executed using one of the following formats:

   run_suite $SRP $CTRL_USER work_order_name [count [delay]]
   run_suite $SRP ctrl_password work_order_name [count [delay]]
   

   If you define a $CTRL_PASSWORD variable with the password value, you can use the command:

   run_suite $SRP $CTRL_PASSWORD work_order_name [count [delay]]
   

   If the password is set with a different value from the user name, run_suite $SRP $CTRL_USER does not work. The run_suite utility can be executed with:

   run_suite $SRP ctrl_password work_order_name [count [delay]]
   

   Or, you can define a $CTRL_PASSWORD environment variable with the password value, then use the command:

   run_suite $SRP $CTRL_PASSWORD work_order_name [count [delay]]
   

   Where:

   • crtl_password is the control password. For example, ctrlPass. Mandatory.

   • work_order_name is the work order or suite name. For example, POTS-2. Mandatory.

   • Values surrounded with [] are optional.

     
     

     Note: If ASAP fails to start, confirm that the ASAP_home/SYBASE/interfaces file is not empty (where ASAP_home is the location of your ASAP server installation directory). If it is, re-install ASAP. See "Re-Running the ASAP Server Installation" below.

     
     

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-2 to test the cartridge in loopback mode.

Table 10-2 Loopback Mode Parameter Settings

Configuration Variable	Parameter Settings	Location
LOOPBACK_ON	1 (default setting)	ASAP_home/configASAP.cfg

Live Mode:

Set the parameter listed in Table 10-3 to test the cartridge in live mode.

Table 10-3 Live Mode Parameter Settings

Configuration Variable	Parameter Settings	Location
LOOPBACK_ON	0	ASAP_home/configASAP.cfg

Mapping the NE_Cartridge_name_HOST.xml file to NEP Servers

To modify the NE_Cartridge_name_HOST.xml file:

1. Create a new source directory with a name of your choice.

   mkdir New_source_directory
   

2. Copy SAR_file.sar to this new source directory.

   cp SAR_file.sar ./New_source_directory
   

3. Change directory to New_source_directory.

   cd New_source_directory
   

4. Un-jar SAR_file.sar. This extracts the contents of the sar file.

   jar xvf SAR_file.sar
   

5. Edit New_source_directory/NE_Cartridge_name_HOST.xml to map the file to the NEP servers.

6. Create a new sar file at the New_source_directory level.

   CreateSar $PWD
   

7. Uninstall the cartridge using SAR_file.sar.

8. After you uninstall the cartridge, rename the sar file, so you have a backup copy.

9. Copy the new sar file from New_source_directory.

10. 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:

1. Stop ASAP by entering the following command at the UNIX prompt:

   stop_asap_sys -d
   

2. Ensure loopback mode is on. See "Configuring Loopback and Live Mode Parameters" for a description of how to set the loop back parameter to On.

3. Start ASAP by entering:

   start_asap_sys -d
   

4. Send the sample work orders through the SRP Emulator by entering:

   run_suite $SRP ctrl_password suite name
   

   You can locate the suite names by entering:

   grep SUITE * | grep -v END
   

   A list of all available suites appears.

   For more information on the SRP Emulator, refer to the ASAP System Administrator's Guide.

5. 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:

1. 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".

2. Locate and view the sample work order files.