Connection to Postilion over PostBredge - q2 based solution
Mladen Mrkic
We need to make a new module at front of our application in order to
connect it to Postilion server over PostBridge interface.
We've been thinking about solution based on q2.
The new module, on the one side, toward our application have to:
1. listen on the specified port for incoming requests
2. then make some ISO8583 Protocol dialect translation (HYPERCOM to
POSTILION)
3. do MAC-ing, and send request to Postilion server
4. accept response from Postilion, etc. (all what it necessary in oposite
direction)
On the other side, toward Postilion server the new module have to:
1. listen on the other specified port for incoming Sign on/Sign off
messages (Sign on/Sign off - Postilion originated).
2. enable/disable receiving messages over first specified port.
Obviously, this work can't be accomplished with only one qserver.
We need two qservers and some way (some kind of space) for coordination
between this two qservers.
Is this approach OK?
Any suggestion/comment is welcome.
Thanks,
Mladen
Alejandro Revilla
> Obviously, this work can't be accomplished with only one qserver.
> We need two qservers and some way (some kind of space) for coordination
> between this two qservers.
>
>
> Any suggestion/comment is welcome.
>
Sounds like a qserver->connector->qmux->channel could do. You can either
use some filters or work on an specific ISORequestListener
implementation.
The Spaces sounds like a nice thing that you can use to coordinate
your server's activities (logon/logoff, etc.).
If you are to conduct dynamic key exchange, then you can use
the (persistent) JDBMSpace to easily store your cryptograms.
mla...@galeb.etf.bg.ac.yu
But in this scenario there are two connections towards Postilion
system.
The first one is for sign on/sign off messages (There will be a port on
which
our modul listen for sign on/sign off messages)
The second one is for financial transactions
(There is a port on which Postilion system listen for financial
transaction)
I am not quite sure that Postilion supports such kind of connection.
Probably not. It is more likely that there is only one connection.
For example, the test scenario for Echo test transaction would be the
following one:
1. Sign on request from Postilion to our modul.
2. Sign on response from our modul to Postilion.
3. Echo test request from our modul to Postilion.
4. Echo test response from Postilion to our modul.
According to this scenario our modul have to:
1. establish connection with Postilion to specified port.
2. then, it waits for Sign on request from Postilion.
3. then it sends Sign on response to Postilion.
4. sends to Postilion other financial transactions received from our
application.
Can someone who has worked with Postilion confirm this approach?
And the second question: is such solution posible in jpos/q2 domain?
Any suggestion is very welcome.
Thanks again,
Mladen
Alejandro Revilla
> 1. Sign on request from Postilion to our modul.
> 2. Sign on response from our modul to Postilion.
>
>
> 3. Echo test request from our modul to Postilion.
> 4. Echo test response from Postilion to our modul.
>
>
> 1. establish connection with Postilion to specified port.
>
>
> 2. then, it waits for Sign on request from Postilion.
>
request listener implementation needs to flag the fact
that you're free to send a signon message.
>
> 3. then it sends Sign on response to Postilion.
>
>
> 4. sends to Postilion other financial transactions received from our
> application.
>
Items 3 and 4 have to wait for some kind of flag that indicate
that the signon procedure was performed.
--Alejandro
murtuza chhil
Mladen>Can someone who has worked with Postilion confirm this approach?
To answer this...
chhil> Your approcah sounds correct. With Postbridge all messages
financial,signon etc are all sent on one connection.
The signon can be initiated from either side i.e. from your end or
Postilion (Postbridge's) end. depends on how Postbridge is configured.
-chhil