Stack3 RHEL WL Runbook R17 V1.2 MT PDF

Stack 3 Red Hat - WebLogic
Runbook for multi-tier installations, V1.2

All 17.x releases up to and including R17
April 2017
C rea t ed b y J u m p S t ar t
S t a ck 3 R ed H a t - W eb L og i c R u n b ook f or m u l t i -t i er i n st a l l a t i on s 1. 2
Contents
1 About this Runbook 5
1.1 Stacks table 5
1.2 Audience 6
1.2.1 Skills and knowledge 7
1.3 Legal 7
1.4 History 8
2 Prerequisites 9
2.1 Software prerequisites 9
2.1.1 Third party software 9
2.1.2 Temenos software 9
UXP Browser deployment files 10
2.2 Running prerequisite tasks 10
2.2.1 Installing Xming on Windows 10
2.2.2 Establishing a connection with X11 forwarding enabled in Putty 11
2.2.3 Enabling X11 forwarding in SecureCRT 11
2.2.4 Testing Xorg-x11-apps or Xming 13
2.2.5 Installing Java Development Kit on Linux 13
3 Before you start 15

3.1 Supporting documentation 15
3.2 Checklist 15
4 Installing WebLogic sever in a cluster 16

4.1 Architecture 16
4.1.1 Web layer 17
4.1.2 Application layer 18
4.1.3 Data layer 18
4.1.4 Load balancer 18
4.2 Preparing the installation package 19
4.3 Installing with the WebLogic installer 19
4.4 Creating a Domain, Administration and Managed Server Cluster in Oracle WebLogic 25
4.5 Starting WebLogic servers 33
4.6 Accessing administration console 34
2 C rea t ed b y J u m p S t ar t
4.7 Configuring all machines to use plain socket 35

4.8 Configuring the NodeManager.properties file 37
4.9 Starting the Node Manager 38
4.10 Creating a domain on the remote managed server 40
4.11 Configuring the nodemanager.properties file on the remote server 45
4.12 Enrolling the servers with a domain 46
4.12.1 Setting the environment 46
4.12.2 Running the wlst.sh script in interactive mode 47
4.12.3 Running the nmEnroll command 48
4.13 Starting the Node Manager on server-2 49
4.14 Starting the Managed Servers in the administration server console in application layer 52
5 Configuring TAFJ-T24 in WebLogic cluster in application layer 54

5.1 Adding the TAFJ-T24 class path in WebLogic cluster 54
5.2 TAFJ configuration scripts in the application server 55
5.3 Deploying and configuring TAFJEE in application layer 56
6 Configuring local queues in application layer 59

6.1 The rationale for creating Local Queues 59
6.2 Creating local queues in a WebLogic cluster 59
6.3 Issue: T24ConnectionFactory load balancing causes failures. 63
7 Configuring the foreign JNDI server in web layer 65

7.1 Creating a foreign JNDI provider 65
7.2 Creating a foreign server 67
7.3 Configuring a foreign server 69
7.4 Configuring a foreign JMS destination 70
7.5 Creating a BROWSER reply queue 71
7.6 Creating connection factories 72
8 Deploying and configuring T24 BrowserWeb in web layer 75

8.1 Preparing for deployment 75
8.2 Deploying BrowserWeb.war 76
8.3 Accessing BrowserWeb 79
9 Deploying and configuring UXP Browser in WebLogic cluster in

application and web layers 80
9.1 Architecture diagram 80
9.2 Overview of the UXP Browser 81
9.3 Uncompressing the BRP-generated.zip file 82
9.4 Configuring hothouse-iris in application layer 83
9.5 Configuring hothouse-iris in application layer 84
9.6 Deploying and configuring Authenticator.war 86
9.6.1 Step 1: Modifying Authenticator.war before the deployment 86
9.6.2 Step 2: Editing the SSOAPI.properties configuration file 87
9.6.3 Step 3: Deploying Authenticator.war 88
9.7 Configuring and deploying UXP Browser in web layer 90
9.7.1 Step 1: Configuring arguments 90
9.7.2 Step 2: Preparing for deployment 91
9.7.3 Step 3: Editing the SSOAPI.Properties configuration file 92
9.7.4 Step 4: Deploying UXP Browser 92
10 Installing and configuring HTTP load balancer server 95

10.1 Configuring the HTTP load balancer server 95
10.2 Starting the load balancer HTTP server 97
10.3 Starting the Node Manager for the HTTP server 97
10.4 Accessing the UXP Browser 99
10.5 Accessing TAFJEE from the Load Balancer 100
11 Glossary 101
1 About this Runbook

The Stack 3 Red Hat - WebLogic Runbook for multi-tier installations shows you how to install and
configure TAFJ-T24 on WebLogic application server in a multi-tier environment. It also shows you how to
deploy a BrowserWeb and UXP Browser and access T24 using those browsers.
This runbook does not provide instructions for installing third-party software, such as the Oracle 12 c
database, the WebLogic application server or OSB (SOA). For more information see the relevant vendor's
documentation.
1.1 Stacks table
Note: TCIB, TCMB, TAP and data source are not documented in this runbook.
1.2 Audience
This runbook is designed for technical consultants who want to deploy TAFJ-T24 on a WebLogic application
server, and deploy T24 Oracle custom adapter on Oracle Service Bus (OSB).
1 . 2 . 1 Sk i l l s and k now l edge

To use this runbook, you need a basic understanding of both TAFJ-T24 and WebLogic application servers and
T24 Oracle custom adapters.
1.3 Legal
© Copyright 2017 Temenos Headquarters SA. All rights reserved.
TM
The information in this guide relates to TEMENOS information, products and services. It also includes
information, data and keys developed by other parties.
While all reasonable attempts have been made to ensure accuracy, currency and reliability of the content in
this guide, all information is provided "as is".
There is no guarantee as to the completeness, accuracy, timeliness or the results obtained from the use of this
information. No warranty of any kind is given, expressed or implied, including, but not limited to warranties
of performance, merchantability and fitness for a particular purpose.
In no event will TEMENOS be liable to you or anyone else for any decision made or action taken in reliance
on the information in this document or for any consequential, special or similar damages, even if advised of
the possibility of such damages.
TEMENOS does not accept any responsibility for any errors or omissions, or for the results obtained from the
use of this information. Information obtained from this guide should not be used as a substitute for
consultation with TEMENOS.
References and links to external sites and documentation are provided as a service. TEMENOS is not
endorsing any provider of products or services by facilitating access to these sites or documentation from this
guide.
The content of this guide is protected by copyright and trademark law. Apart from fair dealing for the
purposes of private study, research, criticism or review, as permitted under copyright law, no part may be
reproduced or reused for any commercial purposes whatsoever without the prior written permission of the
copyright owner. All trademarks, logos and other marks shown in this guide are the property of their
respective owners.
1.4 History
Version Date Description Author
1.0 21 March 2017 Initial version Surender Padakanti
1.1 31 March 2017 Technical author edits Dominik Wietrzak
1.2 7 April 2017 Stack 3 runbook has been split into two books: Dominik Wietrzak
standalone and multi-tier.
2 Prerequisites
The following chapter describes the technical prerequisites and assumptions for installing and configuring
the RedHat Linux - WebLogic stack.
2.1 Software prerequisites
2 . 1 . 1 Thi r d par t y s oft w ar e
Component Name and version
Java JDK 1.7
Application server Oracle WebLogic 12.1.3.x
Database Oracle Database 12c
SOA suite Oracle Service Bus 12c
Database (XE) Oracle Database Express Edition 11g
IDE JDeveloper 12c
Web services engine Apache Axis2 1.6
2 . 1 . 2 Temenos s oft w ar e
To get the Temenos software installers, you need to request them from your account manager.
Component Version
TAFJ (TAFJEE) 201612
T24 201612
T24 BrowserWeb 201612
T24 EJB 201612
UXP Browser deployment files
File name Version

Browser.war latest
generated.zip 201612
hothouser-iris.war 201612
2.2 Running prerequisite tasks
2 . 2 . 1 Ins t al l i ng X mi ng on Wi ndow s
Some installation procedures require a running instance of X11. The X Window System is a networking
windowing system that provides a base set of communication protocols and functions for building graphical
interface clients for computers with bitmapped displays.
Because you need to run all the installations from a remote Telnet or SSH location, you need to install Xorg-
x11-apps on the target server to provide the X11 forwarding to the Telnet client such as SecureCRT® or
PUTTY®. You also need to install Xming on your Windows computer.
1. Download the Xming installation package from http://sourceforge.net/projects/xming/ to your Windows

