|
|
Monitoring a Running System
After your application is up and running, as an administrator you must ensure that it meets the performance, availability, and security standards of your company. To perform this task, you need to monitor the resources (such as shared memory), activities (such as transactions), and potential problems (such as security breaches) in your configuration, and take any corrective actions that are necessary.
To help you meet this responsibility, the BEA WebLogic Enterprise and BEA Tuxedo systems provide tools that enable you to oversee both system events and application events. This chapter explains how to use these tools to keep your application performing fast, correctly, and securely.
This topic includes the following sections:
Overview of System and Application Data
This section describes the types of data available for monitoring a running system and explains how to use that data.
Components and Activities for Which Data Is Available
Your BEA WebLogic Enterprise or BEA Tuxedo system maintains parameter settings and generates statistics for the following system components:
To ensure that you have the information necessary for monitoring your system, the BEA WebLogic Enterprise or BEA Tuxedo system provides the following data repositories:
This chapter describes the data stored in the UBBCONFIG file and in the Bulletin Board, and provides instructions for monitoring that data. For a description of the log files, see Monitoring Log Files.
How You Can Use the Data
The administrative data provided by your BEA WebLogic Enterprise or BEA Tuxedo system lets you monitor a multitude of potential trouble areas on your system. For example, this data lets you:
You can also set up your system so that it is able to use the statistics in the Bulletin Board to make decisions and to modify system components dynamically, without user intervention. With proper configuration, your system may be able to perform tasks such as the following (when indicated by Bulletin Board statistics):
Thus, by monitoring the administrative data for your system, you can prevent and resolve problems that threaten the performance, availability, and security of your application.
Static and Dynamic Data
There are two types of administrative data available on every running BEA WebLogic Enterprise and BEA Tuxedo system: static and dynamic.
Static Data
Static data consists of configuration settings that you assign when you first configure your system and application. These settings are never changed without intervention (either in realtime or through a program you have provided). Examples include system-wide parameters (such as the number of machines being used) and the amount of IPC resources (such as shared memory) that is allocated to your system on your local machine. Static data is kept in the UBBCONFIG file and in the Bulletin Board.
At times you will need to check the static data about your configuration. For example:
Dynamic data consists of information that changes in realtime, that is, while an application is running. For example, the load (the number of requests sent to a server) and the state of various configuration components (such as servers) change frequently. Dynamic data is kept in the Bulletin Board and in JavaServers and the Active Object Map (AOM).
You will need to check the dynamic data about your configuration frequently. For example:
These numbers will help you determine whether adding more servers is likely to improve performance.
Monitoring Methods
To monitor a running application, you need to keep track of the dynamic aspects of your configuration and sometimes check the static data. Thus, you need to be able to watch the Bulletin Board on an ongoing basis and consult the UBBCONFIG file when necessary. Both the BEA WebLogic Enterprise and BEA Tuxedo systems provide the following ways to monitor this data, as shown in the following table.
You Can Use the . . . |
By . . . |
For Instructions, See . . . |
---|---|---|
tmadmin command |
Entering commands after a prompt |
This chapter |
AdminAPI |
Using the MIB (and the commands described in this chapter) to write programs that monitor your run-time application |
Chapter 21, "Event Broker/Monitor (BEA Tuxedo Systems)" BEA Tuxedo Reference Manual, Section 5 |
BEA Administration Console Web-based GUI |
Using a graphical interface |
The Help accessed directly from the GUI |
The preferred method depends on your level of experience and the type of information you need to view.
If you are an experienced administrator (and have shell programming expertise), you may prefer to write programs that automate your most frequently run commands.
If you are not an experienced UNIX user, you may be most comfortable using the Web-based GUI.
If you examine the RESOURCES section of the UBBCONFIG file using the tmadmin command, you can see only the current values; the defaults are not displayed.
If you decide to monitor your system at run time using the tmadmin command interpreter, continue reading; this chapter describes tmadmin and explains how to use it.
Using the tmadmin Command Interpreter
The tmadmin command is an interpreter for a large set of commands that let you view and modify a Bulletin Board and its associated entities.
Note: tmadmin is supported on UNIX and Windows NT platforms.
This section provides step-by-step information about:
Detailed instructions for individual tasks are provided in later sections of this chapter.
How might you want to use tmadmin to modify your system while it is running? Consider the following sample scenario. Suppose you want to check the current values for all the parameters listed in the Bulletin Board, such as maximum number of servers and services. You can do this by running the tmadmin command, bbparms.
$ tmadmin [operating_mode_option]
>
You can request one of three operating modes on the command line: the default mode (which allows you to view and change the Bulletin Board and associated entities), read-only mode (-r), or configuration mode (-c).
No bulletin board exists. Entering boot mode
>
Not all tmadmin commands are available on every machine at all times. Which commands are available depends on several factors:
For details, see the tmadmin(1) reference page in the BEA Tuxedo Reference Manual.
tmadmin Options
Whenever you start a tmadmin session, you have a choice of operating modes for that session: read-only mode, configuration mode, or the default operating mode. You can also generate a report of the BEA WebLogic Enterprise or BEA Tuxedo version and license numbers.
Read-only Mode
In this mode, you can view the data in the Bulletin Board, but you cannot make any changes. The advantage of working in read-only mode is that your administrator process is not tied up by tmadmin; the tmadmin process attaches to the Bulletin Board as a client, leaving your administrator slot available for other work.
To start a tmadmin session in read-only mode, specify the -r option on the command line:
$ tmadmin -r
Configuration Mode
In this mode, you can view the data in the Bulletin Board and, if you are the BEA Tuxedo application administrator, you can make changes. You can start a tmadmin session in configuration mode on any machine, including an inactive machine. On most inactive machines, configuration mode is required. (The only inactive machine on which you can start a tmadmin session without requesting configuration mode is the MASTER machine.)
To start a tmadmin session in configuration mode, specify the -c option on the command line:
$ tmadmin -c
Default Operating Mode
If you want to view and change Bulletin Board data during a tmadmin session, you must:
$ tmadmin
Version Number and License Number Report
To find out which version of the BEA WebLogic Enterprise or BEA Tuxedo system you are running and to get the license number for it, specify the -v option on the command line:
$ tmadmin -v
After displaying the version and license numbers, tmadmin exits, even if you have specified -c or -r in addition to -v. When -v is requested, all other options are ignored.
tmadmin Metacommands
The tmadmin command interpreter is equipped with a set of metacommands, commands that help you use tmadmin. Table 15-1 lists the tmadmin metacommands.
Note: The tables and examples in this chapter include the abbreviated forms of the tmadmin command names.
Use This Command |
Or Its Abbreviation |
To... |
---|---|---|
default |
d |
Set defaults for arguments of other commands. |
dump |
du |
Download the current Bulletin Board into a file. |
echo |
e |
Display input command lines. |
help |
h |
Display command list or command syntax. |
paginate |
page |
Pipe output of commands to a pager. |
quit |
q |
Terminate the session. |
verbose |
v |
Show output in verbose mode (a toggle key). |
!shlcmd |
(n/a) |
Escape to the shell and run the specified shell command. |
!! |
(n/a) |
Repeat the previous shell command. |
<RETURN> |
(n/a) |
Repeat the last tmadmin command. |
The default metacommand (d) lets you set and unset defaults for the following frequently used parameters for most tmadmin commands: group name, server ID, machine, username, client name, queue address, service name, device blocks, device offset, JDBC connection pool name, and UDL configuration device path. For details, see the tmadmin(1) reference page in the BEA Tuxedo Reference Manual.
Note: You cannot assign defaults to any parameters for the boot and shutdown commands.
After defaults are set, they remain in effect until the session ends or until the parameters are reset to different values. The remainder of this section provides a list of instructions for checking, setting, and unsetting defaults.
Listing 15-1 Default Output
> d
Default Settings:
Group Name: (not set)
Server ID: (not set)
Machine ID: (not set)
Queue Name: (not set)
client Name: (not set)
Service Name: (not set)
User Name: (not set)
Conn Pool Name: (not set)
Blocks: 1000
Offset: 0
Path: (not set)
>
default -parameter new_value
For example, to change the default of the service name to "teller," enter the following command:
default -s teller
default -parameter *
For example, to unset the default for the service name (specified with the -s argument), enter the following command:
default -s *
For most parameters, when you unset the default setting without specifying a new one, the result is that you have no default for that parameter. This generalization does not apply to the machine ID parameter, however.
In a multiprocessor environment, the value of the machine ID can be a specific processor, the DBBL, or all. If the value of the machine ID is a specific processor, information is retrieved only from that processor. To remind you of this fact, the logical machine ID is added to the tmadmin session prompt (LMID >), as shown in Listing 15-2.
Listing 15-2 Prompt When Machine ID Is Set to a Specific Processor
# 1. default mid not previously set
> d -m SITE1 # 2. set SITE1 as default mid
SITE1 > # 3. prompt now shows default mid
If you unset the current default of the machine ID without specifying a new default, the DBBL is used automatically as the new default. In other words, if you enter:
default -m *
DBBL becomes the machine ID. You can also simply specify DBBL as the new machine by entering the following:
default -m DBBL
Optional and Required Arguments
Most tmadmin commands require explicit information about the resource on which the command is to act. Required arguments can always be specified on the command line, and can often be set via the default command, as well. tmadmin reports an error if the required information is not available from either source.
Some tmadmin statistical commands interpret unspecified default parameters as all.
Running tmadmin Commands
This section provides the basic procedure for running tmadmin commands. Commands for doing specific monitoring tasks through tmadmin are provided in the section Monitoring a Running System with tmadmin in this chapter.
Note: For complete details about tmadmin, see the tmadmin(1) reference page in the BEA Tuxedo Reference Manual.
To run the tmadmin commands:
tmadmin_command -v
For example: bbparms -v
tmadmin_command -t
For example: printjdbcconnpool -t
quit
Monitoring a Running System with tmadmin
Table 15-2 provides a list of potential problems that you might want to check while monitoring your run-time system, along with a list of the tmadmin commands that enable you to perform such a check. The table also suggests follow-up actions you might take if the tmadmin command you run generates a particular type of output.
Note: For a comprehensive list of the tmadmin commands, see the tmadmin(1) reference page in the BEA Tuxedo Reference Manual.
.
To Determine |
Run This Command . . . |
If . . . |
Then . . . |
---|---|---|---|
Any servers are stalled in a service. |
$ tmadmin -r |
The Current Service and Request fields do not change. |
The server is spending excessive time on the current service. In a development environ- ment, the server might be stalled in an infinite loop; you may want to stop it. |
The load distribution is appropriate. |
$ tmadmin -r |
The values in the Load Done field are not reasonably similar. |
Check the layout of the MSSQs and the data-dependent routing. If the current servers have too heavy a load, you may want to boot more servers. |
A particular service is doing any work. |
$ tmadmin -r |
The value in the Requests Completed field is 0. |
Data-dependent routing may be preventing requests from being sent to that server for that service. You can:
|
An interface is doing any work. |
tmadmin -r |
The value in the Requests Done field is 0. |
Factory-based routing may be preventing requests from being sent to that server for that interface. You can:
|
The number of active objects is approaching the limit. |
tmadmin -r |
The number of active objects reported by the bbstats command is close to the maximum number of objects as reported by the bbparms command. |
You may need to increase the number of maximum objects. |
An object is hung or slow in processing requests. |
tmadmin -r |
The value of the Reference Count field is greater than 1. |
Clients are waiting for requests. The object may be hung or overloaded. You may need more objects performing functions currently assigned to this object. |
Any clients are inactive. |
$ tmadmin -r |
|
Tell the client-via a broadcast message-to exit. |
The work is distributed in such a way that it is flowing smoothly through the system. |
$ tmadmin -r |
Some queues are always heavy and others are not. |
Check the arrangement of services within servers, data-dependent routing, and/or queue organization. |
A client is tying up a connection and preventing a server from doing any work for another client. |
$ tmadmin -r |
A client is maintaining control of a connection and is not issuing any requests. |
|
A JDBC connection pool is overloaded. |
$tmadmin -v |
The high-water mark (HWM) of connections in use is at or close to the maximum size, or connections in use is close to the maximum size and clients are waiting. |
You may want to expand the maximum size of the pool. |
The network is stable. |
$ tmadmin -r |
A machine is no longer connected. |
You may want to:
|
You must manually commit or abort a transaction. |
$ tmadmin -r |
For example, the status is TMGDECIDED. |
The first phase of the two-phase commit has completed successfully. This means you must find out why the second phase cannot be completed. |
Your operating system resources (such as shared memory and semaphores) on a local machine are sufficient. |
$tmadmin -r |
You do not have sufficient resources in the operating system. |
Increase the IPC resources (semaphores, shared memory segments, and so on) in the operating system. |
You want to keep the current values for system-wide parameters (in the RESOURCES section of your UBBCONFIG file). |
$ tmadmin -r |
You do not have sufficient resources for your application. |
|
Example: Output from tmadmin Commands
This section provides examples of output from the following tmadmin monitoring commands:
Note: For a list of all 50 tmadmin commands, see the tmadmin(1) reference page in the BEA Tuxedo Reference Manual.
Listing 15-3 shows output from the printqueue command lets you check the distribution of work in the bankapp application.
Listing 15-3 Printqueue Command Output
printqueue [qaddress]
tmadmin - Copyright © 1996-1999 BEA Systems, Inc.
Portions* Copyright 1986-1997 RSA Data Security, Inc.
>printqueue
Prog Name |
Queue Name |
# Serve |
Wk Queued |
# Queued |
Ave. Len |
Machine |
TLR TLR |
28706 28706 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
TMS_SQL TMS_SQL |
BANKB1_T BANKB1_T |
2 2 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
TLR TLR |
24946 24946 |
1 1 |
0 0 |
0 0 |
0.1 0.1 |
SITE1 SITE1 |
BAL BAL |
8533 8533 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
BAL BAL |
24915 24915 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
BTADD BTADD |
28897 28897 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
XFER XFER |
4380 4380 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
XFER XFER |
28840 28840 |
1 1 |
100 100 |
0 0 |
1.0 1.0 |
SITE1 SITE1 |
TLR TLR |
12519 12519 |
1 1 |
100 100 |
2 2 |
0.0 0.0 |
SITE1 SITE1 |
BBL BBL |
24846 24846 |
1 1 |
0 0 |
2 2 |
0.0 0.0 |
SITE1 SITE1 |
ACCT ACCT |
71 71 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
TMS_SQL TMS_SQL |
BANKB3_T BANKB3_T |
2 2 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
BAL BAL |
28958 28958 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
ACCT ACCT |
254 254 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
BTADD BTADD |
12310 12310 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
XFER XFER |
16494 16494 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
TMS_SQL TMS_SQL |
BANKB2_T BANKB2_T |
2 2 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
BTADD BTADD |
8430 8430 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
ACCT ACCT |
24641 24641 |
1 1 |
0 0 |
0 0 |
0.0 0.0 |
SITE1 SITE1 |
Note: By default, information is supplied for all queues. If you want your output to be limited to information about only one queue, specify the address for the desired queue.
The output of this command includes the following information:
In the Column Labeled . . . |
You See . . . |
---|---|
Prog Name |
The name of the executable to which the queue is connected. |
Queue Name |
The symbolic queue name (set to either the RQADDR parameter of UBBCONFIG or a randomly chosen value). |
# Serve |
The number of servers connected to the queue. |
Wk Queued |
The load factor of all requests currently queued. |
# Queued |
The actual number of requests queued. |
Ave. Len |
The average queue length. Not available in MP mode. |
Machine |
The LMID of the machine on which the queue is located. |
Listing 15-4 shows verbose output from the printconn command shows that the client process has:
Listing 15-4 Printconn Command Output
printconn [-m machine]
tmadmin - Copyright © 1996-1999 BEA Systems, Inc.
> echo
Echo now on.
> v
Verbose now on.
> pc
Originator
Group/pid: Client/29704
LMID: SITE1
Sends: 0
Subordinate
Group/server id: Group1/2
LMID: SITE1
Sends: -
Service: TOUPPER1
Originator
Group/pid: Client/29704
LMID: SITE1
Sends: 0
Subordinate
Group/server id: Group1/2
LMID: SITE1
Sends: -
Service: TOUPPER2
Listing 15-5 shows the output from the following procedure.
Listing 15-5 Printnet Command Output
printnet [-m machine_list]
tmadmin - Copyright © 1996-1999 BEA Systems, Inc. All rights reserved.
> echo
Echo now on.
> pnw
SITE1 Connected To: msgs sent msgs received
SITE2 100103
SITE2 Connected To: msgs sent msgs received
SITE1 104 101
> pnw
SITE1 Connected To: msgs sent msgs received
Could not retrieve status from SITE2
>
printtrans Command Output
The printtrans command reports statistics only for transactions that are currently in progress, specifically, statistics on the number of rollbacks, commits, and aborts that have been executed on your machine, group, or server.
Listing 15-6 shows the output produced by running the printtrans command in both terse and verbose modes:
Note: The index shown in the example is used by the administrator to commit or abort the transaction.
Listing 15-6 Printtrans Command Output
printtrans [-m machine] [-g groupname]
tmadmin - Copyright © 1996-1999 BEA Systems, Inc.
Portions* Copyright 1986-1997 RSA Data Security, Inc.
All rights reserved.
> printtrans
>> index=0>gtrid=x0 x2bb8f464 x1
: Machine id: SITE1, Transaction status: TMGACTIVE
Group count: 1
> v
Verbose now on.
> pt
>> index=0>gtrid=x0 x2bb8d464 x1
: Machine id: SITE1, Transaction status: TMGACTIVE
Group count: 1, timeout: 300, time left: 299
Known participants:
group: GROUP1, status: TMGACTIVE, local, coord
>
printjdbcconnpool Command Output
The printjdbcconnpool command reports statistics on JDBC connection pools such as the maximum number of connections per pool, the number of connections in use, the number of clients waiting for a connection, and the high-water mark or highest number of connections used for a pool.
Listing 15-7 shows the output produced by running the printjdbcconnpool command in terse and verbose modes. In terse mode the maximum pool size, the current pool size, and the number of connections currently in use are shown. In verbose mode the number of clients waiting and the high-water mark are also shown.
Listing 15-7 Printjdbcconnpool Command Output
>printjdbcconnpool
Pool Name Grp Name Srv Id Size Max Size Used
----------- ---------- ------ ---- -------- ----
ejbPool J_SRVGRP 101 1 15 0
Pool2 J_SRVGRP 102 10 30 3
Listing 15-8 shows is the verbose mode output for a single connnection pool:
Listing 15-8 Printjdbcconnpool Command Verbose Mode Output
Pool Name: Pool2
Group ID: J_SRVGRP
Server ID: 102
Driver: (none)
URL: (none)
Database Name: Db
User: leia
Host: SITE1
Password: mypwd
Net Protocol: odbc
Port: 120
Props: (none)
Enable XA: No
Create On Startup: Yes
Pool Size: 10
Maximum Size: 30
Capacity increment: 3
Allow shrinking: Yes
Shrink interval: 10 min(s)
Login delay: 1 sec(s)
Connections in use: 3
Connections awaiting: 0
HWM connections in use: 5
Test table: testtable
Refresh interval: 20 sec(s)
Test conn OnReserve: Yes
Test conn OnRelease: No
Case Study: Monitoring Run-time bankapp
This section presents a sample configuration for a multiprocessor (MP) version of the bankapp application. This section also shows the output that was returned when the local IPC resources and system-wide parameters were checked by running the appropriate tmadmin commands.
Configuration File for bankapp
For this case study, we will use the configuration defined in the UBBCONFIG file shown in Listing 15-9.
Listing 15-9 UBBCONFIG File for bankapp (MP Version)
#Copyright (c) 1997, 1998 BEA Systems, Inc.
#All rights reserved
*RESOURCES
IPCKEY 80952
UID 4196
GID 601
PERM 0660
MAXACCESSERS 40
MAXSERVERS 35
MAXSERVICES 75
MAXCONV 10
MAXGTT 20
MASTER SITE1,SITE2
SCANUNIT 10
SANITYSCA
12
BBLQUERY 180
BLOCKTIME 30
DBBLWAIT 6
OPTIONS LAN,MIGRATE
MODEL MP
LDBAL Y
#
*MACHINES
mchn1 LMID=SITE1
TUXDIR="/home/tuxroot"
APPDIR="/home/apps/bank"
ENVFILE="/home/apps/bank/ENVFILE"
TLOGDEVICE="/home/apps/bank/TLOG"
TLOGNAME=TLOG
TUXCONFIG="/home/apps/bank/tuxconfig"
TYPE="3B2"
ULOGPFX="/home/apps/bank/ULOG"
wgs386 LMID=SITE2
TUXDIR="/home2/tuxroot"
APPDIR="/home2/apps/bank"
ENVFILE="/home2/apps/bank/ENVFILE"
TLOGDEVICE="/home2/apps/bank/TLOG"
TLOGNAME=TLOG
TUXCONFIG="/home2/apps/bank/tuxconfig"
TYPE="386"
ULOGPFX="/home2/apps/bank/ULOG"
#
*GROUPS
DEFAULT: TMSNAME=TMS_SQL TMSCOUNT=2
# For NT/Netware, :bankdb: becomes ;bankdb;
BANKB1 LMID=SITE1 GRPNO=1
OPENINFO="TUXEDO/SQL:/home/apps/bank/bankdl1:bankdb:readwrite"
BANKB2 LMID=SITE2 GRPNO=2
OPENINFO="TUXEDO/SQL:/home2/apps/bank/bankdl2:bankdb:readwrite"
*NETWORK
SITE1 NADDR="//mach1.beasys.com:1900"
BRIDGE="/dev/tcp"
NLSADDR="//mach1.beasys.com:1900"
SITE2 NADDR="//mach386.beasys.com:1900"
BRIDGE="/dev/tcp"
NLSADDR="//mach386.beasys.com:1900"
*SERVERS
#
DEFAULT: RESTART=Y MAXGEN=5 REPLYQ=Y CLOPT="-A"
TLR SRVGRP=BANKB1 SRVID=1 RQADDR=tlr1 CLOPT="-A -- -T 100"
TLR SRVGRP=BANKB1 SRVID=2 RQADDR=tlr1 CLOPT="-A -- -T 200"
TLR SRVGRP=BANKB2 SRVID=3 RQADDR=tlr2 CLOPT="-A -- -T 600"
TLR SRVGRP=BANKB2 SRVID=4 RQADDR=tlr2 CLOPT="-A -- -T 700"
XFER SRVGRP=BANKB1 SRVID=5
XFER SRVGRP=BANKB2 SRVID=6
ACCT SRVGRP=BANKB1 SRVID=7
ACCT SRVGRP=BANKB2 SRVID=8
BAL SRVGRP=BANKB1 SRVID=9
BAL SRVGRP=BANKB2 SRVID=10
BTADD SRVGRP=BANKB1
BTADD SRVGRP=BANKB2 SRVID=12
AUDITC SRVGRP=BANKB1 SRVID=13 CONV=Y MIN=1 MAX=10
BALC SRVGRP=BANKB1 SRVID=24
BALC SRVGRP=BANKB2 SRVID=25
#
*SERVICES
DEFAULT: LOAD=50 AUTOTRAN=N
WITHDRAWAL PRIO=50 ROUTING=ACCOUNT_ID
DEPOSIT PRIO=50 ROUTING=ACCOUNT_ID
TRANSFER PRIO=50 ROUTING=ACCOUNT_ID
INQUIRY PRIO=50 ROUTING=ACCOUNT_ID
CLOSE_ACCT PRIO=40 ROUTING=ACCOUNT_ID
OPEN_ACCT PRIO=40 ROUTING=BRANCH_ID
BR_ADD PRIO=20 ROUTING=BRANCH_ID
TLR_ADD PRIO=20 ROUTING=BRANCH_ID
ABAL PRIO=30 ROUTING=b_id
TBAL PRIO=30 ROUTING=b_id
ABAL_BID PRIO=30 ROUTING=b_id
TBAL_BID PRIO=30 ROUTING=b_id
ABALC_BID PRIO=30 ROUTING=b_id
TBALC_BID PRIO=30 ROUTING=b_id
*ROUTING
ACCOUNT_ID FIELD=ACCOUNT_ID
BUFTYPE="
Output from Checking the Local IPC Resources
To check the local IPC resources for this configuration, a tmadmin session was started, and the bbsread command was run. The output of bbsread is shown in Listing 15-10.
Listing 15-10 bbsread Output
SITE1> bbsread
IPC resources for the bulleti
board o
machine SITE1:
SHARED MEMORY: Key: 0x1013c38
SEGMENT 0:
ID: 15730
Size: 36924
Attached processes: 12
Last attach/detach by: 4181
This semaphore is the system semaphore
SEMAPHORE: Key: 0x1013c38
Id: 15666
| semaphore | current | last | # waiting |
| number | status | accesser | processes |
|----------------------------------------------|
| 0 | free | 4181 | 0 |
|------------|----------|----------|-----------|
This semaphore set is part of the user-level semaphore
SEMAPHORE: Key: IPC_PRIVATE
Id: 11572
| semaphore | current | last | # waiting |
| number | status | accesser | processes |
|----------------------------------------------|
| 0 | locked | 4181 | 0 |
| 1 | locked | 4181 | 0 |
| 2 | locked | 4181 | 0 |
| 3 | locked | 4181 | 0 |
| 4 | locked | 4181 | 0 |
| 5 | locked | 4181 | 0 |
| 6 | locked | 4181 | 0 |
| 7 | locked | 4181 | 0 |
| 8 | locked | 4181 | 0 |
| 9 | locked | 4181 | 0 |
| 10 | locked | 4181 | 0 |
| 11 | locked | 4181 | 0 |
| 12 | locked | 4181 | 0 |
| 13 | locked | 4181 | 0 |
|------------|----------|----------|-----------|
Note: The display is the same with verbose mode on or off.
Output from Checking System-wide Parameter Settings
To check the current values of the system-wide parameters for this configuration, we started a tmadmin session and ran the bbparms command. The output of bbparms is shown in Listing 15-11.
Listing 15-11 Sample bbparms Output
> bbparms
Bulletin Board Parameters:
MAXSERVERS: 50
MAXSERVICES: 100
MAXACCESSERS: 50
MAXGTT: 100
MAXCONV: 1
MAXBUFTYPE: 16
MAXBUFSTYPE: 32
MAXOBJECTS: 1000
MAXINTERFACES: 150
IPCKEY: 35384
MASTER: SITE1,SITE2
MODEL: MP
LDBAL: Y
OPTIONS: LAN,MIGRATE
SCANUNIT: 10
SANITYSCAN: 12
DBBLWAIT: 6
BBLQUERY: 30
BLOCKTIME: 6
Shared Memory ID: 0
Note: The display is the same with verbose mode on or off.
Copyright © 2000 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.