Hi,

please follow the instructions in ReadMe.htm regarding the environment
variables the nedd to be set before the using or building MultiXTpm
based applications

Thanks

Moshe Shitrit







--- In multixtpm@yahoogroups.com, "badreddine_meherzi"
<stratocaster84@...> wrote:
>
> Hello everybody,
>  I'm a new MultiXTpm user and I first downloaded the project version
> 4.0.8a from source forge and when trying to build and execute it using
> make runtime .bat file the following errors occurs:
> 3)LINK :ftal error LNK 1104:cannot open file'..\debug\multixd.lib
> 4)LINK :ftal error LNK 1104:cannot open
> file'..\debug\multixgsoapsuuportd.lib'.
>
> Please can someone help me I really tried so and so but no means to
> resolve them . thanks
>

Hello everybody,
  I'm a new MultiXTpm user and I first downloaded the project version
4.0.8a from source forge and when trying to build and execute it using
make runtime .bat file the following errors occurs:
3)LINK :ftal error LNK 1104:cannot open file'..\debug\multixd.lib
4)LINK :ftal error LNK 1104:cannot open
file'..\debug\multixgsoapsuuportd.lib'.

Please can someone help me I really tried so and so but no means to
resolve them . thanks

Hi,

It looks like all processes have some issue connecting to MultiXTpm, so they do not get the configuration from MultiXTpm and do not open links at all.

One of the reasons that this could happen is that the IP specified on –MultiXTpmIP is not accessible to client applications, maybe you have some VPN program or two adapters.

A possible solution is to change the parameters for link id 999998 in TpmConfig.xml

                                <MultiXTpm:Link>

                                                <MultiXTpm:ID>999998</MultiXTpm:ID>

                                                <MultiXTpm:Description>Default MultiXTpm Server Link</MultiXTpm:Description>

                                                <MultiXTpm:LinkType>MultiXLinkTypeTcp</MultiXTpm:LinkType>

                                                <MultiXTpm:OpenMode>MultiXOpenModeServer</MultiXTpm:OpenMode>

                                                <MultiXTpm:Raw>false</MultiXTpm:Raw>

                                                <MultiXTpm:LocalAddress>217.14.208.78 </MultiXTpm:LocalAddress>

                                                <MultiXTpm:LocalPort>44444 </MultiXTpm:LocalPort>

                                                <MultiXTpm:RemoteAddress></MultiXTpm:RemoteAddress>

                                                <MultiXTpm:RemotePort></MultiXTpm:RemotePort>

                                </MultiXTpm:Link>

The IP is set explicitly to the machine IP

The port is set to a known value so you can try end telnet to that IP and port to see if MultiXTpm successfully listens on the port.

If you still have problem, contact me directly to multixtpm @mitug.co.il

Thanks

Moshe

--- In multixtpm@yahoogroups.com, "kreten3003" <kreten3003@...> wrote:
>
> The problem that I have is that my setup is exactly like that, default
> Tpmconfig.xml with port 38583 for ISO8583IssuerGatewayWSFE. I have
> tried to telnet to that port but the connection is refused, aka the
> port is not open. I have checked and there is no issue with the
> firewall on the machine itself. I can have another application open
> the port 38583 without any problems.
>
> In fact, checking with netstat shows that even though the
> ISO8583IssuerGatewayWSFE process is active, it hasn't opened the port
> 38583 or any other port. Basically, ISO8583IssuerGatewayWSFE is not
> opening any ports when running, and not reporting any errors either. A
> quick look at the C++ code for WSFE gateway shows that it would
> definitely report an error message if it was unable to open the port.
> So, either I can't read code, I am missing something totally obvious,
> or possibly I mis-compiled the application.
>
> Is there a way to force ISO8583ISsuerGatewayWSFE to show full
> debugging notices, or log them in some file? I noticed Tpmconfig.xml
> allows different debug levels to be set but I can't find any
> information on what those debug levels mean.
>
> 1. About MTIs... I don't have any. At this point I have not gotten any
> settings information from my bosses, and they don't have any to share.
> I suppose I can setup the config files with any default MTI that can
> be used for that.
>
> 2. The test server configuration would be great. I'd greatly
> appreciate that. I don't want to attach an untested translation
> software to a production environment which authorizes financial
> transactions..... that would be very irresponsible.
>
> Igor Lulic
>
> --- In multixtpm@yahoogroups.com, "moshe_shitrit" multixtpm@ wrote:
> >
> > 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
> > >
> >
>

Small update - I have obtained the MTIs that will be used:

MTI

