How to set up multiple Unix T24 environments on a single server

Overview
It is usually necessary to create multiple T24 environments as a part of any
implementation for the purposes of environmental and change management, for
example, the necessity to set up Development, Test, UAT, and Live environments on
a user site.

This document aims to cover the steps necessary to implement this type of multiple
environment model.

As with most implementation challenges, it is not difficult to achieve this, but it is

fiddly and open to error so beware!!

Caveats & Assumptions

1. You have already installed, and have working, one full environment. That is to
say, jBASE, T24, TCS, Tomcat (or Websphere), Browser, and the back end
database is demonstrably accessible.
2. This document is specifically modelled on the Swedbank (Helsinki) project
which used Oracle as the backend database with two physical servers hosting
two T24 environments each. Having said this, the ‘rules’ should be the same
for any implementation whatever the backend database (SQL, Oracle, DB2,
and whatever database connectivity may be made available in the future).
This does not apply when native jBASE is used as the backend as the driver
software is redundant and not referenced.
3. References to ORACLE should be read in connection with point 2 above.
4. We only require ONE jBASE operating system environment on a server.
5. This document specifically refers to Unix Server files (such as .profile)
6. It is further assumed that you have created a new top level folder and copied
the working T24 hierarchy into it so that you have an exact copy of a known
working T24 environment. NOTE – You cannot use BLANKS in unix directory
names (unix will create two separate directories)
7. You will get help from the customer for Oracle and Websphere.

Example structure –
/sb/sys/

Below that you can have multiple Model Bank directories eg –

/sb/sys/MB (this is the original t24 instance)

/sb/sys/MB2 (this is the copy t24)

You also need a separate TCS for each instance of Model Bank eg –
Technical How To – Install Multiple Unix T24 environments on a Single Server – Draft 1.3

Author – Ian Rodgers

Date – 27 October 2008
/sb/sys/TCS (this is the original TCS instance)
/sb/sys/TCS2 (this is the copy TCS)

Only a single jbase is required eg –

/sb/sys/jbase509

Only a single Websphere or Tomcat is required but within that separate Browser
instances are needed eg –

/sb/sys/WebSphere (single instance)

/sb/sys/WebSphere/AppServer/profiles/AppSrv01/installedApps/bpfitst/t24test.ear

/sb/sys/WebSphere/AppServer/profiles/AppSrv01/installedApps/bpfitst/
BrowserWeb_MB2_war.ear

Within each *.ear directory there is a *.war directory. Within that (and below it) are
the parameterisation files –

helpParameters.xml

….WEB-INF/conf/channels.xml

Also the help directory

8. For the purposes of this document we will be using MB as the ‘already

working’ instance of T24, and MB2 as the new instance that we are about to
configure.

T24
The change necessary in T24 is straightforward, navigate to the bnk.run directory
of the newly cloned instance (see diagram of Instance 2 in Caveats and
Assumptions section) and open .profile with vi. Replace all occurrences of any
absolute paths that go to MB (in this case) with MB2, file and save. NB –
Normally all paths within t24 are RELATIVE paths so there should be nothing that
needs to be changed. You will see absolute paths for vi, oracle and jbase. These
are OK because we only need one instance of each (nb there is one instance of
oracle but there needs to be a separate oracle database for each instance of
t24).
Make sure ORACLE_SID and TWO_TASK are set to the correct name (check this
with the oracle dba) eg –

export ORACLE_SID=TDET6
export TWO_TASK=tdet5.world

Technical How To – Install Multiple Unix T24 environments on a Single Server – Draft 1.3

Author – Ian Rodgers

Date – 27 October 2008
SQL DB, jedi, and jBASE
1. Get the ORACLE DBA to make a new copy of the ORACLE database eg –

t24_oradb to t24_oradb

2. In order to get our T24 instances to talk to discreet database instances we

have to have a jedi_config file in the bnk.run directory of each t24 directory.
In our example this has been copied to

/sb/sys/MB3/bnk/bnk.run/jedi_config

3. The database driver configuration utility (config-XML<database name>,

config-XMLORACLE in this case) checks for jedi_config based on the
JEDIFILEPATH in the .profile in the bnk.run directory in the T24 environment
which should be set to %HOME% (which is the bnk.run directory). If the
driver cannot find the jedi_config file in the home path it will go look in the
jBASE folder
4. The binaries and library items for the database driver (SQL in this case) can
then be put in $JBCRELEASEDIR/bin and $JBCRELEASEDIR/lib respectively
ensuring that the environment variable $JBCRELEASEDIR points to the path
of the installed jBASE instance (eg c:\jbase\5.0).
5. Before invoking the database configuration utility (config-XML<database
name>) log off and on to ensure clean variablesnavigate to the ‘bnk.run’
folder and run the .profile –

. .profile

this will ensure that all environmental variables are populated. At the START
GLOBUS Y/N prompt enter N <cr> which will drop you to the jSHELL prompt.

6. Execute config-XML<database name> (config-XMLORACLE in this case) and

