Sunteți pe pagina 1din 78

Stack 5 True Blue

Customer Runbook 1.0 May 2017

All 17.x releases up to and including R17

C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

Contents
1 About this Runbook 4
1.1 Stacks table 5
1.2 Audience 5
1.2.1 Skills and knowledge 6
1.3 Optional and Advanced tasks 6
1.4 Legal 6
1.5 History 7

2 Introduction 8
3 Prerequisites 9
3.1 JDK 9
3.2 Directory structure 9
Environment variables 11

4 Before you start 12


4.1 Supporting documentation 12
4.2 Check your OS 12
4.3 Check your database 12
4.4 Check your application server 12

5 Installing TAFJ 13
6 Installing T24 19
6.1 Configuring TAFJ T24 20
Example: 20
6.2 Database connection settings 20
Example 20
6.3 Performance enhancement 21
6.4 JDBC drivers 21

7 Sanity check T24 23


7.1 Classic 23
7.2 DBTools 24

2 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

8 Configuring WebSphere 25
8.1 Creating the profile with Profile Management 25
8.1.1 Multiple profiles 26
8.2 Creating the profile with TAFJ scripts 26
8.2.1 Starting the server 27
Accessing the administration console 28
Stopping the server 29

9 Deploying T24 and WebSphere 30


9.1 Configuring TAFJ properties 30
9.2 Running the setup script 31
Example setup script output: 31
9.3 Test database connection 32
9.4 Restarting the application server 35
9.5 Accessing the applications 35

10 Deploying UXP Browser 38


10.1 Resources to deploy 38
10.2 Copy the required resources 38
10.3 Unzip generated.zip 38
10.4 Modify the hothouse-iris.war file 39
10.5 Configuring WebSphere for the UXP Browser 40
10.5.1 Increase Java Heap size 40
10.6 Change JDBC Provider Isolation mode 42
10.7 Set WebSphere environment variables 45
10.8 Add Java properties 49
10.9 Deploying hothouse-iris.war 53
10.9.1 Installing hothouse-iris.war 53
10.9.2 Map shared libraries 56
10.9.3 Change class loading order 59
10.10 Deploying Browser.war 61
10.10.1 Installing Browser.war 61
10.10.2 Map shared libraries 64
10.11 Accessing the UXP Browser 68

Appendix Installing the JDK 70

3 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

1 About this Runbook


The Stack 5 True Blue Runbook describes how to configure TAFJ-T24 on a DB2 database. It also shows you
how to deploy a Temenos browser and access T24 using that browser. This runbook is relevant to all 17.x
releases up to and including R17.

This runbook does not tell you how to install 3rd Party software, such as DB2 or JDK 1.7. For help, see the
relevant vendor's documentation.

4 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

1. 1 Stacks table

1. 2 Audience
This runbook is designed for technical consultants who want to deploy TAFJ-T24 on a WebSphere application
server with a DB2 database.

5 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

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

To use this runbook, you need a basic understanding of TAFJ-T24, WebSphere application servers and the
DB2 database.

1. 3 Optional and Advanced tasks


Some tasks may be marked as either Optional or Advanced in this runbook.

Term Description

Non-mandatory task. You can install and configure your TAFJ-T24 solution
Optional without carrying out this task, but you may choose to do so if it meets your
organization's requirements.

A task carried out by advanced users - those who have advanced knowledge of
Advanced TAFJ-T24 and/or the technology that supports it. Such tasks can be either
mandatory or Optional.

1. 4 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.

6 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

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. 5 History
Version Date Description Author

1.0 May 2017 Initial release of this runbook. Yanxin Zhao

7 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

2 Introduction
This Stack 5 True Blue Runbook describes how to install and configure TAFJ-T24 on an IBM AIX 7.x server
Operating System. The other components of the stack comprise:

l An IBM DB21 11.1 database.


l An IBM WebSphere2 8.5.5.x application server.
l The IBM version of JDK3 - the JDK from Oracle is not valid on an AIX system.

After TAFJ-T24 is installed to the AIX server, the stack is deployed using a WebSphere application server.

1IBM DB2 contains database server products developed by IBM. These products all support the relational model, but in recent years some products have been
extended to support object-relational features and non-relational structures like JSON and XML.
2WebSphere Application Server (WAS) is an IBM web application server product. It is a software framework and middleware that hosts Java based web
applications.
3Java Development Kit

8 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

3 Prerequisites
Before you start to install and confgure the stack, you must have installed all 3rd Party software, including:

l IBM AIX server 7.x OS.


l IBM DB2 11.1 database.
l WebSphere Application Server 8.5.5.x.

The TAFJ1 runtime, T242 libraries and BrowserWeb.war files are available from Distribution for copying into
the Linux server. UXP Browser3 related files are also provided by Distribution - these include the the UXP
Browser folder, hothouse-iris.war and Browser.war. T24 tables are preloaded to the DB2 11.1 database.

3. 1 JDK
IBM provides its own JDK for the AIX system - the Java Software Development Kit (SDK). The JDK from
Oracle is not valid on an AIX system. WebSphere includes an IBM SDK, but you may need to install an SDK
if you're deploying the Classic view.

The required version is the IBM SDK, Java Technology Edition, Version 7 Release 1. To find out how to
install it, see "Installing the JDK".

3. 2 Directory structure
Create the following directory structure on the AIX server:

1. Log onto the server as t24user.

2. Create the following directory structure:

# mkdir –p /u01/Temenos
# mkdir –p /u01/Temenos/T24
# mkdir –p /u01/Temenos/TAFJ

1Temenos Application Framework Java


2T24 is Temenos' core banking solution
3The new browser from Temenos, designed to access the T24 application

9 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

# mkdir –p /u01/Temenos/Install
# mkdir –p /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer

Directory Description

Temenos/Install The Install directory contains the installers for setting up TAFJ-T24.

The 3rdParty directory contains the installed 3rdParty software, such as


Temenos/3rdParty
WebSphere.

Temenos/TAFJ The TAFJ directory contains the TAFJ runtime libraries.

Temenos/T24 The T24 directory contains the T24 related libraries.

