Platform Framework
R24 AMR | Min(s) read

WebLogic Property File Setup

This section shows you the configurations that you need to setup in the WebLogic property file to deploy TAFJ.

Environment Configuration

WebLogic embeds ANTLR library, which conflicts with the TAFJ ANTLR version. If you use inappropriate version, then the following exception is thrown:

(CharScanner; panic: ClassNotFoundException: com.temenos.tafj.jql.jQLToken).

Setup WebLogic Script

To setup WebLogic classpath, you need to add the following configurations in the %WEBLOGIC_HOME%\user_projects\domains\TAFJ\bin\setDomainEnv.cmd(or sh)file below the @REM IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values line:

@REM TAFJ Memory settings
set USER_MEM_ARGS=-Xms2G -Xmx4G
If the deployment is meant to be done using shared libraries of TAFJ_LIB/T24_LIB, then the following below TAFJ_HOME/T24_HOME need not be set ! Please continue to set all necessary DB drivers and follow the instructions for deploying the shared libs while deploying TAFJEAR file section.
@REM ADD EXTENSIONS TO CLASSPATHS
@REM TAFJ Classpath
set TAFJ_HOME=[TAFJ_HOME]
set T24_HOME=[T24_HOME]
@REM TAFJ antlr lib
set EXT_PRE_CLASSPATH=%TAFJ_HOME%\lib\antlr.jar

@REM TAFJ T24 CLASSPATH 
set TAFJ_T24_CLASSPATH=%TAFJ_HOME%\lib\log4j-api.jar;%TAFJ_HOME%\lib\log4j-core.jar;%TAFJ_HOME%\lib\T24CollectorClient.jar;%TAFJ_HOME%\lib\TemenosSecurity.jar;%TAFJ_HOME%\lib\TAFJCommon.jar;%TAFJ_HOME%\lib\TAFJCache.jar;%TAFJ_HOME%\lib\cache-api.jar;%TAFJ_HOME%\lib\TAFJCompiler.jar;%TAFJ_HOME%\lib\TAFJCore.jar;%TAFJ_HOME%\lib\TAFJClient.jar;%TAFJ_HOME%\lib\TAFJLocking.jar;%TAFJ_HOME%\lib\TAFJLogging.jar;%TAFJ_HOME%\lib\TAFJTelnetD.jar;%TAFJ_HOME%\lib\TAFJHealthCheck.jar;%TAFJ_HOME%\lib\TAFJConfiguration.jar;%TAFJ_HOME%\lib\TAFJDBImport.jar;%TAFJ_HOME%\lib\jansi.jar;%TAFJ_HOME%\lib\TAFJVersion.jar;%TAFJ_HOME%\TAFJBasic.jar;%TAFJ_HOME%\ext\tComponentFramework.jar

@REM JDBC Driver not already in the CLASSPATH for weblogic version < 12.1.3 only
@REM i.e Oracle 11g: set TAFJ_T24_CLASSPATH=%TAFJ_T24_CLASSPATH%;%TAFJ_HOME%\dbdrivers\oracle-11g\xmlparserv2.jar;%TAFJ_HOME%\dbdrivers\oracle-11g\xdb.jar;
@REM i.e Oracle 12c: set TAFJ_T24_CLASSPATH=%TAFJ_T24_CLASSPATH%;%TAFJ_HOME%\dbdrivers\oracle-12c\xmlparserv2.jar;%TAFJ_HOME%\dbdrivers\oracle-12c\xdb6.jar;
@REM i.e H2        : set TAFJ_T24_CLASSPATH=%TAFJ_T24_CLASSPATH%;%TAFJ_HOME%\dbdrivers\h2-1.3.168\h2-1.3.168.jar
set TAFJ_T24_CLASSPATH=%TAFJ_T24_CLASSPATH%;%TAFJ_HOME%\dbdrivers\h2-1.3.168\h2-1.3.168.jar


@REM T24 CLASSPATH
set TAFJ_T24_CLASSPATH=%TAFJ_T24_CLASSPATH%;%T24_HOME%\t24lib\*

set EXT_POST_CLASSPATH=%TAFJ_T24_CLASSPATH%

You can use wildcard * when you want to load all JARs contained in a folder. That is to avoid listing the 900 Temenos Transact JARs, you can set as TAFJ_T24_CLASSPATH=%TAFJ_T24_CLASSPATH%;%T24_HOME%\*

Validate that red word match deployment environment. If you are on a UNIX, Linux or zOS platform the separator file is / instead of \ and ; instead of :.

The xmlparserv2.jar and xdb.jar / xdb6.jar files must match the ojdbc6.jar version provided with WebLogic.

Check ojdbc6.jar version from the server/lib or oracle_common/modules. It will be different depending on your application server version.

UAT / Production Memory Setting

Set USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:MaxPermSize=256m

The above memory setting is the minimal one to be able to deploy the application and run some agents to validate the configuration.

For a UAT and production environment, you must refine this setting depending on your expected number of sessions and tSA. A session or tSA memory impact vary depending on the job done, it will be at least 20MB and could be up to 60MB.

When planning to run for example 80 interactive sessions and 40 tSA on a server, you can dimension the max memory for sessions by applying:

120 sessions * average 50MB = 6G max heap size.

You will have -Xmx6G

A good practice could be to set initial heap size to same value -Xms6G

If you are interested to monitor that more precisely, you could use a monitoring tool like Visual VM.

Take a heapdump when running the expected jobs, isolate the jSession objects and compute the retained size.

This is for one session.

This for 16 sessions.

You could also simply use TAFJ technical monitor to follow the memory evolution graph over the time and refine your setup.

Copyright © 2020- Temenos Headquarters SA

Published on :
Monday, May 27, 2024 5:10:39 PM IST