Configuring the server system

On each z/OS® system where you run the server application, see Table 1 for the tasks needed to configure the server.

Table 1. AT-TLS configuration for the server system
Task Specification
Create key ring Create server key ring with server certificate and necessary certificate authority certificates.
Create Policy Agent files
  1. Create a Policy Agent main configuration file containing a TcpImage statement for the server stack.
  2. Create a Policy Agent image configuration file for the server stack.
  3. If AT-TLS policies are to be retrieved from the policy server, create image-specific AT-TLS configuration files, and optionally, common AT-TLS configuration files, on the policy server.
Add AT-TLS configuration
  1. For local AT-TLS policies, add a TTLSConfig statement to the Policy Agent image configuration file, identifying the TTLSConfig policy file location:
    TTLSConfig	serverpath
  2. For remote AT-TLS policies, add a PolicyServer statement to the policy client image configuration file:
    PolicyServer
    {
       ClientName  name
       PolicyType  TTLS
       {
          …
       }
       …
    }
    Add a DynamicConfigPolicyLoad statement to the policy server main configuration file:
    DynamicConfigPolicyLoad  clientname
    {
       PolicyType TTLS
       {
          PolicyLoad  serverpath
       }
       …
    }
Add statements to the AT-TLS policy file Add the AT-TLS policy statements to the serverpath file:
TTLSRule                     XYZServerRule
{ 
       LocalPortRange                     5000	
       JobName                            XYZSRV	 
       Direction                          Inbound
       TTLSGroupActionRef                 XYZGroup
       TTLSEnvironmentActionRef           XYZServerEnvironment
}
TTLSGroupAction              XYZGroup
{
       TTLSEnabled                        On
}

TTLSEnvironmentAction        XYZServerEnvironment
{
       TTLSKeyRingParms
         {
           Keyring                        server_key_ring 
         }
       HandshakeRole                      SERVER
       Trace                              7
} 
Set up InitStack access control
  1. Define the EZB.INITSTACK.sysname.tcpname profile for each AT-TLS stack.
  2. Permit administrative applications to use the stack before AT-TLS is initialized.
For examples of the security product commands needed to create this resource profile name and grant users access to it, see member EZARACF in sample data set SEZAINST.
Enable AT-TLS Set TCPCONFIG TTLS in PROFILE.TCPIP.