When you register Application Services, you use the CLI to establish a connection between the Application Services environment and the vRealize Automation server so that you can access the vRealize Automation service catalog.

About this task

Typically, registration is done as part of starting the Application Services appliance. Use this procedure if you need to reestablish the registration or if registration information has changed.

When the connection between Application Services and vRealize Automation is established, you can publish the deployment profile to the vRealize AutomationApplication Services catalog so that other users can request the deployment profile. You can also assign Application Services roles to users and user groups after registration.

Note:

You can have only one active registration. If you try to register more than once, you receive an error message.

Prerequisites

  • Log in to Application Services as a system administrator.

  • Verify that you know the password for the darwin_user. This password was set during installation. See Start the Application Services Appliance.

  • Start the Application Services CLI. See Start the CLI Remotely.

  • The vRealize Automation IaaS environment and endpoints must be properly set up and configured. See Installation and Configuration and IaaS Configuration for Virtual Platforms.

  • You must have SSO admin credentials available.

Procedure

  1. In the roo shell prompt, register Application Services to the vRealize Automation server. 
    register-vcac-server --componentRegistryUrl vCACServerURL --ssoAdministratorUsername 
UserName --ssoAdministratorPassword Password

    The componentRegistryUrl is the URL for the vRealize Automation self-service catalog.

    A sample URL for the componentRegistryUrl is https://vcac-oci-071.eng.test.com.

    The registration might take approximately 30 seconds before the status message, vCAC server registered successfully, appears.

  2. (Optional) View the vRealize Automation server information.

    list-vcac-info

  3. (Optional) If there are any changes in the vRealize Automation server information, register Application Services to the vRealize Automation server. 
    register-vcac-server --componentRegistryUrl vCACServerURL --ssoAdministratorUsername 
UserName --ssoAdministratorPassword Password --update
  4. (Optional) Unregister the vRealize Automation server from Application Services to register the appliance to another vRealize Automation server.

    unregister-vcac-server

    Unregister the vRealize Automation server only if the server becomes unusable with Application Services. If you then register Application Services with a different vRealize Automation server, the existing cloud providers and deployment environments become unusable because the underlying templates are no longer valid. You also lose access to any existing Application Services content if the business groups in the new and old vRealize Automation servers do not match.

What to do next

After you register Application Services to vRealize Automation, register the cloud provider and template. See Register the vRealize Automation Cloud Provider and Template.