10 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

Environment variables

To set the environment variables:

1. Edit bash profile file.

2. Enter the following environment variables.

##############################################
# Temenos Home
#
export TEMENOS_HOME=/u01/Temenos
echo "TEMENOS_HOME="$TEMENOS_HOME

##############################################
# TAFJ Home
#
export TAFJ_HOME=$TEMENOS_HOME/TAFJ
echo "TAFJ_HOME="$TAFJ_HOME
export PATH=$TAFJ_HOME/bin:$PATH
##############################################
# T24 Home
#
export T24_HOME=$TEMENOS_HOME/T24
echo "T24_HOME="$T24_HOME
################################################
# WebSphere Home
#
export WAS_HOME=$TEMENOS_HOME/3rdParty/As/IBM/WebSphere8.5.5/AppServer
echo "WAS_HOME="$WAS_HOME
################################################
cd $TEMENOS_HOME

11 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

4 Before you start


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

This runbook does not tell you how to install 3rd Party software, such as DB2 or JDK 1.7. For help, see the
relevant vendor's documentation.

4. 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.

4. 2 Check your OS
To check if the required OS version is used, use the oslevel command to display the AIX version, release,
Technology Level (TL), Service Pack (SP) and build date. For example, this output shows AIX V7.2
Technology Level 0, Service Pack 1, built in the 43rd week of 2015 :

# oslevel -s
7200-00-01-1543

4. 3 Check your database


Check that you can connect to your DB2 11.1 database.

4. 4 Check your application server


After you've installed WebSphere, check that it starts without any errors, without any war or ear files
deployed.

12 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

5 Installing TAFJ
Before you begin, you need the following TAFJ installation package from Temenos: TAFJ.xx.xxx.0.tar.gz

To install TAFJ:

1. Log onto all servers in the Application layer with the t24user.

2. FTP the installation package TAFJ.xx.xxx.0.tar.gz to $TEMENOS_HOME/Install.

3. In $TEMENOS_HOME/Install, create a folder called tafjinst:

# mkdir -p $TEMENOS_HOME/Install/tafjinst

4. Unzip the files:

# gunzip $TEMENOS_HOME/Install/TAFJ.DEV.201612.0.tar.gz

5. Untar the files to the $TEMENOS_HOME/Install/tafjinst folder:

# (cd $TEMENOS_HOME/Install/tafjinst && tar -xvf $TEMENOS_HOME/Install/TAFJ.R16.SP5.0.tar)


x .
x ./Setup_TAFJ.DEV.201612.0.sh, 171 bytes, 1 media blocks.
x ./TAFJ.DEV.201612.0.jar, 234636168 bytes, 458274 media blocks.
x ./Patch_TAFJ.DEV.201612.0.sh, 175 bytes, 1 media blocks.
x ./Patch_TAFJ.DEV.201612.0.bat, 184 bytes, 1 media blocks.
x ./Setup_TAFJ.DEV.201612.0.bat, 180 bytes, 1 media blocks.

6. TAFJ will be located at $TEMENOS_HOME/TAFJ, which is $TAFJ_HOME. To install TAFJ:

a. From $TEMENOS_HOME/Install/tafjinst, execute the file setup command:


Setup_TAFJ.DEV.201612.0.sh

b. During the install, change the default installation directory to the full path of $TAFJ_HOME, when
prompted for the install directory:

13 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

# cd $TEMENOS_HOME/Install/tafjinst
# chmod 755 *
# echo $TAFJ_HOME
# . ./Setup_TAFJ.DEV.201612.0.sh

-----------------
YAJI v R16
WARNING : JDK 1.7 or above required
Starting setup...
========================================================
. Welcome to the Installation program of TAFJ .
. This setup will install the necessary libraries to .
. compile and run BASIC programs as well as some .
. additional tools and Eclipse plug-ins. .
. Note that nothing will be modified outside of the .
. directory you will specify for the installation. .
. To fully uninstall it, just delete the directory. .
========================================================

Press ENTER to continue.

========================================================
Please enter the install Directory.
default :
‘/u01/Temenos/Install/tafjinst/TAFJ’
/u01/Temenos/Install/tafjinst/TAFJ

========================================================
Please enter the eclipse home directory (Optional).
When provided, a tafj.link, used to resolve tafj eclipse
plugins will be created under ECLIPSE_HOME/dropins
If this file already exist it will be replaced
default : '/storage/yanxin/R1612_tafj/Temenos/TAFJ/conf'
'/u01/Temenos/TAFJ/conf' doesn't exist. Create (y/n) ?
y
Extracting META-INF/META-INF/MANIFEST.MFCodeCoverage/ (dir)
JMSInjector/ (dir)
PROC/ (dir)
Regression/ (dir)
RulesEngine/ (dir)
TAFJSessionMonitor/ (dir)
appserver/ (dir)

14 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

appserver/MQ/ (dir)
appserver/basic/ (dir)
appserver/basic/TAFJ.BP/ (dir)
appserver/jboss/ (dir)
appserver/jboss/jboss6eap/ (dir)
appserver/jboss/jboss6eap/jboss-cli/ (dir)
appserver/jboss/jboss6eap/modules/ (dir)
appserver/jboss/jboss6eap/modules/com/ (dir)

appserver/jboss/jboss6eap/modules/com/temenos/ (dir)
appserver/jboss/jboss6eap/modules/com/temenos/t24/ (dir)
appserver/jboss/jboss6eap/modules/com/temenos/tafj/ (dir)



ECLIPSE_HOME: /u01/Temenos/TAFJ/conf
tafj.link created: /u01/Temenos/TAFJ/conf
===========================================================
. Thank you for having installed TAFJ .
. *** IMPORTANT *** .
. Please make sure that you have the environment variable .
. JAVA_HOME set to a JDK 7 or above. .
===========================================================

Press ENTER to terminate.

7. Change the permissions on the $TAFJ_HOME\bin to execute:

# chmod 755 $TAFJ_HOME/bin/*

8. Check the TAFJ installation:

a. Close your session and log in again:

