Database Reference
In-Depth Information
XXCU_COMMON_UTIL_XML.freedocument
(v_inXmlDOM);XXCU_COMMON_UTIL.closetmpclob (olob);
So, the task was done in nine simple steps. Logically, the number of parsers will be equal
to the number of inbound messages, but as long as all of them (we assume) are in canonic-
al form, their number will be quite moderate. Again, after message detection and extrac-
tion from the queue, we can apply the transformation to any custom message, but this ap-
proach should be avoided. In general, these exercises for establishing parsers and con-
structors have a very positive effect on internal App organization, expressed as follows:
• The statements-duplicates provided by parallel teams were consolidated and ad-
justed according to the recommended canonical models. Canonical models are fi-
nalized and approved at last.
• All the remaining SQL statements were carefully turned for optimal performance,
and the usage of all clauses such as
DISTINCT
and
UNION
were redesigned.
• All artifacts, required for rule-based processing and any kind of dynamic invoca-
tions were registered in the Service Repository.
• Canonical models, related parsers/constructors, Business Events, and all other
public artifacts from Service Repository were also published on Corporate WIKI,
a "How-To Cookbook" was composed and provided to every developers.
• Checklists from the previously enforced formal delivery acceptance process.
The example will be not complete without a few words about canonical endpoint hand-
ling.
Endpoint handling
RRD Canonical Protocol is JMS/AQ and we expect that all communications will be
queue-based, especially for inbound flows, because that will considerably simplify mes-
sage recognition and parsing, as demonstrated previously. However, as we mentioned
earlier, Oracle Fusion Apps and Oracle DB, in general, are very capable of supporting
practically all common protocols, without the Adapter framework, directly to the Service
Bus, which is service collaboration and decoupling layer. Oracle DB Listener is a HTTP
listener as well, we can easily do the HTTP
POST
/
GET
and construct SOAP messages,
either manually or using OEBS XML Gateway. File operations never were a problem. We
are not sure that doing FTP directly from DB is a good idea from a security standpoint,
but we can do that as well. Practically, as we can call any Java function and wrap it in PL/
SQL, we can do anything. The question is—should we?
Search WWH ::
Custom Search