The jt400
component allows you to exchanges
messages with an AS/400 system using data queues.
jt400://user:password@system/QSYS.LIB/LIBRARY.LIB/QUEUE.DTAQ[?options]
To call a remote program (Camel 2.7)
jt400://user:password@system/QSYS.LIB/LIBRARY.LIB/program.PGM[?options]
You can append query options to the URI in the following format,
?option=value&option=value&...
For the data queue message exchange:
Table 58. Message exchange uri options
Name | Default value | Description |
---|---|---|
ccsid
| default system CCSID | Specifies the CCSID to use for the connection with the AS/400 system. |
format
|
text
| Specifies the data format for sending messages valid options are: text
(represented by String ) and binary (represented by
byte[] ) |
consumer.delay
|
500
| Delay in milliseconds between each poll. |
consumer.initialDelay
|
1000
| Milliseconds before polling starts. |
consumer.userFixedDelay
|
false
| true to use fixed delay between polls, otherwise fixed rate is used.
See ScheduledExecutorService in JDK for details. |
guiAvailable
|
false
| Specifies whether AS/400 is available in the environment running Camel. |
keyed
|
false
| Specifies whether to use keyed or nonkeyed data queues. |
searchKey
|
null
| Specifies the search key to use for keyed data queues. |
searchType
|
EQ
| Specifies the search type. Valid values are EQ , NE ,
LT , LE , GT , or
GE . |
connectionPool
|
AS400ConnectionPool instance | Reference to a com.ibm.as400.access.AS400ConnectionPool instance in the
Registr, which is used for obtaining connections to the AS/400 system. The lookup notation
('#' character) should be used. |
For the remote program call (Camel 2.7):
Table 59. RPC uri options
Name | Default value | Description |
---|---|---|
outputFieldsIdx
| Specifies which fields (program parameters) are output parameters. | |
fieldsLength
| Specifies the fields (program parameters) length as in the AS/400 program definition. |
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 either as 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.
This endpoint expects the input to be a String array and handles all the CCSID handling trough the native jt400 library mechanisms. After the program execution the endpoint returns a String array with the values as they were returned by the program (the input only parameters will contain the same data as the beginning of the invocation) This endpoint does not implement a provider endpoint!
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.
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"); } }
In the snippet below, the data Exchange sent to the direct:work endpoint will contain three string that will be used as the arguments for the program "compute" in the library "assets". This program will write the output values in the 2nd and 3rd parameters. All the parameters will be sent to the direct:play endpoint.
public class Jt400RouteBuilder extends RouteBuilder { @Override public void configure() throws Exception { from("direct:work").to("jt400://GRUPO:ATWORK@server/QSYS.LIB/assets.LIB/compute.PGM?fieldsLength=10,10,512&ouputFieldsIdx=2,3").to("direct:play"); } }