set up the database connector as per the server details, database name, user
name, and password provided by the on-site Database Administrator. In order
for this to work, the $JBCRELEASEDIR/bin and $JBCRELEASEDIR/lib
environmental variables must be in the PATH variable in remote.cmd as
discussed in point 3 above. Eg –

config-XMLORACLE

Take option 1)

1.2) tdet6
1.3) t24_oradb
1.4) t24_oradb

Take option 9) to go back to main menu

Take option 2)

2.2) t24_user
2.3) t24_pass
Technical How To – Install Multiple Unix T24 environments on a Single Server – Draft 1.3

Author – Ian Rodgers

Date – 27 October 2008
 2.4) t24_oraschema (will default in)

Take option 9) to go back to main menu

Take option 3) – this should show the date and time if everything is working

Take option 5) – save and exit

7. When you have finished the configuration enter exit at the jSHELL prompt
and the command window will close.

TCS
It is possible to use one instance of TCS to control multiple instances of T24, but
for the sake of KISS (Keep It Simple, Stupid and my own experience levels) this
document will focus on the use of one instance of TCS for each instance of T24,
this will keep the entire software set self-contained save for Apache Tomcat /
Websphere, which is a system-wide application anyway. TCS will be installed on
the same level as the main installation folder.

Configuring one instance of TCS per instance of T24

The necessary changes to TCS are as follows:

1. Navigate to the home directory of the new environment and run the .profile.
(this will set the ENVIRONMENT VARIABLES – NB – DON’T use $HOME to go
to the home directory – it won’t have the right value).
2. Invoke env and make sure that the paths look OK. NB – it may be best to exit
from unix and start a new session, go straight to the home directory and then
run .profile to make sure that none of the variables have false values (eg -
$HOME is derived from $PWD initially).
3. Navigate to the xxx/TCS2/TC_Server/tcserver/conf/TCServer folder. Go to the
ksh and do…

mv environment.vars environment_save.vars

to make a backup of the existing environment.vars then do…

env > environment.vars

to make sure the environment vars for Browser match the ones for classic
(NB – you must do this from a unix shell, it won’t work from jsh because the
“>” means “greater than” in the jshell). In the same directory, there is also a
file tcserver.xml

Edit this file to change all ports to a unique number. Eg –

Technical How To – Install Multiple Unix T24 environments on a Single Server – Draft 1.3

Author – Ian Rodgers

Date – 27 October 2008
 <MONITOR_PORT> 9506 </MONITOR_PORT> change to
<MONITOR_PORT> 9536 </MONITOR_PORT>

<LISTENER Name="Browser.1" type="tcp" active="true">

<ADAPTERID>T24</ADAPTERID>
<PORT>10201</PORT> change to
<PORT>10301</PORT>
</LISTENER>

<LISTENER Name="Browser.2" type="tcp" active="true">

<ADAPTERID>T24</ADAPTERID>
<PORT>10202</PORT> change to
<PORT>10302</PORT>
</LISTENER>

We MUST change all ports that are in use to unique numbers, as you will get
physical hardware port clashes if you don’t.

Last, but by no means least, replace any occurrences of MB (in this case) with
MB2, save and file.

Use vi to edit TCServer.sh (xxx/TCS2/TC_Server/tcserver/bin/ TCServer.sh) to

make sure it will run in foreground (ie NOT using nohup).
Start TCS from the ksh (ie . ./TCServer.sh) and make sure it runs properly.

If any of the listeners come up [FAILED], you have entered an incorrect port
number somewhere, you will need to go back and check tcserver.xml as detailed
previously in this document. This will be due to port clashes, you should also
start the TCServer in the other environment and check for the same thing.

If everything works properly (both TCServers are started and running with no
failed listeners), stop the new TCSERVER again and use vi to change TCServer.sh
so that it runs in the background (you just need to comment out the line that
runs tcserver in foreground and uncomment the line that runs it in background).

Apache Tomcat / Websphere Deployment

1. Copy BrowserWeb.war and paste it to a new name eg –

BrowserWeb_MB2.war

Then change the browser settings in websphere to match these. Eg –

Technical How To – Install Multiple Unix T24 environments on a Single Server – Draft 1.3

Author – Ian Rodgers

Date – 27 October 2008
/sb/sys/WebSphere/AppServer/profiles/AppSrv01/installedApps/
bpfitst1Node01Cell/BrowserWeb_MB2_war.ear/BrowserWeb_MB2.war/
WEB-INF/conf

In there is a file called channels.xml

<PORT>10201</PORT> change to
<PORT>10301</PORT>

<PORT>10202</PORT> change to
<PORT>10302</PORT>

The PORT numbers that you use MUST coincide with the PORT numbers given in the
tcserver.xml that we configured earlier, now file and exit.

OK, that’s pretty much all of the configuration done, so let’s see if it works!!

Firstly, stop and restart Websphere (or Apache Tomcat).

Access Via Browser

Open an Internet Explorer (or such like application) on a desktop which is NOT the
server and enter the following URL:

For TOMCAT -

http://10.5.1.200:8080/BrowserWeb_MB2/servlet/BrowserServlet <cr>

