JMETER: how to exclude proxy - web-services

I've a web service built on WSO02 that run in a virtual machine running on my laptop.
My laptop IP: 10.118.xx.yyy
My web service wsdl: http://192.168.zz.kkk/wso001/services/OperCupPrepareProxy?wsdl (NOTE: 192.168.29.128 is the IP of my WSO2 ESB on my virtual machine)
I can invoke my web service using SOAP UI running directly on my laptop (i.e NOT running in the virtual machine ...), with NO proxy setting and all it's working right
Now I'd like to test my web service using JMeter running directly on my laptop (i.e NOT running in the virtual machine ...), and invoking the web service that run inside the virtual machine with WSO2.
JMETER respond ....
Response code: 500
Response message: Internal Server Error
<faultstring>The endpoint reference (EPR) for the Operation not found is /wso001/services/OperCupPrepareService?wsdl and the WSA Action = null. If this EPR was previously reachable, please contact the server administrator.</faultstring>
How can I set my JMETER to invoke my web service?
Thank in advance
Cesare

Related

Identifying dynamic host and port for ATG Web Service created through Create Web Service Wizard

I am using ATG 10.2 with Weblogic server. I have created a Repository web service (getRepositoryItem) using the Web Services Wizard through dyn admin. I left the host and port empty during the EAR creation. My service is up with the EAR now, but according to the documentation for ATG web services, it says the host and port would be provided on run time. I have not provided any security setting for the webservice but it shows me a 403 if I try to hit the context for the servlet for the service.
I am struggling to access the web service. In the Manage Web services through dyn admin I see my WebApp deployed. But its Instance Running and Registered is displayed as false.
Documentation tells that if the service has been executed Instance Running and Registered displays as true.
Could somebody please help in answering, How to access the web service?
You can use the url as follows it will work. I just had to use the name twice.
http://host:port/serviceName/serviceName?WSDL

org.apache.axis2.AxisFault: unknown on connecting to web service from client

I am running into 'org.apache.axis2.AxisFault: unknown' exceptions when connecting to a web service from client stub. This is an axis 2 web service. Client and server side stubs were generated by using WSDL2Java. I used the below links to embed or integrate my web service into an existing web application.
http://wso2.org/library/90
http://www.developer.com/services/article.php/3777111/Embedding-Apache-Axis2-into-Existing-Applications.htm
So, I am not using axis 2 admin console. I verified the web service from server side, I was able to view the wsdl and web service is up and running.
I did not see any activity/error/message in the server side log when the exception happens. I am not sure how to debug this further. Any pointers to investigate this issue is highly appreciated.

mule versioning on web service

I have the same mule webservice application with 2 different versions deployed on the same mule server. Let's call it MuleApp.1.0 and MuleApp.1.1. The flow is as simple as the example of webservice flow on mulesoft website. Their wsdl urls are different as:
http://www.myhost.com:25101/MuleApp.1.0/Service?wsdl
http://www.myhost.com:25101/MuleApp.1.1/Service?wsdl
Both of them are working as expected when the other is not deploying on the mule server. The issue happens when I having both of them deployed on the same mule server like what I used to do in WebLogic. Now I am able to access MuleApp.1.1, but when I tried to access MuleApp.1.0, I got the error as below
07-Mar-2013:14:52:57.142 VWILVM3667 [MuleApp.1.1].connector.http.mule.default.receiver.03
WARN org.mule.transport.http.HttpMessageReceiver NA
No receiver found with secondary lookup on connector: connector.http.mule.default with URI key: http://www.myhost.com:25101/MuleApp.1.0/Service
This is supposed to be a very common versionning case. What did I miss in my config?
You can't have two different applications sharing the same HTTP port in the same Mule instance.
So what probably happens is that MuleApp.1.0 doesn't deploy properly (check the logs), which is why there is no endpoint listening on /MuleApp.1.0.
Either:
Use a different port in the two apps,
Put both flows in a single app.
Create a frontal app that listens on port 25101 and both /MuleApp.1.0 and /MuleApp.1.1 paths and that dispatches requests to MuleApp.1.0 and MuleApp.1.1 on private ports (say 25102 and 25103).
I finally deployed my application on tomcat, and replaced http inbound endpoint with servlet inbound endpoint. I configure the web.xml with servlet class org.mule.transport.servlet.MuleReceiverServlet. Now I am able to deploy multiple applications on the same port.

BPEL: how to solve "end point reference not available..."error

I am performing Web Services Orchestration with BPEL, using Netbeans 6.7.1 and Glassfish server. In my simple BPEL process, I have a sequence of receive->assign->invoke->assign->reply activities, where the invoke is a synchronous one to an operation on a remote web-service (from http://www.webservicex.net). I have successfully deployed my service as a JBI module (in a composite application) and when I try to test it using some input values for the input message of the operation I get the following error message:
....
Caused by: BPJBI-6018: EndPoint Reference is not available from the JBI corresponding to the service name {http://enterprise.netbeans.org/bpel/SimpleInvocation/simpleInvocation}plGlobalWeather and endpoint name GlobalWeatherSoapRole_partnerRole
SimpleInvocation is my BPEL process and GlobalWeatherSoap is the portType in the remote WDSL of the remote service for which the operation I wanted to invoke is defined.
Does anyone have any idea how I can solve this?
It most likely that you do not have connection from Glassfish server to that webservuce. You can login to host where your Glassfish server is runnig and do a telnet to www.webservicex.net on port 80. This will confirm if you have connectivity or not.

The request failed with HTTP Status 403: Forbidden when calling a web service

I have a problem when calling a method from an external web service.
The error returned is as follows:
The request failed with HTTP Status 403
My application is deployed using ClickOnce technology. The strange thing is that when I call service (test the code) on my development machine and additionally in test environment (IIS 6, Windows 2003 Server) everything is fine.
Unfortunately when application is in production environment (Windows 2003 Server, IIS 6) the error is returned.
I don't use a service reference to call a web service, instead I use a proxy class generated from wsdl.exe application. Can someone please help me.
EDIT:
I noticed that I can't even access wsdl file using web browser from that production server. This production server is also in different domain.
I found the solution of my problem. It seems that the company that owns the external web service has some kind of access list with IP addresses allowed to access this web service