This section explains the setup file for describing the SOAP listener definition (SOAP listener definition file).
The SOAP listener definition file is an XML file that has "soapListener" as the root element. A SOAP listener definition file is created for each user-developed Web service.
The items to be set in the SOAP listener definition file are shown below:
Element or attribute | Item name | Explanation | Allowed values | Mandatory/ |
|---|---|---|---|---|
id (attribute of "soapListener") | Development asset ID | ID unique in the deployment CEP engine Used as the output adapter (SOAP listener) in complex event processing rules. | Up to 39 alphanumeric characters, underscores (_), or hyphens (-). Note: The first character must be a letter. | Mandatory |
comment | Comment | Explanation of this definition. | Up to 1,000 characters. | Optional |
url | Connection URL | Connection URL for the user-developed Web service. | Up to 512 alphanumeric characters and symbols. | Mandatory |
nameSpace | Namespace | Namespace of the body of the SOAP message (SOAP body) to be sent to the user-developed Web service. | Up to 512 characters. | Mandatory |
prefix | Namespace prefix | Namespace prefix to be used in the body of the SOAP message (SOAP body). When omitted, "ns" is used. | Up to 20 characters. | Optional |
method | Root element | Root element name of the body of the SOAP message (SOAP body). | Up to 512 characters. | Mandatory |
Note
Up to 32 SOAP listener definitions can be deployed to one CEP engine.
Example
Description example
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<soapListener xmlns="urn:xmlns-fujitsu-com:cspf:bdcep:v1" id="LISTEN_01">
<comment>SOAP listener definition_01</comment>
<url>http://192.168.11.249/WebServWAR/MyApp1Service</url>
<nameSpace>http://webservice/</nameSpace>
<prefix>ns</prefix>
<method>cep</method>
</soapListener>
This example defines the notification of a message (event) that includes a SOAP body specifying that the root element is "cep" in the user-developed Web service with the connection destination URL "http://192.168.11.249/WebServWAR/MyApp1Service".
