2006 BEA Systems, Inc.

185
Configurations for Supporting Remote
Clients
At the end of this module, you will be able to:
Configure support for Workstation Clients
Deploy and Monitor Workstation Listeners
Configure support for Jolt Clients
Deploy Jolt Server components
Module 7
Configurations for Supporting Remote Clients-1
2006 BEA Systems, Inc. 186
Road Map
1. The /WS Subsystem
/WS Components
Configuring Workstation Listeners and Handlers
Configuring Workstation Client
Workstation Listener Failover
2. BEA Jolt
Configurations for Supporting Remote Clients-2
2006 BEA Systems, Inc.
Review: Tuxedo Native Clients
N
e
t
w
o
r
k

DBBL
BBL
BB
BRIDGE
Server

SERVICE A
SITE2
BRIDGE
Server

SERVICE B


Native
Client
SITE1
BBL
BB

Native
Client
Configurations for Supporting Remote Clients-3
2006 BEA Systems, Inc. 188
The Workstation Subsystem (/WS)
Native clients run on the same machines configured
in the MACHINES section
For remote clients, the /WS subsystem connects client
programs running on remote machines to a Tuxedo
domain
The remote desktop or machine is not part of the Tuxedo
*MACHINES configuration
For example, remote Customer Service reps have PCs
connected to a regional center
/WS is supported on common desktop systems and also
on all the Tuxedo server platforms.
Configurations for Supporting Remote Clients-4
2006 BEA Systems, Inc. 189
/WS Components


WSL WSH
NETWORK
UNIX
SERVER
Workstation
Client (WSC)
ATMI
ATMI
Windows, Mac
Remote
Machines
Service
Tuxedo
Domain
Workstation
Handler (WSH)
Workstation
Listener (WSL)
ATMI
Configurations for Supporting Remote Clients-5
2006 BEA Systems, Inc. 190
/WS
Client
WSL
WSH
WSL
WSH
Remote Client Connection Process
Client connects to the WSL via
a known network address
Client sends requests to the
WSH; WSH executes the
request on behalf of client and
returns the response.
A WSH can support (multiplex)
multiple client connections.
/WS
Client
/WS
Client
/WS
Client
WSL
WSL returns the network
address of a WSH
If necessary, the WSL spawns a
new WSH client process;
The WSL informs the WSH that
the client connection request
has passed the security check
Configurations for Supporting Remote Clients-6
2006 BEA Systems, Inc. 191
/WS Client
WSL
WSC Configuration Overview
The WSH on the server machine uses
a different TCP/IP port from the WSL.
Set Environment Variables
TUXDIR=c:\bea\tuxedo9.0
WSNADDR=//gumby:9977
UBBCONFIG
*SERVERS
WSL SRVGRP=SYSGRP SRVID=10 RESTART=Y
CLOPT=-A -- -n //gumby:9977 -m 2 -M 5 -x 5
WSL
WSH WSH ..
The WSH multiplexing factor -
up to 5 /WS clients per WSH.
2 WSHs are started up
initially; up to a maximum
of 5 can be started
WSL is a server provided
with the Tuxedo software
Configurations for Supporting Remote Clients-7
2006 BEA Systems, Inc. 192
Configuring the WSL Server

