RSC/MP Installation and Configuration Guide

Best Practices Guide Scenario 2
Possible improvements to this configuration
To alleviate the heavy loading on the PIPEMAN process, consider running
additional instances of PIPEMAN, each with its own set of TDPs and NIFs (see
Figure E-6). Use PARAM PIPEINI to direct each TDP to its intended instance of
PIPEMAN. Give each PIPEMAN instance its own SystemName setting, and
configure each workstation to use one of those names. Configure DNS to resolve
each host name appropriately (in the example shown in the diagram, DNS resolves
each of two host names to two different IP addresses using the round-robin
method).
Figure E-6. Scenario 2 improved with multiple PIPEMAN instances
workstation
(group “B”)
workstation
(group “A”)
NonStop host
HOST1
Application Application
S er v er s
Servers
S er v er s
RSCPIPE
PIPEMAN
RSCPIPE
PIPEMAN
TDP
Sys temName
HOST1A
TDP
PIPEMAN
TDP
PIPEMAN
TDP
SystemName
HOST1B
NIF NIF NIF NIF NIF NIF
TCP/IP TCP/IP $ZTC0 $ZTC1 $ZTC2 $ZTC3
10.1.90.20 10.1.90.21 10.1.90.22
10.1.90.23
Network
Group A workstations use HOST1A
Group B workstations use HOST1B
DNS serves addresses round-robin:
Wor kstations calling HOST1A get
10.1.90.20 or 10. 1.90.21
Wor kstations calling HOST1B get
10.1.90.22 or 10. 1.90.23
CDT017
HP NonStop Remote Server Call (RSC/MP) Installation and Configuration G uide — 52235 8- 013
E -9