Authorization Request 0100
Authorization Response 0110
*Authorization Response waiting time 30 sec

Reversal Advice 0420
Reversal Advice Response 0430
Reversal Advice Repeat 0421

Thanks again,

Igor Lulic

The problem that I have is that my setup is exactly like that, default
Tpmconfig.xml with port 38583 for ISO8583IssuerGatewayWSFE. I have
tried to telnet to that port but the connection is refused, aka the
port is not open. I have checked and there is no issue with the
firewall on the machine itself. I can have another application open
the port 38583 without any problems.

In fact, checking with netstat shows that even though the
ISO8583IssuerGatewayWSFE process is active, it hasn't opened the port
38583 or any other port. Basically, ISO8583IssuerGatewayWSFE is not
opening any ports when running, and not reporting any errors either. A
quick look at the C++ code for WSFE gateway shows that it would
definitely report an error message if it was unable to open the port.
So, either I can't read code, I am missing something totally obvious,
or possibly I mis-compiled the application.

Is there a way to force ISO8583ISsuerGatewayWSFE to show full
debugging notices, or log them in some file? I noticed Tpmconfig.xml
allows different debug levels to be set but I can't find any
information on what those debug levels mean.

1. About MTIs... I don't have any. At this point I have not gotten any
settings information from my bosses, and they don't have any to share.
I suppose I can setup the config files with any default MTI that can
be used for that.

2. The test server configuration would be great. I'd greatly
appreciate that. I don't want to attach an untested translation
software to a production environment which authorizes financial
transactions..... that would be very irresponsible.

Igor Lulic

--- In multixtpm@yahoogroups.com, "moshe_shitrit" <multixtpm@...> wrote:
>
> 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
> >
>

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
>

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

Hi Igor

I have not built MultiXTpm using VS2008, as I specified, the
solutions are for VS 2005. The next release will probably include VS
2008 solutions

thanks

moshe shitrit







--- In multixtpm@yahoogroups.com, "Igor Vitorio Custodio"
<igorvc@...> wrote:
>
>  Hi all,
>
>  First at all this is project is very interesting.
>
>  Well, I'm Computer Engineer that works with Finantial transactions
> using ISO8583/XML packets.
>
>  I found this project when I was looking for a library to use in a
> open source project to send ISO8583 messagens using C#.
>
>  I'm trying to build a GPL framework to use for make Unit tests in
> ISO8583 enviroment.
>
>  But before start code, I want to study better you platform and see
> what we can use from it in this projetc.
>
>  I started reading the website docs and found a bit docs that really
> help to understand all piece of the project.
>
>  After that, I tryed to compile the source using Visual Studio
Express
> 2008, but I can't finish, because a lot of errors, despite of I had
> all dependecies.
>
>  I already tryed to compile in Linux (Ubuntu 8.04), and can't
finish.
>
>  So I ask: Have you ever compile this project in VS2008?
>
>  Can you give-me some hint?
>
>  Best regards,
>
>  Igor Custodio
>

Hi all,

  First at all this is project is very interesting.

  Well, I'm Computer Engineer that works with Finantial transactions
using ISO8583/XML packets.

  I found this project when I was looking for a library to use in a
open source project to send ISO8583 messagens using C#.

  I'm trying to build a GPL framework to use for make Unit tests in
ISO8583 enviroment.

  But before start code, I want to study better you platform and see
what we can use from it in this projetc.

  I started reading the website docs and found a bit docs that really
help to understand all piece of the project.

  After that, I tryed to compile the source using Visual Studio Express
2008, but I can't finish, because a lot of errors, despite of I had
all dependecies.

  I already tryed to compile in Linux (Ubuntu 8.04), and can't finish.

  So I ask: Have you ever compile this project in VS2008?

  Can you give-me some hint?

  Best regards,

  Igor Custodio

I have just released a new version of MultiXTpm Application Server.
This version includes a Web Services interface for the ISO 8583 Server.
It also includes a test client that can read XML based text files,
convert the data to ISO 8583 messages and forward it to any ISO 8583
based server.

you can download the new version at http://multixtpm.sourceforge.net

Thanks

Moshe Shitrit

Hi George,

First, I want to thank you for your interest in MultiXTpm Application
Server.

In PCI terminology MultiXTpm as is can be considered as a component
located at service provider and it transmits cardholder data.
MultiXTpm functionality as ISO 8583 Router implies that it only
transmits data and store data. This means that the only requirement
from the 12 PCI requirements that applies to MultiXTpm is Requirement
4: Encrypt transmission of cardholder data across open, public
networks.

