Ensure that the following components are installed on your machine before, you start the

installation process.

1.A browser – Temenos recommends the Internet Explorer

2. The latest version of Java. Ensure that you also set the environment variable
JAVA_HOME to the latest version of java installed.

BR2.Browser Installation-R10.01 1
 The following are the components that are required for browser installation using the JMS
architecture,

1. Install TAFC
2. The JBoss application server (4.2.3.GA) must be downloaded and installed on your
machine.
3. Next step is to deploy the BrowserWeb.war file
4. After browser configuration, deploy the OFSMessage message driven bean. The
OFSMessageMDB can be found inside the tocfee.ear.
5. Finally deploy the TAFC resource adapter

BR2.Browser Installation-R10.01 2
 What is an archive file?
An Enterprise ARchive, or EAR, is a file format used by Java EE for packaging one or more
modules into a single archive so that the deployment of the various modules onto an
application server happens simultaneously and coherently. It also contains XML files called
deployment descriptors which describe how to deploy the modules.

The following components can be found in tocfee.ear:

1. delivery-ejb.jar
2. ofsmessage-ejb.jar
3. tocfcommon.jar
4. tocflistener-ejb.jar
5. tocfplugin-ra.rar

BR2.Browser Installation-R10.01 3
 1. Copy tocfee.ear to the deploy directory of jboss. Temenos has provided the packaging
utilities to make your job simpler.

BR2.Browser Installation-R10.01 4
 1. When you execute the unpack.bat file, the artifacts of tocfee.ear will be extracted onto a
work directory as shown. Each of the artifacts will be extracted onto a folder with .tmp
extension.

2. The configuration files for ofsmessage-ejb.jar can be found under ofsmessage-

ejb.jar.tmp. You can make changes to the files under this folder.

BR2.Browser Installation-R10.01 5
 1. After you make the changes to the configuration file, you need to repack the contents of
tocfee.ear so that it is updated with the new configuration settings.

2. Execute the pack.bat file which will pack the artifacts again into a new ear file. The new
tocfee.ear file will be created under a temporary folder . Copy the tocfee.ear file to the
deploy directory of jboss.

BR2.Browser Installation-R10.01 6
Slide 6

a2 The packaging utilities and tocfee.ear file can be downloaded from knowledge base. Copy the bat files
and tocfee.ear to the c drive.

Execute unpack.bat and then make changes to your artifacts.

The new tocfee.ear file will be created under a temporary folder called deploy under the current
directory.
assispriya, 2010/04/15
 Follow the same procedure for TAFC and Jboss installation as shown in the browser
installation process of Agent architecture.

After you install Jboss, to deploy the BrowserWeb war file in Jboss app server, copy the war
file onto the deploy directory of Jboss.

BR2.Browser Installation-R10.01 7
 The server connection method is configured in browserParameters.xml file. For the JMS
architecture, the server connection method should be set to JMS in the file
browserParameters.xml.

BR2.Browser Installation-R10.01 8
 The t24 data source connection file is used to specify the resource adapter for which, you
want a pool of connections for and the jndi name of this pool. A connection pool is only
required for “outbound” resource adapters – e.g. the TAFC resource adapter (jremote-ra.rar)

After you specify the name of the connection object, you should also configure the ip
address of the host, port number and OFS source record id.

Now the jbase_agent will listen on port 9494 as per the configuration details.

BR2.Browser Installation-R10.01 9
 The request and response queues are configured in the t24-destinations-service.xml which,
can be found under the deploy directory of Jboss. The screen shot displayed here defines
two queues called “t24OFSQueue” and “t24OFSReplyQueue”.

The message driven bean acts as a listener and processes the request that is dropped into
the request queue. Once the requests are processed, it is placed in the response queue.

BR2.Browser Installation-R10.01 10
 In the next step you will deploy a Message Driven Bean in Jboss. The OFSMessageMDB
can be found inside the tocfee.ear.

BR2.Browser Installation-R10.01 11
 In order to deploy the tocfee.ear component you can make use of the utilities for packing
and unpacking the artifacts.
1. Copy the tocfee.ear, pack.bat and unpack.bat under any directory
2. Execute the unpack.bat file which will extract the contents of tocfee.ear onto a directory
called work. Each of the artifacts under tocfee.ear will be extracted onto a temporary
directory with .tmp extension. You may configure the files for ofsMessageMDB and the
ear file can be packed again with new configurations. To pack the ear file execute the
pack.bat file which will create the tocfee.ear file with the new configuration settings.
3. To deploy the tocfee.ear file copy it to the deploy directory of jboss

BR2.Browser Installation-R10.01 12
 After the requests are dropped in the request queue, you need a message driven bean to