FOR WEBSPSHERE –

http://10.5.1.200:9080/BrowserWeb_MB2/servlet/BrowserServlet<cr>

Where – 10.5.1.200 is the real IP address of the server where we have installed
everything. NB – We used an underscore in the BrowserWeb_MB2.war name so
there is an underscore in the URL’s shown above (though you can’t see it).

All things being equal you should get a T24 Login Screen, login using
AUTHOR/123456 or any other login that you know works. If you get a Websphere (or
Tomcat) error then you have either not started Websphere or you have put a wrong
port number in somewhere. If you see the T24 Login Screen but get a ‘failed to
connect’ error message when you enter the login credentials, you haven’t started
TCS or TCS has failed.

Now fire up the other BrowserWeb instance and ensure that they work side by side

http://10.5.1.200:9080/BrowserWeb/servlet/BrowserServlet <cr>

Technical How To – Install Multiple Unix T24 environments on a Single Server – Draft 1.3

Author – Ian Rodgers

Date – 27 October 2008
And login as before

If all this works, then congratulations you have successfully configured multiple self-
contained instances of T24

The rest of this document is aimed at tidying up the environment and putting in
place shortcuts and access methods for Temenos Consultants that come after you
and to make the user/administrator’s life a little easier.

Access Via Classic

Firstly, install putty, it is freely downloadable from the web. The install consists of
copying one executable onto your desktop.

You can use a putty from your desktop – ask the customers unix administrator to
give you ip address details ad well as a user and password that is suitable. Ideally
you will want to just drop to a unix shell and invoke the jshell or t24 yourself.

You now have putty access which is necessary for starting up COB and for other Tech
Cons to get proper access to T24.

This is TOTALLY necessary as Browser is fine but the only way that you will see real
error messages is in Classic, a point worth noting.

Monitoring the environments.

You can monitor the environments by issuing the command

telnet <machine id> <monitor port number>

Eg –

telnet localhost 9536

This allows you to stop the server or reset it (etc).

TCMonitor Start Up shell script

Wherever there is a TCServer, there is an associated TC Monitor, so shellscripts for

these need to be changed if you want to use them. The Item Location will be

…\tcs\bin\TCmonitor.sh

TCMonitor Port Configuration

TC Monitor will, by default, monitor port 9500. In this case our first environment had
already been changed to 9506 (see above) we need to change the MB2 TC Monitor
to monitor port 9536 (see above) so, invoke the TCMonitor and then click File on the
TC Monitor Menu Bar and choose Connect to…. A dialog box will be displayed which
shows:
Technical How To – Install Multiple Unix T24 environments on a Single Server – Draft 1.3

Author – Ian Rodgers

Date – 27 October 2008
Localhost 9500

Change this to:

Localhost 9536

Close the monitor window and then start it up again. With both TC Monitors running
on the server desktop you should have two open windows, one title bar showing:

TCMonitor:localhost:9506 / Connected / all

And the other:

TCMonitor:localhost:9536 / Connected / all

Testing
Make sure that the environments have been set up properly, and that each
environment has been correctly attached to its separate database. For example go
into a Browser session for the original environment and create a user. Make sure
that this user is not visible in the second environment. Then set up a user in the
copy environment and make sure its not visible in the original environment.

Important

What would happen if you are using both environments from the jsh by changing
path and using EX to go into them each in turn? In this case you must invoke
the .profile for each environment before you go into t24. If you don’t remember to
invoke the .profile of the environment you want to use but simply change path and
use EX you will be accessing the environment of the last .profile that you invoked.
In fact you should exit the shell each time and log on again, so that all
environment variables are cleared out to begin with (some just get values appended
to them each time you run .profile).

Other Info

You may find that each environment shares the same lock tables. The way to fix this
is (the example below uses database names MB1, MB2, MB3 etc) –

1.)Log in as a root user and export the minimal variables as below.

$export JBCRELEASEDIR=<Path where your jbase is installed>

$export JBCGLOBALDIR=$JBCRELEASEDIR
$export PATH=$JBCRELEASEDIR/bin:$PATH
$export LD_LIBRARY_PATH=$JBCRELEASEDIR/lib:/usr/ccs/lib:/usr/lib
$export JBASE_DATABASE=MB1
$export JBCDATADIR=$JBCRELEASEDIR

$DB-START -n MB1
Technical How To – Install Multiple Unix T24 environments on a Single Server – Draft 1.3

Author – Ian Rodgers

Date – 27 October 2008
$jsh

Check that there will be an entry as 'MB1' in $JBCRELEASEDIR/databases

directory.

Similarly please do the same steps for MB2 as well.

Now in the .profile of MB1 unix account add the below variable as,

export JBASE_DATABASE=MB1

In MB2 unix account add the variable as,

export JBASE_DATABASE=MB2

Now Exit and relogin and check the locking problem from both environments.

Any queries, comments, or further help that anyone needs with this document, you
can get me on [email protected]

Technical How To – Install Multiple Unix T24 environments on a Single Server – Draft 1.3

Author – Ian Rodgers

Date – 27 October 2008