Since MultiXTpm supports SSL encryption thru using the OpenSSL
package, it seems that MultiXTpm complies with PCI.

If one decides to use MultiXTpm and add application level
functionality like : authorizing cards, storing card data in database
and things like that, it is anyways the responsibility of the
developer to develop the new code with PCI compliance in mind. In
that case MultiXTpm does not stand in the way and does not enforce
anything that would prevent the added software from being PCI
compliant.

I hope this answer helps and will be very happy to assist you in any
question or problem regarding MultiXTpm.

Thanks

Moshe Shitrit






--- In multixtpm@yahoogroups.com, "hostsms" <fudge@...> wrote:
>
> Hello,
>
> Was wondering if MultiXTPM is PCI compliant or if it could be as it
> stands?
>
> If I use Panel PC's as client terminals, will the multixtpm help in
> any way to be PCI compliant.
>
> Excuse my ignorance as I currently new and still investigating and
> planning for a project, that will need a server based transaction
> server,
> similar to commercial ones but I would think their overkill for
> what I would need them for,
> therefore prefer to consider using multixtpm that can be adapted
with
> ease to our needs when needed.
> The project in mind is for mobile and stored value top up's and
> transaction person to person transfers for their credit.
>
> Look forward to your feedback and any suggestions you would have.
>
> Regards
> George
>

Hello,

Was wondering if MultiXTPM is PCI compliant or if it could be as it
stands?

If I use Panel PC's as client terminals, will the multixtpm help in
any way to be PCI compliant.

Excuse my ignorance as I currently new and still investigating and
planning for a project, that will need a server based transaction
server,
similar to commercial ones but I would think their overkill for
what I would need them for,
therefore prefer to consider using multixtpm that can be adapted with
ease to our needs when needed.
The project in mind is for mobile and stored value top up's and
transaction person to person transfers for their credit.

Look forward to your feedback and any suggestions you would have.

Regards
George

Hi Nguyen,
1. To set the include path, go to tools->options->Projects and
Solutions->VC++ Directories. There you will choose the "include
files" option and add the gSoap path to the include list.

2. MultiXTpm is a platform for developing distributed applications.
ISO 8583 Server is a prototype application implemented using the
MultiXTpm development platform. The server provides the
infrastructure for developing an ISO 8583 based applications and
routers. IT DOES NOT INCLUDE a full application to serve any general
purpose ISO 8583 requirements. In order to use the server, some
customizations and additions MUST be done. These customizations
include among other things, the processing of different ISO 8583
messages (there are a lot of them, and each system mat support a
different subset), add rules for local authorization and/or remote
authorization by forwarding to other hosts, database activities
handling etc...

If you plan to use MultiXTpm ISO 8583 server as an off-the-shelf
product, I'm afraid, this solution will not help you a lot. On the
hand, if you plan to develop your full application using the provided
server as a starting point, I believe that MultiXTpm ISO 8583 Server
an excellent choice and in that case I will be glad to help you with
your development.
Just let me know when you need help and I'll try to help you the best
as I can.

Thanks

Moshe Shitrit







--- In multixtpm@yahoogroups.com, "hocnvyh" <hocnvyh@...> wrote:
>
> Hi all !
>   I 've just found MultiXTpmApplicationServer-4.0.2d.zip on the
> sourceforge. Following the readme.html, to setup the runtime
environment
> on windows32 platform,  the second step :
>      Make sure that gSoap base directory          is on the INCLUDE
path
> of Visual           Studio. This directory should be
where
> stdsoap2.cpp and stdsoap2.h are located.
> I don't know how to check and set the Include path of visual
studio, can
> anybody help me ?
> After that, I want to setup Iso server  but I also don't know
how/where
> to start up.
>
> help me
>
> Nguyen Van Hoc
> HiPT Group
> http://www.hipt.com.vn
>

I submitted a patch to MultiXTpm ISO 8583 Server. It fixes a bug in the processing of ISO 8583 Messages. It can be downloaded at http://sourceforge.net/tracker/index.php?func=detail&aid=1824085&group_id=196021&atid=955784

Thanks

Moshe Shitrit

Hi Moshe. MTOM server is based on the mtom-stream sample that comes
with gsoap distribution. No problem, I will work on the integration
and will let you know of the outcome.

thanks,

Remsy

