CA Process Automation

Transcription

1 Communications Release

2 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 Chapter 1: Communications Overview Users of use a supported browser ( Client) to connect to Orchestrators, possibly through a load balancer, to perform configuration, to create and modify automation objects, to start and monitor processes and to respond to interaction requests. Clients communicate with an Orchestrator through its HTTP port. Multiple clients and consoles can be initiated from the same desktop systems and can point to the same or different Orchestrators even Orchestrators in different domains. Orchestrators and Agents communicate bi-directionally to perform process operations. Orchestrators also need to communicate with one or more Relational Database Management systems for access to data persisted in the CA Process Automation Runtime, Library, and Reporting databases, as well as the CA Embedded Entitlements authentication and authorization directory. A Domain Orchestrator will also perform mirroring, heartbeat and configuration updates with the Agents and with other For Proxy Agents or Touchpoints, a particular Agent is configured to communicate with the remote host through SSH (v2). The remote host must be running an SSH Server and, for some operations, must have a write-accessible file system. Communication between Agents on UNIX or Windows boxes is based on TCP/IP. Data transmitted between components is encrypted. This section contains the following topics: Sample Configuration (see page 4) Chapter 1: Communications Overview 3

4 Sample Configuration Sample Configuration The following illustration shows the components for a typical deployment with the direction of between components. Please refer to s Used by CA Process Automation (see page 5) for details on the ports and protocols used by each component. 4 Communications

5 Chapter 2: s Used by CA Process Automation The following tables describe in detail the port usage of the various CA Process Automation components. These tables are comprehensive and contain duplication in order to provide a complete picture for each component. This section contains the following topics: s Used by CA EEM (see page 5) s Used by (see page 6) s Used by an Orchestrator (see page 8) s Used by an Agent (see page 12) s Used by Database Servers (see page 13) s Used by Web Clients (see page 13) s Used by CA EEM The following tables provide an overview of the ports used for s from and to CA Embedded Entitlements Manager (CA EEM). Communication from CA EEM From To Listening CA EEM CA EEM 5250 TCP CA EEM configuration Used by CA EEM igateway when CA EEM is configured as an HA cluster CA EEM CA EEM 509 TCP CA EEM configuration Used by CA EEM itechpoz when CA EEM is configured as an HA cluster. CA EEM CA EEM 1684 TCP CA EEM configuration Used by CA EEM itechpoz Router when CA EEM is configured as an HA cluster (CA EEM 8.4 only) Chapter 2: s Used by 5

6 s Used by Communication to CA EEM From To Listening CA EEM CA EEM 5250 TCP CA EEM configuration Used by CA EEM igateway when CA EEM is configured as an HA cluster CA EEM CA EEM 509 TCP CA EEM configuration Used by CA EEM itechpoz when CA EEM is configured as an HA cluster. CA EEM CA EEM 1684 TCP CA EEM configuration Used by CA EEM itechpoz Router when CA EEM is configured as an HA cluster (CA EEM 8.4 only) Orchestrator CA EEM 5250 TCP CA EEM configuration Used by CA EEM igateway (CA EEM Administrator) CA EEM 5250 TCP CA EEM configuration accessing the CA EEM UI. s Used by The following tables provide an overview of the ports used for s from and to the. Communication from the From To Listening Orchestrator 8080 HTTP Apache httpd.conf talks to Orchestrators on this port. Orchestrator 8443 HTTPS Apache httpd.conf talks to secure Orchestrators on this port. 6 Communications

