How To Configure Listeners in Websphere Using TOCF (EE)

3/19/2018 How to configure listeners in websphere using TOCF(EE)
Temenos Support Forum (/SitePages/tsf.aspx) Portal Help N.ALMSILATI
Customer Support
Portal
(/SitePages/Home.aspx)
 MENU Entire Site Enter your keywords here 
Websphere TOCF(EE) Setup

IBM Websphere
Version: 7.0.0.0+
This document is to con gure listeners in TOCF(EE) which can be deployed in websphere application server. Here we
 (/SitePages/Home.aspx)
have taken sample as Batch le listener and mqseries listener.
 (/SitePages/T24Intelligence.aspx)
Install T24 RA:

Resource Adapters
 (/TCSPProfileCenter/infodefault.aspx)
à Install tocfT24ra-ra.rar using default values
 (/Support/DashBoard.aspx)
Was this page
Resource adapters > T24RA > J2C activation speci cation

Yes
à Set activation speci cation which is used by the RA to con gure a speci c endpoint instance
https://tcsp.temenos.com/HowTo/ConfLstnWebSph.aspx 1/27
- NAME: T24 Resource Adapter
- JNDI NAME: jca/t24ResourceAdapter
In this case, we are going to create separate connection factories for separate message driven bean in order to
process the batch le listener and mq series listener requests separately. Create separate connection factories as
given below.
Resource adapters > T24RA > J2C connection factories
à De ne new JCA connection factory for BFL
- NAME: T24 JCA Connection Factory BFL
- JNDI NAME: jca/t24ConnectionFactoryBFL
à De ne new JCA connection factory for MQ
- NAME: T24 JCA Connection Factory MQ
- JNDI NAME: jca/t24ConnectionFactoryMQ
Was this page
Yes
Resource adapters > T24RA > J2C connection factories > T24 JCA Connection Factory > Custom properties
à Con gure JCA connection properties.
Resource adapters > T24RA > J2C connection factories > T24 JCA Connection Factory > Connection pool properties
è Set the connection pool min / max size.
Was this page
Yes
Was this page
Con gure JMS Messaging Using Default Messaging Provider

Yes
Service Integration Bus > Buses
à Create new Service Integration Bus: BrowserBus

Service Integration Bus > Buses > BrowserBus
à Switch to tab 'Local Topology' and add a new Bus member
Note : Stop and Restart the Application Server in order to take e ect the changes.
Was this page
Yes
In this case, we are going to create two di erent JMS request queues each one for accepting requests from BFL and
MQ and two di erent JMS response queues each one for accepting responses from OFS MDB. In order to access
these JMS queues, the JMS connection and queue connection factories should be created as given below.
Resources / Resource Adapters/ JMS > Connection factories
à Create a new JMS connection factory using e.g. the 'Default Messaging Provider' for BFL.
- NAME: T24 JMS Connection Factory BFL
- JNDI NAME: jms/t24CxFactoryBFL
- Bus: BrowserBus
Resources / Resource Adapters/ JMS > Connection factories
à Create a new JMS connection factory using e.g. the 'Default Messaging Provider' for MQ.
- NAME: T24 JMS Connection Factory MQ
- JNDI NAME: jms/t24CxFactoryMQ
- Bus: BrowserBus
Was this page
Yes
JMS > Queue connection factories
à Create a new JMS Queue connection factory using e.g. the 'Default Messaging Provider' for BFL
- NAME: T24 Queue Connection Factory BFL
- JNDI NAME: jms/t24QueueCxFactoryBFL
- Bus: BrowserBus
JMS > Queue connection factories
à Create a new JMS Queue connection factory using e.g. the 'Default Messaging Provider' for MQ
- NAME: T24 Queue Connection Factory MQ
- JNDI NAME: jms/t24QueueCxFactoryMQ
- Bus: BrowserBus
Was this page
Yes
JMS > Queues
à Create a new JMS request Queue for BFL using e.g. the 'Default Messaging Provider'
- NAME: T24 OFS Queue BFL
- JNDI NAME: jms/t24OFSQueueBFL
- Bus: BrowserBus
- Queue name: Create Service Bus Integration destination à t24OFSQueueBFL
JMS > Queues
à Create a new JMS request Queue for MQ using e.g. the 'Default Messaging Provider'
- NAME: T24 OFS Queue MQ
- JNDI NAME: jms/t24OFSQueueMQ
- Bus: BrowserBus
- Queue name: Create Service Bus Integration destination à t24OFSQueueMQ
Was this page
Yes
Was this page

