BEA Tuxedo Application Administration
CONF
Module
CONF Basic Tuxedo Configuration At the end of this module you will be able to • name the main sections of a Tuxedo configuration file • define the relationships between the sections of the configuration file • implement some of the commonly used configuration parameters
BEA Tuxedo Application Administration © BEA Systems, Inc.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-1
CONF-1
BEA Tuxedo Application Administration
CONF
Road Map
1. 2. 3. 4.
Tuxedo Configuration File RESOURCES & MACHINES GROUPS & SERVERS Lab Workshop
BEA Tuxedo Application Administration © BEA Systems, Inc.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-2
CONF-2
BEA Tuxedo Application Administration
CONF
Section
1
Tuxedo Configuration File
At the end of this section you will be able to • name the sections of a Tuxedo configuration file (UBBCONFIG) • define the relationships between the sections of a configuration file
BEA Tuxedo Application Administration © BEA Systems, Inc.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-3
CONF-3
BEA Tuxedo Application Administration
CONF
The Tuxedo Configuration File
The configuration file can contain up to 8 sections for ATMI applications Section
Description
*RESOURCES *MACHINES *GROUPS *SERVERS *SERVICES *ROUTING *NETGROUPS *NETWORK
Required
V\VWHPZLGHLQIRUPDWLRQ< PDFKLQHVSHFLILFLQIRUPDWLRQ< DSSOLFDWLRQVHUYHUJURXSQDPHV VHUYHUSURFHVVHVWREHERRWHG SDUDPHWHUVIRUVHUYLFHV URXWLQJFULWHULDIRU6(59,&(6 QHWZRUNJURXSVDYDLODEOHRQD/$1 QHWZRUNFRQILJIRUPXOWLSOHPF¶V
BEA Tuxedo Application Administration © BEA Systems, Inc.
CONF-4
Lines beginning with an asterisk (*) indicate the beginning of a specification section. RESOURCES - specifies system-wide resources, such as the number of machines, servers, server groups, services, and network groups that can exist within a service area. (This section is required.) MACHINES - specifies the logical names for physical machines for the configuration and parameters specific to a given machine. (This section is required.) GROUPS - defines all application server groups by group name, logical machine, and group number. (This section is optional.) SERVERS - specifies server processes to be booted in the application. (This section is optional.) Note: While the GROUPS and SERVERS sections are not mandatory, an application without these sections has no application servers and therefore little functionality unless these will be added dynamically later. A warning is issued if this section is not supplied. SERVICES - defines parameters for BEA Tuxedo services used by the application. (This section is optional but a warning is issued if this section is not supplied.) ROUTING - defines the routing criteria named in the SERVICES section for BEA Tuxedo datadependant routing. (This section is optional.) NETGROUPS - specifies the network groups available to an application LAN environment. (This section is optional.) NETWORK - describes the network configuration for a networked, multiple-machine ( LAN) environment. (This section is optional.) Tuxedo 8.0 also supports CORBA applications and another section is also supported: INTERFACES. This section has no applicability to ATMI applications and will not be discussed in this course. Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-4
BEA Tuxedo Application Administration
CONF
Formatting Requirements
The RESOURCES and MACHINES sections
must be the first two sections in that order The GROUPS section must be ahead of the SERVERS, SERVICES, and ROUTING sections The NETGROUPS section must be ahead of the NETWORK section You can specify multiple entries, each with its own selection of parameters Use DEFAULT parameter to define those parameters that are common among entries BEA Tuxedo Application Administration © BEA Systems, Inc.
CONF-5
Arrangement of Sections in the Configuration File The sections must be arranged in the file as follows: • The RESOURCES and MACHINES sections must appear as the first two sections, in that order. • The GROUPS section must precede the SERVERS , SERVICES, and ROUTING sections. • The NETGROUPS section must precede the NETWORK section.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-5
BEA Tuxedo Application Administration
CONF
How Sections are Related
5(6285&(6 DSSOLFDWLRQZLGHLQIRUPDWLRQ
0$&+,1(6 PDFKLQHZLGHLQIRUPDWLRQ
*52836 JURXSZLGHLQIRUPDWLRQ
6(59(56 VHUYHUZLGHLQIRUPDWLRQ >6HUYHU@ >6HUYHUQQ @
1(7*52836 QHWZRUNJURXSZLGHLQIRUPDWLRQ
1(7:25. QHWZRUNZLGHLQIRUPDWLRQ
6(59,&(6 DSSOLFDWLRQZLGHLQIRUPDWLRQ
5287,1* DSSOLFDWLRQZLGHLQIRUPDWLRQ
BEA Tuxedo Application Administration © BEA Systems, Inc.
CONF-6
The *RESOURCES section has broadest scope and covers entire application An application can have one or more machines, each listed in a *MACHINES section; one machine in the configuration must be designated as the “MASTER” machine. A machine can have any number of servers grouped in a *GROUPS section. Each server must be listed in the *SERVERS section.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-6
BEA Tuxedo Application Administration
CONF
Review In this section, we discussed ¾ the
structure of a Tuxedo configuration file ¾ the relationship between the sections in a Tuxedo configuration file
BEA Tuxedo Application Administration © BEA Systems, Inc.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-7
CONF-7
BEA Tuxedo Application Administration
CONF
Road Map
Tuxedo Configuration File RESOURCES & MACHINES GROUPS & SERVERS Lab Workshop
BEA Tuxedo Application Administration © BEA Systems, Inc.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-8
CONF-8
BEA Tuxedo Application Administration
CONF
Section
2 RESOURCES & MACHINES At the end of this section you will be able to • understand the use of the RESOURCES section • understand the use of the MACHINES section • configure commonly used entries in the RESOURCES and MACHINES sections
BEA Tuxedo Application Administration © BEA Systems, Inc.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-9
CONF-9
BEA Tuxedo Application Administration
CONF
Configuring the RESOURCES Section
The RESOURCES section ¾ is
a required section ¾ must appear as the first section ¾ contains system-wide parameters ¾ some parameters can be overridden on a per-machine basis in the MACHINES section
BEA Tuxedo Application Administration © BEA Systems, Inc.
CONF-10
RESOURCES is a required section and must appear as the first section in the configuration file. Some of the parameters in the RESOURCES section serve as system-wide defaults (MAXACCESSERS, MAXSERVERS) and can be overridden on a per-machine basis.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-10
BEA Tuxedo Application Administration
CONF
RESOURCES Parameters
Required (mandatory) parameters in the RESOURCES section Parameter
Description XVHGWRXQLTXHO\LGHQWLI\V\VWHP,3&UHVRXUFHV
IPCKEY MASTER MODEL
QDPHRIWKHDGPLQLVWUDWLRQPFIRUERRWDGPLQ VLQJOH 6+0 RUPXOWLSOHPDFKLQH 03 DUFKLWHFWXUH
BEA Tuxedo Application Administration © BEA Systems, Inc.
CONF-11
IPCKEY : An arbitrarily chose number between 32,769 and less than 262,142. Example: a value of 39210 indicates a number unique to this application on this system and is not being used by other applications on the system. MASTER : The administration site (MASTER ) for boot and shutdown. In a single machine (SHM) MODEL application, the single/only machine is the MASTER. The logical machine ID (LMID) of the machine is specified. MODEL : Application architecture, indicating a single machine or multiple machine application. The parameter value SHM indicates a single machine. MP Indicates that this application has more than one machine in the configuration.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-11
BEA Tuxedo Application Administration
CONF
IPCKEY Parameter
IPCKEY ¾ is
used to allocate resources like the Bulletin Board, semaphores and message queues ¾ must be unique among applications ¾ must be in the range between 32,769–262,142 UBBCONFIG
*RESOURCES IPCKEY 39211 ...
BEA Tuxedo Application Administration © BEA Systems, Inc.
CONF-12
The IPCKEY parameter is used by the Tuxedo system allocate system IPC resources. This key and its variations are used internally to allocate the Bulletin Board, message queues, and semaphores that must be made available to new application processes. In a single processor mode, this key identifies the Bulletin Board. The IPCKEY parameter must be unique in that no other application on the system should use this specific value as an identifier for IPC resources.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-12
BEA Tuxedo Application Administration
CONF
MASTER Parameter
MASTER ¾ specifies
the logical machine name of the machine that will assume the administration role for booting and shutting down ¾ logical machine names are mapped to real machine names in the MACHINES section ¾ in a multiple machine configuration, a second machine can be specified as a backup to the master machine UBBCONFIG
*RESOURCES MASTER ...
SITE1[,SITE2]
BEA Tuxedo Application Administration © BEA Systems, Inc.
CONF-13
You must specify a master machine (MASTER) for all configurations. The master machine controls the booting and administration of the entire application. This machine is specified using a Logical Machine Identifier (LMID). The LMID is an alphanumeric string chosen by the Administrator. In a multiple-machine configuration, two LMIDs can be specified when it is required to back up the master machine, either when the master machine fails or when the master machine needs to be shutdown for some planned event such as system maintenance.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-13
BEA Tuxedo Application Administration
CONF
MODEL Parameter
MODEL - for single machine applications ¾ MP - for networked connected, multiple machine configurations ¾ SHM
OPTIONS is set to LAN if MODEL=MP UBBCONFIG
*RESOURCES MODEL SHM ...
BEA Tuxedo Application Administration © BEA Systems, Inc.
CONF-14
Among some of the application architecture decisions needed for a Tuxedo application are the following: • Will this application run on a single machine ? • Will the application be networked multiple machines ? The MODEL parameter is a required parameter and specifies whether an application runs on a single processor or multiple machines. MODEL: A value of SHM indicates a single machine, single processor or multi-processor with global shared memory. A value of MP indicates multiple machines or a loosely coupled multiprocessor system. OPTIONS: It is a comma-separated list of application configuration options. A value of LAN indicates a local area network and is required if MODEL is set to MP.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-14
BEA Tuxedo Application Administration
CONF
Resources
Various tables are kept in the Bulletin Board and hold information os servers,... ; some tables sizes are based on configuration parameters Parameter MAXACCESSERS MAXSERVERS MAXSERVICES
Description
Range Def
0D[LPXPQXPEHURISURFHVVHV 0D[RIVHUYHUVDGPLQDQGXVHU 0D[LPXPQXPEHURIVHUYLFHV
*RESOURCES MAXACCESSERS MAXSERVERS MAXSERVICES ...
UBBCONFIG
75 40 55
BEA Tuxedo Application Administration © BEA Systems, Inc.
CONF-15
The BBL process maintains a system IPC memory segment (Bulletin Board) that contains various Tuxedo-related tables. Some table sizes are based on configured Tuxedo Resource Parameters and impact the size of the allocated system memory. As the shared memory segment (Bulletin Board tables) is statically allocated for fast processing, it is important to size it efficiently. If the Tuxedo resource tables are sized too generously, extra memory and IPC resources will be unused; if they are set too small, application processes will fail when the limits are exceeded. The following tunable parameters are related to IPC sizing in the RESOURCES section: MAXACCESSERS : The maximum limit to the number of clients and servers that can be simultaneously supported on any particular machine. Example: a value of 40 allows up to 40 active clients and server processes per machine for this application. If not specified, the default is 50. MAXSERVERS : The maximum limit for the number of server processes in the application, including all the administrative servers (for example, BBL and TMS). . Example: a value of 20 allows up to 20 active server processes for this application. If not specified, the default is 50. MAXSERVICES : The maximum limit for the number of services offered. Example: a value of 25 allows up to 25 services to be advertised. If not specified, the default is 100. The general idea for these parameters is to allow for current application implementation and future growth of the application. The value of MAXACCESSERS is especially important.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-15
BEA Tuxedo Application Administration
CONF
Sanity Checks
The BBL periodically checks sanity of servers on its machine Parameter SCANUNIT SANITYSCAN BLOCKTIME
Description
Default
VHWVWKHJUDQXODULW\RIFKHFNVLQVHFRQGV VHF 0XVWEHDPXOWLSOHRIVHFV VHFRQGVEHWZHHQVDQLW\FKHFNVRIVHUYHUV VHF SANITYSCAN * SCANUNIT < SHULRGDPHVVDJHEORFNVEHIRUHWLPLQJRXW VHF BLOCKTIME * SCANUNIT < UBBCONFIG
*RESOURCES SCANUNIT SANITYSCAN BLOCKTIME
10 3 1
# 10 seconds # 3 * 10 = 30 seconds # 1 * 10 = 10 seconds BEA Tuxedo Application Administration © BEA Systems, Inc.
CONF-16
You can set the number of times the administrative server (BBL) will periodically check the sanity of servers local to its machine. In addition, you can set the number of timeout periods for blocking messages, and other system activities. The SCANUNIT parameter is used to control the granularity of such checks and timeouts. Its value (in seconds) can be a positive multiple of 5. Its default is 10. You use the SANITYSCAN parameter to specify how many SCANUNITs elapse between sanity checks of the servers. The value of SANITYSCAN * SCANUNIT cannot exceed 300. The default value of SANITYSCAN * SCANUNIT is approximately 120 seconds. A SCANUNIT of 10 and a BLOCKTIME of 3 allows 30 seconds before the client application times out. The BLOCKTIME default is set so that BLOCKTIME * SCANUNIT is approximately 60 seconds. The time is a total of the following times: Time waiting to get on the queue, Time waiting on the queue, Time for service processing, Time on the network. The SCANUNIT, SANITYSCAN, and BLOCKTIME parameters have the following characteristics: • SCANUNIT Establishes granularity of check intervals and timeouts. Value must be in multiples of 5 seconds. Example: SCANUNIT 20. • SANITYSCAN Frequency at which the BBL checks the server (in SCANUNIT intervals). SCANUNIT * SANITYSCAN must not exceed 300. The default of SCANUNIT * SANITYSCAN is approximately 120 seconds. Example: SANITYSCAN 3. • BLOCKTIME Timeout for blocking messages. SCANUNIT * BLOCKTIME must not exceed 300. The default of SCANUNIT * BLOCKTIME is approximately 60 seconds. Example: BLOCKTIME 1.
Copyright © BEA Systems, Inc.
.
All Rights Reserved. Unauthorized Duplication Prohibited
CONF-16
BEA Tuxedo Application Administration
CONF
Some Other RESOURCE Parameters
A general look at some other commonly used parameters; we will be discussing some of these in more detail later Parameter OPTIONS SECURITY AUTHSVC SYSTEM_ACCESS LDBAL NOTIFY SIGNAL
Description YDULRXVRSWLRQVVRPHDVVRFLDWHGZLWK03PRGH OHYHORIVHFXULW\ QDPHRIDSSOLFDWLRQDXWKHQWLFDWLRQVHUYLFH PRGHWRDFFHVV%($7X[HGRLQWHUQDOWDEOHV ORDGEDODQFLQJ GHIDXOWPHWKRGIRUSURFHVVLQJXQVROLFLWHGPHVVDJHV VLJQDOWREHXVHGIRU127,)
