T24 Browser

Configuring Multiple T24 Environments Using JBoss

6.XX EAP in TAFJ using Browser

Temenos Page 1 of 13
T24R4.2 Release Notes

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,

Ref : 484435925.doc July 2002

Page 1
T24 Browser

Introduction

The purpose of this document is to give an overview the procedure used to deploy multiple T24
Browsers for connecting multiple T24 environments using JBoss 6.XX EAP in TAFJ.

Deployment of Components in Jboss

Kindly make ensure that the following files are present under the path (..\jboss-eap-
6.XX\standalone\deployments\).

1. BrowserWeb.war (deployed as WAR file)

2. BrowserWebTWO.war (deployed as WAR file)
3. TAFJJEE_EAR

The components will get deployed once the JBoss is started.

Note: Kindly use latest Browser War from TCSP portal and latest TAFJEE pack from Distribution
team ([email protected]).

Configuration of the Files:

Step 1:
Do the following changes in standalone-full.xml file.( ..\jboss-eap-6\standalone\configuration)
Create two data sources for each environment.
First environment:
<datasources>
<datasource jta="true" jndi-name="java:/jdbc/t24DS" pool-name="T24DS" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:h2:tcp://10.92.12.24:7075/Data</connection-url>
<driver>h2</driver>
<pool>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>

Temenos Page 2 of 13
T24 Browser
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>t24</user-name>
<password>t24</password>
</security>
<validation>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
</validation>
</datasource>
<datasource jta="false" jndi-name="java:/jdbc/t24LockingDS" pool-name="T24LOCKINGDS" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:h2:tcp://10.92.12.24:7075/Data</connection-url>
<driver>h2</driver>
<pool>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>t24</user-name>
<password>t24</password>
</security>
<validation>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
</validation>
</datasource>
<datasource jta="true" jndi-name="java:/jdbc/t24RODS" pool-name="T24RODS" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:h2:tcp://10.92.12.24:7075/Data</connection-url>
<driver>h2</driver>
<pool>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>t24</user-name>
<password>t24</password>
</security>
<validation>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
</validation>
</datasource>

Second environment:
<datasource jta="true" jndi-name="java:/jdbc/t24DSTWO" pool-name="T24DSTWO" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:h2:tcp://10.92.12.66:7075/Data</connection-url>
<driver>h2</driver>
<pool>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>t24</user-name>
<password>t24</password>
</security>
<validation>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
</validation>
</datasource>
<datasource jta="false" jndi-name="java:/jdbc/t24LockingDSTWO" pool-name="T24LOCKINGDSTWO" enabled="true" use-java-context="true" use-
ccm="true">
<connection-url>jdbc:h2:tcp://10.92.12.66:7075/Data</connection-url>
<driver>h2</driver>
<pool>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>t24</user-name>
<password>t24</password>
</security>
<validation>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
</validation>
</datasource>
<datasource jta="true" jndi-name="java:/jdbc/t24RODSTWO" pool-name="T24RODSTWO" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:h2:tcp://10.92.12.66:7075/Data</connection-url>
<driver>h2</driver>
<pool>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>

Temenos Page 3 of 13
T24 Browser
<user-name>t24</user-name>
<password>t24</password>
</security>
<validation>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
</validation>
</datasource>

Note: You can connect to different databases. The database ip and port number should be
changed correspondingly in the <connection-url>.

Step 2:

Create two set of queues in standalone-full.xml file.

First Environment:
<jms-destinations>
<jms-queue name="t24BROWSERQueue">
<entry name="queue/t24BROWSERQueue"/>
<entry name="java:jboss/exported/jms/queue/t24BROWSERQueue"/>
</jms-queue>
<jms-queue name="t24BROWSERReplyQueue">
<entry name="queue/t24BROWSERReplyQueue"/>
<entry name="java:jboss/exported/jms/queue/t24BROWSERReplyQueue"/>
</jms-queue>

