Creating and Configuring Core Administrative Resources

The Oracle Tuxedo system core administrative resources consist of both ATMI and CORBA domains and their associated resources. The Oracle Administration Console enables the system administrator to manage the core Oracle Tuxedo ATMI resources for configuration and run-time administration.

Note:

For detailed instructions on creating and configuring Oracle Tuxedo CORBA administrative resources, refer to Chapter 8, “Creating and Configuring Tuxedo CORBA Resources.”

The following help topics define the fields for the Create New Object window and Configuration Tool tab pages when creating or configuring the Oracle Tuxedo ATMI administrative resources.

This topic includes the following sections:

•

Domains

•	Opening an Existing Domain

•	Creating a New Domain

•	Configuring Domain Resources (T_DOMAIN Class)

•

Machines

•	Creating Machines

•	Configuring Machines (T_MACHINE Class)

•	Transactions

•	Configuring Transactions (T_TRANSACTION Class)

•

Groups

•	Creating Groups

•	Configuring Groups (T_GROUP Class)

•

Servers

•	Creating Servers

•	Routing Tables

•	Creating Routing Tables

•	Configuring Routing Tables (T_ROUTING Class)

•	Service Defaults

•	Creating Service Defaults

•	Configuring Service Defaults (T_SERVICE Class)

•

Services

•	Creating Services

•	Configuring Services (T_SVCGRP Class)

•

Devices

•	Creating Devices

•	Configuring Devices (T_DEVICE Class)

•

Clients

•	Configuring Clients (T_CLIENT Class)

•

Bridges

•	Configuring Bridges (T_BRIDGE Class)

 

Note:

Descriptions fields that do not allow you to enter text or make a choice of entries are described briefly.

Opening an Existing Domain

<a name="C_DOMAIN"></a>

To open an existing domain, select Domain—>DomainName from the menu bar.

Figure 4‑1 shows a sample domain menu listing the simple domain.

Figure 4‑1 Sample Domain Menu

Table 4‑1 describes the other Domain menu options.

 

Table 4‑1 The Other Domain Menu Options

Menu Option	Description
New	Creates a new domain. Use this option if the domain you want is not listed on the menu. After clicking on New, enter the pathname of the tuxconfig file for your domain. The GUI will then invoke the specified domain and add its name to the menu for future reference.
Open	Displays an existing domain that is not listed on the menu.
simple	Opens and displays the domain called simple in the tree view.

Creating a New Domain

<a name="T_DOMAIN"></a>

<a name="C_DOMAIN"></a>

<a name="N_DOMAIN"></a>

Using the Oracle Tuxedo Administration Console applet, you can perform all of the administrative tasks required to manage a Oracle Tuxedo domain.

To create a new domain, select Domain—>New from the menu bar to display the Create New Object window as shown in Figure 4‑2. (You can also select an existing domain in the tree and select Quick Menu—>New.)

Figure 4‑2 Create New Object Window for a Domain

Enter values for the following fields:

•	Domain ID (TA_DOMAINID)

•	IPC Key (TA_IPCKEY)

•	Master Machine (TA_MASTER)

•	Memory Model (TA_MODEL)

•	Application Directory (Full Path) (TA_APPDIR)

•	Application Configuration File (Full Path) (TA_TUXCONFIG)

•	Network Address (TA_NADDR)

•	Network Listener Address (TA_NLSADDR)

•	Bridge Device (TA_BRIDGE)

Click Create to create the new domain. (Or click Cancel to close the window without creating a new domain.)

The following sections explain in detail the attribute fields on the Create New Object window for domains.

Hexadecimal Addresses

Anywhere within the interface, fields that take an address in decimal format can also be specified in hexadecimal format when preceded by the characters 0x. Each character after the initial 0x is a number between 0 and 9 or a letter between A and F (not case sensitive). The hexadecimal format is useful for arbitrary binary network addresses such as IPX/SPX or TCP/IP. For example:

0x0002091E9B02C112

0002 is the first part of a TCP/IP address and 091E is the port number 2334 translated into a hexadecimal number. The rest of the line contains hexadecimal numbers that are translations of the elements of the IP address 155.2.193.12: 155 becomes 9B, 2 becomes 02, and so on.

Domain ID (TA_DOMAINID)

<a name="13000"></a>

<a name="12037"></a>

Description

The name of your Oracle Tuxedo application.

Valid Values

A string of 0 to 30 characters. The default is NoName; this name is used only for display purposes in the GUI; it is not recorded as a value in the MIB.

Example

bankapp

IPC Key (TA_IPCKEY)

<a name="12017"></a>

<a name="13001"></a>

Description

A numeric key that identifies the shared memory segment in which the structures used by your application are located. In a single-processor environment, the interprocess communication (IPC) key identifies the bulletin board. In a multiple-processor or LAN environment, this key names the message queue of the Distinguished Bulletin Board Liaison (DBBL).

Valid Values

An integer in the range from 32769 to 262144. If you expect to define a network of machines using TCP/IP addressing, you may find it helpful to express the value of the IPC key in hexadecimal notation.

Example

34956

Master Machine (TA_MASTER)

<a name="13002"></a>

<a name="12039"></a>

Description

The name of the master machine, which is the node on which the master copy of the configuration file (TUXCONFIG) for your application is located. In a multiprocessor environment, this machine is also the one that should run the DBBL.

Valid Values

The format for this value is:

LMID1[,LMID2]

where:

LMID1

Is the master machine.

LMID2

Is the backup machine.

Notes

Each logical machine identifier (LMID) contains a maximum of 30 characters. The name of the master machine (LMID1) must correspond to the local machine for inactive applications. For a single-machine application, you cannot specify a backup machine.

The administrator can assign the name or it can be specified in your application.

A master machine name is required; specifying a backup machine is optional. For more information about using a Master and Backup machine to swap machines, refer to the section, Setting up Master and Backup Machines. If you specify a backup machine, it will be used as an alternate location (for the TUXCONFIG file and the DBBL) during process relocation and booting.

Example

branch1a,branch1b

Memory Model (TA_MODEL)

<a name="13003"></a>

<a name="12040"></a>

Description

The classification of your Oracle Tuxedo application as a single-machine (SHM) or multiprocessor (MP) application, specified by selecting one of two memory models (SHM or MP) from a drop-down menu.

Valid Values

Either SHM or MP. The default is SHM.

Application Directory (Full Path) (TA_APPDIR)

<a name="13004"></a>

<a name="13009"></a>

<a name="12081"></a>

Description

All directories are searched when application servers are booted. The first directory serves as the current directory for all application and administrative servers booted on this machine.

Valid Values

The format for this value is:

pathname1[:pathname2[:pathname3]...]

where:

pathname

Is a colon-separated list (for UNIX) of absolute pathnames for directories that contain Oracle Tuxedo applications.
Is a semicolon-separated list for Windows 2000. Each pathname is a string of 2 to 78 characters. A full pathnamePathnamepathnames must be specified for every application for which SECURITY has been set.

Example

/home/apps/bankapp:/home/apps/personnelapp

Application Configuration File (Full Path) (TA_TUXCONFIG)

<a name="13005"></a>

<a name="13011"></a>

<a name="12092"></a>

Description

The Application Configuration File field is equivalent to the MIB attribute TA_TUXCONFIG. TUXCONFIG is also the name of an environment variable that is used to compile the configuration file and activate the application. This internal entry is used by the Oracle Tuxedo system software after the application is activated.

Valid Values

The format for this value is:

pathname

where:

pathname

Is the absolute pathname for the location (either a file or device) of the configuration file for your Oracle Tuxedo application. Each pathname is a string of 2 to 78 characters.

Example

/home/bankapp/bankconfig

Network Address (TA_NADDR)

<a name="13079"></a>

<a name="13006"></a>

<a name="12085"></a>

Description

This field specifies the complete network address to be used by the bridge process placed on the LMID as its listening address. The listening address for a bridge is the means by which it is contacted by other bridge processes participating in the application.

Valid Values

A TCP/IP address is specified in one of two formats:

//hostname:port_number

//#.#.#.#:port_number

where:

hostname

The local name for the address of the machine on which the bridge resides.

port_number

The TCP port number or name at which the bridge will listen for incoming requests. The value of port_number can be either a number (between 0 and 65535) or a name. If port_number is a name, then it must be found in the network services database on your local machine.

Notes

In the first format, the bridge finds an address for hostname using the local name resolution facilities (usually DNS). hostname must unambiguously resolve to the address of the machine on which the bridge resides.

In the second format, the #.#.#.# is in dotted decimal format. Each # is a number from 0 to 255. This dotted decimal number represents the IP address of the local machine.

The address can also be specified in hexadecimal format.

The address can also be specified as an arbitrary string (with a maximum of 78 characters). For example, string addresses are used in STARLAN networks.

Example

A local machine on which a TDomain is being run is using TCP/IP addressing and is named backup.company.com, with address 155.2.193.18. The port number at which the TDomain should accept requests is 2334; this port number has been added to the network services database under the name bankapp-bridge. The address can be specified in any of the following five formats:

//155.2.193.18:bankapp-bridge

//155.2.193.18:2334

//backup.company.com:bankapp-bridge

//backup.company.com:2334

//0x0002091E9B02C112

The last example shows the Hexadecimal Addresses format.

Network Listener Address (TA_NLSADDR)

<a name="13080"></a>

<a name="13007"></a>

<a name="12086"></a>

Description

This field specifies the network address used by the UNIX tlisten(1) process servicing the network on the node identified by the LMID.

Valid Values

The format for this field is the same as that of Network Address (TA_NADDR).

Notes

tmloadcf(1) prints an error if you do not enter a value in this field for most machines. If you do not enter a value in this field for the MASTER LMID, tmloadcf prints a warning, and tmadmin(1) will not be able to run in administrator mode on remote machines; it will be limited to read-only operations. This also means that the backup site will be unable to reboot the master site after failure.

Example

See the example under Network Address (TA_NADDR).

Bridge Device (TA_BRIDGE)

<a name="13081"></a>

<a name="13008"></a>

<a name="12082"></a>

Description

The device name to be used by the bridge process placed on that LMID to access the network.

Valid Values

A string of 0 to 78 characters.

Notes

If your networking functionality is TLI-based, the device name must be an absolute pathname. The network transport endpoint file path has the following form:

/dev/provider_name

For STARLAN this is /dev/starlan. In a multiprocessor configuration, the value takes the form /dev/starlanN, where N is the PE number.

If your networking functionality is sockets-based, you need not enter a value in this field.

Example

/dev/starlan

Configuring Domain Resources (T_DOMAIN Class)

Application resources refers to global application attributes; that is, the attributes that apply to an entire application, or domain. These attribute values serve to identify, customize, size, secure, and tune a Oracle Tuxedo application. Many of the attribute values that you set on the tabs for your application resources serve as application default values for other classes of administrative objects.

Information about your application resources is listed in eight tabbed pages:

•	General Tab

•	Security Tab

•	Limits 1 Tab

•	Limits 2 Tab

•	Timers Tab

•	System Parameters Tab

•	Statistics 1 Tab

•	Statistics 2 Tab

General Tab

To configure general domain attributes, select a domain from the Oracle Tuxedo Administration Console tree view and select the General tab in the Configuration Tool pane. The tab contains the following configuration fields:

•	Domain ID (TA_DOMAINID)

•	Master Machine (TA_MASTER)

•	Memory Model (TA_MODEL)

•	IPC Key (TA_IPCKEY)

•	Object State (TA_STATE)

•	License Components (TA_COMPONENTS)

•	License Expiration Date (TA_LICEXPIRE)

•	License Maximum Users (TA_LICMAXUSERS)

•	License Serial Number (TA_LICSERIAL)

Object State (TA_STATE)

<a name="12034"></a>

Description

This field displays the state of your domain. A domain can be in one of the following states:

•

ACTIVE

•

INACTIVE

License Components (TA_COMPONENTS)

<a name="12390"></a>

Description

This field displays the Oracle Tuxedo products that you have licensed.

License Expiration Date (TA_LICEXPIRE)

<a name="12391"></a>

Description

This field displays the date on which your Oracle Tuxedo license will expire.

License Maximum Users (TA_LICMAXUSERS)

<a name="12392"></a>

Description

This field displays the maximum number of people allowed to use your Oracle Tuxedo license.

License Serial Number (TA_LICSERIAL)

<a name="12393"></a>

Description

This field displays your Oracle Tuxedo license number.

Security Tab

The Security tab page contains the following fields:

•	User ID (TA_UID)

•	Group ID (TA_GID)

•	Security (TA_SECURITY)

•	Permission (TA_PERM)

•	Authorization Service Name (TA_AUTHSVC)

•	Password (TA_PASSWORD)

•	Default Commit Control (TA_CMTRET)

User ID (TA_UID)

<a name="12033"></a>

Description

The default user ID of the Oracle Tuxedo administrator’s login for this domain.

Valid Values

An integer greater than or equal to 0 (up to the limits imposed by your operating system). The default is the effective user ID of the person running the tmloadcf command. Specify 0 for Windows 2000 systems.

You can override the value specified here, on individual machines, by specifying other values in the User ID field of the Security tab for the Machines class.

Example

33

Group ID (TA_GID)

<a name="12010"></a>

Description

The default group ID of the Oracle Tuxedo administrator’s login for this domain.

Valid Values

An integer greater than or equal to 0 (up to the limits imposed by your operating system). The default is the effective group ID of the person running the tmloadcf command. Specify 0 for Windows 2000 systems.

You can override the value specified here, on individual machines, by specifying other group IDs in the Security tab for the Machines class.

Example

601

Security (TA_SECURITY)

<a name="12043"></a>

Description

This field specifies a method of application security.

Valid Values

Any of the methods presented in the drop-down menu. The available possibilities are shown in Table 4‑2.

 

Table 4‑2 The Available Possibilities

Security	Description
NONE (default)	Security is turned off.
APP_PW	Application Password security is enforced. Clients will be required to provide the application password during initialization.
USER_AUTH	User Authentication security is enforced during client initialization: • Clients will be required to provide the application password. • Authentication will be performed for each user.
ACL	ACL security is enforced during client initialization: • Clients will be required to provide the application password. • Authentication will be performed for each user. • Access control checks will be run on service names, queue names, and event names. (If an associated ACL is not found for a name, it will be assumed that permission is granted.)
MANDATORY_ACL	Mandatory ACL security is enforced. The method is the same as the ACL method with one additional feature: if an associated ACL is not found for the specified service, queue, or event, then permission is denied.

Notes

A prerequisite for selecting a security method is the assignment of a password.

Permission (TA_PERM)

<a name="12000"></a>

Description

This field holds a number that controls read and write access to the IPC structure files to:

•	The designated user

•	The group with which that user is associated

•	Any user who is not a member of the group

Valid Values

A four-digit octal number (of which the first character is always 0) in the range 0001 to 0777 that represents the read and write permissions (as defined by the UNIX system) that you set for the IPC structures that implement the bulletin board, and default UNIX system permissions for system and application message queues. The default is 0666, signifying that permission to read and write (6) has been given to the designated user, the designated group, and any other user.

