Creating Database Connections Supported Third-Party Databases

9-90 Oracle Fusion Middleware Users Guide for Technology Adapters

9. Enter your connection string name for JDBC URL.

10. Click Test Connection.

11. If the connection is successful, then a screen, as shown in Figure 9–48 is displayed. Figure 9–48 The Create Database Connection Dialog

12. Click OK followed by Finish.

9.7.3 Design Time: Artifact Generation

The Adapter Configuration Wizard – Stored Procedures is capable of creating a WSDL file and a valid XSD file that describes the signature of a stored procedure or function. The following sections describe the relevant structure and content of both the WSDL and the XSD files, and their relationship with each other. This section includes the following topics: ■ Section 9.7.3.1, The WSDL–XSD Relationship ■ Section 9.7.3.2, JCA File ■ Section 9.7.3.3, Oracle Data Types ■ Section 9.7.3.4, Generated XSD Attributes ■ Section 9.7.3.5, User-Defined Types ■ Section 9.7.3.6, Complex User-Defined Types ■ Section 9.7.3.7, Object Type Inheritance ■ Section 9.7.3.8, Object References ■ Section 9.7.3.9, Referencing Types in Other Schemas Oracle JCA Adapter for Database 9-91 ■ Section 9.7.3.10, XSD Pruning Optimization

9.7.3.1 The WSDL–XSD Relationship

In the paragraphs that follow, the operation name, Factorial, and procedure name, Factorial, are taken from an example cited previously see Figure 9–37 . The generated WSDL imports the XSD file. types schema xmlns= http:www.w3.org2001XMLSchema import namespace= http:xmlns.oracle.compcbpeladapterdbSCOTTFACTORIAL schemaLocation=xsdSCOTT_FACTORIAL.xsd schema types The namespace is derived from the schema, package, and procedure name, and appears as the targetNamespace in the generated XSD. A root element called InputParameters is created in the XSD file for specifying elements that correspond to the IN and INOUT parameters of the stored procedure. Another root element called OutputParameters is also created in the XSD file for specifying elements only if there are any INOUT or OUT parameters. Note that INOUT parameters appear in both root elements. These root elements are represented in the XSD file as an unnamed complexType definition whose sequence includes one element for each parameter. If there are no IN or INOUT parameters, then the InputParameters root element is still created; however, complexType is empty. A comment in the XSD file indicates that there are no such parameters. An example of one of these root elements follows. element name=InputParameters complexType sequence element … … sequence complexType element The WSDL defines message types whose parts are defined in terms of these two root elements. message name=args_in_msg part name=InputParameters element=InputParameters message message name=args_out_msg part name=OutputParameters element=OutputParameters message The db namespace is the same as the targetNamespace of the generated XSD. Note that the args_in_msg message type always appears in the WSDL while args_out_ msg is included only if the OutputParameters root element is generated in the XSD file. An operation is defined in the WSDL whose name is the same as the adapter service and whose input and output messages are defined in terms of these two message types. portType name=Factorial_ptt operation name=Factorial