Finding the Compromise – the Adapter Framework - Applied SOA Patterns on the Oracle Platform - page 420

private String errorCode;
private String errorMessage;
private String result;
...
Steps 2 to 4 are related to the standard EJB implementation and DB handling in
Java. For all the necessary details for implementation, you will find in Oracle
documentation and tutorials at http://docs.oracle.com/javase/tutorial/jdbc/basics/
sqldatasources.html .
5. Now, as we have all executable modules, we need to address the inbound message
structure as a carrier and provider of our inbound parameters. As already men-
tioned, we will use our standard message container CTU Message, and all Pro-
tocol Adapter details will be injected into the payload from the Execution Plan.
Adapter-specific parameters, injected from EP are highlighted in the following
example. As you can see from the ESR DB schema presented in the previous
chapter, values for these parameters are taken from the MEP and Endpoint table,
related to the application, action as a TP in our service composition:
<AdapterMessage>
<endpoint>{JNDI name of DB connection}</endpoint>
<protocol>{DB}</protocol>
<payload>
<SQLStatements>
<Sql>SQL Statement 1</Sql>
<Sql>SQL Statement 2</Sql>
<!— ....->
<Sql>SQL Statement N</Sql>
</SQLStatements>
</payload>
</AdapterMessage>
Now, with actual workers (executable modules, XQuery, and Java), and input and
output parameter structures, we can proceed with the assembly of our DB pro-
tocol Adapter as a Service Proxy.
6. Let's return to our Generic Adapter implementation from Chapter 4 , From Tradi-
tional Integration to Composition - Enterprise Business Services and look again
at Operate function. It invokes Facade (actual dispatcher) using dynamic XQuery-
and DB-related part and is presented as seen in the following code snippet. Now