Platform Framework
R24 AMR | Min(s) read

Modifying the Standalone Context

This section shows you how to modify the standalone context using CLI command and predefined XML context.

To start JBoss,

  1. Copy and rename the existing configuration file. That is, rename standalone-full.xml to T24.xml.
  2. Start JBoss with the following command:

    %JBOSS_HOME%\ bin\standalone.bat --server-config=T24.xml

Modifying the Standalone Context with CLI Command

You can modify the standalone context with CLI command using the following procedure.

  1. Modify the %TAFJ_HOME%\appserver\jboss\jboss7eap\jboss-cli\tafj.properties file.
    ############################################################
					# Path details
					#
					TAFJ_HOME=[TAFJ root folder]
					############################################################
					# database details
					#
					#DB_URL doesn't apply for DB2 XA DRIVER
					DB_URL=[url]
					DB_DRIVER=[h2,ora12c,db2jdbc,sqljdbc]
					DB_DRIVER_XA=[h2,ora12cXA,db2jdbc,sqljdbc]
					DB_USER=[user]
					DB_PWD=[password]
					#DB2 XA DRIVER in replacement of DB_URL
					DB_HOST=[hostname]
					DB_NAME=[instance name]
					DB_PORT=[port]

    For example, if you are using an H2 database.

    ############################################################
					# Path details
					#
					TAFJ_HOME=D:\Temenos\Reference\Temenos\TAFJ
					############################################################
					# database details
					#
					DB_URL=jdbc:h2:tcp://localhost/T24
					DB_DRIVER=h2
					DB_USER=mbtafj
					DB_PWD=mbtafj
  2. In JBoss, modify the following section of the %JBOSS_HOME%\bin\jboss-cli.xml file.
    <!-- whether to resolve system properties specified as command argument or operation parameter values in the CLI VM before sending the operation requests to the controller -->
    <resolve-parameter-values>true</resolve-parameter-values>
  3. Execute the jboss-cli command.
    D:\Temenos\Reference\3rdParty\as\jBoss\jboss-eap-7\bin> jBoss-cli.bat --connect --file=%TAFJ_HOME%\appserver\jboss\jboss7eap\jboss-cli\T24Setup.cli --properties= %TAFJ_HOME%\appserver\jboss\jboss7eap\jboss-cli\tafj.properties

Modifying the Standalone Context with Predefined XML Context

This section does not cover the class loading mechanism in JBoss EAP 7. It is recommend that you refer to the following documentation to understand how the libraries are getting loaded and dependencies are managed:

https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7

TAFJ and Temenos Transact libraries are deployed as global modules to allow all applications to be deployed within the server deployment folder for easy access. To reference these global modules you need to modify your main configuration file, that is %JBOSS_HOME%\standalone\configuration\standalone-full.xml.

Add the following section in the Temenos Transact and TAFJ modules declaration:

<subsystem xmlns="urn:jboss:domain:ee:1.2">
					<spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>
					<jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>
					<annotation-property-replacement>false</annotation-property-replacement>
					<global-modules>
					<module name="com.temenos.tafj" slot="main"/>
					<module name="com.temenos.t24" slot="main"/>
					</global-modules>
					</subsystem>

Modules are defined under JBOSS_HOME/modules.

Edit the data source section of %JBOSS_HOME%\standalone\configuration\standalone-full.xml by referring the %TAFJ_HOME%\appserver\jboss\jboss7\standalone-full.xml file as an example.

You need to configure two data sources:

  • Transactional data source for Temenos Transact RDBMS.
  • TAFJ locking data source when using locking mode JDBC or ORCL (this data source is in auto commit mode and is not transactional).

The sample below shows the configured data source section for the Temenos Transact RDBMS.

   <datasource jta="true" jndi-name="java:/jdbc/t24DS" pool-name="T24DS" enabled="true" use-java-context="true" use-ccm="true">
                    <connection-url>jdbc:oracle:thin:@localhost:1521:TAFJDB</connection-url>
                    <driver>ora11g</driver>
                    <pool>
                        <prefill>false</prefill>
                        <min-pool-size>5</min-pool-size>
<max-pool-size>220</max-pool-size>
                        <flush-strategy>FailingConnectionOnly</flush-strategy>
                    </pool>
                    <security>
                        <user-name>tafj</user-name>
                        <password>secret</password>
                    </security>
                    <validation>
                        <validate-on-match>false</validate-on-match>
                        <background-validation>false</background-validation>
                        <use-fast-fail>false</use-fast-fail>
                    </validation>
                </datasource>

The sample below shows the configured data source section for the Temenos Transact locking data source.

<datasource jta="false" jndi-name="java:/jdbc/t24LockingDS" pool-name="T24LOCKINGDS" enabled="true" use-java-context="true" use-ccm="true">
                    <connection-url>jdbc:oracle:thin:@localhost:1521:TAFJDB</connection-url>
                    <driver>ora12c</driver>
                    <pool>
                        <prefill>false</prefill>
                        <min-pool-size>5</min-pool-size>
<max-pool-size>220</max-pool-size>
                        <flush-strategy>FailingConnectionOnly</flush-strategy>
                    </pool>
                    <security>
                        <user-name>tafj</user-name>
                        <password>secret</password>
                    </security>
                    <validation>
                        <validate-on-match>false</validate-on-match>
                        <background-validation>false</background-validation>
                        <use-fast-fail>false</use-fast-fail>
                    </validation>
                </datasource>

Please note that these data sources refer to the module corresponding to your driver. That is for oracle:

<driver>ora12c</driver>

Thus, you should add a reference to this module in the driver section and to the corresponding driver class that you want to use. That is for oracle:

<driver name="ora12c" module="com.oracle.ora12c">
          <xa-datasource-class> oracle.jdbc.xa.client.OracleXADataSource </xa-datasource-class>
  </driver>
The attribute jta="false" in the locking data source header indicates that it is non-transactional.

This section configures the following JMS resources:

  • Default JMS queues used for Temenos products in reply or request pattern,
    • BROWSER,
    • ARC-IB,
    • TWS
    • SEAT injection,
    • CALL_AT subroutine,
  • EXEC queue to launch Temenos Transact Phantom
  • TEC topics for Temenos Transact Monitor purpose

Edit the data source section of %JBOSS_HOME%\standalone\configuration\standalone-full.xml by referring the %TAFJ_HOME%\appserver\jboss\jboss7\standalone-full.xml file as an example.

The following destinations need to be added:

<jms-destinations>
<jms-queue name="t24OFSQueue">
<entry name="queue/t24OFSQueue"/>
<entry name="java:jboss/exported/jms/queue/t24OFSQueue"/>
</jms-queue>
<jms-queue name="t24OFSReplyQueue">
<entry name="queue/t24OFSReplyQueue"/>
<entry name="java:jboss/exported/jms/queue/t24OFSReplyQueue"/>
</jms-queue>
<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>
<jms-queue name="t24ARCMOBQueue">
<entry name="queue/t24ARCMOBQueue"/>
<entry name="java:jboss/exported/jms/queue/t24ARCMOBQueue"/>
</jms-queue>
<jms-queue name="t24ARCMOBReplyQueue">
<entry name="queue/t24ARCMOBReplyQueue"/>
<entry name="java:jboss/exported/jms/queue/t24ARCMOBReplyQueue"/>
</jms-queue><jms-queue name="t24TWSQueue">
<entry name="queue/t24TWSQueue"/>
<entry name="java:jboss/exported/jms/queue/t24TWSQueue"/>
</jms-queue>
<jms-queue name="t24TWSReplyQueue">
<entry name="queue/t24TWSReplyQueue"/>
<entry name="java:jboss/exported/jms/queue/t24TWSReplyQueue"/>
</jms-queue>

<jms-queue name="t24TCIBQueue">
<entry name="queue/t24TCIBQueue"/>
<entry name="java:jboss/exported/jms/queue/t24TCIBQueue"/>
</jms-queue>
<jms-queue name="t24TCIBReplyQueue">
<entry name="queue/t24TCIBReplyQueue"/>
<entry name="java:jboss/exported/jms/queue/t24TCIBReplyQueue"/>
</jms-queue>
<jms-queue name="t24TCIBCORPQueue">
<entry name="queue/t24TCIBCORPQueue"/>
<entry name="java:jboss/exported/jms/queue/t24TCIBCORPQueue"/>
</jms-queue>
<jms-queue name="t24TCIBCORPReplyQueue">
<entry name="queue/t24TCIBCORPReplyQueue"/>
<entry name="java:jboss/exported/jms/queue/t24TCIBCORPReplyQueue"/>
</jms-queue>
<jms-queue name="t24TCIBWEALTHQueue">
<entry name="queue/t24TCIBWEALTHQueue"/>
<entry name="java:jboss/exported/jms/queue/t24TCIBWEALTHQueue"/>
</jms-queue>
<jms-queue name="t24TCIBWEALTHReplyQueue">
<entry name="queue/t24TCIBWEALTHReplyQueue"/>
<entry name="java:jboss/exported/jms/queue/t24TCIBWEALTHReplyQueue"/>
</jms-queue>
<jms-queue name="t24CALLATQueue">
<entry name="queue/t24CALLATQueue"/>
<entry name="java:jboss/exported/jms/queue/t24CALLATQueue"/>
</jms-queue>
<jms-queue name="t24CALLATReplyQueue">
<entry name="queue/t24CALLATReplyQueue"/>
<entry name="java:jboss/exported/jms/queue/t24CALLATReplyQueue"/>
</jms-queue>
<jms-queue name="t24AMLQueue">
<entry name="queue/t24AMLQueue"/>
<entry name="java:jboss/exported/jms/queue/t24AMLQueue"/>
</jms-queue>
<jms-queue name="t24AMLReplyQueue">
<entry name="queue/t24AMLReplyQueue"/>
<entry name="java:jboss/exported/jms/queue/t24AMLReplyQueue"/>
</jms-queue>
<jms-queue name="t24SEATQueue">
<entry name="queue/t24SEATQueue"/>
<entry name="java:jboss/exported/jms/queue/t24SEATQueue"/>
</jms-queue>
<jms-queue name="t24SEATReplyQueue">
<entry name="queue/t24SEATReplyQueue"/>
<entry name="java:jboss/exported/jms/queue/t24SEATReplyQueue"/>
</jms-queue>
<jms-queue name="t24EXECQueue">
<entry name="queue/t24EXECQueue"/>
<entry name="java:jboss/exported/jms/queue/t24EXECQueue"/>
</jms-queue>
<jms-topic name="tecEventsTopic">
<entry name="topic/tecEventsTopic"/>
<entry name="java:jboss/exported/jms/topic/tecEventsTopic"/>
</jms-topic>
</jms-destinations>

<entry name="queue/t24OFSQueue"/>: Allows to access the queue within the appserver.

<entry name="java:jboss/exported/jms/queue/t24OFSQueue"/>: Allows to access the queue remotely from an external standalone client.

Copyright © 2020- Temenos Headquarters SA

Contact Us

knowledge@temenos.com

Published on :
Monday, May 27, 2024 5:10:32 PM IST