computer.
2. Run the installer and leave all the default options on the installation panels.
3. After the installation completes, run Xming.
2 . 2 . 2 Es t abl i s hi ng a c onnec t i on w i t h X 1 1 for w ar di ng enabl ed i n

Put t y
1. Double-click the Putty icon.
2. Load the IP address of your target computer.
3. In the menu on the left, expand Connection > SSH > Auth and click X11.
4. In the "Options Controlling SSH X11 Forwarding" dialog. select Enable X11 forwarding.
5. Click Open.
2 . 2 . 3 Enabl i ng X 1 1 for w ar di ng i n Sec ur eC R T

1. Double-click the SecureCRT icon.
2. Click File > Connect.
3. Right-click your connection and then click Properties.
4. In the tree on the left expand Connection > Port Forwarding and click Remote X/11.
5. In the "Remote Port Forwarding / X11 Forwarding" dialog, select Forward X11 packets.
6. Click OK.
2 . 2 . 4 Tes t i ng X or g- x 1 1 - apps or X mi ng
1. Start your SSH session.
2. Run the xclock command.
X11 clock appears on your screen.
2 . 2 . 5 Ins t al l i ng J ava D evel opment Ki t on L i nux

1. Download the Java JDK installer for Linux (x64 jdk-7u79-linux-x64.tar.gz) from the following
web page:
http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html#jdk-
7u79-oth-JPR .
2. Upload the installer with your ftp client to the following directory on your target server:
$TEMENOS_HOME/Install
3. Open a new SSH connection, for example with Putty and change to the following directory on your
target server:
TEMENOS_HOME/3rdParty
4. Create the installation directory for the Java Development Kit:

mkdir -p $TEMENOS_HOME/3rdParty/Java
5. Copy the JDK installation file to the new installation directory:

cd $TEMENOS_HOME/3rdParty/Java
cp $TEMENOS_HOME/Install/jdk-7u79-linux-x64.tar.gz $TEMENOS_HOME/3rdParty/Java
6. Extract the contents of the JDK installer file:

tar -zxvf jdk-7u79-linux-x64.tar.gz
7. Check if the new jdk1.7.0_79 subdirectory exists: ls -la
8. Delete the redundant JDK installer:

rm jdk-7u79-linux-x64.tar.gz
9. Change to your home directory and open the file setup in your text editor, for example Vi:
cd Linux-/storage2/home/jumpst
vi setup
10. To add $JAVA_HOME to the Linux environment variable PATH, add the following lines in the setup file:
#setting the JAVA_HOME

export JAVA_HOME=/storage2/home/jumpst/Temenos/3rdParty/java/jdk1.7.0_79
echo $JAVA_HOME
Example:
11. Locate your Java executable files in your Linux system by running the which command:
which java
~/Temenos/3rdParty/java/jdk1.7.0_79/bin/java
12. Run another check to verify the JDK location:

Linux-/storage2/home/jumpst: echo $JAVA_HOME
/storage2/home/jumpst/Temenos/3rdParty/java/jdk1.7.0_79
3 Before you start

Before you start installing and configuring the stack, you need to check that your technical infrastructure has
been set up properly.
3.1 Supporting documentation

The TAFJ runtime contains a doc directory, which contains various documents on TAFJ utilities. It also
contains installation guides for various databases and application servers.
3.2 Checklist
To avoid deployment and configuration problems, complete the following checks.
Step number Step details
1☐ Check the version of your operating system.
Run the command cat /etc/redhat-release (cat /etc/system-release on all

other Linux operating systems).
2☐ Verify that you can connect to your database.
In order to verify your Database connection, prepare your database connection

parameters. To check if a connection can be made, you can use Oracle SQL Developer.
3☐ Check your application server.
For more information, see Fusion Middleware Administering Oracle Fusion Middleware.
4☐ Check the configuration of your firewall. Verify that all the required ports are open.
5☐ Check the version and health of your Java Development Kit. Run the following
command:
java -version
4 Installing WebLogic sever in a cluster

Once you have installed TAFJ and T24 on the both application layer servers, it is time to install and configure
WebLogic server in a cluster.
Note: You can follow the same steps to set up the WebLogic cluster on the web layer server.
4.1 Architecture
The solution has been deployed to be highly available using Red Hat Linux Server in a three-tiered
architecture that contains a web, application and database layers. The application and web layers are
WebLogic clusters made of two managed servers in each application and web layer. The data layer is an
Oracle database.
4 . 1 . 1 Web l ayer
In the web layer we deployed T24 Browser with a foreign server collocated with web Manager Servers.
Requests are forwarded to all managed servers on the web layer by the load balancer.
The High Availability at the web layer has been achieved as follows:
l The Temenos code is deployed in a WebLogic cluster consisting of two managed servers. The code has
been deployed with replication enabled. This means there is no need to configure sticky sessions at the
load balancer.
l A foreign JMS server with a JNDI URL pointing to all application servers for redundancy. To ensure
high availability, it is enough to point to only two of them.
4 . 1 . 2 A ppl i c at i on l ayer
High Availability at the application layer has been achieved as follows:
l The Temenos code is deployed in a WebLogic cluster that consists of two managed servers.
l Requests from the web layer are transferred to application servers using JMS technology.
l The browser request queue is configured to be uniformly distributed (WebLogic Uniform Distributed
Queue), accessed from the web layer using a foreign JMS server. The latter has been configured to
point to all application servers to ensure high availability.
l The JMS connection factory has load balancing enabled, which ensures requests are load-balanced
among all four application servers.
l A distributed reply queue has been found to generate errors. Instead, four local browser reply queues
with local JNDI have been configured.
l A JMS server on each of the application servers has been configured for high availability and load
balancing.
l The Temenos shared libraries (TAFJ runtime and T24) have been installed on each application server. A
reliable shared storage was not available.
4 . 1 . 3 D at a l ayer
A standalone Oracle 12c database instance is used in the data layer.
4 . 1 . 4 L oad bal anc er

We recommend that you use a hardware load balancer. In this scenario, a software load balancer is used
because a hardware one was not available.
4.2 Preparing the installation package

Use the Universal Installer to install Oracle WebLogic application server version 12.1.3. You can download
Oracle WebLogic from the following web site:
http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
Procedure
1. Download the WebLogic 12.1.3 generic file (fmw_12.1.3.0.0_wls.jar).

2. Upload the file with your FTP client to $TEMENOS_HOME/3rdParty/WebLogic.
3. Extract the contents of the jar file.
4.3 Installing with the WebLogic installer

1. Issue the following command to start the installation process:
java -jar fmw_12.1.3.0.0_wls.jar
The following messages are displayed:
Launcher log file is /tmp/OraInstall2017-01-26_01-36-33PM/launcher2017-01-26_01-36-33PM.log.

Extracting files......
Starting Oracle Universal Installer
Checking if CPU speed is above 300 MHz. Actual 2128.000 MHz Passed
Checking monitor: must be configured to display at least 256 colors. Actual 16777216
Passed
Checking swap space: must be greater than 512 MB. Actual 12386300 MB Passed
Checking if this platform requires a 64-bit JVM. Actual 64 Passed (64-bit not required)
Checking temp space: must be greater than 300 MB. Actual 118163 MB Passed
Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2017-01-26_01-36-33PM
Next, Installation Inventory Setup page is displayed.
2. Specify the Inventory Directory and click OK.
3. On the welcome screen, click Next.
4. Provide the location of the home directory for this installation of WebLogic 12.1.x and click Next.
Tip: The location you enter here will be your WM_HOME (ORACLE_HOME) value and click Next.
5. On the Installation Type page, select WebLogic Server and click Next.
6. After the Prerequisite Checks step has completed, click Next.
7. On the Security Updates page, click Next.

Tip: You do not need to provide your email address. Leave the field empty if you do not want Oracle
to send you notifications about security issues.
8. On the Installation Summary page, click Install.
The installation progress information is displayed. Click Next.
9. Click Finish.
The WebLogic installation process completes. Next, you need to create a domain for node managers.
4.4 Creating a Domain, Administration and Managed Server Cluster in

