1.1.0
Table Of Contents
- Lifecycle Manager Installation and Configuration Guide
- Contents
- Updated Information
- About This Book
- Understanding LCM
- LCM Installation Process
- Installing and Configuring Orchestrator
- Orchestrator System Requirements
- Install Orchestrator
- Orchestrator Components Setup Guidelines
- Configuring Orchestrator
- Check Configuration Readiness
- Log In to the Orchestrator Configuration Interface
- Change the Default Password
- Configure the Network Connection
- Import the vCenter SSL Certificate
- Configuring LDAP Settings
- Password Encryption and Hashing Mechanism
- Configure the Database Connection
- Server Certificate
- Configure the Default Plug-Ins
- Import the vCenter Server License
- Start the Orchestrator Server
- Export the Orchestrator Configuration
- Import the Orchestrator Configuration
- Configure the Maximum Number of Events and Runs
- Change the Web View SSL Certificate
- Define the Server Log Level
- Maintenance and Recovery
- Controlling Orchestrator Access
- Installing and Configuring LCM
- Installing LCM
- Migrating to LCM 1.1
- Configuring LCM
- Check Configuration Readiness
- Initial Configuration of Lifecycle Manager
- Configure the LCM Web View
- Set Approval Requirements
- Configure Archiving Settings
- Change Authorization Groups
- Change the Naming Convention for Virtual Machines
- Enable Email Notifications
- Configure Email Notification Content
- Configure Currency and Date Formats
- Uninstall LCM and Orchestrator
- Index
Default Configuration Ports
Orchestrator uses some specific ports that allow communication with the other systems. It is embedded in a
JBoss application server, and benefits from built-in redundancy, high-availability, and high-performance
distributed application services and support for complex database access.
The communication ports you must set are a subset of the standard ports that JBoss uses. The ports are set with
a default value, but you can change these values at any time. When you make the changes, make sure that all
ports are free on your host and, if necessary, open these ports on required firewalls.
For a list of default ports, see Table 6-1.
NOTE Other ports might be required if you are using custom plug-ins.
Table 6-1. VMware vCenter Orchestrator Default Ports
Communication Port
Port
Number Description
Lookup port 8230 The main port to communicate with the Orchestrator server (JNDI port). All
other ports communicate with the Orchestrator smart client through this port.
It is part of the Jboss Application server infrastructure.
Command port 8240 The application communication port (RMI container port) used to load
remotely. It is part of the Jboss Application server infrastructure.
Messaging port 8250 The Java messaging port used to dispatch events. It is part of the Jboss
Application server infrastructure.
Data port 8244 The port used to access all Orchestrator data models, such as workflows and
policies. It is part of the Jboss Application server infrastructure.
HTTP server port 8280 The port for the HTTP connector used to connect to the Web frontend.
HTTPS server port 8281 The SSL secured HTTP protocol used to connect to the Web frontend and to
communicate with vCenter API.
Web configuration HTTP
access port
8282 The access port for the Web UI of Orchestrator configuration.
Web configuration HTTPS
access port
8283 The SSL access port for the Web UI of Orchestrator configuration.
NOTE To enable the HTTPS connection, configure Jetty to use SSL. For details,
see Jetty Documentation, Configuring SSL.
LDAP 389 The look up port of your LDAP Authentication server.
LDAP using SSL 636 The look up port of your secure LDAP Authentication server.
LDAP using Global Catalog 3268 The port to which Microsoft Global Catalog server queries are directed.
PostgreSQL 5432 PostgreSQL Server for Orchestrator database.
SQL Server 1433 Microsoft SQL Server for Orchestrator database.
Oracle 1521 Oracle Database for Orchestrator database.
MySQL 3306 MySQL for Orchestrator database.
SMTP Server port 25 Used for email notifications.
vCenter API port 443 vCenter API communication port.
Internal Jboss server ports 3455 RMI server registry invoker.
3873 EJB3/AOP remoting connector.
4445 JBoss pooled invoker.
4446 Remoting server service connector.
8083 Dynamic class/resource loader.
Lifecycle Manager Installation and Configuration Guide
28 VMware, Inc.