Compaq AA-Q88CE-TE System Manager's Manual page 124

Rtr
Table of Contents

Advertisement

CREATE FACILITY
Qualifiers
/ALL_ROLES=node-list
/NOALL_ROLES (D)
Specifies the names of the nodes that are to act as frontend, router
in this facility.
Note that the definition order of nodes may be significant. This applies to the
order of router node definitions when frontend load balancing is not enabled.
Nodes defined with the /ROUTER qualifier have the higher priority and are
followed by nodes defined by the /ALL_ROLES qualifier. For example, in this
definition:
$ RTR CREATE FACILITY /ALL_ROLES=mynode /ROUTER=(anode,bnode)
The router nodes are in definition order
except
mynode
router first.)
/BACKEND=backend-list
/NOBACKEND (D)
Specifies the names of the nodes that are to act as backends for this facility.
Backend-list
than one
Backend-node
specifies a text file containing a
/BALANCE
/NOBALANCE (D)
Specifies that load balancing is enabled for the frontend of the transaction router
listed with /ROUTER. See Section 2.6, Router Load Balancing, for details on load
balancing.
It has no significance on a backend node, and will be ignored if specified.
The default behavior (/NOBALANCE) is for a frontend to connect to the
preferred router
the /ROUTER qualifier of the CREATE FACILITY command. Note that this
preference is subject to the router being available and quorate.
/CALL_OUT[=role-list]
/NOCALL_OUT (D)
Specifies which node types are to have
Role-list
than one
is one of the keywords
role
The default for
/CLUSTER
/NOCLUSTER (D)
Specifies that the command is executed on all the nodes in the cluster.
If neither
nodes specified by the latest
command has been entered then the command is executed only on the node where
the command was issued.
6–48 RTR Command Line Interface
. (Any node that has both frontend and router roles selects its own
is a list of
backend-nodes
, then
backend-node
backend-list
is either the name of a node or
backend-list
. Preferred routers are defined by the order specified in
is a list of
separated by commas. If
roles
then it must be enclosed in parentheses.
role
ROUTER
is
role-list
(ROUTER,BACKEND)
nor
is specified then the command is executed on the
/NODE
/CLUSTER
SET ENVIRONMENT
anode, bnode, mynode
separated by commas. If there is more
must be enclosed in parentheses.
, where
@file-spec
on each line.
servers running on them.
call-out
role-list
or
.
BACKEND
.
command. If no
and
backend
for all frontends
file-spec
contains more
SET ENVIRONMENT

Advertisement

Table of Contents
loading

This manual is also suitable for:

Reliable transaction router, version 3.2

Table of Contents

Save PDF