To perform general administration tasks or to edit and create workflows, you must log in to the Orchestrator Legacy Client interface.
The Orchestrator Legacy Client interface is designed for developers with administrative rights who want to develop workflows, actions, and other custom elements.
- Download and deploy the Orchestrator Appliance.
- Verify that the appliance is up and running.
- Install 64-bit Java on the workstation, on which you run the Orchestrator Legacy Client.
Note: 32-bit Java is not supported
- In a Web browser, go to the IP address of your Orchestrator Appliance virtual machine.
- Click Start Orchestrator Client.
- Enter the IP or the domain name of the Orchestrator Appliance in the Host name text box.
The IP address of the Orchestrator Appliance is displayed by default.
- Log in by using the Orchestrator Legacy Client user name and password.
Depending on whether you use vRealize Automation or vSphere as an authentication provider, enter the respective credentials to log in to the Orchestrator Legacy Client.
If multi tenancy is enabled on your Orchestrator environment, enter the respective system administrator or tenant administrator user name, password, and tenant ID.
- In the Security Warning window, select an option to handle the certificate warning.
The Orchestrator Legacy Client communicates with the Orchestrator server by using an SSL certificate. A trusted CA does not sign the certificate during installation. You receive a certificate warning each time you connect to the Orchestrator server.
Option Description Ignore
Continue using the current SSL certificate.
The warning message appears again when you reconnect to the same Orchestrator server, or when you try to synchronize a workflow with a remote Orchestrator server.
Cancel Close the window and stop the login process. Install this certificate and do not display any security warnings for it anymore. Select this check box and click Ignore to install the certificate and stop receiving security warnings.You can change the default SSL certificate with a certificate signed by a CA. For more information about changing SSL certificates, see Installing and Configuring VMware vRealize Orchestrator.
What to do next
You can import a package, start a workflow, or set root access rights on the system.