CA Process Automation provides the primary interface for content development. System administrators and content administrators use CA Process Automation for the following activities:
Security for CA Process Automation involves user authentication at login and role-based access. You define user accounts, custom groups, and policies that grant permissions through CA EEM.
Domain is the term that is used to describe the enterprise view of the entire CA Process Automation system, including Orchestrators, agents, and process libraries. Domain administration includes adding environments, removing unused agents and touchpoints in bulk, and managing domain properties.
An Orchestrator is the engine component of CA Process Automation that reads from the process library and executes processes. The first CA Process Automation Orchestrator that you install is the Domain Orchestrator. You can add more nodes to the Domain Orchestrator for added processing power and load balancing. If your users are geographically dispersed, consider adding a new standard Orchestrator in each location.
An environment is an optional partition of the Domain that separates content development. Environments can be created for development, testing, and production or for different business units. Configuration includes adding touchpoints and creating touchpoint groups.
An agent is CA Process Automation software that you install on a network host. Orchestrators that run processes can run certain steps of the process on agent hosts or remote hosts to which agents have SSH connections. Configuration includes associating touchpoints, proxy touchpoints, or host groups to agents.
A touchpoint is a logical entity used in operator definitions to represent the target agent or Orchestrator where some portion of the process executes. You can map a touchpoint to many agents at once and to different agents over time. Touchpoints provide flexibility in process implementation while reducing maintenance requirements for the processes themselves.
Remote hosts, that is, hosts without an installed agent, can be targeted to execute operations as part of a running process. To enable connectivity, you establish SSH access from a host with an agent to the remote host. On the host with the agent, you configure either a proxy touchpoint or a host group. An operator can target a host with its proxy touchpoint name. A host group references remote hosts. An operator can target such a remote host with its FQDN or an IP address.
Note: See Syntax for DNS Host Names.
A library is the repository containing operator objects and scripts that content designers assemble to create processes. Processes and other automation objects are stored in the library.
Automation objects define processing, scheduling, monitoring, logging, and other configurable elements of a CA Process Automation package. Automation objects are stored in a library of a specific Orchestrator in a nonclustered architecture. Administration of automation objects includes the optional configuration of security settings on a library folder or object to control access for designated groups and users.
You can create custom CA EEM policies for automation objects. For example, enable Touchpoint Security and create Touchpoint Security policies in CA EEM to limit who can run certain operators on specified high-valued targets. Enable Runtime Security and use Set Owner to grant process starting rights to only the owner of the process.
An example of process administration is aborting failed processes from a process watch.
|
Copyright © 2014 CA.
All rights reserved.
|
|