I am tying to call MDM RMI service with Spring Boot(1.4.2) and Liberty profile beta.When I make a call to RMI service getting javax.naming.NameNotFoundException: Intermediate context does not exist.But same application is working fine in Websphere application server 8.5.
Liberty profile won't support RMI call or am I missing any configuration.I have ebanbled below features in my server.xml.
webProfile-7.0
localConnector-1.0
I can able to make remote EJB RMI call with Liberty 16.0.0.3.
Basically we need certain EJB features enabled in Liberty in order to make Remote EJB call.
Download Liberty Full platform from below link.
https://developer.ibm.com/wasdev/downloads/#asset/runtimes-wlp-javaee7
Add below features in server.xml.By default this will be part of Full platform Liberty.
<feature>javaee-7.0</feature>
<feature>ejbRemote-3.2</feature>
<feature>ejbHome-3.2</feature>
<feature>ejb-3.2</feature>
Related
Does WebSphere liberty profile 8.5.5 have RMI or SOAP port?
If so how to config with server.xml and connect via java client remotely.
Liberty supports RMI over IIOP as of version 8.5.5.6. Information on how to configure it is available here: https://www.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.wlp.doc/ae/rwlp_config_iiopEndpoint.html
SOAP is available over HTTP/HTTPS ports and are configured using httpEndpoints. There is a useful tutorial for configuring SOAP/HTTP and developing a client/server application that uses it here:
https://developer.ibm.com/wasdev/docs/sample_ejbwebservicessample/
Hope this helps, Andy
I am trying to implement an OSGI based JAX-WS WebService client on WebSphere Application Server(8.5.5). I created a web project in my RAD (Rational Application Developer) workbench and added the programming model as osgi.
After that I tried to create the webservice client from the available wsdl.
But I am getting the following error " The IBM WebSphere JAX-WS Web service runtime does not support Client projects with the OSGi Bundle facet."
Are you using JAX-WS on WebSphere Application Server traditional (i.e. not the Liberty Profile)? If so, then traditional does not support JAX-WS in OSGi Applications. The Liberty profile does support JAX-WS.
If not, then this could be a tools check that's no longer valid. I know the tools used to prevent you doing this when JAX-WS was not supported on traditional or Liberty. You could try using the latest WebSphere Developer tools from the Ecilpse Marketplace or https://wasdev.net/repo to create a simple test project to see if you hit the same problem.
I hope this helps.
Regards, Graham.
I have a server running on tomcat exposing Spring services using HttpInvoker.
I have exposed the methods of 5 services using HTTPInvoker.
This works very well.
The spring configuration is described in a file named remoting-servlet.xml; and the remoting servlet (DispatcherServlet) is described in the web.xml.
I now have an additional need to expose one additional service using JAX-WS this time (I will have C# clients).
I will use Spring support to JAX-WS.
I have the option to use the default deployment, or to use JAX-WS RI's to deploy this additional service to the same server as the remoting servlet.
I would prefer this last solution, because I would have only one server providing the remote services (whether they are web services or httpinvokers).
My question is: is this possible?
I think that I can I put the 2 servlets on the same port. But my issue is that it seems to me that I will have to provide 2 different application contexts. One for the DispatcherServlet, and one for the WSSpringServlet.
Is that correct?
Is it possible to put the WSSpringServlet context definition to the same file as the one for the httpinvokers (remoting-servlet.xml)?
Many thanks
Gilles
We are implementing a web service on WCF. The service is consumed by Oracle weblogic. Communication is done through mutual authentication over HTTPS. The only way the communication is successful is when JSSE is enabled on Weblogic server. However this makes other web services incompatible. Is there a way to enable JSSE on the web service level instead of the server level?
In other words, we need the Weblogic server to enable JSSE only for this specific web service.
looks to me you need tomcat or some other servlet engine for the web part.
what about data access part using hibernate and jms? Thanks.
No, you don't need an application server, you can see Spring as a proprietary, modular application server implementation / adapter. But you still need an a servlet container.
Data access part: you can use hibernate and some standalone connection pool
jms: Spring is not a JMS provider, but it nicely integrates POJOs with any JMS provider
Spring also has comprehensive transactions support
Finally you have jmx and aop support built-in and easy integration with bean validation, jpa, web services, rmi, jci, task scheduling, caching...
As you can see you can either use certified application server and Java EE stack or built on top of Tomcat and pick Spring modules you need. Sometimes Spring uses standard Java EE APIs (like JPA), more often it builts its own.