Second Environment.
<jms-queue name="t24BROWSERQueueTWO">
<entry name="queue/t24BROWSERQueueTWO"/>
<entry name="java:jboss/exported/jms/queue/t24BROWSERQueueTWO"/>
</jms-queue>
<jms-queue name="t24BROWSERReplyQueueTWO">
<entry name="queue/t24BROWSERReplyQueueTWO"/>
<entry name="java:jboss/exported/jms/queue/t24BROWSERReplyQueueTWO"/>
</jms-queue>

Step 3:

In the ejb-jar.xml present inside

(..\jbosseap\standalone\deployments\TAFJJEE_EAR.ear\TAFJJEE_MDB.jar\MET
A-INF\) do the following changes.

First Environment:
<display-name>Transacted Listener MDB for BROWSER</display-name>
<ejb-name>BROWSERTransactedMDB</ejb-name>
<mapped-name>jms/t24BROWSERQueue</mapped-name>
<ejb-class>com.temenos.tafj.mdb.TransactedMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>

<env-entry>
<description>Define if use local or remote EJB</description>
<env-entry-name>com.temenos.tafj.mdb.TransactedMDB/useLocal</env-entry-name>
<env-entry-type>java.lang.Boolean</env-entry-type>
<env-entry-value>false</env-entry-value>
</env-entry>
<env-entry>
<description>Define related EJB JNDI name local - name space may vary depending on appserver
version</description>
<env-entry-name>com.temenos.tafj.mdb.TransactedMDB/jndiNameLocal</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>java:comp/env/ejb/OFSProcessingBeanLocal</env-entry-value>
</env-entry>
<env-entry>
<description>Define related EJB JNDI name remote - name space may vary depending on appserver
version</description>
<env-entry-name>com.temenos.tafj.mdb.TransactedMDB/jndiNameRemote</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>java:comp/env/ejb/OFSProcessingBeanRemote</env-entry-value>
</env-entry>

Temenos Page 4 of 13
T24 Browser
<ejb-ref id="BROWSERTransactedMDB_OFSProcessingBeanRemote">
<ejb-ref-name>ejb/OFSProcessingBeanRemote</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home></home>
<remote>com.temenos.tafj.sb.OFSProcessingBeanRemote</remote>
<ejb-link>BROWSERProcessingBean</ejb-link>
</ejb-ref>
<ejb-local-ref id="BROWSERTransactedMDB_OFSProcessingBeanLocal">
<ejb-ref-name>ejb/OFSProcessingBeanLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home></local-home>
<local>com.temenos.tafj.sb.OFSProcessingBeanLocal</local>
<ejb-link>BROWSERProcessingBean</ejb-link>
</ejb-local-ref>
<resource-ref>
<description>Used to get connections to JMS for OFS queues
</description>
<res-ref-name>jms/TAFJQueueConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<message-destination-ref>
<description>BROWSER queue</description>
<message-destination-ref-name>jms/ReplyQueue</message-destination-ref-name>
<message-destination-type>javax.jms.Queue</message-destination-type>
<message-destination-usage>Produces</message-destination-usage>
<message-destination-link>jms/BROWSERReplyQueue</message-destination-link>
</message-destination-ref>
</message-driven>

Second Environment:
<message-driven>
<display-name>Transacted Listener MDB for BROWSER TWO</display-name>
<ejb-name>BROWSERTransactedMDBTWO</ejb-name>
<mapped-name>jms/t24BROWSERQueueTWO</mapped-name>
<ejb-class>com.temenos.tafj.mdb.TransactedMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>