à Create a new JMS response Queue for MQ using e.g. the 'Default Messaging Provider'
Yes
- NAME: T24 OFS Reply Queue BFL
- JNDI NAME: jms/t24OFSReplyQueueBFL
- Bus: BrowserBus
- Queue name: Create Service Bus Integration destination à t24OFSReplyQueueBFL
à Create a new JMS response Queue for MQ using e.g. the 'Default Messaging Provider'
- NAME: T24 OFS Reply Queue MQ
- JNDI NAME: jms/t24OFSReplyQueueMQ
- Bus: BrowserBus
- Queue name: Create Service Bus Integration destination à t24OFSReplyQueueMQ
Was this page
Yes
Was this page

JMS > Activation Speci cation
à Create a new Activation speci cation using e.g. the 'Default Messaging Provider' for BFL
Yes
- NAME: T24 OFS Message MDB BFL
- JNDI NAME: jms/t24OfsMessageMDBBFL
- Destination JNDI NAME: jms/t24OFSQueueBFL
- Bus: BrowserBus
JMS > Activation Speci cation
à Create a new Activation speci cation using e.g. the 'Default Messaging Provider' for MQ
- NAME: T24 OFS Message MDB MQ
- JNDI NAME: jms/t24OfsMessageMDDMQ
- Destination JNDI NAME: jms/t24OFSQueueMQ
- Bus: BrowserBus
Was this page
Yes
Was this page

Install TOCF(EE):
Before installation of tocfee, we need to create batch le and mq series listeners in the tocfee.ear pack. Please follow
the below steps: Yes
1) tcserver.xml (which is present inside the tocfee.ear\tocfplugin-ra.rar)
You can open tocfplugin-ra.rar resource adapter archive with winzip and view the tcserver.xml. The adapter must
be a "TOCF" adapter type. After setting up the tcserver.xml, just zip up the rar again and copy this le to the deploy
directory - in the next step toc istener-ejb.jar will activate this inbound resource adapter.
<?xml version="1.0" ?>





<TCSERVER>
<ADAPTERS>

<ADAPTER id="T24.BFL" type="TOCF" active="true">

<MAX_SESSION> 5 </MAX_SESSION>
<MIN_SESSION> 1 </MIN_SESSION>
<TIMEOUT>30</TIMEOUT>
</ADAPTER>
<ADAPTER id="T24.MQ" type="TOCF" active="true">

<MAX_SESSION> 5 </MAX_SESSION>
<MIN_SESSION> 1 </MIN_SESSION>
<TIMEOUT>30</TIMEOUT>
</ADAPTER>
</ADAPTERS>
<MESSAGEFORMATTERS>

<MESSAGEFORMATTER id="Thai2UTF" type="charsetformatter">

<FROM>CP838</FROM>
<TO>UTF-8</TO>
</MESSAGEFORMATTER>
<MESSAGEFORMATTER id="UTF2Thai" type="charsetformatter">

<FROM>UTF-8</FROM>
<TO>CP838</TO> Was this page
</MESSAGEFORMATTER>
</MESSAGEFORMATTERS>
Yes
<LISTENERS>
<LISTENER id="BFL" type="batch lelistener" active="true">