pick up the request and process it. Therefore the message driven bean configuration is
specified in the ejb-jar.xml file of ofsmessage-ejb.jar. The OFSMessage MDB looks up the
TAFC resource adapter (currently called the JRemote JCA) and performs a remote
subroutine call to OFS.BULK.MANAGER with the OFS request from the OFS request
queue. When OFS.BULK.MANAGER has performed the T24 process the MDB then places
the OFS response onto the OFS response queue.

Note: The ejb-jar.xml file can be found under the ofsmessage-ejb.jar.tmp folder. Implement
the changes to ofsmessage-ejb.jar and repack the tocfee.ear file.

BR2.Browser Installation-R10.01 13
 The OFSMessageMDB should know from which queue it has to pick up the requests and it
should also know onto which queue it has drop the responses. These configurations are
specified in the file jboss.xml of ofsmessage-ejb.jar. Here the requests are dropped in
t24OFSQueue and the responses will be placed in t24OFSReplyQueue.

BR2.Browser Installation-R10.01 14
 After you deploy the OFSMessage MDB, deploy jremote. jremote component forwards your
requests to the T24 application server using the jbase_agent.

BR2.Browser Installation-R10.01 15
 Before you log into browser, the jbase_agent should be started on port 9797.

BR2.Browser Installation-R10.01 16
 Now start the Jboss app server also.

BR2.Browser Installation-R10.01 17
 1. Since the application server server is installed on the local PC, we specify localhost.
You may choose to give the IP address of the PC as well. 9080 is the port where Jboss
is running. The port number is configurable in server.xml. BrowserWeb – Is the servlet
that has been deployed. servlet/BrowserServlet – Enables us to invoke the
‘BrowserWeb’ servlet.

BR2.Browser Installation-R10.01 18
 You may need multiple T24 environments to work on. Here you will learn to configure
multiple T24 instances using the JMS architecture.

1. The components that are to be configured for multiple T24 environments are as follows:
1.1 BrowserWeb
1.2 OFSMessageMDB
1.3 TAFC Resource Adapter – jremote

2. Files that are to be configured are :

2.1t24-destination-services.xml
2.2 ejb-jar.xml in ofsmessage-ejb.jar
2.3 jboss.xml in ofsmessage-ejb.jar
2.4 t24-ds.xml

BR2.Browser Installation-R10.01 19
 You will now learn the steps to configure a new T24 environment using the JMS
architecture. Lets name the new area as TestArea.

BR2.Browser Installation-R10.01 20
 As the first step, let us deploy a new BrowserWeb to communicate to the other T24
environment. The new BrowserWeb is renamed as R10BrowserWeb.war. For ease of
deployment the contents of the war file are extracted onto a folder as shown. Also configure
the server connection method in the file browserParameters.xml.

BR2.Browser Installation-R10.01 21
 You can use the same ofsmessage-ejb.jar that was deployed earlier.

BR2.Browser Installation-R10.01 22
 The jremote component forwards your requests to the T24 application server using the
jbase_agent.

BR2.Browser Installation-R10.01 23
 As you need to communicate to the T24 area now, you need to configure the request and
response queues. These queues are configured in the t24-destinations-service.xml which,
can be found under the deploy directory of Jboss. The screen shot displayed here defines
two queues called “t24OFSQueueTestArea” and “t24OFSReplyQueueTestArea”. Henceforth
these queues will be used for the TestArea.

BR2.Browser Installation-R10.01 24
 You have configured the queues, but who is going to pick up the requests from the queue?
To process these requests you need to create a Message Driven Bean. The message driven
bean acts as a listener and processes the request that is dropped into the request queue.
Once the requests are processed, it is placed in the response queue.

Lets us now see the steps to create a message driven bean. In order to create a MDB, edit
ejb-jar.xml in ofsmessage-ejb.jar and create a new message driven instance.
TestAreaOFSMessageMDB is the new MDB created for the new T24 environment. Extract
the artifacts of tocfee.ear. To modify the file ejb-jar.xml, use the ofsMessage-ejb.jar.tmp
folder under the work directory. After you make changes to this file, rebuild the tocfee.ear file
using the pack.bat file.

Note: To create a new MDB copy the set of tags from <meesage-driven> to </message-
driven> and make the modifications to the latest copy and rebuild your jar.

BR2.Browser Installation-R10.01 25
 Ensure that the T24 Queue Connection Factory is configured to jms/jmsConnectionFactory.

BR2.Browser Installation-R10.01 26
 The TestAreaOFSMessageMDB should know from which queue it has to pick up the
requests and it should also know onto which queue it has drop the responses.

These configurations are specified in the file jboss.xml of ofsmessage-ejb.jar.