<env-entry>
<description>Define if use local or remote EJB</description>
<env-entry-name>com.temenos.tafj.mdb.TransactedMDB/useLocal</env-entry-name>
<env-entry-type>java.lang.Boolean</env-entry-type>
<env-entry-value>false</env-entry-value>
</env-entry>
<env-entry>
<description>Define related EJB JNDI name local - name space may vary depending on appserver
version</description>
<env-entry-name>com.temenos.tafj.mdb.TransactedMDB/jndiNameLocal</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>java:comp/env/ejb/OFSProcessingBeanLocal</env-entry-value>
</env-entry>
<env-entry>
<description>Define related EJB JNDI name remote - name space may vary depending on appserver
version</description>
<env-entry-name>com.temenos.tafj.mdb.TransactedMDB/jndiNameRemote</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>java:comp/env/ejb/OFSProcessingBeanRemote</env-entry-value>
</env-entry>
<ejb-ref id="BROWSERTransactedMDBTWO_OFSProcessingBeanRemote">
<ejb-ref-name>ejb/OFSProcessingBeanRemote</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home></home>
<remote>com.temenos.tafj.sb.OFSProcessingBeanRemote</remote>
<ejb-link>BROWSERProcessingBeanTWO</ejb-link>
</ejb-ref>
<ejb-local-ref id="BROWSERTransactedMDBTWO_OFSProcessingBeanLocal">
<ejb-ref-name>ejb/OFSProcessingBeanLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home></local-home>
<local>com.temenos.tafj.sb.OFSProcessingBeanLocal</local>
<ejb-link>BROWSERProcessingBeanTWO</ejb-link>
</ejb-local-ref>
<resource-ref>
<description>Used to get connections to JMS for OFS queues
</description>
<res-ref-name>jms/TAFJQueueConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<message-destination-ref>
<description>BROWSER queue</description>
<message-destination-ref-name>jms/ReplyQueue</message-destination-ref-name>
<message-destination-type>javax.jms.Queue</message-destination-type>
<message-destination-usage>Produces</message-destination-usage>
<message-destination-link>jms/BROWSERReplyQueueTWO</message-destination-link>
</message-destination-ref>
</message-driven>

Step 4:

Temenos Page 5 of 13
T24 Browser
In jboss-ejb3.xml file
(..\jbosseap\standalone\deployments\TAFJJEE_EAR.ear\TAFJJEE_MDB.jar\MET
A-INF\)

First Environment:
<message-driven>
<ejb-name>BROWSERTransactedMDB</ejb-name>
<activation-config>
<activation-config-property>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>java:/queue/t24BROWSERQueue</activation-config-property-value>
</activation-config-property>
</activation-config>
<ejb-ref>
<ejb-ref-name>ejb/OFSProcessingBeanRemote</ejb-ref-name>
<jndi-name>java:global/TAFJJEE_EAR/TAFJJEE_EJB/BROWSERProcessingBean!com.temenos.tafj.sb.OFSProcessingBeanRemote</jndi-name>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/OFSProcessingBeanLocal</ejb-ref-name>
<jndi-name>java:app/TAFJJEE_EJB/BROWSERProcessingBean!com.temenos.tafj.sb.OFSProcessingBeanLocal</jndi-name>
</ejb-ref>
<resource-ref>
<res-ref-name>jms/TAFJQueueConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<jndi-name>java:/ConnectionFactory</jndi-name>
</resource-ref>
<message-destination-ref>
<message-destination-ref-name>jms/ReplyQueue</message-destination-ref-name>
<jndi-name>java:/queue/t24BROWSERReplyQueue</jndi-name>
</message-destination-ref>

</message-driven>

Second Environment:
<message-driven>
<ejb-name>BROWSERTransactedMDBTWO</ejb-name>
<activation-config>
<activation-config-property>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>java:/queue/t24BROWSERQueueTWO</activation-config property-value>
</activation-config-property>
</activation-config>
<ejb-ref>
<ejb-ref-name>ejb/OFSProcessingBeanRemote</ejb-ref-name>
<jndi-name>java:global/TAFJJEE_EAR/TAFJJEE_EJB/BROWSERProcessingBeanTWO!com.temenos.tafj.sb.OFSProcessingBeanRemote</jndi-name>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/OFSProcessingBeanLocal</ejb-ref-name>
<jndi-name>java:app/TAFJJEE_EJB/BROWSERProcessingBeanTWO!com.temenos.tafj.sb.OFSProcessingBeanLocal</jndi-name>
</ejb-ref>
<resource-ref>
<res-ref-name>jms/TAFJQueueConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<jndi-name>java:/ConnectionFactory</jndi-name>
</resource-ref>
<message-destination-ref>
<message-destination-ref-name>jms/ReplyQueue</message-destination-ref-name>
<jndi-name>java:/queue/t24BROWSERReplyQueueTWO</jndi-name>
</message-destination-ref>

Step 5:

In ejb-jar.xml inside
(..\jboss-eap
6.2\standalone\deployments\TAFJJEE_EAR.ear\TAFJJEE_EJB.jar\META-INF\)

First Environment:

<session>
<description>TAFJ BROWSER Bean</description>
<display-name>TAFJ BROWSER Bean</display-name>
<ejb-name>BROWSERProcessingBean</ejb-name>

<business-local>com.temenos.tafj.sb.OFSProcessingBeanLocal</business-local>
<business-remote>com.temenos.tafj.sb.OFSProcessingBeanRemote</business-remote>

<ejb-class>com.temenos.tafj.sb.OFSProcessingBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>

<!-- For tafj session -->

Temenos Page 6 of 13
T24 Browser
<env-entry>
<description>BrowserWeb OFS Source</description>
<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/ofsSource</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>BROWSERTC</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/ofsTimeout</env-entry-name>
<env-entry-type>java.lang.Integer</env-entry-type>
<env-entry-value>60</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/jTA</env-entry-name>
<env-entry-type>java.lang.Boolean</env-entry-type>
<env-entry-value>false</env-entry-value>
</env-entry>
<!-- TEC feature -->
<resource-ref>
<description>Used to get connections to JMS for OFS queues</description>
<res-ref-name>jms/TopicConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<description>topic queue</description>
<res-ref-name>jms/tecEventsTopic</res-ref-name>
<res-type>javax.jms.Topic</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<!-- for T24 purpose -->
<resource-ref>
<description>Used to get connections from T24 jdbc pool</description>
<res-ref-name>jdbc/t24DataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<description>Used to get connections from jdbc locking pool</description>
<res-ref-name>jdbc/t24LockingDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<description>Used to get connections from T24 jdbc RO pool</description>
<res-ref-name>jdbc/t24RODataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</session>

Second Environment:
<session>
<description>TAFJ BROWSER Bean TWO</description>
<display-name>TAFJ BROWSER Bean TWO</display-name>
<ejb-name>BROWSERProcessingBeanTWO</ejb-name>

<business-local>com.temenos.tafj.sb.OFSProcessingBeanLocal</business-local>
<business-remote>com.temenos.tafj.sb.OFSProcessingBeanRemote</business-remote>

<ejb-class>com.temenos.tafj.sb.OFSProcessingBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>

<!-- For tafj session -->

<env-entry>
<description>BrowserWeb OFS Source</description>
<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/ofsSource</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>BROWSERTC</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/ofsTimeout</env-entry-name>
<env-entry-type>java.lang.Integer</env-entry-type>
<env-entry-value>60</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>com.temenos.tafj.sb.OFSProcessingBean/jTA</env-entry-name>
<env-entry-type>java.lang.Boolean</env-entry-type>
<env-entry-value>false</env-entry-value>
</env-entry>
<!-- TEC feature -->
<resource-ref>
<description>Used to get connections to JMS for OFS queues</description>
<res-ref-name>jms/TopicConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<description>topic queue</description>
<res-ref-name>jms/tecEventsTopic</res-ref-name>
<res-type>javax.jms.Topic</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<!-- for T24 purpose -->
<resource-ref>
<description>Used to get connections from T24 jdbc pool</description>
<res-ref-name>jdbc/t24DataSource</res-ref-name>

Temenos Page 7 of 13
T24 Browser
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<description>Used to get connections from jdbc locking pool</description>
<res-ref-name>jdbc/t24LockingDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<description>Used to get connections from T24 jdbc RO pool</description>
<res-ref-name>jdbc/t24RODataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</session>

Step 6:

In jboss-ejb3.xml inside
(..\jboss-eap
6.2\standalone\deployments\TAFJJEE_EAR.ear\TAFJJEE_EJB.jar\META-INF\)

First environment:
<session>
<ejb-name>BROWSERProcessingBean</ejb-name>
<resource-ref>
<res-ref-name>jdbc/t24DataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/jdbc/t24DS</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jdbc/t24RODataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/jdbc/t24RODS</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jdbc/t24LockingDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/jdbc/t24LockingDS</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jms/TopicConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<jndi-name>java:/ConnectionFactory</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jms/tecEventsTopic</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<jndi-name>java:/topic/tecEventsTopic</jndi-name>
</resource-ref>
</session>