<ADAPTERID>T24.BFL</ADAPTERID>
<DIR_IN>C:\requests</DIR_IN>
<DIR_OUT>C:\responses</DIR_OUT>
<DIR_ERR>C:\errors</DIR_ERR>
<MAX_PROCESS>0</MAX_PROCESS>
<EXTENSION_INDEX>idx</EXTENSION_INDEX>
<EXTENSION_TOPROCESS>txt</EXTENSION_TOPROCESS>
<EXTENSION_PROCESSED>pro</EXTENSION_PROCESSED>
<EXTENSION_ERROR>err</EXTENSION_ERROR>
<EXTENSION_RESPONSE>rsp</EXTENSION_RESPONSE>
<REQ_SEPARATOR>lf</REQ_SEPARATOR>
<SORT_DIRECTORY>true</SORT_DIRECTORY>
<DELETE_SOURCE>true</DELETE_SOURCE>
</LISTENER>
<LISTENER Name="MQ" type="mqseries" active="true">
<ADAPTERID>T24.MQ</ADAPTERID>
<MQHOST>127.0.0.1(1414)</MQHOST>
<MQMANAGER>NBFU</MQMANAGER>
<MQQUEUE>QIN</MQQUEUE>
<MQCHANNEL>NBFU.CH</MQCHANNEL>
<NBTHREADS>106</NBTHREADS>
<WAITINTERVAL>1000</WAITINTERVAL>
<CONSUMER>
<MQQUEUE>QOUT</MQQUEUE>
</CONSUMER>
</LISTENER>
</LISTENERS>
</TCSERVER>
2) ejb-jar.xml (which is present inside the tocfee.ear\toc istener-ejb.jar\META-INF)
Deploy the TOCFListener message driven bean (toc istener-ejb.jar)
This MDB is responsible for activating a TOCF "inbound" resource adapter and providing con guration to the
resource adapter. If you unzip this .jar you will see an "ejb-jar.xml" le that contains the following xml. The
important part is the activation con g – you are telling the tocfplugin-ra.rar which plugin you want to activate.
<message-driven id="MessageDriven_OFSListenerMDBBFL">
<display-name>OFSListener Bean</display-name>
Was this page
<ejb-name>OFSListenerMDBBFL</ejb-name>
<ejb-class>com.temenos.tocf.listener.mdb.TOCFListenerMDB</ejb-class>
Yes
<messaging-type>com.temenos.tocf.common.jca.OFSMessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<activation-con g>
<activation-con g-property>
<activation-con g-property-name>listener</activation-con g-property-name>
<activation-con g-property-value>BFL</activation-con g-property-value>
</activation-con g-property>
</activation-con g>
<resource-ref id="ResourceRef_OFSListenerMDB_jmsQueueConnectionFactoryBFL">
<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_OFSListenerMDB_t24OFSQueueBFL">
<description>OFS queue</description>
<res-ref-name>queue/t24OFSQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
</resource-ref>
<resource-ref id="ResourceRef_OFSListenerMDB_t24OFSReplyQueueBFL">
<description>OFS reply queue</description>
<res-ref-name>queue/t24OFSReplyQueue</res-ref-name>
</resource-ref>
</message-driven>
<message-driven id="MessageDriven_OFSListenerMDBMQ">
<display-name>OFSListener Bean</display-name>
<ejb-name>OFSListenerMDBMQ</ejb-name>
<ejb-class>com.temenos.tocf.listener.mdb.TOCFListenerMDB</ejb-class>
<messaging-type>com.temenos.tocf.common.jca.OFSMessageListener</messaging-type>
Was this page
<activation-con g>
Yes
<activation-con g-property-name>listener</activation-con g-property-name>
<activation-con g-property-value>MQ</activation-con g-property-value>
</activation-con g>
<resource-ref id="ResourceRef_OFSListenerMDB_jmsQueueConnectionFactoryMQ">
</resource-ref>
<resource-ref id="ResourceRef_OFSListenerMDB_t24OFSQueueMQ">
<description>OFS queue</description>
<res-ref-name>queue/t24OFSQueue</res-ref-name>
</resource-ref>
<resource-ref id="ResourceRef_OFSListenerMDB_t24OFSReplyQueueMQ">
</resource-ref>
</message-driven>
In addition to activating the TOCFPlugin this MDB is the message endpoint "TOCF" that you con gured in the
"tcserver.xml". OFS messages are received from the TOCF adapter and placed onto the OFS request queue. This
MDB then waits for OFS responses on the OFS response queue and hands them back to the "TOCF" adapter.
3) ibm-ejb-jar-bnd.xmi (which is present inside the tocfee.ear\toc istener-ejb.jar\META-INF)
<?xml version="1.0" encoding="UTF-8"?>
<com.ibm.ejs.models.base.bindings.ejbbnd:EJBJarBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI"

