The JSRP is an upstream component into ASAP that provides a standardized OSS through Java (OSSJ) interface into the ASAP provisioning functionality and also a web services API implementation.

Figure 4-1 displays a system-level view of the JSRP. The JSRP receives requests from an upstream system, potentially an order manager: for example, Oracle Communications Order and Service Management (OSM) or a customer care system. Requests are translated into ASAP commands, which are then submitted to the SARM for processing.

The JSRP provides two types of interfaces: XML over JMS and Java value types (JVT) over RMI/IIOP. The JSRP is fully compliant with the OSSJ Service Activation API version 1.0.

In addition to the JSRP, web service provides an interface for SOAP/JMS messages. The web service implementation translates these SOAP/JMS messages into JVT work orders and sends them to the JSRP's JVT interface.

For more information about these interfaces, see "About the JSRP Server and Web Service Interfaces."

The JSRP and web service implementation are situated between the SARM and clients designed to send messages to either web service, JVT, or JMS interfaces. These clients are located on a remote application, such as OSM.

Oracle recommends that you create a Store and Forward (SAF) agent for requests and responses to and from the JMS or web service interfaces and the JMS or web service clients and a JMS bridge for work order state changes from ASAP to the JMS or web service clients. For more information about SAF and the JMS bridge, see "About Connecting JSRP JMS and Web Service Interfaces to a Remote Application."

The JVT interface does not require SAF or the JMS bridge.

The following list summarizes the components required for the two JSRP interfaces and the web service interface to a remote application (for example, OSM):

• JSRP JMS Interface to and from SAF and JMS Bridge to and from JSRP JMS Client (OSM)

• ASAP Web Service interface to and from SAF and JMS Bridge to and from JSRP Web Service Client (OSM)

• JSRP JVT Interface (RMI) to and from JSRP JVT Client (OSM)

For more information about creating a JVT or JMS Client, see the discussion about developing Java SRP client applications in ASAP Java Online Reference available from the Oracle software delivery website along with the ASAP installation files. ASAP Java Online Reference also provides a Java library for the JVT interface and lists the XML schemas used for constructing XML-based work order messages.

For more information about the web service API and the Web Services Description Language (WSDL) file, see ASAP Developer's Guide.

For information about sample JVT and JMS clients and source files that you can use to test the Java SRP, go to ASAP_Home/samples/jsrp/README.txt.

The JMS, JVT, and web services JMS modules, connection pools, and JDBC stores are automatically configured when you install ASAP. For information about these components, see "About the JSRP Server and Web Service Interfaces."

The configuration of the Java SRP deployment descriptors are automatically completed when you install ASAP. If you must fine-tune the deployment descriptor attributes of the Java SRP, see "Modifying JSRP Parameters (Deployment Descriptors) in WebLogic Server."

The implementation of the Java SRP and the web services API does not affect any provisioning logic in the existing ASAP product. Support for OSSJ and web services is implemented as translations to and from existing types and structures in ASAP, to OSSJ and web services conferment types and structures.

As with the other types of SRPs, the Java SRP and web services API allows the client to generate and submit work orders, manage work order events, and retrieve work order information.

if (useOriginalServiceInstanceNumbers()) {
    typeElement.appendChild( pKeyText );
    idElement.appendChild( typeText );
} else {
    typeElement.appendChild( typeText );
    idElement.appendChild( pKeyText );
}

<sa:createOrderByValueException
xmlns:co="http://java.sun.com/products/oss/xml/Common"
xmlns:mslv-sa="http://www.metasolv.com/oss/ServiceActivation/2003"
xmlns:sa="http://java.sun.com/products/oss/xml/ServiceActivation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<sa:illegalAttributeValueException>
<co:message>String attribute value[POTS12345678] exceeding its maximum length[8]</co:message>
</sa:illegalAttributeValueException>
</sa:createOrderByValueException>

If you have a custom JSRP client that is not based in WebLogic Server, you can use the Control server to manage (start, stop, auto-restart) it like any other ASAP component.

To configure a Java SRP Client:

1. Write a custom Java SRP client by extending the ASCAppl class (see the sample code below).

2. Implement applMain() method, which is the main function of the Java SRP client (see "Sample Code for a Custom JSRP Client").

3. Implement the initialize() method instead of providing a specialized constructor, if necessary (see "Sample Code for a Custom JSRP Client").

4. Using SACT, populate the Control database and ASAP Environment (tbl_appl_proc and tbl_component) for the new Java SRP client.

   <activationConfig xmlns="http://www.metasolv.com/ServiceActivation/2003/ActivationConfig" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.metasolv.com/ServiceActivation/2003/ActivationConfig 
   M:\hlam_view\ASAP_base\ASAP\jmx\xsd\ActivationConfig.xsd">
   
   <nonControlManagedServer name="JSRPenvid" xsi:type="JSRPServerType">
           <description>Java SRP</description>
           <system>envid</system>
           <territory>envid</territory>
           <diagnosticFilename>JSRPenvid.diag</diagnosticFilename>
           <diagnosticLevel>LOW_LEVEL</diagnosticLevel>
           <SARMListenPort>40070</SARMListenPort>
           <SRPListenHostname>
                   <IPaddress>10.156.53.74</IPaddress>
           </SRPListenHostname>
           <SRPListenPort>40077</SRPListenPort>
   </nonControlManagedServer>
    
   </activationConfig>
   

5. Write the script to run the Java SRP client (see "Sample Script to Run the Custom JSRP Client").

package com.metasolv.activation;

import java.util.*;
import java.io.*;
import java.sql.SQLException;
import java.text.*;
import com.mslv.activation.server.*;

public class SampleJSrpClient extends ASCAppl
{
 public void initialize()
 {
        super.initialize();
        // Do additional initialization
……..
 }

..
.
 public void applMain()
 {
    for(;;) {
        try {
            // Do actual process for JSRP client
………………
        } catch(Exception ex ) {  
        }
    }
  }

}

#!/bin/ksh

#
# =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
#
# (c) 2008 Oracle. 
# The CLASSPATH variable is used by the primordial class loader in the java virtual

The OCA SRP is similar to the Java SRP and resides in WebLogic Server. The OCA SRP shares some of the Java-based APIs used in JSRP. The OCA system includes a GUI based client for configuring the OCA SRP and integrates the work order related main functionality in this single program.