1.After you specify all the configuration information, for each of the T24 environments ensure that a record with ID T24BROWSER exists in the OFS.SOURCE application.
Otherwise create it with Source Type set to SESSION and Syntax type set to XML.
BR2.Browser Installation-R10.01 35
Open new telnet sessions and start the jbase_agents at the respective port numbers as configured in t24-ds.xml
BR2.Browser Installation-R10.01 36
Start the JBoss application server by executing the run.bat file found under the bin directory of JBoss.
BR2.Browser Installation-R10.01 37
1.Can we login to both the environments simultaneously? The answer is - yes
BR2.Browser Installation-R10.01 38
1. The JMS API is an integral part of the Java platform, Enterprise Edition.
2. The Java Message Service API is a messaging standard that allows application components to send and receive messages. It enables distributed communication that is loosely coupled, reliable, and asynchronous.
3. Java Message Service is the new standard for inter-client communication.
Enterprise messaging provides a reliable, flexible service for the asynchronous exchange of messages throughout an enterprise.JMS provides a flexible and powerful API that encourages a fine-grained, modular distribution of functionality among application components.
BR2.Browser Installation-R10.01 39
The JMS architecture is introduced to provide enhanced resilience and load balancing.
Both the architectures are fundamentally the same, they both lookup the TAFC JCA and they both call OFS.BULK.MANAGER as the entry point to T24.Let us now have a look at the role of each component in the JMS architecture,
OFSMessageMDB - In the JMS architecture, the in coming requests are dropped onto a queue. These in-coming requests should be processed by T24. Now who is going to forward the requests to T24?
OFSMessageMDB is the component that picks up the requests from the queue. The message driven bean acts like a listener.
jremote – The OFSMessageMDB hands over the request to the TAFC resource adapter. The OFSMessageMDB looks up the TAFC resource adapter (currently called the JRemote JCA) and performs a remote subroutine call to OFS.BULK.MANAGER.
When OFS.BULK.MANAGER has performed the T24 process the MDB then places the response onto the response queue.
BR2.Browser Installation-R10.01 40
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 41
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 42
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
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 44
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 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 45
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 46
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 47
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 48
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 49
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 50
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 51
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 52
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 53
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 54
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 55
Before you log into browser, the jbase_agent should be started on port 9797.
BR2.Browser Installation-R10.01 56
Now start the Jboss app server also.
BR2.Browser Installation-R10.01 57
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 58
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 :
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 60
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 61
You can use the same ofsmessage-ejb.jar that was deployed earlier.
BR2.Browser Installation-R10.01 62
The jremote component forwards your requests to the T24 application server using the jbase_agent.
BR2.Browser Installation-R10.01 63
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 64
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 65
Ensure that the T24 Queue Connection Factory is configured to jms/jmsConnectionFactory.
BR2.Browser Installation-R10.01 66
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 67
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 68
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 69
1. Log into the telnet sessions and start the jbase agents for each T24 environment.
BR2.Browser Installation-R10.01 70
Start the Jboss App Server also.
BR2.Browser Installation-R10.01 71
You can now log into both the T24 areas simultaneously!
BR2.Browser Installation-R10.01 72
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