xmlns:com.ibm.ejs.models.base.bindings.ejbbnd="ejbbnd.xmi" xmlns:org.eclipse.jst.j2ee.ejb="ejb.xmi"
xmi:id="EJBJarBinding_TOCFListenerMDB">
<ejbJar href="META-INF/ejb-jar.xml#EJBJar_TOCFListenerMDB"/>
<ejbBindings
xmi:type="com.ibm.ejs.models.base.bindings.ejbbnd:MessageDrivenBeanBinding"xmi:id="MessageDrivenBeanBindi
Was this page
ng_OFSListenerMDBBFL" activationSpecJndiName="jca/t24PluginsResourceAdapter">
<enterpriseBean xmi:type="org.eclipse.jst.j2ee.ejb:MessageDriven" href="META-INF/ejb-
jar.xml#MessageDriven_OFSListenerMDBBFL"/> Yes
<resRefBindings xmi:id="ResourceRefBinding_OFSListenerMDB_jmsQueueConnectionFactoryBFL"jndiName="jms/
t24QueueCxFactoryBFL">
<bindingResourceRef href="META-INF/ejb-
jar.xml#ResourceRef_OFSListenerMDB_jmsQueueConnectionFactory"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_OFSListenerMDB_t24OFSQueueBFL" jndiName="jms/t24OFSQueue
BFL">
<bindingResourceRef href="META-INF/ejb-jar.xml#ResourceRef_OFSListenerMDB_t24OFSQueue"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_OFSListenerMDB_t24OFSReplyQueueBFL"jndiName="jms/t24OFSRe
plyQueueBFL">
<bindingResourceRef href="META-INF/ejb-jar.xml#ResourceRef_OFSListenerMDB_t24OFSReplyQueue"/>
</resRefBindings>
</ejbBindings>
<ejbBindings
xmi:type="com.ibm.ejs.models.base.bindings.ejbbnd:MessageDrivenBeanBinding"xmi:id="MessageDrivenBeanBindi
ng_OFSListenerMDBMQ" activationSpecJndiName="jca/t24PluginsResourceAdapter">
jar.xml#MessageDriven_OFSListenerMDBMQ"/>
<resRefBindings xmi:id="ResourceRefBinding_OFSListenerMDB_jmsQueueConnectionFactoryMQ"jndiName="jms/
t24QueueCxFactoryMQ">
<bindingResourceRef href="META-INF/ejb-
jar.xml#ResourceRef_OFSListenerMDB_jmsQueueConnectionFactory"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_OFSListenerMDB_t24OFSQueueMQ" jndiName="jms/t24OFSQueue
MQ">
<bindingResourceRef href="META-INF/ejb-jar.xml#ResourceRef_OFSListenerMDB_t24OFSQueue"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_OFSListenerMDB_t24OFSReplyQueueMQ"jndiName="jms/t24OFSRe
plyQueueMQ">
<bindingResourceRef href="META-INF/ejb-jar.xml#ResourceRef_OFSListenerMDB_t24OFSReplyQueue"/>
</resRefBindings>
</ejbBindings>
</com.ibm.ejs.models.base.bindings.ejbbnd:EJBJarBinding>
As de ned Message driven bean in ejb-jar.xml, the corresponding MDB's has to be de ned in the websphere
descriptor le ibm-ejb-jar-bnd.xmi.
Was this page
4) ejb-jar.xml (which is present inside the tocfee.ear\tocfOFSmessage-ejb.jar\META-INF)
Yes
Deploy the OFS message driven bean (tocfOFSmessage-ejb.jar)
This MDB is responsible for getting a requests from request queue and give to T24 via TOCF resource adapter.
<message-driven id="MessageDriven_OfsMessageMDBBFL">
<display-name>OFSMessage Bean</display-name>
<ejb-name>OFSMessageMDBBFL</ejb-name>
<ejb-class>com.temenos.tocf.ofsmessage.mdb.OFSMessageMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<activation-con g>
<activation-con g-property-name>acknowledgeMode</activation-con g-property-name>
<activation-con g-property-value>Auto-acknowledge</activation-con g-property-value>
</activation-con g>
<resource-ref id="ResourceRef_jmsQueueConnectionFactoryBFL">
<description>T24 Queue Connection Factory</description>
</resource-ref>
<resource-ref id="ResourceRef_t24ConnectionFactoryBFL">
<description>T24 JCA Connection Factory</description>
<res-ref-name>eis/t24ConnectionFactory</res-ref-name>
<res-type>com.temenos.tocf.t24ra.T24ConnectionFactory</res-type>
</resource-ref>
<resource-ref id="ResourceRef_t24OFSReplyQueueBFL">
<res-auth>Container</res-auth> Was this page
</resource-ref>
</message-driven> Yes
<message-driven id="MessageDriven_OfsMessageMDBMQ">
<display-name>OFSMessage Bean</display-name>
<ejb-name>OFSMessageMDBMQ</ejb-name>
<ejb-class>com.temenos.tocf.ofsmessage.mdb.OFSMessageMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<activation-con g>
<activation-con g-property-name>acknowledgeMode</activation-con g-property-name>
<activation-con g-property-value>Auto-acknowledge</activation-con g-property-value>
</activation-con g>
<resource-ref id="ResourceRef_jmsQueueConnectionFactoryMQ">
<description>T24 Queue Connection Factory</description>
</resource-ref>
<resource-ref id="ResourceRef_t24ConnectionFactoryMQ">
<description>T24 JCA Connection Factory</description>
<res-ref-name>eis/t24ConnectionFactory</res-ref-name>
<res-type>com.temenos.tocf.t24ra.T24ConnectionFactory</res-type>
</resource-ref>
<resource-ref id="ResourceRef_t24OFSReplyQueueMQ">
</resource-ref>
</message-driven>
Was this page
5) ibm-ejb-jar-bnd.xmi (which is present inside the tocfee.ear\toc istener-ejb.jar\META-INF)
<?xml version="1.0" encoding="UTF-8"?>

