User defined service
User-defined Service
This component can be used to implement your own Custom Service.
The user-defined service can - given a single input message - generate multiple output messages if the result returned is of type java.util.Collection.
In the table below, you will find an explanation of these properties. All attributes with a ‘*’ are mandatory.
Attribute |
Description |
Name* |
By default, we fill this out with the technical ‘tag’, followed by a serial number. Changing the name is optional. |
Enabled |
Set this value to true, if you want to enable this service at startup. |
Bean or script Reference* |
Here, you can choose an existing java bean or a script. The bean needs to be known within the corresponding interface in the interface overview. This bean has to be an implementation of a class that implements the MyESBService interface.
|
Method |
In case the Service POJO (ref) is not derived from the AbstractMyESBService or the interface MyESBService has not been implemented, this is the name of the method in the Service POJO that will be called. The method has to have the signature Object method(Object content) throws Exception. The default value is invoke. |
Apply Sequence |
If this is enabled, the service will apply sequence information like correlationID, sequenceSize and sequenceNumber to multiple results. By default this is set to ‘false’. |
MessagePart In |
Here, you can specify the name of the MessagePart, which will be used as input. In case “ALL” is configured, the entire ConnectMessage (all MessageParts) will be used as input of the service method. The default value is msgprt0. Only use this when you are using different names and/or MessageParts. |
MessagePart Out |
Here, you can specify the name of the MessagePart, which will be used as output for the service method. The default value is msgprt0. |