Registering Custom Hostname Advisor

Version 1
    Share This:

    These are sample files that can be used to register the custom hostname advisor provider definition and the provider instance.  You'll need to pass these in as the REST body content when making a POST call to the CLM UI.  The header for the REST call will require the authentication token from the super user account.

     

    1. Edit the Create-Hostname-ProviderDefinition-input.json replacing the <AO_MODULE_NAME> and <AO_PROCESS_NAME> values with your hostname workflow values.

    2. Make a POST REST request to http://<PlatformManager>:<Port>/csm/providerdefinition with the authentication token in the header and the contents from step 1 as the body.

    3. Find the providerdefinition GUID in the response and make a GET REST request  with the authentication token in the header to http://<PlatformManager>:<Port>/csm/providerdefinition/<GUID>

    4. Ensure the GUID values match the values in the Hostname-RegisterProvider-Input.json (they should, otherwise change them).

    5. Edit the Hostname-RegisterProvider-Input.json replacing the <AO_ORCA_URL>, <AO_USERNAME>, <AO_ENCRYPTED_PASSWORD>, and <AO_GRID_NAME> with your environment values.

    6. Edit the Hostname-RegisterProvider-Input.json replacing the <PROVIDER_DEFINITION_GUID> with the value from step 3.

    7. Make a POST REST request to http://<PlatformManager>:<Port>/csm/provider with the authentication token in the header and the contents from the modified Hostname-RegisterProvider-Input.json.

     

    All subsequent provisioning requests will now call the AO workflow for a hostname.