You can override the value specified here, on individual machines, by specifying other values for Permission on the Security tab for the Machines class.

Note:

Modifications to this attribute for an active object will not affect running servers or clients.

This attribute is specific to UNIX systems; the Oracle Tuxedo Administration Console might not return this attribute for applications running on other than UNIX platforms.

Authorization Service Name (TA_AUTHSVC)

<a name="12035"></a>

Description

The name of an application authentication service that is invoked by the system for each client joining the system.

Valid Values

A string of 0 to 127 characters, one of the following values as specified in Security (TA_SECURITY): USER_AUTH, ACL, or MANDATORY_ACL.

For upward compatibility, setting both APP_PW and AUTHSVC implies USER_AUTH. If you make those two specifications in Security (TA_SECURITY), service_name will be set, without notification, to USER_AUTH no matter what specification you make here.

If you selected the ACL or MANDATORY_ACL security method in Security (TA_SECURITY), then service_name must be.AUTHSVC; this name will be used no matter what specification you make here.

If you selected the USER_AUTH in Security (TA_SECURITY), then the default for service_name is AUTHSVC.

A value in this field is not required if you selected no security (NONE) or APP_PW in Security (TA_SECURITY).

Password (TA_PASSWORD)

<a name="12046"></a>

Description

Clear-text application password. The system automatically encrypts this information.

Valid Values

A string of 0 to 8 characters. This field is not required if you selected no security (NONE) in Security (TA_SECURITY).

Example

two4one

Default Commit Control (TA_CMTRET)

<a name="12036"></a>

Description

Initial setting of the TP_COMMIT_CONTROL characteristic for all client and server processes in a Oracle Tuxedo application.

Valid Values

Select one of the following security methods presented in the drop-down menu.

COMPLETE

Initializes the TP_COMMIT_CONTROL characteristic to TP_CMT_COMPLETE.

LOGGED

Initializes the TP_COMMIT_CONTROL characteristic to TP_CMT_LOGGED.

Notes

For details about setting this characteristic, refer to the description of the tpscmt(3) function in the BEA Tuxedo ATMI C Function Reference manual.

Note:

Run-time modifications to this attribute do not affect active clients and servers.

Limits 1 Tab

The Limits 1 tab page contains the following fields:

•	Max Accessors (TA_MAXACCESSORS)

•	Max Buffer Types (TA_MAXBUFTYPE)

•	Max Buffer Subtypes (TA_MAXBUFSTYPE)

•	Max Conversations (TA_MAXCONV)

•	Max Routing Entries (TA_MAXDRT)

•	Max Routing Ranges (TA_MAXRFT)

•	Max Routing Data (TA_MAXRTDATA)

•	Limits 2 Tab

Max Accessors (TA_MAXACCESSORS)

<a name="12018"></a>

Description

The default maximum number of processes that can have access to a bulletin board on a particular processor at any one time.

Valid Values

An integer in the range 0 to 32767. You do not need to include system administration processes, such as the BBL and the tmadmin command, when calculating this number. The default is 50.

Limitation

Changes in this field do not affect active or already configured objects in the Machines class.

Max Buffer Types (TA_MAXBUFTYPE)

<a name="12020"></a>

Description

Maximum number of buffer types that can be accommodated in the bulletin board buffer type table.

Valid Values

Displays an integer in the range 1 to 32767. The default is 6.

Max Buffer Subtypes (TA_MAXBUFSTYPE)

<a name="12019"></a>

Description

Maximum number of buffer subtypes that can be accommodated in the bulletin board buffer subtype table.

Valid Values

Displays an integer in the range 1 to 32767. The default is 50.

Max Conversations (TA_MAXCONV)

<a name="12021"></a>

Description

The maximum number of simultaneous conversations in which processes on a particular machine can be involved.

Valid Values

An integer in the range 1 to 32767. The default is 0.

 

This is the default attribute setting for newly configured objects in the Machines class. You can override the value specified here, on individual machines, by specifying other values in the Max Conversations field of the Limits tab for the Machines class.

Max Routing Entries (TA_MAXDRT)

<a name="12022"></a>

Description

Maximum number of routing table entries that can be accommodated in the bulletin board routing table.

 

Displays an integer in the range 1 to 32767. The default is 0.

One entry is required for each object in the Routing Tables class. Additional entries should be allocated to allow for run-time growth.

Example

100

Max Routing Ranges (TA_MAXRFT)

<a name="12027"></a>

Description

Maximum number of routing criteria range table entries to be accommodated in the bulletin board range criteria table.

Valid Values

Displays an integer in the range 1 to 32767. The default is 0.

One entry is required for each range within a specification in the Routing Table Ranges field of the General tab for the Routing class. In addition, one entry is required for each object in the Routing Tables class. Additional entries should be allocated to allow for run-time growth.

Example

1000

Max Routing Data (TA_MAXRTDATA)

<a name="12028"></a>

Description

Maximum amount of string pool space to be accommodated in the bulletin board string pool table. Strings and carrays specified in the Max Routing Ranges (TA_MAXRFT) are stored in the string pool. (A carray, character array, is a typed buffer format in which the data is an array of uninterpreted bytes; it always requires an associated length value.) Additional space should be allocated to allow for run-time growth.

Valid Values

Displays an integer in the range 0 to 32760. The default is 0.

Example

3500

Limits 2 Tab

The Limits 2 tab page contains the following fields:

•	Max Machines (TA_MAXMACHINES)

•	Max Groups (TA_MAXGROUPS)

•	Max Servers (TA_MAXSERVERS)

•	Max Services (TA_MAXSERVICES)

•	Max Queues (TA_MAXQUEUES)

•	Max Global Transactions (MAXGTT)

•	Max ACL Groups (TA_MAXACLGROUPS)

Max Machines (TA_MAXMACHINES)

<a name="12025"></a>

Description

Maximum number of configured machines that can be accommodated in the bulletin board machine table.

Valid Values

Displays an integer in the range 256 to 8191. The default is 256.

Max Groups (TA_MAXGROUPS)

<a name="12023"></a>

Description

Maximum number of configured server groups that can be accommodated in the bulletin board server group table.

Valid Values

Displays an integer in the range 100 to 32767. The default is 100.

Max Servers (TA_MAXSERVERS)

<a name="12029"></a>

Description

Maximum number of servers to be accommodated in the bulletin board server table.

Valid Values

Displays an integer in the range 1 to 8191. The default is 50.

Allowances should be made in setting this attribute for system-supplied administrative servers. Administration of each Oracle Tuxedo site adds approximately one server. Additionally, if TMSs are specified for any server groups (in the TMS Name field of the TMS tab for the Groups class), then they will be booted along with their server group and should be accounted for when determining the value to be entered in this field.

Max Services (TA_MAXSERVICES)

<a name="12030"></a>

Description

Maximum number of services to be accommodated in the bulletin board service table.

Valid Values

Displays an integer in the range 1 to 32767. The default is 100.

Allowances should be made in setting this attribute for system supplied servers offering services for administrative purposes. Administration of each Oracle Tuxedo site adds approximately five services. Other administrative components such as Oracle Tuxedo Workstation, /Q, and Domain may also add administrative services that should be accounted for.

Max Queues (TA_MAXQUEUES)

<a name="12026"></a>

Description

Maximum number of queues to be accommodated in the bulletin board queue table.

Valid Values

Displays an integer in the range 1 to 8191. The default is 50.

Max Global Transactions (MAXGTT)

<a name="12403"></a>

Description

Maximum number of simultaneous global transactions in which a particular machine can be involved.

Valid Values

An integer in the range 0 to 32767. The default is 100.

You can override the value specified here, on individual machines, by specifying other values in the Max Global Transactions field of the Limits tab for the Machines class.

Max ACL Groups (TA_MAXACLGROUPS)

<a name="12024"></a>

Description

Maximum number of group identifiers that can be used for ACL permissions checking.

Valid Values

Displays an integer in the range 1to 16384. The default is 16384. The maximum group identifier that can be defined is 1 less than max_aclgroups.

Timers Tab

The Timers tab contains the following fields:

•	Basic Time Unit for Sanity Checks (TA_SCANUNIT)

•	Bulletin Board Query Time (TA_BBLQUERY)

•	Default Blocking Time (TA_BLOCKTIME)

•	Bulletin Board Waiting Time (TA_DBBLWAIT)

•	Sanity Checking Timer (TA_SANITYSCAN)

Basic Time Unit for Sanity Checks (TA_SCANUNIT)

<a name="12032"></a>

Description

Interval of time (in seconds) between periodic scans by the system. Periodic scans are used to detect old transactions and timed-out blocking calls within service requests.

Valid Values

An integer in the range 0 to 60. The default is 0. The basic time unit (or “scan unit”) must be a multiple of 5.

Passing a value of 0 for this attribute on a SET operation causes the attribute to be reset to its default value.

Bulletin Board Query Time (TA_BBLQUERY)

<a name="12001"></a>

Description

The amount of time (expressed in scan units) between DBBL status checks on registered BBLs. The DBBL checks to ensure that all BBLs have reported in within the period specified in this field. If a BBL has not been heard from, the DBBL sends a message to that BBL asking for status. If no reply is received, the BBL is partitioned.

Valid Values

An integer in the range 0 to 32767. The default is 0. This attribute value should be set to at least twice scan_unit (the value specified in the Basic Time Unit for Sanity Checks (TA_SCANUNIT)). The default is an integer number that is approximately equal to 300 divided by scan_unit.

Default Blocking Time (TA_BLOCKTIME)

<a name="12002"></a>

Description

The minimum amount of time (expressed in scan units) that a blocking ATMI call will block before timing out. The DBBL checks to ensure that all BBLs have reported in within the period specified in this field. If a BBL has not been heard from, the DBBL sends a message to that BBL asking for status. If no reply is received, the BBL is partitioned.

Valid Values

An integer in the range 0 to 32767. The default is an integer number that is approximately equal to 50 divided by scan_unit.

Passing a value of 0 for this attribute on a SET operation will cause the attribute to be reset to its default value.

Bulletin Board Waiting Time (TA_DBBLWAIT)

<a name="12009"></a>

Description

The maximum amount of time (expressed in scan units) that a DBBL should wait for replies from its BBLs before timing out. The DBBL checks to ensure that all BBLs have reported in within the period specified in this field. If a BBL has not been heard from, the DBBL sends a message to that BBL asking for status. If no reply is received, the BBL is partitioned.

Valid Values

An integer in the range 0 to 32767. The default is an integer number that is approximately equal to 20 divided by scan_unit.

Passing a value of 0 for this attribute on a SET operation will cause the attribute to be reset to its default value.

Sanity Checking Timer (TA_SANITYSCAN)

<a name="12031"></a>

Description

The amount of time (expressed in scan units) between basic sanity checks of the system. The DBBL checks to ensure that all BBLs have reported in within the period specified in this field. If a BBL has not been heard from, the DBBL sends a message to that BBL asking for status. If no reply is received, the BBL is partitioned.

Sanity checking includes client/server viability checks done by each BBL for clients/servers running on the local machine as well as BBL status check-ins (MP mode only).

Valid Values

An integer in the range 0 to 32767. The default is an integer number that is approximately equal to 20 divided by scan_unit.

Passing a value of 0 for this attribute on a SET operation will cause the attribute to be reset to its default value.

System Parameters Tab

The System Parameters tab page contains the following fields:

•	Load Balancing Enabled (TA_LDBAL)

•	Notification (TA_NOTIFY)

•	User Signal (TA_USIGNAL)

•	Options (TA_OPTIONS)

•	System Access (TA_SYSTEM_ACCESS)

Load Balancing Enabled (TA_LDBAL)

<a name="12038"></a>

Description

Whether to enable load balancing, specified by selecting either Yes or No from a drop-down menu.

Valid Values

Enter either Yes or No.

Limitation

Modifications to this field do not affect clients and servers.

Notification (TA_NOTIFY)

<a name="12041"></a>

Description

Default notification detection method to be used by the system for unsolicited messages sent to client processes, chosen from a drop-down menu.

Valid Values

Any of the methods presented in the drop-down menu. The available choices are shown in Table 4‑3.

 

Table 4‑3 The Available Choices

Method	Description
Dip in (poll)	Specifies that dip-in-based notification detection should be used. The system will only detect notification messages on behalf of a client process while within ATMI calls. The point of detection within any particular ATMI call is not defined by the system, and dip-in detection will not interrupt blocking system calls.
Signal	Specifies that signal-based notification detection should be used. The system sends a signal to the target client process after the notification message has been made available. The system installs a signal catching routine on behalf of clients selecting this method of notification.
Ignore	Specifies that by default, notification messages are to be ignored by application clients. This is appropriate in applications that specify that only clients requesting notification at tpinit(3) time should receive unsolicited messages

Notes

Once unsolicited messages are detected, they are made available to the application through the unsolicited message handling routine that has been defined by the application and identified by the UNIX tpsetunsol(3) function.) This default value can be overridden on a per-client basis using the appropriate tpinit(3) flag value.

Limitation

Run-time modifications to this attribute do not affect active clients. All signaling of client processes is done by administrative system processes and not by application processes. Therefore, only clients running with the same UNIX system user identifier can be notified using the SIGNAL method.

User Signal (TA_USIGNAL)

<a name="12045"></a>

Description

Displays which of two signals to be used for signal-based notification.

Valid Values

Either SIGUSR1 or SIGUSR2.

Options (TA_OPTIONS)

<a name="12042"></a>

Description

Comma-separated list of application options in effect.

Valid Values

The available choices are shown in Table 4‑4.

 

Table 4‑4 The Available Choices

Option	Description
LAN	Networked application
MIGRATE	Allow server group migration
ACCSTATS	Exact statistics (SHM mode only)

Notes

The default is no options.

Limitation

Only the ACCSTATS option can be set or reset in an active application.

Example

LAN,MIGRATE,ACCSTATS

System Access (TA_SYSTEM_ACCESS)

<a name="12044"></a>

Description

Default mode used by Oracle Tuxedo libraries within application processes to gain access to Oracle Tuxedo internal tables.

Valid Values

The available choices are shown in Table 4‑5.

 

Table 4‑5 The Available Choices

Option	Description
FASTPATH	Specifies that Oracle Tuxedo’s internal tables are accessible by Oracle Tuxedo libraries via unprotected shared memory for fast access.
PROTECTED	Specifies that Oracle Tuxedo’s internal tables are accessible by Oracle Tuxedo libraries via protected shared memory for safety against corruption by application code.
NO_OVERRIDE	Specifies that the mode selected cannot be overridden by an application process using flags available for use with tpinit(3).

Notes

The default is FASTPATH.

Limitation

Updates to this attribute value in a running application affect only newly started clients and newly configured objects in the Servers class.

Example

FASTPATH, NO_OVERRIDE

Statistics 1 Tab

The Statistics 1 tab contains the following fields:

•	Highest Number of Machines (TA_HWMACHINES)

