Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference

Table 1 BEA Tuxedo File Formats, Data Descriptions, MIBs, and System Processes  

Name	Description
Introduction to Tables and Files	Overview of this document
ACL_MIB(5)	Management Information Base for ACLs
APPQ_MIB(5)	Management Information Base for /Q
AUTHSVR(5)	Server providing per-user authentication
compilation(5)	Instructions for compilation of BEA Tuxedo system application components
DMADM(5)	Domains administrative server
DMCONFIG(5)	Text version of a Domains configuration file
DMCONFIG for GWTOPEND(5)	Text version of a Domains configuration file for a TOP END Domain Gateway
DM_MIB(5)	Management Information Base for Domains
EVENTS(5)	List of system-generated events
EVENT_MIB(5)	Management Information Base for EventBroker
factory_finder.ini(5)	FactoryFinder Domains configuration file
Ferror, Ferror32(5)	FML error codes
field_tables(5)	FML mapping files for field names
GWADM(5)	Domains gateway administrative server
GWTDOMAIN(5)	TDomain gateway process
GWTOPEND(5)	TOP END Domain Gateway process
GWTUX2TE, GWTE2TUX(5)	BEA Tuxedo / BEA TOP END gateway servers
ISL(5)	Enables access to BEA Tuxedo objects by remote BEA Tuxedo clients using IIOP.
langinfo(5)	Language information constants
LAUTHSVR	WebLogic Server embedded LDAP-based authentication server
MIB(5)	Management Information Base
nl_types(5)	Native language data types
servopts(5)	Run-time options for server processes
TM_MIB(5)	Management Information Base for core BEA Tuxedo system
TMFFNAME(5)	Server that runs the FactoryFinder and NameManager services
TMIFRSVR(5)	The Interface Repository server
TMQFORWARD(5)	Message Forwarding Server
TMQUEUE(5)	Message Queue Manager
TMSYSEVT(5)	System event reporting process
tmtrace(5)	Run-time tracing facility
TMUSREVT(5)	User event reporting process
tperrno(5)	BEA Tuxedo system error codes
tpurcode(5)	BEA Tuxedo system global variable for an application-specified return code
tuxenv(5)	List of environment variables in the BEA Tuxedo system
tuxtypes(5)	Buffer type switch; descriptions of buffer types provided by the BEA Tuxedo system
typesw(5)	Buffer type switch structure; parameters and routines needed for each buffer type
UBBCONFIG(5)	Text version of a BEA Tuxedo configuration file
viewfile(5)	Source file for view descriptions
WS_MIB(5)	Management Information Base for Workstation
WSL(5)	Workstation Listener server

 

 

---

Introduction to Tables and Files

Description

This section describes the format of miscellaneous tables and files.

The page named compilation(5) summarizes information about header files, libraries, and environment variables needed when compiling application source code.

The section includes descriptions of BEA Tuxedo system-supplied servers. Applications wishing to use the BEA Tuxedo system-supplied servers should specify them in the configuration file for the application.

The servopts page describes options that can be specified in the configuration file as the CLOPT parameter of application servers.

The BEA Tuxedo Management Information Base is documented in the MIB(5) reference page and in the following component MIB pages:

• ACL_MIB(5)

• APPQ_MIB(5)

• DM_MIB(5)

• EVENT_MIB(5)

• TM_MIB(5)

• WS_MIB(5)

 

---

ACL_MIB(5)

Name

ACL_MIB—Management Information Base for ACLs

Synopsis

#include <fml32.h>
#include <tpadm.h>

Description

The BEA Tuxedo MIB defines the set of classes through which access control lists (ACLs) may be managed. A BEA Tuxedo configuration with SECURITY set to USER_AUTH, ACL, or MANDATORY_ACL must be created before accessing or updating these classes. ACL_MIB(5) should be used in combination with the generic MIB reference page MIB(5) to format administrative requests and interpret administrative replies. Requests formatted as described in MIB(5) using classes and attributes described in this reference page may be used to request an administrative service using any one of a number of existing ATMI interfaces in an active application. For additional information pertaining to all ACL_MIB(5) class definitions, see ACL_MIB(5) Additional Information.

ACL_MIB(5) consists of the following classes.

Table 2 ACL_MIB Classes

Class Name	Attribute
T_ACLGROUP	ACL group
T_ACLPERM	ACL permissions
T_ACLPRINCIPAL	ACL principal (users or domains)

 

Each class description section has four subsections:

Overview

High level description of the attributes associated with the class.

Attribute Table

A table that lists the name, type, permissions, values and default for each attribute in the class. The format of the attribute table is described below.

Attribute Semantics

Tells how each attribute should be interpreted.

Limitations

Limitations in the access to and interpretation of this class.

Attribute Table Format

As described above, each class that is a part of this MIB is defined below in four parts. One of these parts is the attribute table. The attribute table is a reference guide to the attributes within a class and how they may used by administrators, operators and general users to interface with an application. There are five components to each attribute description in the attribute tables: name, type, permissions, values and default. Each of these components is discussed in MIB(5).

TA_FLAGS Values

MIB(5) defines the generic TA_FLAGS attribute which is a long containing both generic and component MIB specific flag values. At this time, there are no ACL_MIB(5) specific flag values defined.

FML32 Field Tables

The field tables for the attributes described in this reference page are found in the file udataobj/tpadm relative to the root directory of the BEA Tuxedo system software installed on the system. The directory ${TUXDIR}/udataobj should be included by the application in the colon-separated list specified by the FLDTBLDIR environment variable and the field table name tpadm() should be included in the comma-separated list specified by the FIELDTBLS environment variable.

Limitations

Access to the header files and field tables for this MIB is provided only at sites running BEA Tuxedo release 6.0 and later, both native and Workstation.