ODI Using Axis2 Passing Multiple Variables

Question

Hi,
We are using Axis2 in between a .Net web app to pass four parameters to an ODI scenario. I am using SOAPUI to remove the web app from the testing process. Everything is working well except for the fact that only the last variable in the XML is ever read and stored in the ODI scenario execution. Below is a sample of our XML variable setup. In the ODI scenario we declare each of the four variables in the first four steps of the package (which I read somewhere was the proper setup). Regardless, if I remove the last two variable in the XML then only the second variable "v_HFMI_Fiscal_Year" is stored properly and the first is ignored. Furthermore, if I remove the last variable then the third is stored properly and the first two are ignored. Can anyone help?
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:odi="xmlns.oracle.com/odi/OdiInvoke/">
<soapenv:Header/>
<soapenv:Body>
<odi:invokeScenarioRequest>
<odi:Variables>
<odi:Name>HFMI_PROJECT.v_HFMI_UserID</odi:Name>
<odi:Value>CORMSBY</odi:Value>
<odi:Name>HFMI_PROJECT.v_HFMI_Fiscal_Year</odi:Name>
<odi:Value>2008</odi:Value>
<odi:Name>HFMI_PROJECT.v_HFMI_Fiscal_Period</odi:Name>
<odi:Value>06</odi:Value>
<odi:Name>HFMI_PROJECT.v_HFMI_Submission_Type</odi:Name>
<odi:Value>BPY2</odi:Value>
</odi:Variables>
</odi:Command>
</odi:invokeScenarioRequest>
</soapenv:Body>
</soapenv:Envelope>

Answer 1

Rhian80 wrote:
I would use Applescript to do everything but I'm the only Apple person on staff and if I get hit by a beer truck tomorrow, someone has to know how to do this stuff. I figure they have better odds of finding someone on staff who knows UNIX.
Another option may be to write the whole thing as a shell script and use Pashua or Platypus to create a GUI around it.
One warning about creating and running shell scripts from AppleScript: make sure you correctly escape any user-supplied values when assembling the shell script. The easiest way to do this is by using the text object's 'quoted form' property, like this:
do shell script "/Users/labadmin/Desktop/labbuild.sh " & quoted form of RoomNumber & space & quoted form of StationNumber
or, if your shell script expects the room and station numbers to be supplied as a single argument rather than two separate ones:
do shell script "/Users/labadmin/Desktop/labbuild.sh " & quoted form of (RoomNumber & StationNumber)
If you forget to do this, Very Bad Things can easily happen when the inputted text contains spaces or other 'special' characters, either by accident or intent, e.g.:
set user_input to "; say Oops;"
do shell script "echo My name is " & user_input
Do a web search for 'injection attack' for more on the perils of failing to sanitize your inputs properly.
Incidentally, the latest edition of Apress's Learn AppleScript, which I co-wrote, has an entire chapter devoted to combining AppleScript and Unix shell scripting, if you're new to this subject./self-plug