DSMLv2SOAPServerConnector

You can know more about DSMLv2SOAPServerConnector using the information provided here.

The migration from the DSMLv2 EventHandler to the DSML v2 SOAP Server Connector requires rework of the AssemblyLines that are previously used with the EventHandler, so that they can be integrated in the solution with the DSMLv2 SOAP Server Connector. This is because the core architecture as changed; now a single AssemblyLine processes all operations. Therefore, all the old AssemblyLines logic responsible for handling the different types of DSMLv2 operations should be incorporated into the new AssemblyLine containing the DSMLv2 Soap Server Connector, or should be invoked using a AssemblyLine Connector. For this purpose branching components can be used in order to separate the logic for the specific DSMLv2 operations (available in the dsml.operation Attribute).

The migration of a configuration with the DSMLv2 EventHandler to a similar one with the DSMLv2 SOAP Server Connector consists of the following steps:

1. Create a new AssemblyLine with an instance of a DSMLv2 SOAP Server Connector in Server mode.
2. Copy the content of the EH port parameter to the dsmlPort Connector parameter.
3. Set the authRealm, useSSL, binaryAttributes and msgChunked to the values these connection parameters have in the EventHandler configuration.
4. Create a branch component for each of the DSMLv2 operations listed as parameters in the EH configuration and apply in the branches the logic implemented in the corresponding old AssemblyLine, either by transferring there the appropriate AL components or by invoking the old AL itself using an AssemblyLine connector. In both cases the naming context will no longer be needed.
5. Copy the content of the twoEH WaySSL parameter to the needClientAuth Connector parameter.
6. The EH Attribute headerAsProperties cannot be passed to the Connector, since the HTTP parser it initializes internally is configured to always set this value to "false". Therefore, in case the solution accesses headers as properties, it should be modified to use Attributes for this purpose (getAttribute() instead of getProperty()).
7. For compliance, the soapbinding Connector Attribute should be set to "false" since the DSMLv2 parser internally used by the EH does not take advantage of it.
8. In case an authConnector is specified in the configuration of the DSMLv2 EventHandler, then the HTTP basic authentication of the Connector must be enabled and the appropriate logic must be implemented in the "After Accepting connection" hook (for example, initialize the authenticator Connector and call its lookup() method using an Entry with Attributes "username" and "password" as search criteria. Similar to the EventHandler the authentication is to be considered successful in case an Entry is returned).
9. The indentoutput parameter of the DSMLv2 parser internally used by the Connector cannot be set in contrast to the one used by the EH.