Second Environment:
<session>
<ejb-name>BROWSERProcessingBeanTWO</ejb-name>
<resource-ref>
<res-ref-name>jdbc/t24DataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/jdbc/t24DSTWO</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jdbc/t24RODataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/jdbc/t24RODSTWO</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jdbc/t24LockingDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:/jdbc/t24LockingDSTWO</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jms/TopicConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<jndi-name>java:/ConnectionFactory</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jms/tecEventsTopic</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<jndi-name>java:/topic/tecEventsTopic</jndi-name>
</resource-ref>
</session>

Temenos Page 8 of 13
T24 Browser

Step 7:

Inside deployements folder two war files should be deployed BrowserWeb.war

and BrowserWebTWO.war

In browserParamers.xml file of both the war files change Parameter value to JMS
mode.

<parameter>
<parameterName>Server Connection Method</parameterName>
<parameterValue>JMS</parameterValue>
<!-- Options: INSTANCE / AGENT / JMS / AGENT_JREMOTE -->
</parameter>

Step 8:

Inside web.xml file comment the Resource Ref of Connection factory(highlighted

in blue).
(..\jboss-eap-6\standalone\deployments\BrowserWeb.war(or)
BrowserWebTWO.war\WEB-INF\)

<resource-ref id="ResourceRef_t24ConnectionFactory">
<description>T24</description>
<res-ref-name>jca/t24ConnectionFactory</res-ref-name>
<res-type>com.temenos.tocf.t24ra.T24ConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_jmsConnectionFactory">
<description>Used to get connections to JMS for OFS queues</description>
<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_t24OFSQueue">
<description>OFS queue</description>
<res-ref-name>queue/t24OFSQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_t24OFSReplyQueue">
<description>OFS reply queue</description>
<res-ref-name>queue/t24OFSReplyQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<res-auth>Container</res-auth>
</resource-ref>

Step 9:

In jboss-web.xml file
(\jboss-eap-6.2\standalone\deployments\BrowserWeb.war\WEB-INF\) and
comment the resource-ref related to T24 Connection Factory
<resource-ref>
<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<jndi-name>java:/ConnectionFactory</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>queue/t24OFSQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<jndi-name>java:/queue/t24BROWSERQueue</jndi-name>
</resource-ref>
<resource-ref>

Temenos Page 9 of 13
T24 Browser
<res-ref-name>queue/t24OFSReplyQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<jndi-name>java:/queue/t24BROWSERReplyQueue</jndi-name>
</resource-ref>
</jboss-web>

(..\jboss-eap-6.2\standalone\deployments\BrowserWebTWO.war\WEB-INF\)
<resource-ref>
<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<jndi-name>java:/ConnectionFactory</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>queue/t24OFSQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<jndi-name>java:/queue/t24BROWSERQueueTWO</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>queue/t24OFSReplyQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<jndi-name>java:/queue/t24BROWSERReplyQueueTWO</jndi-name>
</resource-ref>
</jboss-web>

Step 10:

Inside jboss-deployment-structure.xml file comment the highlighted lines.

(..\jboss-eap-6\standalone\deployments\BrowserWeb.war(or)
BrowserWebTWO.war\WEB-INF\)
<!-- <dependencies>
<module name="deployment.tocfT24ra-ra.rar" />
</dependencies>-->

<!--Enable the below configuration only when SSO with SAML and ADFS is enabled-->
<!--<module name="org.apache.xerces" />

<module name="org.picketlink" /> -->

<!-- Exclusions allow you to prevent the server from automatically adding some dependencies
<exclusions>
<module name="org.apache.log4j" />
</exclusions> -->

Step 11:

After doing the above changes start the JBoss and database, then login to the
browser using the URL’s. Each browser will connect to the T24 environments
configured above.

http://10.92.12.24:8080/BrowserWeb/

Temenos Page 10 of 13
T24 Browser

http://10.92.12.24:8080/BrowserWebTWO/

Temenos Page 11 of 13