Has anyone created VUgen scripts for SOAP over JMS, we need help!!!

[Steve Harris]

We've been attempting to create a script to run a simple test on our
server and failing miserably. Our software engineer provided us with
the message his application expects to receive. Our loadrunner script
sends a message that is very close but is apparently lacking the Mime
version and Content type that our implementation of TIBCO requires.
We have been trying to figure out where this content type is generated
as we imported the wsdl directly off the TIBCO server and loadrunner
created our weblogic script from the Add Service Request option in the
vugenerator. We are complete loadrunner newbies and could really use
any assistance we can receive.

Here is our web_service_call

Action()
{
web_service_call( "StepName=PingURL_102",
"SOAPMethod=PingUrl|PingURLServer|PingURL",
"ResponseParam=response",
"Service=PingUrl",
"JMSSendQueueName=PingURL.Request",
"JMSReceiveQueueName=PingURL.Response",
"ExpectedResponse=SoapResult",
"Mime_Version={string:'1.0'}",
"Content_Type={string:'text/xml; charset='utf-8'}",
"Snapshot=t1330386795.inf",

BEGIN_ARGUMENTS,
"xml:MSMsgHeader="
"<MSMsgHeader>"
// "<build>3</build>"
// "<buildString></buildString>"
// "<CSUnits>feet</CSUnits>"
// "<majorVersion>4</majorVersion>"
// "<minorVersion>1</minorVersion>"
// "<pwd></pwd>"
// "<userID></userID>"
"</MSMsgHeader>",
"xml:PingURL="
"<PingURL></PingURL>",
END_ARGUMENTS,

BEGIN_RESULT,
"MSMsgHeader/build=Param_build",
"MSMsgHeader/buildString=Param_buildString",
"MSMsgHeader/CSUnits=Param_CSUnits",
"MSMsgHeader/majorVersion=Param_majorVersion",
"MSMsgHeader/minorVersion=Param_minorVersion",
"MSMsgHeader/pwd=Param_pwd",
"MSMsgHeader/userID=Param_userID",
"PingURLResponse/PingURLResult=Param_PingURLResult",
"PingURLResponse/PingURLResult/*[1]=Param_ErrorObject",
END_RESULT,
LAST);
return 0;
}

[James Pulley]

" We are complete loadrunner newbies "

Training? Do you have a mentor assigned to work with you? Have you
confirmed the core skills you need for success?

Here is our web_service_call

--
You received this message because you are subscribed to the Google
"LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en

[Load Runito]

for content-type you might want to add a header.

Look for web_add_header on the help.

[manny...@gmail.com]

I would use thw web_custom_request function. Please read up on it, there are so many examples for it.

[kiran_sahoo]

Hi,

Can you try using the soap_request method instead of
Web_Service_Call ?
I believe you have the wsdl file provided to you.

Thanks,
Kiran

[loadrunn...@jamespulley.com]

This is one of the few areas in which I recommend giving HP support a
call. Plan on the turnaround to resolution taking a few days to go
through. The first path will be to establsih general JMS connectivity
from the script, to which support will have you connect to a local dummy
JMS service. Once that is working then it will be a matter of sorting
out the Java Version(s) for your version of LR, the general JMS items in
the classpath and which Tibco specific items you need to have involved as
well.

The "Plan B" path would be to use a Jave Template virtual user with JMS
code for the pushing of your message onto the queue.

From the above you can gather that this has certainly been done, but the
initial path is really rocky to get to working cycle 0.

'Pulley

[Shane (HP)]

Have you looked at any of the jms_* functions available? Also, there
are several good blog posts on the subject if you google 'jms tibco
LoadRunner'. I also think you should look at HP Service Test, which
has excellent support for composite apps and the scripts can be used
by LoadRunner provided you are entitled to the SOA protocol bundle.