The CloudCenter platform provides a framework to enable enterprises to integrate the CCM with a messaging service bus (referred to as the Enterprise Service Bus, ESB) system interface using RabbitMQ, an external AMQP Message Broker. The CCM works with service bus interface to accept message requests, and allows external consumers to listen to the CloudCenter logs and status messages. See Enterprise Service Bus (ESB) >
|15672||Ingress/Egress (optional)||AMQP module in the CCM||For two-way communication with the ESB AMQP module in the CCM. This port must be open if you need to establish access to the AMQP module from the AMQP UI.|
|5671||Ingress/Egress (optional)||AMQP module in the CCM||For two-way communication with the ESB AMQP module in the CCM. This port must be open if you need to establish programmatic access to the AMQP module.|
Depending on your use of out-of-box Services, your environment will need to be accessed.
See Application Tier Properties for details on when these services may need details from your environment.
|1433||Ingress/Egress (optional)||Application VMs|
All communication between Services used by the Application VMs require access to Port 1433. See Worker (Conditional) for additional details.
The CloudCenter platform supports a Federated CCM Management infrastructure.
A Federated CCM Management infrastructure refers to a collection of CCM servers that are connected as a federation of networks to enable information sharing, reduce complexity, and improve management flexibility within a private cloud infrastructure. See Federated CCM Management > Firewall Communication for additional details.
|8443||Ingress/Egress (optional)||Linked CCMs|
All communication between federated CCMs are based on HTTPS protocol defaulting to Port 8443. The Parent CCM can only communicate with mutually authenticated Subordinate CCMs. See CCM Firewall Rules for precise port information.