Fetching Details of Migrated Pending Consumer Registrations
Pre-requisites:
To fetch details of migrated consumer registration requests through the CentraSite Command Line Interface, you must have the CentraSite Administrator role.
If you migrate CentraSite from a pre-9.9 version, the consumer registration requests that were pending for an approval by the asset owner in the previous version of CentraSite will continue to remain in the new CentraSite Registry Repository.
Once you have the list of pending consumer registrations from the old Registry Repository, you can do one of the following:
Issue email notifications to specified groups or individuals requesting them to register as consumers for the specified assets.
Manually register the individual consumers for the specified assets.
CentraSite provides a command tool named list Pending Consumer Registrations for this purpose.
To fetch details of pending consumer registrations
Run the command list Pending Consumer Registrations. The syntax is of the format: C:\SoftwareAG\CentraSite\utilities>CentraSiteCommand.cmd list Pending Consumer Registrations -user <USER-ID> - password <PASSWORD> [-url <CENTRASITE-URL>] -file <LOG-FILE>
Note:
This command will not synchronize consumer application, if the
CentraSite run-time aspects are not enabled. By default, run-time policies configured from
CentraSite are disabled. To enable the
CentraSite run-time policies, see
Enabling CentraSite Run-Time Aspects.
The input parameters are:
Parameter | Description |
CENTRASITE-URLurl | (Optional). The URL of the CentraSite registry. For example, http://localhost:53307/CentraSite/CentraSite. |
USER-ID | The user ID of a registered CentraSite user who has the CentraSite Administrator role. For example, Administrator. |
PASSWORD | The password for the CentraSite user identified by the parameter USER-ID. |
LOG-FILE | Name of an output file that will contain the migrated consumer registration details. |
The command response is of the following syntax:
Requested By:
<Name={Name_of_the_Requestor}> <{UDDI_Key_of_the_Requestor}> <Organization=
{Organization_to_which_Requestor_belongs}>
For the Asset:
<Type={Type_ of_the_consumed_asset}> <Name={Name_of_the_consumed_asset}>
<{UDDI_key_of_the_consumed_asset}>
<Organization={Submitting_organization_of_the_consumed_asset}>
<Version={version_of_the_consumed_asset}>
Has Consumers:
<Type={Type_of_the_consuming_asset}> <Name={Name_of_the_consuming_asset}>
<Key={UDDI_key_of_the_consuming_asset}>
<Organization={Submitting_organization_of_the_consuming_asset}>
<Version={version_of_the_consuming_asset}>
….
Example (all in one line):
The command for viewing the pending consumer registration requests with an administrator account INTERNAL\Admin and password AdminPW would be:
C:\SoftwareAG\CentraSite\utilities>CentraSiteCommand.cmd list Pending Consumer Registrations -user INTERNAL\Admin -password AdminPW -url http://localhost:53307/CentraSite/CentraSite –file c:\temp \PendingConsumerRegistrations.txt
The response to this command could be:
Executing the command: list Pending Consumer Registrations
===================================================================
Details of the 'Pending' Consumer Registration Requests
===================================================================
Requested By:
<Name=INTERNAL\Cameron> <Key=uddi:c89dcf73-f25d-11e4-8fd1-b6bf1262f3c2>
<Organization=Default Organization>
For the Asset:
<Type=Virtual Service> <Name=RealTimeStockQuotes_VS>
<Key=uddi:5f8b0a0c-f26a-11e4-b8e7-849ec8059cef>
<Organization=Default Organization> <Version=1.0>
Has Consumers:
<Type=Application> <Name=Cam's Application 3>
<Key=uddi:ea1eeb10-f26f-11e4-b8e7-86fdbb748830>
<Organization=Default Organization> <Version=1.0>
….
Successfully executed the command: list Pending Consumer Registrations