1. The requests are dropped in t24OFSQueueTestArea

2. The responses will be placed in t24OFSReplyQueueTestARea
3. Also specify the JNDI connection object here.

BR2.Browser Installation-R10.01 27
 The jndi name of the connection object should be specified in t24-ds.xml. Also specify the ip
address of the host, the port number and OFS source record id.

Important Note: Speciy a different port number to communicate to a new T24 environment.

BR2.Browser Installation-R10.01 28
 The browser should forward the request to T24, now to do this you need a communication
link between the browser and the T24 application server. So where do you configure this
link?

The jndi connection object should be configured in the BrowserWeb.war. This is specified in
the jboss-web.xml file of BrowserWeb.

Now onto which queue should the requests be dropped by the browser and from which
queue should the responses be picked up?
The request and response queue information should also be configured in jboss-web.xml.
These should the same queue names as specified in the t24-destinations-service.xml.

BR2.Browser Installation-R10.01 29
 1. Log into the telnet sessions and start the jbase agents for each T24 environment.

BR2.Browser Installation-R10.01 30
 Start the Jboss App Server also.

BR2.Browser Installation-R10.01 31
 You can now log into both the T24 areas simultaneously!

BR2.Browser Installation-R10.01 32
 1. There are various components that are required for Browser to work on T24

2. Errors may arise in the process of installation of any of these components

3. Errors may arise in any of the following components

3.1 java
3.2 JBoss
3.3 jremote

BR2.Browser Installation-R10.01 33
 1. Always ensure that java version of 1.5 or above is installed

2. The JAVA_HOME environment variable should point to the jdk 1.6

BR2.Browser Installation-R10.01 34
 Earlier you used to set time out interval in tcserver which is the time limit upto which the
tcserver session waits for the response from T24 server for each request sent from the
browser. Now where do you specify the TIME OUT parameter?

To set time out parameter, you need to configure your t24-ds.xml and set the property -
actionTimeout. This property will cause the jbase_agent process to exit if T24 does not
process the request within the configured number of seconds.

Note: The reason T24 could take longer than 30 seconds is due to a lock collision or a very
slow query.

BR2.Browser Installation-R10.01 35
 The error ‘ Could not connect to remote jBASE instance’ , has occurred when a user has
tried to loginto T24 . If you take a look at the displayed error message it tells you about the
host ip address and the port number using which the browser communicates with T24.
Therefore it implies that the jbase_agent has not been started on port number 7001.

BR2.Browser Installation-R10.01 36
 netstat (network statistics) is a command-line tool that displays network connections (both
incoming and outgoing). You can specify the command netstat –a –n –p followed by protocol
name, to know the status of all connections for the specified protocol.

The –a option displays all active TCP connections and the TCP and UDP ports on which the
computer is listening.
The –n option displays active TCP connections, however, addresses and port numbers are
expressed numerically and no attempt is made to determine names.
The -p Protocol : Shows connections for the protocol specified by option Protocol. In this
case, the Protocol can be tcp, udp, tcpv6, or udpv6. If this parameter is used with -s it
displays statistics by protocol.

BR2.Browser Installation-R10.01 37
 By now you must be able to

1. Explain the T24 multi-tier architecture

2. Explain TOCF
3. Identify the different Components required for Browser installation.
4. Create a T24 area with the Browser as its front end .
5. Install T24 Browser on Windows

BR2.Browser Installation-R10.01 38
 1. Who converts the http request into Browser xml?
a. Web Browser
b. jremote
c. T24 Browser
d. Jbase agent
2. Which is the entry point of T24 from third party systems?
a. Web Browser
b. T24 Browser
c. jremote
d. TOCF
3. Who sends the request to jbase agent?
a. Web Browser
b. Web Server
c. jremote
d. T24 Application server
4. Which of the following request format is directly understood by T24?
a. HTTP
b. HTTPS
c. Browser XML
d. XML
5.In which layer does the business logic reside?
a. Presentation layer
b. Web Server
c. Application Server layer
d. Database server layer
6.Which is the HOME directory of T24 user?
a. bnk.dict
b. Bnk.data
c. Bnk.run
d. Bnk.interface
7.What is configured in t24-ds.xml?
a. Jndi connection object, ip address of the host , port number and OFS SOURCE record id.
b. Listeners
c. Channels
d. Listeners,channels
8. In which port does JBoss run run in case of localhost?
a. 7001
b. 20001
c. 8080
d. 7002
9. ___________ enables us to invoke the servlet ‘Browser.Web’.
a. T24 Browser
b. TCS
c. TCC
d. Servlet/BrowserServlet

BR2.Browser Installation-R10.01 39
BR2.Browser Installation-R10.01 40