•	Highest Number of Queues (TA_HWQUEUES)

•	Highest Number of Routing Table Entries (TA_HWDRT)

•	Highest Number of Routing Criteria Entries (TA_HWRFT)

•	Largest Size of Routing Table String Pool (TA_HWRTDATA)

•	Highest Number of BBL Servers in Use (TA_HWSERVERS)

•	Highest Number of Groups (TA_HWGROUPS)

•	Highest Number of Services (TA_HWSERVICES)

Highest Number of Machines (TA_HWMACHINES)

<a name="12012"></a>

Description

This field displays the high-water number of configured machines (since Oracle Tuxedo was booted or you reset the counter for this field).

Highest Number of Queues (TA_HWQUEUES)

<a name="12013"></a>

Description

This field displays the high-water number of bulletin board queue table entries that have been used since Oracle Tuxedo was booted.

Highest Number of Routing Table Entries (TA_HWDRT)

<a name="12011"></a>

Description

This field displays the maximum number of routing table entries that can be accommodated in the bulletin board routing table. One entry is required for each object in the Routing Tables class. Additional entries should be allocated to allow for run-time growth.

Highest Number of Routing Criteria Entries (TA_HWRFT)

<a name="12014"></a>

Description

This field displays the maximum number of routing criteria range table entries accommodated in the bulletin board range criteria table. One entry is required for each individual range specified in the Routing Table Ranges field (on the General tab for the Routing Tables class). In addition, one entry is required for each object in the Routing Tables class. Additional entries should be allocated to allow for run-time growth.

Largest Size of Routing Table String Pool (TA_HWRTDATA)

<a name="12015"></a>

Description

This field displays the maximum string pool space accommodated in the bulletin board string pool table. Strings and carrays specified in the Routing Table Ranges field (on the General tab for the Routing Tables class) are stored in the string pool. Additional space should be allocated to allow for run-time growth.

Highest Number of BBL Servers in Use (TA_HWSERVERS)

<a name="12016"></a>

Description

This field displays the high-water number of in-use bulletin board server table entries.

Highest Number of Groups (TA_HWGROUPS)

<a name="12048"></a>

Description

This field displays the high-water number of in-use bulletin board server group table.

Highest Number of Services (TA_HWSERVICES)

<a name="12049"></a>

Description

This field displays the high-water number of in-use bulletin board service table entries.

Statistics 2 Tab

The Statistics 2 tab contains the following fields:

•	Current Number of Machines (TA_CURMACHINES)

•	Current Number of Queues (TA_CURQUEUES)

•	Current Number of Routing Table Entries (TA_CURDRT)

•	Current Number of Routing Criteria Entries (TA_CURRFT)

•	Current Size of Routing Table String Pool (TA_CURRTDATA)

•	Current Number of BBL Servers In Use (TA_CURSERVERS)

•	Current Number of Groups (TA_CURGROUPS)

•	Current Number of Services (TA_CURSERVICES)

•	Current Number of Type Entries (TA_CURTYPE)

•	Current Number of Subtype Entries (TA_CURSTYPE)

Current Number of Machines (TA_CURMACHINES)

<a name="12004"></a>

Description

This field displays the number of machines currently configured.

Current Number of Queues (TA_CURQUEUES)

<a name="12005"></a>

Description

This field displays the number of bulletin board queue table entries currently being used.

Current Number of Routing Table Entries (TA_CURDRT)

<a name="12003"></a>

Description

This field displays the number of bulletin board routing table entries currently being used.

Current Number of Routing Criteria Entries (TA_CURRFT)

<a name="12006"></a>

Description

This field displays the number of bulletin board routing criteria range table entries currently being used.

Current Size of Routing Table String Pool (TA_CURRTDATA)

<a name="12007"></a>

Description

This field displays the current size of the routing table string pool.

Current Number of BBL Servers In Use (TA_CURSERVERS)

<a name="12008"></a>

Description

This field displays the number of bulletin board server table entries currently being used.

Current Number of Groups (TA_CURGROUPS)

<a name="12404"></a>

Description

This field displays the number of bulletin board server group table entries that are currently being used.

Current Number of Services (TA_CURSERVICES)

<a name="12405"></a>

Description

This field displays the number of bulletin board service table entries that are currently being used.

Current Number of Type Entries (TA_CURTYPE)

<a name="12406"></a>

Description

This field displays the number of bulletin board type table entries that are currently being used.

Current Number of Subtype Entries (TA_CURSTYPE)

<a name="12407"></a>

Description

This field displays the number of bulletin board subtype table entries that are currently being used.

Creating Machines

<a name="N_MACHINE"></a>

The following help topics describe what information to enter in the Create New Object window for creating machines.

To create a new Machine:

1.	Select the Machine folder in the tree view.

2.	Select Quick Menu —>New (right-click) to display the New Object window.

3.	Enter values for the following fields:

•	Machine Name (TA_PMID)

•	Logical Machine Name (TA_LMID)

•	Tuxedo Root Directory (Full Path) (TA_TUXDIR)

•	Application Configuration File (Full Path) (TA_TUXCONFIG)

•	Application Directory (Full Path) (TA_APPDIR)

•	Network Address (TA_NADDR)

•	Network Listener Address (TA_NLSADDR)

•	Bridge Device (TA_BRIDGE)

4.	Click the Create button to close the window and create the new Machine.

The rest of this section describes the fields on the Create New Object window.

Machine Name (TA_PMID)

<a name="13010"></a>

<a name="12087"></a>

Description

Physical machine identifier used by Oracle Tuxedo (specifically, in the TM_MIB) for mapping application resources to machines configured for this application.

Valid Values

A string of 1 to 30 characters.

For UNIX users: The value of Machine Name is the node name returned when you run the uname -a command on this machine.

Example

jupiter

Logical Machine Name (TA_LMID)

<a name="13013"></a>

<a name="12096"></a>

<a name="12087"></a>

Description

Logical machine identifier used, in the TM_MIB definition, as the sole means of mapping application resources to configured machines.

Valid Values

A string of 1 to 30 characters.

You have the option of assigning a logical name to a backup machine in case the first machine fails.

Example

SITE1

Tuxedo Root Directory (Full Path) (TA_TUXDIR)

<a name="13012"></a>

<a name="12093"></a>

Description

TUXDIR is the absolute pathname of the directory (on this machine) in which the Oracle Tuxedo software resides.

Valid Values

A string of 2 to 78 characters. This directory should not be on a remote filesystem.

Example

/home/tuxedo

Configuring Machines (T_MACHINE Class)

<a name="T_MACHINE"></a>

<a name="C_MACHINE"></a>

Machine attributes are listed in nine tab pages with the following labels:

•	General Tab

•	Networking Tab

•	Security Tab

•	Limits Tab

•	Transaction Log Tab

•	Statistics 1 Tab

•	Statistics 2 Tab

•	Statistics 3 Tab

•	ACL Statistics Tab

General Tab

The General tab for machine attributes contains the following fields:

•	Machine Name (TA_PMID)

•	Logical Machine Name (TA_LMID)

•	Machine Type (TA_TYPE)

•	ULOG Prefix (TA_ULOGPFX)

•	Tuxedo Root Directory (Full Path) (TA_TUXDIR)

•	Application Directory (Full Path) (TA_APPDIR)

•	Application Configuration File (Full Path) (TA_TUXCONFIG)

•	Environment File (TA_ENVFILE)

•	Object State (TA_STATE)

Machine Type (TA_TYPE)

<a name="12094"></a>

Description

Machine type. Machines are grouped on the basis of like data representations.

Valid Values

A string of 0 to 15 characters. This value is used only for comparison. The default is no entry, that is, the null string, which matches any other machine for which a value has not been specified in this field.

This parameter is used for comparing machines. If the same type has been assigned to two machines, data encoding/decoding is bypassed when data is sent between them. We recommend specifying a type when your application involves a heterogeneous network of machines or when different compilers are used on the machines in the network.

Example

486

ULOG Prefix (TA_ULOGPFX)

<a name="12095"></a>

Description

The directory in which the user log error message file (for all servers, clients, and administrative processes executed on this machine) will be stored. The directory is specified as an absolute pathname (not including the filename) for the user log error message file.

Valid Values

A string of 0 to 78 characters. This directory should not be on a remote filesystem. The default is $APPDIR/ULOG.

 

Modifications to this attribute for an active object will not affect running servers or clients.

Example

/usr2/apps/bank/ULOG

where /usr2/apps/bank is the value of $APPDIR.

Environment File (TA_ENVFILE)

<a name="12084"></a>

Description

The pathname of the file that contains variables to be added to the environment for all servers on this machine.

Valid Values

A string of 0 to 78 characters. The default is no entry, that is, the null string.

Example

/home/bankapp/bankenv

Object State (TA_STATE)

Description

<a name="12080"></a>

This field displays the state of your machine. A machine can be in one of the following states:

•

ACTIVE

•

INACTIVE

•	PARTITIONED

Networking Tab

The Networking tab for machine attributes contains the following fields:

•	Network Address (TA_NADDR)

•	Network Listener Address (TA_NLSADDR)

•	Bridge Device (TA_BRIDGE)

•	Network Load (TA_TMNETLOAD)

Network Load (TA_TMNETLOAD)

<a name="12075"></a>

Description

The additional load to be added during load balancing, specifically, when computing the cost of sending a service request from this machine to another.

Valid Values

An integer in the range 0 to 32767. The default is 0.

Security Tab

The Security tab for machine attributes contains the following fields:

•	User ID (TA_UID)

•	Group ID (TA_GID)

•	Permission (TA_PERM)

•	Minimum Encryption Bits (TA_MINENCRYPTBITS)

•	Maximum Encryption Bits (TA_MAXENCRYPTBITS)

User ID (TA_UID)

<a name="12077"></a>

Description

UNIX system user identifier for the Oracle Tuxedo application administrator on this machine.

Valid Values

An integer in the range 0 to 2147483647. The default is the value entered in the User ID field on the Security tab for the Application Resources (T_DOMAIN) class). Administrative commands such as tmboot(1), tmshutdown(1), and tmadmin(1) must be run, on this machine, by the owner of this ID. Application and administrative servers on this machine will be started as this user. IPC structures created for the bulletin board are associated with this ID.

Limitation

This is a UNIX system-specific attribute that cannot be returned if the platform on which the application is being run is not UNIX-based.

Example

466

Group ID (TA_GID)

<a name="12053"></a>

Description

UNIX system group identifier for the Oracle Tuxedo application administrator on this machine. (The administrator for this machine is the owner of the user ID, as defined by the value you entered in the User ID (TA_UID).)

Valid Values

An integer in the range 0 to 2147483647. The default is the value entered in the User ID field on the Security tab for the Application Resources (T_DOMAIN) class.

Limitation

This is a UNIX system-specific attribute that cannot be returned if the platform on which the application is being run is not UNIX-based.

Example

512

Permission (TA_PERM)

<a name="12049"></a>

Description

The numeric permissions associated with the IPC structures that implement the bulletin board.

Valid Values

A four-digit octal number (of which the first character is always 0) in the range 0001 to 0777 that represents the read and write permissions (as defined by the UNIX system) that you set for the IPC structures that implement the bulletin board, and default UNIX system permissions for system and application message queues. For example, the value 0666 signifies that permission to read and write (6) has been given to the designated user, the designated group, and any other user. The default is the value entered in the User ID field on the Security tab for Application Resources (T_DOMAIN)).

This attribute is specific to UNIX systems; the Oracle Tuxedo Administration Console might not return this attribute for applications running on other than UNIX platforms.

Example

0600

Minimum Encryption Bits (TA_MINENCRYPTBITS)

<a name="12047"></a>

Description

The minimum encryption level that will be accepted by a process when data flowing over Oracle Tuxedo network links has been encrypted.

Valid Values

One of the methods presented in the drop-down menu. The available choices are shown in Table 4‑6.

 

 

 

Table 4‑6 The Available Choices

Security	Description
0	No encryption
40	Encryption key length (in bits)
128	Encryption key length (in bits)

Note:

Modifications to this attribute for an active object will not affect running servers or clients.

Notes

The encryption level is the size of the encryption key used for decrypting (expressed in bits). The default is 0, that is, no encryption. When establishing a network link to this machine, at least this minimum level of encryption is required. If this minimum level of encryption cannot be met, link establishment will fail.

Minimum and maximum encryption levels must be specified for every machine participating in a Oracle Tuxedo domain. During a communication session, the minimum encryption level will be used if either participating process does not support the maximum level that has been specified for the current machine.

Maximum Encryption Bits (TA_MAXENCRYPTBITS)

<a name="12048"></a>

Description

The maximum encryption level that will be accepted by a process when data flowing over Oracle Tuxedo network links has been encrypted.

Valid Values

One of the methods presented in the drop-down menu. The available choices are shown in Table 4‑7.

 

Table 4‑7 The Available Choices

Security	Description
0	No encryption
40	Encryption key length (in bits)
128	Encryption key length (in bits)

Notes

The encryption level is the size of the encryption key used for decrypting (expressed in bits). The default is 28. When establishing a network link to this machine, up to this level of encryption will be accepted.

Minimum and maximum encryption levels must be specified for every machine participating in a Oracle Tuxedo domain. During a communication session, the minimum encryption level will be used if either participating process does not support the maximum level that has been specified for the current machine.

 

Limits Tab

The Limits tab for machine attributes contains the following fields:

•	Max Accessors (TA_MAXACCESSORS)

•	Max Conversations (TA_MAXCONV)

•	Max Workstation Clients (TA_MAXWSCLIENTS)

•	Max Global Transactions (TA_MAXGTT)

•	Spin Count (TA_SPINCOUNT)

•	Compression Limit (TA_CMPLIMIT)

•	Max ACL Entries in Cache (TA_MAXACLCACHE)

Max Accessors (TA_MAXACCESSORS)

<a name="12057"></a>

Description

The maximum number of clients and servers that can have access to a bulletin board on a particular processor at any one time.

Valid Values

An integer in the range 0 to 32767. You do not need to include system administration processes, such as the BBL, when calculating this number, but all application servers, clients, and TMS servers should be counted. If the application is activating workstation listeners on this site, then both the listeners and the potential number of workstation handlers that may be activated should be counted. The default is the value entered in the Max Accessors (TA_MAXACCESSORS) on the Limits 1 Tab tab for Application Resources (T_DOMAIN).

Example

150

Max Conversations (TA_MAXCONV)

<a name="12058"></a>

Description

The maximum number of simultaneous conversations in which processes on a particular machine can be involved.

Valid Values

An integer in the range 1 to 32767. The default is the value you specified in the Max Conversations (TA_MAXCONV) on the Limits 1 Tab tab for Application Resources (T_DOMAIN).

 

This is the default attribute setting for newly configured objects in the Machines class. The maximum number of simultaneous conversations per server is 64. The maximum number of simultaneous conversations per server is 64.

Example

400

Max Workstation Clients (TA_MAXWSCLIENTS)

<a name="12060"></a>

Description

