After you export the configuration of an external Orchestrator server and import it to vRealize Automation 7.2, you must configure the Orchestrator server that is built into vRealize Automation.

Prerequisites

Migrate the configuration from the external to the internal vRealize Orchestrator.

Procedure

  1. Log in to the vRealize Automation Appliance over SSH as root.
  2. Start the Control Center service of the built-in vRealize Orchestrator server.
    service vco-configurator start
  3. Log in to Control Center of the built-in Orchestrator server as root.
    Note:

    If you migrate from an external vRealize Orchestrator 7.2 instance, skip to 8.

  4. Go to the advanced Orchestrator Management page, at https://vra-va-hostname.domain.name:8283/vco-controlcenter/#/?advanced.
    1. Refresh the browser page by clicking the F5 button on the keyboard.
  5. On the Configure Database page, click Save.
    Note:

    If the Save button is not active, click Update Database and after that click Save.

  6. Verify that Orchestrator is configured properly at the Validate Configuration page in Control Center.
  7. On the Licensing page, select vRA License from the Select License Provider drop-down menu.
  8. If the external Orchestrator was configured to work in cluster mode, reconfigure the Orchestrator cluster in vRealize Automation.
    1. Go to the advanced Orchestrator Cluster Management page, at https://vra-va-hostname.domain.name:8283/vco-controlcenter/#/control-app/ha?advanced&remove-nodes.
      Note:

      If the Remove check boxes next the existing nodes in the cluster do not appear, you must refresh the browser page by clicking the F5 button on the keyboard.

    2. On the Orchestrator Node Settings page, change the Number of active nodes to 10.
    3. If you want to remove some of the external Orchestrator nodes from the cluster, select the check boxes next to these nodes and click Remove.
    4. To exit the advanced cluster management page, remove the &remove-nodes string from the URL and refresh the browser page by clicking the F5 button on the keyboard.
    5. At the Validate Configuration page in Control Center, verify that Orchestrator is configured properly.
  9. (Optional) : Under the Package Signing Certificate tab on the Certificates page, generate a new package signing certificate.
  10. (Optional) : Change the values for Default tenant and Admin group on the Configure Authentication Provider page.
  11. From the Startup Options page, start the Orchestrator server service of the built-in Orchestrator server in vRealize Automation.
  12. Verify that the vco-server service appears as REGISTERED under the Services tab in the vRealize Automation Appliance management console.
  13. Select the vco services of the external Orchestrator server and click Unregister.

What to do next

  • Import any certificates that were trusted in the external Orchestrator server to the trust store of the built-in Orchestrator. For more information, see Manage Orchestrator Certificates.

  • Join the vRealize Automation replica nodes to the vRealize Automation cluster to synchronize the Orchestrator configuration.

  • Update the vRealize Orchestrator endpoint to point to the migrated built-in Orchestrator server.

  • Add the vRealize Automation host and the IaaS host to the inventory of the vRealize Automation plug-in, by running the Add a vRA host and Add the IaaS host of a vRA host workflows.