Академический Документы
Профессиональный Документы
Культура Документы
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
2 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
3 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
11 Glossary 101
4 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
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.
5 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
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).
6 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
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.
7 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
1.4 History
Version Date Description Author
1.2 7 April 2017 Stack 3 runbook has been split into two books: Dominik Wietrzak
standalone and multi-tier.
8 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
2 Prerequisites
The following chapter describes the technical prerequisites and assumptions for installing and configuring
the RedHat Linux - WebLogic stack.
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
T24 201612
9 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
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.
10 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
5. Click Open.
11 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
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.
12 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
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.
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
13 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
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:
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
14 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
3.2 Checklist
To avoid deployment and configuration problems, complete the following checks.
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
15 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
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.
16 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
4 . 1 . 1 Web l ayer
In the web layer we deployed T24 Browser with a foreign server collocated with web Manager Servers.
17 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
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.
18 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
Procedure
19 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
20 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
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.
21 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
22 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
23 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
9. Click Finish.
The WebLogic installation process completes. Next, you need to create a domain for node managers.
24 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
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.
25 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
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
26 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
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:
27 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
Server Name
AdminServer
Listen Address
All local IP addresses on the machine
Listen port
7001
Tip: The default port value for WebLogic is 7001.
28 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
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.
29 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
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.
30 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
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.
31 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
14. On the Configuration Summary page, review your configuration and click Create.
32 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
33 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
./startWebLogic.sh
Procedure
34 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
2. Enter the user name and password that you specified while you were creating your WebLogic domain:
1. In the Domain Structure on the left, click your domain name, expand Environment and click
Machines.
35 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
36 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
5. Click Save.
6. Follow the same steps for configuring Machine-2 to use a plain socket.
37 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
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
38 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
/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:
/storage2/home/jumpst/Temenos/Middleware/Oracle_Home/user_
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
39 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
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_
projects/domains/mydomain/servers/Server-1/data/nodemanager/startup.properties">
<06-Mar-2017 09:47:52 o'clock GMT> <INFO> <Plain socket listener started on port 5556, host
rhdevblade2.temenosgroup.com
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.
40 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
Procedure
41 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
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.
42 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
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.
43 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
9. Specify the server name, listen address and listen port and click Next.
44 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
45 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
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
46 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
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_
Home/wlserver/../oracle_common/modules/net.sf.antcontrib_1.1.0.0_1-0b3/lib/ant-
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.
47 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
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.
Procedure
48 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
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')
wls:/mydomain/serverConfig> exit()
Exiting WebLogic Scripting Tool.
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_
Home/wlserver/../oracle_common/modules/net.sf.antcontrib_1.1.0.0_1-0b3/lib/ant-
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 -
49 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
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
50 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
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=
<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_
projects/domains/mydomain/servers/Server-2/data/nodemanager/startup.properties">
<Mar 6, 2017 4:50:45 AM EST> <INFO> <mydomain> <Server-2> <Adjusted state of server 'Server-2 '
from FORCE_SHUTTING_DOWN to SHUTDOWN>
<Mar 6, 2017 4:50:45 AM EST> <INFO> <mydomain> <Server-1> <Startup configuration properties
loaded from "/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/servers/Server-1/data/nodemanager/startup.properties">
<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">
<Mar 9, 2017 11:01:17 AM EST> <INFO> <mydomain> <Server-2> <Startup configuration properties
saved to "/t24app1/home/jumpstat/Temenos/Middleware/Oracle_Home/user_
projects/domains/mydomain/servers/Server-2/data/nodemanager/startup.properties">
<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
51 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
'/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.>
3. In Domain Structure, under your domain name, expand Environment and click Servers.
4. In the pane on the right, click the Control tab.
52 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
After a few minutes, both Managed Servers are in the Running state.
53 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
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.
54 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
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
com.temenos.tafj.common.exception.InvalidJMSMessageException
weblogic.application.ModuleException: java.lang.ClassNotFoundException:
com.temenos.tafj.common.exception.InvalidJMSMessageException
weblogic.application.ModuleException: java.lang.ClassNotFoundException:
com.temenos.tafj.logging.LoggerHelper
weblogic.application.ModuleException: java.lang.ClassNotFoundException:
com.temenos.tafj.common.constants.keys.ConstantsKeyAppserver$VALUES_APPSERVER_NAME
weblogic.application.ModuleException: java.lang.ClassNotFoundException:
com.temenos.tafj.jms.IMdbTafjSessionTimeout
An error occurred during activation of changes, please see the log for details.
com.temenos.tafj.common.exception.InvalidJMSMessageException
com.temenos.tafj.common.exception.InvalidJMSMessageException
55 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
<wls:package-name>org.apache.neethi.*</wls:package-name>
Procedure
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.
56 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
5. To upload the TAFJEE file that is provided with the Release, click upload your file(s) and chose file
TAFJJEE_EAR.ear.
57 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
7. Select Target as: Cluster_1 and All servers in the cluster and click Next.
58 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
Tip: Ensure that you have stopped the Managed Server before you create the Local Queue.
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, expand Services.
59 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
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.
60 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
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.
61 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
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.
62 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
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
63 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
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>
64 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
Procedure
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, 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.
65 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
66 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
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.
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, expand Services, then Messages and click JMS
Modules
4. Click New.
67 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
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.
68 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
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.
69 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
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.
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, expand Services, then Messages and click JMS
Modules.
4. Click the Destinations tab.
70 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
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.
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, expand Services, then Messages and click JMS
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
71 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
6. Click Save.
7. To view both BROWSERQueue and BROWSERReplyQueue click the Destinations tab.
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, expand Services, then Messages and click JMS
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.
72 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
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
73 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
74 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
<container-descriptor>
<show-archived-real-path-enabled>true</show-archived-real-path-enabled>
</container-descriptor>
75 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
<session-descriptor>
<persistent-store-type>replicated_if_clustered</persistent-store-type>
</session-descriptor>
2. Log in with the user name and password that you created while creating your WebLogic domain. The
main page opens.
76 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
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.
77 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
7. In Clusters, select Webcluster and All servers in the cluster. Click Next.
8. Click Finish.
78 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
79 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
80 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
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.
81 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
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.
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.
82 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
1. Access the Weblogic console on the server in the application layer. The console is available at
http://ip_address:port/console.
83 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
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.
84 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
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.
85 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
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.
86 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
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>
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
87 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
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.
88 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
6. In Clusters, select Cluster_1 and All servers in the cluster and click Next.
89 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
90 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
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
Procedure
GlobalParameterValue="http://IP-Address:Port/hothouse-iris/Hothouse.svc" Name="IRIS_ROOT"
91 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
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
1. Access the Weblogic console on the server in the application layer. The console is available at
http://ip_address:port/console.
92 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
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.
93 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
6. Select the Webcluster and All Servers in the Cluster and click Next.
94 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
########################
#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">
SetHandler balancer-manager
Order Deny,Allow
Allow from all
</Location>
<Location "/Authenticator">
SetHandler balancer-manager
Order Deny,Allow
Allow from all
</Location>
<Location "/hothouse-iris">
SetHandler balancer-manager
95 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
Order Deny,Allow
Allow from all
</Location>
<Location "/balancer-manager">
SetHandler balancer-manager
Order Deny,Allow
Allow from all
</Location>
## 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"
96 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
97 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
3. To verify that Node Manager has started, access the load balancer which is available at the following
URL:
http://IP-address:7777/BrowserWeb
98 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
99 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
100 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
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
Integration
JDK
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
TAFJ
101 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
UXP Browser
The new browser from Temenos, designed to access the T24 application
102 C rea t ed b y J u m p S t ar t