Name of alternative handler (created using buildwsh) Default: WSH -w name
Upper size limit (in bytes) for incoming messages received from WSC -U limit
Enables network keep-alive for: client, handler or both Default: none -K option
Min and Max levels for LLE Levels: 0|40|56|128 Defaults: -z0 Z128 -z|-Z level
Number of seconds used for WSC network timeout Default:0(no timeout) -N time
Specifies the complete network address of the WSL (Required) -n netaddr
The name of the device file used by WSL and WSH for network access -d device
Specifies a complete network address template to be used by WSHs -H extaddr
Min and Max port numbers used by WSHs Defaults: -p2048 P65535 -p|-P port
Sets the compression threshold (in bytes) between WSC and WSH -c threshold
Number of seconds to complete initialization with the WSH Default: 60 -I time
Multiplexing factor for each WSH Range: 1-4096 Default: 10 -x mpxfactor
Maximum number of WSHs Range: 0-4096 Default: MAXWSCLIENTS/-x -M maxh
Minimum number of WSHs to remain booted Range: 0-255 Default: 0 -m minh
Number of minutes allowed for IDLE clients Default: 0 (no timeout) -T time
Description CLOPT option
Configurations for Supporting Remote Clients-8
2006 BEA Systems, Inc. 193
Configuring the MACHINES Section
MAXWSCLIENTS specifies the maximum number of
remote clients that can be connected to this specific
Tuxedo machine.
MAXACCESSERS may need to be increased to allow
for that possible number of remote clients.
Configuring Remote Client Support in the MACHINES section:
*MACHINES
MYMACHINE
LMID=SITE1
TUXDIR=C:\bea\tuxedo9.0
APPDIR=C:\student\course_tux\domains\adminTng
TUXCONFIG=C:\student\course_tux\domains\adminTng\tuxconfig
MAXACCESSERS=125
MAXWSCLIENTS=50
Assuming that the prior setting
for MAXACCESSERS was only 75
Configurations for Supporting Remote Clients-9
2006 BEA Systems, Inc. 194
Example: Configuring WSC Support







Example UBBCONFIG File:
*MACHINES
gumby
MAXACCESSERS=225
MAXWSCLIENTS=150
snoopy
MAXWSCLIENTS=0

*SERVERS
WSL SRVGRP=SYSGRP SRVID=100 RESTART=Y
CLOPT= -A -- -n //gumby:9977 -m 5 -M 30 -x 5
Machine gumby is configured to support
up to 150 WSCs; MAXACCESSERS has
also been increased from 75 to 225
WSL server listens on TCP/IP port 9977;
5 WSHs are initially booted up, each
supporting up to 5 /WS clients
UBBCONFIG
Machine snoopy will not support WSCs
Configurations for Supporting Remote Clients-10
2006 BEA Systems, Inc. 195
WSC Configuration on Client Machines
Workstation Client Platforms
Desktop machines: The /WS software is installed for the
specific desktop platform
Server Machines: /WS client software can be installed with
the Tuxedo software
WSC executables are created using the /WS ATMI
libraries enabled by the w flag in buildclient:
buildclient -f simpcl.c -o simpcl -w
Set environment variables
minimum : TUXDIR, PATH, WSNADDR
if applicable, the library path may also need to include
$TUXDIR/lib
Configurations for Supporting Remote Clients-11
2006 BEA Systems, Inc. 196
WSC Environment Variables

Network address to be used for WSH connection WSFADDR
Directory used for overflow reply storage Default: pwd TMPDIR
Number of bytes used for buffering replies Default: 256k WSREPLYMAX


