SOAP event publisher sends SOAP events in the XML format via HTTP, HTTPS and local transports.
...
For instructions on creating a SOAP event publisher, see Publishing Events . see Creating Alerts .
Configuring global properties
The following global properties can be set for the SOAP event publisher type in the <DAS_HOME>/repository/conf/input-event-adapters.xml file. These properties apply to all the publishers of the soap type. If a global property available by default is removed, the default value of the property is considered.
| Info |
|---|
Custom properties cannot be added as global properties. |
| Property Key | Description | Data Type | Default Value |
|---|---|---|---|
minThread | The minimum number of threads (including idle threads) that should be available in the thread pool at a given time. | Integer | 8 |
maxThread | The maximum number of threads (including idle threads) that should be available in the thread pool at a given time. | Integer | 100 |
keepAliveTimeInMillis | The maximum number of milliseconds that idle threads should be kept alive when the total number of threads in the pool exceeds the number of cores in the machine. | Integer | 20000 |
jobQueueSize | The maximum number of milliseconds that idle threads should be kept alive when the total number of threads in the pool exceeds the number of cores in the machine. | Integer | 10000 |
axis2ClientConnectionTimeout | The number of milliseconds allowed to elapse before the Axis2 client connection times out. | Integer | 10000 |
reuseHTTPClient | If this property is set to true, it is allowed to reuse the connection to the HTTP client for subsequent requests. | Boolean | true |
autoReleaseConnection | If this property is set to true, inactive connections are automatically killed. | Boolean | true |
maxConnectionsPerHost | The maximum number of connections allowed per host configuration. | Integer | 50 |
Configuring adapter properties
...
| Info |
|---|
After entering the above adapter properties, select the select t he Message Format which you want to apply on the published events . Also, click click Advanced to to define custom output mappings based on the Message Format you you selected. For more information on custom output mapping types, see Publishing Events in Various Event Formats Output Mapping Types . |
You can also d efine the respective adapter properties of the event publisher based on the transport type within the <to> element of the event publisher configuration in the <PRODUCT_HOME>/repository/deployment/server/eventpublishers/ directory as follows.
...
Adapter Property | Description | Configuration file property | Example |
|---|---|---|---|
Url | Destination web service URL | url | http://localhost:9763/services/Axis2LogService/log |
| User Name | Username token which is required to send event to a HTTPS endpoint. | username | soap-user |
| Password | Password token which is required to send event to a HTTPS endpoint. | password | soap-password |
| SOAP Headers | Necessary SOAP headers. | soapHeaders | header1: value1, header2: value2 |
HTTP Headers | Necessary HTTP headers. | httpHeaders | header1: value1, header2: value2" |
Related samples
For more information on soap event publisher type, see the following sample in CEP Documentation.