Last login: Tue Feb 14 22:01:50 CET 2017 on ssh from 10.44.245.119
TEMENOS_HOME=/storage/auser/R1612_tafj/Temenos
JAVA_HOME=/usr/java71_64
java version "1.7.0"
Java(TM) SE Runtime Environment (build pap6470_27-20131115_04)

15 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

IBM J9 VM (build 2.7, JRE 1.7.0 AIX ppc64-64 Compressed References 20131114_175264 (JIT
enabled, AOT enabled)
J9VM - R27_Java727_GA_20131114_0833_B175264
JIT - tr.r13.java_20131113_50523
GC - R27_Java727_GA_20131114_0833_B175264_CMPRSS
J9CL - 20131114_175264)
JCL - 20131113_01 based on Oracle 7u45-b18
TAFJ_HOME=/u01/Temenos/TAFJ
T24_HOME=/u01/Temenos/T24
WAS_HOME=/u01/Temenos/3rdParty/As/WAS/WebSphere8.5.5/AppServer
#

b. Run a diagnostic for TAFJ:

# tDiag
__________________________________________________________________

Home : '/u01/Temenos/TAFJ'
Conf directory : '/u01/Temenos/TAFJ/conf'
Log directory : '/u01/Temenos/TAFJ/log
Log directory T24 : '/u01/Temenos/TAFJ/log_T24
Version : R16_SP5
__________________________________________________________________

java.home : /usr/java71_64/jre
java.vendor : IBM Corporation
java.version : 1.7.0
os.arch : ppc64
os.name : AIX
HostName : gvalpar03
IP Address : 10.42.4.202
Runtime : Double Byte SysSeparator
__________________________________________________________________

Default Project : 'tafj'


__________________________________________________________________
Common validation:
Common validation completed - All fine
__________________________________________________________________

- Project : 'tafj'
Basic source : /u01/Temenos/TAFJ/samples/basic

16 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

Java src dir : /u01/Temenos/TAFJ/data/tafj/java


Java classes dir : /u01/Temenos/TAFJ/data/tafj/classes
Update dir : /u01/Temenos/TAFJ/updates
------------------------------------------------------------------
Java default package : com.temenos.t24
------------------------------------------------------------------
DataBase URL :
DataBase user :
------------------------------------------------------------------
Locking mode : JDBC
Locking name :
------------------------------------------------------------------
Current dir : /u01/Temenos/TAFJ/UD
Como dir : /u01/Temenos/TAFJ/UD/&COMO&
Hold dir : /u01/Temenos/TAFJ/UD/&HOLD&
UD encoding : UTF-8
------------------------------------------------------------------
Timezone :
Local : en_US
Debug enabled : true
------------------------------------------------------------------
JMS logger enabled : false
Logger API enabled : true
TEC disabled : false
------------------------------------------------------------------
Session monitor enabled : true
Session monitor host : localhost
Session monitor port : 8377
__________________________________________________________________
Project validation:
TAFJ Java Functions Version in DB : NOT FOUND
TAFJ Java Functions Version in File : PB201510 08/18/2015
There is a mismatch between the java stored functions version available in the
runtime and the one loaded in the database, make sure you are using the latest version.
To update the java stored functions, please follow "Load stored functions
instruction" in the TAFJ DB documentation related to your database. No duplicated classes
found.
__________________________________________________________________

c. Run the tVersion application:

17 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

# tVersion
<ivy-module version="1.0">
<info organisation="Temenos" module="TAFJ" branch="R17_ALL"/>
<dependencies>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJCache" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJClient" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJCommon" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJCompiler" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJCore" rev="2" />
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJDBImport" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJLocking" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJLogging" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJPackager" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJTelnetD" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJVersion" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_TAFJBASIC" rev="0"/>
<dependency org="Temenos" branch="DEV_201612" name="FJ_tComponentFramework" rev="0"/>
</dependencies>

TAFJ has now been installed.

18 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

6 Installing T24
Before you start, you'll need the MB.R16.000.DB2XX.UNIX.TAFJR16.20170930.bnk.tar.gz installation
package from Distribution.

To install T24:

1. FTP the installation package MB.R16.000.DB2XX.UNIX.TAFJR16.20170930.bnk.tar.gz to $TEMENOS_


HOME/Install.

2. In $TEMENOS_HOME/Install create a T24 folder:

# mkdir -p $TEMENOS_HOME/T24

3. Unzip the files:

# gunzip $TEMENOS_HOME/Install/MB.R16.000.DB2XX.UNIX.TAFJR16.20170930.bnk.tar.gz

4. Untar the files:

# tar –xvf $TEMENOS_HOME/Install/MB.R16.000.DB2XX.UNIX.TAFJR16.20170930.bnk.tar

5. Check that the files were extracted to the bnk folder:

# ls bnk
Extensions
UD
lib
t24lib

6. Move the extracted bnk folder to the T24 folder:

# mv $TEMENOS_HOME/Install/bnk $TEMENOS_HOME/T24
# ls $TEMENOS_HOME/T24
bnk

T24 has now been installed.

19 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

6. 1 Configuring TAFJ T24


You'll need to specify values for properties in the tafj.properties file, which is stored in $TAFJ_
HOME/conf.

temn.tafj.directory.precompile Specify where you store all T24 libraries .

Example:

# Specify the Precompile classes directories


# You can specify multiple directory, separated by
# ':' or ';' (eg /home/t24/lib;/home/t24/FT)
#
temn.tafj.directory.precompile = /u01/Temenos/T24/bnk/t24lib

6. 2 Database connection settings

Specify the URL to connect to your RDMS. You can ask your database
temn.tafj.jdbc.url
administrator about this URL.

Specify the driver to connect to your RDMS. You can ask your database
temn.tafj.jdbc.driver
administrator about the driver to use.

temn.tafj.jdbc.username and Specify the user name and password to connect to the database. Ask your
temn.tafj.jdbc.password database administrator for them.

Example

#********************************************************************
#
# Database setup
#
#********************************************************************

# URL that describes database connection,


