CA Workload Automation AE uses no encryption or AES 128-bit encryption to exchange data with CA Workload Automation EE and CA WA Agent for z/OS. If you are using AES encryption, you must generate an instance-wide communication alias encryption file (cryptkey_alias.txt) in the $AUTOUSER.instance_name (on UNIX) or %AUTOUSER%.instance_name (on Windows) directory. The cryptkey_alias.txt file stores the communication alias encryption key.
Note: For more information about generating the instance-wide communication alias encryption file, see the Windows Implementation Guide.
Important! You must set AES encryption for z/OS communication only if AES encryption is also configured on CA Workload Automation EE or the agent on z/OS. For more information about the encryption types that CA Workload Automation EE and the agent on z/OS support, see the CA Workload Automation EE and CA WA Agent for z/OS documentation.
Notes:
Follow these steps:
The Instance - CA Workload Automation AE Administrator window opens.
The Services - CA Workload Automation AE Administrator window appears, displaying a list of services installed on the selected instance.
The scheduler and application server stop.
The Instance - CA Workload Automation AE Administrator window appears.
The Hexadecimal Key and Verify Hexadecimal Key fields are enabled.
Note: If you clear the Use AES 128-bit encryption when communicating with zOS managers check box, CA Workload Automation AE uses no encryption for z/OS communication.
Note: The encryption key must be a hexadecimal string of 32 characters.
The Services - CA Workload Automation AE Administrator window appears, displaying a list of services installed on the selected instance.
The scheduler and application server start. The encryption for z/OS communication is set.
Note: The zOS Encryption Status field in the Instance Encryption Status pane displays the current encryption set for the selected CA Workload Automation AE instance.
|
Copyright © 2013 CA.
All rights reserved.
|
|