The views expressed on this blog are my own and do not necessarily reflect the views of any Organisations owning these products.I keep on doing R & D with different products in and around Middle ware stack and these posts are result of that.Most of the post are result of my own experiments or ideas taken from other blogs .If in any case You feel content is not right you can comment to remove that post. This blog uses the default features,cookies of blogspot.com
Tuesday, January 22, 2013
How to change the time format in SOA
Tuesday, January 08, 2013
How to pass Batch ID in ODI Call from SOAP UI
Create a project variable.
DAta type -alphanumeric
No history
default value -1
In refreshing page get the sequence value
select XX_WSH_SHIPMENT_GDW_STG_S2.NEXTVAL from dual
Now the logic is we can call the process from SOAP UI or otherwise it should be put in scheduler
So for this to achieve we first create the variable BATCH_ID as defined earlier
Then in the package we first declare then evaluate it .
We compare if it is greater than zero .
If yes then directly complete the interface
however if it is less than zero then go to another step where again drag and drop the BATCH_ID as refresh variable.
This way you can both call the service from SOAP ui and as well as you can put it on scheduler.
In case of scheduler default value will be always -1 hence it will refresh the value
however in case of ODI call the passed value will be always greater than 0 hence refresh step will be skipped and the value passed from SOAP ui will be used as a BATCH _ID
DAta type -alphanumeric
No history
default value -1
In refreshing page get the sequence value
select XX_WSH_SHIPMENT_GDW_STG_S2.NEXTVAL from dual
Now the logic is we can call the process from SOAP UI or otherwise it should be put in scheduler
So for this to achieve we first create the variable BATCH_ID as defined earlier
Then in the package we first declare then evaluate it .
We compare if it is greater than zero .
If yes then directly complete the interface
however if it is less than zero then go to another step where again drag and drop the BATCH_ID as refresh variable.
This way you can both call the service from SOAP ui and as well as you can put it on scheduler.
In case of scheduler default value will be always -1 hence it will refresh the value
however in case of ODI call the passed value will be always greater than 0 hence refresh step will be skipped and the value passed from SOAP ui will be used as a BATCH _ID
Calling ODI SCenario from SOAP UI
When calling ODI Scenario from SOAP UI make sure that you are passing the correct user id password which is there for ODI console.
If you are passing any input variable it should be passed in Variable.
Name should be poject name.variable name
and value should contain the value.
One important thing is there is gap in the project name make sure you are replacing it with underscore _ while passing the variable in odi call.