Professional Documents
Culture Documents
The files to be Archived must have an entry in ARCHIVE application. Create a record in
ARCHIVE, for each set of files which must be Archived.
The second set of fields (ARC.FILENAME to MODULUS) are related multi-value fields, which
describe the Archive files to be created.
The ARC.FILENAME field indicates the names of all the $ARC files which are created based on
Type and Modulo specified. If Type and Modulo specification are not present, then $ARC files
inherits the same Type and Modulus; as the corresponding LIVE files.
The third set (COMPANY.RUN.IN to TIME.ENDED) are related multi-value fields, which are
auto populated by the system after the Contracts are archived. They maintain a history.
The FIELD.TO.CHECK field indicates the date field in the Contract, which must be compared
with the Purge date for Archiving. If this field is left blank, then the standard DATE.TIME field
is used for comparison. For example, to Archive the history records of FUNDS.TRANSFER
record, use the PROCESSING.DATE value of the Contract.
Note: If the above MAIN.FILE field is multi-valued and populated with two or more
applications, the date field mentioned in FIELD.TO.CHECK considers the application populated
in the first multi-value set.
The FILTER.RTN field is a hook routine to select or ignore a Contract for Archiving. This field
is used as an alternative to FIELD.TO.CHECK field.
For example, in FUNDS.TRANSFER the user can compare debit value date and credit
value date of the Contract and return a final date as the OUT parameter, that is compared
with purge date finally for Archival.
SKIP.FLAG (OUT Parameter 2) Returns Value 1 as the OUT parameter, to skip the
current Contract from Archiving. Value 1 confirms that the current Contract need not be
Archived. (Logic to ignore the Contract must be available in the filter routine. So, the
current Contract is skipped from being Archived).
The RELATED.FILES.RTN field is a hook routine that returns the names of related files that
have to be Archived along with the main Archival record in a dynamic array.
ID.CONTRACT (IN Parameter 1) - Record key of the main Contract that is ready to be
Archived.
GENERIC.METHOD
a. Specify 'Y' to execute generic Archival process. This allows Archival service
(ARC.GENERIC service) to take care of all selection and purging of records. For
example, FUNDS.TRANSFER, TELLER, STMT.ENTRY.DETAIL and so on; are Archived
using the generic Archival process based on the inputs provided in MAIN.FILE,
FIELD.TO.CHECK or FILTER.ROUTINE field.
This field indicates a valid multi-threaded routine that is responsible for Archiving the set of files
specified in the ARCHIVE record. These are application specific routines and should not be
changed unless a site specific program is written. For example, for FOREX, the routine is
ARC.FOREX. This record routine is responsible to decide on the Archival logic and to do
Archiving. Separate ARC.FOREX.LOAD, ARC.FOREX.SELECT routines must be available for
opening and selecting all necessary files for Archiving. However, it is not necessary to create a
separate ARC.FOREX service. It is the responsibility of ARC.GENERIC service to simply invoke
ARC.FOREX.LOAD, ARC.FOREX.SELECT, ARC.FOREX routines internally for Archiving in
the presence of ROUTINE field.
Setting Up ARC.GENERIC.REQUEST
Create a SYSTEM record in ARC.GENERIC.REQUEST and specify the ARCHIVE ID for
Archival. Upon verification of this record, ARC.GENERIC service is started in the background
and in turn it reads the ARCHIVE record. Based on the Generic.Method set-up or the application
specific ROUTINE, the records are selected for Archival. Ensure that TSM is already running.
Backups
The system in which Archiving must be run is fully backed up to tape.
Note: Archiving is a one-way process. Data cannot be restored afterwards, except by fully
restoring the database back to the point of pre-archiving.
From UNIX, change to the directory that is being backed up. For example, if the area being
backed up is BNK and the directory structure is /usr/T24/bnk/bnk.run; then enter
$cd /usr/T24
TAFJ-Runner
Introduction
tRun is the main entry point for running a program. This is a script in the /bin directory. It is used
to execute the Compiled Basic Files
tRun
Syntax
TAFJ Classpath
TAFJ is managing the classpath base on the properties file of the project. There are no need to
setup the CLASSPATH variable environment.
5. All T24 jars and folder specify with the key <temn.tafj.directory.precompile>
You can specify multiple paths separate with the separator path. : or ;. Except for the key
<temn.tafj.directory.classes> only 1 folder can be specify.
I.e.
temn.tafj.directory.precompile=/T24/Modules/GB0003:/T24/lib
Each entry has a clear state and the defined order cannot be change.
<temn.tafj.directory.classes>
<temn.tafj.runtime.classpath>
Specify where all internal jars and classpath before ext folder (3rd party jars and jdbc drivers)
will be loaded.
<TAFJ_HOME>/ext
Specify where all 3rd party jars, jdbc drivers and subfolder classpath will be loaded.
<temn.tafj.runtime.extended.classpath>
Specify where all internal jars and classpath after ext folder (3rd party jars and jdbc drivers) will
be loaded.
<temn.tafj.directory.precompile>
Specify where all T24, components and modules jars and classpath will be loaded.
TAFJ support UD tables. The root of the current directory where all UD tables is specify with the
key : temn.tafj.runtime.directory.current.
# Specify what will be considered as the "current" directory (eg in an OPEN "." ...)
temn.tafj.runtime.directory.current= <tafj.home>/UD
The default file encoding is UTF-8. You can spefify the file encoding of the UD Table with the
key : temn.tafj.runtime.ud.encoding.
In the properties file the default is:
temn.tafj.runtime.ud.encoding= UTF-8
TAFJ treat differently the directory &COMO&. You can specify where is the &COMO& folder
outside the current directory of the UD Tables with the key
: temn.tafj.runtime.directory.como.
temn.tafj.runtime.directory.como= <temn.tafj.runtime.directory.current>/&COMO&
The default file encoding (empty key) is the platform specific. You can specify the file encoding
of the UD Table with the key : temn.tafj.runtime.ud.encoding.
# default is ISO-8859-1
#temn.tafj.runtime.como.encoding = IBM-1047
TAFJ treat differently the directory &HOLD&. You can specify where is the &HOLD& folder
outside the current directory of the UD Tables with the key : temn.tafj.runtime.directory.hold.
#Specify where is the &HOLD& directory when SETPTR is used with the HOLD option
temn.tafj.printer.directory.hold = <temn.tafj.runtime.directory.current>/&HOLD&
TimeZone represents a time zone offset, and also figures out daylight savings. You can set the
Timezone with the key: temn.tafj.runtime.timezone.
In the properties file the default is:
temn.tafj.runtime.timezone=
A Locale object represents a specific geographical, political, or cultural region. An operation that
requires a Locale to perform its task is called locale-sensitive and uses the Locale to tailor
information for the user. You can set the Local with the key: temn.tafj.runtime.local.
temn.tafj.runtime.local= en_US
By convention a JBC command : EXECUTE PHANTOM will forks a new OS Process with a
new instance of a JVM (Java Virtual Machine). For performance raison you can define with the
key temn.tafj.runtime.phantom.as.process to execute the new process as a thread in the current
JVM.
# be more efficient.
temn.tafj.runtime.phantom.as.process= true
When the new process forks a new JVM, you have to specify the environment of the JVM with
options. Use the key: temn.tafj.runtime.new.process.params
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
-esa | -enablesystemassertions
-dsa | -disablesystemassertions
-agentlib:<libname>[=<options>]
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
-splash:<imagepath>
By properties, you can specify the default precision for the runtime with the
key: temn.tafj.runtime.default.precision.
temn.tafj.runtime.default.precision =4
# Rounding Mode for operands : HALF_UP(Default) (2.25 -> 2.3 and 2.24 -> 2.2)
temn.tafj.runtime.rounding.mode= HALF_UP
# Rounding Mode result : HALF_UP(Default) (2.25 -> 2.3 and 2.24 -> 2.2)
temn.tafj.runtime.rounding.mode.result= DOWN
If TAFJ is install on a Mainframe (zOS), you need to specify to true the key:
temn.tafj.runtime.zos.mode. It will avoid the INPUT statement with timer. (not allow on zOS).
Set the correct encoding for logger in TAFJTrace.properties and COMO encoding.
temn.tafj.runtime.zos.mode= false
# just throwing the exception (in case of TAFJ is used like an API)
temn.tafj.runtime.exception.mode= false
temn.tafj.runtime.clean.on.shutdown= true
# By default data files loaded require manual authorization.
# When set to false data are uploaded directly in the LIVE table
temn.tafj.runtime.authorize.record= true
TAFJ Performance
For Performance raison, and if you are not in development environment you have to active some
cache and stop TAFJ to have the capability to debug code.
temn.tafj.runtime.enable.debug = true
temn.tafj.runtime.enable.cached.opf= false
temn.tafj.runtime.use.cache.get= false
TAFJ has the capability to redirect API message to the logger API (T24) to the JMS Topic
Queue with the key : temn.tafj.runtime.enable.logger.api.jms
# Enable the Logger api for TEC Items recording using JMS (used by T24Monitor)
temn.tafj.runtime.enable.logger.api.jms= false
TAFJ has the capability to disable any T24 Logger API or TEC. With the key:
temn.tafj.runtime.enable.logger.api and the key: temn.tafj.runtime.disable.tec
temn.tafj.runtime.enable.logger.api= true
temn.tafj.runtime.disable.tec = false
#********************************************************************
# JIMI
#********************************************************************
temn.tafj.runtime.jimi.on = 0
temn.tafj.runtime.directory.jimi = <temn.tafj.runtime.directory.current>
temn.tafj.runtime.jimi.append= false
temn.tafj.runtime.jimi.image.index= 1
TAFJ Monitor
To use TAFJ Monitor, TAFJSessionMonitor have to be up and running on the network. TAFJ
with the following properties will send all the information to the TAFJSessionMonitor. Read the
section TAFJSessionMonitor to know how setup and start the monitor.
#********************************************************************
# TAFJ Monitor
#********************************************************************
temn.tafj.runtime.session.monitor.enable = true
temn.tafj.runtime.session.monitor.host=localhost
# TCP port of the TAFJMonitorSession
temn.tafj.runtime.session.monitor.port=8377
TAFJ Printer
On Windows, JPS use the Printer Manager. You can connect any printers installed on Windows.
The Printer has to be online.
On UNIX/LINUX, JPS use CUPS (Common Unix Printing System). CUPS is not install by
default. You have to install it. Please refer to your OS documentation for the installation.
In the properties file, category printer, the setup of TAFJ automatically adds your printers online
with default driver name PRN #. You can affect the channel to any drivers name.
You can affect 256 channels to different printer with the key: temn.tafj.channel.name.#. # is
the number of the channel.
The name you affect to the key have to match the name of the driver.
i.e
temn.tafj.channel.name.0 = PRN2
To find the devices online on your OS, use the command tFindDevice.
__________________________________________________________________
__________________________________________________________________
Default printer : >HP Officejet Pro 8600 (Network)<
Printer 5 : >Fax<
__________________________________________________________________
Chose the device you want and add to the properties file:
temn.tafj.driver.class.# = com.temenos.tafj.jlp.drivers.jPrinterDriver
i.e.
temn.tafj.channel.name.0 = PRN0
temn.tafj.channel.name.1 = PR23
temn.tafj.channel.name.2= PRN1
temn.tafj.driver.name.0 = PRN0
temn.tafj.driver.class.0 = com.temenos.tafj.jlp.drivers.jPrinterDriver
temn.tafj.driver.name.1 = PRN1
temn.tafj.driver.name.2 = PRN2
temn.tafj.driver.class.2 = com.temenos.tafj.jlp.drivers.jPrinterDriver
TAFJ DataBase
TAFJ use JDBC to connect and use a database. Short for Java Database Connectivity, a Java API
that enables Java programs to execute SQL statements. This allows Java programs to interact
with any SQL-compliant database. Since nearly all relational database management systems
(DBMSs) support SQL, and because Java itself runs on most platforms, JDBC makes it possible
to write a single database application that can run on different platforms and interact with
different DBMSs. JDBC is similar to ODBC, but is designed specifically for Java programs,
whereas ODBC is language-independent.
temn.tafj.jdbc.url
temn.tafj.jdbc.driver
temn.tafj.jdbc.username
temn.tafj.jdbc.password
The password
i.e.
#********************************************************************
# Database setup
#
#********************************************************************
# ex. ms-sql:
jdbc:sqlserver://<host_or_ip>:1433;databaseName=<db_name>;integratedSecurity=true
# ex. H2(Embedded):jdbc:h2:<path_to_my_db>
temn.tafj.jdbc.url= jdbc:db2://158.35.69.124:50000/t24mb
temn.tafj.jdbc.driver= com.ibm.db2.jcc.DB2Driver
temn.tafj.jdbc.username = tafjdb
temn.tafj.jdbc.password = secret
!! WARNING !!
You need the specific database drivers you are targeting to go in <TAFJ_HOME>/ext. Please
find these drivers in <TAFJ_HOME>/dbdrivers and copy them to <TAFJ_HOME>/ext
i.e for oracle 11g database
TAFJ LockManager
To configure the client system to use the Distributed Lock Service, each client user must be
configured with the TAFJ Locking mechanism.
To be properly effective ALL users of the same database must be configured with exactly the
same
Distributed Lock Service parameters, otherwise locks will NOT be correctly respected and data
inconsistencies may occur.
temn.tafj.locking.mode
temn.tafj.locking.hostname
Hostname or the IP address of the system where the Distributed Lock Service is executing.
temn.tafj.locking.port
The socket port number on which TAFJ Distributed Lock service is listening.
temn.tafj.locking.callstack
temn.tafj.locking.name
1. MEM :
The LockManager is part of the same JVM than the process running.
High Performance.
The LockManager is a table in the database. The name of the table use for the lock is
LOCK_RECORDS
Poor performance.
3. PROC / PROCHASH
The PROCHASH is the same mechanism as PROC but the lock is a hash. It cannot be monitor.
Good Performance.
4. ORCL / MSQL
The LockManager use the lock engine of the database via an API.
Good Performance.
tDiag is part of the TAFJ tools. It allows to easily get information about your environment like
the java version, the TAFJ version, The tDiag utility is used to display information about your
TAFJ installation and projects setup. It is useful in pin-pointing problem areas of the setup.
Syntax
extract
Example
tDiag
__________________________________________________________________
Home : 'D:\Temenos\T24Enterprise\TAFJ'
Version : DEV_201404
__________________________________________________________________
java.home : D:\Temenos\T24Enterprise\3rdParty\java\jdk1.7.0_51-64\jre
os.arch : amd64
os.name : Windows 7
HostName : wkshome01
IP Address : 10.244.1.137
__________________________________________________________________
- Project : 'tafj'
------------------------------------------------------------------
------------------------------------------------------------------
DataBase URL :
DataBase user :
------------------------------------------------------------------
Locking name :
------------------------------------------------------------------
UD encoding : UTF-8
------------------------------------------------------------------
Timezone : Europe/London
Local : en_US
------------------------------------------------------------------
------------------------------------------------------------------
tShow
Introduction
tShow is part of the TAFJ tools. It allows finding easily where your BASIC source has been
compiled, when and on what machine it has been compiled. It can search for the resource on one
single project and multiple ones.It can also produce a report of all the duplicate classes when run
with d argument.
Syntax
Example
tShow CACHE.READ
It will, for all projects in your distribution, try to load the java class for CACHE.READ
(CACHE_READ_cl.class), and get information like:
Home : 'D:\Temenos\T24Enterprise\TAFJ'
on : GVAL1201010
Timestamp : 1342072107042
Grammar : 1
tShow -d
tShowCheck
Introduction
tShowCheck is part of the TAFJ tools. It allows to find out easily whether all the BASIC source
files have been compiled successfully. It reports the error and warning messages to a flat file if a
class is found missing in the precompiled or in the classes folder.
-s <PATH_OF_SOURCE_FOLDER>
-p <PATH_OF_PRECOMPILED> or <PATH_OF_CLASSES_FOLDER>
-r <PATH_OF_REPORT_FOLDER>
Syntax
Example
******************************************************************************
******
tCrypt
Introduction
tCrypt is part of the TAFJ tools. It allows encrypting the password specified in
temn.tafj.jdbc.password. This will encrypt the password with DES3 Algorithm. The key used to
encrypt is auto generated and stored in a file called .key in the conf directory of your TAFJ
installation.
Syntax
extract
Example
To get encrypt the password for the database mentioned in configuration file
C:\TAFJ\bin>tCrypt
Configuration: 'C:\TAFJ\bin\..\conf\tafj.properties'
C:\TAFJ\bin>
temn.tafj.jdbc.username = t24
temn.tafj.jdbc.password = secret
temn.tafj.jdbc.username = t24
temn.tafj.jdbc.password = ::P6PeGkfV134=
tFindDevice
Introduction
tFindDevice is part of the TAFJ tools. It allows to easily getting information about your Default
Printer on your System and a list of printers which are available on your system.
Syntax
tFindDevice
extract
Example
tFindDevice
__________________________________________________________________
__________________________________________________________________
Printer 5 : >Fax<
__________________________________________________________________
This document describes the T24 Operational Performance (tOP) monitoring tool.
Intended Audience
This User Guide is intended for the use of Internal Temenos users and Clients.
Overview
tOP is the new performance monitoring tool which supersedes T24 Monitor. tOP is built as an
add-on to the industry standard splunk product (www.splunk.com)
1. Captures indexes and correlates real-time data in a searchable repository from which it
can generate graphs, reports, alerts, dashboards and visualizations. It will produce
software for searching, monitoring, and analyzing machine-generated big data, via a web-
style interface.
2. Performs real-time and historical search, as well as reporting and statistical analysis.
4. Logs can also be forwarded to remote machine that has splunk installed using splunk
universal forwarder
Prerequisites
The tOP (Splunk App for T24) is dependent on the Splunk Enterprise platform, which must be
installed and configured prior to installing and deploying the Splunk App for tOP.
Getting Started
Splunk is pre-configured in Windows Model bank area.
Start splunk by choosing Start->Model Bank R13.2->Utilities->T24 Splunk. The jBoss server
should be started before starting splunk
Login with username admin and password 123456
UNIX Installation
The following steps must be followed to setup SPLUNK in UNIX area with T24 already
installed.
The applications for SPLUNK are available in the folder splunk/etc/apps. Hence the tOP
application should be extracted in this directory.
Create the file inputs.conf in the folder splunk/etc/apps/tOP/local. Specify the logs that
are the inputs for SPLUNK and the absolute path where the logs are available. Comment
logs as required
Go to splunk/binStart the SPLUNK using splunk start. This command will start SPLUNK
and give an address to access SPLUNK web interface. License will be displayed when
SPLUNK is started for the first time.
Access the SPLUNK interface using above address
You can now access SPLUNK dashboard.
T24 Dashboards
tOP Home dashboard page displays following information for the selected time frame
T24 User information, T24 System Information, Transaction Timeout Error information
The graph is displayed and the details of the jobs are also listed below.
Services Menu -> Job Statistics
Job statistics under Services Menu displays the throughput for the jobs of the selected batch and
company for the chosen time frame. Click on graph to drill down and view details.
Services Menu -> Job Timing Compare
The time taken by a Job during different COB runs can be compared using this option.
Services Menu -> Job Times
Select the time frame for which Job Times information is required. Detailed information about
the jobs is displayed in the report
Services menu -> TSA Agent Status
Select the time frame and service name under TSA Agent Status option of Services menu to view
details of the selected agent.
This document is intended for the Performance and Monitoring tool for T24 known as tOP. tOP
is based on a standard monitoring solution known as splunk.
Intended Audience
This User Guide is intended for the use of Internal Temenos users and Clients.
Overview
Splunk captures, indexes and correlates real-time data in a searchable repository from which it
can generate graphs, reports, alerts, dashboards and visualizations. It'll produces software for
searching, monitoring, and analyzing machine-generated big data, via a web-style interface.
Splunk can perform real-time and historical search, as well as reporting and statistical analysis.
Splunk can index structured or unstructured textual machine-generated data. Search and analytics
operations are specified using SPL (Search Processing Language), created for managing
machine-generated big data. Originally based upon Unix Piping and SQL, its scope includes data
searching, filtering, modification, manipulation, insertion, and deletion.
Prerequisite
The tOP (Splunk App for T24) is dependent on the Splunk Enterprise platform, which must be
installed and configured prior to installing and deploying the Splunk App for tOP.
Splunk Enterprises
Splunk for Windows 5.0.1 or later
Windows 7 x64
Other MacOSX
Browsers
IE 7, 8, 9 and 10
Firefox
Firefox 3
Google Chrome
Safari 5
Splunk Dependency
The tOP requires the Sideview Utils plugin to function correctly.
Deployment
Splunk Installation
Splunk Manual Installation Method
Download Splunk from http://www.splunk.com. You have to be a valid user of Splunk or create
a new user to download Splunk. Install Splunk and login. On the first login, you will be required
to change the default password. Follow the below steps to deploy T24 app.
2. Select Apps
6. After installing sideview utils install T24 app - Click on "Install app from file".
7. Select T24.spl file and click on "Upload".
8. T24 app is now deployed in Splunk Start T24 appfrom main screen or the App Menu
Script Based Installation
1. Extract the splunk_t24.zip package in temp or any other folder.
6. Now launch your favorite browser and open default URL [http://127.0.0.1:8000]
3. Start the Splunk forwarder application from the Splunk bin directory
./splunk start
confirm the license agreement and reserve port.
6. Restart splunk server to take effects from the Splunk bin directory.
./splunk restart
Enable Receiver
Skip this section, if the log data and Splunk server reside on the same machine.
To send data from another machine, enable receiver from Splunk Web.
Follow steps below to enable Splunk receiver.
1. Select Manager
Configuration
Before starting to monitor or analyse log file data, configure the log file/directory path in Splunk
and enable logging from tafc.ini or other configuration files.
Model Bank
The following configuration is based on the Model bank package. Any change must be made
according to your model bank configuration. Before starting T24 app you need to configure
inputs.conf. This can be done using a batch file or manually. Both methods are given below;
1. Extract splunk package in a directory and set the following environment variables
a. TAFC_HOME
b. JBOSS_HOME
c. JBOSE_IP
d. JBOSE_PORT
4. Navigate to Splunk Home tab or App menu and make sure T24 Application is listed
there.
# For Windows OS
# [monitor://%TAFC_HOME%\log\default]
[monitor:/$TAFC_HOME/log/default]
sourcetype = tafc_log
blacklist = WARNING|ERROR|FATAL
# jBOSS log
#
# For Windows OS
# [monitor://%ModelBankPath%\jboss-5.1.0.GA\server\default\log\server.log]
[monitor:/$ModelBankPath/jboss-5.1.0.GA/server/default/log/server.log]
sourcetype = jboss_log
# TAFC.ini
# For Windows OS
# [monitor://% TAFC_HOME%\config\default\tafc.ini]
[monitor:/$TAFC_HOME/config/default/tafc.ini]
sourcetype = tafc_ini
[common]
[logger]
LOGGING=FILE
MINLOGLEVEL_FILE=INFO
[jBC]
LOGGING=FILE
MINLOGLEVEL_FILE=INFO
Note: Do not remove your any existing setting. If the above settings already exist, override them
alone.
[common]
[logger]
LOGGING=FILE
MINLOGLEVEL_FILE=INFO
[jBC]
LOGGING=FILE
MINLOGLEVEL_FILE=INFO
Note: Do not remove your any existing setting. If the above settings already exist, override them.
T24 Infrastructure
Hardware Specifications
1. ComServ
Noname Machine
2. WebSrv01 &02
DELL LATITUDE E6400
3. JmsSrv01 & 02
4. AppSrv01 & 02
5. Network
100 Mb Network
6. Subnet
192.168.1.0
255.255.255.0
7. Gateway
192.168.1.5
8. Internet connection
Upload:up to 15 Mbit/s
9. DNS
192.168.1.5
This hardware was setup in the Temenoss data Center of Pampigny at Swizerland.
This infrastructure is a 5 layers.
This run-book will NOT describe how setup and configure this layer
Application Layer (AppSrv01 and AppSrv02)
This layer contains the Application Servers with Channels (BrowserWeb, TWS,
TOCFEE, TCIB,)
Layer
4
This is the topmost level of the application. The presentation tier displays information
related business services. It communicates with other tiers by which it puts out the results
to the browser/client tier and all other tiers in the network. (In simple terms it is a layer
which users can access directly such as a web page, or an operating systems GUI)
Load Balancer Layer (ComSrv01)
This layer contains the Load balancer the NTP Server and the NFS Server Layer load
balancing operates at the intermediate transport layer, which deals with delivery of
Layer
messages with no regard to the content of the messages. Transmission Control Protocol
5
(TCP) is the Layer 4 protocol for Hypertext Transfer Protocol (HTTP) traffic on the
Internet. Layer 4 load balancers simply forward network packets to and from the upstream
server without inspecting the content of the packets. They can make limited routing
decisions by inspecting the first few packets in the TCP stream.
This infrastructure is built to cover all scenarios of T24 Solution installation and configuration.
This run-book will describe step by step how install and configure all scenarios with each
different product (3rd party software) on Oracle Linux 7.1 based.
The scenarios are:
You will have to adapt your installation and your configuration based on your
infrastructure.
Choose your scenario and your products (3rd party software) then follow step-by-step the
order of the installation process.
T24 Compile is java is certify JEE Compliant. Officially it can be install and configure
with any JEE product certify. If you have to configure a product not in this list you will
have to learn by yourself, that is; JBoss with OpenMQ
If you have to mix a stack (WebPhere as Web Layer and WebLogic as App Layer), you
will have to mix yourself the step-by-step installation process. All is in this runbook.
LINUX installation
On all machine, Oracle Linux 7.1 is installed. Downloaded from oracle website. (image :
V74844-01.iso
Software Installation
Base Environment
FTP Server
Partitions
Hostname : AppSrv01.temenos.com
LINUX configuration
Network configuration
If you want to set up a static IP address on a network interface, there are several different ways to
do it, varying depending on whether or not you want to use Network Manager for that.
Network Manager is a dynamic network control and configuration system that attempts to keep
network devices and connections up and active when they are available). Oracle Linux 7 comes
with Network Manager service installed and enabled by default.
Save changes and restart the network service using the following command:
Adding Users
If you are signed in as the root user, you can create a new user at any time by typing:
If you are signed in as a non-root user who has been given sudo privileges, as demonstrated in
the next section of this tutorial, you can add a new user by typing:
Next, you'll need to give your user a password so that they can log in. To do so, use the passwd
command:
Note: Remember to add sudo ahead of the command if you are signed in as a non-root user with
sudo privileges.
You will be prompted to type in the password twice to confirm it. Now your new user is set up
and ready for use! You can now log in as that user, using the password that you set up.
If your new user should have the ability to execute commands with root (administrative)
privileges, you will need to give the new user access to sudo.
We can do this by adding the user to the wheel group (which gives sudo access to all of its
members by default) through the gpasswd command. This is the safest and easiest way to
manage sudo user rights.
Now your new user is able to execute commands with administrative privileges. To do so,
simply type sudo ahead of the command that you want to execute as an administrator:
You will be prompted to enter the password of the regular user account that you are signed in as.
Once the correct password has been submitted, the command you entered will be executed with
root privileges.
While you can add and remove users from a group (such as wheel) with gpasswd, the command
doesn't have a way to show which users are members of a group. In order to see which users are
part of the wheel group (and thus have sudo privileges by default), you can use the lid function.
lid is normally used to show which groups a user belongs to, but with the '-g' flag, you can
reverse it and show which users belong in a group:
The output will show you the usernames and UIDs that are associated with the group. This is a
good way of confirming that your previous commands were successful, and that the user has the
privileges that they need.
Deleting Users
If you have a user account that you no longer need, it's best to delete the old account. You have a
couple of methods to do so, though the choice of which method to use depends on your own
situation.
If you want to delete the user without deleting any of their files, type this command as root:
If you want to delete the user's home directory along with the user account itself, type this
command as root:
Note: Remember to add sudo ahead of the command if you are signed in as a non-root user with
sudo privileges.
With either command, the user will automatically be removed from any groups that they were
added to, including the wheel group if they were given sudo privileges. If you later add another
user with the same name, they will have to be added to the wheel group again to gain sudo
access.
LINUX configuration
Network configuration
If you want to set up a static IP address on a network interface, there are several different ways to
do it, varying depending on whether or not you want to use Network Manager for that.
Network Manager is a dynamic network control and configuration system that attempts to keep
network devices and connections up and active when they are available). Oracle Linux 7 comes
with Network Manager service installed and enabled by default.
If the output of nmcli shows "connected" for a particular interface (e.g., em1 in the example), it
means that the interface is managed by Network Manager. You can easily disable Network
Manager for a particular interface, so that you can configure it on your own for a static IP
address.
In the above, "NM_CONTROLLED=no" indicates that this interface will be set up using this
configuration file, instead of being managed by Network Manager service. "ONBOOT=yes" tells
the system to bring up the interface during boot.
Save changes and restart the network service using the following command:
Users configuration
Adding Users
If you are signed in as the root user, you can create a new user at any time by typing:
If you are signed in as a non-root user who has been given sudo privileges, as demonstrated in
the next section of this tutorial, you can add a new user by typing:
Next, you'll need to give your user a password so that they can log in. To do so, use the passwd
command:
Note: Remember to add sudo ahead of the command if you are signed in as a non-root user with
sudo privileges.
You will be prompted to type in the password twice to confirm it. Now your new user is set up
and ready for use! You can now log in as that user, using the password that you set up.
If your new user should have the ability to execute commands with root (administrative)
privileges, you will need to give the new user access to sudo.
We can do this by adding the user to the wheel group (which gives sudo access to all of its
members by default) through the gpasswd command. This is the safest and easiest way to
manage sudo user rights.
If you are signed in using a non-root user with sudo privileges, type this instead:
Now your new user is able to execute commands with administrative privileges. To do so,
simply type sudo ahead of the command that you want to execute as an administrator:
You will be prompted to enter the password of the regular user account that you are signed in as.
Once the correct password has been submitted, the command you entered will be executed with
root privileges.
Managing Users with Sudo Privileges
While you can add and remove users from a group (such as wheel) with gpasswd, the command
doesn't have a way to show which users are members of a group. In order to see which users are
part of the wheel group (and thus have sudo privileges by default), you can use the lid function.
lid is normally used to show which groups a user belongs to, but with the '-g' flag, you can
reverse it and show which users belong in a group:
The output will show you the usernames and UIDs that are associated with the group. This is a
good way of confirming that your previous commands were successful, and that the user has the
privileges that they need.
Deleting Users
If you have a user account that you no longer need, it's best to delete the old account. You have a
couple of methods to do so, though the choice of which method to use depends on your own
situation.
If you want to delete the user without deleting any of their files, type this command as root:
If you want to delete the user's home directory along with the user account itself, type this
command as root:
Note: Remember to add sudo ahead of the command if you are signed in as a non-root user with
sudo privileges.
With either command, the user will automatically be removed from any groups that they were
added to, including the wheel group if they were given sudo privileges. If you later add another
user with the same name, they will have to be added to the wheel group again to gain sudo
access.
As all the installations will be from a remote Telnet SSH connection we need to install the tool
Xorg-x11-apps on Server to provide the X11 forwarding to the Telnet client like SecureCRT or
PUTTY. On the Windows client you need to install Xming
Install Xorg-x11-apps
Command:
Install xming
Execute the installation package Xming and leave all default option.
Run Xming
Telnet Client
With Putty
Enable in Menu Putty Configuration -> Connection -> SSH -> X11 the checkbox Enable X11
forwarding.
With SecureCRT
Enable in Menu Session Options -> Connection -> Port Forwarding -> Remote/X11 the
checkbox Forward X11 packets.
Test Xorg-x11-apps / Xming
Command:
Most servers are probably automatically configured to internet network time. But sometime the
servers have no access to it. In this case, a NTP server have to be created in the infrastructure and
force all other servers to synchronize to it.
In the infrastructure the ComSrv01 will be dedicate to have the NTP Server
Install NTP package on all server using the appropriate package management tool.
Command:
Configure NTP Server
After the server is installed, first go to official NTP Public Pool Time Servers, choose your
Continent area where the server physically is located, then search for your Country location and
a list of NTP servers should appear.
On NTP Servers with root user.
Edit the /etc/ntp.conf file, which is quite possibly already filled out for you.
Youll find a lot of lines in there, but the important ones are the server lines. Comment the
default list of Public Servers from pool.ntp.org project and replace it with the list provided for
your country like in the screenshot below. For my purposes, that meant:
Allow clients from your networks to synchronize time with this server. To accomplish this, add
the following line to NTP configuration file, where restrict statement controls, what network is
allowed to query and sync time replace network IPs accordingly.
The nomodify notrap statements suggest that your clients are not allowed to configure the server
or be used as peers for time sync.
Add information for troubleshooting in case there are problems with your NTP daemon add a log
file statement which will record all NTP server issues into one dedicated log file.
After you have edited the file with all configuration explained above save and close ntp.conf file.
Your final configuration should look like in the screenshot below.
NTP service uses UDP port 123 on OSI transport layer (layer 4). It is designed particularly to
resist the effects of variable latency (jitter). To open this port on RHEL/CentOS 7 run the
following commands against Firewalld service.
Command:
After you have opened Firewall port 123, start NTP server and make sure you enable it system-
wide. Use the following commands to manage the service.
Verify Server Time Sync
If you want to query and synchronize against a pool of your choice use ntpdate command,
followed by the server or servers addresses, as suggested in the following command line
example.
Configure NTP Client to Synchronize with NTP Server
Edit the /etc/ntp.conf file, which is quite possibly already filled out for you.
To synchronize the time of your local Linux client machine with NTP server, edit the
/etc/ntp.conf file on the client side. Youll find a lot of lines in there, but the important ones are
the server lines. Comment the default list of Public Servers from pool.ntp.org project and replace
it with the NTP Server. For my purposes, that meant:
Prefer: If this option is specified that server is preferred over other servers. A response from the
preferred server will be discarded if it differs significantly different from other servers
responses.
Once the ntp.conf is configured with correct settings, start the ntp daemon.
Check the NTP Status
Check the status of NTP using the ntpq command. If you get any connection refused errors then
the time server is not responding or the NTP daemon/port is not started or listening.
Command:
The ntpdate command can be used to set the local date and time by polling the NTP server.
Typically, youll have to do this only one time.
Your jitter value should be low, else check the drift from the clock in the driftfile. You may also
need to change to some other NTP server based on the difference. This command synchronizes
the time with your NTP server manually.
After this initial sync, NTP client will talk to the NTP server on an on-going basis to make sure
the local time reflects the accurate time.
You can also use the following command to get the current status of ntpd.
On each server we have to define a folder to install the Temenos solution. We need to check the
where we can install it and the space left.
Command:
Change the owner and the permission to the t24user to this folder
Command:
In our infrastructure we will install 3rd party software like java, WebSphere, Weblogic. All
no Temenos software will be installing in the 3rdParty folder
Only on all servers in an Application Layer (AppSrv01 and AppSrv02), with t24user user.
Edit file .bach_profile and set the environment variable $TAFJ_HOME and $T24_HOME
We will not install on this infrastructure other Temenos products. If you want to install other
Temenos Product like AML, TAP (Triple A),..
Command:
Command:
On NFS server we will define $TEMENOS_HOME/Install as a share folder
Command:
Note: 192.168.1.0 is the subnet of all client machine, if you wish a specific client should access it
only, you need to specify the IP of the client, otherwise you can add "*" instead of IP for all IP
access
Check
NFS service uses UDP port on OSI transport layer (layer 4). It is designed particularly to resist
the effects of variable latency (jitter). To open this port on RHEL/CentOS 7 run the following
commands against Firewalld service.
Command :
Command:
Start NFS Deamon
Command :
Next we will mount the NFS shared content in the client machine as shown below:
Command :
Restart your server and check if the drive is mounted
Command :
Command:
NFS Share T24 and TAFJ folder (not mandatory, not recommended)
Warning: NFS have a bad performance compare to local disk access. For performance
infrastructure, do not share TAFJ and T24 on NFS. This is only to use with a Cluster on the
Applcation layer.
Command:
Start NFS Deamon
Command:
Note: 192.168.1.0 is the subnet of all client machine, if you wish a specific client should access it
only, you need to specify the IP of the client, otherwise you can add "*" instead of IP for all IP
access.
Check
In $TEMENOS_HOME/TAFJ create a file test.
NFS service uses UDP port on OSI transport layer (layer 4). It is designed particularly to resist
the effects of variable latency (jitter). To open this port on RHEL/CentOS 7 run the following
commands against Firewalld service.
Command:
Command :
Next we will mount the NFS shared TAFJ content in the client machine as shown below:
Next we will mount the NFS shared T24 content in the client machine as shown below:
Command :
Restart your server and check if the drive is mounted.
Command :
Check the permanent mount
Command :
Warning: This is for advanced user. The goal is to share a TAFJ for uid (PortNumber) and
properties file. But the lib, ext and log folders will have a local copy set to the application server.
This is only to use with a Cluster on the Application layer. This is very convenient (about zero
administration) and a very good performance.
Command:
Command :
Note: 192.168.1.0 is the subnet of all client machine, if you wish a specific client should access it
only, you need to specify the IP of the client, otherwise you can add "*" instead of IP for all IP
access
Check
NFS service uses UDP port on OSI transport layer (layer 4). It is designed particularly to resist
the effects of variable latency (jitter). To open this port on RHEL/CentOS 7 run the following
commands against Firewalld service.
Command :
Command:
Next we will mount the NFS shared TAFJ content in the client machine as shown below:
Command :
Restart your server and check if the drive is mounted.
Command :
The next step of the setup NFS Share TAFJ (mix) folder will be describe in the step by step
configuration of a cluster for the Application Layer.
Command:
Command :
$TEMENOS_HOME/3rdParty/Jms/MQ/mqshare
Command :
Change the owner and the permission to the t24user to this folder
Note: 192.168.1.0 is the subnet of all client machine, if you wish a specific client should access it
only, you need to specify the IP of the client, otherwise you can add "*" instead of IP for all IP
access
Check
NFS service uses UDP port on OSI transport layer (layer 4). It is designed particularly to resist
the effects of variable latency (jitter). To open this port on RHEL/CentOS 7 run the following
commands against Firewalld service.
Command
On all servers part of the MQ Cluster except NFS Server with root user.
Command:
Command :
$TEMENOS_HOME/3rdParty/Jms/MQ/mqshare
On all servers part of the MQ Cluster except NFS Server with root user.
Command :
Change the owner and the permission to the t24user to this folder
Next we will mount the NFS shared TAFJ content in the client machine as shown below:
Check the file test we created
On all servers part of the MQ Cluster except NFS Server with root user.
Command :
Command :
ools Installation
KSH Installation
KornShell (ksh) is a Unix shell. KornShell is backward-compatible with the Bourne shell and
includes many features of the C shell, inspired by the requests of Bell Labs users. This is zje
default shell used by TAFJ.
NMAP Install
Nmap (Network Mapper) is a security scanner used to discover hosts and services on a computer
network, thus creating a "map" of the network. To accomplish its goal, Nmap sends specially
crafted packets to the target host and then analyzes the responses.
On all servers, with root user.
# nmap -v 127.0.0.1
NMON Installation
nmon (short for Nigel's Monitor) is a Performance system monitor tool for the AIX and Linux
operating systems.
# wget http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
nmon includes support for older AIX releases, Linux running on x86, POWER and
Mainframe platforms
# nmon
NLOAD Install
nload is a console application which monitors network traffic and bandwidth usage in real time.
It visualizes the in- and outgoing traffic using two graphs and provides additional info like the
total amount of transferred data and min/max network usage.
# nload
HTOP Installation
htop is an interactive system-monitor process-viewer written for Linux. It is designed as an
alternative to the Unix program top.
# wget http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
# htop
IFTOP Installation
Iftop is a command-line system monitor tool that produces a frequently-updated list of network
connections. By default, the connections are ordered by bandwidth usage, with only the "top"
bandwidth consumers shown.
Iftop listens to network traffic on a named interface and displays a table of current bandwidth
usage by pairs of hosts. Handy for answering the question 'why is our ininternet connection so
slow?'".
# wget http://pkgs.repoforge.org/iftop/iftop-0.17-1.el6.rf.x86_64.rpm
# iftop
HELP MENU
Port Display:
L - linear/log scales
! - shell command
q - quit
JDK installation
From http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
# mkdir -p $TEMENOS_HOME/3rdParty/Java
# cd $TEMENOS_HOME/3rdParty/Java
# cp $TEMENOS_HOME/Install/jdk-7u79-linux-x64.tar.gz $TEMENOS_HOME/3rdParty/Java
Extract jdk-7u79-linux-x64.tar.gz
# ls -ail
Delete jdk-7u79-linux-x64.tar.gz
# rm jdk-7u79-linux-x64.tar.gz
# cd
# vi .bash_profile
Close your session and login again with t24user
linuxamd64_12102_database_1of2.zip
linuxamd64_12102_database_2of2.zip
# su - root
The /etc/hosts file must contain a fully qualified name for the server.
# vi /etc/hosts
Add groups
# passwd oracle
unixODBC-devel zlib-devel
Install missing packages.
fs.file-max = 6815744
kernel.shmmni = 4096
kernel.shmall = 1073741824
kernel.shmmax = 4398046511104
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
fs.aio-max-nr = 1048576
kernel.panic_on_oops=1
# cat /proc/sys/fs/file-max
# cat /proc/sys/kernel/sem
# cat /proc/sys/kernel/shmmni
# cat /proc/sys/kernel/shmall
# cat /proc/sys/kernel/shmmax
# cat /proc/sys/net/core/rmem_default
# cat /proc/sys/net/core/rmem_max
# cat /proc/sys/net/core/wmem_default
# cat /proc/sys/net/core/wmem_max
# cat /proc/sys/fs/aio-max-nr
# cat /proc/sys/net/ipv4/ip_local_port_range
# cat /proc/sys/kernel/panic_on_oops
To modify a value
# sysctl -w fs.file-max=6815744
# sysctl -w kernel.shmmni=4096
# sysctl -w kernel.shmall=1073741824
# sysctl -w kernel.shmmax=4398046511104
# sysctl -w net.core.rmem_default=262144
# sysctl -w net.core.rmem_max=4194304
# sysctl -w net.core.wmem_default=262144
# sysctl -w net.core.wmem_max=1048576
# sysctl -w fs.aio-max-nr=1048576
# sysctl -w kernel.panic_on_oops=1
# sysctl -p
Add following lines to set shell limits for user oracle in file /etc/security/limits.conf
# vi /etc/security/limits.conf
# vi /etc/pam.d/login
Modify /etc/selinux/config and change flag SELINUX. Restart server after this change.
Open the file "/etc/selinux/config "
# vi /etc/selinux/config
Disable firewall
# cd
# vi .bash_profile
On all servers in DB Layer, with root user.
ORACLE_BASE = $TEMENOS_HOME/3rdParty/Db/Oracle
# mkdir -p $TEMENOS_HOME/3rdParty/Tools/Oracle/oraInventory
# shutdown -r
In Oracle Enterprise Linux 7 /tmp data is stored on tmpfs which consumes memory and is too
small. To revert it back to storage just run following command and REBOOT machine to be
effective.
# su - oracle
# cd $TEMENOS_HOME/Install
# unzip linuxamd64_12102_database_1of2.zip
# unzip linuxamd64_12102_database_2of2.zip
# cd $TEMENOS_HOME/Install/database
# ./runInstaller
Click "Next" Button.
# /u01/Temenos/3rdParty/Db/Tools/Oracle/oraInventory/orainstRoot.sh
# /u01/Temenos/3rdParty/Db/Oracle/product/12.1.0/db_1/root.sh
Click "OK" Button.
DB2_ESE_10_Linux_x86-64.tar.gz
# su root
The /etc/hosts file must contain a fully qualified name for the server.
# vi /etc/hosts
# mkdir $TEMENOS_HOME/Install/db2inst
# cd $TEMENOS_HOME/Install
# cd /u01/Temenos/Install/db2inst/ese
# ./db2setup
Select "Install a Product" and Click Install New Button.
Select "Do not create a DB2 instance" and click the "Next"
Click "Next" Button.
# cd
# vi .bash_profile
# mkdir -p $TEMENOS_HOME/3rdParty/Db/H2
# cd $TEMENOS_HOME/Install
Start the H2 installer
# unzip $TEMENOS_HOME/Install/h2-2014-04-05.zip -d
$TEMENOS_HOME/3rdParty/Db/H2/
# mv $TEMENOS_HOME/3rdParty/Db/H2/h2 $TEMENOS_HOME/3rdParty/Db/H2/h2-
1.3.176
On all servers in Application Layer and Web Layer, with t24user user.
# cd
# vi .bash_profile
Close your session and login again with t24user
TAFJ Installation
Have the installer package of TAFJ.
TAFJ.xx.SPy.0.tar.gz
# cd $TEMENOS_HOME/Install
# mkdir -p $TEMENOS_HOME/Install/tafjinst
Untar the files:
TAFJ installation
# cd $TEMENOS_HOME/Install/tafjinst
# chmod 755 *
# echo $TAFJ_HOME
# . ./Setup_TAFJ.R15.SP4.0.sh
# tDiag
T24 Installation
T24 Files structure
The UD file type specifies NT or UNIX directories and NT or UNIX files are to be used to
represent file and records respectively. With TAFJ all data are inside the RDBMS expect the
UD. UD files are officialy the bnk.run folder from modelbank.
# mkdir -p $T24_HOME/Src/T24.BP
# mkdir -p $T24_HOME/Src/LOCAL.BP
# mkdir -p $T24_HOME/Src/RG.BP
# mkdir -p $T24_HOME/Src/t24inserts
# mkdir -p $T24_HOME/Data/bnk/bnk.run
# mkdir -p $T24_HOME/Lib/LocalDev
# mkdir -p $T24_HOME/Lib/GPACK
# mkdir -p $T24_HOME/Lib/T24Lib
# mkdir -p $T24_HOME/Lib/T24Sms
# mkdir -p $T24_HOME/Lib/T24Email
# mkdir -p $T24_HOME/Lib/RepGen
# mkdir -p $T24_HOME/Lib/RulesEngine
T24 Modelbank
MB.R15.000.ORACLE11gR2.UNIX.TAFJR15.20161130.bnk.tar.gz
t24email.1.0.0.zip
t24sms.1.0.1.zip
Rules-engine.1.0.0.zip
# cd $TEMENOS_HOME/Install
# mkdir -p $TEMENOS_HOME/Install/t24inst
# mkdir -p $TEMENOS_HOME/Install/emailinst
# mkdir -p $TEMENOS_HOME/Install/smsinst
# mkdir -p $TEMENOS_HOME/Install/ruleengineinst
Untar the T24 files:
# cp $TEMENOS_HOME/Install/t24inst/bnk/lib/* $T24_HOME/Lib/RepGen
# cp $TEMENOS_HOME/Install/t24inst/bnk/t24lib/* $T24_HOME/Lib/T24Lib
# cp $TEMENOS_HOME/Install/t24inst/bnk/T24_BP/* $T24_HOME/Src/T24.BP
# cp $TEMENOS_HOME/Install/t24inst/bnk/UD/RG.BP/* $T24_HOME/Src/RG.BP
# cp $TEMENOS_HOME/Install/t24inst/bnk/t24inserts/* $T24_HOME/Src/t24inserts
# cp -R $TEMENOS_HOME/Install/t24inst/bnk/UD/* $T24_HOME/Data/bnk/bnk.run
T24 Sms
# unzip $TEMENOS_HOME/Install/smsinst/t24sms.1.0.1/MTR-SMS/Releases/t24sms.1.0.1.zip
-d $T24_HOME/Lib/T24Sms
# cp -R $T24_HOME/Lib/T24Sms/t24sms.1.0.1/* $T24_HOME/Lib/T24Sms
# rm -R $T24_HOME/Lib/T24Sms/t24sms.1.0.1
T24 Email
# unzip $TEMENOS_HOME/Install/emailinst/t24email.1.0.0/MTR-
Email/Releases/t24email.1.0.0.zip -d $T24_HOME/Lib/T24Email
# cp -R $T24_HOME/Lib/T24Email/t24email.1.0.0/* $T24_HOME/Lib/T24Email
# rm -R $T24_HOME/Lib/T24Email/t24email.1.0.0
T24 RuleEngine
# cp ./ruleengineinst/Rules-engine.1.0.0/jars/* $T24_HOME/Lib/RulesEngine
T24 DataSet Configuration
T24 DataSet configuration with H2
This is the full structure of T24 installation. Al Dataset will be install under T24_Home/Data
If T24 is not install on the Database Server (most of the case), create the mnimum structure for
the dataset in T24.
The H2 dtaset is under:
$T24_HOME/data/Rdbms/H2
# mkdir -p $TEMENOS_HOME/T24/data/Rdbms/H2
# cd
# vi .bash_profile
Close your session and login again with t24user
# cd $H2_HOME/bin
# vi t24h2.sh
change the mod of the t24h2 scripts
The param //localhost/data have to macth the file name of H2 dataset file name
That is;
data.h2.db ->//localhost/data
R15.h2.db ->//localhost/R15
T24MD.h2.db ->//localhost/T24MB
# cd $TEMENOS_HOME/Install
# cp $TEMENOS_HOME/Install/data.h2.db $TEMENOS_HOME/T24/Data/Rdbms/H2
# cd $TEMENOS_HOME/Install
# cp $TEMENOS_HOME/Install/TAFJFunctions.jar $H2_HOME/bin
Start t24h2
# cd $H2_HOME/bin
# t24h2.sh
# cd $ORACLE_HOME/bin
# netca
Click "Next" Button.
# dbca
Unselect the container database and do not specify a Pluggable Database name.
Click "Next" Button.
# cd $TAFJ_HOME/dbscripts/oracle
# vi createtablespace_oracle.sql
# cd $TAFJ_HOME/dbscripts/oracle
# vi createuser_oracle.sql
On DB server, with oracle user.
Once these values have been changed, launch a console and from
/u01/Temenos/TAFJ/dbscripts/oracle
# cd /u01/Temenos/TAFJ/dbscripts/oracle
: @createtablespace_oracle.sql
: @createuser_oracle.sql
: exit
Load the necessary Stored functions
# cd $TAFJ_HOME/dbscripts/oracle
# vi javaload
# chmod 777 *
# cd /u01/Temenos/TAFJ/dbscripts/oracle
# ./javaload
# cd /u01/Temenos/TAFJ/dbscripts/oracle
# sqlplus t24
: @javafunctions_oracle.sql
: exit
On AppSrv01 server, with t24user user.
# cp -R $TAFJ_HOME/dbdrivers/oracle-12c $TAFJ_HOME/ext
# cp -R $TAFJ_HOME/dbdrivers/h2-1.3.176 $TAFJ_HOME/ext
# DBImport -gui
Click "Next" Button.
Select "From Database" and Click "Next" Button.
Database = H2
Url = jdbc:h2:tcp//192.168.1.159/T24
UserId= t24
Password= t24
Click "Next" Button.
Database = Oracle
Url = jdbc:oracle:thin//192.168.1.159:1521:T24
UserId= t24
Password= t24
Click "Next" Button.
# groupadd db2grp1
# groupadd db2fgrp1
# cd /u01/Temenos/3rdParty/Db/Ibm/DB2/V10.1/instance
# db2set DB2COMM=tcpip
Start DB2:
# db2start
Check DB2 service
# cd /u01/Temenos/3rdParty/Db/Ibm/DB2/V10.1/instance
# mkdir db2repo
Database Creation
# cd $TAFJ_HOME/dbscripts/db2
# vi createDatabase_db2.db2
# cd $TAFJ_HOME/dbscripts/db2
# vi createtablespace_db2.db2
# vi grantPrivileges_db2.db2
# db2 -td@ -vf $TAFJ_HOME/dbscripts/db2/ grantPrivileges_db2.db2
# cd /u01/Temenos/3rdParty/Db/Ibm/DB2/V10.1/function
# mkdir -p com/temenos/dbi/storedfunctions
#
/u01/Temenos/3rdParty/Db/Ibm/DB2/V10.1/java/jdk64/bin/javac /u01/Temenos/TAFJ/dbscripts
/BasicFunctions.java
# cp /u01/Temenos/TAFJ/dbscripts/BasicFunctions.class .
# cd $TAFJ_HOME/dbscripts/db2
# vi javafunctions_db2.db2
# cp -R $TAFJ_HOME/dbdrivers/db2_v10.1 $TAFJ_HOME/ext
# cp -R $TAFJ_HOME/dbdrivers/h2-1.3.176 $TAFJ_HOME/ext
Database = H2
Url = jdbc:h2:tcp//192.168.1.159/T24
UserId= t24
Password= t24
Click "Next" Button.
Database = Oracle
Url = jdbc:db2://192.168.1.159:50000:T24
UserId= db2inst1
Password= dbinst1
Click "Next" Button.
In $TAFJ_HOME\conf, copy and rename the .properties file template with the extention
properties. In our context we will call the Project TRAINT24
# cd $TAFJ_HOME/conf
# cp .properties T24.properties
In $TAFJ_HOME\conf, edit the file .default and set the name of the default Project TRAINT24.
# vi .default
# tDiag
Properties file
Directories
Database
Runtime
# vi T24.properties
Directories
The key temn.tafj.directory.insert specify where is the I_ files folders or zip/jar. Temenos
provide 3 differents files I_BP.jar, I_RG.jar and I_T24.BP.jar
temn.tafj.directory.insert=<$T24_HOME>/Src/t24inserts/I_BP.jar:<$T24_HOME>/Src/t24insert
s/I_RG.jar:<$T24_HOME>/Src/t24inserts/I_T24.BP.jar
The key temn.tafj.directory.java Specify where the java files will be generated. By convention
the java folder have to be $TAFJ_HOME/data/<Project_name>/java
temn.tafj.directory.java = <$TAFJ_HOME>/data/T24/java
The key temn.tafj.directory.classes specify where the classes files will be generated. By
convention the java folder have to be $TAFJ_HOME/data/<Project_name>/classes
temn.tafj.directory.classes = <$TAFJ_HOME>/data/T24/classes
The key temn.tafj.directory.precompile specify where are all libs of T24 except the RuleEngin
libs because a conflict with the xml parser of the Oracle JDBC drivers.
temn.tafj.directory.precompile=<$T24_HOME>/Lib/LocalDev:<$T24_HOME>/Lib/GPack:<$T
24_HOME>/Lib/T24Lib:<$T24_HOME>/Lib/T24Sms:<$T24_HOME>/Lib/T24Email:<$T24_
HOME>/Lib/RepGen:
Database
The key temn.tafj.jdbc.url specify the URL to connect to the RDMS. Ask your DBA about this
URL.
temn.tafj.jdbc.url=jdbc:oracle:thin:@192.168.1.159:1521/T24
The key temn.tafj.jdbc.driver specify the driver to connect to the RDMS. Ask your DBA about
the driver to use.
temn.tafj.jdbc.driver = oracle.jdbc.driver.OracleDriver
temn.tafj.jdbc.username = t24
temn.tafj.jdbc.password = t24
temn.tafj.jdbc.write.use.merge = false
temn.tafj.jdbc.write.use.merge.no.xml = false
Runtime
The key temn.tafj.runtime.classpath specify a classpath loaded before the ext folder of TAFJ
where is the JDBC driver. This is here we have to set the RuleEngile libs.
temn.tafj.runtime.classpath = <$T24_HOME>/Lib/RuleEngine
The key temn.tafj.runtime.directory.current where is the UD T24 files. In our case the path is
<$T24_HOME>/Data/bnk/bnk.run
temn.tafj.runtime.directory.current = <$T24_HOME>/Data/bnk/bnk.run
For performance raison change the key temn.tafj.runtime.enable.cached.opf and
temn.tafj.runtime.enable.cached.opf to true and you can disable the debug mode
temn.tafj.runtime.enable.debug to false
temn.tafj.runtime.enable.debug = false
temn.tafj.runtime.enable.cached.opf = true
temn.tafj.runtime.use.cache.get = true
# tDiag
JDBC Drivers
You have to copy the correct JDBC driver into the $TAFJ_HOME/ext. This folder is
automaticaly taken as a classpath of TAFJ.
Officialy you supposed to request the JDBC drivers from the database install itself. TAFJ
provide some differents JDBC drivers in $TAFJ_HOME/dbdrivers
# cp -R $TAFJ_HOME/dbdrivers/oracle-12c $TAFJ_HOME/ext
Check T24
Check your T24 Compile in java in standalone mode.
# tRun EX
Logon INPUTT/123456
#********************************************************************
#
# TAFJ Monitor
#********************************************************************
This book has been updated with the new features introduced with T24 R15 AMR.
3 Software Installation
3.1 JDK installation
From http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
# mkdir -p $TEMENOS_HOME/3rdParty/Java
# cd $TEMENOS_HOME/3rdParty/Java
# cp $TEMENOS_HOME/Install/jdk-7u79-linux-x64.tar.gz $TEMENOS_HOME/3rdParty/Java
[t24user@appsrv01 Java]$
Extract jdk-7u79-linux-x64.tar.gz
jdk1.7.0_79/db/bin/startNetworkServer.bat
jdk1.7.0_79/db/bin/startNetworkServer
jdk1.7.0_79/db/bin/setNetworkServerCP.bat
jdk1.7.0_79/db/bin/stopNetworkServer
jdk1.7.0_79/db/README-JDK.html
jdk1.7.0_79/db/NOTICE
jdk1.7.0_79/README.html
jdk1.7.0_79/THIRDPARTYLICENSEREADME.txt
[t24user@appsrv01 Java]$
# ls -ail
total 150080
[t24user@appsrv01 Java]$
Delete jdk-7u79-linux-x64.tar.gz
# rm jdk-7u79-linux-x64.tar.gz
# cd
# vi .bash_profile
[t24user@AppSrv01 ~]$ cd
# .bash_profile
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
PATH=$PATH:$HOME/.local/bin:$HOME/bin
export PATH
##############################################
# Temenos Home
export TEMENOS_HOME=/u01/Temenos
echo "TEMENOS_HOME="$TEMENOS_HOME
##############################################
# JAVA Home
export JAVA_HOME=$TEMENOS_HOME/3rdParty/Java/jdk1.7.0_79
echo "JAVA_HOME="$JAVA_HOME
export PATH=$JAVA_HOME/bin:$PATH
java -version
##############################################
# TAFJ Home
export TAFJ_HOME=$TEMENOS_HOME/TAFJ
echo "TAFJ_HOME="$TAFJ_HOME
export PATH=$TAFJ_HOME/bin:$PATH
##############################################
# T24 Home
export T24_HOME=$TEMENOS_HOME/T24
echo "T24_HOME="$T24_HOME
cd $TEMENOS_HOME
JAVA_HOME=/u01/Temenos/3rdParty/Java/jdk1.7.0_79
TAFJ_HOME=/u01/Temenos/TAFJ
T24_HOME=/u01/Temenos/T24
[t24user@appsrv01 Temenos]$
http://www-
933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7ERational&product=ibm/Ration
al/IBM+Installation+Manager&release=1.8.3.0&platform=Linux&function=all&useReleaseAsT
arget=true
# cd $TEMENOS_HOME/Install
[t24user@appsrv01 Install]$
# mkdir $TEMENOS_HOME/Install/instmgr
# cp agent.installer.linux.gtk.x86_64_1.8.3000.20150606_0047.zip ./instmgr/
[t24user@appsrv01 Install]$
# cd $TEMENOS_HOME/Install/instmgr
# unzip agent.installer.linux.gtk.x86_64_1.8.3000.20150606_0047.zip
inflating: user-silent-install.ini
inflating: userinst
inflating: userinst.ini
inflating: userinstc
inflating: userinstc.ini
[t24user@ComSrv01 instmgr]$
The location of Installation Manager will be $TEMENOS_HOME/3rdParty/Tools/IBM
# mkdir -p $TEMENOS_HOME/3rdParty/Tools/IBM/InstallationManager/eclipse
[t24user@AppSrv02 Install]$
# cd $TEMENOS_HOME/Install/instmgr
On all servers in Application Layer and Web Layer, with root user.
# ./install
Click the "Next" button.
Select I accept the terms in this license agreement and click the "Next" button.
Menus File->Exit
WAS_ND_V8.5.5_1_OF_3.zip
WAS_ND_V8.5.5_2_OF_3.zip
WAS_ND_V8.5.5_3_OF_3.zip
On all servers in Application Layer and Web Layer, with t24user user.
[t24user@appsrv01 Install]$
# mkdir $TEMENOS_HOME/Install/was
[t24user@appsrv01 Install]$
# cp WAS_ND_V8.5.5_* ./was/
[t24user@appsrv01 Install]$
# cd $TEMENOS_HOME/Install/was
# unzip WAS_ND_V8.5.5_1_OF_3.zip
# unzip WAS_ND_V8.5.5_2_OF_3.zip
# unzip WAS_ND_V8.5.5_3_OF_3.zip
[t24user@ComSrv01 instmgr]$ unzip WAS_ND_V8.5.5_1_OF_3.zip
inflating: disk3/ad/native/file000277
inflating: disk3/ad/native/file000278
inflating: disk3/ad/native/toc.xml
inflating: disk3/ad/repository.config
inflating: disk3/diskTag.inf
[t24user@ComSrv01 was]$
# mkdir -p $TEMENOS_HOME/3rdParty/As/IBM/WebSphere8.5.5/AppServer
[t24user@AppSrv02 Temenos]$
# mkdir -p $TEMENOS_HOME/3rdParty/Tools/IBM/IMShared
[t24user@AppSrv02 Temenos]$
# ./launcher
Menus File->Preferences
Click the "Add Repository" button.
Select Version 8.5.5.6 for Websphere and Version 7.1.3.0 for IBM WebSphere SDK and click
the "Next" button
Select all and click the "Next" button
On all servers in Application Layer and Web Layer, with root user.
[root@appsrv01 As]#
The new folder $TEMENOS_HOME/3rdParty/As/IBM/WebSphere8.5.5/AppServer is
WAS_HOME
On all servers in Application Layer and Web Layer, with t24user user.
# cd
# vi .bash_profile
[t24user@AppSrv01 ~]$ cd
##############################################
# TAFJ Home
export TAFJ_HOME=$TEMENOS_HOME/TAFJ
echo "TAFJ_HOME="$TAFJ_HOME
export PATH=$TAFJ_HOME/bin:$PATH
##############################################
# T24 Home
#
export T24_HOME=$TEMENOS_HOME/T24
echo "T24_HOME="$T24_HOME
#############################################
# WebSphere Home
export WAS_HOME=$TEMENOS_HOME/3rdParty/As/IBM/WebSphere8.5.5/AppServer
echo "WAS_HOME="$WAS_HOME
cd $TEMENOS_HOME
TEMENOS_HOME=/u01/Temenos
JAVA_HOME=/u01/Temenos/3rdParty/Java/jdk1.7.0_79
TAFJ_HOME=/u01/Temenos/TAFJ
T24_HOME=/u01/Temenos/T24
WAS_HOME=/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer
[t24user@appsrv01 Temenos]$
On all servers in Application Layer and Web Layer, with t24user user.
You have now to validate and set as default the SDK 1.7. In $WAS_HOME/bin, There are the
script managesdk.
# cd $WAS_HOME/bin
# ./managesdk.sh -listavailable
[t24user@appsrv01 bin]$
Issue this command to change the default SDK to Version 7.1 SDK:
[t24user@appsrv01 bin]$
Set New Profile Default to Version 7.1 SDK
Issue this command to change the set the default for new profiles to Version 7.1 SDK:
CWSDK1022I: New profile creation will now use SDK name 1.7.1_64.
[t24user@appsrv01 bin]$
If you have already create a profile you need covert the forfile to use the new SDK.
Issue this command to change the set the default for existing profiles to Version 7.0 SDK:
[t24user@appsrv01 bin]$
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Installation
--------------------------------------------------------------------------------
Version
Directory /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/properties/version
DTD
Directory /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/properties/version
/dtd
Product List
--------------------------------------------------------------------------------
ND installed
IBMJAVA71 installed
Installed Product
--------------------------------------------------------------------------------
Version 8.5.5.6
ID ND
Package com.ibm.websphere.ND.v85_8.5.5006.20150529_0536
Installed Product
--------------------------------------------------------------------------------
Version 7.1.3.0
ID IBMJAVA71
Package com.ibm.websphere.IBMJAVA.v71_7.1.3000.20150528_1959
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
[t24user@appsrv01 bin]$
# cd $TEMENOS_HOME/3rdParty/Tools/IBM/InstallationManager/eclipse
# ./launcher
Menus File->Preferences
Select "I accept the terms in this license agreement" and click the "Next" button.
Select the Shared Resources Directory "/u01/Temenos/3rdParty/Tools/IBM/IMShared" and click
Next button.
Select the Installation Directory "/u01/Temenos/3rdParty/As/IBM/HTTPServer" and click
"Next" button
On all servers in Application Layer and Web Layer, with root user.
[root@appsrv01 As]#
The new folder $TEMENOS_HOME/3rdParty/As/IBM/WebSphere8.5.5/AppServer is
WAS_HOME
On all servers in Application Layer and Web Layer, with t24user user.
# cd
# vi .bash_profile
[t24user@AppSrv01 ~]$ cd
##############################################
# TAFJ Home
export TAFJ_HOME=$TEMENOS_HOME/TAFJ
echo "TAFJ_HOME="$TAFJ_HOME
export PATH=$TAFJ_HOME/bin:$PATH
##############################################
# T24 Home
#
export T24_HOME=$TEMENOS_HOME/T24
echo "T24_HOME="$T24_HOME
#############################################
export HTTP_HOME=$TEMENOS_HOME/3rdParty/As/IBM/HTTPServer
echo "HTTP_HOME="$HTTP_HOME
cd $TEMENOS_HOME
TEMENOS_HOME=/u01/Temenos
JAVA_HOME=/u01/Temenos/3rdParty/Java/jdk1.7.0_79
TAFJ_HOME=/u01/Temenos/TAFJ
T24_HOME=/u01/Temenos/T24
HTTP_HOME=/u01/Temenos/3rdParty/As/IBM/HTTPServer
[t24user@appsrv01 Temenos]$
On all servers in Application Layer and Web Layer, with t24user user.
You have now to validate and set as default the SDK 1.7. In $WAS_HOME/bin, There are the
script managesdk.
# cd $WAS_HOME/bin
# ./managesdk.sh -listavailable
[t24user@appsrv01 bin]$
Issue this command to change the default SDK to Version 7.1 SDK:
Issue this command to change the set the default for new profiles to Version 7.1 SDK:
CWSDK1022I: New profile creation will now use SDK name 1.7.1_64.
[t24user@appsrv01 bin]$
If you have already create a profile you need covert the forfile to use the new SDK.
Issue this command to change the set the default for existing profiles to Version 7.0 SDK:
[t24user@appsrv01 bin]$
[t24user@appsrv01 bin]$ ./versionInfo.sh
WVER0010I: Copyright (c) IBM Corporation 2002, 2012; All rights reserved.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Installation
--------------------------------------------------------------------------------
Version
Directory /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/properties/version
DTD
Directory /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/properties/version
/dtd
Product List
--------------------------------------------------------------------------------
ND installed
IBMJAVA71 installed
Installed Product
--------------------------------------------------------------------------------
Version 8.5.5.6
ID ND
Package com.ibm.websphere.ND.v85_8.5.5006.20150529_0536
Installed Product
--------------------------------------------------------------------------------
Version 7.1.3.0
ID IBMJAVA71
Package com.ibm.websphere.IBMJAVA.v71_7.1.3000.20150528_1959
Architecture x86-64 (64 bit)
Installed Features IBM WebSphere SDK for Java Technology Edition Version 7.1
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
[t24user@appsrv01 bin]$
3.5 MQ Installation
Have the installer package of WebSphere MQ.
WS_MQ_FOR_LNX_ON_X86_64_V7.5_EIMG.tar.gz
7.5.0-WS-MQ-LinuxX64-FP0005.tar.gz
# cd $TEMENOS_HOME/Install
[t24user@appsrv01 Install]$
Under install folder create a folder mqinst and mqinst _fp
# mkdir $TEMENOS_HOME/Install/mqinst
# mkdir $TEMENOS_HOME/Install/mqinst_fp
./repackage/MQSeriesXRClients.spec
./repackage/MQSeriesXRService.spec
./repackage/MQSeriesXRClients.spec
./repackage/MQSeriesXRService.spec
# groupadd mqm
# passwd mqm
New password:
[root@JmsSrv01 Temenos]# $
kernel.shmmni = 4096
kernel.shmall = 2097152
kernel.shmmax = 268435456
net.ipv4.tcp_keepalive_time = 300
# cat /proc/sys/kernel/shmmni
# cat /proc/sys/kernel/shmall
# cat /proc/sys/kernel/shmmax
# cat /proc/sys/kernel/sem
# cat /proc/sys/net/ipv4/tcp_keepalive_time
4096
268435456
4294967295
7200
[root@JmsSrv01 ipv4]#
To modify a value
[root@JmsSrv01 Temenos]#
# sysctl -w net.ipv4.tcp_keepalive_time=300
net.ipv4.tcp_keepalive_time = 300
[root@JmsSrv01 Temenos]#
#sysctl -p
# vi /etc/security/limits.conf
#* soft core 0
#@student - maxlogins 4
# End of file
WebSphere MQ 7.5 installation
# mkdir -p $TEMENOS_HOME/3rdParty/Jms/MQ/Installation/1
[root@JmsSrv02 mqinst]#
cd $TEMENOS_HOME/Install/mqinst
# ./mqlicense.sh -accept
5724-H72
(C) Copyright IBM Corporation 1994, 2012 All rights reserved.
[root@JmsSrv01 mqinst]#
MQSeriesRuntime
MQSeriesServer
MQSeriesClient
MQSeriesSDK
MQSeriesJava
MQSeriesMan
MQSeriesJRE
Updating / installing...
Updating / installing...
Updating / installing...
Updating / installing...
Updating / installing...
Updating / installing...
Updating / installing...
[root@JmsSrv01 mqinst]#
cd $TEMENOS_HOME/Install/mqinst_fp
MQSeriesRuntime
MQSeriesServer
MQSeriesClient
MQSeriesSDK
MQSeriesJava
MQSeriesMan
MQSeriesJRE
Updating / installing...
Updating / installing...
After the installation of this fix pack has completed, run the
su mqm -c "/u01/Temenos/3rdParty/Jms/MQ/Installation/1/bin/mqconfig"
The 'mqconfig' command validates that the system configuration satisfies the
requirements for WebSphere MQ, and ensures that the settings for the 'mqm'
'mqm' group can run this command to ensure their user limits are also
If 'mqconfig' indicates that any of the requirements have not been met,
for details about how to configure the system and user limits.
Updating / installing...
Updating / installing...
1:MQSeriesSDK-U200533-7.5.0-5 ################################# [100%]
Updating / installing...
Updating / installing...
Updating / installing...
[root@JmsSrv01 mqinst_fp]#
Post Installations
# su mqm -c "/u01/Temenos/3rdParty/Jms/MQ/Installation/1/bin/mqconfig"
System V Semaphores
System Settings
# $TEMENOS_HOME/3rdParty/Jms/MQ/Installation/1/bin/setmqinst -i -p
$TEMENOS_HOME/3rdParty/Jms/MQ/Installation/1
[root@JmsSrv01 mqinst_fp]#
$TEMENOS_HOME/3rdParty/Jms/MQ/Installation/1/bin/setmqinst -i -p
$TEMENOS_HOME/3rdParty/Jms/MQ/Installation/1
Primary Installation.
[root@JmsSrv01 mqinst_fp]#
Works with MQ
# cd
# vi .bash_profile
[mqm@AppSrv01 ~]$ cd
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
PATH=$PATH:$HOME/.local/bin:$HOME/bin
export PATH
##############################################
# Temenos Home
export TEMENOS_HOME=/u01/Temenos
echo "TEMENOS_HOME="$TEMENOS_HOME
cd $TEMENOS_HOME
Close your session and login again with mqm
TEMENOS_HOME=/u01/Temenos
[mqm@JmsSrv01 Temenos]$
# . $TEMENOS_HOME/3rdParty/Jms/MQ/Installation/1/bin/setmqenv -s
[mqm@JmsSrv01 Temenos]$ .
$TEMENOS_HOME/3rdParty/Jms/MQ/Installation/1/bin/setmqenv -s
[mqm@JmsSrv01 Temenos]$
# dspmqver
Name: WebSphere MQ
Version: 7.5.0.5
Level: p750-005-150424
Mode: 64-bit
InstName: Installation1
InstDesc:
Primary: Yes
InstPath: /u01/Temenos/3rdParty/Jms/MQ/Installation/1
DataPath: /var/mqm
MaxCmdLevel: 750
LicenseType: Production
[mqm@JmsSrv01 Temenos]$
You need to add all user exepct mqm who have to access to MQ. Including user for MQExplorer
[root@JmsSrv01 Temenos]#
4 Software configuration
4.1 WebSphere configuration
4.1.1 WebSphere Tier 1 standalone
AdminServer
AppServer
JMS Server
WebServer
[root@appsrv01 Temenos]#
To create a new profile you can use the GUI tools or the command line. To start the GUI tools
you can start the command:
# $WAS_HOME/bin/ProfileManagement/wct.sh
Under $TAFJ_HOME/AppServer/was you will find all the scripts to create profiles.
<product_name><Business_role><type><number>
<product_name>
T24
AML
TAP
<Business_role>
<type>
<number>
From 00 to 99
In our situation we will create on the Application layer a standalone Server for T24
i.e
Set the Profile name to T24AppStd01 and the Profile path to /profiles/T24AppStd01
Set the Node name to T24AppStd01Node01 and the Server name to T24AppSrv01
Click the "Next" button
# vi $TAFJ_HOME/appserver/was/setUpEnv.sh
# *********************************
# WAS
# *********************************
#export WAS_HOME=[WAS_HOME]
export HOST_NAME=
export PROFILE_NAME=T24AppStd01
export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME=$NODE_NAME'Cell'
export DMGR_USER=admin
export DMGR_PASSWORD=Temenos_1
export DMGR_HOST=
export DMGR_PORT=
# cd $TAFJ_HOME/appserver/was
# . ./createStandalone.sh
[t24user@appsrv01 was]$
# $WAS_HOME/bin/startServer.sh T24AppStd01
[t24user@appsrv01 bin]$ ./startServer.sh T24AppSrv01 -profileName T24AppStd01
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppStd01/logs/
T24AppSrv01/startServer.log
[t24user@appsrv01 bin]$
To determin the port of the instance, check the AboutThisProfile.txt in the log folder of the
profile
# cat $WAS_HOME/profiles/T24AppStd01/logs/AboutThisProfile.txt
Location: /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppStd01
[t24user@appsrv01 logs]$
http://192.168.1.161:9060/ibm/console
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppStd01/logs/
T24AppSrv01/stopServer.log
Table 1. Port definitions for WebSphere Application Server Version 7.0 and Version 8.0 . The
table lists port names and the default values of the port numbers.
Default Value Files
Secur
Port Name Job
Applicatio Administrativ e Administrativ
Manage
n Server e Agent Proxy e Subsystem
r
Server
Administrative
Console Port 9060 9060 9960 ---- ----
(WC_ adminhost)
Administrative
Console Secure
Port (WC_ 9043 9043 9943 ---- ----
adminhost_ serverindex.xml
secure) and
HTTP Transport virtualhosts.xml
Port (WC_ 9080 ---- ---- 80 ----
defaulthost)
HTTPS Transport
Secure Port (WC_
9443 ---- ---- 443 ----
defaulthost_
secure)
Bootstrap Port
(BOOTSTRAP_ 2809 9807 9808 ---- ----
ADDRESS)
Cell Discovery
Address (CELL_
---- ---- ---- ---- ---- serverindex.xml
DISCOVERY_
ADDRESS)
CSIV2 Client
Authentication 9402 9402 9402 ---- ----
Listener Port
(CSIV2_ SSL_
MUTUALAUTH_
LISTENER_
ADDRESS)
CSIV2 Server
Authentication
Listener Port
(CSIV2_ SSL_ 9403 9403 9403 ---- ----
SERVERAUTH_
LISTENER_
ADDRESS)
High Availability
Manager
Communication
9353 ---- ---- ---- ----
Port (DCS_
UNICAST_
ADDRESS)
Internal JMS
Server Port
(JMSSERVER_ 5557 ---- ---- ---- ----
SECURITY_
PORT)
IPC Connector
Port (IPC_
9633 9630 9631 9633 9634
CONNECTOR_
ADDRESS)
MQ Transport
Port (SIB_ MQ_
5558 ---- ---- ---- ----
ENDPOINT_
ADDRESS)
MQ Transport
Secure Port (SIB_
MQ_
5578 ---- ---- ---- ----
ENDPOINT_
SECURE_
ADDRESS)
ORB Listener Port
(ORB_
9100 9098 9099 ---- ----
LISTENER_
ADDRESS)
serverindex.xml
RMI Connector
Port (RMI_
---- ---- ---- ---- 9810
CONNECTOR_
ADDRESS)
JSR 160 RMI
Connector Port
(JSR160RMI_ ---- ---- ---- ---- 9811
CONNECTOR_
ADDRESS)
SAS_ SSL_
SERVERAUTH_
9401 9401 9401 ---- ----
LISTENER_
ADDRESS
Service
Integration Port
(SIB_ 7276 ---- ---- ---- ----
ENDPOINT_
ADDRESS)
Service
Integration Secure
Port (SIB_
7286 ---- ---- ---- ----
ENDPOINT_
SECURE_
ADDRESS)
SIP Container Port
(SIP_ 5060 ---- ---- 5060 ----
DEFAULTHOST)
SIP Container
Secure Port (SIP_
5061 ---- ---- 5061 ----
DEFAULTHOST
_ SECURE)
SOAP Connector
Port (SOAP_
8880 8877 8876 ---- 8881
CONNECTOR_
ADDRESS)
virtualhosts.xml
, plugin-
IBM HTTP cfg.xml, and
80 ---- ---- ---- ----
Server Port web_ server_
root/conf/
httpd.conf
IBM HTTPS
web_ server_
Server
8008 ---- ---- ---- ---- root/conf/
Administration
admin.conf
Port
4.1.2 WebSphere Manager Server
AppServer
JMS Server
WebServer
4.1.2.1 Configure the firewall on the Management Server
[root@appsrv01 Temenos]#
# $WAS_HOME/bin/ProfileManagement/wct.sh
Under $TAFJ_HOME/AppServer/was you will find all the scripts to create profiles.
<product_name><Business_role><type><number>
<product_name>
T24
AML
TAP
<Business_role>
<type>
<number>
From 00 to 99
In our situation we will create on the Application layer a Manager Server for T24
i.e
Select "Deploy the administrative console" and click the "Next" button
Set the Profile name to T24AppMgr01 and the Profile path to /profiles/T24AppMgr01
# vi $TAFJ_HOME/appserver/was/setUpEnv.sh
# *********************************
# WAS
# *********************************
#export WAS_HOME=[WAS_HOME]
export HOST_NAME=192.168.1.161
export PROFILE_NAME=T24AppMgr01
export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME='T24Cell'
export DMGR_USER=admin
export DMGR_PASSWORD=Temenos_1
export DMGR_HOST=
export DMGR_PORT=
Create the management profile
# cd $TAFJ_HOME/appserver/was
# . ./createManagement.sh
[t24user@appsrv01 was]$
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMgr01/logs
/dmgr/startServer.log
[t24user@appsrv01 profiles]$
To determin the port of the instance, check the AboutThisProfile.txt in the log folder of the
profile
# cat $WAS_HOME/profiles/T24AppMgr01/logs/AboutThisProfile.txt
Location: /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMgr01
[t24user@appsrv01 logs]$
4.1.2.5 Admin Console
http://192.168.1.161:9060/ibm/console
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMgr01/logs
/dmgr/stopServer.log
[t24user@appsrv01 profiles]$
AppServer
JMS Server
WebServer
4.1.3.1 Configure the firewall on the App Server and Web Server
[root@appsrv01 Temenos]#
To create a new profile you can use the GUI tools or the command line. To start the GUI tools
you can start the command:
# $WAS_HOME/bin/ProfileManagement/wct.sh
Under $TAFJ_HOME/AppServer/was you will find all the scripts to create profiles.
<product_name>
T24
AML
TAP
<Business_role>
<type>
<number>
From 00 to 99
In our situation we will create on the Application layer a Manager Server for T24
Set the Profile name to T24AppMng01 and the Profile path to /profiles/T24AppMng01
Click the "Next" button
Set the IP and the port of the ManagerServer with the security credential admin/Temenos_1
# vi $TAFJ_HOME/appserver/was/setUpEnv.sh
# *********************************
# WAS
# *********************************
#export WAS_HOME=[WAS_HOME]
export HOST_NAME=192.168.1.161
export PROFILE_NAME=T24AppMng01
export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME=$NODE_NAME'Cell'
export DMGR_USER=admin
export DMGR_PASSWORD=Temenos_1
export DMGR_HOST=192.168.1.161
export DMGR_PORT=8879
# cd $TAFJ_HOME/appserver/was
# . ./createNode.sh
[t24user@appsrv01 was]$
Repeat the same process on Web Layer with the following parameters:
t24user@192.168.1.165's password:
[t24user@appsrv01 was]$
# vi $TEMENOS_HOME/Install/was/setUpEnv.sh
# *********************************
# WAS
# *********************************
#export WAS_HOME=[WAS_HOME]
export HOST_NAME=192.168.1.165
export PROFILE_NAME=T24WebMng01
export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME=$NODE_NAME'Cell'
export DMGR_USER=admin
export DMGR_PASSWORD=Temenos_1
export DMGR_HOST=192.168.1.161
export DMGR_PORT=8879
# cd $TEMENOS_HOME/Install/was/
# . ./createNode.sh
[t24user@WebSrv01 was]$
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMng01/log
s/nodeagent/startServer.log
[t24user@WebSrv01 was]$
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24WebMng01/log
s/nodeagent/startServer.log
[t24user@WebSrv01 was]$
To determin the port of the instance, check the AboutThisProfile.txt in the log folder of the
profile
# cat $WAS_HOME/profiles/T24AppMgr01/logs/AboutThisProfile.txt
Location: /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMgr01
[t24user@appsrv01 logs]$
http://192.168.1.161:9060/ibm/console
Login with user and password Admin/Temenos_1
Select the node T24AppMng01Node01 and set the Server name T24AppMng01
Repeat the same process on Web Layer with the following parameters:
In the AdminConsole
Domain Structure
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMng01/log
s/nodeagent/stopServer.log
AppServer
JMS Server
[root@appsrv01 Temenos]#
To create a new profile you can use the GUI tools or the command line. To start the GUI tools
you can start the command:
# $WAS_HOME/bin/ProfileManagement/wct.sh
Under $TAFJ_HOME/AppServer/was you will find all the scripts to create profiles.
<product_name><Business_role><type><number>
<product_name>
T24
AML
TAP
<Business_role>
<type>
<number>
From 00 to 99
In our situation we will create on the Application layer a Manager Server for T24
i.e
Set the Profile name to T24AppMng01 and the Profile path to /profiles/T24AppMng01
Click the "Next" button
Set the IP and the port of the ManagerServer with the security credential admin/Temenos_1
# vi $TAFJ_HOME/appserver/was/setUpEnv.sh
# *********************************
# WAS
# *********************************
#export WAS_HOME=[WAS_HOME]
export HOST_NAME=192.168.1.161
export PROFILE_NAME=T24AppMng01
export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME=$NODE_NAME'Cell'
export DMGR_USER=admin
export DMGR_PASSWORD=Temenos_1
export DMGR_HOST=192.168.1.161
export DMGR_PORT=8879
# cd $TAFJ_HOME/appserver/was
# . ./createNode.sh
[t24user
Repeat the same process on Web Layer with the following parameters:
t24user@192.168.1.165's password:
[t24user@appsrv01 was]$
# vi $TEMENOS_HOME/Install/was/setUpEnv.sh
# *********************************
# WAS
# *********************************
#export WAS_HOME=[WAS_HOME]
export HOST_NAME=192.168.1.165
export PROFILE_NAME=T24WebMng01
export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME=$NODE_NAME'Cell'
export SERVER_NAME=
export DMGR_USER=admin
export DMGR_PASSWORD=Temenos_1
export DMGR_HOST=192.168.1.161
export DMGR_PORT=8879
# cd $TEMENOS_HOME/Install/was/
# . ./createNode.sh
[t24user@WebSrv01 was]$
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMng01/log
s/nodeagent/startServer.log
[t24user@WebSrv01 was]$
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24WebMng01/log
s/nodeagent/startServer.log
[t24user@WebSrv01 was]$
To determin the port of the instance, check the AboutThisProfile.txt in the log folder of the
profile
# cat $WAS_HOME/profiles/T24AppMgr01/logs/AboutThisProfile.txt
Location: /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMgr01
[t24user@appsrv01 logs]$
http://192.168.1.161:9060/ibm/console
Login with user and password Admin/Temenos_1
Select the node T24AppMng01Node01 and set the Server name T24AppMng01
In the AdminConsole
Domain Structure
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMng01/log
s/nodeagent/stopServer.log
[t24user@appsrv01 bin]$
[root@appsrv01 Temenos]#
t24user@192.168.1.163's password:
t24.queues 100%
1575 1.5KB/s 00:00
t24.bind 100%
1544 1.5KB/s 00:00
[t24user@appsrv01 appserver]$
total 40
[root@JmsSrv01 MQ]#
# . $TEMENOS_HOME/3rdParty/Jms/MQ/Installation/1/bin/setmqenv -s
[mqm@JmsSrv01 Temenos]$ .
$TEMENOS_HOME/3rdParty/Jms/MQ/Installation/1/bin/setmqenv -s
[mqm@JmsSrv01 Temenos]$
# dspmqver
Name: WebSphere MQ
Version: 7.5.0.5
Level: p750-005-150424
Mode: 64-bit
InstName: Installation1
InstDesc:
Primary: Yes
InstPath: /u01/Temenos/3rdParty/Jms/MQ/Installation/1
DataPath: /var/mqm
MaxCmdLevel: 750
LicenseType: Production
[mqm@JmsSrv01 Temenos]$
# cd $TEMENOS_HOME/Install/MQ
# . ./MQCommand.sh
Completing setup.
Setup completed.
5 log records accessed on queue manager 'MQT24' during the log replay phase.
5724-H72 (C) Copyright IBM Corp. 1994, 2011. ALL RIGHTS RESERVED.
2 : START LISTENER('T24_LISTENER.TCP')
6 : REFRESH SECURITY
[mqm@JmsSrv01 MQ]$
5724-H72 (C) Copyright IBM Corp. 1994, 2011. ALL RIGHTS RESERVED.
$ display qlocal(T24.*)
display qlocal(T24.*)
3 : display qlocal(T24.*)
QUEUE(T24.AML.QUEUE) TYPE(QLOCAL)
QUEUE(T24.AML.REPLY.QUEUE) TYPE(QLOCAL)
QUEUE(T24.ARC.MOBILE.QUEUE) TYPE(QLOCAL)
QUEUE(T24.ARC.MOBILE.REPLY.QUEUE) TYPE(QLOCAL)
QUEUE(T24.BROWSER.QUEUE) TYPE(QLOCAL)
QUEUE(T24.BROWSER.REPLY.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(T24.CALLAT.QUEUE) TYPE(QLOCAL)
QUEUE(T24.CALLAT.REPLY.QUEUE) TYPE(QLOCAL)
QUEUE(T24.IF.INBOUND.QUEUE) TYPE(QLOCAL)
QUEUE(T24.IF.OUTBOUND.QUEUE) TYPE(QLOCAL)
QUEUE(T24.OFS.QUEUE) TYPE(QLOCAL)
QUEUE(T24.OFS.REPLY.QUEUE) TYPE(QLOCAL)
QUEUE(T24.SEAT.QUEUE) TYPE(QLOCAL)
QUEUE(T24.SEAT.REPLY.QUEUE) TYPE(QLOCAL)
QUEUE(T24.TCIB.CORP.QUEUE) TYPE(QLOCAL)
QUEUE(T24.TCIB.CORP.REPLY.QUEUE) TYPE(QLOCAL)
QUEUE(T24.TCIB.QUEUE) TYPE(QLOCAL)
QUEUE(T24.TCIB.WEALTH.QUEUE) TYPE(QLOCAL)
QUEUE(T24.TCIB.WEALTH.REPLY.QUEUE) TYPE(QLOCAL)
QUEUE(T24.TWS.QUEUE) TYPE(QLOCAL)
QUEUE(T24.TWS.REPLY.QUEUE) TYPE(QLOCAL)
You need to add all user exepct mqm who have to access to MQ. Including user for MQExplorer
You can create a specific group called mq1 then set specific priviledge on MQT24
where MQT24 is the queue manager, T24.OFS.QUEUE is the T24 queue mq1 is the group(you
can user -p for specific user ) and all +get +put +inq are the privileges
where MQT24 is the queue manager, T24.OFS.QUEUE is the T24 queue mqm is the group(you
can user -p for specific user ) and all +get +put +inq are the privileges
get
AppServer
JMS Server
WebServer
4.1.5.1 Configure the firewall on the AdminServer
[root@appsrv01 Temenos]#
# $WAS_HOME/bin/ProfileManagement/wct.sh
Under $TAFJ_HOME/AppServer/was you will find all the scripts to create profiles.
<product_name><Business_role><type><number>
<product_name>
T24
AML
TAP
<Business_role>
<type>
<number>
From 00 to 99
In our situation we will create on the Application layer a Manager Server for T24
i.e
Set the Profile name to T24AppMng01 and the Profile path to /profiles/T24AppMng01
Click the "Next" button
Set the IP and the port of the ManagerServer with the security credential admin/Temenos_1
# vi $TAFJ_HOME/appserver/was/setUpEnv.sh
# *********************************
# WAS
# *********************************
#export WAS_HOME=[WAS_HOME]
export HOST_NAME=192.168.1.161
export PROFILE_NAME=T24AppMng01
export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME=$NODE_NAME'Cell'
export DMGR_USER=admin
export DMGR_PASSWORD=Temenos_1
export DMGR_HOST=192.168.1.161
export DMGR_PORT=8879
# *********************************
# TAFJ_HOME
# *********************************
#export TAFJ_HOME=/opt/Temenos/TAFJ
#export CONF_PATH=$TAFJ_HOME/appserver/was/jython
#export
PATH=$WAS_HOME/bin:$WAS_HOME/profiles/$PROFILE_NAME/bin:$CONF_PATH:$P
ATH:. #export CONF_PATH=$TAFJ_HOME/appserver/was/jython
#export
PATH=$WAS_HOME/bin:$WAS_HOME/profiles/$PROFILE_NAME/bin:$CONF_PATH:$P
ATH:.
You can setup the profile as default and set a user and password the the Admin Console
# vi $TAFJ_HOME/appserver/was/createNode.sh
# -isDefault
# -adminUserName
# -adminPassword
~
# cd $TAFJ_HOME/appserver/was
# . ./setUpEnv.sh
# . ./createNode.sh
[t24user@appsrv01 was]$
Repeat the same process on Web Layer with the following parameters:
t24user@192.168.1.165's password:
[t24user@appsrv01 was]$
# vi $TEMENOS_HOME/Install/was/setUpEnv.sh
# *********************************
# WAS
# *********************************
#export WAS_HOME=[WAS_HOME]
export HOST_NAME=192.168.1.165
export PROFILE_NAME=T24WebMng01
export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME=$NODE_NAME'Cell'
export SERVER_NAME=
export DMGR_USER=admin
export DMGR_PASSWORD=Temenos_1
export DMGR_HOST=192.168.1.161
export DMGR_PORT=8879
# *********************************
# TAFJ_HOME
# *********************************
#export TAFJ_HOME=/opt/Temenos/TAFJ
#export CONF_PATH=$TAFJ_HOME/appserver/was/jython
#export
PATH=$WAS_HOME/bin:$WAS_HOME/profiles/$PROFILE_NAME/bin:$CONF_PATH:$P
ATH:. #export CONF_PATH=$TAFJ_HOME/appserver/was/jython
#export
PATH=$WAS_HOME/bin:$WAS_HOME/profiles/$PROFILE_NAME/bin:$CONF_PATH:$P
ATH:.
# cd $TEMENOS_HOME/Install/was/
# . ./setUpEnv.sh
# . ./createNode.sh
[t24user@WebSrv01 was]$
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMgr01/logs
/dmgr/startServer.log
To determin the port of the instance, check the AboutThisProfile.txt in the log folder of the
profile
# cat $WAS_HOME/profiles/T24AppMng01/logs/AboutThisProfile.txt
Location: /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMgr01
http://192.168.1.161:9060/ibm/console
Select the node T24AppMng01Node01 and set the Server name T24AppMng01
Click the "Next" button
Repeat the same process on Web Layer with the following parameters:
In the AdminConsole
Domain Structure
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMng01/log
s/nodeagent/stopServer.log
[t24user@appsrv01 bin]$
AppServer
JMS Server
WebServer
4.1.6.1 Configure the firewall on the AdminServer
[root@appsrv01 Temenos]#
# $WAS_HOME/bin/ProfileManagement/wct.sh
Under $TAFJ_HOME/AppServer/was you will find all the scripts to create profiles.
<product_name><Business_role><type><number>
<product_name>
T24
AML
TAP
<Business_role>
<type>
<number>
From 00 to 99
In our situation we will create on the Application layer a Manager Server for T24
i.e
Set the Profile name to T24AppMng01 and the Profile path to /profiles/T24AppMng01
Click the "Next" button
Set the IP and the port of the ManagerServer with the security credential admin/Temenos_1
# vi $TAFJ_HOME/appserver/was/setUpEnv.sh
# *********************************
# WAS
# *********************************
#export WAS_HOME=[WAS_HOME]
export HOST_NAME=192.168.1.161
export PROFILE_NAME=T24AppMng01
export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME=$NODE_NAME'Cell'
export DMGR_USER=admin
export DMGR_PASSWORD=Temenos_1
export DMGR_HOST=192.168.1.161
export DMGR_PORT=8879
# *********************************
# TAFJ_HOME
# *********************************
#export TAFJ_HOME=/opt/Temenos/TAFJ
#export CONF_PATH=$TAFJ_HOME/appserver/was/jython
#export
PATH=$WAS_HOME/bin:$WAS_HOME/profiles/$PROFILE_NAME/bin:$CONF_PATH:$P
ATH:. #export CONF_PATH=$TAFJ_HOME/appserver/was/jython
#export
PATH=$WAS_HOME/bin:$WAS_HOME/profiles/$PROFILE_NAME/bin:$CONF_PATH:$P
ATH:.
You can setup the profile as default and set a user and password the the Admin Console
# vi $TAFJ_HOME/appserver/was/createNode.sh
# -isDefault
# -adminUserName
# -adminPassword
~
# cd $TAFJ_HOME/appserver/was
# . ./setUpEnv.sh
# . ./createNode.sh
[t24user@appsrv01 was]$
Repeat the same process on Web Layer with the following parameters:
t24user@192.168.1.165's password:
[t24user@appsrv01 was]$
# vi $TEMENOS_HOME/Install/was/setUpEnv.sh
# *********************************
# WAS
# *********************************
#export WAS_HOME=[WAS_HOME]
export HOST_NAME=192.168.1.165
export PROFILE_NAME=T24WebMng01
export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME=$NODE_NAME'Cell'
export SERVER_NAME=
export DMGR_USER=admin
export DMGR_PASSWORD=Temenos_1
export DMGR_HOST=192.168.1.161
export DMGR_PORT=8879
# *********************************
# TAFJ_HOME
# *********************************
#export TAFJ_HOME=/opt/Temenos/TAFJ
#export CONF_PATH=$TAFJ_HOME/appserver/was/jython
#export
PATH=$WAS_HOME/bin:$WAS_HOME/profiles/$PROFILE_NAME/bin:$CONF_PATH:$P
ATH:. #export CONF_PATH=$TAFJ_HOME/appserver/was/jython
#export
PATH=$WAS_HOME/bin:$WAS_HOME/profiles/$PROFILE_NAME/bin:$CONF_PATH:$P
ATH:.
# cd $TEMENOS_HOME/Install/was/
# . ./setUpEnv.sh
# . ./createNode.sh
[t24user@WebSrv01 was]$
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMgr01/logs
/dmgr/startServer.log
To determin the port of the instance, check the AboutThisProfile.txt in the log folder of the
profile
# cat $WAS_HOME/profiles/T24AppMng01/logs/AboutThisProfile.txt
Location: /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMgr01
http://192.168.1.161:9060/ibm/console
Select the node T24AppMng01Node01 and set the Server name T24AppMng01
Click the "Next" button
Repeat the same process on Web Layer with the following parameters:
In the AdminConsole
Domain Structure
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppMng01/log
s/nodeagent/stopServer.log
[t24user@appsrv01 bin]$
5 T24 Configuration
5.1 Configuring T24 in embedded mode (1 Tier)
AdminServer
AppServer
JMS Server
WebServer
Before copy BrowserWeb.war in the install folder you have to make some changes.
Remove xmlparserv2.jar
<resRefBindings xmi:id="ResourceRefBinding_jmsConnectionFactory"
jndiName="jms/t24ConnectionFactory">
<bindingResourceRef href="WEB-INF/web.xml#ResourceRef_jmsConnectionFactory"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_t24OFSQueue"
jndiName="jms/t24BROWSERQueue">
<bindingResourceRef href="WEB-INF/web.xml#ResourceRef_t24OFSQueue"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_t24OFSReplyQueue"
jndiName="jms/t24BROWSERReplyQueue">
<bindingResourceRef href="WEB-INF/web.xml#ResourceRef_t24OFSReplyQueue"/>
</resRefBindings>
# cd $TAFJ_HOME/appserver/was/jython
# vi tafj.py
############################################################
# Node details
server_name="T24AppStd01"
node_name=server_name+"Node01"
cell_name=node_name+"Cell"
#
############################################################
# JVM param
min_mem="1024"
max_mem="1024"
############################################################
# Path details
tafjHome="/u01/Temenos/TAFJ"
t24Home="/u01/Temenos/T24"
############################################################
# database details
# driver = [oracle11g,oracle-12c,db2_v10.x,h2-1.x.x]
dbDriver="oracle-12c"
dbHostName="192.168.1.159"
dbPort="1521"
dbName="T24"
dbUser="t24"
dbPwd="t24"
############################################################
dbROHostName=""
dbROPort=""
dbROdbName=""
dbROdbUser=""
dbROdbPwd=""
############################################################
# MQ Details details
mqManager="MQT24"
mqServerName=""
mqPort="1414"
mqChannel="T24Channel"
############################################################
# Browser details
browserWebHome="/u01/Temenos/Install"
Setup Environment
orac
Driver classpath${TAFJ_HOME}/dbdrivers/oracle-
12c/xmlparserv2.jar;${TAFJ_HOME}/dbdrivers/oracle-12c/xdb6.jar
JMS Environment
T24Bus created
t24ConnectionFactory created
t24OFSQueue created
t24OFSReplyQueue created
t24BROWSERQueue created
t24BROWSERReplyQueue created
t24ARCMOBQueue created
t24ARCMOBReplyQueue created
t24TWSQueue created
t24TWSReplyQueue created
t24TCIBQueue created
t24TCIBReplyQueue created
t24TCIBCORPReplyQueue created
t24TCIBWEALTHQueue created
t24TCIBWEALTHReplyQueue created
t24CALLATQueue created
t24CALLATReplyQueue created
t24AMLQueue created
t24AMLReplyQueue created
t24SEATQueue created
t24SEATReplyQueue created
t24IFInboundQueue created
t24IFOutboundQueue created
t24EXECQueue created
tecEventsTopic created
Created JDBC Provider with the name :T24 XA ORACLE JDBC Driver
Created JDBC Provider with the name :T24 NON-XA ORACLE JDBC Driver
Created JDBC DataSource with the name :TAFJ XA ORACLE Data source
Created JDBC DataSource with the name :TAFJ NON-XA ORACLE Locking Data source
Setting the properties for DataSource :TAFJ NON-XA ORACLE Locking Data source
ADMA5058I: Application and module versions are validated with versions of deployment
targets.
ADMA5081I: The bootstrap address for client module is configured in the WebSphere
Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5011I: The cleanup of the temp directory for application TAFJJEE_EAR is complete.
TAFJEE_EAR deployed
---------------------------------------------------------------
Usage: AdminApplication.configureWebModulesOfAnApplication("TAFJJEE_EAR",
"TAFJServices", "1000", "PARENT_LAST")
---------------------------------------------------------------
Setup Browser
//
//
// NOTE: Syntax errors in the policy files will cause the enterprise application FAIL to start.
// Extreme care should be taken when editing these policy files. It is advised to use
// the policytool provided by the JDK for editing the policy files
// (WAS_HOME/java/jre/bin/policytool).
//
};
};
};
};
};
ADMA5058I: Application and module versions are validated with versions of deployment
targets.
ADMA5081I: The bootstrap address for client module is configured in the WebSphere
Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5011I: The cleanup of the temp directory for application BrowserWeb_war is complete.
[t24user@appsrv01 jython]$
http://192.168.1.161:9060/ibm/console
Data sources > TAFJ XA ORACLE Data source > JAAS - J2C authentication data >
T24AppStd01Node01/T24 database
5.1.1.5 Restart the application Server.
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppStd01/logs/
T24AppSrv01/stopServer.log
# $WAS_HOME/bin/startServer.sh T24AppStd01
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppStd01/logs/
T24AppSrv01/startServer.log
[t24user@appsrv01 bin]$
http://192.168.1.161:9080/TAFJEE/
http://192.168.1.161:9080/BrowserWeb
5.2 Configuring T24 in embedded mode (2
Tiers)
5.2.1 Configuring T24 in embedded mode 2 Tiers in WebSphere
AppServer
JMS Server
WebServer
Before copy BrowserWeb.war in the install folder you have to make some changes.
Remove xmlparserv2.jar
<resRefBindings xmi:id="ResourceRefBinding_jmsConnectionFactory"
jndiName="jms/t24ConnectionFactory">
<bindingResourceRef href="WEB-INF/web.xml#ResourceRef_jmsConnectionFactory"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_t24OFSQueue"
jndiName="jms/t24BROWSERQueue">
<bindingResourceRef href="WEB-INF/web.xml#ResourceRef_t24OFSQueue"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_t24OFSReplyQueue"
jndiName="jms/t24BROWSERReplyQueue">
<bindingResourceRef href="WEB-INF/web.xml#ResourceRef_t24OFSReplyQueue"/>
</resRefBindings>
# cd $TAFJ_HOME/appserver/was/jython
# vi tafj.py
############################################################
# Node details
server_name="T24AppMng01"
node_name=server_name+"Node01"
cell_name=node_name+"Cell"
cluster_name=""
############################################################
# JVM param
min_mem="1024"
max_mem="1024"
############################################################
# Path details
tafjHome="/u01/Temenos/TAFJ"
t24Home="/u01/Temenos/T24"
############################################################
# database details
# driver = [oracle11g,oracle-12c,db2_v10.x,h2-1.x.x]
dbDriver="oracle-12c"
dbHostName="192.168.1.159"
dbPort="1521"
dbName="T24"
dbUser="t24"
dbPwd="t24"
############################################################
dbROHostName=""
dbROPort=""
dbROdbName=""
dbROdbUser=""
dbROdbPwd=""
#
############################################################
# MQ Details details
mqManager="MQT24"
mqServerName=""
mqPort="1414"
mqChannel="T24Channel"
############################################################
# Browser details
browserWebHome="/u01/Temenos/Install"
Setup Environment
orac
Driver classpath${TAFJ_HOME}/dbdrivers/oracle-
12c/xmlparserv2.jar;${TAFJ_HOME}/dbdrivers/oracle-12c/xdb6.jar
JMS Environment
T24Bus created
t24ConnectionFactory created
t24OFSQueue created
t24OFSReplyQueue created
t24BROWSERQueue created
t24BROWSERReplyQueue created
t24ARCMOBReplyQueue created
t24TWSQueue created
t24TWSReplyQueue created
t24TCIBQueue created
t24TCIBReplyQueue created
t24TCIBCORPQueue created
t24TCIBCORPReplyQueue created
t24TCIBWEALTHQueue created
t24TCIBWEALTHReplyQueue created
t24CALLATQueue created
t24CALLATReplyQueue created
t24AMLQueue created
t24AMLReplyQueue created
t24SEATQueue created
t24SEATReplyQueue created
t24SEATQueue - t24SEATMessageMDB activation created
t24IFInboundQueue created
t24IFOutboundQueue created
t24EXECQueue created
tecEventsTopic created
Created JDBC Provider with the name :T24 XA ORACLE JDBC Driver
Created JDBC Provider with the name :T24 NON-XA ORACLE JDBC Driver
Created JDBC DataSource with the name :TAFJ XA ORACLE Data source
Created JDBC DataSource with the name :TAFJ NON-XA ORACLE Locking Data source
Setting the properties for DataSource :TAFJ NON-XA ORACLE Locking Data source
ADMA5058I: Application and module versions are validated with versions of deployment
targets.
ADMA5081I: The bootstrap address for client module is configured in the WebSphere
Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5011I: The cleanup of the temp directory for application TAFJJEE_EAR is complete.
TAFJEE_EAR deployed
---------------------------------------------------------------
Usage: AdminApplication.configureWebModulesOfAnApplication("TAFJJEE_EAR",
"TAFJServices", "1000", "PARENT_LAST")
---------------------------------------------------------------
Setup Browser
//
//
// NOTE: Syntax errors in the policy files will cause the enterprise application FAIL to start.
// Extreme care should be taken when editing these policy files. It is advised to use
// the policytool provided by the JDK for editing the policy files
// (WAS_HOME/java/jre/bin/policytool).
//
};
};
};
grant codeBase "file:${webComponent}" {
};
};
ADMA5058I: Application and module versions are validated with versions of deployment
targets.
ADMA5081I: The bootstrap address for client module is configured in the WebSphere
Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5011I: The cleanup of the temp directory for application BrowserWeb_war is complete.
BrowserWeb deployed
[t24user@appsrv01 jython]$
http://192.168.1.161:9060/ibm/console
Login with user and password Admin/Temenos_1
Data sources > TAFJ XA ORACLE Data source > JAAS - J2C authentication data >
T24AppStd01Node01/T24 database
In the AdminConsole
Domain Structure
In the AdminConsole
Domain Structure
http://192.168.1.161:9080/TAFJEE/
5.1.1.7 BrowserWeb Application
http://192.168.1.161:9080/BrowserWeb
5.3 Configuring T24 in embedded mode
(Cluster 2 Tiers)
5.3.1 Configuring T24 in embedded mode Cluster 2 Tiers in WebSphere
AppServer
JMS Server
WebServer
5.4 Configuring T24 in embedded mode (3
Tiers)
5.4.1 Configuring T24 in embedded mode 3 Tiers in WebSphere
AppServer
JMS Server
Before copy BrowserWeb.war in the install folder you have to make some changes.
Remove xmlparserv2.jar
<resRefBindings xmi:id="ResourceRefBinding_jmsConnectionFactory"
jndiName="jms/t24ConnectionFactory">
<bindingResourceRef href="WEB-INF/web.xml#ResourceRef_jmsConnectionFactory"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_t24OFSQueue"
jndiName="jms/t24BROWSERQueue">
<bindingResourceRef href="WEB-INF/web.xml#ResourceRef_t24OFSQueue"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_t24OFSReplyQueue"
jndiName="jms/t24BROWSERReplyQueue">
<bindingResourceRef href="WEB-INF/web.xml#ResourceRef_t24OFSReplyQueue"/>
</resRefBindings>
Save all and FTP BrowserWeb.jar in $TEMENOS_HOME/Install
# cd $TAFJ_HOME/appserver/was/jython
# vi tafj.py
############################################################
# Node details
server_name="T24AppMng01"
node_name=server_name+"Node01"
cell_name=node_name+"Cell"
cluster_name=""
############################################################
# JVM param
min_mem="1024"
max_mem="1024"
#
############################################################
# Path details
tafjHome="/u01/Temenos/TAFJ"
t24Home="/u01/Temenos/T24"
############################################################
# database details
# driver = [oracle11g,oracle-12c,db2_v10.x,h2-1.x.x]
dbDriver="oracle-12c"
dbHostName="192.168.1.159"
dbPort="1521"
dbName="T24"
dbUser="t24"
dbPwd="t24"
############################################################
dbROHostName=""
dbROPort=""
dbROdbName=""
dbROdbUser=""
dbROdbPwd=""
############################################################
# MQ Details details
mqManager="MQT24"
mqServerName="192.168.1.163"
mqPort="1414"
mqChannel="T24_CHANNEL"
############################################################
# Browser details
#browserWebHome="/u01/Temenos/Install"
5.4.1.3 Configure T24/TAFJ in the Application Server
Setup Environment
orac
Driver classpath${TAFJ_HOME}/dbdrivers/oracle-
12c/xmlparserv2.jar;${TAFJ_HOME}/dbdrivers/oracle-12c/xdb6.jar
JMS Environment
T24Bus created
t24ConnectionFactory created
t24OFSQueue created
t24OFSReplyQueue created
t24BROWSERQueue created
t24BROWSERReplyQueue created
t24ARCMOBQueue created
t24ARCMOBReplyQueue created
t24TWSQueue created
t24TWSReplyQueue created
t24TCIBQueue created
t24TCIBReplyQueue created
t24TCIBCORPQueue created
t24TCIBCORPReplyQueue created
t24TCIBWEALTHQueue created
t24TCIBWEALTHReplyQueue created
t24CALLATQueue created
t24CALLATReplyQueue created
t24AMLQueue created
t24AMLReplyQueue created
t24SEATQueue created
t24SEATReplyQueue created
t24IFInboundQueue created
t24IFOutboundQueue created
t24EXECQueue created
tecEventsTopic created
Created JDBC Provider with the name :T24 XA ORACLE JDBC Driver
Created JDBC Provider with the name :T24 NON-XA ORACLE JDBC Driver
Created JDBC DataSource with the name :TAFJ XA ORACLE Data source
Setting the properties for DataSource :TAFJ NON-XA ORACLE Locking Data source
ADMA5058I: Application and module versions are validated with versions of deployment
targets.
ADMA5081I: The bootstrap address for client module is configured in the WebSphere
Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5011I: The cleanup of the temp directory for application TAFJJEE_EAR is complete.
TAFJEE_EAR deployed
---------------------------------------------------------------
Usage: AdminApplication.configureWebModulesOfAnApplication("TAFJJEE_EAR",
"TAFJServices", "1000", "PARENT_LAST")
---------------------------------------------------------------
Setup Browser
//
//
// NOTE: Syntax errors in the policy files will cause the enterprise application FAIL to start.
// Extreme care should be taken when editing these policy files. It is advised to use
// the policytool provided by the JDK for editing the policy files
// (WAS_HOME/java/jre/bin/policytool).
//
};
grant codeBase "file:${jars}" {
};
};
};
};
ADMA5058I: Application and module versions are validated with versions of deployment
targets.
ADMA5081I: The bootstrap address for client module is configured in the WebSphere
Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5011I: The cleanup of the temp directory for application BrowserWeb_war is complete.
BrowserWeb deployed
[t24user@appsrv01 jython]$
http://192.168.1.161:9060/ibm/console
Login with user and password Admin/Temenos_1
Data sources > TAFJ XA ORACLE Data source > JAAS - J2C authentication data >
T24AppStd01Node01/T24 database
In the AdminConsole
Domain Structure
In the AdminConsole
Domain Structure
http://192.168.1.161:9080/TAFJEE/
5.4.1.7 BrowserWeb Application
http://192.168.1.161:9080/BrowserWeb
5.5 Configuring T24 in embedded mode
(Cluster 3 Tiers)
5.5.1 Configuring T24 in embedded mode Cluster 3 Tiers in WebSphere
AppServer
The JMSServer will have 1 role:
JMS Server
WebServer
TAFJ Setup
What is TAFJ
TAFJ (Temenos Application Framework Java) is a Pick BASIC runtime and compiler, written in
100% java. It allows compiling and running Pick BASIC programs. TAFJ has been written
specifically for T24 needs, and all tests and proof of concepts have been done using T24. TAFJ
also manage the connectivity on JDBC compliant databases like jBASE, Oracle, Microsoft SQL
Server, DB2, derby, derby (Embedded). It comes with an embedded exporting tool for migrate
your Pick data to Oracle.
Overview
Install guide
Prerequisites
Java JDK
To install TAFJ, the only prerequisite is having a Java Development Kit (JDK) version 1.6.x or
1.7.x installed. To check what version of java you have, type in a console:
>java -version
If the version reported is not 1.6.x or 1.7.x, you should install it. Java JDK can be downloaded
here:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
NOTE: If you have installed java 1.6 but the command java -version doesn't report the correct
version, this is certainly because your PATH environment variable points to another version.
This is a bad practice to have your java virtual machine (VM) in the PATH. We highly
recommend removing it. The best practice is to set-up an environment variable called
JAVA_HOME pointing to the root directory of your Java Development Kit (JDK) installation.
Then, you could reference JAVA_HOME/bin in your PATH environment variable.
On Unix/Linux/:
export JAVA_HOME=<path_to_your_jdk>
On Windows:
START Menu > Settings > Control Panel > System > Advanced > Environment Variables
You could use System variables (Preferred) OR User variables to set the JAVA_HOME.
set JAVA_HOME=<path_to_your_jdk>
Setup TAFJ
The installation comes as a single .tar file. On Unix/Linux, run the tar -xf <filename>
command. On Windows, you can use 7zip to extract the zip Contents.
Setup_TAFJ.[version].jar
Setup_TAFJ.[version].sh
Setup_TAFJ.[version].bat
Then run the script .sh on UNIX or .bat on Windows operating system.
Note: That the JAVA_HOME environment variable must be set before running the scripts.
The following section will show a typical install procedure on a UNIX platform. The procedure
will be exactly the same on Windows. The user input is in [blue]. If you have values in
brackets, these are the default values (typing <ENTER> is accepting the default).
Note: If you do not have the T24 sources you will need to give any existing directory in order to
continue the setup. The insert directory is optional.
On UNIX:
$ . ./Setup_TAFJ.<version>.sh
On Windows:
> Setup_TAFJ.<version>.bat
-----------------
YAJI v 1.6
Starting setup...
========================================================
========================================================
========================================================
C:\TAFJ_GA\
appserver/icefaces/ (dir)
appserver/icefaces/jsf/ (dir)
appserver/icefaces/jsf/iceFaces/ (dir)
appserver/icefaces/jsf/iceFaces/1.8.2/ (dir)
appserver/icefaces/jsf/iceFaces/1.8.2/pushserver/ (dir)
appserver/icefaces/jsf/iceFaces/1.8.2/pushserver/push-server.war (bin)
appserver/jboss/ (dir)
appserver/jboss/jboss-app.xml (text)
appserver/jboss/jboss-classloading.xml (text)
appserver/jboss/openmq-ds.xml (text)
appserver/jboss/opnemq-queue-ds.xml (text)
appserver/jboss/readme.txt (text)
appserver/jboss/t24-ds.xml (text)
appserver/jboss/tafj-service.xml (text)
appserver/TAFJJEE_EAR.ear (bin)
appserver/was/ (dir)
appserver/was/createManagement.bat (text)
TAFJSync/log4j-1.2.13.jar (bin)
TAFJSync/logger.properties (text)
TAFJSync/logs (text)
TAFJSync/README (text)
TAFJSync/TAFJSyncServer.jar (bin)
TAFJSync/tSync (text)
Updating : 'C:\TAFJ_GA\conf\tafj.properties'.
Updating : 'C:\TAFJ_GA\conf\.properties'.
Updating : 'C:\TAFJ_GA\conf\.data'.
Updating : 'C:\TAFJ_GA\dbscripts\oracle\javaload'.
Updating : 'C:\TAFJ_GA\dbscripts\oracle\javaload.bat'.
Updating : 'C:\TAFJ_GA\dbscripts\oracle\javaunload'.
Updating : 'C:\TAFJ_GA\dbscripts\oracle\javaunload.bat'.
===========================================================
===========================================================
<TAFJ_HOME>/
appserver/: The directory containing the different application server configuration like jboss,
Websphere application server etc.
bin/: The directory containing the different executable scripts (tRun, tCompile, ...).
data/: This directory contains classes and java folder. classes folder holds the all the compiled
class files (.class) and java folder holds .java files
dbdrivers/: The directory containing the drivers needed to different database communication.
eclipse/plugins/: The directory containing all the plugins to enable the TAFJ perspective in
eclipse IDE.
ext/: The default directory containing java extension (see specific chapter).
TAFJSessionMonitor/: The directory containing some TAFJ MV42 Monitor tar.gz file.
<TAFJ_HOME>/data/
/tafj/classes/: The default directory where the compiled BASIC goes (like globuslib).
Once the setup of TAFJ is completed and if you have eclipse v.3.7.x or above installed, you can
simply link the contents of the directory <TAFJ_HOME>/eclipse/plugins in your directory
<ECLIPSE_HOME>/dropins.
2. Edit the file tafj.link and add a property key : path=<relative_path_to _TAFJ_HOME>
3. Set the path with the relative path from <ECLIPSE_HOME> to <TAFJ_HOME>
i.e
+---3rdParty
| +---eclipse
+---TAFJ
path=../../TAFJ
Once done, in order to verify that all TAFJ Plug-ins are loaded with eclipse, you can go in the
Eclipse menu:
Help -> About Eclipse SDK, press on Installation Details, and Tab: Plug-ins
Setup project
A project is a specific setting of properties. All properties of a project are in file properties in
<TAFJ_HOME>\conf. the name of the project is given by the name of the properties file.
To Create a new project base on a properties file, copy the file <TAFJ_HOME>\conf\.properties
and renamed it with the name of your project.
i.e
T24.properties
MYPROJECT.properties
All scripts in <TAFJ_HOME>\bin need a project (properties) to work. To specify the project to
use with a script, pass the argument: -cf ProjectName
i.e
tRun cf T24.properties EX
You can omit the -cf argument to use the default project. The default project is specified in the
file <TAFJ_HOME>\conf\.default. After a setup of TAFJ the default project in tafj.properties.
By conventions, the java and class path for TAFJ of a project have to be set under:
i.e
for myProject.properties :
# by the compiler
temn.tafj.directory.java = <tafj.home>\data/myProject/java
# by the compiler
temn.tafj.directory.classes = <tafj.home>\data/myProject/classes
Logger
All executions are logged with TAFJ. TAFJ use the standard LOG4J open source.
In this file you can change the level and the appender of all loggers. For more information read
the documentation of LOG4J.
http://logging.apache.org/log4j/1.2/manual.html
File TAFJTrace.properties :
#####################################
# Note :The 'File' must have only slashes '/' and never backslashes ''
#####################################
log4j.debug=false
log4j.rootLogger=OFF
log4j.logger.T24=INFO, t24
log4j.logger.BASIC=ERROR, basic
log4j.logger.PRINTER=ERROR, printer
log4j.logger.DATABASE=ERROR, database
log4j.logger.JQL=ERROR, jql
log4j.logger.LOCKING=INFO, locking
log4j.logger.COMPILER=WARN, compiler
log4j.logger.DEPENDENCY=INFO, dependency
log4j.logger.RUNTIME=ERROR, runtime
log4j.logger.DBIMPORT=ERROR, dbimport
log4j.logger.SQLTRACE=ERROR, sqltrace
log4j.logger.ITYPE=ERROR, itype
log4j.logger.EXECUTE=ERROR, execute
log4j.logger.IOSERVER=INFO, ioserver
log4j.logger.MDB=ERROR, mdb
log4j.logger.EJB=ERROR, ejb
log4j.logger.MONITOR=ERROR, monitor
log4j.logger.FILTER=ERROR, filter
log4j.logger.COBERTURA=ERROR, cobertura
#log4j.logger.org.apache.tools.ant=ERROR, merge
log4j.logger.DBIMPORT-COMPARER=ERROR, dbcomparer
log4j.logger.UPDATER=DEBUG, updater
log4j.logger.JQL-NOTSUPPORTED=ERROR, jqlnotsupported
log4j.logger.API=INFO, api
log.directory=<PATH_TO_YOUR_TAFJ_LOG_FOLDER>
log.directory.t24=<PATH_TO_YOUR_T24_LOG_FOLDER>
It has to be set at TAFJ start up, and should be done through environment properties or JVM
arguments.
You cannot use the tafj.properties file for that purpose as loggers get initialized before tafj
properties get loaded.
In a multi-tenant environment you may want to define a specific logger context to differentiate
the logs from the different tenants. It could also be useful for debugging purpose where a user
can define its own context.
By using property
log.context=<YOUR_CONTEXT_NAME>
When using a context you will also generate a dedicated file to configure your appenders:
TAFJTrace.<YOUR_CONTEXT_NAME>.properties file.
Like log directories properties it has to be set at TAFJ start up, and should be done through
environment properties or JVM arguments.
Properties
TAFJ doesnt use Environment Variables. All setup for TAFJ is based on a properties file.
.properties is a file extension for files used in TAFJ related technologies to store the
configurable parameters of an application. These are known as Property Resource .
Each parameter is stored as a pair of strings, one storing the name of the parameter (called the
key), and the other storing the value
All Properties can be overload with -D<key>=<value> set to the JVM (Java Virtual Machine)
A string as a value
i.e.
tafj.home = \Temenos\T24Enterprise\TAFJ
i.e.
tafj.home = \Temenos\T24Enterprise\TAFJ
temn.tafj.runtime.directory.current = <tafj.home>/UD
tafj.home = <%TAFJ_HOME%>
temn.tafj.runtime.directory.current = <$TAFJ_HOME>/UD
Printer
TAFJ use the JPS (Java Print Service.
On Windows, JPS use the Printer Manager. You can connect any printers installed on Windows.
The Printer has to be online.
On UNIX/LINUX, JPS use CUPS (Common Unix Printing System). CUPS is not install by
default. You have to install it. Please refer to your OS documentation for the installation.
In the properties file, category printer, the setup of TAFJ automatically adds your printers online
with default driver name PRN #. You can affect the channel to any drivers name.
#********************************************************************
#
# Printer
#********************************************************************
# Printer list
# This list has been generated during the setup. You can modify it at any moment to reflect any
# If the Channel 1 is missing (or remed-out), it will be defaulted to the default printer (if any)
#Specify where is the &HOLD& directory when SETPTR is used with the HOLD option
temn.tafj.printer.directory.hold = <temn.tafj.runtime.directory.current>/&HOLD&
temn.tafj.channel.name.0 = PRN0
temn.tafj.driver.name.0 = PRN0
temn.tafj.driver.class.0 = com.temenos.tafj.jlp.drivers.jPrinterDriver
__________________________________________________________________
Home : 'D:\Temenos\T24Enterprise\TAFJ'
Version : DEV_201404
__________________________________________________________________
java.home : D:\Temenos\T24Enterprise\3rdParty\java\jdk1.7.0_51-64\jre
java.version : 1.7.0_51
os.arch : amd64
os.name : Windows 7
HostName : wkshome01
IP Address : 10.244.1.137
__________________________________________________________________
- Project : 'tafj'
------------------------------------------------------------------
------------------------------------------------------------------
DataBase URL :
DataBase user :
------------------------------------------------------------------
Locking name :
------------------------------------------------------------------
UD encoding : UTF-8
------------------------------------------------------------------
Timezone : Europe/London
Local : en_US
------------------------------------------------------------------
------------------------------------------------------------------
temn.tafj.runtime.port.range =
Scenario 1
All the servers have a NFS/MAP to a share HDD where TAFJ is installed.
No Need to setup any port range. All servers will share the uid (unique ID file).
Scenario 2
You need to setup for each TAFJ a port range. Each servers will have his own uid (unique ID
file).
WebSphere v7 v8 configuration for T24
solution with TAFJ
You can configure the following websphere resources either by using the administrative console
or by running jython scripts. This document only covers script mode. For console mode, please
refer to Websphere documentation.
Script Mode
The configuration can be run automatically on your server by using some jython scripts.
Note: These scripts cant be used on an existing configuration. To create a new configuration
from scratch, first create a new profile and then run the configuration.
Creating a profile
You can easily create a new profile by using the tool %TAFJ_HOME% \appserver\was\
createStandalone.bat.
Prerequisites
To run a jython script your server must be started and your PATH must contain:
%WAS_HOME%\bin: the path to your websphere\bin directory
Edit the file setUpEnv and set the following properties i.e. :
set HOST_NAME=localhost
set PROFILE_NAME=AppSrv01
set NODE_NAME=%PROFILE_NAME%Node01
set CELL_NAME=%NODE_NAME%Cell
set SERVER_NAME=server1
You can then launch createStandalone.bat and the targeted profile will be created in your
WAS_HOME\profiles directory.
Edit the file Create createStandalone and choose the param enableAdminSecurity to add at the
end of the command to the scripts:
-enableAdminSecurity false
Or
Launch createStandalone
One step configuration
You can run all configurations: environment configuration, JMS configuration, JDBC
configuration, application deployments for T24 and TAFJ by using a single script or by doing a
one step at a time configuration.
Previously you have had to fill out the main configuration file:
%TAFJ_HOME%\appserver\was\jython\ tafj.py.
This file contains the variables that are needed at each configuration step. If you need more
information about these variables or if you want to adapt the scripts to your specific use case
please refer to the next section of this document.
The below assumes you are using a local Oracle database with database name TAFJDB and no
MQ Series message broker.
If you want to use another database or MQ, fill out the below properties in tafj.py and modify
the file T24Setup.py appropriately.
############################################################
# Node details
cell_name="AppSrv01Node01Cell"
node_name="AppSrv01Node01"
server_name="server1"
############################################################
# Path details
tafjHome="D:\Temenos\Reference\Temenos\TAFJ"
t24Home="D:\Temenos\Reference\Temenos\T24\lib\t24lib"
############################################################
# database details
dbDriver="h2_1.3.175"
dbHostName="localhost"
dbPort="[port]"
dbName="T24"
dbUser="mbtafj"
dbPwd="mbtafj"
#dbROHostName="[hostname]"
#dbROPort="[port]"
#dbROdbName="[sid]"
#dbROdbUser="[user]"
#dbROdbPwd="[password]"
############################################################
oracleXDBjarName="xdb.jar"
############################################################
#use type 4
#use type 2
dbDriverType="4"
############################################################
# Browser details
############################################################
# MQ Details details
mqManager="MQT24"
mqServerName="[IP]"
mqPort="1414"
mqChannel="T24Channel"
Multiple profiles
Please note that if you have multiple profiles defined and if you want to execute the scripts
against a profile which is not the default one you will have to add to the command presented
below the profile name.
-profileName %PROFILE_NAME%
Security enabled
If you have enabled the admin console security you will be prompt to enter your admin user and
password when executing the script or you will have to add to the command presented below
your admin user and password.
Edit the file and comment and uncomment what you need:
execfile('jmsConfiguration.py')
#or
#execfile('mqConfiguration.py')
execfile('ORACLEConfiguration.py')
#or
#execfile('DB2Configuration.py')
#or
#execfile('MSSQLConfiguration.py')
#or
#execfile('H2Configuration.py')
execfile('TAFJapplicationDeployment.py')
execfile('T24applicationDeployment.py')
password: *******
Click OK.
Click Apply then Click Save.
This section will cover in details each configuration step presented above in the One step
configuration section.
If you have executed the One step configuration you dont need to execute the following
scripts.
Environment configuration
TAFJ_HOME, ORACLE_TAFJ_JDBC_DRIVER_PATH,
T24_MODELBANK_SHAREDLIB, TAFJ shared libraries, -Dtafj.home
Before running it you have to define some parameters such as node, cell and server name to set
the scope of the configuration and tafjHome, t24Home to specify the environment variable
values.
cell_name="localhostNode01Cell"
node_name="localhostNode01"
server_name="server1"
tafjHome="C:/product/appserver/websphere/TAFJ"
t24Home="C:/product/appserver/websphere/T24"
Multiple profiles
Please note that if you have multiple profiles defined and if you want to execute the scripts
against a profile which is not the default one you will have to add to the command presented
below the profile name.
-profileName %PROFILE_NAME%
Security enabled
If you have enabled the admin console security you will be prompt to enter your admin user and
password when executing the script or you will have to add to the command presented below
your admin user and password.
You can browse the administrative console to check that this step has been correctly done.
Environment WebSphere variables
Server -> Server Type -> WebSphere application servers -> #profileName# -> (Server
infrastructure) Java and Process Management ->Process definition -> Java Virtual Machine
Before running it you have to define some parameters such as node, cell and server name to set
the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file. You
might have already done it previously in the environment configuration step.
Launch the following command in the command line (refer to Environment configuration for
additional command parameters).
You can browse the administrative console to check this step has been correctly done.
Message engines status (under Buses->T24 Bus -> Messaging engines) should automatically be
(Started).
Check connection factory was created:
When you setup the datasource you have to use the drivers provide by the database. The
%TAFJ_HOME%\DBDrivers is just a helper. We cannot guaranty the drivers we provide with
TAFJ is working for all version of Database.
Before running it you have to define some parameters such as node, cell and server name to set
the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file. You
must also define the following properties to identify your Oracle database and provide a user id
and password for authentication i.e. :
dbDriver="oracle-12c"
dbHostName="172.16.22.102"
dbPort="1521"
dbName="MB2013"
dbUser="mbtafj"
dbPwd="mbtafj"
Launch the following command in the command line (refer to Environment configuration for
additional command parameters).
You can browse the administrative console to check this step has been correctly done.
Note: The property dbPwd is not correctly set, you have to run the administrative console to re-
enter it manually as shown below.
password: *******
Click OK.
Before running it you have to define some parameters such as node, cell and server name to set
the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file. You
must also define the following properties to identify your DB2 database and provide a user id
and password for authentication i.e. :
dbDriver="db2_v10.1"
dbHostName="localhost"
dbPort="50000"
dbDriverType="4"
dbName="MB2013"
dbUser="mbtafj"
dbPwd="mbtafj"
Launch the following command in the command line (refer to Environment configuration for
additional command parameters).
You can browse the administrative console to check this step has been correctly done.
Note: The property dbPwd is not correctly set, you have to run the administrative console to re-
enter it manually as shown below.
password: *******
Click OK.
dbDriver="sqljdbc_1.2"
dbServerName="localhost"
dbPort="1433"
dbName="R14DB"
dbUser="R14DB"
dbPwd="R14DB"
Launch the following command in the command line (refer to Environment configuration for
additional command parameters).
You can browse the administrative console to check this step has been correctly done.
Note: The property dbPwd is not correctly set, you have to run the administrative console to re-
enter it manually as shown below.
password: *******
Click OK.
Click Apply then Click Save.
Before running it you have to define some parameters such as node, cell and server name to set
the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file. You
must also define the tafjHome as root folder to locate the applications to be deployed i.e. :
tafjHome="C:/product/appserver/websphere/TAFJ"
Launch the following command in the command line (refer to Environment configuration for
additional command parameters).
You can then browse the administrative console to check they have been correctly deployed and
started.
Console Mode
You could also manually deploy or redeploy TAFJJEE_EAR.
Select local file deployment option and the TAFJJEE_EAR.ear file under %
TAF_HOME%\appserver folder and click on next.
Click Next.
Validate at the end of the installation processing that TAFJJEE_EAR.ear application was well
installed.
Click Save.
http://localhost:8080/TAFJEE
tDiag Servlet
TAFJJEE_WAR_TAFJ contains a servlet which could be used to get details about TAFJ
installation
http://localhost:8080/TAFJEE/tDiag
i.e.
tShow Servlet
TAFJJEE_WAR_TAFJ contains a servlet which could be used to get compilation details about a
specific routine
http://localhost:8080/TAFJEE/tShow
i.e.
TAFJJEE_WAR_TAFJ contains a servlet which could be used to post message to the JMS queue
t24ExeqQueue.
http://localhost:8080/TAFJEE/Execute
i.e
Remark:
The following properties need to be set correctly to run TAFJ within an application server
context.
temn.tafj.runtime.phantom.as.process = false
TAFJEE application offers many other functionalities like monitoring, changing log level, como
viewer please refer to TAFJ AS documentation for detailed information.
Before running it you have to define some parameters such as node, cell and server name to set
the scope of the configuration in the %TAFJ_HOME%\appserver\was\jython\ tafj.py file. You
must also define the browserWebHome as root folder to locate the Browserweb.war to be
deployed i.e. :
browserWebHome="C:/product/appserver/websphere/TAFJ/appserver"
Launch the following command in the command line (refer to Environment configuration for
additional command parameters).
You have to stop and restart your server to start the application. You can then browse the
administrative console to check it has been correctly deployed and started.
Console mode
Select local file deployment option and the browser.war file click on next
Select Detailed - Show all installation options and parameters.
Click Next.
Step 6:
Step 8:
Note: In the Enterprise Applications page, select BrowserWeb application and click on start.