Generally speaking, you should ensure that the following conditions are satisfied before you create a virtualized service:
Ensure that the interface for the native service is completely implemented and that interface is reflected in the WSDL or schema file that is registered for the service in the CentraSite registry.
An instance of the service is deployed and running at a known point in network.
The metadata for the native service is valid and up-to-date. If the metadata for the native service has not been completely specified or is out-of-date, you should update it before you generate the virtual service so that you do not carry inaccurate/incomplete data into the virtualized service.
There are two ways to virtualize a service:
You can create a virtualized Web Service, REST Service or XML Service from scratch, meaning you manually create the virtualized service and set its attributes.
To create a virtualized service from scratch
In CentraSite Control, go to Asset Catalog > Browse.
Click the Add Asset button.
In the Add Asset dialog, specify the following attributes:
| In this field... | Do the following... |
|---|---|
| Type |
The type of virtualized service that you want to create (i.e., Virtual Service, Virtual REST Service or Virtual XML Service). |
| Name |
A name for the new virtualized service. Unlike native services, the names of virtualized 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 virtualized service name, then the names of the services themselves must not contain characters that are invalid in virtualized service names. If you want to change the name of a virtual service later, make sure the service in undeployed, and then change the name in the service's detail page. |
| Description |
Optional. A description for the virtualized service. This description appears when a user displays a list of virtualized services in the user interface. |
| Organization |
Specify the organization to which this virtualized service will be added. Note: If you select an organization other than your own organization, you will nevertheless be the owner of the virtualized service. Note: |
Click OK. The virtualized service is added to the Asset Catalog. The asset’s details page is displayed.
Important:
During virtualization of an asset, CentraSite will not
allow you to add the virtualized asset to the asset catalog unless you have
specified all “required” attributes in the asset’s type definition and all
referenced objects to which the asset has an association. The value for the
“required” attribute and referenced object must be specified in the virtualized
service’s profile in order to add the asset to the asset catalog.
View or edit the virtualized service's profiles as described in Viewing or Editing the Profiles of Virtualized Services.
Configure the virtualized service's processing steps as described in either Configuring SOAP-based Virtual Services or Configuring REST or XML Virtual Services.
You use the option to virtualize an existing Web Service, REST Service or XML Service in CentraSite Control.
To virtualize an existing service
In CentraSite Control, display the service for that you want to create a virtual copy. For procedures, see the section Using the Asset Catalog.
On the asset detail page, click and then select .
Important:
Be aware that CentraSite will not allow you to virtualize a
service if it does not contain an associated WSDL or schema file in the
registry.
In the Virtualize <name of the type> Service wizard, specify the following fields:
| In this field... | Specify... |
|---|---|
| Name |
A name for the new virtualized service. Unlike services, the names of virtualized 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 virtualized service name, then the names of the services themselves must not contain characters that are invalid in virtualized service names. If you want to change the name of a virtual service later, make sure the service in undeployed, and then change the name in the service's detail page. |
| Description |
Optional. A description for the virtualized service. This description appears when a user displays a list of virtualized services in the user interface. |
| Organization |
Specify the organization to which this virtualized service will be added. Note: If you select an organization other than your own organization, you will nevertheless be the owner of the virtualized service. Note: |
| Version |
Optional. A version identifier for the virtualized 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 (see the section Using the Asset Catalog). In addition, CentraSite automatically generates a system version number, which is visible on the virtualized service detail page. The system version number is independent from the version number you specify here. For more information, see the section Using the Asset Catalog. |
| Create a Run-Time Policy |
Use this checkbox to specify the behavior for the run-time policy (or policies) associated with the virtualized service. If you select the checkbox, the run-time policy or policies associated with the virtualized service will be created automatically when the service is virtualized. If you do not select the checkbox, the run-time policy or policies will not be created when the service is virtualized. You can only select the checkbox if you have the "Manage Runtime Policies" organization-level permission; without this permission, the checkbox is deactivated. |
If you have attributes specified in the service for virtualizing, click to go to the attribute mapping dialog.
In the Attributes dialog, choose the attributes of the service that you want to copy to the virtualized service.
Notes:
Click .
The virtualized service is created in the Asset Catalog and its detail page is displayed. The WSDL or XML interface and the entry/exit protocol (e.g., HTTP, HTTPS or JMS) will be identical to the service.
View or edit the virtualized service's profiles as described in Viewing or Editing the Profiles of Virtualized Services.
Configure the virtualized service's processing steps as described in either Configuring SOAP-based Virtual Services or Configuring REST or XML Virtual Services.
Even if a Service asset type contains one or more custom profiles, a virtualized service of the asset type Service will never include any of these custom profiles in the catalog.