The number of accesser entries on this machine to be reserved for Workstation clients only.

Valid Values

An integer in the range 1 to 32767. The default is 0.

This field is active only when the WorkStation feature is being used. The number specified here takes a portion of the total accesser slots specified with the value entered in the Max Accessors (TA_MAXACCESSORS). The appropriate setting of this parameter helps to conserve IPC resources since Workstation client access to the system is multiplexed through a Oracle Tuxedo supplied surrogate, the workstation handler.

The value of this field must be less than the value of the Max Accessors (TA_MAXACCESSORS); setting this field to a greater value is an error.

Example

150

Max Global Transactions (TA_MAXGTT)

<a name="12059"></a>

Description

Maximum number of simultaneous global transactions in which this machine can be involved

Valid Values

An integer in the range 1 to 32767. The default is the value you specified in the Max Global Transactions (MAXGTT) on the Limits 2 Tab tab for Application Resources (T_DOMAIN).

Example

10000

Spin Count (TA_SPINCOUNT)

<a name="12072"></a>

Description

The number of attempts that should be made at the user level to lock the bulletin board before blocking processes on a UNIX semaphore.

Valid Values

An integer greater than or equal to 0. The default is 0. A value of 0 indicates that the spin count built into the delivered binary should be used. If set, this parameter causes the TMSPINCOUNT environment variable to be ignored. This behavior varies from platform to platform.

Default values are built into the Oracle Tuxedo binaries on each machine. These defaults can be overridden at run time for tuning purposes using this attribute. The spin count can be reset to the default built-in value for the site by resetting this attribute value to 0. The system uses the TMSPINCOUNT environment variable if the value is not set here or in the ubbconfig file.

Example

10

Compression Limit (TA_CMPLIMIT)

<a name="12083"></a>

Description

Threshold message size at which compression will occur for remote traffic and, optionally, for local traffic.

Valid Values

remote[,local]

Notes

The values of remote and local can be either nonnegative numeric values or the string MAXLONG, which is dynamically translated to the maximum long setting for the machine. The default is MAXLONG,MAXLONG.

If you enter a value only for remote, the value of local will be set to MAXLONG.

Max ACL Entries in Cache (TA_MAXACLCACHE)

<a name="12410"></a>

Description

Number of entries in the cache used for ACL entries when TA_SECURITY is set to ACL or MANDATORY_ACL. The appropriate setting of this parameter helps to conserve shared memory resources and yet reduce the number of disk access needed to perform ACL checking.

Valid Values

An integer in the range 1 to 32767. The default is 100.

Transaction Log Tab

The Transaction Log tab for machine attributes contains the following fields:

•	TLOG Name (TA_TLOGNAME)

•	TLOG Size (TA_TLOGSIZE)

•	TLOG Device (TA_TLOGDEVICE)

TLOG Name (TA_TLOGNAME)

<a name="12091"></a>

Description

The name of the DTP transaction log for this machine.

Valid Values

A string of 0 to 30 characters. The default is TLOG.

If more than one DTP transaction log (or TLOG) exists on the same TLOG device (TLOG Device (TA_TLOGDEVICE)), they must have unique names. The name you specify in this field must not match any other name in any other table in the configuration in which the TLOG table is created.

Example

JUPITERLOG

TLOG Size (TA_TLOGSIZE)

<a name="12074"></a>

Description

The number of pages of the DTP transaction log (or “TLOG”) for this machine.

Valid Values

An integer in the range 1 to 2048, represents the number of pages. The default is 100. The value you enter is entirely application-dependent. After a global transaction completes, the TLOG records are no longer needed and are thrown away.

TLOG Device (TA_TLOGDEVICE)

<a name="12090"></a>

Description

The full pathname for the device (raw slice) or UNIX system file that contains the DTP transaction log (TLOG) for this machine. (The TLOG is stored as a Oracle Tuxedo VTOC table on the device.)

Valid Values

A string of 0 to 64 characters. If you do not enter a value in this field, it is assumed that there is no TLOG on this machine.

You can specify the same value that you entered (for this machine) in the Tuxedo Root Directory (Full Path) (TA_TUXDIR) on the General tab for the Machines class. If no TLOG device exists for a given machine, the associated LMID cannot be used by server groups that participate in distributed transactions.

Example

/usr2/apps/bank/TLOG

Statistics 1 Tab

The Statistics 1 tab for machine attributes contains the following fields:

•	Number of Conversations (TA_NUMCONV)

•	Number of Dequeues (TA_NUMDEQUEUE)

•	Number of Enqueues (TA_NUMENQUEUE)

•	Number of Posts (TA_NUMPOST)

•	Number of Requests (TA_NUMREQ)

•	Number of In Use Transaction Table Entries (TA_CURGTT)

•	Number of Transactions (TA_NUMTRAN)

•	Number of Transactions Aborted (TA_NUMTRANABT)

•	Number of Transactions Committed (TA_NUMTRANCMT)

Number of Conversations (TA_NUMCONV)

<a name="12061"></a>

Description

Number of tpconnect(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).

Valid Values

conversations

Notes

An integer greater than or equal to 0. If the machine is in an active state, you can reset the counter by replacing the number shown with a number that will be used as the starting point for a new count. We recommend entering 0 when you reset the counter.

Interpret the number shown in this field in terms of the starting point for the counter. For example, if you reset the counter to 1000 and the number displayed in this field later is 10000, the number of operations performed is 9000.

Example

100

Number of Dequeues (TA_NUMDEQUEUE)

<a name="12062"></a>

Description

Number of tpdequeue(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).

Valid Values

An integer greater than or equal to 0. If the machine is in an active state, you can reset the counter by replacing the number shown with a number that will be used as the starting point for a new count. We recommend entering 0 when you reset the counter.

Interpret the number shown in this field in terms of the starting point for the counter. For example, if you reset the counter to 1000 and the number displayed in this field later is 10000, the number of operations performed is 9000.

Example

100

Number of Enqueues (TA_NUMENQUEUE)

<a name="12063"></a>

Description

Number of tpenqueue(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).

Valid Values

An integer greater than or equal to 0. If the machine is in an active state, you can reset the counter by replacing the number shown with a number that will be used as the starting point for a new count. We recommend entering 0 when you reset the counter.

Interpret the number shown in this field in terms of the starting point for the counter. For example, if you reset the counter to 1000 and the number displayed in this field later is 10000, the number of operations performed is 9000.

Example

100

Number of Posts (TA_NUMPOST)

<a name="12064"></a>

Description

Number of tppost(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).

Valid Values

An integer greater than or equal to 0. If the machine is in an active state, you can reset the counter by replacing the number shown with a number that will be used as the starting point for a new count. We recommend entering 0 when you reset the counter.

Interpret the number shown in this field in terms of the starting point for the counter. For example, if you reset the counter to 1000 and the number displayed in this field later is 10000, the number of operations performed is 9000.

Example

100

Number of Requests (TA_NUMREQ)

<a name="12065"></a>

Description

Number of tpacall(3) or tpcall(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).

Valid Values

An integer greater than or equal to 0. If the machine is in an active state, you can reset the counter by replacing the number shown with a number that will be used as the starting point for a new count. We recommend entering 0 when you reset the counter.

Interpret the number shown in this field in terms of the starting point for the counter. For example, if you reset the counter to 1000 and the number displayed in this field later is 10000, the number of operations performed is 9000.

Example

100

Number of In Use Transaction Table Entries (TA_CURGTT)

<a name="12052"></a>

This field displays the number of transaction table entries on this machine that are currently in use.

Number of Transactions (TA_NUMTRAN)

<a name="12067"></a>

Description

The number of transactions initiated (with tpbegin(3)) from this machine since Oracle Tuxedo was booted (or since you reset this field).

Valid Values

An integer greater than or equal to 0. If the machine is in an active state, you can reset the counter by replacing the number shown with a number that will be used as the starting point for a new count. We recommend entering 0 when you reset the counter.

Interpret the number shown in this field in terms of the starting point for the counter. For example, if you reset the counter to 1000 and the number displayed in this field later is 10000, the number of operations performed is 9000.

Example

2

Number of Transactions Aborted (TA_NUMTRANABT)

<a name="12068"></a>

Description

The number of transactions aborted (tpabort(3)) from this machine since Oracle Tuxedo was booted (or since you reset this field).

Valid Values

An integer greater than or equal to 0. If the machine is in an active state, you can reset the counter by replacing the number shown with a number that will be used as the starting point for a new count. We recommend entering 0 when you reset the counter.

Interpret the number shown in this field in terms of the starting point for the counter. For example, if you reset the counter to 1000 and the number displayed in this field later is 10000, the number of operations performed is 9000.

Example

0

Number of Transactions Committed (TA_NUMTRANCMT)

<a name="12069"></a>

Description

The number of transactions committed (with tpcommit(3)) from this machine since Oracle Tuxedo was booted (or since you reset this field).

Valid Values

An integer greater than or equal to 0. If the machine is in an active state, you can reset the counter by replacing the number shown with a number that will be used as the starting point for a new count. We recommend entering 0 when you reset the counter.

Interpret the number shown in this field in terms of the starting point for the counter. For example, if you reset the counter to 1000 and the number displayed in this field later is 10000, the number of operations performed is 9000.

Example

2

Statistics 2 Tab

The Statistics 2 tab for machine attributes contains the following fields:

•	Current Number of Clients (TA_CURCLIENTS)

•	Current Number of WS Clients (TA_CURWSCLIENTS)

•	Current Number of Conversations (TA_CURCONV)

•	Current Number of Accessors (TA_CURACCESSORS)

•	Current Service Load (TA_CURRLOAD)

•	Highest Number of Accessors (TA_HWACCESSORS)

•	Highest Number of Conversations (TA_HWCONV)

•	Highest Number of In Use Transaction Table Entries (TA_HWGTT)

•	Highest Number of Clients (TA_HWCLIENTS)

•	Highest Number of WS Clients (TA_HWWSCLIENTS)

Current Number of Clients (TA_CURCLIENTS)

<a name="12050"></a>

Description

This field displays the number of clients, both native and workstation, currently logged in to this machine.

Current Number of WS Clients (TA_CURWSCLIENTS)

<a name="12051"></a>

Description

This field displays the number of Workstation clients currently logged in to this machine

<a name="12051"></a>

Current Number of Conversations (TA_CURCONV)

<a name="12412"></a>

Description

This field displays the number of active conversations with participants on this machine.

Current Number of Accessors (TA_CURACCESSORS)

<a name="12054"></a>

Description

This field displays the number of clients and servers currently accessing the application either directly on this machine or through a workstation handler on this machine.

Current Service Load (TA_CURRLOAD)

<a name="12055"></a>

Description

This field displays the current service load on this machine.

Note:

If the T_DOMAIN:TA_LDBAL attribute is N or the T_DOMAIN:TA_MODEL attribute is MP, then an FML32 NULL value is returned (0).

Highest Number of Accessors (TA_HWACCESSORS)

<a name="12056"></a>

Description

This field displays the high-water number of clients and servers accessing the application (either directly, on this machine, or through a workstation handler on this machine).

Highest Number of Conversations (TA_HWCONV)

<a name="12055"></a>

Description

This field displays the highest number of simultaneous conversations that have occurred on this machine since Oracle Tuxedo was booted.

Highest Number of In Use Transaction Table Entries (TA_HWGTT)

<a name="12056"></a>

Description

This field displays the high-water number of transaction table entries currently being used on this machine.

Highest Number of Clients (TA_HWCLIENTS)

<a name="TA_HWCLIENTS"></a>

Description

This field displays the high-water number of clients (both native and workstation) logged in to this machine.

Highest Number of WS Clients (TA_HWWSCLIENTS)

<a name="TA_HWWSCLIENTS"></a>

Description

This field displays the high-water number of Workstation clients currently logged in to this machine.

Statistics 3 Tab

The Statistics 3 tab for machine attributes contains the following fields:

•	Number of Subscriptions (TA_NUMSUBSCRIBE)

•	Disk Page Size (TA_PAGESIZE)

•	Offset to the TLOG File (TA_TLOGOFFSET)

•	Offset to the Oracle Tuxedo File (TA_TUXOFFSET)

•	Total Service Load Completed (TA_WKCOMPLETED)

•	Total Service Load Initiated (TA_WKINITIATED)

•	Machine Role (TA_ROLE)

•	Software Release (TA_SWRELEASE)

•	Current Number of Accessors (TA_CURACCESSORS)

Number of Subscriptions (TA_NUMSUBSCRIBE)

<a name="12066"></a>

Description

The number of tpsubscribe(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).

Valid Values

An integer greater than or equal to 0. If the machine is in an active state, you can reset the counter by replacing the number shown with a number that will be used as the starting point for a new count. We recommend entering 0 when you reset the counter.

Interpret the number shown in this field in terms of the starting point for the counter. For example, if you reset the counter to 1000 and the number displayed in this field later is 10000, the number of operations performed is 9000.

Example

1

Disk Page Size (TA_PAGESIZE)

<a name="12070"></a>

Description

This field displays the disk page size used on this machine.

Offset to the TLOG File (TA_TLOGOFFSET)

<a name="12073"></a>

Description

This field displays the size (in pages) of the offset between the beginning of the device and the beginning of the Oracle Tuxedo filesystem that contains the DTP transaction log for this machine.

Offset to the Oracle Tuxedo File (TA_TUXOFFSET)

<a name="12076"></a>

Description

This field displays the size (in pages) of the offset between the beginning of the device and the beginning of the Oracle Tuxedo filesystem that contains the TUXCONFIG file for this machine. (If the offset is greater than 0, then it is placed in the environment of all servers booted on a machine.)

Total Service Load Completed (TA_WKCOMPLETED)

<a name="12078"></a>

Description

This field displays the total service load dequeued and processed successfully by servers running on this machine.

Total Service Load Initiated (TA_WKINITIATED)

<a name="12079"></a>

Description

This field displays the total service load enqueued by clients/servers running on this machine.

Machine Role (TA_ROLE)

<a name="12088"></a>

Description

This field displays the role of this machine, as shown in Table 4‑8.

 

Table 4‑8 Machine Role

Role	Description
MASTER	This machine is the master machine.
BACKUP	This machine is the backup master machine.
OTHER	This machine is neither the master nor the backup master machine.

For more information about using a Master and Backup machine to swap machines, refer to the section, Setting up Master and Backup Machines.

Software Release (TA_SWRELEASE)

<a name="12089"></a>

Description

This field displays the software release for the binary on this machine (or a 0-length string if the binary is not a Oracle Tuxedo master binary).

ACL Statistics Tab

The ACL Statistics tab for machine attributes contains the following fields:

•	Highest Number of Entries in ACL Cache (TA_HWACLCACHE)

•	Number of ACL Cache Hits (TA_ACLCACHEHITS)

•	Number of Accesses to ACL Cache (TA_ACLCACHEACCESS)

•	Number of Failed Accesses to ACL Cache (TA_ACLFAIL)

Highest Number of Entries in ACL Cache (TA_HWACLCACHE)

<a name="12416"></a>

