Pathway/XM System Management Manual

Configuring the Pathway/XM Environment
Compaq NonStop™ Pathway/XM System Management Manual—426761-001
4-4
SERVER Objects
SERVER Objects
A SERVER object represents a server class, which is a set of duplicate copies of a single
server process. All server processes in a server class use the same object program. The
TYPE attribute of a server class determines whether it is managed as a distributed,
direct, or replicated server class. For distributed and replicated server classes, the
SERVER object can act as a template for the creation of multiple instances of the server
class under multiple PATHMON processes.
SERVICE Objects
A SERVICE object represents a pre-configured set of node-independent SERVER
objects that can be imported into your current Pathway/XM configuration to support
third-party applications. Each imported SERVER object configuration is linked to the
NODE object definition supplied by your SERVICE object. To facilitate easy
management of the imported servers, the SERVICE object name is automatically
assigned as a server group name for the imported server classes associated with the
SERVICE object.
Keeping Development and Production Separate
It is recommended that you do not mix your development and production environments.
Ideally, you should use NonStop™ TS/MP and Pathway/iTS (without Pathway/XM) for
development of requesters and servers and use a separate Pathway/XM environment for
your production system.
If you do not maintain separate environments, you might jeopardize the availability of
your production environment. For example, suppose there are problems with a
Guardian server that indicate the developer must use the Inspect product to debug the
server. During this time, the server is unavailable, and any processes attempting to
establish links to the server could encounter an unacceptable delay. Similarly, a TCP
that handles both production and development SCREEN COBOL requesters might not
be able to respond to a user if a developer is making changes based on development
requirements.
If you cannot maintain totally separate development and production environments, try to
keep as much of your production environment separate as you can. It is highly
recommended that you maintain separate sets of development and production server
classes. It is also desirable to define separate TCP templates for development and
production, so that Pathway/XM creates separate sets of TCPs.
You can also use the version control capabilities of the Pathway/XM Analyst tool to
maintain different configuration versions.
Using the PXMCFG Utility
PXMCFG is a batch-type utility program that configures your Pathway/XM
environment. To use PXMCFG, you first write a sequence of PXMCFG statements that
define the objects in your Pathway/XM configuration. You prepare this sequence of
statements in an EDIT file, called a configuration source file.