Required
Location of Tuxedo Product Software TUXDIR
Network address of the WSL (must match n flag) WSNADDR
String value compared to TYPE parameter in MACHINES WSTYPE
The name of the device file used for network access WSDEVICE
File may be used to read in remaining ENV variables WSENVFILE
Description ENV Variable
NONE | APP_PW | USER_AUTH | ACL SECURITY
Upper range of ports to be used for WSH connections WSFRANGE
Minimum number of bits used for LLE Default: 0
TMMINENCRYPTBITS
Location and prefix name of the WSC ULOG ULOGPFX
Maximum number of bits used for LLE Default: 128
TMMAXENCRYPTBITS
Configurations for Supporting Remote Clients-12
2006 BEA Systems, Inc. 197
Configuring for WSL/WSH Failover
WSCs can be configured to attempt alternate network
addresses:
Configure additional WSLs in the Tuxedo domain
Include the additional network addresses in WSNADDR
Try each host in turn until successful:
WSNADDR=//gumby:5001,//gumby:6001,//snoopy:5001
Choose any host at random:
WSNADDR=(//gumby:5001|//gumby:6001|//snoopy:5001)
Choose one of two hosts at random, with the third as
backup:
WSNADDR=(//gumby:5001|//gumby:6001),//snoopy:5001
Configurations for Supporting Remote Clients-13
2006 BEA Systems, Inc. 198
Setting WSC Environment Variables
Common practice is to set WSENVFILE prior to
starting the WSC.
Set in Control Panel, as a System Env Var, or in a script
Example: set WSENVFILE=C:\clientapps\wsc.env
The WSENVFILE is a simple text format, each line
containing: <variableName>=<value>
Comments are preceded by the # symbol

10
0101
1110
Example WSENVFILE format:
# wsc.env setting WSC environment variables
WSNADDR=//mach1:2468,//mach2:3579
ULOGPFX=C:\clientapps\wscULOG
TMMAXENCRYPTBITS=0
CURRENT_TAX_RATE=6.5
Configurations for Supporting Remote Clients-14
2006 BEA Systems, Inc. 199
Section Review
Add Workstation Client support
Use WSL CLOPT options
Configure the Workstation Client Environment
Plan for WSL Failover

In this section, we learned how to:
Configurations for Supporting Remote Clients-15
2006 BEA Systems, Inc. 200
Lab Exercise
For details on the exercise, refer to the Lab Guide.
If questions arise, ask the instructor.
The instructor will determine the stop time.
Lab 07 CLNT: Configure and Deploy
Workstation Client Support
Configurations for Supporting Remote Clients-16
2006 BEA Systems, Inc. 201
Road Map
1. The /WS Subsystem
2. BEA Jolt
Jolt Architecture and Components
Jolt Repository
Repository Editor and Bulk Loader
Jolt Internet Relay Components
Configuring the Jolt Server Listener and Handler
Configuring the Jolt Repository Server
Deploying Jolt Client Applications
Configurations for Supporting Remote Clients-17
2006 BEA Systems, Inc. 202
BEA Jolt
Jolt is a Java-based interface to the BEA Tuxedo
system.
Jolt software enables Tuxedo clients to be written as
Java applications or applets WITHOUT CHANGES to
Tuxedo services
Tuxedo servers are still written in C/C++ or COBOL
Users can take advantage of Java features:
develop Java object-oriented, GUI clients and deploy easily
to various client platforms.
support for universal client (browser + applet).
run Jolt client code within Web Server applications.
Configurations for Supporting Remote Clients-18
2006 BEA Systems, Inc. 203
Jolt Components

JSL JSH
NETWORK
UNIX
SERVER
Jolt Clients
ATMI
Jolt Class Library
Windows, Mac
Remote
Machines
Service
Tuxedo
Domain
Jolt Server
Handler (JSH)
Jolt Server
Listener (JSL)
Jolt Class Library
JREPSVR
Jolt
Repository
Jolt
Repository
Server
Configurations for Supporting Remote Clients-19
2006 BEA Systems, Inc. 204
Jolt
Client
JSL
JSH
JSL
JSH
The Jolt Client Connection Process
Client connects to the JSL via
a known network address
Client sends requests to the
JSH; JSH executes the request
on behalf of client and returns
the response.
A JSH can support (multiplex)
multiple client connections.
Jolt
Client
Jolt
Client
Jolt
Client
JSL
JSL returns the network
address of a JSH
If necessary, the JSL spawns a
new JSH client process;
The JSL informs the JSH that
the client connection request
has passed the security check
Configurations for Supporting Remote Clients-20
2006 BEA Systems, Inc. 205
Java
Object
Tuxedo
data
Service Definition Repository
Service: Name, Buffer Type (FML, )
Parameters:Type,
Name,
Direction (In/Out)
Jolt Protocol
Repository Methods:
add, delete, update,
advertise, unadvertise, test
Jolt Repository
Configurations for Supporting Remote Clients-21
2006 BEA Systems, Inc. 206
Creating the Jolt Repository:
Jolt Repository Editor
The Jolt Repository Editor is available as a
downloadable Java applet.
The Jolt Repository is updated and modified using the
JSL and the JREPSVR W servers.
The applet can run within a provided appletviewer
or within your web browser.

Logon
Package Organizer
Services
Edit Service Edit Parameters
View Packages & Services
Test Service Add Service
Packages
Configurations for Supporting Remote Clients-22
2006 BEA Systems, Inc. 207
Creating the Jolt Repository:
Bulk Loader
The Bulk Loader program is a Java application:
bea.jolt.admin.jbld
The Bulk Load File is a text file that defines services
and their associated parameters.
Syntax for this file is divided into Service-level and
Parameter-level keywords.
The jbld program expects two key arguments:
The Bulk Load File
The network address of the JSL

JREPSVR
Jolt
Repository
JSL
JSH
jbld
Bulk Load
File
Configurations for Supporting Remote Clients-23
2006 BEA Systems, Inc. 208
Jolt Internet Relay
Jolt clients connecting from outside a firewall may
need to connect to JRLY instead of JSL.
The Jolt Relay server is run on the clients machine (or
another machine local to the client).
The Jolt Relay Adapter is configured within the
UBBCONFIG as the bridge between one JRLY and one
JSL.
JRAD
JSL
JSH
Tuxedo
Domain
JRLY
Jolt
Client
F
I
R
E
W
A
L
L
Configurations for Supporting Remote Clients-24
2006 BEA Systems, Inc. 209
Jolt Client
WSL
Basic Jolt Configuration Overview
The JSH on the server machine uses a
different TCP/IP port from the JSL.
The Jolt client developer must
provide for the setting of the JSL
network address in:
JoltSessionAttributes.APPADDRESS
*SERVERS
JREPSVR SRVGRP=SYSGRP SRVID=11 RESTART=Y
CLOPT=-A -- -P /appdir/jrepository
JSL SRVGRP=SYSGRP SRVID=10 RESTART=Y
CLOPT=-A -- -n //gumby:9977 -m 2 -M 5 -x 5
JSL
JSH ..
2 JSHs are started up
initially; up to a maximum
of 5 can be started
JREPSVR and JSL are
servers provided with
the Tuxedo software
JSH
Configurations for Supporting Remote Clients-25
2006 BEA Systems, Inc. 210
Configuring the JSL Server

Sets the connection mode: RETAINED|RECONNECT|ANY(default) -j mode
Length (in bits) of DH encryption key Bits: 0|56|128 Default: -z0 -z bits
Use this name for identifying the JSH process Default: JSH -w name
Specifies the complete network address of the JSL (Required) -n netaddr
The name of the device file used by JSL and JSH for network access -d device
Specifies a complete network address template to be used by JSHs -H extaddr
Enables the security context for a Jolt Connection Pool Default:(not set) -a
Sets the compression threshold (in bytes) between the client and JSH -c threshold
Number of seconds to complete initialization with the JSH Default: 60 -I time
Multiplexing factor for each JSH Range: 1-32767 Default: 10 -x mpxfactor
Maximum number of JSHs Range: 1-32767 Default: MAXWSCLIENTS/-x -M maxh
Minimum number of JSHs to remain booted Range: 0-255 Default: 0 -m minh
Number of minutes allowed for IDLE clients Default: 0 (no timeout) -T time
Description CLOPT option
Configurations for Supporting Remote Clients-26
2006 BEA Systems, Inc. 211
Configuring the Jolt Repository Server
The Jolt Repository Server JREPSVR can be
configured to be read-only or read-write capable.
Only one read-write server can be configured.
Use the W option for write access to the Jolt repository.
Use the P option to indicate the location and name of
the Jolt repository file.

Example JREPSVR configuration:
*SERVERS
JREPSVR SRVGRP=SYSGRP1 SRVID=100 RESTART=Y
CLOPT=-A -- -W -P /nfs/filesystem/jrepository
JREPSVR SRVGRP=SYSGRP1 SRVID=101 RESTART=Y
CLOPT=-A -- -P /nfs/filesystem/jrepository
JREPSVR SRVGRP=SYSGRP2 SRVID=100 RESTART=Y
CLOPT=-A -- -P /nfs/filesystem/jrepository
This server is used for write
access to jrepository
All servers
need access
to the same
file
Configurations for Supporting Remote Clients-27
2006 BEA Systems, Inc. 212
Configuring the MACHINES Section
MAXWSCLIENTS specifies the maximum number of
remote clients that can be connected to this specific
Tuxedo machine.
MAXACCESSERS may need to be increased to allow
for that possible number of remote clients.
Configuring Remote Client Support in the MACHINES section:
*MACHINES
MYMACHINE
LMID=SITE1
TUXDIR=C:\bea\tuxedo9.0
APPDIR=C:\student\course_tux\domains\adminTng
TUXCONFIG=C:\student\course_tux\domains\adminTng\tuxconfig
MAXACCESSERS=125
MAXWSCLIENTS=50
Assuming that the prior setting
for MAXACCESSERS was only 75
Configurations for Supporting Remote Clients-28
2006 BEA Systems, Inc. 213
Example: Configuring Jolt Support







Example UBBCONFIG File:
*MACHINES
gumby
MAXACCESSERS=225
MAXWSCLIENTS=150

*SERVERS
DEFAULT: SRVGRP=SYSGRP RESTART=Y
JREPSVR SRVID=80 CLOPT=-A -- -W P /appdir/jrep
JREPSVR SRVID=81 CLOPT=-A -- -P /appdir/jrep
JSL SRVID=90
CLOPT=-A -- -n //gumby:9977 -m 5 -M 30 -x 5
JRAD SRVID=95
CLOPT=-A -- -l //gumby:9950 c //gumby:9977
Machine gumby is configured to support
up to 150 remote clients; MAXACCESSERS
has also been increased from 75 to 225
JSL listens on TCP/IP port 9977; 5
JSHs are initially booted up, each
supporting up to 5 Jolt clients
UBBCONFIG
10
0101
1110
Example JRLY Configuration File:
LISTEN=//snoopy:2468
CONNECT=//gumby:9950
Start JRLY as a Windows service
or from the command-line:
> jrly f jrly_config_file
Configurations for Supporting Remote Clients-29
2006 BEA Systems, Inc. 214
Jolt Configuration on Client Machines
The Jolt client software can be installed along with the
Tuxedo Server software or separately on the client
machine.
Jolt clients can run in any Java Virtual Machine (JVM)
Jolt class files must be added to the JVMs CLASSPATH
Jolt classes are located in:
$TUXDIR/udataobj/jolt/jolt.jar
10
0101
1110
Setting the Jolt client environment:
set CLASSPATH=%TUXDIR%\udataobj\jolt\jolt.jar;%CLASSPATH%
set PATH=C:\bea\jre\bin;%PATH%
Starting a Jolt client application:
> setJoltEnv.cmd
> java myJoltClient.class
Configurations for Supporting Remote Clients-30
2006 BEA Systems, Inc. 215
Configuring for JSL/JSH Failover
Jolt clients can be configured to attempt alternate
network addresses:
Configure additional JSLs in the Tuxedo domain
Include the additional network addresses in the
JoltSessionAttributes.APPADDRESS string.
Try each host in turn until successful:
//gumby:5001,//gumby:6001,//snoopy:5001
Choose any host at random:
(//gumby:5001|//gumby:6001|//snoopy:5001)
Choose one of two hosts at random, with the third as
backup:
(//gumby:5001|//gumby:6001),//snoopy:5001
Configurations for Supporting Remote Clients-31
2006 BEA Systems, Inc. 216
Section Review
Add Jolt Client support
Use JSL and JPREPSVR CLOPT options
Use additional Jolt components
Plan for JSL Failover

In this section, we learned how to:
Configurations for Supporting Remote Clients-32
2006 BEA Systems, Inc. 217
Lab Exercise
For details on the exercise, refer to the Lab Guide.
If questions arise, ask the instructor.
The instructor will determine the stop time.
Lab 08 CLNT: Configure and Deploy Jolt
Client Support
Configurations for Supporting Remote Clients-33
2006 BEA Systems, Inc. 218
Module Review
Configure support for Workstation Clients
Deploy and Monitor Workstation Listeners
Run a Workstation Client
Configure support for Jolt Clients
Deploy Jolt Server components
Run a Jolt Client Application
In this module, we learned how to:
Configurations for Supporting Remote Clients-34