www.it-ebooks.info
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Configuration and Administration of Tuxedo<br />
The ROUTING section<br />
The ROUTING section provides <strong>info</strong>rmation for data-dependent routing of service<br />
requests using Tuxedo buffer types such as the FML, VIEW, and XML buffers.<br />
Parameter name and values<br />
ROUTING_CRITERIA_NAME =<br />
string_value<br />
Required/<br />
optional<br />
Required<br />
Comments/values -- what <strong>it</strong> means<br />
This is a name assigned to a routing<br />
parameter for a service defined in the<br />
SERVICE section.<br />
FIELD = string_value Required This is the actual routing based on the values<br />
of the field from the FML or FML32 buffer,<br />
XML element or the element attribute, or<br />
the VIEW or VIEW32 field name.<br />
FIELDTYPE = string_value Required The type of routing field specified in the<br />
FIELD parameter, which can be one of CHAR,<br />
SHORT, LONG, FLOAT, DOUBLE, or STRING.<br />
RANGES = string_value Required A range is e<strong>it</strong>her a single value or a range of<br />
the lower-upper form.<br />
BUFTYPE = string_value Optional This can be one of FML, FML32, XML, VIEW,<br />
VIEW32, X_C_TYPE, or X_COMMON. No<br />
subtype can be specified for types FML,<br />
FML32, or XML.<br />
The NETGROUPS section<br />
The NETGROUPS section describes the network groups available to the application in<br />
a LAN environment. There are only three parameters in this group: NETGROUP is the<br />
name of the network group, while NETGRPNO and NETPRIO w<strong>it</strong>h numeric values are<br />
used to specify the prior<strong>it</strong>y of this network group.<br />
Parameter name and values<br />
Required/<br />
optional<br />
Comments/values -- what <strong>it</strong> means<br />
NADDR = String Required This specifies the network address (as <strong>it</strong>s<br />
listening address) for the BRIDGE process<br />
under LMID, so that other BRIDGE processes<br />
are contacted through this address w<strong>it</strong>hin<br />
the same application. For example,<br />
//host.name:port_number.<br />
[ 34 ]<br />
<strong>www</strong>.<strong>it</strong>-<strong>ebooks</strong>.<strong>info</strong>