CentraSite Documentation : Runtime Governance with CentraSite : Virtualized APIs in CentraSite Business UI : Creating Virtualized APIs : Creating a Virtualized API from an Existing Native API : Creating a Virtual SOAP API : Add a Virtual SOAP API
Add a Virtual SOAP API
You use the panel 1 of the Virtualize your API page to specify the proxy and invocation aliases, and endpoints for the new Virtual API.
To add a Virtual SOAP API
1. Display the list of Web services, by executing an advanced search for Service asset type (see Working with the CentraSite Business UI for details).
2. In the displayed list, click the link of the Web service for which you want to create a virtual copy. This shows the profile details of the Web service.
3. In the details page of the Web service, click the Virtualize icon.
4. In the Virtualize <API_Name> (Step 1 of 3) wizard, complete the fields.
In this field...
Do the following...
Create a New Virtual Alias
Enter a name for the new virtual alias.
This name must be NCName-conformant, meaning that:
*The name must begin with a letter or the underscore character (_).
*The remainder of the name can contain any combination of letters, digits, or the following characters: . - _ (that is, period, dash, or underscore). It can also contain combining characters and extender characters (for example, diacriticals).
*The name cannot contain any spaces.
*Furthermore, if the Virtual API name contains any non-conformant character, upon publishing the Virtual API to any gateway, the non-conformant character is simply replaced with the underscore character (_) in Mediator. However, in CentraSite the Virtual API name defined by you is displayed.
For more information about the NCName type, see http://www.w3.org/TR/xmlschema-2/#NCName
An API name does not need to be unique within the registry. However, if for example, a Virtual API with the same name already exists within the native API, a warning message will be issued.
By default, CentraSite populates the Create a New Virtual Alias field with the display name that was specified for the native API.
Endpoint prefix for invocation alias
Optional. Enter a prefix for the alias. It accepts URL paths.
For example, /testmethod/myprefix/, test@1234, and so on.
Endpoints of <API_name> to be virtualized
Select the endpoint that you want to use for invoking the Virtual API.
The Endpoints list displays the URLs of all endpoints that are available for the native API.
5. Click Next to complete the settings.
Copyright © 2005-2015 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback