ISO8583 Java Connector
Free ISO8583 Java Connector
Solution: "J-Reactive-8583" ISO8583 Client and Server built on top of excellent Netty asynchronous messaging framework with the help of j8583. It is distributed under Apache License 2.0.
For data transmission TCP/IP uses sessions. Each session is a bi-directional data stream. The protocol uses a single TCP/IP session to transfer data between hosts in both directions.
The continuous TCP/IP data stream is split into frames. Each ISO8583 message is sent in a separate frame.
A Frame consists of a N-byte length header and a message body. Usually, N==2. The header contains the length of the following message. The high byte of value is transmitted first, and the low byte of value is transmitted second.
N bytes | M bytes |
---|---|
Message Length = M | ISO–8583 Message |
First, you need to download latest release or clone this repository and build artifact with maven manually.
Then add dependency to your project:
<dependencies>
<dependency>
<groupId>org.jreactive</groupId>
<artifactId>netty-iso8583</artifactId>
<version>0.1.1</version>
</dependency>
...
<dependencies>
Now you may use ISO8583 client or server in your code.
The minimal client workflow includes:
MessageFactory<IsoMessage> messageFactory = ConfigParser.createDefault();// [1]
Iso8583Client<IsoMessage> client = new Iso8583Client<>(clientMessageFactory());// [2]
client.addMessageListener(new IsoMessageListener<IsoMessage>() { // [3]
...
});
client.getConfiguration().replyOnError(true);// [4]
client.init();// [5]
client.connect(host, port);// [6]
if (client.isConnected()) { // [7]
IsoMessage message = messageFactory.newMessage(...);
...
client.send(message);// [8]
}
...
client.shutdown();// [9]
MessageFactory
Iso8583Client
providing MessageFactory
and, optionally, SocketAddress
IsoMessageListener
s to handle IsoMessage
s.IsoMessage
Typical server workflow includes:
MessageFactory<IsoMessage> messageFactory = ConfigParser.createDefault();// [1]
Iso8583Server<IsoMessage> server = new Iso8583Server<>(port, serverMessageFactory());// [2]
server.addMessageListener(new IsoMessageListener<IsoMessage>() { // [3]
...
});
server.getConfiguration().replyOnError(true);// [4]
server.init();// [5]
server.start();// [6]
if (server.isStarted()) { // [7]
...
}
...
server.shutdown();// [8]
MessageFactory
Iso8583Server
providing MessageFactory
and port to bind to IsoMessageListener
s to handle IsoMessage
s.Default IsoMessageLoggingHandler
may produce output like:
312 [nioEventLoopGroup-5-1] DEBUG IsoMessageLoggingHandler - [id: 0xa72cc005, /127.0.0.1:50853 => /127.0.0.1:9876] MTI: 0x0200
2: [Primary account number (PAN):NUMERIC(19)] = '000400*********0002'
3: [Processing code:NUMERIC(6)] = '650000'
7: [Transmission date & time:DATE10(10)] = '0720233443'
11: [System trace audit number:NUMERIC(6)] = '483248'
32: [Acquiring institution identification code:LLVAR(3)] = '456'
35: [Track 2 data:LLVAR(17)] = '***'
43: [Card acceptor name/location (1-23 address 24-36 city 37-38 state 39-40 country):ALPHA(40)] = 'SOLABTEST TEST-3 DF MX '
49: [Currency code, transaction:ALPHA(3)] = '484'
60: [Reserved national:LLLVAR(3)] = 'foo'
61: [Reserved private:LLLVAR(5)] = '1234P'
100: [Receiving institution identification code:LLVAR(3)] = '999'
102: [Account identification 1:LLVAR(4)] = 'ABCD'
Using client or server configurationYou may :
You may provide your own logging handler and disable default one by using org.jreactive.iso8583.ConnectorConfiguration.addLoggingHandler(boolean)
method and customizing ChannelPipeline.