|
|
|
System requirements include TCP/IP, UNIX Systems Services and SNMP.
To install CA Agent Technology, follow the instructions in the CA Common Services for z/OS Installation Guide. The installation relies on standard SMP/E procedures RECEIVE, APPLY and ACCEPT. It also requires UNIX System Services under z/OS, including the use of zFS (zSeries File System).
Note: For additional information, see the IBM SMP/E manuals, UNIX System Services manuals, and the z/OS Distributed File Service zSeries File System manuals.
Common Services Prerequisites
There are no CA Common Services prerequisites for Agent Technology itself. However, every agent for which Agent Technology acts as middleware requires the CAIRIM Common Services component for initialization and license checking. Examples of such agents are the z/OS Agent, the CICS Agent, the Memo Agent, and so on..
Files
Two zFS’s are required for Agent Technology running on any single system:
The Read-Only zFS contains executable code, and the ReadWrite zFS contains configuration files, scripts that can be tailored, and log files.
SMP/E APPLY of Agent Technology populates both the zFS and the CA Common Services .CNSMLOAD load library with the same executables.
The ENVFILE used by the mainframe Agents is delivered in the CNSMOPTV data set. It must reflect the environment settings for this installation and its limited settings must match the same environment settings in the /cai/agent/agentworks.profile on the zFS.
Upgrading
If you are upgrading from a previous release, you should do a base install into a new zFS. Many of the configuration file entries required for this release are similar to the entries required by previous releases. Therefore, it is helpful to retain the previous release’s HFS for reference during the Post-Installation configuration phase.
If you are upgrading from a previous release of Agent Technology and you do not intend to re-install the mainframe Agents that you use, you must run the install_agents script found in the $AGENTWORKS_DIR/services/tools directory in order to register the Agents with this installation of AT. This script can be used to add or remove entries from the awservices.cfg file for any Agents or services currently supported on z/OS. Any of the mainframe Agents using Agent Technology must be started using the new CNSMLOAD and the new ENVFILE found in the CNSMOPTV data set.
Multiple Systems
Detailed instructions for installing on multiple z/OS systems is contained in the Agent Technology Post-Installation chapter of the CA Common Services Installation Guide.
Security
One of the key steps to the successful installation of Agent Technology is the establishment of the administrator account (default name, AWADMIN). An installation job is provided to establish this account.
This account must be authorized to:
This account must also specify a HOME directory equal to that of the root Agent Technology directory (cai/agent by default). It is not necessary to use the exact Group and User codes (911 and 912 respectively) as those specified in the installation process.
Additionally, if you use the CA Top Secret Security for z/OS product, you may want to amend the example TSS commands to add syntax to create a department specific to Agent Technology. For example:
tss cre(awdept) type(dept) name('Agent Technology Department')
This department name should then be referenced in the AWGROUP and AWUSER definitions.
Questions occasionally arise regarding the need to grant superuser privileges to user ID’s that are used to run one or more of the z/OS-based agents. It is neither required, nor desired, for these ID’s to hold this privilege. What is required however, is that these accounts must participate in the Agent Technology security group (default name, AWGROUP), as established in the AT installation process. In addition, if you intend to run your agent as a started task, the Agent Technology security group must be the default group for the task’s user ID.
Access to Agent Technology applications and commands may be further tightened by means of the access.off file (which will be renamed if it is to be used) in the /cai/agent/services/config/aws_orb directory. If this extra level of security is desired, please see the comments in that file to determine how to implement the changes. As delivered, this extra security is disabled.
Services
Agent Technology for z/OS is comprised of the following services, which are a subset of the CA NSM services on the distributed platforms:
The service controller.
The object request broker (that is, the communications handler).
The SNMP handler. This service is also responsible for maintaining the MIBs within the Object Store in the UNIX System Services zFS.
Port usage
All the z/OS based agents communicate with the Agent Technology z/OS services, which in turn communicate with the distributed NSM machines’ Agent Technology services. The communication occurs using the TCP/IP protocol. By default, the following ports are used by these services on the mainframe:
Review the TCPIP.ETC.SERVICES file to determine if any other service has been registered to use any of these ports. In addition, you should review the BPXPRMnn used at IPL to determine if any of these ports is within a range of ports has been reserved in the INADDRANYPORT and INADDRANYCOUNT settings.
If you need to change the UDP port used by aws_ sadmin, you must modify the servicectrl command for aws_sadmin in the $AGENTWORKS_DIR/services/tools/install_agents script for the port, that is change the following:
-p 6665 to -p wwww
where wwww is the new port number.
Then rerun the script.
If you need to change the TCP port for ORB-> ORB communications, modify the $AGENTWORKS_DIR/services/config/aws_orb/quick.cfg file with the new port number. For example:
PLUGIN QIKSODLL xxxx
where xxxx is the new port number.
If you need to change the awservices request or control port, you can reassign those port numbers by including the following environment variables with the new assignments to the agentworks.profile file in your $AGENTWORKS_DIR directory:
export AWS_STARTER_REQUEST=yyyy export AWS_STARTER_CONTROL=zzzz
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |