BPEL_USEJPUB.sql – Creates the schema objects.

Oracle JCA Adapter for Database 9-119 and any additional schema objects must then be reloaded into the database schema. After editing the SQL file, the signature of the wrapper procedure is as follows: TOPLEVELNEEDSWRAPPER B INTEGER DEFAULT 1, N NUMBER DEFAULT 0 For Boolean parameters, the default value for true is 1, and the default value for false is 0. As a final step, the XSD file generated for the wrapper must be edited. A special attribute must be added to elements representing parameters that now have default clauses. Add db:default=true to each element representing a parameter that now has a default clause. For example, element name=B … db:default=true … element name=N … db:default=true … This attribute is used at run time to indicate that if the element is missing from the instance XML, then the corresponding parameter must be omitted from the procedure call. The remaining attributes of these elements remain exactly the same.

9.8 Oracle Database Adapter Use Cases

This describes the Oracle Database Adapter and Oracle Database Adapter - stored procedures use cases. This section includes the following topics: ■ Section 9.8.1, Use Cases for Oracle Database Adapter ■ Section 9.8.2, Use Cases for Oracle Database Adapter - Stored Procedures

9.8.1 Use Cases for Oracle Database Adapter

To obtain Oracle Database Adapter use cases, access the Oracle SOA Sample Code site, and select the Adapters tab. Table 9–20 shows the Oracle Database Adapter samples that are provided with Oracle BPEL PM, and Mediator. Table 9–20 Oracle Database Adapter Use Cases Tutorial Name Description Delete Illustrates the outbound delete operation of the Oracle Database Adapter. An XML record is passed to the operation and the row in the database with the same primary key is deleted. File2Table Illustrates the use of an input a native CSV data file defined in a custom format. The input file is a purchase order, which the file adapter processes and publishes as an XML message to the FIle2Table BPEL process. The message is transformed to another purchase order format and routed to an invoke activity. Insert Illustrates the outbound insert operation of the Oracle Database Adapter. An XML record is passed to the operation and inserted into the database as relational data. In JDeveloper BPEL Designer, Merge Insert or Update is provided. InsertWithCatch Illustrates the extra steps based on the Insert tutorial needed to add fault handling to your BPEL process.