Hi,

Port 46941, in this case is dynamically allocated by the system and
is by the different processes to talk to MultiXTpm process. It
appears on the command line to inform the process how to communicate
with MultiXTpm. On this port, MultiXTpm utilizes the MultiX protocol
which is used only when using the MultiX API, but in any case there
is no need to deal with this protocol. But, this means that if you
try to send information in other protocols, like HTTP/SOAP/XML, it
will not work.
For your Web Services client (Gateway) you should use the port
specified for ISO8583IssuerGatewayWSFE which is 38583. When your
gateway connects to this port, it will be accepted by
ISO8583IssuerGatewayWSFE which will parse the XML, translate it to
ISO8583 and forward it to MultiXTpm, which based on the routine table
for messages found in TpmConfig.xml, will forward it the appropriate
process. This table can be configured by the admin system or directly
by modifying the TpmConfig.xml file.
Since I assume you are not familiar with its content and structure, I
can help you in this way:
1. You will send me a list of the MTI's that you gateway will
use.
2. I will provide you with a new TpmConfig.xml file that will
forward these MTI's to ISO8583AcquirerGatewayFE which in turn will
forward it to the ISO 8583 server of your own.
Since you do not have such test server, I can configure for you
another file that will enable you to run another instance of
MultiXTpm system, that you can run from another directory on the same
machine, which will receive the ISO8583 connections and receive the
messages, but will reject all the messages.

--- In multixtpm@yahoogroups.com, "kreten3003" <kreten3003@...> wrote:
>
> Hi.
>
> I apologize if this post comes across as ignorant, but I have hit a
> problem with MultiXTpm ISO8583Server. I am trying to create a
> middleware for my company's payment gateway to connect to an ISO8583
> payment authorization server. MultiXTpm seemed like a good way to go
> about it.
>
> I successfully compiled MultiXTpm and ISO8583Server directories on a
> CentOS 5.1 Linux. I then copied the MultiXTpm runtime binary to
> ISO8583Server runtime directory. I made no changes to default
> Tpmconfig.xml.
>
> [ilulic@multix runtime]$ ls
> ISO8583AcquirerGatewayFE ISO8583IssuerGatewayWSFED
> libISO8583Shared.so TpmConfig.xml
> ISO8583AcquirerGatewayFED ISO8583TestClient
> libISO8583Shared.so.1 TpmConfig.xml~
> ISO8583BackEnd ISO8583TestClientD
> libISO8583Shared.so.1.0.1 TpmConfig.xml.original
> ISO8583BackEndD ISO8583WS.wsdl
MultiXTpm
> UsersPermissions.xml
> ISO8583IssuerGatewayFE libISO8583SharedD.so MultiXTpmD
> ISO8583IssuerGatewayFED libISO8583SharedD.so.1
MultiXTpm.wsdl
> ISO8583IssuerGatewayWSFE libISO8583SharedD.so.1.0.1
TestFileIn.xml
>
> After that, I ran MultiXTpm. This is what I got:
>
> [ilulic@multix runtime]$ ./MultiXTpm &
> [1] 3833
> [ilulic@multix runtime]$ ( 266) (MultiXID 1) MultiXTpm started
> ( 269) (MultiXID 1) (Link
> ID=0,LocalIp=,LocalPort=,RemoteIp=,RemotePort=) Open Completed
> ( 279) (MultiXID 1) Starting Procees: ISO8583IssuerGatewayFE
> -MultiXID=100300 -MultiXTpmIP=217.14.208.78 -MultiXTpmPort=46941 &
> ( 290) (MultiXID 1) Starting Procees: ISO8583BackEnd
> -MultiXID=100400 -MultiXTpmIP=217.14.208.78 -MultiXTpmPort=46941 &
> ( 304) (MultiXID 1) Starting Procees:
ISO8583AcquirerGatewayFE
> -MultiXID=100500 -MultiXTpmIP=217.14.208.78 -MultiXTpmPort=46941 &
> ( 327) (MultiXID 100300) Application started
> ( 330) (MultiXID 1) Starting Procees:
ISO8583IssuerGatewayWSFE
> -MultiXID=100600 -MultiXTpmIP=217.14.208.78 -MultiXTpmPort=46941 &
> ( 343) (MultiXID 100500) Application started
> sh: ISO8583Authorizer: command not found
> ( 347) (MultiXID 1) Starting Procees: ISO8583Authorizer
> -MultiXID=100700 -MultiXTpmIP=217.14.208.78 -MultiXTpmPort=46941 &
> ( 348) (MultiXID 1) (Link
> ID=1,LocalIp=,LocalPort=18583,RemoteIp=,RemotePort=) Open Completed
> ( 361) (MultiXID 100400) Application started
> ( 367) (MultiXID 100600) Application started
>
> Please note that I know Authorizer is not compiled - I am not
> interested in running it as my gateway application keeps track of
it's
> own authorizations. I only want the translation from our application
> to ISO8583.
>
> At this point, I am somewhat confused. Despite Tpmconfig.xml putting
> the ISO8583IssuerGatewayWSFE at port 38583, the MultiXTpm
application
> server opens it and all other gateways at the same port, 46941. Does
> this mean I can have my gateway application shoot some well-formed
XML
> request in correct ISO8583WS.wsdl format to port 46941, and then
> MultiXTpm will send it off to AcquirerGateway translated to ISO8583?
> Or did I misconfigure something?
>
> Also, at this point it looks like the other side of my connection,
the
> ISO8583 authorization server I am connecting to, does not have a
test
> environment. Since I do not want to test with live production server
> while testing authorizations, is there a way to setup another
> MultiXTpm to accept connections the first one so I can test it,
> specifically the ISO8583IssuerGatewayWSFE -> MultiXTpm -> ISO8583
> whichever gateway?
>
> Thank you in advance, and again, apologies for my ignorance.
>
> Igor Lulic
>