The web service event listener allows publishing a custom web service in conjunction with the eBiss infrastructure. It requires a job containing a BackendObjectRetrieverEx with the backend type set to 'eBiss.WebServices.WebServiceBackendObjectSender' to be used. The service itself needs to be created in .NETby a class implementing the 'IWebServiceObjectSender' interface present in the eBiss.Api. The dll containing the services implementation must then be placed in the Plugins directory. See this for further information on how to create your own eBiss compatible web service.
| Properties | |
|---|---|
| Name | Description |
| Active | Event listener is active/inactive |
| Name | Name of the event listeners |
| Job | Job execute when an event is raised |
| User | User referenced in the resulting job run |
| Listener type | Type of the event listeners |
| Last time triggered | Time of last execution |
| Last change | Time of last change |
| Bound URL | The fully qualified URL that the service will be bound to |
| Webservice type | Webservice implementation to be used |
| Binding type | The binding type to be used when the webservice is initialized. Basic HTTP binding, for ASMX-bases services and clients and other services that conform to the WS-I Basic Profile 1.1. Web HTTP binding, for services exposed through HTTP requests instead of SOAP messages. WS HTTP binding, for services that conform to WS-* specifications. |
| Security mode | Security mode used to authenticate the clients access, this is highly dependant on the selected 'Binding type', |
| Max request size | Maximum of requested data in bytes. Default value -1 uses the system default that is usually 65535 bytes. |
| Debug trace | Debug information is printed to the service log |
| Change logs | The changes to the element are logged. The logging is activated in the System settings, which is possible if a versioning license is available. |