HP-UX SNAplus2 R7 APPC Application Suite User's Guide

APPC Application Suite for HP-UX Programs
Configuring Your System for APPC Application Suite
When specifying a target LU, the destination name can either be a fully qualified LU name,aCPI-C (Common
Programming Interface for Communications) symbolic destination name,oran
ANAME
alias.Ifan
ANAME
alias
conflicts with a CPI-C symbolic destination name, the application uses the CPI-C symbolic destination name.(For
more information, see Section 1.2.2, Configuring Your System.)
1.2.2 Configuring Your System
You must configure the local SNA node and its clients (if any) to support APPC Application Suite programs.
Security and session configuration is optional depending on your needs. This section describes how to configure
each of the following elements:
• Node
• Link
• Local LU
• Security
• Requester programs
• Provider programs
Configuring the Node
Configure the local node by providing a control point name for the node and the name of the local network to
which the node belongs.
Configuring the Link
If the local node is:
• A low-entry networking (LEN) node, configure links to any other nodes that are required. You must also
configure the partner LUs explicitly.
• An APPN end node (EN), configure a link to an APPN network node that acts as a network node server for the
local node.
• An APPN network node (NN), configure links to other network nodes and any attached client end nodes.
Configuring the Local LU
Normally, APPC Application Suite applications can use the default LU associated with the local node (the control
point LU), so you do not need to define any local LUs.
If you need to use different LUs, you should define each local LU that will be used for these applications (refer to
the HP-UX SNAplus2 Administration Guide for more information). The application user can then use the
APPCLLU
environment variable to specify which local LU to use. For more information on APPCLLU, refer to the HP-UX
SNAplus2 Administration Command Reference or the HP-UX SNAplus2 CPI-C Programmer’s Guide.
Configuring Security
As delivered with SNAplus2, the APPC Application Suite provider programs do not require conversation security,
so the user of a requester program does not need to specify a user ID and password. If you want to set up the
provider programs to require conversation security, you will need to do the following:
• Define conversation security user IDs and passwords for the users who are permitted to access the provider
programs. For the
AFTP provider program running on the local node or on a HP-UX client, the conversation
security user IDs should match HP-UX login IDs on the local system. This ensures that the remote user, logging
in to the
AFTP provider with a specific user ID, can access only the files and directories that are available to the
corresponding HP-UX login ID. On Windows clients, file access using
AFTP is controlled by the aftp.ini
file; see Section 2.1, AFTP Configuration for more information.
• Optionally, define a security access list to restrict the use of each provider program to a specific set of users.
11