WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of which message formats or network protocols are used in implementation. Type the following URL in your web browser and access the ASAP Web Services WSDL:

http://server:port/env_id/Oracle/CGBU/Mslv/Asap/Ws?WSDL

where:

• server is the server address.

• port is the port number of the Oracle WebLogic Server installation.

• env_id is the environment identifier specified when ASAP was installed.

HTTP protocol is used for a handshake with the application server to authenticate and request a web service client stub, which is used as the launch pad to talk to the web service. Then the client can communicate with the ASAP Web Services using one of the HTTP, HTTPS, or JMS protocols.

The ASAP Web Services WSDL exposes most of the functionality that is available through JSRP in ASAP for flow through activation. See "About Web Service Operations" for more information about WSDL operations.

ASAP Web Services must use OSS/J compliant data types. The WSDL file defines message types according to the OSS/J-type XML files with ASAP extensions. You can refer to the following XSD files provided with the ASAP application for extension descriptions:

• XmlCommonSchema.xsd

• XmlServiceActivationSchema.xsd

• ASAPServiceActivation.xsd

See ASAP Online Reference for more information about the XSD files. The ASAP Online Reference can be extracted from the ASAP_src/doc.tar file, where ASAP_src is the location of the ASAP installation files. The annotated XSD files can also be found in the ASAP environment at ASAP_Home/xml/xsd.

The WSDL document declares the OSS/J elements for each web services operation. Following is a snippet for the startOrderByKey operation in a WSDL document:

<xs:element name="startOrderByKey">
<xs:complexType>
<xs:sequence>
<xs:element ref="s4:startOrderByKeyRequest"/>
</xs:sequence>
</xs:complexType>
</xs:element>

For ASAP, we need to pass a raw XML document in OSS/J plus ASAP extension type.