Description

This field displays the high-water number of entries used in the ACL cache.

Number of ACL Cache Hits (TA_ACLCACHEHITS)

<a name="12417"></a>

Description

This field displays the number of accesses to the ACL cache that resulted in a “hit” (that is, the entry was already in the cache).

Number of Accesses to ACL Cache (TA_ACLCACHEACCESS)

<a name="12418"></a>

Description

This field displays the number of accesses to the ACL cache.

Number of Failed Accesses to ACL Cache (TA_ACLFAIL)

<a name="12419"></a>

Description

This field displays the number of accesses to the ACL cache that resulted in an access control violation.

Configuring Transactions (T_TRANSACTION Class)

<a name="T_TRANSACTION"></a>

<a name="C_TRANSACTION"></a>

Transaction attributes are listed in two tabbed tabs with the following labels:

•	General Tab

•	Miscellaneous Tab

General Tab

The General tab of the transactions class contains the following fields:

•	Logical Machine Name, Backup (TA_LMID)

•	Transaction Identifier (TA_XID)

•	Transaction Identifier (from tpsuspend) (TA_TPTRANID)

•	Coordination Logical Machine (TA_COORDLMID)

•	Object State (TA_STATE)

Logical Machine Name, Backup (TA_LMID)

<a name="12323"></a>

Description

This field displays the retrieval machine logical machine identifier. Note that transaction attributes are primarily kept local to a site and coordinated with common transaction identifiers by transaction management servers (TMSs).

Transaction Identifier (TA_XID)

<a name="12322"></a>

Description

This field displays the transaction identifier as returned from tx_info(3) mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.

Transaction Identifier (from tpsuspend) (TA_TPTRANID)

<a name="12321"></a>

Description

This field displays the transaction identifier as returned from tpsuspend(3) mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.

Coordination Logical Machine (TA_COORDLMID)

<a name="12319"></a>

Description

This field displays logical machine identifier of the server group responsible for coordinating the transaction.

Object State (TA_STATE)

<a name="12318"></a>

This field displays the state of the transaction. A transaction can be in one of the following states:

•

ACTIVE

•

ABORTONLY

•

ABORTED

•

COMCALLED

•

READY

•

DECIDED

•

SUSPENDED

Miscellaneous Tab

The Miscellaneous tab of the transactions class contains the following fields:

•	Number of Groups (TA_GRPCOUNT)

•	First Group Index (TA_GRPINDEX)

•	Group Number (TA_GRPNO)

•	Timeout (TA_TIMEOUT)

•	Runtime State (TA_GSTATE)

Number of Groups (TA_GRPCOUNT)

<a name="12314"></a>

Description

This field displays the number of groups identified as participants in the transaction by the information returned from the retrieval site.

First Group Index (TA_GRPINDEX)

<a name="12315"></a>

Description

This field displays the index of the first group specific attribute values (TA_GRPNO and TA_GSTATE) corresponding to this object.

Group Number (TA_GRPNO)

<a name="12316"></a>

Description

This field displays the group number of the participating group.

Timeout (TA_TIMEOUT)

<a name="12317"></a>

Description

This field displays time left, in seconds, before the transaction will time out on the retrieval site. This attribute value is returned only when the transaction state (TA_STATE) is ACTIVE.

Runtime State (TA_GSTATE)

<a name="12320"></a>

Description

This field displays the state, at run time, of the selected transactions for the specified group. Such a transaction can be in one of the following states:

•

ACTIVE

•

ABORTED

•

READONLY

•

READY

•

HCOMMIT

•

HABORT

•

DONE

Creating Groups

<a name="N_GROUP"></a>

To create new Groups:

1.	Select the Groups folder in the tree view.

2.	Select Quick Menu —>New (right-click) to display the New Object window.

3.	Enter values for the following fields:

•	Group Name (TA_SRVGRP)

•	Group Number (TA_GRPNO)

•	Logical Machine Name, Backup (TA_LMID)

4.	Click the Create button to close the window and create the new Group.

Group Name (TA_SRVGRP)

<a name="13016"></a>

<a name="13022"></a>

<a name="13019"></a>

<a name="12135"></a>

<a name="12105"></a>

<a name="12151"></a>

Description

Logical name of the server group.

Valid Values

A string of 0 to 30 characters.

The group name cannot contain an asterisk, a comma, or a colon. The group name must be unique among all group names in the Groups class and all values entered in the Logical Machine Name (TA_LMID) for objects in the Machines class.

This name is used as the value of the SRVGRP parameter in two places: in the Servers tabs (to identify a server as a part of this group), and the Services tab (to identify an instance of a service with its occurrences in the group).

Example

BANKB1

Group Number (TA_GRPNO)

<a name="13014"></a>

<a name="12097"></a>

Description

Number associated with this server group.

Valid Values

An integer in the range 1 to 30000. The number must be unique among all entries in the Groups tabs.

Example

100

Logical Machine Name, Backup (TA_LMID)

<a name="13015"></a>

<a name="12104"></a>

Description

Primary logical machine identifier for this server group (LMID1) and optional secondary logical machine identifier (LMID2).

Valid Values

LMID1[,LMID2]

Notes

Each LMID (logical machine identifier) contains a maximum of 30 characters. Logical machine identifiers specified in this field must be configured already. Each name must be unique within this group’s configuration.

The name of a new group cannot contain an asterisk, comma, or colon.

You are required to specify one machine; specifying a backup machine is optional. If you specify a backup machine and server group migration is enabled, then you will be able to migrate this server group to the backup machine, if necessary.

Example

SITE1, SITE2

Configuring Groups (T_GROUP Class)

<a name="T_GROUP"></a>

<a name="C_GROUP"></a>

Group attributes are listed in three tabbed tabs:

•	General Tab

•

TMS Tab

•

Args Tab

General Tab

The General tab contains the following fields:

•	Group Name (TA_SRVGRP)

•	Group Number (TA_GRPNO)

•	Logical Machine Name, Backup (TA_LMID)

•	Current Logical Machine (TA_CURLMID)

•	Object State (TA_STATE)

Current Logical Machine (TA_CURLMID)

<a name="12101"></a>

Description

Name (expressed as a logical machine identifier) of the machine on which this server group is currently running.

Valid Values

A string of 1 to 30 characters. This attribute is not returned for server groups that are not active.

Example

MACH1

Object State (TA_STATE)

<a name="12099"></a>

Description

This field displays the state of your group. A group can be in one of the following states:

•

ACTIVE

•

INACTIVE

•

MIGRATING

TMS Tab

The TMS tab provides two fields.

•	TMS Name (TA_TMSNAME)

•	TMS Count (TA_TMSCOUNT)

TMS Name (TA_TMSNAME)

<a name="12103"></a>

Description

Name of the transaction manager server a.out file associated with this group. This file is executed by tmboot when you boot this server group.

Valid Values

A string of 0 to 78 characters. The value TMS is reserved to indicate use of the null XA interface. The default is no entry, that is, the null string.

You must enter a value in this field for any group that includes servers that will participate in distributed transactions. (A distributed transaction is a transaction executed across multiple resource managers, and possibly machines, that are started with tpbegin(3), and ended with a tpcommit(3) or tpabort(3) call.)

If you specify a nonempty value other than TMS, then you must also specify a TLOG device for the one or more machines associated with the primary and secondary logical machines for this group.

A unique server identifier is selected automatically for each TM server. You will be able to restart the servers an unlimited number of times.

Example

srvrboot

TMS Count (TA_TMSCOUNT)

<a name="12098"></a>

Description

Number of transaction manager servers to be started for the associated group, if you have specified a value for the TMS Name (TA_TMSNAME).

Valid Values

tmscount

Notes

tmscount is an integer in the range 2 to 10. The default is 3. If you have not specified a value for the TMS Name (TA_TMSNAME), then this field is ignored.

The servers are set up in an MSSQ set automatically.

Args Tab

The Args tab contains the following fields:

•	Open Information (TA_OPENINFO)

•	Close Information (TA_CLOSEINFO)

Open Information (TA_OPENINFO)

<a name="12102"></a>

Description

Information needed to open a particular instance of a particular resource manager, or an indication that such information is not required for this group.

Valid Values

A string of 0 to 256 characters, consisting, if not empty, of four substrings, separated by colons, of the format:

rm_name:fsconfig:dbname:open_mode

These subfields are described in Table 4‑9.

 

Table 4‑9 Subfield

Substring	Description
rm_name	TUXEDO/D for Oracle Tuxedo System/D databases. TUXEDO/SQL for Oracle Tuxedo System/SQL databases. TUXEDO/QM for Oracle Tuxedo /Q databases.
fsconfig	An environment variable that contains the pathname of the database.
dbname	The name of the database.
open_mode	One of readonly or readwrite.

Note:

The /D and /SQL databases are only used by the sample applications provided with Oracle Tuxedo (for example, bankapp) and are not supported for use with the application code.

The default is no entry, that is, the null string.

On a Windows 2000 machine, semicolons are used instead of the colons after fsconfig and dbname.

The Open Information format depends on the requirements of the resource manager vendor. The string required by the vendor must be prefixed by rm_name, which is the published name of the vendor’s transaction (XA) interface, followed immediately by a colon.

This field is ignored if you have not specified a name in the TMS Name (TA_TMSNAME) or if you have specified it as TMS. If you have specified a value for the TMS name but you have not done so for the Open Information field, it means that a resource manager exists for this group but does not require any information for executing an open operation.

Oracle Tuxedo /Q databases use the following format:

TUXEDO/QM:qmconfig:qspace

Limitation

Run-time modifications to this attribute does not affect active servers in the group.

Example

TUXEDO/SQL:/usrq/apps/bank/bankdq:billing_db:readwrite

Close Information (TA_CLOSEINFO)

<a name="12100"></a>

Description

Information needed when the resource manager is being closed.

Valid Values

A string of 0 to 256 characters, consisting, if not empty, of three substrings, separated by colons, of the format:

rm_name:entity_name:open_mode

These subfields are described in Table 4‑10.

 

Table 4‑10 Subfield

Substring	Description
rm_name	TUXEDO/D for Oracle Tuxedo System/D databases. TUXEDO/QM for Oracle Tuxedo /Q databases.
entity_name	The name of the database or queue space.
open_mode	One of readonly or readwrite.

The default is no entry, that is, the null string.

On Windows 2000 and NetWare machine, semicolons are used instead of the colons after fsconfig and dbname.

The Close Information format depends on the requirements of the resource manager vendor. The string required by the vendor must be prefixed by rm_name, which is the published name of the vendor’s transaction (XA) interface, followed immediately by a colon.

This field is ignored if you have not specified a name in the TMS Name (TA_TMSNAME) or if you have specified it as TMS. If you have specified a value for the TMS name but you have not done so for the Close Information field, it means that a resource manager exists for this group but does not require any information for executing a close operation.

Limitations

Run-time modifications to this attribute will not affect active servers in the group.

Example

TUXEDO/D:billing_db:readwrite

Creating Servers

<a name="N_SERVER"></a>

To create new Servers:

1.	Select the Servers folder in the tree view.

2.	Select Quick Menu —>New (right-click) to display the New Object window.

3.	Enter values for the following fields:

•	Group Name (TA_SRVGRP)

•	Server ID (TA_SRVID)

•	Server Name (TA_SERVERNAME)

4.	Click the Create button to close the window and create the new Server.

Server ID (TA_SRVID)

<a name="13017"></a>

<a name="12124"></a>

Description

A numeric identifier, selected by the administrator, that uniquely identifies a server within a group.

Valid Values

An integer in the range 1 to 30000.

If multiple instances of servers are desired, do not use consecutive numbers. Instead, leave enough room for the system to assign additional server IDs up to the number specified in the Max Servers Activated (TA_MAX) field.

Example

4

Server Name (TA_SERVERNAME)

<a name="13018"></a>

<a name="12133"></a>

Description

Pathname of the execpathnameutable file for the server.

Valid Values

A string of 1 to 78 characters. The server identified in this field will run on the machines specified in the Logical Machine Name, Backup (TA_LMID) for the Groups class to which this server belongs. If you specify a relative pathname, a search will be done for the executable file in the following order:

1.	The directory specified in the “Application Directory” field.

2.	The bin subdirectory of the directory specified in the Tuxedo Root Directory (Full Path) (TA_TUXDIR).

3.

/bin

4.

/usr/bin

5.	The pathname specified as the first PATH= entry in the machine environment file (if one exists).

Example

/home/bankapp/credit_dept/ACCT

Configuring Servers (T_SERVER Class)

<a name="T_SERVER></a>

<a name="C_SERVER></a>

Group attributes are listed in six tabbed folders:

•	General Tab

•

Args Tab

•	Commands Tab

•	System Parameters Tab

•	Statistics 1 Tab

•	Statistics 2 Tab

•	Statistics 3 Tab

General Tab

The General tab contains the following fields:

•	Group Name (TA_SRVGRP)

•	Group Number (TA_GRPNO)

•	Server ID (TA_SRVID)

•	Server Name (TA_SERVERNAME)

•	Environment File (TA_ENVFILE)

•	Current Logical Machine Name (TA_LMID)

•	Object State (TA_STATE)

Group Number (TA_GRPNO)

<a name="12420"></a>

Description

This field displays the group number associated with this server’s group.

Environment File (TA_ENVFILE)

<a name="12128"></a>

Description

This field displays the name of the file that defines the environment in which the a.out file is executed by tmboot.

Valid Values

A string of 0 to 78 characters. The default is no entry, that is, the null string.

Example

environ

Current Logical Machine Name (TA_LMID)

<a name="12422"></a>

Description

This field displays the current logical machine on which the server is running.

Object State (TA_STATE)

<a name="12125"></a>

Description

This field displays the state of your server. A server can be in one of the following states:

•

ACTIVE

•

INACTIVE

•

MIGRATING

•

CLEANING

•	RESTARTING

•

SUSPENDED

•	PARTITIONED

•

DEAD

Args Tab

The Args tab contains the following fields:

•	Grace Period (TA_GRACE)

•	Max Servers Activated (TA_MAX)

•	Min Servers Activated (TA_MIN)

•	Max Generations (TA_MAXGEN)

•	Activation Sequence Number (TA_SEQUENCE)

•	System Access (TA_SYSTEM_ACCESS)

Grace Period (TA_GRACE)

<a name="12106"></a>

Description

The amount of time (in seconds) during which this server can be started.

Valid Values