Oracle WebLogic
About this task
You are going to create a new Domain with one Administration Server (AdminServer) and two Managed
Servers (Server-1 and Server-2) in a cluster. The Administration Server and both Managed Servers are
installed on a single machine. (You can configure them on multiple servers as well.)
Procedure
1. To create a domain, start the configuration manager by running the config.cmd (Windows) or
config.sh (Linux) command that is available in $WEBLOGIC_HOME/wlserver/common/bin.
2. On the Configuration Type page, select Create a new domain, specify the domain location and click
Next.
3. Leave the default template and click Next.
4. Provide the administrator user name and password for the new WebLogic domain and click Next.
5. Define Domain Mode in which you wish to start your domain and specify the location of your JDK. In
this example, Development mode and Oracle Hotspot JDK installation are selected. You can keep this
configuration as the default one. Click Next.
6. On the Advanced Configuration page, select the components of your domain that you want to
customize. In this example: Adminsitration Server, Node Manager, Manager Server, Cluster and
Coherence are going to be configured.
7. Configure the Administration Server: specify server name, listen address and listen port and click Next.
The following values are used in this example:
Server Name
AdminServer
Listen Address
All local IP addresses on the machine
Listen port
7001
Tip: The default port value for WebLogic is 7001.
8. On the Node Manager page, in Node Manager Type, select Per Domain Default Location, provide
Node Manager user name and password (twice) and click Next.
9. On the Managed Servers page, define your two managed servers: click Add and specify server name,
from the drop-down list choose the IP address and enter 7003 as the listen port. Repeat the procedure
for the second server.
10. On the Clusters page, define your cluster: click Add and specify the name of your cluster, for example
WebCluster. Click Next.
11. Assign Server-1 to WebCluster: select the server in the option box on the left and click > to add the
server to your cluster. Click Next.
12. On the Machines page, add managed server-2: specify the name, IP address and listen port.
13. On the Assign Servers to Machines page, highlight available servers in the Servers list and click > to
assign the available servers to newly defined machines: Server_1 to Machine1 and Server_2 to
Machine2.
14. On the Configuration Summary page, review your configuration and click Create.
15. Click Next.
16. Click Finish to exit the configuration wizard.
4.5 Starting WebLogic servers

1. Set up the WEBLO_HOME environment variable:
export WEBLO_HOME=WEBLO_HOME=path_to_domain_home
2. Verify that you have set the variable correctly:

echo $WEBLO_HOME
3. Navigate to $WEBLO_HOME and run the startup script:

cd $WEBLOG_HOME
./startWebLogic.sh
4.6 Accessing administration console

To access the web console, you need to use the port that you specified while you were creating your
WebLogic domain. Otherwise, use the default administration port (7001).
Procedure
1. To log in to the WebLogic administration console, access the following URL:

http://ip_adress:port/console/
2. Enter the user name and password that you specified while you were creating your WebLogic domain:
The following welcome screen is displayed:
4.7 Configuring all machines to use plain socket

Procedure
1. In the Domain Structure on the left, click your domain name, expand Environment and click
Machines.
The Summary of Machines page opens.
2. Click a machine, for example Machine-1.
3. Click the General and then the Node Manager tab.

4. From the Type drop-down list, select Plain.
5. Click Save.
6. Follow the same steps for configuring Machine-2 to use a plain socket.
4.8 Configuring the NodeManager.properties file

Procedure
1. On the command line, change to MW_HOME/domain/nodeManager/

2. List the contents of the directory:
-/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager: ls
The directory contents are displayed:
nodemanager.domains nodemanager.log nodemanager.log.lck nodemanager.process.id
nodemanager.process.lck nodemanager.properties stopnodemanager.log
3. Open the nodemanager.properties file in the text editor of your choice, for example Vi:
/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager: vi nodemanager.properties
The contents of the file are displayed.
4. Provide the values for the following two parameters and save the changes:
l ListenAddress=IP_address
l SecureListener=false
4.9 Starting the Node Manager

Procedure
1. Navigate to your domain_home/bin directory:

cd /storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/bin
2. Run the startNodeManager.sh script in background mode:

projects/domains/mydomain/bin: nohup ./startNodeManager.sh &
/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_projects/domains/mydomain/nodemanager
CLASSPATH=/storage2/home/jumpst/Temenos/3rdParty/java/jdk1.7.0_
79/lib/tools.jar:/storage2/home/jumpst/Temenos/Middleware/Oracle_
Home/wlserver/server/lib/weblogic_sp.jar:/storage2/home/jumpst/Temenos/Middleware/Oracle_
Home/wlserver/server/lib/weblogic.jar:/storage2/home/jumpst/Temenos/Middleware/Oracle_
Home/wlserver/../oracle_common/modules/net.sf.antcontrib_1.1.0.0_1-0b3/lib/ant-
contrib.jar:/storage2/home/jumpst/Temenos/Middleware/Oracle_
Home/wlserver/modules/features/oracle.wls.common.nodemanager_
2.0.0.0.jar::/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/wlserver/..
+ /storage2/home/jumpst/Temenos/3rdParty/java/jdk1.7.0_79/bin/java -server -Xms32m -Xmx200m -
XX:MaxPermSize=128m -Dcoherence.home=/storage2/home/jumpst/Temenos/Middleware/Oracle_
Home/wlserver/../coherence -Dbea.home=/storage2/home/jumpst/Temenos/Middleware/Oracle_
Home/wlserver/.. -Dweblogic.RootDirectory=/storage2/home/jumpst/Temenos/Middleware/Oracle_
Home/user_projects/domains/mydomain -Xverify:none -
Djava.endorsed.dirs=/storage2/home/jumpst/Temenos/3rdParty/java/jdk1.7.0_
79/jre/lib/endorsed:/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/wlserver/../oracle_
common/modules/endorsed -Djava.security.policy=/storage2/home/jumpst/Temenos/Middleware/Oracle_
Home/wlserver/server/lib/weblogic.policy -
Dweblogic.nodemanager.JavaHome=/storage2/home/jumpst/Temenos/3rdParty/java/jdk1.7.0_79
weblogic.NodeManager -v
<06-Mar-2017 09:47:52 o'clock GMT> <INFO> <Loading domains file:
projects/domains/mydomain/nodemanager/nodemanager.domains>
<06-Mar-2017 09:47:52 o'clock GMT> <INFO> <Loaded NodeManager configuration properties from
'/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager/nodemanager.properties'>
Node manager v12.1.3
Configuration settings
DomainsFile=/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager/nodemanager.domains
LogLimit=0
DomainsDirRemoteSharingEnabled=false
AuthenticationEnabled=true
LogLevel=INFO
DomainsFileEnabled=true
ListenAddress=10.44.5.192
NativeVersionEnabled=true
ProcessDestroyTimeout=20000
ListenPort=5556
LogToStderr=true
weblogic.StartScriptName=startWebLogic.sh
SecureListener=false
LogCount=1
LogAppend=true
weblogic.StopScriptEnabled=false
StateCheckInterval=500
CrashRecoveryEnabled=false
weblogic.StartScriptEnabled=true
LogFile=/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
coherence.StartScriptEnabled=false
ListenBacklog=50
NodeManagerHome=/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager
weblogic.startup.JavaHome=/storage2/home/jumpst/Temenos/3rdParty/java/jdk1.7.0_79
weblogic.startup.MW_Home=
coherence.startup.JavaHome=/storage2/home/jumpst/Temenos/3rdParty/java/jdk1.7.0_79
coherence.startup.MW_Home=
Domain name mappings:
mydomain -> /storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_projects/domains/mydomain
<06-Mar-2017 09:47:52 o'clock GMT> <INFO> <WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT
2014 1604337 >
<06-Mar-2017 09:47:52 o'clock GMT> <INFO> <mydomain> <Server-2> <Startup configuration
properties loaded from "/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/servers/Server-2/data/nodemanager/startup.properties">
<06-Mar-2017 09:47:52 o'clock GMT> <INFO> <mydomain> <Server-1> <Startup configuration
properties loaded from "/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_
<06-Mar-2017 09:47:52 o'clock GMT> <INFO> <Plain socket listener started on port 5556, host
rhdevblade2.temenosgroup.com
4.10 Creating a domain on the remote managed server

To create a WebLogic cluster in AppLayer, you must create one more domain server on your remote server.
Before you begin
l For information about how to create a WebLogic domain, see Creating a domain.
l Use the universal installer to install Oracle WebLogic 12.1.3.
If you did not choose to launch the configuration wizard as part of the installation, you can do it manually.
Procedure
1. Upload the files with your FTP client to $TEMENOS_HOME.

2. Extract the contents of the fmw_12.1.3.0.0_wls.jar file.
java -jar fmw_12.1.3.0.0_wls.jar
3. At the command prompt, change to $WLS_HOME/common/bin/

