The IBM® Configuration Assistant for z/OS® Communications Server can request that existing policy configuration files or TCP/IP profile information be imported for further changes and additions. When the Policy Agent provides this configuration file import service, the IBM Configuration Assistant is acting as an import requester. These policy files are import configuration files and the resulting policies are import policies. When the IBM Configuration Assistant is acting as an import requester, the required input values are configured on its Import Policy Data panel or on request panels for discovery import (for example, the Discover Stack Local Addresses panel):
- Host connection IP address and port for the Policy Agent
- Host connection user name and password to identify resources that this user can access
Indication of whether a secure connection (SSL) should
be used, by configuring your own AT-TLS policies or by having the
Policy Agent install generated AT-TLS policies.You configure
the type of security for a connection (basic or secure) on the ServicesConnection
statement for the Policy Agent. The type can be either basic or secure.
For more details, see Step 6: Configure Policy Agent for configuration file import services.
- Import Policy Data panel only:
- Policy type to identify what type of policies to import
- Optional policy configuration file names (common file, stack-specific file, or both)
- Import request name to identify the stack name
The import request name, user name, and policy type are used to identify resources this user can access.
If no import configuration files are passed, the import request name is used to match an existing TcpImage or PEPInstance statement to find the import configuration file names for the input policy type.
- The import requester's port value must be the same as the port value defined on the ServicesConnection statement.
- The import requester's type of security (SSL or not)
must match the type of security configured on the ServicesConnection
statement (secure or basic).
- For the secure type, it must match the Policy Agent generated AT-TLS policies.
- For the basic type, you can either use a default unsecure connection or explicitly define AT-TLS policies to protect the connection.
- Import policies only:
- The import configuration files are parsed only once. The import policies are not installed in the TCP/IP stack, so the FLUSH and PURGE parameters and the MODIFY REFRESH and MODIFY UPDATE commands do not apply to these files. These files are not monitored for changes.
- You can define import policies only in configuration files. You cannot define them on an LDAP server.
- The import request name, user name, and policy type are required for security product authorization in the SERVAUTH class. For authorization details, see Step 1: Configure general information.
For detailed configuration information, see Step 6: Configure Policy Agent for configuration file import services.