THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
JT/400 Component
The jt400: component allows you to exchanges messages with an AS/400 system using data queues. This components is only available in Camel 1.5 and above.
...
| Code Block |
|---|
jt400://user:password@system/QSYS.LIB/LIBRARY.LIB/QUEUE.DTAQ[?options]
|
You can append query options to the URI in the following format, ?option=value&option=value&...
URI options
Name | Default value | Description |
|---|---|---|
| default system CCSID | specifies Specifies the CCSID to use for the connection with the AS/400 system. |
| | specifies Specifies the data format for sending messages |
| | Delay in millis milliseconds between each poll. |
| | Millis Milliseconds before polling starts. |
| | |
...
When configured as a consumer endpoint, the endpoint will poll a data queue on a remote system. For every entry on the data queue, a new Exchange is sent with the entry's data in the 'in' In message's body, formatted either as either a String or a byte[], depending on the format. For a provider endpoint, the 'in' In message body contents will be put on the data queue as either raw bytes or text.
...
In the snippet below, the data for an exchange sent to the direct:george endpoint will be put in the data queue PENNYLANE in library BEATLES on a system named LIVERPOOL.
Another user connects to the same data queue to receive the information from the data queue and forward it to the mock:ringo endpoint.
...