WSO2 ESB unable to un-deploy endpoints, localentries with CAR undeployment - deployment

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.

Related

Web service consumer SOAP version is showing error by default

I am trying to configure a SOAP service using web service consumer, as soon as I click on new configuration in the connector configuration, I see SOAP version column is turning into error and when I hover on it, it is showing some tooling related error and when i check my tooling stats in preferences, it shows in running state.
My studio version is 7.11.1
Please let me know how to resolve this issue.
The information is not complete to identify the root cause. Having said that it is possible that the error is happening when the Web Service Consumer connector is trying to download the WSDL if the access is restricted in some way. For example if the server has whitelisted the IPs of authorized clients, or there is an access restriction in your network, or some other permission issue.
In that case you may resolve the issue if you can download the WSDL locally and add it to the application in the src/main/resources folder, and reference it by the file name (with no path) instead of an URL.

Mta application failing to deploy with conflict error

I had deployed the app last on friday and it got deployed successfully.But since, today morning the deployment is not happening at all.It is checking for conflicting process and failing.
I'm doing this from the webide and i'm not able to check what are the conflicting process and how to resolve it.
WebIDE lacks the ability to do proper investigation on deploying apps to SAP Cloud Foundry.
The best way to do this is to install the Cloud Foundry Multi-apps plugin (see this tutorial). This will allow you to use the local terminal to control the deployment (or alternatively use SAP Business Application Studio which already has the commands built in).
Then use the command cf mta-ops to get the list of ongoing operations and cf dmol <operation_id> to download the logs for that operation. cf deploy can be used to abort/retry operations.

Enable Data Service on new WSO2 - ESB installation

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.

Application Can Not Be Deployed on Cloudhub

currently I am working with mule esb in cloud, to achieve this I am using free trial version of Cloudhub. FYI, I am new to cloudhub and right now tring to deploy my mule application there. Unfortunately, everytime I tried to deploy my application, it can not be deployed.
I have tried 2 ways to deploy the apps.
The first one is from the Mule Studio, by following this documentation:
Deploy Apps to Cloudhub From Mule Studio
When I tried that way, I got following error:
I guess it was because of the proxy.
The second way I tried is by deploying it directly from the cloudhub.io, by following this documentation:
Deploying Apps Directly From Cloudhub.io
But, when I check on the deployment section, I found out, that my application is not uploaded. Then I tried to upload it again, update it, and run the application, but it seems that the application still not uploaded and the change I made is not applied.
Here is the error I got:
FYI, before I upload the application to cloudhub, I compressed the application folder into zip file.
How can I solved this problem? Do you think I did something wrong when deploying it? Thanks in advance.
I too faced similar problem, when deploying application in cloud hub, using Mule 3.5. My application inserts Contacts info (FirstName, LastName, Title, Email etc) from CSV file in Salesforce "Contacts" object. With proxy details configured, my application was running fine in local machine but when deployed in cloud hub, I was getting "Unknown host Exception. Root exception in proxy (something similar to this) " exception.
What I did:
I have removed proxy details from Salesforce connector and re-compiled and deployed in cloud hub. When I tested, the contacts from csv file are getting inserted in Salesforce "Contacts" objects.
Note: When Proxy details are removed, it works in cloud hub but fails in local. It seems cloud hub takes care of proxy connection and we don't need to explicitly mention it.
Regards
Ravi Nori
Be sure that you configure your http endpoint like this:
<http:inbound-endpoint host="localhost" port="${http.port}".... />
CloudHub will automatically expand http.port property to the correct value.
To make it work deploying from CloudHub you shouldn't compress your project yourself and upload but make Studio create a deployable archive: Right click on your project and then click export, select 'Anypoint Studio Project to Mule Deployable Archive' under Mule category. That will have Mule ESB application structure and should work in CloudHub.
Check your http global endpoint is like that
or you can give in properties file like http.host=0.0.0.0 http.port=8081
these values you can give directly in cloudhub properties.
From flow you can access like ${http.host} , ${http.port}
First check that domain name is available

Jboss ESB Services on multiple machines

I am very new to jboss esb and trying to learn and configure a new startup project.
The project deals with using ESB as the backbone and multiple applications connecting to it for Intg.
I have gone through each of the examples provided and was able to reach to a certain level, but little confused on few other stuff.
1) Use ESB to be hosted on machine1 (consumer) and process this message (it works).
2) Now the sender and ESB consumer are on 2 different machines. The sender is unable to locate/load the esb consumer.
I believe you might have enough experience working through this, so would you know how do I get this resolved.
you can reach out to me on hitjain_83#hotmail.com
Your help would be appreciated!!!
This will probably help:
https://community.jboss.org/thread/146623