our supplier programs for us a webservice which is reachable over the www. Now I like to consum this webservice in a Lotus Notes Database. I import the wsdl file in the Domino Design an developed two buttons in a form to consum the webservice. The first button start the WebService over the Notes Client, the second button start the WebService over the Domino Server.
Now my problems start, when I consume the Web Service over the Client i get an error:
Web-Service AddPortType, Methode add - Fehler Fehler beim Verbindungsaufbau zu 'xxxproxy.xxx.xxx' auf Port '3128', SSL Fehlerhaftes Peer-Zertifikat. Verbindung wurde abgelehnt.
When I consume the Web Service over the Server, the Server get an error:
14.03.2016 12:38:53 Agent 'add' error: Web Service AddPortType method add error Error connecting to 'xxx.xx-xxx.de' on port '443', The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.
First of all I decide to solve the Problem on the Server, because I think it's easyer to solve one Problem on one server as to solve one problem one many many clients.
The webservice must be reachable because, I can open it in the browser, an when I consum it over the Client, it looks like the connection isn't the problem.
In our network we have an proxyserver between the Domino Server and the Webservice.
So may the connection between domino server and Proxy is the Problem. I try the configur this proxy server in the server document in the names.nsf.
Proxy-Konfiguration
HTTP-Proxy:http://xxx.xx.xx:3128
FTP-Proxy:http://
Gopher-Proxy:http://
SSL-Sicherheits-Proxy:http://
HTTP-Tunnel-Proxy:http://
SOCKS-Proxy:Kein Proxy für folgende Hosts und Domänen:
But this change anything, the error message is still the same.
Did anyone can solve my problem.
As SSL is involved, I had some issues running Java Agents getting content from https sites because of too strong certificates and disabled SSL.
Public sites nowadays use SHA-2 and TLS. But the java core on Domino do not seem to fully support this.
Related
Suppose I have an internet facing application. The architecture would be like I have an application server i.e, the browser and the application talks to each other, the application server in turn talks to the web service provider to fetch the service. The calls between my application (not from the browser) and the web services provider is SOAP. The web services server in turn talks to my real backend server to get the transactions done. Now my doubt here is, since the communication between my application server and web services server is internal/intra, only my application server is facing the internet, is my application safe. What could be the possible attack surface. In this case, I do not need to disclose my wsdl to internet. There is no mutual trust between any of my servers and there is no source validation. Is my application secure since wsdl is not disclosed and the only the app-server is facing internet.
please pardon my style of narrating.
Even if your WSDL is not revealed, an intruder may guest it.You can encrypt all the soap call Encrypting SOAP Messages.
I have been testing WCF and WWS services, both my own and the SortService by Mykolad Dudar.
First the WCF version is created, and then wsutil is used for the WWS version.
Both the WCF and WWS services are working fine if the server and client run on the same machine. However, the WWS server is not responding if the server and client are on different machines. The WCF version works fine.
The binding is wshttp and security is set to ’None’. No firewalls or anti virus programs running.
This is the error message I get on the client calling the WWS:
Error: There was no endpoint listening at http://10.100.81.218:8080/SortService
that could accept the message. This is often caused by an incorrect address or S
OAP action. See InnerException, if present, for more details.
System.Net.WebException: The remote server returned an error: (400) Bad Request.
The InnerException is empty.
I’m sure I’m missing something, can anyone please help me out?
Got it working. In case anyone else encounters the same problem, here is how:
Turns out that using ‘localhost’ in the web service url was the problem (on the server). Using the machine IP address instead, solved the problem.
Using ‘localhost’ for the WCF service worked fine, so there is a difference between WCF and WWS on this point.
I'm trying to figure out how to forward web service requests from the web server to a remote application server through jms.
In my architecture there are web services client which communicate with some web server (Tomcat) which needs to forward the request to be executed on a remote application server and at the end get the result and push it back to the web service client.
Something like:
Web Service Client <-> HTTP <-> Tomcat <-> JMS <-> Application Server.
I want to use jax-ws so my methods will be called automatically in the application server.
Although I've expected this will be common approach, I didn't find any examples.
I would appreciate if someone can provide some links or tips on how such a configuration can be built.
Currently I'm using Metro but any other solution is valid as well.
Another aspect which I'm interested in, is whether I can use the fast-infoset over JMS to increase performance.
Thanks in advance,
Avner
you can try wso2MB as a JMS provider ...Check following links, would be useful
[1]http://wso2.org/library/message-broker
[2]http://pzf.fremantle.org/2011/04/introduction-to-wso2-message-broker_05.html
One option to solve it is using Apache Camel.
Then you can configure such a thing with an XML configuration file.
I've a simple jax-ws web service that on localhost works fine with the clients, but now I want to publish the web service on a public ip, so the clients can interact with it through wan network instead lan network.
I signed to no-ip dns service provider and defined my host like "myname.no-ip.info".
In my code i start the service in this way:
Endpoint.publish("http://localhost:8080/baseStationProvider", new BaseStationProvider());
and the browser at http://myname.no-ip.info:8080/baseStationProvider#wsdl doesn't show the wsdl.
If i start the service in this way:
Endpoint.publish("http://myname.no-ip.info/baseStationProvider", new BaseStationProvider());
compiling the code, it raise this exception:
Server Runtime Error: java.net.SocketException: Unresolved address
Any idea to problem and/or how to do what i need?
thanks in advance
This seems likely to do with routing and firewalls as opposed to web service publication etc. Ignoring the web-service aspect, can you even reach your server when you use this in your browser:
http://myname.no-ip.info:8080/
?
Which should look the same as
http://localhost:8080/
If not, then it is probably DNS/Routing/Firewalls that you need to check. Diagnostics that will help there are:
1) can the machine you are testing on resolve the DNS name mynam.no-ip.info? nslookup, ping, traceroute/tracert
2) is there a firewall blocking port 8080 from reaching local host? If the route from the internet to your host hits a firewall (which it will) that firewall will have to forward the request.
Good luck.
I am trying to call a web service from a BizTalk (2006) orchestration.
Having got the hang of the basics, I have been following this tutorial (page 74 onwards) in which i have a web reference to an external web service (I am using this web service instead of the one in the tutorial), I have my web message in a Send component, and have set up the request / response ports for the web service call.
I'm fairly sure that eveything is set up correctly, but my orchestration fails to call the web service with the following error:
The adapter failed to transmit the message going to send port
"My_Order_Processor.Orchestration-CurrencyConvertPort-36c122f41c5596ae"
with URL "http://www.webservicex/net/CurrencyConvertor.asmx.
WebException: Unable to connect to the remote server.
SocketException: An existing connection was forcibly
closed by the remote host 209.162.186.60:80
The IP 209.162.186.60 is the address for the web service I am trying to connect to. I am trying to narrow down the reasons for the error, e.g.:
Firewall issues
Proxy server issues (I don't know how to configure BizTalk to use a proxy server)
Something else
The BizTalk server can ping the web service, I can access the internet (through IE), I can add the WebReference to the project successfully (meaning at least the orchestration designer can access the web service okay). I have also tried a different web service, with the same result.
Any ideas on finding out why this is happening or how to find out more info? (I'm new to BizTalk)
I've seen this veru vague error before for many different reasons. Two suggestions.
Download something like NetMon and watch what is going on on the wire.
Turn off chunked encoding. For some reason, many web services don't handle this well.
Let us know what you find out.
Could this not be an authentication issue? Check that you can connect to the webservice using the Bts credentials.
This turned out to be a proxy issue.
By navigating to Biz Talk Group -> Platform Settings -> Adapters -> SOAP, I was able to configure the BizTalk server host's SOAP adapter (which is what the web service call uses to make the call) to use our company proxy server correctly. Double click the 'send' SOAP adapter, go to Properties under adapter name.