Filter
Top Products
CREATE FACILITY
Qualifiers
/ALL_ROLES=node-list
/NOALL_ROLES (D)
Specifies the names of the nodes that are to act as frontend, router
and
backend
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
anode, bnode, mynode
for all frontends
except
mynode
. (Any node that has both frontend and router roles selects its own
router first.)
/BACKEND=backend-list
/NOBACKEND (D)
Specifies the names of the nodes that are to act as backends for this facility.
Backend-list
is a list of
backend-nodes
separated by commas. If there is more
than one
backend-node
, then
backend-list
must be enclosed in parentheses.
Backend-node
is either the name of a node or
@file-spec
, where
file-spec
specifies a text file containing a
backend-list
on each line.
/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
. Preferred routers are defined by the order specified in
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
call-out
servers running on them.
Role-list
is a list of
roles
separated by commas. If
role-list
contains more
than one
role
then it must be enclosed in parentheses.
role
is one of the keywords
ROUTER
or
BACKEND
.
The default for
role-list
is
(ROUTER,BACKEND)
.
/CLUSTER
/NOCLUSTER (D)
Specifies that the command is executed on all the nodes in the cluster.
If neither
/NODE
nor
/CLUSTER
is specified then the command is executed on the
nodes specified by the latest
SET ENVIRONMENT
command. If no
SET ENVIRONMENT
command has been entered then the command is executed only on the node where
the command was issued.
6–48 RTR Command Line Interface