MultiXTpm Application Server

• MultiXTpm Application Server - This file contains a description of MultiXTpm environment and architecture.
• MultiXTpm Administration Server - Describes the Web Application to control and configure MultiXTpm Application Server.
• MultiXTpm Simple System - Describes how start developing a MultiXTpm based applications using MultiX Simplified API.
• MultiXTpm gSoap Enhancer - Describes the enhancements provided by MultiXTpm to gSoap toolkit.
• MultiXTpm ISO 8583 Server - Describes the prototype application used to develop ISO 8583 based applications.
• MultiXTpm ISO 8583 XML Bridge - Describes the application used to connect ISO 8583 based clients to SOAP/XML Web Services based back end servers.
• MultiXTpm Generic Multiplexer - Describes the features and architecture of the multiplexer.

Setting Up the runtime environment

WIN 32 platforms

1. The build process assume the existance of 2 software packages:
   • gSoap - for handling Web Service calls to MultiXTpm - can be downloaded at SourceForge.net
   • OpenSSL - for handling secured connections to MultiXTpm when performing control and configuration tasks - Can be downloaded at http://www.openssl.org .
2. Before building the solution, make sure that defined the following:
   • Add an environment variable called MultiXTpm and set its value to MultiXTpm Application Server main directory. (for example: MultiXTpm="c:/MultiXTpmInstallation/MultiXTpmApplicationServer"
   • Add the runtime directory to the PATH using the MultiXTpm environment variable. (PATH=...;%PATH%;%MultiXTpm%/runtime)
   • Make sure that %MultiXTpm%/include is on the INCLUDE path of Visual Studio
   • Make sure that %MultiXTpm%/Debug and %MultiXTpm%/Release are on the LIB path of Visual Studio
   • 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. 
3. Build the entire solution. You will notice that all DLL and EXE file names built using Debug Mode have a "D" appended to their names.
4. Once the entire solution is built with no errors, on the command prompt, change directory to MultiXTpm Application Server directory (cd %MultiXTpm%) and run the batch file MakeRuntime.cmd. This will create the directory "runtime" and will copy all relevant files to it.
5. The current setting in TpmConfig.xml instructs MultiXTpm to look for DLLs and executables in the current directory – the runtime directory.
6. If you want to run MultiXTpm as a standard process, just change to the runtime directory and run MultiXTpm.
7. If you want to run MultiXTpm as a windows service, do the following:
   • Type: net start MultiXTpm (to start the service).
   • Type: net stop MultiXTpm (to stop the service).

Linux platforms

1. The build process assume the existance of 3 software packages:
   • gSoap - for handling Web Service calls to MultiXTpm - can be downloaded at SourceForge.net 
   • OpenSSL - for handling secured connections to MultiXTpm when performing control and configuration tasks - Can be downloaded at http://www.openssl.org .
   • tmake-1.8 -  for generating the makefiles - can be downloaded at - Trolltech FTP server.
2. Before building the solution, make sure that defined the following:
   • Add an environment variable called MultiXTpm and set its value to MultiXTpm Application Server main directory. (for example: export MultiXTpm=~/MultiXTpmInstallation/MultiXTpmApplicationServer"
   • Add the runtime directory to the PATH using the MultiXTpm environment variable. (PATH="${MultiXTpm}"/runtime:":"${PATH}")
   • Add the runtime directory to the environment variable LD_LIBRARY_PATH. (export LD_LIBRARY_PATH="${LD_LIBRARY_PATH}":"${MultiXTpm}"/runtime)
   • Make sure that gSoap base directory is on the INCLUDE path of the compiler. This directory should be where stdsoap2.cpp and stdsoap2.h are located. (for gcc use CPATH=${CPATH}:~/<gSoap install directory>) 
3. Build the entire solution - Change to MultiXTpm Application Server directory (cd $MultiXTpm) and execute LinuxBuildAll.sh. You will notice that all DLLs and executable file names built using Debug Mode have a "D" appended to their names.
4. Once the entire solution is built with no errors, on the command prompt, change directory to MultiXTpm Application Server directory and run the batch file MakeRuntime.sh. This will create the directory "runtime" and will copy all relevant files to it.
5. The current setting in TpmConfig.xml instructs MultiXTpm to look for DLLs and executables in the current directory – the runtime directory.
6. If you want to run MultiXTpm, just change to the runtime directory and run MultiXTpm (or MultiXTpmD for the debug version).

Configuring the runtime environment

SSL Support

Using the Visual Studio 2005 MultiXTpm Application Wizard

1. In the IDE, Right click the project "MultiXTpm Application Wizard".
2. Select "Properties".
3. Select "Configuration Properties->Build Events->Post-Build Event".
4. Change "Exclude from build" from "Yes" to "No".
5. Click OK.
6. Build the project.
7. To avoid repeating the copy operation, perform steps 1-4 again but on step 4 change "Exclude from build" from "No" to "Yes".

Download information

Contact information