Yes
<com.ibm.ejs.models.base.bindings.ejbbnd:EJBJarBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI"

xmlns:com.ibm.ejs.models.base.bindings.ejbbnd="ejbbnd.xmi" xmlns:org.eclipse.jst.j2ee.ejb="ejb.xmi"
xmi:id="EJBJarBinding_OfsMessageMDB">
<ejbJar href="META-INF/ejb-jar.xml#EJBJar_OfsMessageMDB"/>
<ejbBindings xmi:type="com.ibm.ejs.models.base.bindings.ejbbnd:MessageDrivenBeanBinding"
xmi:id="MessageDrivenBeanBinding_OfsMessageMDBBFL" activationSpecJndiName="jms/t24OfsMessageMDBBFL">

jar.xml#MessageDriven_OfsMessageMDBBFL"/>
<resRefBindings xmi:id="ResourceRefBinding_jmsQueueConnectionFactoryBFL"
jndiName="jms/t24QueueCxFactoryBFL">
<bindingResourceRef href="META-INF/ejb-jar.xml#ResourceRef_jmsQueueConnectionFactory"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_t24ConnectionFactoryBFL"
jndiName="jca/t24ConnectionFactoryBFL">
<bindingResourceRef href="META-INF/ejb-jar.xml#ResourceRef_t24ConnectionFactory"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_t24OFSReplyQueueBFL" jndiName="jms/t24OFSReplyQueueBFL">
<bindingResourceRef href="META-INF/ejb-jar.xml#ResourceRef_t24OFSReplyQueue"/>
</resRefBindings>
</ejbBindings>
<ejbBindings xmi:type="com.ibm.ejs.models.base.bindings.ejbbnd:MessageDrivenBeanBinding"
xmi:id="MessageDrivenBeanBinding_OfsMessageMDBMQ" activationSpecJndiName="jms/t24OfsMessageMDBMQ">

jar.xml#MessageDriven_OfsMessageMDBMQ"/>
<resRefBindings xmi:id="ResourceRefBinding_jmsQueueConnectionFactoryMQ"
jndiName="jms/t24QueueCxFactoryMQ">
<bindingResourceRef href="META-INF/ejb-jar.xml#ResourceRef_jmsQueueConnectionFactory"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_t24ConnectionFactoryMQ"
jndiName="jca/t24ConnectionFactoryMQ">
<bindingResourceRef href="META-INF/ejb-jar.xml#ResourceRef_t24ConnectionFactory"/>
</resRefBindings>
<resRefBindings xmi:id="ResourceRefBinding_t24OFSReplyQueueMQ" jndiName="jms/t24OFSReplyQueueMQ">
<bindingResourceRef href="META-INF/ejb-jar.xml#ResourceRef_t24OFSReplyQueue"/>
</resRefBindings>
Was this page
</ejbBindings>
</com.ibm.ejs.models.base.bindings.ejbbnd:EJBJarBinding>
Yes
As de ned Message driven bean in ejb-jar.xml, the corresponding MDB's has to be de ned in the websphere
descriptor le ibm-ejb-jar-bnd.xmi.
Enterprise Applications
à Install tocfee.ear using default values.
The following warnings can be ignored at this stage:
ADMA0114W: Resource assignment with JNDI name eis/com.temenos.tocf.common.jca.OFSMessageListener is not

found …
ADMA0114W: Resource assignment with JNDI name jca/t24PluginsResourceAdapter is not found …
ADMA0115W: Resource assignment of name queue/requestQueue and type javax.jms.Queue, with JNDI name

jms/requestQueue is not found...
ADMA0115W: Resource assignment of name queue/responseQueue and type javax.jms.Queue, with JNDI name

jms/responseQueue is not found…

Was this page
Yes
Enterprise Applications > TOCF(EE)_EAR > Manage Modules > TOCFPLUGIN > Resource Adapter > J2C Activation
speci cations > com.temenos.tocf.common.jca.OFSMessageListener
à Set activation speci cation for the TOCF(EE) Plugin component
- NAME: T24 Plugin Resource Adapter
- JNDI NAME: jca/t24PluginsResourceAdapter
Was this page
Yes
Was this page

Enterprise Applications
à Start TOCF(EE)_EAR
Yes
Start the jbase_agent :