4. Run the config.sh script. A configuration wizard starts. Click Next.
5. On the Templates page, leave the following options selected: Create Domain Using Product
Templates and Basic WebLogic Server Domain. Click Next.
6. Provide the administrator user name and password and click Next.
7. On the next page, select the following two options: Development in Domain Mode and Oracle
HotSpot 1.7.0_79 in JDK. Click Next.
8. Select Node Manager and click Next.
9. Specify the server name, listen address and listen port and click Next.
10. On the Configuration Summary page, click Create.
11. On the Configuration Progress page, click Next.
12. Click Finish to exit the wizard.
4.11 Configuring the nodemanager.properties file on the remote server

Procedure
1. On the command line, change to MW_HOME/domain_name/nodemanager.

cd nodemanager/
2. List the contents of the directory

ls
The following names are displayed:
nodemanager.domains nodemanager.log nodemanager.log.lck nodemanager.process.id
nodemanager.process.lck nodemanager.properties stopnodemanager.log [jumpstat@t24app1
nodemanager]$
3. Open the nodemanager.properties file in the text editor of your choice, for example vi.
4. Provide the values for the following two parameters and save the changes:
l ListenAddress=Remote_server2_IP_addres
l SecureListener=false
4.12 Enrolling the servers with a domain

You need to enroll a computer with a domain so that the Node Manager on that computer will accept
requests from the domain.
4 . 1 2 . 1 Set t i ng t he envi r onment

1. Log on to the Server-2 remote machine.
2. Change to $MW_HOME/wlserver/server/bin.
cd $MW_HOME/wlserver/server/bin
3. To set the environment, run the setWLSEnv.sh script.

./setWLSEnv.sh
The following output is dsplayed:
CLASSPATH=/home/jumpstat/Temenos/3rdParty/Java/jdk1.7.0_
79/lib/tools.jar:/home/jumpstat/Temenos/Middleware/Oracle_Home/wlserver/server/lib/weblogic_
sp.jar:/home/jumpstat/Temenos/Middleware/Oracle_
Home/wlserver/server/lib/weblogic.jar:/home/jumpstat/Temenos/Middleware/Oracle_
contrib.jar:/home/jumpstat/Temenos/Middleware/Oracle_
Home/wlserver/modules/features/oracle.wls.common.nodemanager_2.0.0.0.jar:
PATH=/home/jumpstat/Temenos/Middleware/Oracle_
Home/wlserver/server/bin:/home/jumpstat/Temenos/Middleware/Oracle_Home/wlserver/../oracle_
common/modules/org.apache.ant_1.9.2/bin:/home/jumpstat/Temenos/3rdParty/Java/jdk1.7.0_
79/jre/bin:/home/jumpstat/Temenos/3rdParty/Java/jdk1.7.0_
79/bin:/home/jumpstat/Temenos/3rdParty/Java/jdk1.7.0_
79/bin:/home/jumpstat/Temenos/3rdParty/Java/jdk1.7.0_
79/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/jumpstat/.local/bin:/home/jumpst
at/bin:/bin:/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/bin::/home/jumpstat/.local/bin:/home/jumpstat/bin:/bin:/home/jumpstat
/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/bin::/home/jumpstat/Temenos/Middleware/Oracle_
Home/wlserver/../oracle_common/modules/org.apache.maven_3.0.5/bin
4 . 1 2 . 2 R unni ng t he w l s t . s h s c r i pt i n i nt er ac t i ve mode
1. At the command prompt, change to /home/jumpstat/Temenos/Middleware/Oracle_
Home/wlserver/common/bin.
2. List the contents of the directory:

ls
The directory contents are displayed.
clonedunpack.sh commEnv.sh config_builder.sh config.sh pack.sh
prepareCustomProvider.sh qs_config.sh reconfig.sh unpack.sh wlscontrol.sh
wlsifconfig.sh wlst.sh
3. Run the script:

./wlst.sh
The following message is displayed:
Initializing WebLogic Scripting Tool (WLST) ...

Jython scans all the jar files it can find at first startup. Depending on the system, this
process may take a few minutes to complete, and WLST may not return a prompt right away.
Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands
4. Connect to the admin server by running the Connect method:

