Create Virtual Service
You use panel 1 of the Virtualize Your API page to specify the proxy and invocation aliases, and endpoints for the new Virtual Service.
1. In CentraSite Business UI, access the Advanced Search panel in one of the following ways:
Click the
Browse link in the upper-left corner of the menu bar.
Click the
Search icon next to the
Scope list. The default search scope is
Assets.
This displays a list of assets in the Search Results page.
2. In the Additional Search Criteria list, select Asset Types.
3. To search for the assets of type, Web Service, click Choose.
4. In the Choose Asset Types dialog box, select the Assets option button, and follow these steps:
a. Click the chevron next to Assets option button.
b. In the displayed list of asset types, select Service.
c. Click OK.
5. Click the Web Service you want to virtualize.
This opens the Web Service details page. Also, the actions bar displays a set of actions that are available for working with the Web Service.
6. On the actions bar of the Web Service details page, click Virtualize.
7. In the Virtualize <Service_Name> (Step 1 of 3) wizard, provide the required information for each of the displayed data fields.
Field | Description |
Create New Virtual Alias | Name of the Virtual Service asset (also, termed as Virtual Alias). The name of a Virtual Service asset 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 Service name contains any non-conformant character, upon publishing the Virtual Service to any gateway, the non-conformant character is simply replaced with the underscore character (_) in Mediator. However, in CentraSite the Virtual Service name defined by you is displayed. Note: The name of a Virtual Service asset must be unique within an organization. If, for example, a Virtual Service with the same name already exists within the CentraSite registry, 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 Service. |
Endpoint prefix for invocation alias | (Optional). Prefix for the Virtual Service. This field accepts URL paths. Example: /testmethod/myprefix/ test@1234 |
Endpoints of <API_name> to Virtualize | The Native Service endpoint you want to use for invoking the Virtual Service. The Endpoints list displays a list of the Endpoint URLs available for the Native Service. |
8. Do one of the following:
Click
Next and proceed to panel 2 to proceed with configuring run-time policy actions. This button is enabled only if the run-time aspects from
CentraSite is enabled. For procedure to enable CentraSite run-time aspects, see
Enabling CentraSite Run-Time Aspects.
Click
Virtualize to create virtual (proxy) copy of REST Service (without publishing the newly created Virtual Service to the selected gateways).
A Virtual REST Service asset instance is created in the specified organization and registered with the CentraSite registry/repository. The details page for the Virtual REST Service that you just created is displayed.
Note:
The Virtualize button is displayed in panel 1, only if the CentraSite run-time aspects are not enabled.