Installing TAFJ for WebSphere under z/OS
The TAFJ application can be deployed in any WebSphere for z/OS configuration; stand-alone, network deployment configuration, or in a cluster. In effect, there are two Enterprise applications that need to be deployed, the TAFJ application itself, and the BrowserWeb application. This section does not describe how to install WebSphere Application Server for z/OS, or any other part of the z/OS operating system or middleware. For hardware and software prerequisites, see the TAFJ for system z prerequisites document.
Configuring WebSphere for Temenos Transact
This section creates service integration and adds a Bus member. A bus needs to be assigned to run on one or more application servers and server clusters. For most development activity, you will create and assign a single bus member to the bus. When a bus member is added, a messaging engine is created in that WebSphere instance, which has its own data store for messages.
Creating JMS Connection Factories
A JMS connection factory is used to create connections to JMS destinations. The associated JMS provider creates the JMS connection factory.
External components need to send request and receive response from Temenos Transact. Each component has a receive queue and a reply queue.
A topic queue is a queue that can broadcast too many registered components. This is the situation for the monitors. Many monitor clients can be registered to one server.
Creating Activation Specification
You create a JMS activation specification if you want to use a message-driven bean to communicate with the default messaging provider through Java™ EE Connector Architecture (JCA) 1.5. JCA provides Java connectivity between application servers such as WebSphere® Application Server, and enterprise information systems. It provides a standardized way of integrating JMS providers with Java EE application servers, and provides a framework for exchanging data with enterprise systems, where data is transferred in the form of messages. One or more message-driven beans can share a single JMS activation specification.
Configuring Session Replication
By default session replication is disabled in WebSphere Application Server. This section shows you how to manually configure session replication.
Installing the TAFJ Application Executables
This section shows how to install the executable files available in TAFJ installation pack.
Configuring TAFJ and WebSphere DataSource
This section shows the steps required in configuring TAFJ and WebSphere Data source.
This section shows the steps required to deploy TAFJ.
This section shows you how to deploy BrowserWeb.war in the application server.
In this topic
