|
|
|
|
You must establish links with any remote systems before running APPC Application Suite programs that communicate with those systems.
APPC Application Suite includes both source programs and target programs. A source program resides on a local node and requests services from a target program residing on a partner node. Source and target programs are paired; the source program requests services, and the target program performs the services.
For example, AFTP is a source program that enables you to send and receive files between two computers; its target program is AFTPD. Assume that AFTP resides on local node A and AFTPD resides on remote node B. To send a file named ABC from node A to node B, you invoke AFTP, which then communicates with the target program AFTPD at node B, requesting that it execute the required task.
APPC Application Suite includes both the source and target programs (AFTP and AFTPD, respectively). This allows it to be used both to access remote AFTPD services and to service remote versions of AFTP. The same is true of all the applications provided by APPC Application Suite.
In order for a source program to communicate with its target program, you must identify the target LU and specify an SNA mode. You can supply this information on the command line or include it in a configuration file.
When specifying a target LU, the destination name can either be a fully qualified LU name, a CPI-C (Common Programming Interface for Communications) symbolic destination name, or an ANAME alias. If an ANAME alias conflicts with a CPI-C symbolic destination name , the application uses the CPI-C symbolic destination name. (For more information, see Destination Names.)
You must configure the local SNA node 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
Source programs
Target programs
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.
A low-entry networking (LEN) node, configure links to any other nodes that are required. You must also configure the partner LUs explicitly.
An APPNend 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.
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 SNAP-IX Administration Guide for
more information). The application user can then use the
As delivered with SNAP-IX, the APPC Application Suite target programs do not require conversation security, so the user of a source program does not need to specify a user ID and password. If you want to set up the target 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 target programs. For the AFTP and ACOPY applications, the conversation security user IDs should match Solaris login IDs on the local system. This ensures that the remote user, logging in to AFTP or ACOPY with a specific user ID, can access only the files and directories that are available to the corresponding Solaris login ID.
Optionally, define a security access list to restrict the use of each program to a specific set of users.
Define each target TP to require conversation security (and optionally specify the security access list).
For more information, refer to the SNAP-IX Administration Guide.
If the target programs on the remote system are set up to require conversation security, the user of a source program on the local system must specify a user ID and password. For the AFTP application, these parameters are specified while using AFTP to log in to the remote system; for all other APPC Application Suite applications, these parameters are specified using command-line options. See the description of each individual application for more information.
All of the APPC Application Suite applications use LU 6.2 sessions to communicate with their partner applications on the destination nodes. To establish an LU 6.2 session with the partner application, you must supply the following parameters:
The RTPN enables the local application to identify the remote application. By default, each application uses the standard RTPN for its partner application, but you can override this value by using the application's command line options.
The local application must provide an SNA mode name for use by the session. The same mode name must be defined on the remote system. By default, each application provides a mode name, but you can override this value by using the application's command line options.
The local application must specify the LU on the remote system that handles requests for the remote TP. Specify the partner LU name (which is called the RemoteSystemID in the syntax statements) by specifying one of the following destination names on the command line:
Fully qualified partner LU name ( FQPLU)
CPI-C symbolic destination name
ANAME alias
(For more information, see Destination Names.)
Enter one of the following destination names on the command line to specify the partner LU name (which is called the RemoteSystemID in the syntax statements):
You can explicitly specify the partner LU name as the FQPLU in the form NetworkName.LUName . In this case, the application either uses the default mode name and RTPN values or the values you specify by using the application's command line options.
For example, to establish an APING session with the LU called LUNAME7 on the SNA network NETID, enter the following on the command line:
aping NETID.LUNAME7
You can supply the partner LU name by specifying a CPI-C symbolic destination name. The CPI-C symbolic destination name is the name of a CPI-C side information record; see SNAP-IX Administration Guide for details of how to configure this.
By using the CPI-C symbolic destination name, the application locates the appropriate side information record and uses the information contained in it to determine the partner LU address.
To establish an APING session with the partner LU specified in the side information record that has the symbolic destination name FRED, enter the following command:
aping FRED
You can supply the partner LU name by specifying an ANAME alias as a destination name. This alias refers to a specific LU within the SNA network.
For example, enter the following command to associate the ANAME alias called max with the local control point LU:
aname reg -u max
Enter the following command to establish an APING session with the LU associated with the user called max:
aping max
For more information about ANAME, see Using ANAME.
The application searches for destination names in the following sequence:
Fully qualified partner LU name (FQPLU)
If the destination name contains a period (.), the application interprets it as an FQPLU . If the application cannot locate the FQPLU, it does not continue to try to connect to any other LUs.
CPI-C symbolic destination name
If the destination name does not contain a period (.), the application tries to locate a CPI-C symbolic destination name with that name.
ANAME alias
If the application cannot locate a CPI-C symbolic destination name that matches the destination name you entered on the command line, it tries to obtain the ANAME alias from the ANAME target program (ANAMED).
For more information about how the application obtains the alias from the ANAME record, see Locating an ANAME Alias Using the ANAMED Target Program.
If these three methods fail, the application returns an error.
For a source program to communicate with a target program, SNAP-IX must automatically start the target program when required. SNAP-IX uses the invokable-TP file fragment called asuite.tps (stored in the /etc/opt/sna subdirectory) to select the correct target program and execute it.
The asuite.tps file fragment, which is included with the APPC Application Suite, provides the standard configuration for the target TPs (AFTPD, ATELLD, AREXECD, and ANAMED).
By default, the target programs run with the user ID nobody. If you need
to run the target programs with user ID root, in order
to use features that are available only to a System Administrator, the permissions
of the target programs must be changed to add the set-group-ID bit. For example
to run AREXECD with root privilege, change the
chmod +s /opt/sna/bin/arexecd
The ACOPY program does not have its own target program. Instead, it uses the AFTPD target program.
The APING program uses a target program that is configured automatically as part of SNAP-IX.
Enter the following command to install asuite.tps:
snatpinstall -a asuite.tps
Following is the standard asuite.tps file fragment that is provided with APPC Application Suite:
[AFTPD] PATH=/opt/sna/bin/aftpd ENV=APPCTPN=AFTPD USERID=nobody GROUP=other TYPE=NON-QUEUED [ATELLD] PATH=/opt/sna/bin/atelld ENV=APPCTPN=ATELLD USERID=nobody GROUP=other TYPE=NON-QUEUED [AREXECD] PATH=/opt/sna/bin/arexecd ENV=APPCTPN=AREXECD USERID=nobody GROUP=other TYPE=NON-QUEUED [ANAMED] PATH=/opt/sna/bin/anamed ENV=APPCTPN=ANAMED USERID=nobody GROUP=other TYPE=NON-QUEUED
|
|
|
 |
|