7 s Used by From To Listening Orchestrator 7000 HTTP node0-config.xml, http.port Orchestrator 7443 HTTPS node0-config.xml, https.port Orchestrator 8009 TCP/AJP tomcat.connector.ajp.po rt Catalyst container port Catalyst container secure port Loadbalancer - AJP connector port between Load and Orchestrator Communication to the From To Listening Catalyst REST client Catalyst REST client Agent Agent (CA Process Automation user) (CA Process Automation user) Web Service (SOAP) client Web Service (SOAP) client 7000 HTTP node0-config.xml, http.port 7443 HTTPS node0-config.xml, https.port Catalyst container port Catalyst container secure port 80 HTTP Apache httpd.conf port for basic 443 HTTPS Apache httpd.conf port for secure 80 TCP Apache httpd.conf port for basic 443 TCP Apache httpd.conf port for secure 80 TCP Apache httpd.conf port for basic 443 TCP Apache httpd.conf port for secure Chapter 2: s Used by 7

8 s Used by an Orchestrator s Used by an Orchestrator The following tables provide an overview of the ports used for s from and to a Orchestrator. Communication from an Orchestrator to Another Component From To Listening Orchestrator CA EEM 5250 TCP CA EEM configuration Used by CA EEM igateway Orchestrator Agent 7003 HTTP/ HTTPS Orchestrator Microsoft SQL Database Server Orchestrator MySQL Database Server Orchestrator Oracle Database Server Orchestrator Target Remote Host Agent installation script Agent listens on this port for with Orchestrators 1433 TCP Microsoft SQL configured The database port can be changed in the database server installation; 1433 is the default value TCP MySQL configured The database port can be changed in the database server installation; 3306 is the default value TCP Oracle configured Listener The database port can be changed during Create Listener; 1521 is the default value for the Oracle Listener port. The database instance can be associated with a different listener. Refer to the Oracle configuration. 22 TCP Standard SSH port Used for SSH with a proxy touchpoint or a hostgroup 8 Communications

9 s Used by an Orchestrator Communication between Orchestrators From To Listening Orchestrator Orchestrator 1090 TCP jboss.remoting.port JBoss Remoting port is Orchestrator Orchestrator 1098 TCP jboss.rmi.port JBoss RMI port is used only between Orchestrator Orchestrator 1099 TCP jboss.jndi.port JBoss JNDI port is used only between Orchestrator Orchestrator 1100 TCP jboss.ha.jndi.port JBoss: HA_Java Naming and Directory Interface is Orchestrator Orchestrator 1101 TCP jboss.ha.jndi.port JBoss: HA-Java Remote Method Invocation is Orchestrator Orchestrator 1102 UDP jboss.mcast.jndi.autodisc overy.port Orchestrator Orchestrator 3873 TCP jboss.remoting.transport.connector.port JBoss: JNDI Autodiscovery service is JBoss: EJB3 Remoting Connector is used only between Orchestrator Orchestrator 4444 TCP jboss.rmi.object.port JBoss RMI Server port is Orchestrator Orchestrator 4445 TCP jboss.ha.pooledinvoker.s erverbind.port Orchestrator Orchestrator 4446 TCP jboss.pooledinvoker.serv erbind.port JBoss Pooled Invoker port is used only between JBoss HA Pooled Invoker port is used only between Orchestrator Orchestrator 4447 TCP jboss.ha.rmi.object.port JBoss HA-RMI Server port is used only between Chapter 2: s Used by 9

10 s Used by an Orchestrator From To Listening Orchestrator Orchestrator 4448 TCP JBoss HA Pooled Invoker port is used only between Orchestrators Orchestrator Orchestrator 4457 TCP jboss.service.binding.por t Orchestrator Orchestrator 4712 TCP jboss.tx.recovery.manag er.port JBoss Messaging port is JBoss Transaction Status Recovery Manager port is Orchestrators Orchestrator Orchestrator 4713 TCP JBoss Transaction Status Manager port is used only between Orchestrator Orchestrator 7001 HTTP/ HTTPS oasis.jxta.port Orchestrator Orchestrator 7600 TCP jboss.jgroups.tcp.tcp_por t Orchestrator Orchestrator 7900 TCP jboss.messaging.datacha nneltcpport Orchestrator Orchestrator 7901 TCP jboss.messaging.controlc hanneltcpport Orchestrator Orchestrator 8083 TCP jboss.rmi.classloader.we bservice.port used for between JBoss clustering port is JBoss clustering port is JBoss clustering port is JBoss RMI WebService port is used only between Note: uses JBoss 5.1. In turn, JBoss 5.1 uses intermittent dynamic ports usually in the range ( ) when configured as a cluster for between nodes (Orchestrators only) Many of the ports are used for intra-cluster management. CA does not recommend splitting clusters between WAN links/firewalls. The default cluster configuration uses multicast and, if multicast is not open end-to-end between cluster nodes, they are effectively not part of the same cluster, leading to unpredictable behavior. 10 Communications

