You can import one or more web services from a web server or a file system to a CentraSite registry and repository. For the import, you must specify a WSDL file that may define one or more web services.
You can update web services in CentraSite by importing an updated WSDL file. The WSDL file must have the same namespace, service names, and organization as the original WSDL file. It may also include additional web services. However, it is not possible to remove a service from CentraSite via an updated WSDL file that no longer includes the corresponding service element.
Please note that the import will fail if you specify a WSDL file containing a namespace and services that already exist in CentraSite but are affiliated to a different organization.
Procedure
Start CentraSite and log in.
Click Create Asset.
Select Service from the Type list.
Optional: Enter a name.
Optional: Select the organization to which the web services are to be assigned.
Optional: Specify a version identifier for the new service. The version identifier you enter here is the service's public, user-assigned version identifier. You can enter any string in the Initial version field, that is, the version identifier does not need to be numeric. You can also leave this field blank.
Optional: Enter a Description.
Enable File in the Import a File section.
Click Choose.
Select the WSDL file you want to import.
Click Next.
In case you imported a new web service, CentraSite retrieves the specified file and creates the web service.
If the importer detects that the service you are trying to import already exists within CentraSite, the import dialog will prompt you to specify whether you want to Create asset, Always overwrite or Always create new versions and click Next.
The following registry objects and folders and files are created by the import of web services:
In the registry, objects are created for different elements defined in the WSDL file being imported: An object of the service type is created for each Service element defined in the WSDL file. The corresponding name attribute in the WSDL file determines the registry object's name. The Service objects are assigned to the organization which you specify in the import parameters. A corresponding Organization object is created, if required.
Depending on the WSDL file, additional objects of the following types may be created: ServiceBinding objects for service bindings, SpecificationLink objects for specification links, Concept objects for bindings, Operation objects for operations, Interface objects for interfaces, BPELPartnerLinkType objects for partnerLinkType elements in the WSDL file, BPELRole objects for role elements within partnerLinkType elements. The new objects are connected by associations and implicit references as required.
For each imported web service, an external link is created, which points to the WSDL file in the repository.
The WSDL file is copied to a subfolder of projects/WSDL in the repository.
The name of the subfolder is determined by the namespace defined in the targetNamespace attribute of the WSDL's definition element. For example, if the namespace is http://www.MyOrganization.com/products, the WSDL file is copied to projects/WSDL/www.MyOrganization.com/products.
The name of the WSDL file in the repository is built as follows:
organization_service_file.wsdl, where organization is the organization name you specify in the import parameters, service is the name of the service as specified in the WSDL, and file is the file name or final part of the URL specified in the import parameters. For example, when you import a web service from C:\services\MyService.wsdl, the service name in the WSDL file is queryService, and the specified organization is MyOrg, the resulting file name in the repository is MyOrg_queryService_MyService.wsdl.
If the WSDL file contains references to schema files, these are also imported, including all of the schema files that are referenced. The folders and files and registry objects that are created correspond to importing an XML schema.