ASAP 1.1 Hybrid Manual

HP NonStop ASAP Hybrid Manual – 529729-004
Page 2-6
CPU <cpu> defines the CPU in which the Gateway runs. This value must be
a valid CPU number from 0 through 15. Hybrid Gateways should be spread
across processors to take advantage of the parallelism inherent on the
NonStop platform. The default is CPU 0.
OBJECT <object-filename> is the object filename for the Hybrid Gateway.
The default is $SYSTEM.SYSTEM.ASAPGATE.
PRI <priority> is the execution priority for the Hybrid Gateway. The default
is 150.
TERM <term> is the home terminal for the Gateway process.
Considerations
The number of Hybrid Gateway processes that need to be started depends
on several factors: the number of external systems and domains that need
to be processed; the number of ASAPX domains that are available in a
processor; the amount of processor time a Gateway can obtain to process
data; and problems in the network that place upper limits on the amount of
data that can flow to a single IP address or port.
When a Hybrid Gateway reaches a limit or begins to show that all domains
are not being updated, you should consider starting another Gateway
process and repartitioning the domain load. Each Hybrid Gateway should
execute in a separate processor, if possible, and should use a separate
TCPIP process name, IP address, and port to achieve maximum parallelism.
Example
This example shows the contents of a Proxy SGP configuration file that
starts three Hybrid Gateway processes:
GATEWAY CONFIG $SYSTEM.ASAP.GATEWAY1 NAME $GATE1
GATEWAY CONFIG = $SYSTEM.ASAP.GATEWAY2 CPU = 1 NAME
$GATE2
GATEWAY CONFIG $SYSTEM.ASAP.GATEWAY3 CPU 2 PRI 185
NAME = $GATE3
GATEWAY NAME $GATE4 CONFIG $SYSTEM.ASAP.GATEWAY4 TERM
$ZHOME