VCP-410 Dumps

o Orchestrator Default Ports: Purpose Port Description Lookup 8230 The main port to communicate with the Orchestrator server (JNDI port). Command 8240 The application communication port (RMI container port) used for remote invocations Messaging 8250 The Java messaging port used to dispatch events. Data 8244 The port used to access all vcp-410 Orchestrator data models, such as workflows and policies. HTTP server 8280 The port for the HTTP connector used to connect to the Web front-end. HTTPS server 8281 To connect to the Web front-end and to communicate with vCenter API. HTTP access 8282 The access port for the Web UI of Orchestrator configuration. HTTPS access 8283 The SSL access port for the Web UI of Orchestrator configuration. To enable configure Jetty to use 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. 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 25 Email notifications. o The Orchestrator configuration interface uses a secure connection to communicate with vCenter. You can import the required SSL certificate from a URL or file. o The users in the Developers role have editing privileges on all elements. o Plug-in file extensions are .vmoapp (can contain several .dar files) and .dar (contains all the resources associated with one plug-in). o You must import the vCenter Server license. The set of plug-ins delivered with Orchestrator do not require a license vCenter Orchestrator 4.0 – Administration Guide o VMware vCenter Orchestrator is a vmware vcp 410 development & process-automation platform that provides a library of extensible workflows to allow you to create & run automated, configurable processes to manage the VMware vCenter infrastructure. o Orchestrator is composed of three distinct layers: an orchestration platform that provides the common features required for an orchestration tool, a plug-in architecture to integrate control of subsystems, & a library of preexisting processes. o Three global user roles: Administrators, Developers (creates applications, customizes/creates new workflows & customizes web front ends), & End Users (can run & schedule workflows & policies.). o You can access Orchestrator through the Orchestrator client interface, through a Web browser, or through Web services. o The Orchestrator client is a desktop application to perform daily administration tasks such as importing packages, running & scheduling workflows & policies, & managing user permissions. It also serves as an IDE for creating or customizing workflows. o Workflows consist of actions, attributes, parameters, & schemas. o Read-only workflow attributes act as global constants for a workflow. Writeable attributes act as a workflow’s global variables. o You use attributes to transfer variables between workflow elements. o A workflow schema is a graphical representation of a workflow that shows the workflow as a flow diagram of interconnected workflow elements. o A workflow token represents a workflow that is running or has run. o Actions are JavaScript functions that take multiple input parameters & have a single return value. o Action referencing is based on the action module name & action name. Make sure that all elements that reference this action are still valid after you move the action. o The Find Elements that Use this Element function checks all packages, workflows, & policies, but it does not check in scripts. o You can use a task to schedule a workflow once, or multiple times. o Policies are event triggers that monitor the activity of the system. Policies run predefined events in response to changes in the status or performance of certain defined objects. o Packages are for transporting content vmware vcp 4 from one Orchestrator server to another. Packages can contain workflows, actions, policies, Web views, configurations, or resources. o Orchestrator signs packages & encrypts the packages for data protection. Packages use X509 certificates to monitor which users export & redistribute elements. o Orchestrator client interface allows you to add, import, export, & synchronize packages. o The naming convention for packages is .category.. o Packages from Orchestrator 4.0 are not backwards compatible with Orchestrator 3.2. o Plugins installed by default: o vCenter 4.0 o vCO library – provides workflows that act as templates o Mail – SMTP o SSH