# ex. oracle: jdbc:oracle:thin:@<host_or_ip>:1521:<db_name>
# ex. db2: jdbc:db2://<host_or_ip>:50000/<db_name>
# ex. ms-sql: jdbc:sqlserver://<host_or_ip>:1433;databaseName=<db_
name>;integratedSecurity=true
# ex. H2: jdbc:h2:tcp://<host_or_ip>/<db_name>
# ex. H2(Embedded): jdbc:h2:<path_to_my_db>
#
temn.tafj.jdbc.url = jdbc:db2://< host_or_ip>:50000/<db_name>

20 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

# Class that describes the specific Driver for a database,


# ex. oracle: oracle.jdbc.driver.OracleDriver
# ex. db2: com.ibm.db2.jcc.DB2Driver
# ex. ms-sql: com.microsoft.sqlserver.jdbc.SQLServerDriver
# ex. H2: org.h2.Driver

#
temn.tafj.jdbc.driver = com.ibm.db2.jcc.DB2Driver
temn.tafj.jdbc.username = <user name>
temn.tafj.jdbc.password = <password>

6. 3 Performance enhancement
For performance reasons, change the value of the keys temn.tafj.jdbc.write.use.merge and tem-
n.tafj.jdbc.write.use.merge.no.xml to false.

#********************************************************************
#
# Database Specific setup
#
#********************************************************************

# Use the MERGE statement instead of UPDATE/INSERT for XML Schema


#
temn.tafj.jdbc.write.use.merge = false

# Use the MERGE statement instead of UPDATE/INSERT for NO XML Schema and NO XML Schema work
#
temn.tafj.jdbc.write = false

6. 4 JDBC drivers
You need to copy the correct JDBC driver into the $TAFJ_HOME/ext directory. This directory is automatically
added to the TAFJ classpath.

JDBC drivers are provided in the $TAFJ_HOME/dbdrivers directory. The jars under dbdrivers folder can be
used as reference - ideally, the JDBC drivers should match the database version. You might need to find the
correct version of the jars from your database administrator, for example:

l ${DB2_HOME}/sqllib/java/db2jcc*.jar
l ${DB2_HOME}/sqllib/java/db2jcc_license*.jar

21 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

To ensure you use the correct JDBC driver:

1. Create the $TAFJ_HOME/ext/db2_v11.1 folder.

2. Copy the db2jcc*.jar and db2jcc_license*.jar files to the newly created folder.

22 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

7 Sanity check T24


The following chapter describes how to check T24, after you've installed and configured it for standalone
mode.

7. 1 Classic
To check T24 in Classic view:

1. Change to $TAFJ_HOME/bin.

2. Execute tRun EX.

3. Log into the application using a valid T24 username and password.

The home screen is displayed:

GLOBUS Rev. 201612 SIGN.ON Copyright (c) Temenos Systems Ltd 2017
------------------------------------------------------------------------------
$$$$$$$$$$ $ $ $ $$ $$$$$ $$$$$ $$$ $$$$$$$$$$$$$$$$$$$$
$$$$$$$$$$$$$$$$$$ $$$ $$$ $ $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$$$$$$$$$$$$$$ $$ $$ $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$ $$$$$$$$ $$$$ $ $$ $$$$$$$$$$$$$$$$$$$$$$ $$
$$$$$$$$$$$$$$$ $$ $$$$$$$$$$$$$$$$$$$$$$$$$$$ $
$$$$$$$$$$$$ $ $$$$$$$$$$$$$$$$$$$$$$$$$$$$
$$$$$$$$$$$ $$ $$$$ $$ $$$$$$$$$$$$$$$ $
$$$$$$$$$ $$$$ $$$$$$$$$$$$$$$$$ $ $
$$$ $$$$$$$$$$$$$$$$$$$$$$$$$$$
$$$$ $$$$$$$$$$$$$ $$ $$$ $
$$$$$$ $$$$$$$$$$$$ $ $
$$$$$$$$$ $$$$$$ $ $$ $$$
$$$$$$$ $$$$$$ $ $$$$$
$$$$$ $$$$ $ $$$$$$$$
$$$ $$ $$ $$$ $
$$ $
------------------------------------------------------------------------------
21 MAR 2017 13:17:42 USER [14593,]
ACTION

23 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

7. 2 DBTools
To access DBTools, you need to create a user, using the tUserMgnt utility. You use the same username and
password to log into DBTools.

24 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

8 Configuring WebSphere
This chapter assumes that the IBM WebSphere 8.5 Application Server has already been installed (see
"Prerequisites").

The following sections describe how to configure IBM WebSphere. In this scenario, the application server is
configured as a standalone server and all T24 components are installed on one instance of the WebSphere
server.

The application server has four roles:

l Administration server
l Application server
l JMS server
l Web server

8. 1 Creating the profile with Profile Management


The WebSphere profile is your application server environment. You need to configure this environment
before you deploy the stack.

You can use GUI tools or command line to create a new WebSphere Profile. Before you begin, the following is
the suggested nomenclature for profile naming.

Parameter Value Comments


T24

product_name AML

TAP

App Application layer

Business_role Web Web layer or presentation layer

JMS Broker layer

25 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

Parameter Value Comments


Std Standalone

Mng Managed

type Clu Cluster

Mgr Manager

Srv Server

number From 00 to 99

8 . 1 . 1 M ul t i pl e pr ofi l es

You can create a standalone server for T24 in the application layer. The profile name will be T24AppStd01.
You can have multiple profiles on one server, for example you can have profiles T24AppSrv01,
T24AppStd01,T24AppMgr01, and T24AppMng01 on the same machine.

8. 2 Creating the profile with TAFJ scripts


To create the WebSphere profile with TAFJ scripts:

1. Log on to the target server in the application layer as t24user.

2. Open the file setUpEnv.sh.

# vi $TAFJ_HOME/appserver/was/setUpEnv.sh

3. Provide the values for PROFILE_NAME, DMGR_USER and DMGR_PASSWORD

# *********************************
# WAS
# *********************************
export WAS_HOME=/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer

export HOST_NAME=
export PROFILE_NAME=T24AppStd01

26 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

export NODE_NAME=$PROFILE_NAME'Node01'
export CELL_NAME=$NODE_NAME'Cell'
export SERVER_NAME=

