Installation Guide
2
Document History
3
1. System Requirements
2. General Considerations
When transferring object code via FTP the transport method must be set to binary.
When transferring data libraries via FTP the transport method must be set to ASCII
and the FTP client should be configured to preserve the case names of the source
files.
4
4. Installing the Package - Automated
Pre-Installation
3.1 Development Installation
The following steps are to be followed for the installation of ATM ISO8583 Development.
GR0800012Ins.tar.Z, radIns.tar.Z, is a compressed tar file that contains the Insert Files
of the development.
GR0800012lib.tar.Z, radlib.tar.Z is a compressed tar file that contains the necessary
executables (object codes) and libraries
TMNS000-GR0800012.tar.Z is a compressed data record
Do a FTP of these files in Binary mode into the “.run” directory of the area in which
you wish to install the development.
Go to the Unix Prompt from the jBASE prompt by typing the following command
$exit
JBCOBJECTLIST
5
Command Syntax - Example - Executing the .profile
In the .profile in the following line (sample displayed below - Environment specific)
export JBCOBJECTLIST=$HOME/globuspatchlib:$HOME/globuslib:$HOME/lib
Now we have successfully installed the development into the client‟s machine.
6
Login into TEMENOS GLOBUS TM.
Please refer to the Path in SCREEN SHOT (1) and make the required changes to
point to the path you wish to install
It is advised that the USER performing this action, has access to all the Companies in
the Account, if the installation is on a MULTI COMPANY Environment
The SCREEN SHOT (3) below shows a sample DL.DEFINE record IN “Verify” function.
7
Once this Record is Committed using the “Verify” function, the Data Records will get
placed into the corresponding files in IHLD Status in the $NAU Files, and in Live in
LIVE Files.
Authorizing records
Authorise all the records found in IHLD Status in the below applications,
1. PGM.FILE
2. EB.API
3. STANDARD.SELECTION
4. ENQUIRY
5. INTRF.MAPPING
6. VERSION
7. OFS.SOURCE
Post-Installation
Now, the listener plug-in to TC (Temenos Connector) needs to be installed and configured.
8
<PORT> 4002 </PORT>
</LISTENER>
(The below screen shot was taken in a windows installation for better illustration)
The adapter for this listener should be a normal T24adapter with
Note: The values in STARTIN and JBASEPATH below, are for illustration only. The
values may change depending on the implementation site.
<ADAPTER id="ATM">
<!--
<REQUEST_FORMATTER>Thai2UTF, OFSML, UTF2Thai</REQUEST_FORMATTER>
<RESPONSE_FORMATTER>Thai2UTF, OFSML, UTF2Thai</RESPONSE_FORMATTER>
-->
<MAX_SESSION> 5 </MAX_SESSION>
<MIN_SESSION> 0 </MIN_SESSION>
<TIMEOUT>30</TIMEOUT>
<LOGIN_CONTEXT></LOGIN_CONTEXT>
<STARTIN>/glois/Tempareas/priyag/bnk/bnk.run</STARTIN>
<JBASEPATH>/jbase/jbc507</JBASEPATH>
<PROGRAM>tSS</PROGRAM>
<PARAMETER>ATM</PARAMETER>
</ADAPTER>
The <PARAMETER> tag should contain the OFS.SOURCE record to be used by this
adapter.
(The below record is supplied with the package and the BUILD.CONTROL should
automatically authorise this record subject to the availability of GENERIC.USER
mentioned, the same needs to be verified. If the record is in un-authorised status the
existence of GENERIC.USER must be checked and the loginid should be changed to the
UNIX login of the environment. Both of these fields are not used by the interface but are
required just for authorising the OFS.SOURCE record.)
9
Logging setup
Logging for the interface is achieved by using monitoring adapter of TCServer used for T24
event logging. The level of logging is controlled through a parameter definition in a parameter
table called RAD.LOG.PARAMETER as shown below.
Note: All listeners are defined inside <LISTENERS> </LISTENERS> tag and all adapters are
defined inside <ADAPTERS></ADAPTERS> tag.
10
The users created must have the following sign on names and passwords if the mapping files
provided are to be used as they are.
TEMENOS01/123456,
TEMENOS02/123456
TEMENOS03/123456
TEMENOS04/123456
The interface doesn‟t force the above. If USERs are created with a different SIGN.ON.NAME
and/or PASSWORD the INTRF.MAPPING records should be changed accordingly.
Verifying installation
To make sure the configurations shown above are in place the interface can be run without
actually connecting to the switch s/w.
This can be achieved at two levels.
1. From tSS
2. From the listener
The basic program tSS needs to be run from jbase prompt and a sign on message needs to
be fed as shown.
When the listener is left unlocked the same test can be extended to one more level where the
request is fed through the listener. This is achieved using the atmsimulator if the simulator is
supplied with the package or the same can be achieved by using telnet as well.
11