# Administration Guide

# Viewing Native Web Services

A native web service is a data service that is exposed as a web service through Oracle Data Service Integrator. It allows a direct mapping from the data service to the web service and updates configurations at runtime.

To generate a native web service the system requires a web service map file, which is used to generate the WSDL for the web service. A web service map file describes the mapping between the data services, functions, and WSDL operations.

- For more information about creating a native web service, refer to How To Generate a Web Service Map from a Data Service in the Data Services Developer’s Guide.
- For information about consuming a native web service, refer to Invoking Data Services Through Web Services in the Application Developer’s Guide.

Oracle Data Service Integrator Administration Console displays the web service map artifacts in the dataspace through the Service Explorer.

This chapter describes the steps to view the artifacts for the web service and the WSDL definition, and export it using Oracle Data Service Integrator Administration Console.

## Viewing Native Web Service Artifacts

When you click the Service Explorer category for a web service, the following tabs are displayed in the workspace content area, as shown in Figure 6-1.

Note: | For more information about using the Service Explorer, refer to Chapter 7, “Viewing Metadata Using the Service Explorer.”

### Using the General Tab

This tab displays general configuration information about the web service, such as the target namespace, SOAP version, the status of the ADO.NET control. In addition, it provides the option to select basic authorization for the web service. Figure 6-1 displays the General tab page for the ADDRESS.ws.

Figure 6-1 Native Web Service: General Tab

Note: | You can set security policies for a native web service using the Basic Auth Required property. For more information, refer to Securing Native Web Services section in Chapter 5, “Securing Oracle Data Service Integrator Resources.”

Using the General tab, you can also perform the following functions:

- Test the Generated Web Service
- View the WSDL
- Export the Static JAR File

#### Test the Generated Web Service

Click the Test Web Service link on the General tab. This displays the WebLogic Test Client, which allows you to test the web service as shown in Figure 6-2.

Figure 6-2 WebLogic Test Client

#### View the WSDL

Click the View WSDL Definition link to open the WSDL definition for the web service. A sample WSDL definition looks similar to the displayed in Figure 6-4.

Figure 6-3 WSDL Definition

#### Export the Static JAR File

Click the Export Static Client Jar link (Figure 6-1) to export the web service artifacts. This option is useful when a client needs to consume the data service as a static web service.

### Using the Operations Tab

This tab displays information about underlying data service and data service functions associated with the web service as shown in Figure 6-4.

Figure 6-4 Native Web Service: Operations Tab

### Using the Data Lineage Tab

This tab displays the dependencies and where used information for the web service. The information is same as the data lineage for the referenced data service as shown in Figure 6-5.

Figure 6-5 Native Web Service Data Lineage

## Generating a Web Services Mediator Client JAR File

To use the Static Mediator API in a web services-enabled client application, you must generate a Web Services Mediator Client JAR file. This JAR file contains the Static Mediator API interfaces, plus all the necessary SDO-compiled schemas for a data space. This section explains how to generate a Web Services Mediator Client JAR file using the Administration Console.

Tip: | For information on the Static Mediator API and on writing web services-enabled clients, see the Client Application Developer’s Guide.

1. Start the Oracle Data Service Integrator Administration Console. See the Oracle Data Service Integrator Administration Guide for instructions.
2. Select the Service Explorer category, as shown in Figure 6-6.
Figure 6-6 Selecting the Service Explorer Category

3. In the explorer, click the Data Space node that you wish to export. In Figure 6-6, the node is called myDataspace.
4. In the Data Space pane, select the General tab.
5. Select Export Webservice Map Static Mediator Client Jar, as shown in Figure 6-7. The mediator JAR file is saved to your local file system.
Figure 6-7 Exporting the Client JAR File

## Generating a Mediator Client JAR File

To use the Static Mediator API in a web services-enabled client application, you must generate a Mediator Client JAR file. This JAR file contains the Static Mediator API interfaces, plus all the necessary SDO-compiled schemas for a data space. This section explains how to generate a Mediator Client JAR file using the Administration Console.

Tip: | For information on the Static Mediator API and on writing web services-enabled clients, see the Client Application Developer’s Guide.

1. Start the Oracle Data Service Integrator Administration Console. See the Oracle Data Service Integrator Administration Guide for instructions.
2. Select the Service Explorer category, as shown in Figure 6-8.
Figure 6-8 Selecting the Service Explorer Category

3. In the explorer, click the Data Space node that you wish to export. In Figure 6-8, the node is called myDataSpace.
4. In the Data Space pane, select the General tab.
5. Select Export Static Mediator Client Jar, as shown in Figure 6-9.
Figure 6-9 Exporting the Client JAR File