Index
Symbols
-
/Q (Queued Message Facility) 13-2
A
-
access control in a configuration file
-
defining 3-14
-
access control lists (ACLs)
-
using 14-10
-
ACLs
-
administering 14-11
-
limitations 14-11
-
AdminAPI 21-1
-
administration
-
configuration tools 2-2
- using AdminAPI 2-4
- using BEA Administration Console 2-3
- using command-line interface 2-3
-
differences between WLE and BEA TUXEDO 1-4
-
run-time tools 2-4
- using AdminAPI 2-6
- using BEA Administration Console 2-4
- using command-line interface 2-6
-
tasks
- configuration 2-1
- run-time 2-1
-
tools 2-1-2-7
-
administration phases
-
groundwork 1-2
-
operational 1-3
-
APP_PW 11-5
-
APP_PW variable 11-6
-
application components
-
replacing 23-13
-
application failure 23-2
-
application parameters
-
SANITYSCAN parameter 17-9
-
setting 17-10
-
using 17-8
-
application type in a configuration file
-
setting 3-13
-
applications
-
starting 4-1
-
authentication server
-
configuring 14-8
-
using 14-7
-
AUTOTRAN parameter 7-9, 7-10, 7-13
-
AUTOTRAN timeout value
-
changing 19-5
B
-
bankapp application 15-21
-
BBLQUERY parameter 17-9, 17-10
-
BLOCKTIME parameter 3-19, 17-9, 17-10
-
bottlenecks, detecting system
-
example 17-12
-
sar(1) command options
- -b option 17-13
- -c option 17-13
- -m option 17-13
- -p option 17-13
- -q option 17-13
- -r option 17-14
- -u option 17-13
- -w option 17-13
-
buffer type and subtype limits in a configuration file
-
setting 3-18
-
buffer types allowed for a service
-
BUFTYPE parameter examples 3-55
-
specifying 3-55
-
BUFTYPE parameter 3-55
-
bulletin board 15-2
-
bundling services into servers
-
when to bundle services 17-7
C
-
CLOPT parameter 12-8
-
command line options 11-8
-
format 11-7
-
CLOSEINFO parameter 7-7
-
CMTRET parameter 7-3
-
configuration file
-
creating 3-1-3-70
-
GROUPS section
- sample 3-32
-
identifying the location 3-27
-
MACHINES section
- description of parameters in sample MACHINES section 3-25
- identifying machines 3-24
- sample 3-25
-
NETGROUPS section
- configuring information 3-67
-
SERVERS section
- identifying server process information 3-33
-
SERVICES section
- sample 3-53, 3-54
-
setting domain-wide parameters 3-10
-
configuration file forms
-
TUXCONFIG file 3-2
-
configuration file parameters
-
APPDIR 3-28
-
AUTHSVC 3-21
-
AUTOTRAN 3-57
-
BLOCKTIME 3-20
-
BUFTYPE 3-55
-
CONV 3-51
-
ENVFILE 3-29
-
FACTORYROUTING 3-57
-
FASTPATH 3-24
-
GID 3-30
-
GRACE 3-51
-
IPCKEY 3-12
-
LDBAL 3-53
-
LMID 3-26
-
LOAD 3-57
-
MASTER 3-13
-
MAX 3-45
-
MAXACCESSERS 3-17, 3-30
-
MAXBUFSTYPES 3-19
-
MAXBUFTYPE 3-18
-
MAXCONV 3-20
-
MAXGEN 3-50
-
MAXINTERFACES 3-17
-
MAXNETGROUPS 3-67, 3-68
-
MAXOBJECTS 3-17, 3-30
-
MAXPENDINGBYTES 3-67, 3-68
-
MAXSERVERS 3-17
-
MAXSERVICES 3-18
-
MIN 3-45
-
NETGROUP 3-67, 3-68
-
NETGRPNO 3-67
-
NETPRIO 3-67
-
NO_OVERRIDE 3-24
-
NOTIFY 3-22
-
PERM 3-30
-
PRIO 3-54, 3-57, 3-60
-
PROTECTED 3-24
-
RCMD 3-50
-
REPLYQ 3-49
-
RESTART 3-50
-
RPPERM 3-49
-
RQADDR 3-49
-
RQPERM 3-49
-
SANITYSCAN 3-20
-
SCANUNIT 3-20
-
SECURITY 3-21
-
SEQUENCE 3-45
-
SRVGRP 3-36, 3-57
-
SRVID 3-36
-
SYSTEM_ACCESS 3-52
-
TIMEOUT 3-58
-
TRANTIME 3-57
-
TUXCONFIG 3-27
-
TUXDIR 3-28
-
UID 3-30
-
ULOGPFX 3-28
-
USIGNAL 3-23
-
configuring a local and remote domain 31
-
configuring a networked application
-
assigning priorities to each network group 6-8
-
example 6-5
-
steps 6-3
-
UBBCONFIG file 6-7
- NETGROUPS section 6-7
-
configuring groups 3-31
-
defining server groups in GROUPS section 3-31
-
configuring machines 3-24
-
identifying locations of WLE or BEA TUXEDO system software and application servers 3-27
-
identifying log file location 3-28
-
identifying machines in the MACHINES section 3-24
-
identifying the location of the configuration file 3-27
-
overriding system-wide parameters 3-30
-
reserving the physical address and machine ID 3-26
-
specifying environment variable settings for processes 3-29
-
configuring network information
-
network groups configuration 3-68
-
specifying information in NETGROUPS section 3-67
-
configuring routing
-
defining routing criteria in ROUTING section 3-61
-
specifying range criteria in sample ROUTING section 3-62
-
WLE factory-based routing example 3-63
-
configuring servers
-
command-line options 3-38
-
defining server access to shared memory 3-51
-
defining server name, group, ID 3-36
-
defining server restart information 3-50
-
identifying server environment file location 3-48
-
identifying server process information in SERVERS section 3-33
-
identifying server queues 3-48
-
setting order in which servers are booted 3-44
-
specifying a TUXEDO server as conversational 3-51
-
using server command-line options 3-37
-
configuring the UBBCONFIG with netgroups 3-70
-
configuring TUXEDO services
-
controlling data flow by service priority 3-54
-
enabling load balancing 3-53
-
identifying services in the SERVICES section 3-52
-
sample SERVICES section 3-53, 3-54
-
specifying a list of allowable buffer types for a service 3-55
-
specifying different service parameters for different server groups 3-54
-
configuring WLE interfaces
-
controlling data flow by interface priority 3-60
-
enabling load balancing 3-60
-
specifying CORBA interfaces in the INTERFACES section 3-56
-
specifying different service parameters for different server groups 3-60
-
specifying FACTORYROUTING criteria 3-58
-
configuring workstation listener (WSL) 11-7
-
using the CLOPT parameter 11-7
-
configuring your system
-
determining your server needs 1-7
-
planning the overall design 1-6
-
CORBA interface processing
-
distributing using factory-based routing 5-3
-
CORBA interfaces in a configuration file
-
specifying 3-56
-
crdl command
-
blocks value 7-4
-
creating a TLOG device 4-6
D
-
data
-
dynamic 15-4
-
static 15-4
-
data flow in a configuration file
-
controlling by interface priority 3-60
-
controlling by service priority 3-54
-
data-dependent routing
-
characteristics 5-8
-
using in TUXEDO 5-7
-
DBBLWAIT parameter 17-9, 17-10
-
device
-
reinitializing a 23-6
-
device list
-
creating 23-5
-
destroying 23-6
-
distributing an application
-
benefits 5-2
-
characteristics 5-2
-
description of routing section parameters 5-15
-
domain gateway configuration file 5-14
-
example 5-8
-
modifying domain gateway file to support routing 5-14
-
modifying the GROUPS section 5-9
- description of GROUPS parameters 5-10
-
modifying the SERVICES section
- description of SERVICES parameters 5-12
- sample SERVICES section 5-12
-
modifying the SERVICES section for TUXEDO 5-11
-
purpose 5-1
-
UBBCONFIG file example 5-13
-
DLL 12-2
-
DLL (Dynamic Link Libraries) 11-2
-
DMCONFIG file 30
-
DMTLOGDEV parameter 7-11
-
DMTLOGNAME parameter 7-12
-
DMTLOGSIZE parameter 7-12
-
domain access control list, creating 41
-
domain transaction log, creating 7-5
-
domains
-
benefits of using BEA TUXEDO system 28
-
components of DMCONFIG file 30
-
configuring a local and remote domain 31
-
creating domain access control list (ACL) 41
-
defining addressing 36
-
defining exported services 39
-
defining imported and exported services 36
-
defining local and remote domains 36
-
defining remote domain environment 37
-
defining the local domain environment 34
-
domain gateway configuration file 29
-
ensuring security 40
-
example of /DOMAINS 33
-
illustration of /DOMAINS 33
-
local application configuration file example 35
-
local domain configuration file example 37
-
remote application configuration file example 38
-
remote domain gateway configuration file example 39
-
routing service requests to remote domains 41
-
working with multiple 27-43
E
-
encryption, link-level 6-15
-
environment variable settings in a configuration file
-
specifying 3-29
-
environment variables, setting
-
ROOTDIR 11-5
-
errors
-
identifying using log files 16-1
-
Event Broker/Monitor 21-1
F
-
factory-based routing
-
characteristics 5-4
-
example 5-5
-
using to distribute CORBA interface processing 5-3
-
factory-based WLE routing example 3-63
-
failback 6-12
-
failover 6-12
-
failure
-
determining cause of application 23-2
-
determining cause of system 23-3
-
failure types 23-2
-
figures
-
assigning network group priorities 6-8
-
bank application with remote clients 12-5
-
bank application with two workstation clients 11-4
-
BEA Administration Console screen 2-5
-
BEA TUXEDO /DOMAIN gateway 30
-
example of a network grouping 3-69, 6-6
-
flow of data over the BRIDGE 6-11
-
local and remote application (simpapp) 34
-
sample NETGROUPS and NETWORK sections 3-70
-
TUXEDO message queueing illustration 13-5
-
file system maintenance 23-5
G
-
GRACE parameter 3-50
-
GROUPS parameters used to distribute an application 5-10
I
-
IIOP (Internet Inter-ORB Protocol) 12-2
-
interface repositories
-
administering 8-2
-
creating and populating 8-4
-
deleting 8-4
-
displaying or extracting content 8-4
-
managing
- prerequisites 8-3
- using administrative commands 8-3
-
IPC limits in a configuration file
-
defining 3-15
-
IPC requirements
-
tuning 17-11
- MAXACCESSERS 17-11
-
tuning queue-related kernel parameters 17-11
-
IPC requirements, determining 17-10-17-11
-
IPCKEY parameter 3-12
-
ISH (IIOP Server Handler) 12-2
-
ISL (IIOP Server Listener) 12-2
J
-
JavaServer
-
configuration options 3-38
-
enabling multithreading 3-38
-
nonstandard Java options 3-42
-
standard Java options 3-41
-
WLE-noredirect option 3-41
K
-
kernel parameters
-
how to tune 17-11
L
-
listings
-
bbsread output 15-24
-
canceling a server group migration 18-10
-
configuration file for bankapp (MP version) 15-21
-
local application configuration file 35
-
local domain gateway configuration file 37
-
migrating a machine when an alternate machine is accessible 18-8
-
migrating a machine when an alternate machine is not accessible 18-8
-
migration when a master machine is accessible 18-3
-
migration when a master machine is not accessible 18-4
-
migration when an alternate machine is accessible 18-6
-
migration when an alternate machine is not accessible 18-6
-
remote application configuration file 38
-
remote domain gateway configuration file 39
-
sample GROUPS and NETWORK sections 7-16
-
sample MACHINES section 7-15
-
sample RESOURCES section 7-14
-
TMADMIN default output 15-11
-
tmadmin session example 23-9
-
load balancing
-
enabling 17-3
-
measuring service performance time 17-3
-
load balancing in a configuration file
-
enabling 3-18
-
load balancing TUXEDO services in a configuration file
-
enabling 3-53
-
load balancing WLE interfaces in a configuration file
-
enabling 3-60
-
locations of WLE or BEA TUXEDO system software and application servers
-
identifying 3-27
-
log file in a configuration file
-
identifying location 3-28
-
log files 15-3
-
using to detect failures 16-14-16-16
M
-
MANDATORY_ACL parameter
-
restriction for WLE systems 14-10
-
MAX parameter 3-44
-
MAXACCESSERS
-
threads 3-15
-
MAXACCESSERS parameter 17-10
-
MAXBUFSTYPE parameter 17-10
-
MAXBUFTYPE parameter 17-10
-
MAXBUFSTYPE parameter 17-9
-
MAXENCRYPTBITS parameter 6-18
-
MAXGEN parameter 3-50
-
MAXGTT 17-11
-
MAXGTT parameter 7-3, 17-10
-
MAXRDTRAN parameter 7-12
-
MAXSERVERS
-
MAXSERVICES 17-11
-
MAXSERVERS parameter 17-10
-
MAXSERVICES parameter 17-10
-
MAXTRAN parameter 7-12
-
MAXWSCLIENTS parameter 11-6
-
migrating applications 18-1-18-11
-
examples of switching master and backup machines 18-3
- when the master machine is accessible from the backup machine 18-3
- when the master machine is not accessible from the backup machine 18-4
-
how to switch master and backup machines 18-3, 18-10
-
migration options 18-2
-
canceling a migration 18-9
-
example of canceling a migration
- canceling a server group migration for a server group GROUP1 18-10
-
example of migrating a machine
- when the alternate machine is accessible from the primary machine 18-8
- when the alternate machine is not accessible from the primary machine 18-8
-
example of migrating a server group
- when the alternate machine is accessible from the primary machine 18-6
- when the alternate machine is not accessible from the primary machine 18-6
-
migrating a server group 18-4
- how to migrate a server group when the alternate machine is accessible from the primary machine 18-5
- how to migrate a server group when the alternate machine is not accessible from the primary machine 18-5
-
migrating machines 18-7
- how to migrate machines when the alternate machine is accessible from the primary machine 18-7
- how to migrate machines when the alternate machine is not accessible from the primary machine 18-8
-
migrating transaction logs to a backup site 18-10
-
switching master and backup machines 18-2
-
MIN parameter 3-44
-
MINENCRYPTBITS parameter 6-18
-
modifying systems, dynamically 19-1-19-5
-
procedures 19-2
- advertising services 19-4
- changing AUTOTRAN timeout value 19-5
- changing service parameters 19-5
- resuming BEA TUXEDO services 19-3
- suspending BEA TUXEDO services 19-3
- unadvertising services 19-4
-
monitoring a running system 15-1-15-25
-
bankapp configuration file 15-21
-
checking local IPC resources 15-24
-
checking system-wide parameters 15-25
-
data repositories
- bulletin board 15-2
- log files 15-3
- UBBCONFIG file 15-2
-
methods 15-5
-
output from TMADMIN commands
- PRINTCONN 15-18
- PRINTNET 15-19
- PRINTQUEUE 15-17
- PRINTTRANS 15-20
-
running TMADMIN commands 15-13
-
sample bankapp application 15-21
-
sample bankapp application output 15-24-??
-
sample bankapp applicatiooutput 15-25
-
TMADMIN meta-commands 15-9
-
TMADMIN operating modes 15-8
-
types of administrative data 15-3
-
using AdminAPI 15-5
-
using statistics 15-3
-
monitoring log files 16-1-16-16
-
MSSQ (multiple server single queue) 17-2
-
MSSQ sets
-
example 17-3
-
using 17-2
-
multiple server single queue (MSSQ) 17-2
-
Multithreaded JavaServers
-
enabling 3-38
-
MAXACCESSERS parameter 3-15
N
-
NETGROUPS section 6-7
-
NETLOAD parameter 6-14
-
network data flow
-
advantages of data compression 6-13
-
failback 6-12
-
failover 6-12
-
using data compression
- setting the compression level 6-12
-
network failures
-
recovering from severe 23-10
-
recovering from transient 23-10
-
network groups configuration
-
sample 3-68
-
networked application
-
balancing request loads 6-14
-
changing network configuration parameters 6-18
-
negotiating encryption key size 6-16
-
running a 6-9
-
scheduling network data over parallel circuits 6-10
-
specifying encryption key bits 6-18
-
using link-level encryption 6-15
-
networked applications 6-1-6-18
-
node
-
restoring a failed nonmaster 23-11
-
NOTIFY parameter 3-22
O
-
OPENINFO parameter 7-7
-
Outbound IIOP
-
bi-directional 12-12
-
outbound IIOP
-
asymetric 12-13
-
Asymmetric 12-11
-
Bi-directional 12-11
-
dual-paired 12-11, 12-14
-
overriding system-wide parameters 3-30
P
-
partitioned networks
-
detecting 23-8
-
repairing 23-7
-
performance time
-
servopts(5) -r option 17-3
-
physical address and machine ID
-
reserving 3-26
-
PRINTCONN command 15-18
-
PRINTNET command 15-19
-
PRINTNETWORK command 23-9
-
PRINTQUEUE command 15-17
-
PRINTSERVER command 23-9
-
PRINTSERVICE command 23-9
-
PRINTTRANS command 15-20
-
PRIO parameter 17-6
Q
-
QMADMIN
-
using to create message queues 13-7
-
QMCONFIG 13-2
-
QMCONFIG environment variable
-
setting 13-7
-
queue 13-2
-
queue space 13-2
-
queued BEA TUXEDO messages
-
managing 13-1-13-11
-
queued messages
-
associating queue with group 13-10
-
creating application queue space and queues 13-8
-
listing /Q servers in SERVER section 13-11
-
modifying the configuration file 13-10
-
setting the QMCONFIG environment variable 13-7
-
using QMADMIN 13-7
R
-
range criteria in a configuration file
-
specifying 3-62
-
RCMD parameter 3-50
-
remote clients
-
configuring a listener for 12-8
- using the CLOPT parameter 12-8
-
defined 12-4
-
how it connects to application 12-6
-
illustrated 12-5
-
managing 12-1-12-10
-
setting environment variables 12-6
-
setting maximum number of 12-7
-
remote domains
-
routing service requests 41
-
REPLYQ parameter 3-49
-
request queue 13-2
-
resources
-
cleaning up 23-14
-
cleaning up those associated with dead processes 23-14
-
resources, maximizing application 17-1-17-10
-
RESTART parameter 3-50
-
routing example for a five-site domain configuration 5-17
-
ROUTING parameter 7-10
-
ROUTING parameters used to distribute an application 5-15
-
RPPERM parameter 3-49
-
RQADDR parameter 3-49
-
RQPERM parameter 3-49
S
-
sanity checks and timeouts in a configuration file
-
BLOCKTIME parameter 3-19
-
example 3-19
-
SANITYSCAN parameter 3-19
-
SCANUNIT parameter 3-19
-
setting the number of 3-19
-
SANITYSCAN parameter 3-19, 17-10
-
sar(1) command options
-
-b option 17-13
-
-c option 17-13
-
-m option 17-13
-
-p option 17-13
-
-q option 17-13
-
-r option 17-14
-
-u option 17-13
-
using 17-13
-
-w option 17-13
-
SCANUNIT parameter 3-19
-
scheduling network data 6-10
-
securing applications 14-1-14-11
-
ACL's limitations 14-11
-
adding, modifying, deleting user accounts 14-8
-
adding, modifying, deleting user groups 14-9
-
configuring authentication server 14-8
-
configuring SECURITY parameter 14-5
-
determining levels of security 14-1
-
implementing application password-level security 14-6
-
implementing operating system security 14-6
-
using an authentication server 14-7
-
using shell-level commands 14-8
-
security
-
implementing application password-level 14-6
-
implementing operating system 14-6
-
security level in a configuration file
-
setting 3-21
-
SECURITY parameter
-
configuring 14-5
-
SEQUENCE parameter 3-44
-
server access to shared memory
-
characteristics of SYSTEM_ACCESS parameter 3-51
-
server command-line options 3-38
-
server environment file
-
identifying location 3-48
-
server groups
-
defining 3-31
-
sample GROUPS section 3-32
-
specifying group name, number, and LMID 3-31
-
server process information
-
identifying 3-33
-
server queue information
-
characteristics of RQADDR, RQPERM, REPLYQ, and RPPERM parameters 3-49
-
example 3-48
-
identifying 3-48
-
server restart information
-
characteristics of RESTART, RCMD, MAXGEN, and GRACE parameters 3-50
-
defining 3-50
-
servers
-
bundling services into 17-7
-
servers boot order in a configuration file
-
characteristics of SEQUENCE, MIN, and MAX parameters 3-44
-
setting 3-44
-
service parameters
-
changing 19-5
-
service parameters specification in a configuration file
-
sample INTERFACES section 3-60
-
services
-
advertising 19-4
-
unadvertising 19-4
-
SERVICES parameters used to distribute an application 5-12
-
setting domain-wide parameters
-
buffer type and subtype limits 3-18
-
defining access control 3-14
-
defining IPC limits 3-15
-
enabling load balancing 3-18
-
enabling unsolicited notification 3-21
-
identifying the master machine 3-12
-
protecting shared memory 3-23
-
setting conversation limits 3-20
-
setting parameters of unsolicited notification 3-22
-
setting the address of shared memory 3-12
-
setting the application type 3-13
-
setting the number of sanity checks and timeouts 3-19
-
setting the security level 3-21
-
shared memory
-
defining server access to 3-51
-
protecting 3-23
-
setting the address of 3-12
-
simpapp application illustrated 34
-
Single-threaded JavaServers 3-38
-
SPINCOUNT parameter 6-14
-
standard Java options 3-41
-
starting applications 4-1
-
support
-
documentation xxi
-
technical xxi
-
system components
-
replacing 23-12
-
system-wide parameters
-
overriding 3-30
T
-
tables
-
commands for monitoring TMADMIN tasks 15-14
-
TMADMIN meta-commands 15-10
-
TAGENT log
-
analyzing 16-14
-
threads 3-39
-
time(2) option 17-3
-
TLISTEN log
-
analyzing 16-15
-
message format 16-5
-
purpose 16-5
-
when created 16-5
-
TLOG 7-4, 16-1
-
analyzing 16-16
-
creating 16-8-16-13
-
how to use 16-6
-
location 16-6
-
maintaining 16-13
-
purpose 16-6
-
TLOGDEVICE parameter 7-5
-
TLOGNAME parameter 7-5
-
TLOGOFFSET parameter 7-5
-
TLOGSIZE parameter 7-5
-
TMADMIN command 15-6
-
TMADMIN meta-commands 15-9
-
tmboot(1) -c command
-
using 17-10
-
TMNETLOAD parameter 6-14
-
TMPDIR 11-5
-
TMPDIR variable 11-6
-
TMQFORWARD 13-2
-
TMQUEUE 13-2
-
TMS_QM 13-2
-
TMSCOUNT parameter 7-7
-
TMSNAME parameter 7-7
-
traffic, measuring system 17-12-17-14
-
transaction log, creating 7-4
-
transaction-related parameters in MACHINES section, defining 7-4
-
transactions
-
aborting 23-17
-
committing 23-18
-
example of distributed BEA TUXEDO application using 7-13
-
recovering from failures when using 23-18
-
sample of distributed TUXEDO application using
- GROUPS section 7-16
- MACHINES section 7-15
- NETWORK section 7-16
- RESOURCES section 7-13
- ROUTING section 7-17
- SERVERS section 7-17
- SERVICES section 7-17
-
transactions, configuring 7-1-7-17
-
AUTOTRAN parameter 7-9, 7-10, 7-13
-
CLOSEINFO parameter 7-7
-
CMTRET parameter 7-3
-
creating a transaction log
- creating the domain transaction log 7-5
- creating the Universal Device List (UDL) 7-4
- defining transaction-related parameters in MACHINES section 7-4
-
creating a transaction log (TLOG) 7-4
-
defining each resource manager and the transaction manager server in GROUPS section 7-6
-
DMTLOGDEV parameter 7-11
-
DMTLOGNAME parameter 7-12
-
DMTLOGSIZE parameter 7-12
-
enabling a TUXEDO service to begin a transaction in the SERVICES section 7-9
-
enabling an WLE interface to begin a transaction in the INTERFACES section 7-8
-
example 7-1
-
MAXGTT parameter 7-3
-
MAXRDTRAN parameter 7-12
-
MAXTRAN parameter 7-12
-
modifying the domain configuration file to support transactions 7-11
-
modifying the UBBCONFIG file 7-2
-
OPENINFO parameter 7-7
-
ROUTING parameter 7-10
-
sample GROUPS section 7-6
-
specifying application-wide transactions in RESOURCES 7-3
-
TLOGDEVICE parameter 7-5
-
TLOGNAME parameter 7-5
-
TLOGOFFSET parameter 7-5
-
TLOGSIZE parameter 7-5
-
TMSCOUNT parameter 7-7
-
TMSNAME parameter 7-7
-
transaction values description in sample GROUPS section 7-6
-
TRANTIME parameter 7-9, 7-10, 7-13
-
TRANTIME parameter 7-9, 7-10, 7-13, 17-10
-
troubleshooting applications 23-1-23-19
-
aborting a transaction 23-17
-
application failure 23-2
-
broadcasting unsolicited messages 23-4
-
checking the ULOG 23-8
-
checking WLE hostname capitalization 23-15
-
cleaning up and restarting servers 23-13
-
cleaning up resources 23-14
-
cleaning up resources associated with dead processes 23-14
-
committing a transaction 23-18
-
detecting partitioned networks 23-8
-
gathering information about network, server, and service 23-9
-
maintaining system files 23-5
- creating device list 23-5
- destroying device list 23-6
- printing the UDL 23-7
- printing the VTOC 23-7
- reinitializing a device 23-6
-
recovering from severe network failures 23-10
-
recovering from transient network failures 23-10
-
recovering when using transactions 23-18
-
repairing partitioned networks 23-7
-
replacing application components 23-13
-
restoring failed master node 23-11
-
restoring failed nonmaster node 23-11
-
restoring failed nonmaster node example 23-12
-
types of failures 23-2
-
WLE or BEA TUXEDO system failure 23-3
-
tsprio parameter 17-6
-
tuning applications 17-1-17-14
-
determining IPC requirements 17-10
-
maximizing application resources 17-1
- bundling services into servers 17-7
- enabling load balancing 17-3
-
measuring system traffic 17-12
- detecting a system bottleneck 17-12
-
using application parameters 17-8
- MAXGTT parameter 17-9
- SANITYSCAN parameter 17-9
-
using MSSQ sets in BEA TUXEDO 17-2
-
TUXCONFIG file 3-2
-
TUXDIR variable 11-5
-
TUXEDO and WLE
-
differences 1-4
-
TUXEDO conversation limits in a configuration file
-
setting 3-20
-
TUXEDO queued message facility
-
administrative tasks 13-3-13-7
-
overview 13-3-??
-
TUXEDO queued messages
-
associating queue with group 13-10
-
creating application queue space and queues 13-8
-
listing /Q servers in SERVER section 13-11
-
managing 13-1-13-11
-
modifying the configuration file 13-10
-
setting the QMCONFIG environment variable 13-7
-
using QMADMIN 13-7
-
TUXEDO services
-
resuming 19-3
-
suspending 19-3
-
TUXEDO services in a configuration file
-
identifying 3-52
-
sample SERVICES section 3-53
U
-
UBBCONFIG file 15-2
-
configuring with netgroups 3-70
-
UDL 13-7
-
printing 23-7
-
UDL (Universal Device List), creating 7-4
-
ULOG 16-1, 23-8
-
analyzing 16-14
-
assigning a location for 16-7
-
how to use 16-2
-
location 16-4
-
maintaining 16-7
-
message format 16-3
-
purpose 16-2
-
when created 16-2
-
Universal Device List (UDL), creating 7-4
-
unsolicited messages
-
broadcasting 23-4
-
unsolicited notification in a configuration file
-
characteristics of NOTIFY and USIGNAL parameters 3-22
-
setting parameters of 3-22
-
USIGNAL parameter 3-22
V
-
VTOC
-
printing 23-7
W
-
WLE and BEA TUXEDO
-
differences 1-4
-
WLE factory-based routing example 3-63
-
WLE hostname capitalization
-
checking 23-15
-
WLE interface
-
enabling to begin a transaction in the INTERFACES section 7-8
-
WLE interface repositories
-
managing 8-1
-
worker threads 3-15
-
workstation clients
-
defined 11-2
-
how to connect to an application 11-5
-
illustration of a 2-workstation client application 11-3
-
managing 11-1-11-9
-
modifying MACHINES section to support 11-9
- sample UBBCONFIG file 11-9
-
setting environment variables 11-5
-
setting number of
- MAXACCESSERS parameter 11-6
- MAXWSCLIENTS parameter 11-6
-
workstation listener (WSL), configuring 11-7
-
WSC (workstation client) 11-2
-
WSDEVICE variable 11-5
-
WSENFILE 11-5
-
WSENFILE variable 11-5
-
WSH (workstation handler) 11-2
-
WSL (workstation listener) 11-2
-
WSNADDR
-
WSDEVICE 11-5
-
WSNADDR variable 11-5
-
WSREPLYMAX variable 11-6
-
WSRPLYMAX 11-5
-
WSTYPE 11-5
-
WSTYPE variable 11-5