WSO2 ESB by default stores configuration changes to the integrated registry. This enables the WSO2 ESB to load the exact configuration at the next start of the server. If the user wishes to load the configuration from file system instead from the registry, however, he/she may do it using the following option when starting the WSO2 ESB server. Note: This will overwrite the existing registry configuration.
The configuration will be loaded from the synapse.xml file that you find inside $ESB_HOME/conf.
Log in to the Management Console and click on Synapse menu on the left hand side. This will show the entire configuration and there you will find the option to save the configuration. The configuration will be saved to the synapse.xml file that you find inside $ESB_HOME/conf.
See the documentation to see how to write a custom meditor.There are two ways to deploy a custom mediatror.
First method is to convert your mediator into an OSGi bundle and put the backend code into $esbhome/webapps/ROOT/WEB-INF/plugins/server and put into $esbhome/webapps/ROOT/WEB-INF/plugins/console if you have UI for your mediator and into $esbhome/webapps/ROOT/WEB-INF/plugins/common if your mediator have common parts in back end and front end components. Refer to see how you can convert a non-OSGi jar into an OSGi bundle.
Second method is to put your mediator jar(non OSGi jar) into $esbhome/repository/components/mediators and the WSO2 esb will convert it into an OSGi bundle.
See the documentation to see how to write a custom task. Put your non-OSGi task jar into $esbhome/repository/components/lib directory. WSO2 ESB will automatically deploy your custom task.
Yes, it does with both.
Yes, it does.
You need to write a class implementing the org.apache.synapse.registry.Registry interface to intergrate the third party registry to WSO2 ESB.
Once you have service hosting component installed you can have this feature.
WSO2 ESB has a JMS transport wich support JTA.
Yes. WSO2 ESB are known to be deployed on following application servers.
Have a look at the web app deployment guide to see how you can deploy WSO2 ESB on following application servers.
Edit the following section of the $ESB_HOME/conf/axis2.xml to include proper values for an HTTP proxy server configuration.
<transportSender name="http" class="org.apache.synapse.transport.nhttp.HttpCoreNIOSender"> <parameter name="non-blocking" locked="false">true</parameter> <parameter name="warnOnHTTP500" locked="false">*</parameter> <parameter name="http.proxyHost" locked="false">localhost</parameter> <parameter name="http.proxyPort" locked="false">3128</parameter> <parameter name="http.nonProxyHosts" locked="false">localhost|moon|sun</parameter> </transportSender>
Specify the transport.jms.ReplyDestination property in the endpoint configuration for your JMS endpoint. See the following sample configuration.
<address uri="jms:/someService? transport.jms.ConnectionFactoryJNDIName=someConnectionfactory& java.naming.factory.initial=someInitialContextFactory&transport.jms.ReplyDestination=replyQueue"/>
If you are using a proxy service then you can specify the reply desitination as a parameter in the proxy service configuration as well. Use the following parameter in your configuration.