Setting the Order in Which Servers Are Booted

To specify the sequence of servers to be booted, set the SEQUENCE parameter for each server. The value of SEQUENCE can be any number between 1 and 10,000. A server with a smaller SEQUENCE value is booted before a server with a larger value. If the SEQUENCE parameter is not set for any servers, the servers are booted in the order in which they are listed in the SERVERS section. If some, but not all servers are sequenced, the sequenced servers are booted first. The order in which servers are shut down is the reverse of the order in which they were booted.

The SEQUENCE parameter is optional. It may be helpful in a large application in which control over boot order is important.

To boot multiple servers, set the MIN parameter, which provides a shortcut to booting. All servers share the same options. If you specify RQADDR, the servers form an MSSQ set. The default for MIN is 1.

To specify the maximum number of servers that can be booted, set the MAX parameter. The tmboot(1) command boots MIN servers at run time. Additional servers can be booted up to MAX. The default is MIN.

The MIN and MAX parameters are helpful in keeping the size of the configuration files for large applications manageable. Allowances for MAX values must be made in the IPC resources. The MIN and MAX parameters are also used for conversational services and automatic server spawning.

Required Order in Which to Boot CORBA C++ Servers

The following is the correct order in which to boot the servers In a BEA Tuxedo CORBA environment. A CORBA application program will not boot if the order is changed.

Edited SERVERS Section from a University Sample UBBCONFIG

*SERVERS
    # By default, restart a server if it crashes, up to 5 times 
    # in 24 hours.
    #
    DEFAULT:
        RESTART = Y
        MAXGEN  = 5

    # Start the BEA Tuxedo System EventBroker. This event broker 
    # must be started before any servers providing the 
    # NameManager Service
    #
    TMSYSEVT
        SRVGRP  = SYS_GRP
        SRVID   = 1

    # TMFFNAME is a BEA Tuxedo CORBA provided server that 
    # runs the NameManager and FactoryFinder services.

    # The NameManager service is a BEA Tuxedo CORBA-specific
     # service that maintains a mapping of application-supplied names
    # to object references.

    # Start the NameManager Service (-N option). This name 
    # manager is being started as a Master (-M option).
    #
    TMFFNAME
        SRVGRP  = SYS_GRP
        SRVID   = 2
        CLOPT   = "-A -- -N -M"

    # Start a slave NameManager Service
    #
    TMFFNAME
        SRVGRP  = SYS_GRP
        SRVID   = 3
        CLOPT   = "-A -- -N"

    # Start the FactoryFinder (-F) service
    #
    TMFFNAME
        SRVGRP  = SYS_GRP
        SRVID   = 4
        CLOPT   = "-A -- -F"

    # Start the interface repository server
    #
    TMIFRSVR
        SRVGRP  = SYS_GRP
        SRVID   = 5

    # Start the university server
    #
    univb_server
        SRVGRP  = ORA_GRP
        SRVID   = 6
        RESTART = N

    # Start the listener for IIOP clients
    #
    # Specify the host name of your server machine as
    # well as the port. A typical port number is 2500
    #
    ISL
        SRVGRP  = SYS_GRP
        SRVID   = 7
        CLOPT   = "-A -- -n //TRIXIE:2500"

In the example, after the TMSYSEVT and TMFFNAME servers are started, servers are started for:

Note: When migrating or shutting down and restarting groups or machines for any reason, if there are active slave NameManagers in other groups, be sure to organize your UBBCONFIG file so that a FactoryFinder or a slave NameManager is never restarted before the master NameManager is active. For example, if you have a FactoryFinder in the same group as the master NameManager, arrange the order of these servers in the UBBCONFIG file so the master NameManager is started first.