In WSO2 ESB (4.7.0), I have added application server feature (4.1.0). My carbon app contains the following artefacts
AxisService (aar)
AxisClientStub (lib)
Mediator (synapse-mediator) that uses the client stub
Error Sequence
Main Sequence (Uses mediator 3)
Out Sequence
REST Api (using the 4,5,6)
When I deploy this CAR file in the ESB, it starts deploying from 3 onwards and cribs that it does not find the client stub library.
What am I missing here?
Developer studio by default, for axis service, capp property is set as capp/ApplicationServer. I changed this to capp/EnterpriseServiceBus. With this change, I am able to deploy my axis services in the ESB thru carbon application
<com.xx.yyy:CCCService:1.1-SNAPSHOT>capp/EnterpriseServiceBus</com.xx.yyy:CCCService:1.1-SNAPSHOT>
Related
I create a client in Domino to consume a web service that works with SOAP 1.2 and has HTTPBinding.
The client generation tool for Domino Designer Web services an error is displayed when trying to generate reporting that the SOAP accepted version is 1.1.
I decided to create the client with CXF framework through tool wsdl2java. In an agent I used these classes to consume the web service, however the below error was displayed. I think it's because of the SOAP version, but I'm not sure.
com.sun.xml.internal.ws.protocol.soap.MUTube getMisUnderstoodHeaders
INFO: Element not understood={http://www.w3.org/2005/08/addressing}Action
Also generated a jar of classes generated by wsdltojava and imported to another agent, but the error below is displayed.
java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=, offset=6
The question is, no way consume a web service with SOAP 1.2 in Domino only supports up to version 1.1?
Thanks a lot!
I don't believe that Domino's web service consumer supports SOAP 1.2 at this time. You might be able to do what you need with an agent though - here's one way: How can I call a SOAP 1.2 Web service from a LotusScript agent?
In fact there is no way to natively consume a web service with soap version 1.2. There are already several requests from IBM to upgrade the SOAP version. What I did, was to develop a new layer through a new web service with the version SOAP 1.1, which internally calls the web service with the SOAP version 1.2;
I am trying to migrate an installation of WSO2 - ESB from an old 2003 server to a new 2012 server. The old server had version 2.0.2 while the new server has version 4.8.1. The application is running and I can log in and browse the system. The problem I have is that it appears to be missing components. For example, on the old server there are a list of services including: Proxy, Data, POJO, Spring, Jar ect..on the new server I only have Proxy service. The main service I only need is the Data service but I have no idea how to get that. I am completely new to Java and this application however my boss wants this up and running as the Data service we had on the old server is designed to pull a data feed from a remote SQL server and push it to another server we have. Please help, I have absolutely no idea how to proceed.
WSO2 has a complete middleware stack and it has many components where each of them has it's own specific functionalities so that users can select according to their requirements without overkill the server with lots of features. In abstract WSO2 ESB do the mediation (proxy), WSO2 Application Server do the service hosting and WSO2 Data Services Server can be use to pull data out from a remote SQL server which you need to engage with.
Also you can install the features of WSO2 Application Server and WSO2 Data Services Server to WSO2 ESB. But it's bit tricky since we may need to add some configuration files in order to work these feature properly.
Scenario to replicate the issue with wso2 esb 4.8.0
create the CAR file by selecting all the proxy services, sequences, endpoints, and local entries.
Deploy the car on to WSO2 ESB with console.
This makes deployment of all the artifacts into server.
Now try to un-deploy the car from the console.
Except endpoints, local-entries, everything will be un-deployed.
Please let us know the way to resolve this issue without server restart.
I think this is a bug in WSO2, if u try same thing from wso2 web management console it shows similar behaviour, As far i have researched on the topic WSO2 by default does not un-deploy the Registry Artifacts like endpoints or local-entries. Every time you re-deploy the CAR file it overwrites the contents of all the registry artifacts.
I am using Eclipse + Oracle Enterprise Pack to write some jax-ws based service. It works fine in my development mode (composed WSDL, generated Weblogic web service stub code, completed the detail, and tested code from client), one by one. But when I moved these services into a public testing server (running WL 12c (12.1.1) the web service handler looks like is single threaded. This does not make sense to me, but from my app log, one service was running and then all other requests had to wait until the first one completed its task.
What had I missed in my stub code or configuration setting (I just used default server setting)? Any suggestion is appreciated.
Alan
I am using Jboss5.1 and I have a EAR1 deployed which has a EJB3 component implemented using #Stateless annotation and the same EJB is also exposed as webservice using the annotation #webservice.
I want to check through a EJB service/management service bean(Packaged in another EAR2) from the start of deployment to un-deployment of EAR1 PERIODICALLY, if the EJB and Webservice is deployed and running properly and working normally and is not in deadlock/non responsive state.
I have looked into JMX and I am able to get notifications of create and destroy for EJB as well as webservice, but how to check periodically whether the EJB and webservice is working normally and is not in deadlock/non responsive state?
Also how to monitor Jboss ESB services?
Is the JMX is the only way or does jboss provides any other API's to do monitoring how about JBOSS MONITORING
Thanks in advance if you are looking at this.
Especially JBoss AS5.x is using the so called profile service (PS) as the main way to interact with the server. Unfortunately the PS is not JMX-based and on the other side you don't see all EJBs in the Platform MBean server.
RHQ has a plugin to monitor EJB instances inside AS5 as well as for other resource types like JBoss ESB or Apache Tomcat and is able to determine the availability of EJBs.
but how to check periodically whether the EJB and webservice is
working normally and is not in deadlock/non responsive state?
This is usually something that you can (only)(*) determine by hitting the relevant beans/methods and evaluating the outcome.
*) It may be possible to determine a bean in a deadlocked state by requesting a heap dump and looking for deadlocked periodically.