Inbound integration configuration XML elements
The following element types for inbound integrations are subtypes of the abstract
<inbound-integration> type:
<file-integration>- File inbound integration
<jms-integration>- JMS inbound integration
<custom-integration>- Custom inbound integration, directly implementing the
InboundIntegrationStartablePluginorInboundIntegrationMessageReplyinterface
<inbound-integration> XML element attributes and subelements
The abstract inbound integration XML element has the following attributes.
|
Attribute name |
Type |
Required |
Default value |
Description |
|---|---|---|---|---|
|
|
|
• |
A unique identifying name for this inbound integration in the inbound-integration-config.xml file. The |
|
|
|
|
|
Determines whether to disable this inbound integration. Set to true
to disable the inbound integration. |
|
|
|
|
Sets a configuration that is valid only for a specific server environment or set of server environments. You can specify multiple values for this attribute by using a comma-separated list. |
The abstract inbound integration XML element has the following subelements, in the order shown.
| Subelement name |
Type |
Required |
Default value |
Description |
|---|---|---|---|---|
|
|
|
• |
The unique name of a thread pool as configured earlier in the file. For testing inbound JMS integration in |
|
|
|
|
• |
60 |
The time interval in seconds between polls, though the algorithm interacts with the throttle interval and the ordered parameter. |
|
|
|
• |
60 |
The time interval in seconds after polling, though the algorithm interacts with the polling interval and the ordered parameter. |
|
|
|
• |
|
By default, the inbound file integration handles files in a single thread sequentially. To handle multiple files at a time in parallel in multiple threads on this server, set this value to
For file inbound integration, the order of the processing of individual files in the directory is undefined. Never rely on the order being any particular order, such as alphabetic or creation date. |
|
|
|
• |
|
If If not |
|
|
|
• |
|
Set this parameter to |
|
|
|
• |
|
Always set to |
<file-integration> XML element subelements
The file inbound integration XML element has the following additional subelements, in the order shown.
|
Subelement name |
Type |
Required |
Default value |
Description |
|---|---|---|---|---|
|
|
|
• |
|
The value is specified by the constants in gw.logging.TraceabilityIDCreationPoint. As well as the default value, the following value is also valid:
|
|
|
|
• |
The name in the Plugins registry for an implementation of the
|
|
|
|
|
• |
line |
To process one line at a time, set to To process one file at a time, set to |
|
|
|
• |
The full path of the configured incoming events directory. The value of this element must not be empty. |
|
|
|
|
• |
The full path of the configured processing events directory. The value of this element must not be empty. |
|
|
|
|
• |
The full path of the configured error events directory. The value of this element must not be empty. |
|
|
|
|
• |
The full path of the configured done events directory. The value of this element must not be empty. |
|
|
|
|
• |
UTF-8 |
The character set that the inbound file uses. The value of this element must not be empty. |
|
|
|
• |
|
If If For better security, set to |
<jms-integration> XML element subelements
The JMS inbound integration XML element has the following additional subelements, in the order shown.
|
Subelement name |
Type |
Required |
Default value |
Description |
|---|---|---|---|---|
|
|
|
• |
|
The value is specified by the constants in gw.logging.TraceabilityIDCreationPoint. As well as the default value, the following value is also valid:
|
|
|
|
• |
The name in the Plugins registry for an implementation of the
The value of this element must not be empty. |
|
|
|
|
• |
The application server configured JNDI connection factory. The value of this element must not be empty. |
|
|
|
|
• |
The application server configured JNDI destination. The value of this element must not be empty. |
|
|
|
|
• |
The default value is an empty |
Username for authenticating on the JMS queue. |
|
|
|
• |
The default value is an empty |
Password for authenticating on the JMS queue. |
|
|
|
• |
The default value is an empty |
Reserved for future use. |
|
|
|
• |
|
Reserved for future use. |
|
|
|
• |
The default value is an empty |
Reserved for future use. |
|
|
|
• |
15 |
The maximum time in seconds to wait for an individual JMS message. |
|
|
|
• |
5 |
The maximum number of messages to receive in a poll interval. |
|
|
A sequence of <jndi-property> elements |
• |
A sequence of arbitrary JNDI properties that you define. |
|
|
|
|
An arbitrary JNDI property that you define. Define |
<custom-integration> XML element subelements
The custom inbound integration XML element has the following additional subelements, in the order shown.
|
Subelement name |
Type |
Required |
Default value |
Description |
|---|---|---|---|---|
|
|
|
• |
|
The value is specified by the constants in gw.logging.TraceabilityIDCreationPoint. As well as the default value, the following values are also valid:
|
|
|
|
• |
The fully qualified name, including the package, of the
If your class is a Gosu class, you must also include the suffix .gs. For example: mycompany.integ.MyInboundPlugin.gs. The value of this element must not be empty. |
|
|
|
A sequence of |
• | A sequence of arbitrary parameters that you define. For example, you can use these
parameters to store server names and port numbers. For each parameter, create a
parameter subelement.The plugin interface has a setup method.
These parameters are in the |
|
|
|
|
An arbitrary parameter that you define. Define key and
value subelements that contain key/value pairs. |
