SeeView Server Gateway (SSG) Manual

SSG Component Configuration
HP NonStop SeeView Server Gateway (SSG) Manual—526356-004
3-2
SSG Object Files
The SET SECURE commands in this example set the default rules for all CI access
using the SSG. The SET SSGCONFSEARCH ON command causes SSGCOM to load
the user's custom SSGCONF file after loading the file on $SYSTEM.SYSTEM. The
SET AUTOSTART ON command allows SSGCOM to automatically start an SSG
process if needed when a request is received from a client application.
SSG Object Files
After performing the SSG setup and confirming the settings in the SSG configuration
file, you can run SSG on your system. When the SSG setup is complete, the
SSGCOM, SSGHELP, SSGSHELL, and SEEVIEW files should be located in the
$SYSTEM.SYSTEM subvolume and secured for network access.
SSGCOM
The object file SSGCOM is the SSG command interpreter. It starts and manages the
Gateway processes and also displays SSG status information. The SSGCOM program
also provides the host support for the transport services built into workstation Client
Server Gateways (CSGs).
The SSG command interpreter provides command and control of the SSG environment
and enables interactive reporting of statistics. STATUS, STARTUP, and SHUTDOWN
commands control SSG Gateway processes. SSG command syntax and semantics
are described in detail in Section 4, SSG Commands.
SSGHELP
The Edit file SSGHELP is the SSGCOM interactive text help file. It contains all
interactive help text used by the SSGCOM command interpreter.
SSGSHELL
The SeeView Server Gateway Shell (SSGSHELL) is a SeeView server mode script
that provides the command interpreter gateway functionality. When the SSG gateway
is started, this file is the input file to the SeeView interpreter. The SSGSHELL
implements context-retaining and context-free stream protocols that provide a host-
based command interpreter gateway.
1 > COMMENT Check/edit the SSG configuration file
2 > EDIT $SYSTEM.SYSTEM.SSGCONF; LA
CURRENT FILE IS $SYSTEM.SYSTEM.SSGCONF
1. SET SECURE TACL NONE ! Users can't access TACL via SSG
2. SET SECURE FUP USER ! Access to FUP only for user that started SSG
3. SET SECURE ASAP ANY ! Any user can access ASAP via SSG
4. SET SSGCONFSEARCH ON ! Load user's SSGCONF file
5. SET AUTOSTART ON ! Start SSG servers on demand