--- In multixtpm@yahoogroups.com, "moshe_shitrit" <multixtpm@...> wrote:
>
> Hi Remsy,
>
> I beleive that the main issue in MultiXTpm was that it did not
> support "chunked" transfer-encoding. Once this issue is solved and
> DIME is supported, I think that MTOM is supported automatically, at
> least from MultiXTpm point view.
>
> From looking at your source of the server, it looks like it is also
> based on the "dimeserver" from gSoap samples. If you look
> at "gSoapDimeServer" project in "MultiXTpm gSoap Enhancer" solution,
> you can see the modifications I made in order to
> integrate "dimeserver" into MultiXTpm environment. I suggest you try
> doing the same with your mtomserver and see if it works. It should be
> straight forward. Remember that you need to modify "TpmConfig.xml" to
> add support to your mtomserver dll. If you have problems, just let me
> know and we could do it together.
>
> regarding CYGWIN, I problems compiling the source using gcc 3.4.4, I
> have some c++ template issues using gcc 3.4.4 release. when solve
> these issues, I'll be able to provide support for CYGWIN as well.
>
> Thanks
>
> Moshe Shitrit
>
>
>
> --- In multixtpm@yahoogroups.com, "rschmilinsky" <rschmilinsky@>
> wrote:
> >
> > Hi Moshe, Thanks for the release. I was wondering if it includes
> > support for MTOM streaming ?
> >
> > regards
> >
> > remsy
> >
> > --- In multixtpm@yahoogroups.com, "moshe_shitrit" <multixtpm@>
> wrote:
> > >
> > > I have release a new version of MultiXTpm Application Server.
> > > Besides some bug fixes, I added support for DIME streaming in
> MultiXTpm
> > > gSoap Enhancer.
> > >
> > > I also fixed an error in the build shell script for ISO 8583
> Server, so
> > > if you have not succeeded to build it under linux, try the new
> release,
> > > it should be OK.
> > >
> > > Thanks
> > >
> > > Moshe Shitrit
> > >
> >
>

Hi again,

One thing I did not mention,currently MultiXTpm support
HTTP "chunked" Transfer-Encoding, but it does not really stream the
data. when data is received, MultiXTpm buffers all data, and only
when all chunks are received, the request is forwarded to gSoap code.
The same happens on the output, when gSoap writes the data, MultiXTpm
buffers all data, and only when gSoap finishes it "writes", MultiXTpm
forwards the data to the client (Asynchronously).

The benefit of this processing is that the service functions are tied
up for a very short period (all data transfer is in memory).

The disadvantage is that if there is a lot of data (big files), a lot
of virtual memory is consumed.

I might improve the algorithm as MultiXTpm developes.

Thanks

Moshe Shitrit



--- In multixtpm@yahoogroups.com, "rschmilinsky" <rschmilinsky@...>
wrote:
>
> Hi Moshe, Thanks for the release. I was wondering if it includes
> support for MTOM streaming ?
>
> regards
>
> remsy
>
> --- In multixtpm@yahoogroups.com, "moshe_shitrit" <multixtpm@>
wrote:
> >
> > I have release a new version of MultiXTpm Application Server.
> > Besides some bug fixes, I added support for DIME streaming in
MultiXTpm
> > gSoap Enhancer.
> >
> > I also fixed an error in the build shell script for ISO 8583
Server, so
> > if you have not succeeded to build it under linux, try the new
release,
> > it should be OK.
> >
> > Thanks
> >
> > Moshe Shitrit
> >
>

Hi Remsy,

I beleive that the main issue in MultiXTpm was that it did not
support "chunked" transfer-encoding. Once this issue is solved and
DIME is supported, I think that MTOM is supported automatically, at
least from MultiXTpm point view.

From looking at your source of the server, it looks like it is also
based on the "dimeserver" from gSoap samples. If you look
at "gSoapDimeServer" project in "MultiXTpm gSoap Enhancer" solution,
you can see the modifications I made in order to
integrate "dimeserver" into MultiXTpm environment. I suggest you try
doing the same with your mtomserver and see if it works. It should be
straight forward. Remember that you need to modify "TpmConfig.xml" to
add support to your mtomserver dll. If you have problems, just let me
know and we could do it together.

regarding CYGWIN, I problems compiling the source using gcc 3.4.4, I
have some c++ template issues using gcc 3.4.4 release. when solve
these issues, I'll be able to provide support for CYGWIN as well.

Thanks

Moshe Shitrit



