Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • Tuxedo

    Uploaded by

    Predrag Terzic
    187 views2 pages
    To summarize the Tuxedo configuration file: 1. The configuration file contains 9 sections that define system parameters, machines, groups, servers, services, resources, interfaces, networks, and routing. 2. The configuration file exists in both a text format (UBBCONFIG) and binary format (TUXCONFIG). The tmloadcf command is used to convert between the two formats. 3. The TUXCONFIG file location and environment variables must match settings in the configuration file for tmloadcf to successfully compile the binary configuration file.

    Original Description:

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    To summarize the Tuxedo configuration file: 1. The configuration file contains 9 sections that define system parameters, machines, groups, servers, services, resources, interfaces, networks, and routing. 2. The configuration file exists in both a text format (UBBCONFIG) and binary format (TUXCONFIG). The tmloadcf command is used to convert between the two formats. 3. The TUXCONFIG file location and environment variables must match settings in the configuration file for tmloadcf to successfully compile the binary configuration file.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    187 views2 pages

    Tuxedo

    Uploaded by

    Predrag Terzic
    To summarize the Tuxedo configuration file: 1. The configuration file contains 9 sections that define system parameters, machines, groups, servers, services, resources, interfaces, networks, and routing. 2. The configuration file exists in both a text format (UBBCONFIG) and binary format (TUXCONFIG). The tmloadcf command is used to convert between the two formats. 3. The TUXCONFIG file location and environment variables must match settings in the configuration file for tmloadcf to successfully compile the binary configuration file.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 2

    TUXEDO

    http://download.oracle.com/docs/cd/E13203_01/tuxedo/tux80/interm/admin.htm
    1. Create and edit the UBBCONFIG file (a text version of TUXCONFIG) with a text editor. 2. Run tmloadcf to convert the UBBCONFIG file into a TUXCONFIG (binary) file. Before tmloadcf is executed, the environment variable TUXCONFIG must be set to the full pathname of the device or system file where TUXCONFIG is to be loaded.

    Contents of the Configuration File


    The following table lists the nine sections of the configuration file and describes the purpose of each section. Required or Optional Required Required Optional Optional Purpose Defines all system parameters. Specifies all the machines in your application. Defines all groups, group names, and group IDs for your application. Specifies the initial conditions for servers started in the system. Provides information on services used by the application. For CORBA environments, provides information on application-wide, default parameters for interfaces used by the application. Describes the network configuration for a LAN environment. Describes the network groups available to the application in the LAN environment. Provides information for data-dependent routing of service requests using FML buffers and views.

    Section MACHINES GROUPS SERVERS SERVICES

    RESOURCES Required

    INTERFACES Optional

    NETWORK

    Optional

    NETGROUPS Optional ROUTING Optional

    How to find out the total number of users connected


    If you use TUXEDO's tmadmin command and then use 'printclient' from the prompt, you'll be able to see the number of TUXEDO connections for both types of clients.

    What Is the Workstation Component?


    The Workstation component of the BEA Tuxedo system allows application clients to reside on a machine that does not have a full server-side installation, that is, a machine that does not support any administration or application servers. All communication between the client and the application servers takes place over the network.

    A Workstation client process can run on a Windows 98, Windows 2000, or UNIX platform. The client has access to the ATMI. The networking behind requests is transparent to the user. The Workstation client registers with the system through a Workstation handler (WSH) and has access to the same capabilities as a native client. All communication between a Workstation client and application server is done through a Workstation handler (WSH) process. Workstation clients can perform almost all the same functions that can be performed by network clients. They can, for example: Send and receive messages Begin, end, or commit transactions Send and receive unsolicited messages Take full advantage of any security mechanism offered to BEA Tuxedo clients

    How to Compile a Configuration File


    Compiling a configuration file means generating a binary version of the file (TUXCONFIG) from the text version (UBBCONFIG). To compile a configuration file, run the tmloadcf command. tmloadcf parses a UBBCONFIG file and loads the binary file. tmloadcf reads a file (or standard input written in UBBCONFIG syntax), checks the syntax, and optionally loads a binary configuration file called TUXCONFIG. The TUXCONFIG and (optionally) TUXOFFSET environment variables point to the TUXCONFIG file and (optional) offset where the information should be stored. You can run tmloadcf only on the machine designated as MASTER in the RESOURCES section of the UBBCONFIG file, unless the -c or -n option is specified. Notes: The user identifier (UID) of the person running tmloadcf must match the UID, if specified, in the RESOURCES section of the UBBCONFIG file. The pathname specified for the TUXCONFIG environment variable must match exactly (including case) the pathname specified for TUXCONFIG parameter within the MACHINES section of the UBBCONFIG file. Otherwise, tmloadcf(1) cannot be run successfully.

    Using Log Files to Monitor Activity


    To help you identify error conditions quickly and accurately, the BEA Tuxedo system provides the following log files: Transaction log (TLOG)a binary file that is not normally read by you (the administrator), but that is used by the Transaction Manager Server (TMS). A TLOG is created only on machines involved in BEA Tuxedo global transactions. User log (ULOG)a log of messages generated by the BEA Tuxedo system while your application is running.

    These logs are maintained and updated constantly while your application is running.

    You might also like