Create a Physical Data Service from a Web Service
This page last changed on Jan 12, 2009.
Oracle Data Service Integrator Documentation > Data Services Developer's Guide How To Create a Physical Data Service from a Web ServiceIn Oracle Data Service Integrator, three top-level provider types are identified:
A Web service is a self-contained, platform-independent unit of business logic that is accessible through application adaptors, as well as standards-based Internet protocols such as HTTP or SOAP. Web services greatly facilitate application-to-application communication. As such they are increasingly central to enterprise data resources. A familiar example of an externalized Web service is a frequent-update weather portlet or stock quotes portlet that can easily be integrated into a Web application. Similarly, a Web service can be effectively used to track a drop shipment order from a seller to a manufacturer. TopicsSetting Up the Physical Data Service Creation WizardPhysical data services are created using a wizard. Physical Data Service Creation WizardStarting the WizardTo start the physical data service creation wizard:
Creating a New Physical Data ServiceAccessing a Web ServiceAfter you select web service as your data source, you are given the option of specifying a WSDL file, URI, or ALSB proxy service.
Selecting Web Service as a Data SourceThere are several ways to access a specific web service:
Locating a WSDL FileYou can select a WSDL file in two ways:
Browsing to a WSDLClick Browse to navigate to a WSDL in your current dataspace project. Downloading a WSDL File via the Service Consumption FrameworkTo download a WSDL file using the Service Consumption Framework:
Using the Service Consumption Framework to Access a WSDLThe following table briefly describe available service resources:
Selecting the Product TypeFor a Workspace service resource, services can be consumed from several types of products. By default, three product types are available:
If AquaLogic Service Bus is present, ALSB may also be an option. Selecting a WSDL from an ALDSP WorkspaceIf you download a WSDL via SCF through either the Enterprise Repository or Workspace option and you are using the ALDSP or ALSB product type, you can locate and view the originated service of the WSDL using the Navigate to External Service right-click menu option on the WSDL file in the Project Explorer. Specifying a WSDL URIYou can select an external WSDL through the URI Web Service Data Source option.
Importing Metadata from a WSDLThe ALSB Proxy Service OptionTo access web services through AquaLogic Service Bus (ALSB) you need to:
AquaLogic Service Bus access requires providing the following:
This information should be available from your AquaLogic Service Bus administrator.
After the required information is provided, the WSDL will become available using the name of the selected proxy service. Steps in Importing a Web Service
Selecting Web Service Operations to ImportFrom the list of available webservice operations grouped by serviceName and portname, choose the operation that you want to turn into data service operation. Selecting Web Service Operations
Adding Operations to an Existing Data ServiceYou can add operations to an existing physical data service based a web service by adding an external function from the same WSDL.
Adding an External Operation to a Data ServiceSteps Involved in Selecting Web Service Operations
Setting Characteristics of Imported Web Service OperationsThe following table describes available options for each operation you have selected to import. Options Available for Imported Web Service Operations
Setting Characteristics of Imported Web Service OperationsSetting the Data Service NameYou can change the name of your data service to any legal name that does not conflict with another name in the current data space. In addition, if there already is a data service in your project based on the same WSDL an option to add the new operation to the existing data service appears.
Generally Available Test WSDLsAs of this writing the following sample URIs can be used for experimentation with importing WSDLs as data services: Implementation NotesThis section contains implementation notes. Special Considerations when Creating a Data Service Based on a RPC-Style Web ServiceIn case of RPC-style web services, results are return as qualified or unqualified based on the setting of the schema attribute: elementFormDefault In the general case of web services, elementFormDefault can be overridden by setting the form attribute for any child element. However, such individual settings are ignored for RPC-style web services since only the global setting (qualified or unqualified) is taken into account. For example: <s:schema elementFormDefault="qualified" targetNamespace="http://temp.openuri.org/SampleApp/CustomerOrder.xsd" xmlns:s0="http://temp.openuri.org/SampleApp/CustomerOrder.xsd" xmlns:s="http://www.w3.org/2001/XMLSchema"> <s:complexType name="ORDER"> <s:sequence> <s:element minOccurs="0" maxOccurs="1" form="unqualified" name="ORDER_ID" type="s:string"/> <s:element minOccurs="0" maxOccurs="1" form="unqualified" name="CUSTOMER_ID" type="s:string"/> </s:sequence> </s:complexType> </s:schema> In the above code the global element is qualified but a child element (ORDER_ID) is unqualified. In the standard case, the special setting of "unqualified" for ORDER_ID will be honored. In the case of RPC-style web services, however, the runtime will generate "qualified" attributes for all the elements, including ORDER_ID.
Multi-dimensional Arrays in RPC ModeMulti-dimensional arrays in RPC mode are not supported. See Also |
Document generated by Confluence on Jan 13, 2009 15:57 |