An integer in the range 0 to 2147483647. The default is 86400 (the number of seconds in 24 hours. The Automatic Restart (TA_RESTART) must be set to Yes. The equation used to calculate the grace period is:

(MAXGEN - 1)

where MAXGEN is set in the Max Generations (TA_MAXGEN). As soon as one grace period ends, the next one begins. Thus setting the value of this field to 0 removes all limitations. The server can then be restarted an unlimited number of times.

Max Servers Activated (TA_MAX)

<a name="12107"></a>

Description

The maximum number of times this server can be reactivated.

Valid Values

An integer in the range 1 to 1001. The default is 1. Use this parameter to prevent having to repeat an entry for multiple occurrences of the same server.

Example

10

Min Servers Activated (TA_MIN)

<a name="12109"></a>

Description

The minimum number of times this server can be reactivated.

Valid Values

An integer in the range 1 to 1001. The default is 1. Use this parameter to prevent having to repeat an entry for multiple occurrences of the same server.

Limitation: Run-time modifications to this attribute will not affect a running server.

If you have specified a value in the Request Queue (TA_RQADDR) and the Min Servers Activated value is greater than 1, then an MSSQ set is formed.

Max Generations (TA_MAXGEN)

<a name="12108"></a>

Description

The maximum number of times this server can be started within the period specified in the Grace Period (TA_GRACE).

Valid Values

An integer in the range 1 to 255. The default is 1. To restart the server, the value in this field must be 2 or less.

Limitation

Run-time modifications to this attribute will affect a running server and all other active servers with which it is sharing a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of booting in subsequent activations unless the administrator ensures that all servers sharing a queue have the same value for this attribute.

Activation Sequence Number (TA_SEQUENCE)

<a name="12121"></a>

Description

The order in which servers are activated and deactivated.

If a value is specified in this field for some servers but not for others, those with assigned numbers will be activated first. The servers for which numbers have not been assigned are then activated in the order in which they appear in the configuration file. If the same value (for “Activation Sequence Number”) is assigned to more than one server, those servers may be activated in parallel.

Valid Values

An integer in the range 1 to 9999. The default is for servers to be activated in the order in which they are listed in the configuration file, and deactivated in reverse order.

System Access (TA_SYSTEM_ACCESS)

<a name="12134"></a>

Description

This field controls the allocation of shared memory space.

Valid Values

One of the methods presented in the drop-down menu. The available choices are shown in Table 4‑11.

 

Table 4‑11 The Available Choices

Method	Description
FASTPATH	This method allows for faster processing, but is less secure. Processes that share memory space are vulnerable to potential software defects on one of the processes. This is the default method.
PROTECTED	The shared memory for Oracle Tuxedo Internal tables is not accessible from code outside of Oracle Tuxedo libraries.

Limitation

Run-time modifications to this attribute will not affect a running server.

Commands Tab

The Commands tab contains the following fields:

•	Executable Options (TA_CLOPT)

•	Restart Command (TA_RCMD)

•	Automatic Restart (TA_RESTART)

Executable Options (TA_CLOPT)

<a name="12126"></a>

Description

Command-line options to be passed to the server when it is activated.

Valid Values

A string of 0 to 256 characters. The default is -A.

Limitation

Run-time modifications to this attribute will not affect a running server.

Restart Command (TA_RCMD)

<a name="12129"></a>

Description

A command, specified by the application, that is executed in parallel with the system restart of an application server.

Valid Values

A string of 0 to 78 characters. The default is no entry, that is, the null string. This command must be an executable UNIX system file.

Servers sharing a request queue (that is, equal values in the Request Queue (TA_RQADDR) on the System Parameters tab) should have equal values for this attribute. If they do not, then the first server activated will establish the run-time value associated with all servers on the queue.

Limitation

Run-time modifications to this attribute will affect a running server and all other active servers with which it is sharing a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of booting in subsequent activations, unless the administrator ensures that all servers sharing a queue have the same value for this attribute.

Automatic Restart (TA_RESTART)

<a name="12131"></a>

Description

Determines whether or not the server is restartable.

Valid Values

Enter either Yes or No.

The default is No. You must specify Yes in this field if server migration has been specified for this server group in the following manner: You selected MIGRATE in the Options (TA_OPTIONS) of the General tab for Configuring Domain Resources (T_DOMAIN Class), and you designated an alternate site in the Logical Machine Name, Backup (TA_LMID) of the General tab in the Groups class.

Servers sharing a request queue (that is, equal values in the Request Queue (TA_RQADDR) on the System Parameters tab) should have equal values for this attribute. If they do not, then the first server activated will establish the run-time value associated with all servers on the queue.

Limitation

Run-time modifications to this attribute will affect a running server and all other active servers with which it is sharing a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of booting in subsequent activations, unless the administrator ensures that all servers sharing a queue have the same value for this attribute.

System Parameters Tab

The System Parameters tab contains the following fields:

•	Request Queue (TA_RQADDR)

•	Reply Queue (TA_REPLYQ)

•	Request Queue Perm (TA_RQPERM)

•	Reply Queue Perm (TA_RPPERM)

•	Reply Message Queue ID (TA_RPID)

•	Request Message Queue ID (TA_RQID)

•	Process ID (TA_PID)

•	Conversations Allowed (TA_CONV)

Request Queue (TA_RQADDR)

<a name="12132"></a>

Description

A symbolic name that points to the address queue of the server.

Valid Values

A string of 0 to 30 characters. The default is GRPNO.SRVID, where:

•	GRPNO is the value specified in the Group Number (TA_GRPNO) of the General tab for the Groups class.

•	SRVID is the value specified in the Server ID (TA_SRVID) of the General tab for the Servers class).

Multiple Server, Single Queue (MSSQ) sets are established by using the same symbolic name for more than one server or by specifying the Min Servers Activated (TA_MIN) to be greater than 1. All members of an MSSQ set must offer an identical set of services and must be in the same server group.

Reply Queue (TA_REPLYQ)

<a name="12130"></a>

Description

Determines whether or not a reply queue, separate from the request queue, is to be set up for this server.

Valid Values

Enter either Yes or No.

Notes

The default is Yes.

If you specify Yes, the server is a member of a Multiple Server, Single Queue (MSSQ) set and contains services programmed to receive reply messages. This ensures that the individual reply queue is created for this server. If this is not done, the reply is sent to the request queue shared by all servers of the MSSQ set, and there is no way of assuring that it will be picked up by the server waiting for it. It should be standard practice to specify Yes for all member servers of an MSSQ set if replies are anticipated. Servers in an MSSQ set must have identical service offerings, so it is reasonable to expect that if one server in the set expects replies, any server in the set may do likewise.

If you specify No, only one server uses the request queue. Replies are then picked up from the request queue without difficulty.

Request Queue Perm (TA_RQPERM)

<a name="12120"></a>

Description

The numeric permissions assigned to the request queue for this server.

Valid Values

A four-digit octal number (of which the first character is always 0) in the range 0001 to 0777 that represents the UNIX system read and write permissions (as defined by the UNIX system) that you set for the request queue for this server. For example, the value 0666 signifies that permission to read and write (6) has been given to the designated user, the designated group, and any other user. The default is 0666. If you do not enter a value in this field, the permissions of the bulletin board, as specified by the Permission (TA_PERM) on the Security tab for the Application Resources class (T_DOMAIN), are implemented.

If the default is active, your application could be open to the owner of any login on the system, which is not recommended.

Limitation

This attribute is specific to UNIX systems; it might not be returned if the platform on which the application is being run is not UNIX-based.

Reply Queue Perm (TA_RPPERM)

<a name="12119"></a>

Description

UNIX system-style permissions assigned to the server’s reply queue.

Valid Values

A four-digit octal number, in the range 0001 to 0777, as described under Request Queue Perm (TA_RQPERM). The default is the value you entered for this field in the Permission (TA_PERM) on the Security tab for the Application Resources class (T_DOMAIN).

Limitation

This attribute is specific to UNIX systems; it might not be returned if the platform on which the application is being run is not UNIX-based.

Example

0666

Reply Message Queue ID (TA_RPID)

<a name="12425"></a>

Description

This field displays the UNIX system message queue identifier for the server’s reply queue. If a separate reply queue is not allocated (the Reply Queue (TA_REPLYQ) specified No), then this attribute will be the same as the value of the Request Message Queue ID (TA_RQID).

Limitation

This field is specific to UNIX systems; there might be no value displayed here if the platform on which the application is being run is not UNIX-based.

Request Message Queue ID (TA_RQID)

<a name="12426"></a>

Description

This field displays the UNIX system message queue identifier for the server’s request queue. If a separate queue is not allocated (the Reply Queue (TA_REPLYQ) specified No), then this attribute will be the same as the value of the Reply Message Queue ID (TA_RPID).

Limitation

This field is specific to UNIX systems; there might be no value displayed here if the platform on which the application is being run is not UNIX-based.

Process ID (TA_PID)

<a name="12424"></a>

Description

This field displays the UNIX system process identifier for the server. Note that this may not be a unique attribute since servers may be located on different machines allowing for duplication of process identifiers.

Limitation

This field is specific to UNIX systems; there might be no value displayed here if the platform on which the application is being run is not UNIX-based.

Conversations Allowed (TA_CONV)

<a name="12127"></a>

Description

This field causes the number of conversations initiated through this server by tpconnect(3) since Oracle Tuxedo was booted (or you reset the counter) to be displayed in the Number of Conversations (TA_NUMCONV).

Valid Values

Enter either Yes or No.

Statistics 1 Tab

The Statistics 1 tab contains the following fields:

•	Number of Conversations (TA_NUMCONV)

•	Number of Dequeues (TA_NUMDEQUEUE)

•	Number of Enqueues (TA_NUMENQUEUE)

•	Number of Posts (TA_NUMPOST)

•	Number of Requests (TA_NUMREQ)

•	Total Number of Workload Completed (TA_TOTWORKL)

•	Restarting Time (TA_TIMERESTART)

•	Starting Time (TA_TIMESTART)

•	Time Left in Current Service (TA_SVCTIMEOUT)

•	Time Left for Reply (TA_TIMELEFT)

Number of Conversations (TA_NUMCONV)

<a name="12110"></a>

Description

This field displays the number of tpconnect(3) conversations initiated by this server since Oracle Tuxedo was booted (or you reset the counter).

Valid Values

An integer greater than or equal to 0.

Example

1500

Number of Dequeues (TA_NUMDEQUEUE)

<a name="12111"></a>

Description

This field displays the number of tpdequeue(3) operations initiated by this server since Oracle Tuxedo was booted (or since you reset the counter).

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Enqueues (TA_NUMENQUEUE)

<a name="12112"></a>

Description

This field displays the number of tpenqueue(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset the counter).

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Posts (TA_NUMPOST)

<a name="12113"></a>

Description

This field displays the number of tppost(3) operations performed from this machine since Oracle Tuxedo was booted (or you reset the counter).

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Requests (TA_NUMREQ)

<a name="12114"></a>

Description

This field displays the number of tpacall(3) or tpcall(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset the counter).

Valid Values

An integer greater than or equal to 0.

Example

0

Total Number of Workload Completed (TA_TOTWORKL)

<a name="12123"></a>

Description

This field displays the total work load completed by this server.

Valid Values

An integer greater than or equal to 0.

For conversational servers, the value of this field indicates the workload of completed incoming conversations. This is a run-time attribute that is kept across server restart but is lost at server shutdown.

Example

0

Restarting Time (TA_TIMERESTART)

<a name="12398"></a>

Description

This field displays the amount of time since restart.

Valid Values

An integer greater than or equal to 0, representing the seconds since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on the machine identified in the Current Logical Machine Name (TA_LMID). This value shows when the server was last started or restarted.

Starting Time (TA_TIMESTART)

<a name="12399"></a>

Description

This field displays the amount of time since the server was first started.

Valid Values

An integer greater than or equal to 0, representing the seconds since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on the machine identified in the Current Logical Machine Name (TA_LMID). This value shows when the server was first started.

Restarts of the server do not reset this value; however, if the value entered in the Max Generations (TA_MAXGEN) on the Args tab and the amount of time specified in the Grace Period (TA_GRACE) on the Args tab has expired, the value in this field (Starting Time) will be reset to the time of the restart.

Time Left in Current Service (TA_SVCTIMEOUT)

<a name="12436"></a>

Description

This field displays the time remaining for this server to process the current service request (if any).

Valid Values

An integer greater than or equal to 0, representing the number of seconds. A value of 0 for an active service means that no timeout processing is being performed.

Time Left for Reply (TA_TIMELEFT)

<a name="12437"></a>

Description

This field displays the time remaining for this server to receive the reply for which it is currently waiting before it will time out.

Valid Values

An integer greater than or equal to 0, representing the number of seconds. This timeout can be a transactional timeout or a blocking timeout.

Statistics 2 Tab

The Statistics 2 tab contains the following fields:

•	Number of Subscriptions (TA_NUMSUBSCRIBE)

•	Number of Transactions (TA_NUMTRAN)

•	Number of Transactions Aborted (TA_NUMTRANABT)

•	Number of Transactions Committed (TA_NUMTRANCMT)

•	Total Number of Requests Completed (TA_TOTREQC)

•	Statistics 3 Tab

Number of Subscriptions (TA_NUMSUBSCRIBE)

<a name="12115"></a>

Description

This field displays the number of subscriptions made by this server.

Valid Values

An integer greater than or equal to 0, the number of subscriptions made by this server with tpsubscribe(3) since Oracle Tuxedo was booted (or you reset the counter).

Example

0

Number of Transactions (TA_NUMTRAN)

<a name="12116"></a>

Description

This field displays the number of transactions begun by this server since its last start or restart.

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Transactions Aborted (TA_NUMTRANABT)

<a name="12117"></a>

Description

This field displays the number of transactions aborted by this server since its last start or restart.

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Transactions Committed (TA_NUMTRANCMT)

<a name="12118"></a>

Description

This field displays the number of transactions committed by this server since its last start or restart.

Valid Values

An integer greater than or equal to 0.

Example

0

Total Number of Requests Completed (TA_TOTREQC)

<a name="12122"></a>

Description

This field displays the number of requests completed by this server.

Valid Values

An integer greater than or equal to 0. For conversational servers, the value in this field indicates the number of completed incoming conversations. This is a run-time attribute that is kept across server restart but is lost at server shutdown.

Example

0

Statistics 3 Tab

The Statistics 3 tab contains the following fields:

•	Client Logical Machine Name (TA_CLTLMID)

•	Client Process ID (TA_CLTPID)

•	Client Expecting Reply (TA_CLTREPLY)

•	Commit Control (TA_CMTRET)

•	Current Number of Conversations (TA_CURCONV)

•	Current Number of Requests (TA_CURREQ)

•	Current Service (TA_CURRSERVICE)

•	Current Time (TA_CURTIME)

•	Last Group Contacted (TA_LASTGRP)

•	Current Transaction Level (TA_TRANLEV)

Client Logical Machine Name (TA_CLTLMID)

<a name="12427"></a>

Description

This field displays the logical machine for the initiating client or server. The initiating client or server is the process that made the service request on which the server is currently working.

Client Process ID (TA_CLTPID)

<a name="12428"></a>

Description

This field displays the UNIX system process identifier for the initiating client or server.

Limitation

This field is specific to UNIX systems; there might be no value displayed here if the platform on which the application is being run is not UNIX-basedUNIX-based.

Client Expecting Reply (TA_CLTREPLY)

<a name="12429"></a>

Description

This field displays whether or not the initiating client or server is expecting a reply.

Valid Values

Enter either Yes or No.

