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.
URI format
jt400://user:password@system/QSYS.LIB/LIBRARY.LIB/QUEUE.DTAQ
URI options
Name |
Default value |
Description |
---|---|---|
ccsid |
default system CCSID |
specifies the CCSID to use for the connection with the AS/400 system |
format |
|
specifies the data format for sending messages |
consumer.delay |
500 |
Delay in millis between each poll |
consumer.initialDelay |
1000 |
Millis before polling starts |
consumer.userFixedDelay |
false |
true to use fixed delay between pools, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details. |
Usage
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'
message's body, formatted as either a String
or a byte[]
, depending on the format. For a provider endpoint, the 'in'
message body contents will be put on the data queue as either raw bytes or text.
Example
In the snippet below, the data for an exchange sent to the direct:george
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.
public class Jt400RouteBuilder extends RouteBuilder { @Override public void configure() throws Exception { from("direct:george").to("jt400://GEORGE:EGROEG@LIVERPOOL/QSYS.LIB/BEATLES.LIB/PENNYLANE.DTAQ"); from("jt400://RINGO:OGNIR@LIVERPOOL/QSYS.LIB/BEATLES.LIB/PENNYLANE.DTAQ").to("mock:ringo"); } }