Hi friends,
I just created this technique because I was in a POC (Prov
e of Concept) and needed to call a WS (Web Service) but t
he WS must wait the scenario execution until the end and,
too, receives a return (OK or Not OK).
As is from common knowledge , calls the ODI web service fo
r scenario execution only starts a scenario but doesn’t “w
ait” the scenario execution. The response just indicates tha
t the process was started, not if it finish with or withou
t error.
This behavior is absolutely normal once a scenario could tak
e hours to finish and WS aren’t done for that.
However, as a programmer, it ‘s always good to break the
rules!
What I’m about to show is very simple and easy. The techn
ique was designed to work with Oracle.
Recipe:
Ingredients
1 ODI scenario (from any developed process)
1 Oracle Database with the following packages compiled :
http://www.oracle.com/technology/tech/java/jsp/pdf/calling_shell_co
mmands_from_plsql_1.1.pdf
1 ”Temporary” table created just for be called for a WS .
This table should have the same number of columns as the
ODI scenario parameters or at least one column of any dat
atype if the scenario doesn’t receive parameters.
1 Trigger in the temporary table
How to do:
1º) Publish a web service to insert data into this temporar
y table (Called Temp_Table from now forward)
You can do that from ODI using a SKM (Service knowledge Mo
dule)
2º) Be sure about to have followed all instructions from Or
acle document (link at ingredients)
评论0