11 s Used by an Orchestrator Communication to an Orchestrator from another Component From To Listening Orchestrator 8080 HTTP Apache httpd.conf talks to Orchestrators on this port. Orchestrator 8443 HTTPS Apache httpd.conf talks to secure Orchestrators on this port. Orchestrator 7000 HTTP node0-config.xml, http.port Orchestrator 7443 HTTPS node0-config.xml, https.port Orchestrator 8009 TCP/AJP tomcat.connector.ajp.po rt Agent Orchestrator 8080 HTTP tomcat.connector.http.p ort Catalyst container port Catalyst container secure port Loadbalancer - AJP connector port between Load and Orchestrator UI - Basic port Agent Orchestrator 8443 HTTPS tomcat.secure.port UI - Secure port Agent Orchestrator 7001 HTTP/ HTTPS (CA Catalyst Administrator) oasis.jxta.port Orchestrator 8181 TCP ucf.pax.web.http.port Catalyst Karaf Admin UI - not used in typical operations. Chapter 2: s Used by 11

12 s Used by an Agent s Used by an Agent The following tables provide an overview of the ports used for s from and to a agent. Communication from an Agent From To Listening Agent Orchestrator 8080 HTTP tomcat.connector.http.p ort UI - port for basic. Agent Orchestrator 8443 HTTPS tomcat.secure.port UI - port for secure. Agent Agent Agent Orchestrator 7001 HTTP/ HTTPS Agent Target Remote Host 80 HTTP Apache httpd.conf port for basic 443 HTTPS Apache httpd.conf port for secure oasis.jxta.port 22 TCP Standard SSH port Used for SSH with a proxy touchpoint or hostgroup. Communication to an Agent From To Listening Orchestrator Agent 7003 HTTP/ HTTPS Agent installation script Agent listens on this port for with 12 Communications

13 s Used by Database Servers s Used by Database Servers The following table provides an overview of the ports used for s to a Database server. Communication to a Database Server From To Listening Orchestrator Microsoft SQL Database Server Orchestrator MySQL Database Server Orchestrator Oracle Database Server 1433 TCP Microsoft SQL configured The database port can hanged in the database server installation; 1433 is the default value TCP MySQL configured The database port can changed in the database server installation; 3306 is the default value TCP Oracle configured Listener The database port can be changed during Create Listener; 1521 is the default value for the Oracle Listener port. The database instance can be associated with a different listener. Refer to the Oracle configuration. s Used by Web Clients The following table provides an overview of the ports used for s from the Web clients. Communication from Web Clients From To Listening (CA EEM Administrator) CA EEM 5250 TCP CA EEM configuration accessing the CA EEM UI. Chapter 2: s Used by 13

14 s Used by Web Clients From To Listening (CA Process Automation user) 80 TCP Apache httpd.conf port for basic (CA Process Automation user) 443 TCP Apache httpd.conf port for secure Web Services (SOAP) client Web Services (SOAP) client Catalyst REST client Catalyst REST client (CA Catalyst Administrator) 80 TCP Apache httpd.conf port for basic 443 TCP Apache httpd.conf port for secure 7000 HTTP node0-config.xml, http.port 7443 HTTPS node0-config.xml, https.port Catalyst container port Catalyst container secure port Orchestrator 8181 TCP ucf.pax.web.http.port Catalyst Karaf Admin UI - not used in typical operations. 14 Communications