Virtualizing an Existing Service
You use the Virtualize option to virtualize an existing web service in CentraSite Control.
To virtualize an existing service
1. In CentraSite Control, display the service for which you want to create a virtual copy. For procedures, see CentraSite User’s Guide.
2. On the asset detail page, click Actions and then select Virtualize.
Important: | CentraSite will not allow you to virtualize a service if it does not contain an associated WSDL or schema file in the registry. |
3. In the Virtualize <name of the type> Service wizard, specify the following fields:
In this field... | Specify... |
Name | A name for the new virtual service. Unlike services, the names of virtual services cannot contain spaces or special characters (except _ and -). Consequently, if you adopt a convention that involves using the name of the service as part of the virtual service name, then the names of the services themselves must not contain characters that are invalid in virtual service names. If you want to change the name of a virtual service later, ensure that the service in undeployed, and then change the name in the service's detail page. |
Description | Optional. A description for the virtual service. This description appears when a user displays a list of virtual services in the user interface. |
Organization | Specify the organization to which this virtual service will be added. Note: | The Organization list contains the names of all organizations for which you have Manage Assets permission. |
If you select an organization other than your own organization, you will nevertheless be the owner of the virtual service. Note: | Choose the organization with care. You cannot change the organization assignment after the virtual service is added to the catalog. You can, however, export a virtual service from one organization and import it to another. |
|
Version | Optional. A version identifier for the virtual service. The version identifier is an optional attribute that you can increment when a service is modified to indicate that the service has been updated. You can use any versioning scheme you choose. The version identifier does not need to be numeric. This is the "public" version identifier that CentraSite Control shows to users when it displays the list of services. Examples: 0.0a
1.0.0 (beta)
Pre-release 001
V1-2007.04.30 You can later create new versions of the virtual service. In addition, CentraSite automatically generates a system version number, which is visible on the virtual service detail page. The system version number is independent from the version number you specify here. For more information, see the CentraSite User’s Guide. |
Create a Run-Time Policy | Use this checkbox to specify the behavior for the run-time policy (or policies) associated with the virtual service. If you select the checkbox, the run-time policy or policies associated with the virtual service will be created automatically when the service is virtual. If you do not select the checkbox, the run-time policy or policies will not be created when the service is virtual. You can only select the checkbox if you have the Manage Runtime Policies organization-level permission; without this permission, the checkbox is deactivated. |
4. If you have attributes specified in the service for virtualizing, click Next to go to the attribute mapping dialog.
5. In the Attributes dialog, choose the attributes of the service that you want to copy to the virtual service.
Note: | Keep the following in mind:  If you choose a parent attribute, by default all its child attributes are copied as well. You can de-select any child attribute. Similarly, if you de-select a parent attribute, all its child attributes are de-selected as well. Attributes defined as required in the asset’s type definition and all referenced objects to which the asset has an association will be internally copied from the asset to the virtual service. These attributes will remain selected and disabled by default in the attribute mapping dialog. |
6. Click Finish.
The virtual service is created in the Asset Catalog and its detail page is displayed. The WSDL interface and the entry/exit protocol (for example, HTTP, HTTPS or JMS) will be identical to the service.
Restriction
Even if a Service asset type contains one or more custom profiles, a virtual service of the asset type Service will never include any of these custom profiles in the catalog.