Connect(‘username’,’password’,’t3://admin_host:admin_port’)
Example:
connect('weblogic','weblogic1','t3://10.44.5.192:7001')
The following command-line output is displayed:
Connecting to t3://localhost:7001 with userid weblogic,weblogic1 ...

wls:/offline> connect('weblogic','weblogic1','t3://10.44.5.192:7001')
Connecting to t3://10.44.5.192:7001 with userid weblogic ...
Successfully connected to Admin Server "AdminServer" that belongs to domain "mydomain".
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
4 . 1 2 . 3 R unni ng t he nmEnr ol l c ommand

This command enrolls the computer on which WLST is running with the domain of the administration
server to which WLST is connected. "Enrolling" means the command downloads two files from the
administration server to this computer: nm_password.properties and SerializedSystemIni.dat.
The Node Manager "secret file" nm_password.properties contains the encrypted username and password
that are used by the adminstration server to authenticate itself to the Node Manager process. This file is
placed in the domain directory under /config/nodemanager/. The file used for encryption and decryption.
The SerializedSystemIni.dat file is placed in the domain directory under /security.
In addition, the nmEnroll() command creates or updates the nodemanager.domains file that is found in the
Node Manager home directory. It adds the current domain to the list of domains that this Node Manager is
allowed to manage.
The nmEnroll() command has two arguments:
l The domain home directory on this computer

l The Node Manager home directory on this computer
Procedure
1. At the command prompt, run the nmEnroll() command:

nmEnroll('/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain','/t24app1/home/jumpstat/Temenos/Middleware/Oracle_
Home/user_projects/domains/mydomain/nodemanager')
The following command-line output is displayed:
wls:/mydomain/serverConfig> nmEnroll('/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain','/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager')
Enrolling this machine with the domain directory at /home/jumpstat/Temenos/Middleware/Oracle_

Home/user_projects/domains/mydomain ...
Successfully enrolled this machine with the domain directory at

/home/jumpstat/Temenos/Middleware/Oracle_Home/user_projects/domains/mydomain.
wls:/mydomain/serverConfig>
2. To exit, enter exit().

The following output is displayed:
wls:/mydomain/serverConfig> exit()
Exiting WebLogic Scripting Tool.
4.13 Starting the Node Manager on server-2

Procedure
1. On the command line, navigate to $MW_HOME/bin.

2. Run the startNodeManager.sh in background mode:
nohup ./startNodeManager.sh &
The following output is displayed:
CLASSPATH=/home/jumpstat/Temenos/3rdParty/java/jdk1.7.0_
79/lib/tools.jar:/home/jumpstat/Temenos/Middleware/Oracle_Home/wlserver/server/lib/weblogic_
sp.jar:/home/jumpstat/Temenos/Middleware/Oracle_
Home/wlserver/server/lib/weblogic.jar:/home/jumpstat/Temenos/Middleware/Oracle_
contrib.jar:/home/jumpstat/Temenos/Middleware/Oracle_
Home/wlserver/modules/features/oracle.wls.common.nodemanager_
2.0.0.0.jar::/home/jumpstat/Temenos/Middleware/Oracle_Home/wlserver/..
+ /home/jumpstat/Temenos/3rdParty/java/jdk1.7.0_79/bin/java -server -Xms32m -Xmx200m -
XX:MaxPermSize=128m -Dcoherence.home=/home/jumpstat/Temenos/Middleware/Oracle_
Home/wlserver/../coherence -Dbea.home=/home/jumpstat/Temenos/Middleware/Oracle_Home/wlserver/..
-Dweblogic.RootDirectory=/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain -Xverify:none -
Djava.endorsed.dirs=/home/jumpstat/Temenos/3rdParty/java/jdk1.7.0_
79/jre/lib/endorsed:/home/jumpstat/Temenos/Middleware/Oracle_Home/wlserver/../oracle_
common/modules/endorsed -Djava.security.policy=/home/jumpstat/Temenos/Middleware/Oracle_
Home/wlserver/server/lib/weblogic.policy -
Dweblogic.nodemanager.JavaHome=/home/jumpstat/Temenos/3rdParty/java/jdk1.7.0_79
weblogic.NodeManager -v
<Mar 6, 2017 4:50:45 AM EST> <INFO> <Loading domains file:
/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager/nodemanager.domains>
<Mar 6, 2017 4:50:45 AM EST> <INFO> <Loaded NodeManager configuration properties from
'/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager/nodemanager.properties'>
Node manager v12.1.3
Configuration settings:
DomainsFile=/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager/nodemanager.domains
LogLimit=0
DomainsDirRemoteSharingEnabled=false
AuthenticationEnabled=true
LogLevel=INFO
DomainsFileEnabled=true
ListenAddress=10.44.245.54
NativeVersionEnabled=true
ProcessDestroyTimeout=20000
ListenPort=5556
LogToStderr=true
weblogic.StartScriptName=startWebLogic.sh
SecureListener=false
LogCount=1
LogAppend=true
weblogic.StopScriptEnabled=false
StateCheckInterval=500
CrashRecoveryEnabled=false
weblogic.StartScriptEnabled=true
LogFile=/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
coherence.StartScriptEnabled=false
ListenBacklog=50
NodeManagerHome=/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/nodemanager
weblogic.startup.JavaHome=/home/jumpstat/Temenos/3rdParty/java/jdk1.7.0_79
weblogic.startup.MW_Home=
coherence.startup.JavaHome=/home/jumpstat/Temenos/3rdParty/java/jdk1.7.0_79
coherence.startup.MW_Home=
Domain name mappings:
mydomain -> /home/jumpstat/Temenos/Middleware/Oracle_Home/user_projects/domains/mydomain
<Mar 6, 2017 4:50:45 AM EST> <INFO> <WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014
1604337 >
<Mar 6, 2017 4:50:45 AM EST> <INFO> <mydomain> <Server-2> <Startup configuration properties
loaded from "/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
<Mar 6, 2017 4:50:45 AM EST> <INFO> <mydomain> <Server-2> <Adjusted state of server 'Server-2 '
from FORCE_SHUTTING_DOWN to SHUTDOWN>
loaded from "/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
<Mar 6, 2017 4:50:45 AM EST> <INFO> <Plain socket listener started on port 5556, host
t24app1.temenosgroup.com>
<Mar 9, 2017 10:57:28 AM EST> <INFO> <mydomain> <Server-2> <The server 'Server-2' with process
id 21946 is no longer alive; waiting for the process to die.>
<Mar 9, 2017 10:57:28 AM EST> <INFO> <mydomain> <Server-2> <Server was shut down normally>
<Mar 9, 2017 11:01:17 AM EST> <INFO> <mydomain> <Server-2> <Boot identity properties saved to
"/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/servers/Server-2/data/nodemanager/boot.properties">
saved to "/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
<Mar 9, 2017 11:01:17 AM EST> <INFO> <mydomain> <Server-2> <Rotated server output log to
"/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/servers/Server-2/logs/Server-2.out00030">
<Mar 9, 2017 11:01:17 AM EST> <INFO> <mydomain> <Server-2> <Server error log also redirected to
server log>
<Mar 9, 2017 11:01:17 AM EST> <INFO> <mydomain> <Server-2> <Starting WebLogic server with
command line: /t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/bin/startWebLogic.sh >
<Mar 9, 2017 11:01:17 AM EST> <INFO> <mydomain> <Server-2> <Working directory is
'/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_projects/domains/mydomain>
<Mar 9, 2017 11:01:17 AM EST> <INFO> <mydomain> <Server-2> <Server output log file is
'/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/servers/Server-2/logs/Server-2.out'>
<Mar 9, 2017 11:04:05 AM EST> <INFO> <mydomain> <Server-2> <The server 'Server-2' is running
now.>
4.14 Starting the Managed Servers in the administration server console

in application layer
1. Access the following URL:
http://ip_address:port/console/
The login page opens.
2. Provide your user name and password and click Login. The WebLogic welcome screen opens.
3. In Domain Structure, under your domain name, expand Environment and click Servers.
4. In the pane on the right, click the Control tab.
5. Select both servers (Server-1 and Server-2) and click Start.
After a few minutes, both Managed Servers are in the Running state.
5 Configuring TAFJ-T24 in WebLogic cluster

in application layer
5.1 Adding the TAFJ-T24 class path in WebLogic cluster

1. Access the following URL:
http://ip_address:port/console/
The login page opens.
2. Provide your user name and password and click Login. The WebLogic Adminstration Console opens.
3. In Domain Structure, under your domain name, expand Environment, and click Servers.
4. In the pane on the right, click the Server Start tab.
5. Add the class paths in Server-1 and Server-2. You need to add all the jar files that are in TAFJ_
HOME/lib and TAFJ_HOME/ext.
Note: For more information on how to add TAFJ-T24 classpath in WebLogic, see the topic Setting up
WebLogic class paths that is in Stack 3 Red Hat - WebLogic Runbook for standalone installations.
6. Provide the following arguments in the Arguments field:
-Xms1024m -Xmx2048m -XX:MaxPermSize=1024m -Dtafj.home=/storage2/home/jumpst/Temenos/TAFJ -

Dhostname=Server-1 -Dfile.encoding=utf8
7. Restart both managed servers.
5.2 TAFJ configuration scripts in the application server

To have a working deployment you need to configure:
l Environment variables and shared libraries (TAFJ and T24 libraries)

l JMS resources (communication channels between applications)
l JDBC data sources (database connectivity)
l Applications deployment (TAFJ ear file, BrowserWeb)
The script of the complete configuration is located at %TAFJ_HOME%/appserver/weblogic/T24Setup.py.
Note: For more information, see the topic Running the WebLogic configuration script that is in Stack 3 Red Hat -
WebLogic Runbook for standalone installations. This script also deploys TAFJEE.ear in the WebLogic cluster
environment.
After you have run the python script to deploy TAFJEE.ear, you might encounter the following issue
(WebLogic cluster only):
An error occurred during activation of changes, please see the log for details.
com.temenos.tafj.common.exception.InvalidJMSMessageException
weblogic.application.ModuleException: java.lang.ClassNotFoundException:
com.temenos.tafj.logging.LoggerHelper
com.temenos.tafj.common.constants.keys.ConstantsKeyAppserver$VALUES_APPSERVER_NAME
com.temenos.tafj.jms.IMdbTafjSessionTimeout
An error occurred during activation of changes, please see the log for details.
5.3 Deploying and configuring TAFJEE in application layer

Before you begin
Before deploying TAFJEE.ear in your WebLogic application layer cluster, you need to add the
org.apache.neethi parameter in the Weblogic-application.xml configuration file. The file is stored in the
following location: TAFJJEE_EAR.ear/META-INF
The configuration entry:
<wls:package-name>org.apache.neethi.*</wls:package-name>
Procedure
1. Access the console, which is available at the following URL:

http://ip-address:port/console/
2. Log in with the user name and password that you created while creating your WebLogic domain.
3. In Domain Structure on the left, under your_domain, click Deployments.
4. In the pane on the right, click Install.
5. To upload the TAFJEE file that is provided with the Release, click upload your file(s) and chose file
TAFJJEE_EAR.ear.
6. Select Install this deployment as an application.
7. Select Target as: Cluster_1 and All servers in the cluster and click Next.
8. Provide TAFJEE_EAR as the name, click Next and Finish.
TAFJEE_EAR has been deployed successfully.
6 Configuring local queues in application

layer
6.1 The rationale for creating Local Queues

Local queues must be created because of a lot of errors that are caused by JMS exceptions resulting from
timeouts while waiting for replies on the T24BrowserReplyQueue. You need to replace the uniformly
distributed reply queues that have a global JNDI name with local reply queues that a have local JNDI name.
The local JNDI names must be the same on all application servers, namely jms/t24BrowserReplyQueue.
Tip: Ensure that you have stopped the Managed Server before you create the Local Queue.
6.2 Creating local queues in a WebLogic cluster

1. Access the console, which is available at the following uRL:
3. In Domain Structure on the left, under your_domain, expand Services.
4. Click Messaging and then JMS Modules.
5. In the JMS Modules table, click the name of JMS module in which you want to configure the queue
resource.
6. On the module Settings page, in the Summary of Resources table, click New.
7. On the Create a New JMS System Module Resource page, select Queue from the list of JMS resources,
and then click Next.
8. On the Queue Properties page, In Name, enter a name for the uniform distributed queue. In JNDI
Name, enter the JNDI name used to look up the queue within the JNDI namespace. In this example,
jms/t24BROWSERQueue is specified. Click Next.
Note: Once you create a uniform queue, you cannot rename it. Instead, you must delete it and create
another one that uses the new name.
9. For basic default targeting, accept the default targets presented in the Targets box and then click Finish.
The default targets are based on the parent JMS system module targets. From the Subdeployments
dropdow list, select SubModule-t24.
Note: You must create a new submodule for the local JNDI queue. If you choose the default, that is
submodule-T24, then all your queues will modify the target to Server-1 or server-1 rather than cluster-1.
10. Click Finish. The configured uniform queue is added to the module's Summary of Resources table,
which displays its default targets. The default targeting will also be reflected by the Default Targeting
Enabled check box on the queue Configuration: General page.
The local queue for jms/t24BROWSERQueue and jms/t24BROWSERReplyQueue has been created.
Warning: Make sure that the uniform Distributed Queue for jms/t24BROWSERReplyQueue is renamed
to something else, for example jms/t24BROWSERReplyQueue1.
11. Similarly, you can create a local queue for JMS-server-2.
6.3 Issue: T24ConnectionFactory load balancing causes failures.

Issue
While generating online traffic with many concurrent users, a lot of errors occurred. The errors have
been tracked to be caused by JMS exceptions resulting from timeouts while waiting for replies on the
T24BrowserReplyQueue.
If you enable affinity and disable load balancing on the T24Connection factory, errors do not occur.
However, the application layer is not balanced. With affinity set, a given web server has its requests
handled by one given application server. This means, in case of an application server failure, all requests
would be redirected to one single application server, which may overload that application server.
Note: When affinity is enabled the load balancing option becomes redundant.
Recommended solution
Replace the uniformly distributed reply queue that has a global JNDI name with a local reply queue that
have local JNDI name. The local JNDI names must be the same on all application servers, namely
jms/t24BrowserReplyQueue.
This solution requires updating the ejb-jar.xml that is in the TFAJEE_MDB.jar file as follows:
<message-driven>
<display-name>Transacted Listener MDB for BROWSER</display-name>
<ejb-name>BROWSERTransactedMDB</ejb-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>Enable jmsReplyTo feature of an MDB </description>
<env-entry-type>java.lang.Boolean</env-entry-type>
<env-entry-value>true</env-entry-value>
</env-entry>
<ejb-local-ref>
</message-driven>
7 Configuring the foreign JNDI server in

web layer
This section describes the tasks you can perform to create, monitor, and configure foreign JNDI providers. A
foreign server represents a JNDI provider that resides outside a WebLogic server. It contains information that
allows WebLogic server to reach the remote JNDI provider. This way, a number of connection factory and
destination objects (queues or topics) can be defined on one JNDI directory. Using this you are going to
configure a foreign server.
7.1 Creating a foreign JNDI provider

A foreign server represents a JNDI provider that is outside a WebLogic server. It contains information that
allows a local WebLogic server instance to reach a remote JNDI provider, thereby allowing for a number of
foreign connection factory and destination objects to be defined on one JNDI directory.
Procedure

3. In Domain Structure on the left, under your_domain, expand Services, then Messages and click JMS
Modules
4. In the JMS Modules table, click the name of JMS module in which you want to configure the foreign
server resource.
5. On the module Settings page, in the Summary of JMS Modules pane, click New.
6. Specify SystemModule-0 as the name and click Next.
7. Select WebCluster as the Target (name of cluster).
8. Click Finish.
This page displays general information about the JMS system module and its resources. It also allows
you to configure new resources and access existing resources.
7.2 Creating a foreign server

A foreign server foreign messaging providers or remote WebLogic Server instances that are not part of the
current domain.

Modules
4. Click New.
5. On the Create a New JMS System Module Resource page, select Foreign Server from the list of JMS
resources and then click Next.
6. On the Foreign Server Properties page, enter a name for the foreign server and click Next.
Note: Once you create a foreign server, you cannot rename it. Instead, you must delete it and create
another one that uses the new name.
7. Select the target server and click Finish to create the foreign server.
The configured foreign server is added to the module's Summary of Resources table.
7.3 Configuring a foreign server

A foreign server represents a JNDI provider that resides outside a WebLogic server. It contains information
that allows WebLogic server to reach the remote JNDI provider. This way, a number of connection factory
and destination objects (queues or topics) can be defined in one JNDI directory.
1. Click the created ForignServer-0.
2. In the JNDI Initial Context Factory field, enter the name of the class that must be instantiated to
access the JNDI provider. This class name depends on the provider and vendor that are being used.
3. In JNDI Connection URL, enter the application layer IP addresses that the WebLogic Server uses to
contact the JNDI provider.
t3://IP-Address:Port,IP-Address:Port. Click Save.
7.4 Configuring a foreign JMS destination

A foreign destination (topic or queue) can be found on a remote server. When this destination is looked up
on the local server, a look-up will be performed automatically on the remote JNDI directory, and the object
will be returned from that directory.

Modules.
4. Click the Destinations tab.
5. Click the Configure a new Foreign JMS Destination text link. A dialog is displayed in the right pane
showing the tabs associated with configuring a foreign destination.
6. On the General tab, enter the following values in the Name, Local JNDI Name and Remote JNDI
Name fields:
l Name: ForeignDestination-0
l Local JNDI Name: jms/t24BROWSERQueue
l Remote JNDI Name: jms/t24BROWSERQueue
Here, you provide JMS destination matching in application layer.
7. Click OK.
7.5 Creating a BROWSER reply queue

Modules
4. Click the Configuration tab.
5. Enter the following values in the Local JNDI Name and Remote JNDI Name fields:
l Local JNDI Name: jms/t24BROWSERReplyQueue
l Remote JNDI Name: jms/t24BROWSERReplyQueue
6. Click Save.
7. To view both BROWSERQueue and BROWSERReplyQueue click the Destinations tab.
7.6 Creating connection factories

Modules
4. Expand the JMS > Connection Factories node. The JMS Connection Factories table is displayed in the
right pane showing all the connection factories defined in your domain.
5. Click New to create a foreign connection factory.
6. Click the General tab to define the general configuration attributes for the connection factory.
7. Enter a name for the connection factory: in this example ForeignConnectionFactory-0 is used. The
name must be unique within the WebLogic Server cluster or domain.
8. Specify the JNDI names and click OK.
l Local JNDI Name: jms/connectionFactory
l Remote JNDI Name: jms/connectionFactory
ForeignConnectionFactory-0 has been created.
Note: You can define multiple ConnectionFactories.
8 Deploying and configuring T24

BrowserWeb in web layer
8.1 Preparing for deployment

1. Add the following change to the Weblogic.xml file that is in the BrowserWeb.war file, in the WEB-INF
subdirectory.
<container-descriptor>
<show-archived-real-path-enabled>true</show-archived-real-path-enabled>
</container-descriptor>
2. Save the changes.

3. Enable the OHS servers in active/active mode, configured to forward requests from the load balancer to
all managed servers in the WebLogic cluster. To do that, add the following change to the
weblogic.xml file that is in BrowserWeb/WEB-INF.
<session-descriptor>
<persistent-store-type>replicated_if_clustered</persistent-store-type>
</session-descriptor>
4. Save the changes.
8.2 Deploying BrowserWeb.war

2. Log in with the user name and password that you created while creating your WebLogic domain. The
main page opens.
3. In Domain Structure on the left, under your_domain, click Deployments.
4. On the Summary of Deployments pane, click Install.
5. To upload the BrowserWeb file that is provided with the Release, click upload your file(s) and chose
the file BrowserWeb.war. Click Next.
.
6. Select Install this deployment as application and click Next.
7. In Clusters, select Webcluster and All servers in the cluster. Click Next.
8. Click Finish.
BrowserWeb is successfully deployed and in the Active state.
8.3 Accessing BrowserWeb

1. Access the following page in your web browser:
http://server_name:port/BrowserWeb
2. Log in with your valid credentials.
T24 Browser Welcome screen is displayed.
9 Deploying and configuring UXP Browser

in WebLogic cluster in application and web
layers
9.1 Architecture diagram
9.2 Overview of the UXP Browser

UXP Browser was deployed and tested on Oracle WebLogic 12C cluster as part of the Oracle Reference
Architecture. The purpose of this topic is to record all the steps followed for a successful deployment and
also keep track of all the issues faced. T24/TAFJ 201610 is installed in the test environment.
You need to request the following artefacts from your account manager:
l Browser.war
l hothouse-iris.war
l BRP-generated.zip
Browser.war is the new screen rendering engine based on the Temenos Connect platform. The end user
accesses the UXP Browser screen via this WAR file. When a URL is passed to DashBoardDynamic, it loads a
corresponding Temenos Connect screen from the UXP Browser folder (produced from the expanded
BRP.zip). It will also read from and write to T24 via hothouse-iris.war. This is done using the OData XML
protocol over HTTP or HTTPS.
hothouse-iris.war contains the IRIS runtime. It is responsible for all data interactions with T24. When it
receives a URL request, it loads a corresponding IRIS definition from the UXP Browser folder (produced from
the expanded BRP.zip file).
The BRP-generated.zip file contains all the artefacts needed by the new Temenos Connect screens and IRIS.
The contents of this folder are produced at build time. This is done by the developer using Design Studio or
by an automated build job. It is commonly referred to as Metadata.
The following section explains how all these artefacts work with each other.
1. The user opens the UXP Browser by accessing the following URL in their web browser:
http://ip:port/Browser.
2. The T24 Authenticator filter intercepts this request and looks for an HTTP Cookie called T24Auth. As
this is the first request, this cookie is not present.
3. The filter redirects the user to a login page.
4. The user enters their user name and password and submits the form.
5. The filter receives this request and then makes a connection to T24 and invokes a routine to check the
user’s password.
6. If successful, it signs the user’s ID, a random GUID and expiry time with a private key.
7. It then creates a HTTP cookie called T24Auth, which contains the encrypted data.
8. The filter then allows the URL request to flow through to the new Browser application.
9. Before it can display the home page for the user, it needs to make several data requests from IRIS. This
is needed to determine the user’s department code, default company etc.
10. The Temenos Connect Browser code takes the T24Auth cookie and injects into every subsequent
request it makes to IRIS.
11. When the IRIS war file is invoked by the Temenos UXP Browser, the same T24 authentication filter
code is invoked.
12. The same filter checks to see if there is a T24Auth cookie or HTTP header present. In this case, there
will be a T24Auth cookie be because the UXP Browser has injected it.
13. The filter attempts to decrypt the cookie using the public key.
14. If the decryption is successful, it will be able to see the user’s ID, correlation ID, GUID and expiry time.
15. The filter then asserts that this user is trusted and passes the request to IRIS for processing.
16. IRIS retrieves the user’s ID via the filtered request (from a Java User Principal).
17. Because the user ID has come from a signed encrypted cookie, it is trusted.
18. IRIS processes this request under the user ID given. It uses a preauthenticated T24 connection
(OFS.SOURCE = ‘IRISPA’).
19. The results are sent back to the UXP Browser.
20. The Browser renders the screen to the end user.
9.3 Uncompressing the BRP-generated.zip file

BRP-generated.zip is a large file (1.5 GB) and when unzipped will occupy about 4 GB.
1. Create the following directory structure in the web and application layer server:
/Temenos/BRP/generated
/Temenos/BRP/manual
2. Extract the contents of the generated-201612.3.zip file in the generated directory. As a result, the
edge and iris directories are created.
9.4 Configuring hothouse-iris in application layer

hothouse-iris.war contains the IRIS runtime, which is responsible for all data interactions with T24. When
it receives a URL request, it loads a corresponding IRIS definition from the BRP/iris folder.
1. Access the Weblogic console on the server in the application layer. The console is available at
http://ip_address:port/console.
2. In Domain Structure, under yourdomain, click Servers.
3. Click Server-1 and then click the Server start tab.
4. In the Arguments field, provide the following argument and click Save:
-Dcom.temenos.interaction.config.dir=/Temenos/BRP/generated/iris
When the applications start, they will look for the BRP/generated folder based on settings passed to
the webserver at start up. These are configured after accessing the web server Server Start tab.
9.5 Configuring hothouse-iris in application layer

2. Provide your user name and password and click Login.
3. In Domain Structure, under yourdomain, click Deployments.
4. Click Install to start the installation wizard.
5. To upload the hothouse-iris.war file that is provided with the Release, click upload your file(s) and
chose file hothouse-iris.war. Click Next.
6. In Clusters, select Cluster_1 and All servers in the cluster and click Next.
7. Click Next and Finish. You have successfully deployed hothouse-iris.war in WebLogic cluster in
application layer.
Note: Make sure the hothouse-iris is in Active status.

Tip: Verify whether hothouse-iris.war is working using the Postman application.
9.6 Deploying and configuring Authenticator.war

Authenticator.war is protected with a security layer which authenticates the user against T24. It provides a
password check, change password, reset password and new user password service.
9 . 6 . 1 St ep 1 : M odi fyi ng A ut hent i c at or . w ar befor e t he depl oyment

By default, the web.xml file that is in the Authenticator.war\WEB-INF directory does not have any data
sources defined. You need to add the following data sources if they are not present in your web.xml file.
<resource-ref id="ResourceRef_OFSIRISt24Datasource">
<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 id="ResourceRef_OFSIRISt24LockingDatasource">
<description>Used to get connections from T24 jdbc pool</description>
<res-ref-name>jdbc/t24LockingDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
9 . 6 . 2 St ep 2 : Edi t i ng t he SSO A PI. pr oper t i es c onfi gur at i on fi l e

The configuration settings for the T24Authenticator are located in the SSOAPI.properties file, which is in
the WEB-INF directory in Browser.war, hothouse-iris.war and Authenticator.war.
You need to uncomment the following lines in the SSOAPI.properties file.
SSOAPI=com.temenos.technology.SSOAPI.SSOAPIT24UserAuthorisationImpl
SSOAPI.T24REMOTE.URL=http://localhost:8001/auth
#SSOAPI=com.temenos.technology.SSOAPI.SSOAPIT24RemoteImpl
SSOAPI=com.temenos.technology.SSOAPI.SSOAPIT24UserAuthorisationImpl
LOG.LEVEL=INFO
BASIC.AUTH.MODE=false
PRIVATE.KEY=/WEB-INF/ssoprivate.key
PUBLIC.KEY=/WEB-INF/ssopublic.key
SSOAPI.AUTH.TOKEN.TIMEOUT=3600
SSOAPI.AUTH.MAX.LEASE=86400
SSOAPI.T24REMOTE.URL=http://IP-Address:port/auth
# TAFJ settings
TAFJ.POOLSIZE=2
TAFJ.APPSERVER.MODE=false
TAFJ.SUPER.TRANSACTION.MODE=false
TAFJ.OFS.SOURCE=GCS
9 . 6 . 3 St ep 3 : D epl oyi ng A ut hent i c at or . w ar


5. To upload the Authenticator.war file that is provided with the Release, click upload your file(s) and
chose file Authenticator.war. Click Next.
6. In Clusters, select Cluster_1 and All servers in the cluster and click Next.
7. Click Next and Finish.
Authenticator.war has been deployed.
9.7 Configuring and deploying UXP Browser in web layer
9 . 7 . 1 St ep 1 : C onfi gur i ng ar gument s


3. In Domain Structure, under base_domain, click Servers.
4. Click Server-1..
5. In the Arguments text area, add the following variables and click Save.
-Dcom.edgeipk.librarypath=/Temenos/BRP/manual/edge,/Temenos/BRP/generated/edge
-Doverride.IRIS_MAP
=/Temenos/BRP/manual/edge/data/HrefComponentManualMap.properties,/Temenos/BRP/manual/edge/data/
HrefComponentMap.properties
-Doverride.IRIS_ROOT=http://IP-Address:port/hothouse-iris/Hothouse.svc
9 . 7 . 2 St ep 2 : Pr epar i ng for depl oyment

Before deploying the Browser.war file, you have to modify the internal Browser.dfs file.
Procedure
1. Open the Browser.war file in a compression utility, for example 7zip.

2. Navigate to the Browser.war/WEB-INF directory.
3. Open the Browser.dfs file in a text editor and provide the IP address and port.
GlobalParameterValue="http://IP-Address:Port/hothouse-iris/Hothouse.svc" Name="IRIS_ROOT"
GlobalParameterValue="http:// IP-Address:Port /hothouse-iris/Hothouse.svc" Name="SOLR_URL"

GlobalParameterValue="http:// IP-Address:port /BrowserWeb/servlet/BrowserServlet"
Name="BROWSER_URL”
4. Save the file.
9 . 7 . 3 St ep 3 : Edi t i ng t he SSO A PI. Pr oper t i es c onfi gur at i on fi l e

The SSOAPI.properties file is located in the WEB-INF directory of Browser.war, hothouse-iris.war and
Authenticator.war.
You need to uncomment the following lines in the SSOAPI.properties file:
SSOAPI=com.temenos.technology.SSOAPI.SSOAPIT24RemoteImpl
#SSOAPI=com.temenos.technology.SSOAPI.SSOAPIT24UserAuthorisationImpl
LOG.LEVEL=INFO
BASIC.AUTH.MODE=false
PRIVATE.KEY=/WEB-INF/rsaprivate.key
PUBLIC.KEY=/WEB-INF/rsapublic.key
SSOAPI.AUTH.TOKEN.TIMEOUT=3600
SSOAPI.AUTH.MAX.LEASE=86400
#SSOAPI.T24REMOTE.URL=http://localhost:8001/Authenticator/auth
SSOAPI.T24REMOTE.URL=http://IP-Address:Port/Authenticator/auth
# TAFJ settings
TAFJ.POOLSIZE=2
TAFJ.APPSERVER.MODE=true
TAFJ.SUPER.TRANSACTION.MODE=false
TAFJ.OFS.SOURCE=GCS
9 . 7 . 4 St ep 4 : D epl oyi ng U X P B r ow s er
5. To upload the Browser file that is provided with the Release, click upload your file(s) and choose the
file Browser.war. Click Next.
6. Select the Webcluster and All Servers in the Cluster and click Next.
Browser.war has successfully been deployed.
10 Installing and configuring HTTP load

balancer server
10.1 Configuring the HTTP load balancer server

Ensure that you have already installed the HTTP OHS server on you machine as a standalone server.
The httpd.conf file is stored in D:\JumpStart\LB\HTTP\user_projects\domains\HTTP_

domain\config\fmwconfig\components\OHS\ohs1. Open the httpd.conf file in the text editor of your
choice and enter the following parameters.
########################
#Added for configuration WebLogic Cluster
#########################
# Enabling balancer manager support --> http://<server>/balancer-manager
#<Location "/balancer-manager">
<Location "/">
Order Deny,Allow
Allow from all
</Location>
<Location "/BrowserWeb">
SetHandler balancer-manager
Order Deny,Allow
Allow from all
</Location>
<Location "/Browser">
Order Deny,Allow
Allow from all
</Location>
<Location "/Authenticator">
Order Deny,Allow
Allow from all
</Location>
<Location "/hothouse-iris">
Order Deny,Allow
Allow from all
</Location>
<Location "/balancer-manager">
Order Deny,Allow
Allow from all
</Location>
# WebLayer cluster Non sticky load balancing

<Proxy "balancer://MyCluster">
BalancerMember "http://IP-WebServer-1:Port"
BalancerMember "http:// IP-WebServer-2:Port"
</Proxy>
ProxyPass "/BrowserWeb" "balancer://MyCluster/BrowserWeb"
ProxyPassReverse "/BrowserWeb" "balancer://MyCluster/BrowserWeb"
## Load balancing with stickyness using mod_headers, even if the back-end server does not set a
suitable session cookie
Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
<Proxy "balancer://mycluster2">
BalancerMember "http:// IP-WebServer-1:port" route=1
BalancerMember "http:// IP-WebServer-2:port" route=2
ProxySet stickysession=ROUTEID
</Proxy>
ProxyPass "/Browser" "balancer://MyCluster2/Browser"
ProxyPassReverse "/Browser" "balancer://MyCluster2/Browser"
#AppLayer Non sticky load balancing

<Proxy "balancer://MyCluster3">
BalancerMember "http://IP-AppServer-1:port"
BalancerMember "http://IP-Appserver-2:port"
</Proxy>
ProxyPass "/TAFJEE" "balancer://MyCluster3/TAFJEE"
ProxyPassReverse "/TAFJEE" "balancer://MyCluster3/TAFJEE"
ProxyPass "/Authenticator" "balancer://MyCluster3/Authenticator"
ProxyPassReverse "/Authenticator" "balancer://MyCluster3/Authenticator"
ProxyPass "/hothouse-iris" "balancer://MyCluster3/hothouse-iris"
ProxyPassReverse "/hothouse-iris" "balancer://MyCluster3/hothouse-iris"
10.2 Starting the load balancer HTTP server

1. On the command line, change to /HTTP_domain/bin.
2. Run the following command:
startComponent.sh ohs1
3. When prompted, provide the password.
You have started the load balancer HTTP server.
10.3 Starting the Node Manager for the HTTP server

1. On the command line, change to /HTTP_domain/bin.
2. Run the following command:
startNodeManager.sh
3. To verify that Node Manager has started, access the load balancer which is available at the following
URL:
http://IP-address:7777/BrowserWeb
4. Log in to the server.
The main page is displayed.
10.4 Accessing the UXP Browser

1. Open the following URL in your web browser:
http://IP_address:7777/Browser
2. Log in to the UXP Browser.
The main page opens.
10.5 Accessing TAFJEE from the Load Balancer

Accessing TAFJEE from the Load Balancer, open the following URL in your web browser:
http://IP_address:7777/TAFJEE
11 Glossary
A
Axis2
Apache Axis2 is a core engine for Web services. Axis2 provides the capability to add Web services interfaces to
Web applications.
BrowserWeb
A Temenos browser, used for accessing the T24 application.
Integration
Communication between two or more systems.
JDK
Java Development Kit
JMS
Java Message Service (JMS) is an application program interface (API) from Sun Microsystems that supports the
formal communication known as messaging between computers in a network.
T24
T24 is Temenos' core banking solution
TAFJ
Temenos Application Framework Java
UXP Browser
The new browser from Temenos, designed to access the T24 application

Stack3 RHEL WL Runbook R17 V1.2 MT PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Stack3 RHEL WL Runbook R17 V1.2 MT PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Stack 3 Red Hat - WebLogic

Runbook for multi-tier installations, V1.2

3 Before you start 15

4 Installing WebLogic sever in a cluster 16

4.7 Configuring all machines to use plain socket 35

5 Configuring TAFJ-T24 in WebLogic cluster in application layer 54

6 Configuring local queues in application layer 59

7 Configuring the foreign JNDI server in web layer 65

8 Deploying and configuring T24 BrowserWeb in web layer 75

9 Deploying and configuring UXP Browser in WebLogic cluster in

10 Installing and configuring HTTP load balancer server 95

1 About this Runbook

1.1 Stacks table

1 . 2 . 1 Sk i l l s and k now l edge

1.0 21 March 2017 Initial version Surender Padakanti

1.1 31 March 2017 Technical author edits Dominik Wietrzak

2.1 Software prerequisites

2 . 1 . 1 Thi r d par t y s oft w ar e

Component Name and version

Java JDK 1.7

Application server Oracle WebLogic 12.1.3.x

Database Oracle Database 12c

SOA suite Oracle Service Bus 12c

Database (XE) Oracle Database Express Edition 11g

IDE JDeveloper 12c

Web services engine Apache Axis2 1.6

TAFJ (TAFJEE) 201612

T24 BrowserWeb 201612

T24 EJB 201612

UXP Browser deployment files

File name Version

2.2 Running prerequisite tasks

1. Download the Xming installation package from http://sourceforge.net/projects/xming/ to your Windows

2 . 2 . 2 Es t abl i s hi ng a c onnec t i on w i t h X 1 1 for w ar di ng enabl ed i n

2 . 2 . 3 Enabl i ng X 1 1 for w ar di ng i n Sec ur eC R T

3. Right-click your connection and then click Properties.

X11 clock appears on your screen.

2 . 2 . 5 Ins t al l i ng J ava D evel opment Ki t on L i nux

4. Create the installation directory for the Java Development Kit:

5. Copy the JDK installation file to the new installation directory:

6. Extract the contents of the JDK installer file:

7. Check if the new jdk1.7.0_79 subdirectory exists: ls -la

8. Delete the redundant JDK installer:

#setting the JAVA_HOME

12. Run another check to verify the JDK location:

3 Before you start

3.1 Supporting documentation

Step number Step details

1☐ Check the version of your operating system.

Run the command cat /etc/redhat-release (cat /etc/system-release on all

2☐ Verify that you can connect to your database.

In order to verify your Database connection, prepare your database connection

3☐ Check your application server.

4 Installing WebLogic sever in a cluster

4 . 1 . 4 L oad bal anc er

4.2 Preparing the installation package

1. Download the WebLogic 12.1.3 generic file (fmw_12.1.3.0.0_wls.jar).

4.3 Installing with the WebLogic installer

The following messages are displayed:

Launcher log file is /tmp/OraInstall2017-01-26_01-36-33PM/launcher2017-01-26_01-36-33PM.log.

Next, Installation Inventory Setup page is displayed.

2. Specify the Inventory Directory and click OK.

3. On the welcome screen, click Next.