export DMGR_USER=admin
export DMGR_PASSWORD=admin
export DMGR_HOST=
export DMGR_PORT=8879

4. Save the changes and quit the editor.

5. Create the standalone profile.

# . ./createStandalone.sh
INSTCONFSUCCESS: Success: Profile T24AppStd01 now exists. Please consult
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppStd01/logs/AboutThisProfile.txt for more
information about this profile.

8 . 2 . 1 St ar t i ng t he s er ver

To start the server:

1. Log on to the target server in the application layer as t24user.

2. Start the T24AppStd01 application

# echo $WAS_HOME
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer
#
# $WAS_HOME/bin/startServer.sh T24AppStd01
ADMU0116I: Tool information is being logged in file
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppStd01/logs/
T24AppStd01/startServer.log
ADMU0128I: Starting tool with the T24AppStd01 profile
ADMU3100I: Reading configuration for server: T24AppStd01
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server T24AppStd01 open for e-business; process id is 10420582

3. To determine the port of the instance, check the file AboutThisProfile.txt that is in the log folder of
the profile.

27 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

# cat $WAS_HOME/profiles/T24AppStd01/logs/AboutThisProfile.txt

Application server environment to create: Application server


Location: /u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppStd01
Disk space required: 200 MB
Profile name: T24AppStd01
Make this profile the default: True
Node name: T24AppStd01Node01
Host name: gvalpar03
Enable administrative security (recommended): True
Administrative console port: 9060
Administrative console secure port: 9043
HTTP transport port: 9080
HTTPS transport port: 9443
Bootstrap port: 2809
SOAP connector port: 8880
Run application server as a service: False
Create a Web server definition: False
Performance tuning setting: Standard

Accessing the administration console

To access the administration console:

1. Open the following URL in your web browser:

http://server_name:9060/ibm/console

28 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

2. Log in with the user admin and password admin. The WebSphere Integrated Solutions Console opens.

Stopping the server

To stop the server:

1. Log on to the server as t24user.

2. Stop the server.

# $WAS_HOME/bin/stopServer.sh T24AppStd01 -username admin -password admin


ADMU0116I: Tool information is being logged in file
/u01/Temenos/3rdParty/As/IBM/WebSphere8.5.5/AppServer/profiles/T24AppStd01/logs/T24AppStd01/sto
pServer.log
ADMU0128I: Starting tool with the T24AppStd01 profile
ADMU3100I: Reading configuration for server: T24AppStd01
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server T24AppStd01 stop completed.

29 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

9 Deploying T24 and WebSphere


9. 1 Configuring TAFJ properties
To configure TAFJ properties:

1. Log on to the target server in the Application layer as t24user.

2. Open the file setUpEnv.sh in a text editor.

# vi $TAFJ_HOME/appserver/was/jython/tafj.py

3. Provide the parameters, save the changes and exit the editor.

############################################################
# Node details
#
server_name="T24AppStd01"
node_name=server_name+"Node01"
cell_name=node_name+"Cell"
cluster_name=""

