Page Comparison

...

The service bus samples use several sample clients, configurations and sample back-end services in order to explain different use cases. The diagram below depicts the interaction between the sample clients, WSO2 Enterprise Integrator and the services at a high level. The clients are able to send SOAP/REST or POX messages over transports such as HTTP/HTTPS or JMS with WS-Addressing, or WS-Security. They can send binary optimized content using MTOM, SwA, binary or plain text JMS messages. After mediation through WSO2 Enterprise Integrator, the requests are passed over to sample services.

Image RemovedImage Added

...

Deploying samples in WSO2 EI

To start WSO2 Enterprise Integrator with a selected service bus sample configuration

1. Open WSO2 Integration Studio.
2. Copy the sample configuration from the samples documentation into the source view of the WSO2 Integration Studio project files.
3. Start the server.

...

Deploying sample back-end services

...

1. Open a command prompt (or a shell in Linux) and go to the required sample folder in the <EI_HOME>/samples/axis2Server/src directory.

2. Run ant from the selected sample directory.
   
   For example, to build and deploy SimpleStockQuoteService, run the ant command from the <EI_HOME>/samples/axis2Server/src/SimpleStockQuoteService directory, as follows:

   Code Block
   user@host:/tmp/wso2ei-6.1.1/samples/axis2Server/src/SimpleStockQuoteService$ ant Buildfile: build.xml ... build-service: .... [jar] Building jar: /tmp/wso2ei-6.06.0/samples/axis2Server/repository/services/SimpleStockQuoteService.aar BUILD SUCCESSFUL Total time: 1 second

3. Next, you need to start the Axis2 server. 

...

Configuring WSO2 Enterprise Integrator to use the TCP transport

To enable the TCP transport /wiki/spaces/EI6xx/pages/49613826 for samples

• Edit the <EI_HOME>/conf/axis2/axis2.xml file and add the transport receiver configuration as well as the sender configuration as follows:

...

Configuring WSO2 Enterprise Integrator to use the UDP transport

To enable the UDP transport /wiki/spaces/EI6xx/pages/49613828 for samples

• Edit the <EI_HOME>/conf/axis2/axis2.xml file and add the transport configuration as follows:

...

Anchor
Configuring the ESB for Script Mediator Support Configuring the ESB for Script Mediator Support

Configuring WSO2 Enterprise Integrator for script mediator support

The Script mediator /wiki/spaces/EI6xx/pages/49612694 is a Synapse extension. Therefore, pre-requisites for all BSF supported scripting languages may not be bundled by default with the WSO2 Enterprise Integrator distribution. Before you use some of the script mediators, you need to manually add the required JAR files to the <EI_HOME>/dropins  directory, and optionally perform other installation tasks as required by the individual scripting language. The following section describes this in detail.

...

Install the JRuby engine for mediation. This is available in the WSO2 P2 repository as a feature (WSO2 Carbon - JRuby Engine for Mediation). See the instructions on how to install features in WSO2 EI/wiki/spaces/EI6xx/pages/49611927.

Alternatively, you can download and install the JRuby engine manually: Download the jruby-complete-1.3.0.wso2v1.jar file from the WSO2 P2 repository and copy it to the <EI_HOME>/dropins directory.

...