AS2Service
The AS2Service integrates the Lobster AS2 system into the Lobster Integration Server.
XML configuration
Important note: The availability of a service depends on the license purchased and whether the service has been registered in the configuration file ./etc/factory.xml of the Service Factory (changes require server restart!). There you will also find the responsible configuration file for a service, otherwise you can also edit the configuration file of the service directly in the GUI of the service (changes require a service restart!).
Setting the servlet context to use for responses to AS2 requests
To respond to AS2 requests via HTTP, the AS2Service uses a servlet. Which HTTP server should provide the servlet under which context is set with the following XML fragment.
<Call name="setContext"> <Arg>Main Server</Arg> <Arg>/partner/*</Arg> <Arg>/AS2Retrieve/*</Arg></Call>The parameters have the following meaning.
|
servername |
The name of the HTTP server, here Main Server. |
|
contextname |
The context to use, which is an equivalent to the path to a resource represented by a URL. A peculiarity that differs from a regular path is the use of wildcards to specify where more values may be added. An example would be /partner/*. |
|
pathspec |
The pathspec to use. That is the equivalent of the filename of a resource represented by a URL. A peculiarity that differs from a normal filename is the use of wildcards to determine whether or not a path info is allowed. AN example would be /AS2Retrieve/*. |
Setting an AS2 "PartnerManager"
Setting the AS2 PartnerManager determines how the partner relations for AS2 requests are to be determined.
The following XML fragment sets the AS2 PartnerManager for the corresponding AS2Service.
<Call name="setPartnerManager"> <Arg> <New class="com.ebd.hub.services.as2.manager.commlog.PartnerManager"> </New> </Arg></Call>General settings
(1) and (2) The name of the HTTP server and the associated context and path for the servlet that accepts the AS2 requests.
(3) The used PartnerManager.
Settings for the "PartnerManager"
(1) Name of the cryptographic provider (here BouncyCastle).
(2) LogService and LogManager for the output of log messages.
(3) Message context and message queue. AS2 events are sent as messages to this queue.
(4) Used AuthenticationService and CommunicationLogService.
Attention: The AS2Service needs strong encryption. Standard virtual machine installations may be limited in key size, for example to comply with US export restrictions. Therefore, in order to be able to use key sizes required by this service, it may be necessary to unlock the virtual machine for strong encryption. For more information, please refer to the documentation of the virtual machine.
Log level dependencies
Changes to the log level of the LogService have no influence on the logging behaviour of the AS2Service. In verbose mode, the received data is Base64 encoded and transferred to the AS2 LogManager.