Commit Control (TA_CMTRET)

<a name="12430"></a>

Description

This field displays the setting of the TP_COMMIT_CONTROL characteristic for this server. For details about setting this characteristic, refer to the description of the tpscmt(3) function in the BEA Tuxedo ATMI C Function Reference manual, and the Default Commit Control (TA_CMTRET) in the File Formats, Data Descriptions, MIBs, and System Processes manual.

Current Number of Conversations (TA_CURCONV)

<a name="12431"></a>

Description

Number of tpconnect(3) conversations initiated by this server that are still active.

Valid Values

An integer greater than or equal to 0.

Example

1500

Current Number of Requests (TA_CURREQ)

<a name="12432"></a>

Description

This field displays the number of requests that have been initiated by this server with tpcall(3) that are still active.

Current Service (TA_CURRSERVICE)

<a name="12433"></a>

Description

This field displays the service name on which the server is currently working (if any).

Current Time (TA_CURTIME)

<a name="12434"></a>

Description

This field displays the current time (in seconds) since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on the machine identified in the Current Logical Machine Name (TA_LMID). This attribute can be used to compute elapsed time from the Starting Time (TA_TIMESTART) and Restarting Time (TA_TIMERESTART) attribute values.

Last Group Contacted (TA_LASTGRP)

<a name="12435"></a>

Description

This field displays the server group number (as shown in the Group Number (TA_GRPNO)) of the last service request made or conversation initiated from this server outward.

Current Transaction Level (TA_TRANLEV)

<a name="12438"></a>

Description

This field displays the current transaction level for this server. A value of 0 means that the server is not currently involved in a transaction.

Creating Routing Tables

<a name="N_ROUTING"></a>

To create new Routing Tables:

1.	Select the Routing Tables folder in the tree view.

2.	Select Quick Menu —>New (right-click) to display the New Object window.

3.	Enter values for the following fields:

•	Routing Table Name (TA_ROUTINGNAME)

•	Buffer Type (TA_BUFTYPE)

•	Field Name (TA_FIELD)

•	Routing Table Ranges (TA_RANGES)

4.	Click the Create button to close the window and create the new Routing Tables.

Routing Table Name (TA_ROUTINGNAME)

<a name="13052"></a>

Description

The name of the routing criteria table.

Valid Values

A string of 1 to 15 characters.

Example

BRNCH

Buffer Type (TA_BUFTYPE)

<a name="13050"></a>

<a name="12303"></a>

Description

A list of types and subtypes (specified with the relevant types) of data buffers for which this routing entry is valid.

Valid Values

A string of 1 to 256 characters, of the following format:

type1[:subtype1[,subtype2 ...]][;type2[:subtype3[, ...]]] ...

Entries for types are separated by semicolons. Within a type/subtype pair, the type and subtype components are separated by a colon. Subtype names should not contain semicolon, colon, comma, or asterisk characters.

Duplicate type/subtype pairs can not be specified for the same routing criterion name; more than one routing entry can have the same criterion name as long as the type/subtype pairs are unique. If multiple buffer types are specified for a single routing entry, the data types of the routing field for each buffer type must be the same.

A maximum of 32 type/subtype combinations are allowed.

The valid types are:

•

FML

•

VIEW

•

X_C_TYPE

•

X_COMMON

•

XML

No subtype can be specified for the FML type. Subtypes are required for VIEW, X_C_TYPE, and X_COMMON. (The wildcard character, *, is not allowed.)

Example

FML

 

Field Name (TA_FIELD)

<a name="13051"></a>

<a name="12304"></a>

Description

Routing field name.

Valid Values

A string of 1 to 30 characters.

This field is assumed to be an FML buffer or view field name that is identified in an FML field table (using the FLDTBLDIR and FIELDTBLS environment variables) or an FML view table (using the VIEWDIR and VIEWFILES environment variables), respectively. This information is used to get the associated field value for data-dependent routing during the sending of a message.

Example

ACCOUNT_ID

Routing Table Ranges (TA_RANGES)

<a name="13053"></a>

<a name="12306"></a>

Description

The ranges and associated server groups for the routing field.

Valid Values

lower[-upper]:group[, lower[-upper]:group[, ...]]

These constructs have the following values as shown in Table 4‑12.

 

Table 4‑12 Valid Values

Construct	Description
lower	Signed numeric value or character string in single quotes. Its value must be less than or equal to that of upper.
upper	Signed numeric value or character string in single quotes.
group	The associated group to which the request is routed if the field matches the range. A group name of "*'' indicates that the request can go to any group that has a server offering the desired service.

Notes

The values MIN and MAX can be used to indicate the minimum and maximum values for the data type of the associated field on the machine. The asterisk, a wildcard character, is a metacharacter that, when used in the position of a range, indicates any values not covered by any previous ranges. Only one wildcard range is allowed per entry and it should be listed last, since ranges following it will be ignored.

The routing field can be of any data type supported in FML. A numeric routing field must have numeric range values, and a string routing field must have string range values.

String range values for string, carray, and character field types must be delimited by single quotes and cannot be preceded by a sign. (To embed a single quotation mark in a character string value, precede it with two backslashes.) Short and long integer values are a string of digits, optionally preceded by a plus or minus sign. Floating point numbers are of the window accepted by the C compiler or atof(3):

•	An optional sign

•	A string of digits optionally containing a decimal point

•	An optional e or E followed by an optional sign or space, followed by an integer

Examples

0:BANKB0

10000-59999:BANKB1

In the following example, entries in the range 60,000 to 69,999 are routed to BANKB2, those in the range 70,000 to 79,999 to BANKB3, and the rest to BANKB4.

60000-69999:BANKB2, 70000-79999:BANKB3, *:BANKB4

In the following example, all entries less than or equal to -5 are routed to BANKB6.

'MIN--5':BANKB6

In the following example, all entries greater than or equal to 6 are routed to BANKB7.

'6-MAX':BANKB7

Configuring Routing Tables (T_ROUTING Class)

<a name="T_ROUTING"></a>

<a name="C_ROUTING"></a>

Routing table attributes are listed in one tabbed folder labeled General Tab.

General Tab

The General tab contains the following fields:

•	Routing Table Name (TA_ROUTINGNAME)

•	Object State (TA_STATE)

•	Buffer Type (TA_BUFTYPE)

•	Field Name (TA_FIELD)

•	Routing Table Ranges (TA_RANGES)

Routing Table Name (TA_ROUTINGNAME)

<a name="12305"></a>

Description

This field displays the name of the routing criteria table specified in the Routing Table Name (TA_ROUTINGNAME) of the Create New Object window.

Valid Values

rctable

Notes

rctable is a string of 1 to 15 characters.

Example

BRNCH_1

Object State (TA_STATE)

<a name="12302"></a>

Description

This field displays the state of your routing table. A routing table has only one state: VALID.

Creating Service Defaults

<a name="N_SERVICE"></a>

To create new Service Defaults:

1.	Select the Service Defaults folder in the tree view.

2.	Select Quick Menu —>New (right-click) to display the New Object window.

3.	Enter values for the following field:

Service Name (TA_SERVICENAME)

4.	Click the Create button to close the window and create the new Service Defaults.

Service Name (TA_SERVICENAME)

<a name="13020"></a>

<a name="13021"></a>

<a name="12144"></a>

<a name="12150"></a>

Description

The name of the service.

Valid Values

A string of 1 to 127 characters.

Example

OPEN_ACCT

Configuring Service Defaults (T_SERVICE Class)

<a name="T_SERVICE"></a>

<a name="C_SERVICE"></a>

<a name="12305"></a>

Service defaults class attributes are listed in two tabbed folders:

•	General Tab

•	System Parameters Tab

General Tab

The General tab contains the following fields:

•	Service Name (TA_SERVICENAME)

•	Routing Table Name (TA_ROUTINGNAME)

•	Buffer Type (TA_BUFTYPE)

•	Object State (TA_STATE)

Routing Table Name (TA_ROUTINGNAME)

<a name="12143"></a>

Description

The name of the routing criteria table used for this service when doing data-dependent routing.

Valid Values

A string of 1 to 15 characters. The default is no entry, that is, the null string; it means data-dependent routing is not done for this service.

If multiple entries exist for the same service name but with different SRVGRP (see Group Name (TA_SRVGRP)) parameters, the Routing Table Name parameter must be the same for all of these entries.

Buffer Type (TA_BUFTYPE)

<a name="12142"></a>

Description

A list of types and subtypes of data buffers accepted by this service.

Valid Values

A string of 1 to 256 characters, of the following format:

type1[:subtype1[,subtype2 ...]][;type2[:subtype3[, ...]]] ...

Types of data buffers provided with Oracle Tuxedo:

•	FML (for FML buffers)

•

VIEW

•

X_C_TYPE

•	X_COMMON (for FML views)

•	STRING (for null-terminated character arrays)

•	CARRAY or X_OCTET (for a character array that is neither encoded nor decoded during transmission)

•

XML

Of these types, only VIEW, X_C_TYPE, and X_COMMON have subtypes. A view subtype gives the name of the particular view expected by the service. Application types and subtypes can also be added (see the UNIX manpage on tuxtypes(5)). For a type that has subtypes, an asterisk can be specified for the subtype to indicate that the service accepts all subtypes for the associated type.

A single service can interpret only a fixed number of buffer types, namely those found in its buffer type switch (see the UNIX manpage on tuxtypes(5)). If this parameter is set to ALL, that service will accept all buffer types found in its buffer type switch. Leaving this field blank is equivalent to setting it to ALL. If multiple entries exist for the same service name but with different SRVGRP parameters, this parameter must be the same for all of these entries.

A maximum of 32 type/subtype combinations are allowed. A type name can be 8 characters or less in length and a subtype name can be 16 characters or less in length. Type and subtype names should not contain semicolon, colon, comma, or asterisk characters; otherwise it is difficult to see where type and subtype values end.

The default is ALL.

Example

The following specifies that the service takes FML buffers:

FML

The following specifies that the service takes all FML views:

VIEW:*

Object State (TA_STATE)

<a name="12140"></a>

This field displays the state of your default service. A default service can be in one of the following states:

•

ACTIVE

•

INACTIVE

System Parameters Tab

The System Parameters tab contains the following fields:

•	Auto Transaction Mode (TA_AUTOTRAN)

•	Service Load (TA_LOAD)

•	Priority (TA_PRIO)

•	Service Time Out (TA_SVCTIMEOUT)

•	Transaction Time (TA_TRANTIME)

Auto Transaction Mode (TA_AUTOTRAN)

<a name="12141"></a>

<a name="12146"></a>

Description

This field specifies whether or not a transaction should automatically be started if a request message is received for this service and the request is not already in transaction mode.

Valid Values

Enter either Yes or No. The default is No.

Limitation

Run-time updates to this attribute are not reflected in active service group objects.

Note:

This field is available only for DTP (distributed transaction processing) applications.

Service Load (TA_LOAD)

<a name="12136"></a>

<a name="12145"></a>

Description

The relative load that the service imposes on the system.

Valid Values

An integer in the range 1 to 32767. The default is 50.

Service loads are used for load balancing purposes; that is, queues with higher enqueued workloads are less likely to be chosen for a new request. Service loads have meaning only if the value of the Load Balancing Enabled (TA_LDBAL) for the domain class is Yes.

Limitation

Run-time updates to this attribute are not reflected in active groups (in the Groups class).

Priority (TA_PRIO)

<a name="12137"></a>

<a name="12147"></a>

Description

A number that assigns a dequeueing priority to the service request.

Valid Values

An integer in the range 1 to 100. The default is 50. Higher numbers mean higher priority.

This number is considered relative to the priority assigned to other services offered in the same server. Oracle Tuxedo software prevents services with low priorities from remaining enqueued forever behind a continuing stream of higher priority requests. After every tenth request dequeued by priority, Oracle Tuxedo takes one off the bottom of the queue. When a value is specified in this field, it affects only priority when the system is activated.

Limitation

Run-time updates to this attribute are not reflected in active service group objects.

Service Time Out (TA_SVCTIMEOUT)

<a name="12138"></a>

<a name="12148"></a>

Description

The time limit (in seconds) for processing requests for this service name.

Valid Values

An integer greater than or equal to 0, representing the number of seconds. The default is 0.

Servers processing service requests for this service are terminated if they exceed the specified time limit in processing the request. A value of 0 for this attribute indicates that the service should not be terminated.

Limitations

Run-time updates to this attribute are not reflected in active objects in the Groups class.

Transaction Time (TA_TRANTIME)

<a name="12139"></a>

<a name="12149"></a>

Description

The default timeout period for a transaction automatically started for the associated service.

Valid Values

An integer in the range 0 to 2147483647, representing seconds. The default is 30 seconds. A value of 0 implies the maximum timeout value for the machine.