Start the jbase_agent with port number(20002) on the host(127.0.0.1) speci ed in the custom properties of T24 JCA
connection factory.
Resource adapters > T24RA > J2C connection factories > T24 JCA Connection Factory BFL > Custom properties
Put the SWIFT messages in the directory which you have speci ed in <DIR_IN> batch lelistener and the messages
will be processed via batch lelistener.
For example, we created a text le called r1_swift.txt which contains the actual SWIFT message and put it in the
<DIR_IN> directory.
Was this page
Yes
The message has been processed and record has been created in SWIFT.IN.LIST.
Start the jbase_agent with port number(20003) on the host(127.0.0.1) speci ed in the custom properties of T24 JCA
connection factory.
Resource adapters > T24RA > J2C connection factories > T24 JCA Connection Factory MQ > Custom properties
Put any sample messages in the directory which you have speci ed in MQ input queue and the messages will be
processed via mqseries listener.
For example, we have a sample enquiry message and put it in queue INQ and you can get the output in OUTQ.
Was this page
Yes
The output will be posted in the Output queue 'QOUT'.
Was this page
COPYRIGHT © 2016 TEMENOS HEADQUARTERS SA

(http://www.temenos.com/)
Best viewed in Internet Explorer 10 & above
Yes

How To Configure Listeners in Websphere Using TOCF (EE)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

How To Configure Listeners in Websphere Using TOCF (EE)

Uploaded by

Copyright:

Available Formats

3/19/2018 How to configure listeners in websphere using TOCF(EE)

Temenos Support Forum (/SitePages/tsf.aspx) Portal Help N.ALMSILATI

 MENU Entire Site Enter your keywords here 

Websphere TOCF(EE) Setup

Was this page

Resource adapters > T24RA > J2C activation speci cation

- NAME: T24 Resource Adapter

- JNDI NAME: jca/t24ResourceAdapter

Resource adapters > T24RA > J2C connection factories

à De ne new JCA connection factory for BFL

- NAME: T24 JCA Connection Factory BFL

- JNDI NAME: jca/t24ConnectionFactoryBFL

à De ne new JCA connection factory for MQ

- NAME: T24 JCA Connection Factory MQ

- JNDI NAME: jca/t24ConnectionFactoryMQ

Was this page

à Con gure JCA connection properties.

è Set the connection pool min / max size.

Was this page

Was this page

Con gure JMS Messaging Using Default Messaging Provider

à Create new Service Integration Bus: BrowserBus

Service Integration Bus > Buses > BrowserBus

à Switch to tab 'Local Topology' and add a new Bus member

Was this page

Resources / Resource Adapters/ JMS > Connection factories

- NAME: T24 JMS Connection Factory BFL

- JNDI NAME: jms/t24CxFactoryBFL

Resources / Resource Adapters/ JMS > Connection factories

- NAME: T24 JMS Connection Factory MQ

- JNDI NAME: jms/t24CxFactoryMQ

Was this page

JMS > Queue connection factories

- NAME: T24 Queue Connection Factory BFL

- JNDI NAME: jms/t24QueueCxFactoryBFL

JMS > Queue connection factories

- NAME: T24 Queue Connection Factory MQ

- JNDI NAME: jms/t24QueueCxFactoryMQ

Was this page

JMS > Queues

- NAME: T24 OFS Queue BFL

- JNDI NAME: jms/t24OFSQueueBFL

- Queue name: Create Service Bus Integration destination à t24OFSQueueBFL

JMS > Queues

- NAME: T24 OFS Queue MQ

- JNDI NAME: jms/t24OFSQueueMQ

- Queue name: Create Service Bus Integration destination à t24OFSQueueMQ

Was this page

Was this page

- JNDI NAME: jms/t24OFSReplyQueueBFL

- Queue name: Create Service Bus Integration destination à t24OFSReplyQueueBFL

- NAME: T24 OFS Reply Queue MQ

- JNDI NAME: jms/t24OFSReplyQueueMQ

- Queue name: Create Service Bus Integration destination à t24OFSReplyQueueMQ

Was this page

Was this page

- JNDI NAME: jms/t24OfsMessageMDBBFL

- Destination JNDI NAME: jms/t24OFSQueueBFL

JMS > Activation Speci cation

- NAME: T24 OFS Message MDB MQ

- JNDI NAME: jms/t24OfsMessageMDDMQ

- Destination JNDI NAME: jms/t24OFSQueueMQ

Was this page