--- In multixtpm@yahoogroups.com, "rschmilinsky" <rschmilinsky@...>
wrote:
>
> Hi Moshe, Thanks for the release. I was wondering if it includes
> support for MTOM streaming ?
>
> regards
>
> remsy
>
> --- In multixtpm@yahoogroups.com, "moshe_shitrit" <multixtpm@>
wrote:
> >
> > I have release a new version of MultiXTpm Application Server.
> > Besides some bug fixes, I added support for DIME streaming in
MultiXTpm
> > gSoap Enhancer.
> >
> > I also fixed an error in the build shell script for ISO 8583
Server, so
> > if you have not succeeded to build it under linux, try the new
release,
> > it should be OK.
> >
> > Thanks
> >
> > Moshe Shitrit
> >
>

Hi Moshe, Thanks for the release. I was wondering if it includes
support for MTOM streaming ?

regards

remsy

--- In multixtpm@yahoogroups.com, "moshe_shitrit" <multixtpm@...> wrote:
>
> I have release a new version of MultiXTpm Application Server.
> Besides some bug fixes, I added support for DIME streaming in MultiXTpm
> gSoap Enhancer.
>
> I also fixed an error in the build shell script for ISO 8583 Server, so
> if you have not succeeded to build it under linux, try the new release,
> it should be OK.
>
> Thanks
>
> Moshe Shitrit
>

I have release a new version of MultiXTpm Application Server.
Besides some bug fixes, I added support for DIME streaming in MultiXTpm
gSoap Enhancer.

I also fixed an error in the build shell script for ISO 8583 Server, so
if you have not succeeded to build it under linux, try the new release,
it should be OK.

Thanks

Moshe Shitrit

Since it is posix complient, I beleive that it is not a problem, but
it will take some time because Im working now on something else.

And as I said, in few days, I beleive the enhancer will be fixed to
support streaming.

Thanks

Moshe

--- In multixtpm@yahoogroups.com, "rschmilinsky" <rschmilinsky@...>
wrote:
>
> Thanks Mushe. Another question, do you think it is possible to build
> it under cygwin?
>
> Remsy
>

Thanks Mushe. Another question, do you think it is possible to build
it under cygwin?

Remsy

Hi Remsy,

I will look into it. I do not see why we could not integrate both
projects. There is one issue with MultiXTpm gSoap Enhancer that
currently it does not support streaming (chunked http messages). once
I add the support for chunked IO on the receiving side, I beleive the
mtomserver can be integrated almost transaparently. Just give me few
days and I'll return to you with firm answers.

Thanks

Moshe


--- In multixtpm@yahoogroups.com, "rschmilinsky" <rschmilinsky@...>
wrote:
>
> Hi Moshe.
>
> I have this project http://sourceforge.net/projects/mtomserver/ and
> would like to integrate it with multixtpm to automate the tasks of
> threading and queues management.
>
> This is the source for the server:
>
>
http://mtomserver.svn.sourceforge.net/viewvc/mtomserver/server/Server.
cpp?view=markup
>
> do you think the enhancer could be integrated to this? Another
concern
> is that the server references other functions and libraries.
>
> Please feel free to review anything under
> http://mtomserver.svn.sourceforge.net/viewvc/mtomserver/
>
> thanks
>
> Remsy
>

Hi Moshe.

I have this project http://sourceforge.net/projects/mtomserver/ and
would like to integrate it with multixtpm to automate the tasks of
threading and queues management.

This is the source for the server:

http://mtomserver.svn.sourceforge.net/viewvc/mtomserver/server/Server.cpp?view=m\
arkup

do you think the enhancer could be integrated to this? Another concern
is that the server references other functions and libraries.

Please feel free to review anything under
http://mtomserver.svn.sourceforge.net/viewvc/mtomserver/

thanks

Remsy

Hi Remsy,

Assuming you downloaded the latest version (4.0.2c), in the
directory "MultiXTpm Application Server" you will find a file called
ReadMe.htm, there you will find exact instructions on the steps
required to compile the application server on each platform.

once you installed the required software (tmake and gsoap), and once
you set the environment variables, in each directory (for gsoap
enahancer and iso 8583 and the application server itself) you will find
a files called "LinuxBuildAll.sh", just invoke it and its done.

You should build "MultiXTpm Application Server" first.
After you built it, invoke "MakeRuntime.sh" in "MultiXTpm Application
Server" directory.

After that you may build the other projects.

I hope this helps, if you have more questions, Im here to help.

Thanks

Moshe Shitrit


--- In multixtpm@yahoogroups.com, "rschmilinsky" <rschmilinsky@...>
wrote:
>
> Hi. Can you provide instructions on how to build it on linux ? I
> couldn't build it on my machine.
>
> thanks
>
> remsy
>

Hi. Can you provide instructions on how to build it on linux ? I
couldn't build it on my machine.

thanks

remsy