(Transactions are started automatically when a request not in transaction mode is received and the value for the service (in the Auto Transaction Mode (TA_AUTOTRAN) is Yes.

Limitation

Run-time updates to this attribute are not reflected in active GROUPS.

Example

90

Creating Services

<a name="N_SVCGRP"></a>

To create new Services:

1.	Select the Services folder in the tree view.

2.	Select Quick Menu —>New (right-click) to display the New Object window.

3.	Enter values for the following field:

•	Service Name (TA_SERVICENAME)

•	Group Name (TA_SRVGRP)

4.	Click the Create button to close the window and create the new Service.

Configuring Services (T_SVCGRP Class)

<a name="T_SVCGRP"></a>

<a name="C_SVCGRP"></a>

Services class attributes are listed in two tabbed folders:

•	General Tab

•	System Parameters Tab

General Tab

The General tab contains the following fields:

•	Service Name (TA_SERVICENAME)

•	Group Name (TA_SRVGRP)

•	Service Type (TA_SVCTYPE)

•	Service Request Name (TA_SVCRNAM)

•	Object State (TA_STATE)

Service Type (TA_SVCTYPE)

<a name="12152"></a>

Description

This field displays the type of service.

Valid Values

Enter one of the following values shown in Table 4‑13.

 

Table 4‑13 Valid Values

Construct	Description
APP	An application-defined service name.
CALLABLE	A system-provided, callable service.
SYSTEM	A system provided and system callable service.

Service Request Name (TA_SVCRNAM)

<a name="12153"></a>

Description

Function name within the associated server assigned to process requests for this service.

Valid Values

A string of 1 to 127 characters. The default is the value you entered in the Service Name (TA_SERVICENAME).

On a SET request, this server must be able to map the function name to a function using its symbol table to successfully advertise the service. In some situations (for example, direct calls to tpadvertise(3) by the server), the function name for an active service object will not be known and a question mark will be returned as the attribute value.

Limitation

You can enter a value in this field only when changing the state of the service from inactive to active.

Example

SERVC2

Object State (TA_STATE)

<a name="12154"></a>

Description

This field displays the current state of the service. A service can be in one of the following states:

•

ACTIVE

•

INACTIVE

•

SUSPENDED

•	PARTITIONED

System Parameters Tab

The System Parameters tab contains the following fields:

•	Service Load (TA_LOAD)

•	Auto Transaction Mode (TA_AUTOTRAN)

•	Priority (TA_PRIO)

•	Service Time Out (TA_SVCTIMEOUT)

•	Transaction Time (TA_TRANTIME)

Creating Devices

<a name="N_DEVICE"></a>

To create new Devices:

1.	Select the Devices folder in the tree view.

2.	Select Quick Menu —>New (right-click) to display the New Object window.

3.	Enter values for the following fields:

•	Full Path to Device (TA_CFGDEVICE)

•	Logical Machine Name, Backup (TA_LMID)

•	Device Name (Full Path) (TA_DEVICE)

•	Numeric Offset to Start of Disk Space (in Pages) (TA_DEVOFFSET)

•	Disk Area Size (in Pages) (TA_DEVSIZE)

4.	Click the Create button to close the window and create the new Device.

Full Path to Device (TA_CFGDEVICE)

<a name="13047"></a>

<a name="12311"></a>

Description

Absolute pathname of the file or device in which the Oracle Tuxedo filesystem is stored (or is to be stored).

Valid Values

A string of 2 to 64 characters.

Example

/home/apps/bankapp/tuxconfig

Logical Machine Name, Backup (TA_LMID)

<a name="13049"></a>

<a name="12313"></a>

Description

Name (expressed as a logical machine identifier) of the machine on which this device is located

Valid Values

LMID1[,LMID2]

Notes

Each LMID (logical machine identifier) contains a maximum of 30 characters. The default is the local machine, as a single-machine application.

This attribute can be used as a key field in both unbooted and booted applications as long as they are already configured (that is, at least one machine is defined). This name is required as a key field on SET operations when you are accessing a booted application.

You can assign a value to this field only in a configured application. If you enter a value in this field when accessing the Devices class in an unconfigured application, it will be ignored.

Device Name (Full Path) (TA_DEVICE)

<a name="13048"></a>

Description

Absolute pathname of the device list entry.

Valid Values

A string of 2 to 64 characters. The default is the pathname entered in the Full Path to Device (TA_CFGDEVICE).

This field is optional.

Numeric Offset to Start of Disk Space (in Pages) (TA_DEVOFFSET)

<a name="13045"></a>

<a name="12308"></a>

Description

The offset between the beginning of this device and the point at which the space on this device is reserved for use by the Oracle Tuxedo VTOC specified by the value you entered in the Full Path to Device (TA_CFGDEVICE).

Valid Values

An integer greater than or equal to 0. The default is 0.

Limitation

This attribute must be set to at creation time 0 for the first device list entry (TA_DEVICE) on the Oracle Tuxedo filesystem (TA_CFGDEVICE).

This field is optional.

Disk Area Size (in Pages) (TA_DEVSIZE)

<a name="13046"></a>

<a name="12309"></a>

Description

The offset (specified in pages) from the start of the disk space to this device.

Valid Values

An integer greater than or equal to 0. The default is 1000. If you use a file-based device, this is normally 0. The only time you can specify a value for this field is when you are creating this device.

This field is optional.

Configuring Devices (T_DEVICE Class)

<a name="T_DEVICE"></a>

<a name="C_DEVICE"></a>

Device attributes are listed in one tabbed folder labeled General Tab.

General Tab

The General tab contains the following fields:

•	Logical Machine Name, Backup (TA_LMID)

•	Object State (TA_STATE)

•	Full Path to Device (TA_CFGDEVICE)

•	Numeric Offset in Pages (TA_CFGOFFSET)

•	Device Name (Full Path) (TA_DEVICE)

•	Numeric Offset to Start of Disk Space (in Pages) (TA_DEVOFFSET)

•	Disk Area Size (in Pages) (TA_DEVSIZE)

Object State (TA_STATE)

<a name="12310"></a>

Description

This field displays the state of your routing table. A device has only one state: VALID.

Numeric Offset in Pages (TA_CFGOFFSET)

<a name="12307"></a>

Description

The offset at which space on this device begins for use within the Oracle Tuxedo VTOC specified in the Device Name (Full Path) (TA_DEVICE) on this tab.

Valid Values

An integer, representing blocks, in the range 0 to the page size of the disk. The default is 0.

We strongly recommend leaving this field set to 0.

Device Name (Full Path) (TA_DEVICE)

<a name="12312"></a>

Description

Absolute pathname of the device list entry.

Valid Values

A string of 2 to 64 characters. The default is the pathname entered in the Full Path to Device (TA_CFGDEVICE).

Configuring Clients (T_CLIENT Class)

<a name="T_CLIENT"></a>

<a name="C_CLIENT"></a>

Routing table attributes are listed in three tabbed folders:

•	General Tab

•	System Parameters Tab

•	Statistics Tab

General Tab

The General tab contains the following fields:

•	Client Name (TA_CLTNAME)

•	User Name (TA_USRNAME)

•	Client ID (TA_CLIENTID)

•	WorkStation Client (TA_WSC)

•	WorkStation Handler (TA_WSH)

•	WorkStation Client ID (TA_WSHCLIENTID)

•	WorkStation Client Address (TA_NADDR)

•	Object State (TA_STATE)

Client Name (TA_CLTNAME)

<a name="12172"></a>

Description

This field displays the client name associated with the client at tpinit(3) by the cltname element of the TPINIT structure.

User Name (TA_USRNAME)

<a name="12173"></a>

Description

This field displays the username associated with the client at tpinit(3) time by the usrname element of the TPINIT structure.

Client ID (TA_CLIENTID)

<a name="12174"></a>

Description

This field displays the client identifier. The data in this field should not be interpreted directly by the end user except for equality comparison.

WorkStation Client (TA_WSC)

<a name="12175"></a>

Description

This field displays the Workstation client. If this attribute is set to Yes, then the indicated client is logged in to the application from a remote workstation.

WorkStation Handler (TA_WSH)

<a name="12176"></a>

Description

This field displays the workstation handler. If this attribute is set to Yes, then the indicated client is a workstation handler process.

WorkStation Client ID (TA_WSHCLIENTID)

<a name="12177"></a>

Description

This field displays the client identifier for the associated workstation handler (WSH) if this client is a Workstation client; otherwise, this attribute will be returned as a zero-length string.

WorkStation Client Address (TA_NADDR)

<a name="12439"></a>

Description

This field displays the network address of a Workstation client. Network addresses with unprintable characters are converted to the Hexadecimal Addresses format. If the address is a TCP/IP address, then it is returned in the dotted decimal format with appended port number, as described under Network Address (TA_NADDR).

No value is displayed (that is, the field is blank) for a non-Workstation client.

Limitation

The ability of the system to provide this information is determined by the transport provider in use. In some cases, Workstation clients may not have addresses associated with them if the provider does not make this information available.

Object State (TA_STATE)

<a name="12178"></a>

Description

This field displays the state of your client. A client can take one of the following states:

•

ACTIVE

•

SUSPENDED

•

DEAD

System Parameters Tab

The System Parameters tab contains the following fields:

•	Logical Machine Name, Backup (TA_LMID)

•	Process ID (TA_PID)

•	Group Name (TA_SRVGRP)

•	Up Time (TA_TIMESTART)

•	Idle Time (TA_IDLETIME)

•	Current Time (TA_CURTIME)

•	Current Encryption Bits (TA_CURENCRYPTBITS)

•	Seconds Remaining Before Timeout (TA_TIMELEFT)

Logical Machine Name, Backup (TA_LMID)

<a name="12155"></a>

Description

This field displays the logical machine identifier for the machine on which the client is running (native clients) or to which the client is connected (Workstation clients).

Process ID (TA_PID)

<a name="12156"></a>

Description

This field displays the process identifier of the client. For Workstation clients, this identifier indicates the workstation handler through which the Workstation client is connected. A negative number can be specified on a GET operation for the purpose of retrieving client information for the calling process. If the calling process is not a client, then an error will be returned.

Group Name (TA_SRVGRP)

<a name="12157"></a>

Description

This field displays the server group with which the client is associated. This information is set by the grpname element of the TPINIT structure at tpinit(3) time.

Up Time (TA_TIMESTART)

<a name="12158"></a>

Description

This field displays the time (specified in seconds) since the client joined the application (as reported by the time(2) system call on the machine identified in the Logical Machine Name, Backup (TA_LMID).

Idle Time (TA_IDLETIME)

<a name="12397"></a>

Description

This field displays the approximate amount of time (in seconds) since this client last interacted with the system through an ATMI call. This value is accurate to within the value the scan units, as described in Basic Time Unit for Sanity Checks (TA_SCANUNIT).

When specified as a key field:

•	A positive value indicates that all clients with idle times of at least the indicated value match.

•	A negative value indicates that all clients with no more than the indicated value match.

•	A value of 0 indicates that all clients match.

Current Encryption Bits (TA_CURENCRYPTBITS)

<a name="12160"></a>

Description

This field displays the current encryption level for this client. The level is negotiated when the link is established.

Valid Values

Enter one of the following: 0, 40, or 128, representing bits.

Seconds Remaining Before Timeout (TA_TIMELEFT)

<a name="12161"></a>

Description

This field displays the time left (in seconds) for this client to receive the reply for which it is currently waiting before it will time out.

Valid Values

An integer greater than or equal to 0, representing the number of seconds. This timeout can be a transactional timeout or a blocking timeout.

Statistics Tab

The Statistics tab contains the following fields:

•	Number of Conversations (TA_NUMCONV)

•	Current Number of Conversations (TA_CURCONV)

•	Number of Dequeues (TA_NUMDEQUEUE)

•	Number of Enqueues (TA_NUMENQUEUE)

•	Number of Posts (TA_NUMPOST)

•	Number of Requests (TA_NUMREQ)

•	Number of Subscriptions (TA_NUMSUBSCRIBE)

•	Number of Transactions (TA_NUMTRAN)

•	Number of Transactions Aborted (TA_NUMTRANABT)

•	Number of Transactions Committed (TA_NUMTRANCMT)

Number of Conversations (TA_NUMCONV)

<a name="12162"></a>

Description

Number of tpconnect(3) conversations initiated by this client since Oracle Tuxedo was booted.

Valid Values

An integer greater than or equal to 0.

Example

0

Current Number of Conversations (TA_CURCONV)

<a name="12163"></a>

Description

Number of tpconnect(3) conversations initiated by this client that are still active.

Valid Values

An integer greater than or equal to 0.

Example

1500

Number of Dequeues (TA_NUMDEQUEUE)

<a name="12164"></a>

Description

Number of tpdequeue(3) operations initiated by this client since Oracle Tuxedo was booted.

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Enqueues (TA_NUMENQUEUE)

<a name="12165"></a>

Description

Number of tpenqueue(3) operations performed from this client since Oracle Tuxedo was booted (or since you reset the counter).

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Posts (TA_NUMPOST)

<a name="12166"></a>

Description

Number of tppost(3) operations performed from this client since Oracle Tuxedo was booted.

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Requests (TA_NUMREQ)

<a name="12167"></a>

Description

This field displays the number of tpacall(3) or tpcall(3) operations performed from this client since Oracle Tuxedo was booted.

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Subscriptions (TA_NUMSUBSCRIBE)

<a name="12168"></a>

Description

This field displays the number of subscriptions made by this client.

Valid Values

An integer greater than or equal to 0, the number of subscriptions made by this server with tpsubscribe(3) since Oracle Tuxedo was booted (or you reset the counter).

Example

0

Number of Transactions (TA_NUMTRAN)

<a name="12169"></a>

Description

This field displays the number of transactions begun by this client since its last start or restart.

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Transactions Aborted (TA_NUMTRANABT)

<a name="12170"></a>

Description

This field displays the number of transactions aborted by this client since its last start or restart.

Valid Values

An integer greater than or equal to 0.

Example

0

Number of Transactions Committed (TA_NUMTRANCMT)

<a name="12171"></a>

Description

This field displays the number of transactions committed by this client since its last start or restart.

Valid Values

An integer greater than or equal to 0.

Example

0

Configuring Bridges (T_BRIDGE Class)

<a name="T_BRIDGE"></a>

<a name="C_BRIDGE"></a>

Bridge attributes are listed in three tabbed folders:

•	General Tab

•	Timers Tab

•	Statistics Tab

General Tab

The General tab contains the following fields:

•	Logical Machine Name, Backup (TA_LMID)

•	Object State (TA_STATE)

•	Current Encryption Bits (TA_CURENCRYPTBITS)

Logical Machine Name, Backup (TA_LMID)

<a name="12291"></a>

Description

This field displays the source logical machine identifier (LMID1) and optionally, the destination logical machine identifier (LMID2) for network connection.

Valid Values

LMID1[,LMID2]

Object State (TA_STATE)

<a name="12292"></a>

Description

This field displays the state for your bridge. A bridge can take one of the following states:

•

ACTIVE

•

INACTIVE

•

SUSPENDED

Current Encryption Bits (TA_CURENCRYPTBITS)

<a name="12293"></a>

Description

This field displays the current encryption level for this link. The level is negotiated between machines when the link is established.

Valid Values

Enter one of the following: 0, 40, or 128, representing bits.

Timers Tab

The Timers tab contains the following fields:

•	Connection Time (TA_CONTIME)

•	Time Remaining in Suspension (TA_SUSPTIME)

Connection Time (TA_CONTIME)

<a name="12295"></a>

Description

This field displays the amount of time (in seconds) that has elapsed since the connection was established.

Time Remaining in Suspension (TA_SUSPTIME)

<a name="12296"></a>

Description

This field displays the time remaining in the suspension of this connection.

Valid Values

An integer greater than or equal to 0, representing seconds. The default is 300. After this amount of time, the state of the connection will automatically change to inactive and can be activated by normal application traffic.

Statistics Tab

The Statistics tab contains the following fields:

•	Bytes Sent (TA_SENTBYT)

•	Bytes Received (TA_RCVDBYT)

•	System Messages Sent (TA_SENTNUM)

•	System Messages Received (TA_RCVDNUM)

•	Flow Control Events (TA_FLOWCNT)

Bytes Sent (TA_SENTBYT)

<a name="12297"></a>

Description

Number of bytes sent from the source logical machine to the destination logical machine.

Valid Values

An integer greater than or equal to 0.

Example

0

Bytes Received (TA_RCVDBYT)

<a name="12298"></a>

Description

Number of bytes received by the source logical machine the destination logical machine.

Valid Values

An integer greater than or equal to 0.

Example

0

System Messages Sent (TA_SENTNUM)

<a name="12299"></a>

Description

Number of messages sent from the source logical machine to the destination logical machine.

Valid Values

An integer greater than or equal to 0.

Example

0

System Messages Received (TA_RCVDNUM)

<a name="12300"></a>

Description

Number of messages received by the source logical machine the destination logical machine.

Valid Values

An integer greater than or equal to 0.

Example

0

Flow Control Events (TA_FLOWCNT)

<a name="12301"></a>

Description

Number of times flow control has been encountered over this connection.

Valid Values

An integer greater than or equal to 0.

Example

0