CloudHealth – UPDATE PERSPECTIVE
CloudHealth – UPDATE PERSPECTIVE
To use the adapter for CloudHealth, to update perspective, fill the field “Web Service Home URL” with the CloudHealth URL you want to connect to. Then, provide a valid username/password to connect, or the API credentials (API Key), that can be generated by a valid account.
Please, make sure that the account has the correct permissions to use CloudHealth API: http://apidocs.cloudhealthtech.com/#documentation_getting-your-api-key
The “Next” button steps into the next window that shows the available operations of this Web Service; choose “UPDATE PERSPECTIVE”, to push groups to the desired perspective in CloudHealth.
After selecting the desired operation, it is required to enter a name and a description for the adapter into the appropriate fields; the user must browse the file system for the adapter folder (used to save intermediate and result file for adapter execution).
The next button steps into the next window that allows the user to set values for the Web Service parameters.
When a lens icon shows beside the parameter name, this means that user may choose the parameter value from a list of available items.
In case of this example, with the double-click on the lens icon, a table appears, with the available perspectives:
and Queryable assets:
Select and apply the selection, even using multiselection in case of queryable assets:
Pressing the “Save” button will store all the entered parameters for the web service adapter in the DT database.
The “Exit" button closes the data preview window and goes back to the Web Service configuration form.
The Adapter, as mentioned, can be used to push data to CloudHealth and fill perspective groups. Based on an asset tag (for instance, application ID), corresponding metadata associated with the application ID will be pushed to CloudHealth in the form of perspectives and groups.
As an example, the perspective listing an Application Ecosystem and their associated applications can be aligned configuring a workflow, with a source providing values for application ecosystems name and associated application ID, and with the target operation “Web Service POST”, using the configured adapter. To provide mappings between source and target field, use a “Data Formatting: Rename and Order Columns” transformation, with the mandatory “Name” field for the perspective groups, the optional “ref_id” field to manage object renaming and additional fields name corresponding to tag fields to populate:
Business Terms from BGM – Download Business Terms
Business Terms from BGM – Download Business Terms
To use the adapter for BGM to get Business Terms, select the authorization method (Account / Access Token) and enter the relevant credentials.
Click the 
Click the
To save the adapter to the DT database, click the 
Click the
To preview a sample of the first 50 results, click the 
To save the adapter to the DT database, click the
Business Terms from BGM – Upload Business Terms
Business Terms from BGM – Upload Business Terms
To use the adapter for BGM to get Business Terms, select the authorization method (Account / Access Token) and enter the relevant credentials.
Click the
Click the
The adapter can now be used as a target endpoint when mapping data in a workflow. To select the adapter as a target, select “Web Service POST” as the operation and select your BGM adapter. A mapping table will appear, allowing the source fields to be mapped to relevant target fields for creating BGM Business Terms.
erwin DISuite Metadata Manager
erwin DISuite Metadata Manager
To use the adapter for erwin DISuite Metadata Manager to download Data Dictionary, provide the url of erwin DISuite and enter the relevant credentials
Click the
Provide the “System Name”, “System Id”, “Environment Name”, “Environment Id” in their respective edit box.
Enter a name and folder for the adapter. A description can also optionally be entered for the adapter.
Click the
To preview a sample of the first 50 results, click the
To save the adapter to the DT database, click the