Create jPOS Custom XML Channel not ISO8583 Format

Today, i have new project for creating TCP server and client for electronic financial transaction. Actually, i feel strange to the requirment because we have to sent xml messaging through an TCP, my big question is WHY DONT YOU USE HTTP??? and my boss said, “we have to coddling the clients!” so i can’t say anything. I am jPOS ISO8583 framework fanatics, so i want to use jPOS for this project. My big problems is, the messaging is not ISO8583 format, so i have to custom to fits the jPOS

Continue reading

Custom jPOS Channel binary bitmap Active Bit Indicator

Today, i have implement new Custom jPOS Channel binary bitmap Active Bit Indicator for communicate between some bank with goverment tax system. there are strange ISO 8583 message structure like this [ISO HEADER] [BODY], there are no message length indicator, and tail. The strange occure in the body message, they are not using hexa format for the ‘active bit indicator’ or we call it bitmap (primary/secondary/tertiary bitmap), but in binary format. So, i create Custom jPOS Channel binary bitmap Active Bit Indicator that can fit that requirment called BinaryX25Channel. The

Continue reading

Tutorial Customize JPos NACChannel with Tail

Today i want to share Tutorial Customize JPos NACChannel with Tail Jpos Library comes with several channel implementation. Most channel implementation extend BaseChannel class and just override the sendMessageLength and getMessageLenght methods. every channel implementation have different message format, for example NACCHannel using LL LL [TPDU] ISO-Data message format, where: LL LL represent the TPDU + ISO-Data length in network byte order Optional TPDU(Transport protocol data unit) ISO-Data: ISO-8583 image in my experience for integration with Base24 they send ISO-8583 with format LL LL [TPDU] ISO-Data tail, so my JPos

Continue reading