#
############################################################
# JVM param
# -Xms and -Xmx of the JVM.
min_mem="1024"
max_mem="1024"
#
############################################################
# Path details
# i.e [/u01/Temenos/TAFJ] or [C:/Temenos/TAFJ]
tafjHome="/u01/Temenos/TAFJ"
# i.e [/u01/Temenos/T24] or [C:/Temenos/T24]
# will add <t24Home>/Lib/LocalDev/*;<t24Home>/Lib/GPack/*;
#
<t24Home>/Lib/T24Lib/*;<t24Home>/Lib/T24Email/*;<t24Home>/Lib/T24Sms/*;<t24Home>/Lib/RepGen/*;<t24Ho
me>/Lib/RulesEngine/*;
t24Home="/u01/Temenos/T24"
t24LocalDev=""

#
############################################################
# database details
#
# 1. replace the x by the version
# 2. The password have to be encrypted
#
# driver = [oracle11g,oracle-12c,db2_v10.x,h2-1.x.x]
dbDriver="db2_v11.1"
dbHostName="10.xx.xxx.xxx"
dbPort="50000"
dbName="<Your DB name>"

30 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

dbUser="<user name>"
dbPwd="<password>"
dbDriverType="4"

############################################################
# Read only database details
#
# 1. replace the x by the version
# 2. The password have to be encrypted
#
dbROHostName=""
dbROPort=""
dbROdbName=""
dbROdbUser=""
dbROdbPwd=""
#
############################################################
# MQ Details details
#
# DO NOT PUT "localhost" but the IP for MQ!
mqManager="MQT24"
mqServerName=""
mqPort="1414"
mqChannel="T24Channel"
############################################################
# Browser details
#
# path of your BrowserWar file
browserWebHome="/u01/Temenos/Install/deployment"

4. Check that the WebSphere server is running.

9. 2 Running the setup script


To run the setup script:

# cd $TAFJ_HOME/appserver/was/jython
# ./T24Setup.sh T24AppStd01 admin admin

Example setup script output:

# ./T24Setup.sh T24AppStd01 admin admin


WASX7209I: Connected to process "T24AppStd01" on node T24AppStd01Node01 using SOAP connector; The
type of process is: UnManagedProcess
---------------------------------------------------------------------
Start T24/TAFJ configuration in WebSphere
---------------------------------------------------------------------
Server Environment
...

...

31 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

...

...

Script15b43699419/workspace/cells/T24AppStd01Node01Cell/applications/BrowserWeb_war.ear/BrowserWeb_
war.ear
ADMA5005I: The application BrowserWeb_war is configured in the WebSphere Application Server
repository.
SECJ0400I: Successfully updated the application BrowserWeb_war with the appContextIDForSecurity
information.
ADMA5005I: The application BrowserWeb_war is configured in the WebSphere Application Server
repository.
ADMA5005I: The application BrowserWeb_war is configured in the WebSphere Application Server
repository.
ADMA5113I: Activation plan created successfully.
ADMA5011I: The cleanup of the temp directory for application BrowserWeb_war is complete.
ADMA5013I: Application BrowserWeb_war installed successfully.
BrowserWeb deployed
---------------------------------------------------------------------
T24/TAFJ configuration in WebSphere is done !
---------------------------------------------------------------------

9. 3 Test database connection


To test the database connection:

1. Open the WebSphere Application Server console in your web browser by going to:

http://<Your IP Address>:9060/ibm/console

2. Log on to the console as user admin with password admin.

3. To test the connection:

a. In the left navigation menu, click Expand Resources.


b. Select Data sources > Check TAFJ XA DB2 Data source and TAFJ NON-XA DB2 Data source.
c. Click Test connection.

32 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

4. Check that both connections were successful.

5. If a connection is not successful:

33 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

a. Click the Data source (for example, TAFJ XA DB2 Data Source).

b. Click JAAS - J2C authentication data > T24AppStd01Node01/T24 database.

c. Provide the new password. Click Apply and OK.

34 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

d. Test connection again to verify the changes.

e. Save your changes.

9. 4 Restarting the application server


To restart the application server:

1. Log on to the application server as t24user.

2. Stop the server.

# $WAS_HOME/bin/stopServer.sh T24AppStd01 -username admin -password admin

3. Start the server.

# $WAS_HOME/bin/startServer.sh T24AppStd01

9. 5 Accessing the applications


To access the applications:

1. To access the TAFJEE application, open the following URL in your web browser:

http://<YOUR IP ADDRESS>:9080/TAFJEE/

35 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

2. To access the BrowserWeb application, open the following URL in your web browser:

http://<YOUR IP ADDRESS>:9080/BrowserWeb

36 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

37 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

10 Deploying UXP Browser


10. 1 Resources to deploy
You need to deploy the following resources for the UXP Browser:

l hothouse-iris.war
l Browser.war

l generated.zip (for example, generated-201612.3.zip)

10. 2 Copy the required resources


To copy the required resources:

1. Create a folder to store the required files (listed above).

# mkdir $TEMENOS_HOME/Install/UXP-Browser

2. Copy the three files listed above into the folder, then list the folder.

# cd $TEMENOS_HOME/Install/UXP-Browser
# ls -a | cat
.
..
Browser.war
hothouse-iris.war
generated-201612.3.zip

10. 3 Unzip generated.zip


To unzip generated.zip:

1. Unzip the generated.zip file.

# unzip generated-201612.3.zip

2. The generated and manual directories should now be present within UXP-Browser folder. To check,

38 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

list the folder.

# cd $TEMENOS_HOME/Install/UXP-Browser
# ls -a | cat
.
..
Browser.war
hothouse-iris.war
generated
generated-201612.3.zip
manual

10. 4 Modify the hothouse-iris.war file


To modify the hothouse-iris.war file:

1. Unpack hothouse-iris.war into a temporary directory.

# cd $TEMENOS_HOME/Install/UXP-Browser
# mkdir tmp && cd tmp
# jar xf ../hothouse-iris.war

2. In WEB-INF, edit the web.xml.

# vi WEB-INF/web.xml

3. Remove the following block from the file:

<filter>
<filter-name>gzip-output</filter-name>
<filter-class>filter.gzip.GZIPFilter</filter-class>
</filter>

<filter-mapping>
<filter-name>gzip-output</filter-name>
<servlet-name>IRIS</servlet-name>
</filter-mapping>

39 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

4. Repack hothouse-iris.war and replace the original hothouse-iris.war.

# cd $TEMENOS_HOME/Install/UXP-Browser/tmp
# jar cvf hothouse-iris.war *
# cp hothouse-iris.war ../
# cd ..
# rm -rf $TEMENOS_HOME/Install/UXP-Browser/tmp

10. 5 Configuring WebSphere for the UXP Browser

1 0 . 5 . 1 Inc r eas e J ava H eap s i z e

The UXP Browser requires more JVM memory.

To increase the Java Heap size:

1. Open the WebSphere Application Server console in your web browser by going to the following
location:

http://<Your IP Address>:9060/ibm/console

2. Log on to the console as user admin with password admin.

3. Go to Servers > Server Types > WebSphere application servers. In Application servers, click
T24AppStd01.

40 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

4. 4. Go to Process definition > Java Virtual Machine. Increase Maximum heap size from 1024 to be
4096.

5. 5. Click Apply and Save the configuration.

41 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

10. 6 Change JDBC Provider Isolation mode


To change JDBC Provider Isolation mode:

1. In the WebSphere admin console, select JDBC providers > T24 NON-XA DB2 JDBC Driver.

2. Check that the Isolate this resource provider checkbox is not selected. Click Apply and OK.

42 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

3. Save the changes.

4. Click T24 XA DB2 JDBC Driver.

43 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

5. Ensure the Isolate this resource provider checkbox is not selected. Click Apply and then OK.

44 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

6. Save the changes.

10. 7 Set WebSphere environment variables


You need to add the following environment variables:

Environment variable Path


UXPBROWSER /u01/Temenos/Install/UXP-Browser

GENERATED ${UXPBROWSER}/generated

MANUAL ${UXPBROWSER}/manual

To set the WebSphere environment variables:

45 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

1. In the WebSphere admin console:

a. Go to Environment > WebSphere variables.

b. From the dropdown menu select Node=T24AppStd01Node01, Server=T24AppStd01.

In this example, DB2UNIVERSAL_JDBC_DRIVER_PATH and DB2UNIVERSAL_JDBC_DRIVER_


NAMEPATH uses libraries from the dbdrivers folder. However, you can choose the ext
folder instead, if the ext folder contains the right jdbc jars.

2. Click New.

46 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

3. Add the UXPBROWSER variable.

4. Add the GENERATED variable.

47 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

5. Add the MANUAL variable.

6. Save the changes.

48 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

7. Check the newly added environment variables.

10. 8 Add Java properties


To add Java properties:

49 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

1. In the WebSphere admin console, go to Application servers > T24AppStd01 > Process definition >
Java Virtual Machine. Click Custom properties.

2. Click New.

50 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

3. On the New property page, add the following name value pairs:

Name com.ibm.websphere.jaxrs.server.DisableIBMJAXRSEngine

Value true

Name com.edgeipk.librarypath

Value ${MANUAL}/edge,${GENERATED}/edge

Name com.temenos.interaction.config.dir

Value ${GENERATED}/iris

51 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

Name override.IRIS_MAP

${MANUAL}/HrefComponentManualMap.properties,${GENERATED}
Value
/edge/data/HrefComponentMap.properties

Name override.IRIS_ROOT

Value http://localhost:9080/hothouse-iris/Hothouse.svc

4. Check the newly added Java property values. Click Save.

52 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

10. 9 Deploying hothouse-iris.war

1 0 . 9 . 1 Ins t al l i ng hot hous e- i r i s . w ar

To install hothouse-iris.war:

53 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

1. In the WebSphere admin console, select WebSphere enterprise applications > Install.

2. Select Remote file system and browse to the location of the hothouse-iris.war file. Click Next.

3. Choose Fast Path install. Click Next.

54 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

4. Click Next.

5. Click Next through the rest of the wizard and click Finish.

55 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

6. Click Save.

1 0 . 9 . 2 M ap s har ed l i br ar i es

To map the shared libraries:

56 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

1. In the WebSphere admin console, click the hothouse-irs.war application.

2. Click Shared library references.

3. Select hothouse-iris.war then click Reference shared libararies.

57 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

4. Move T24_libraries and TAFJ_libraries to the Selected box.

5. Click OK.

58 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

6. Check your changes.

7. Save your changes.

1 0 . 9 . 3 C hange c l as s l oadi ng or der

To change the class loading order:

1. In the WebSphere admin console, go to Enterprise Applications > hothouse-iris_war. Click Manage
Modules.

59 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

2. Select HothouseIRIS then click OK.

3. Change the class load order to Classes loaded with local class loader first (parent last).

60 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

10. 10 Deploying Browser.war

1 0 . 1 0 . 1 Ins t al l i ng B r ow s er . w ar

To install Browser.war:

1. In the WebSphere admin console, select WebSphere enterprise applications > Install.

2. Select Remote file system and browse to the location of the Browser.war file. Click Next.

61 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

3. Choose Fast Path install. Click Next.

4. Click Next through the rest of the wizard and click Finish.

62 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

5. Click Save.

63 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

1 0 . 1 0 . 2 M ap s har ed l i br ar i es

To map the shared libraries:

64 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

1. In the WebSphere admin console, click the Browser.war application.

2. Click Shared library references.

65 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

3. Select Browser.war then click Reference shared libararies.

4. Move T24_libraries and TAFJ_libraries to the Selected box.

66 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

5. Click OK.

6. Check your changes.

67 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

7. Save your changes.

10. 11 Accessing the UXP Browser


To access the UXP Browser:

1. Open the following URL in your web browser:

http://<Your IP Address>:9080/Browser/servletcontroller

68 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

2. Enter your username and password. The UXP Browser interface is displayed.

69 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

Appendix Installing the JDK


IBM provides its own JDK for the AIX system - the Java Software Development Kit (SDK). The JDK from
Oracle is not valid on an AIX system. WebSphere includes an IBM SDK, but you may need to install an
SDK if you're deploying the Classic view.

Check the Java installation

Before you download the JDK / SDK from IBM, check if you need to do so - you may already have the right
version of Java installed. Run the following command - highlighted in red - to see which Java filesets are
installed.

# $ lslpp -l | grep Java


Java7_64.docs 7.0.0.320 COMMITTED Java SDK 64-bit Docs
Java7_64.jclsource 7.0.0.370 COMMITTED Java SDK 64-bit Java Class
Java7_64.jre 7.0.0.370 COMMITTED Java SDK 64-bit Java Runtime
Java7_64.samples.demo 7.0.0.370 COMMITTED Java SDK 64-bit Demo Samples
Java7_64.samples.jmx 7.0.0.370 COMMITTED Java SDK 64-bit JMX and other
Java7_64.samples.jnlp 7.0.0.370 COMMITTED Java SDK 64-bit JNLP Samples
Java7_64.sampsource 7.0.0.370 COMMITTED Java SDK 64-bit Source Files
Java7_64.sdk 7.0.0.370 COMMITTED Java SDK 64-bit Development
Java7_64.jre 7.0.0.370 COMMITTED Java SDK 64-bit Java Runtime

Installing the IBM JDK

If the required version of JDK is not installed, then you need to install it.

To install the JDK:

1. Download the JDK from the IBM website. We need IBM SDK, Java Technology Edition, Version 7
Release 1. You'll need to register for an IBM ID to perform the download (it's free).

Go to: https://www.ibm.com/developerworks/java/jdk/aix/service.html

For FAQs, see: https://www.ibm.com/developerworks/java/jdk/aix/faqs.html

70 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

2. Download the following two files - highlighted in red in the example - to a temporary folder:

l Java7r1_64.jre.tar.gz

l Java7r1_64.sdk.tar.gz

3. Unzip the two files:

# gunzip Java7r1_64.jre.tar.gz
# gunzip Java7r1_64.sdk.tar.gz
#
# tar -xvf Java7r1_64.jre.tar
x Java71_64.jre, 173418496 bytes, 338708 media blocks.
#
# tar -xvf Java7r1_64.sdk.tar
x Java71_64.sdk, 15676416 bytes, 30618 media blocks.

4. Login as root user.

5. Install the JRE:

71 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

a. Enter the smitty command:

smitty

b. Select Sofware Installation and Maintenance and press Enter.

System Management

Move cursor to desired item and press Enter.


Software Installation and Maintenance
Software License Management
Manage Editions
Devices
System Storage Management (Physical & Logical Storage)
Security & Users
Communications Applications and Services

c. Select Install and Update Software and press Enter.

Software Installation and Maintenance

Move cursor to desired item and press Enter.


Install and Update Software
List Software and Related Information
Software Maintenance and Utilities
Software Service Management
Relocatable Software Installation and Maintenance
Network Installation Management
EZ NIM (Easy NIM Tool)
System Workload Partition Software Maintenance
System Backup Manager
Alternate Disk Installation
EFIX Management
Thin Server Maintenance

d. Select Install Software and press Enter.

Install and Update Software

Move cursor to desired item and press Enter.

72 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

Install Software
Update Installed Software to Latest Level (Update All)
Update Installed Software to Latest Level (Live Update)
Install Software Bundle
Update Software by Fix (APAR)
Install and Update from ALL Available Software

e. The INPUT device / directory value is [temporary folder]/Java71_64.jre. Accept the new
license agreements by selecting yes.

Press Enter.

Install Software

Type or select values in entry fields.


Press Enter AFTER making all desired changes.

[Entry Fields]
* INPUT device / directory for software
/tmp/download/install_jdk/Java71_64.jre
* SOFTWARE to install [_all_latest]
+
PREVIEW only? (install operation will NOT occur) no
+
COMMIT software updates? yes
+
SAVE replaced files? no
+
AUTOMATICALLY install requisite software? yes
+
EXTEND file systems if space needed? yes
+
OVERWRITE same or newer versions? no
+
VERIFY install and check file sizes? no
+
Include corresponding LANGUAGE filesets? yes
+
DETAILED output? no
+
Process multiple volumes? yes

73 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

+
ACCEPT new license agreements? yes
+
Preview new LICENSE agreements? no
+

INVOKE live update? no


+
Requires /var/adm/ras/liveupdate/lvupdate.data.

WPAR Management
Perform Operation in Global Environment yes
+
Perform Operation on Detached WPARs no
+
Detached WPAR Names [_all_wpars]
+
Remount Installation Device in WPARs yes
+
Alternate WPAR Installation Device []

You should see the following successful JRE install message:

74 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

6. Install the JDK, using the smitty command. The steps are the same as the JRE installation (see 6.).

When you reach Install Software, the INPUT device / directory value is [temporary
folder]/Java71_64.jdk. Accept the new license agreements by selecting yes.

Press Enter.

Install Software

Type or select values in entry fields.


Press Enter AFTER making all desired changes.

[Entry Fields]

75 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

* INPUT device / directory for software


/tmp/download/install_jdk/Java71_64.jdk
* SOFTWARE to install [_all_latest]
+
PREVIEW only? (install operation will NOT occur) no
+
COMMIT software updates? yes
+
SAVE replaced files? no
+
AUTOMATICALLY install requisite software? yes
+
EXTEND file systems if space needed? yes
+
OVERWRITE same or newer versions? no
+
VERIFY install and check file sizes? no
+
Include corresponding LANGUAGE filesets? yes
+
DETAILED output? no
+
Process multiple volumes? yes
+
ACCEPT new license agreements? yes
+
Preview new LICENSE agreements? no
+

INVOKE live update? no


+
Requires /var/adm/ras/liveupdate/lvupdate.data.

WPAR Management
Perform Operation in Global Environment yes
+
Perform Operation on Detached WPARs no
+
Detached WPAR Names [_all_wpars]
+
Remount Installation Device in WPARs yes
+

76 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

Alternate WPAR Installation Device []

You should see the following successful install message for the JDK:

7. Verify the installed JDK folder.

[root@gvalpar03 install_jdk]# ls -al /usr/java71_64


total 488
drwxr-xr-x 7 bin bin 4096 Feb 14 19:32 .
drwxr-xr-x 42 bin bin 4096 Feb 13 16:35 ..
drwxr-xr-x 2 bin bin 4096 Feb 14 19:32 bin
-rw-r--r-- 1 bin bin 688 Nov 18 2013 copyright
drwxr-xr-x 3 bin bin 4096 Oct 28 09:53 include
drwxr-xr-x 5 bin bin 256 Dec 12 2013 jre
drwxr-xr-x 2 bin bin 256 Oct 28 09:53 lib

77 C reat ed b y J u mp S t art
S t a ck 5 T ru e B l u e R u n b ook 1. 0

-rw-r--r-- 1 bin bin 60279 Nov 18 2013 license_en.txt


-rw-r--r-- 1 bin bin 155662 Nov 18 2013 notices.txt
drwxr-xr-x 3 bin bin 256 Oct 28 09:53 properties
-rw-r--r-- 1 bin bin 802 Nov 18 2013 readme.txt
-rw-r--r-- 1 bin bin 97 Nov 18 2013 release

8. Verify which Java filesets are installed.

[root@gvalpar03 install_jdk]# lslpp -l | grep Java


Java71_64.jre 7.1.0.0 COMMITTED Java SDK 64-bit Java Runtime
Java71_64.sdk 7.1.0.360 COMMITTED Java SDK 64-bit Development
Java7_64.docs 7.0.0.320 COMMITTED Java SDK 64-bit Docs
Java7_64.jclsource 7.0.0.370 COMMITTED Java SDK 64-bit Java Class
Java7_64.jre 7.0.0.370 COMMITTED Java SDK 64-bit Java Runtime
Java7_64.samples.demo 7.0.0.370 COMMITTED Java SDK 64-bit Demo Samples
Java7_64.samples.jmx 7.0.0.370 COMMITTED Java SDK 64-bit JMX and other
Java7_64.samples.jnlp 7.0.0.370 COMMITTED Java SDK 64-bit JNLP Samples
Java7_64.sampsource 7.0.0.370 COMMITTED Java SDK 64-bit Source Files
Java7_64.sdk 7.0.0.370 COMMITTED Java SDK 64-bit Development
Java71_64.jre 7.1.0.0 COMMITTED Java SDK 64-bit Java Runtime
Java7_64.jre 7.0.0.370 COMMITTED Java SDK 64-bit Java Runtime

Java environment variable

To set the environment variable $JAVA_HOME to /usr/java71_64, add $JAVA_HOME/bin to the environment
PATH of Linux.

The following sample .bash_profile file contains the necessary environment variables:

##############################################

# JAVA Home
export JAVA_HOME=/usr/java71_64
echo "JAVA_HOME="$JAVA_HOME
export PATH=$JAVA_HOME/bin:$PATH
java -version
##############################################

78 C reat ed b y J u mp S t art

S-ar putea să vă placă și