This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

The topics in this section provide information on how you can use WSO2 Enterprise Integrator Tooling to create various EI artifacts that you can build and deploy to the EI in order to process requests. The tooling functionality is available from the Developer Studio dashboard in Eclipse. 

Getting help in the source view

When working with your EI configurations in the Source view instead of the Design view, you can hover your mouse over any element (such as the definitions tag) to see the syntax of that element. You can also press Ctrl + Space to get suggested auto-completion text.

For example, if you view a proxy service in the Source view, and you remove the / from the <inSequence/> element and press Ctrl + space, the Content Assist appears and lists all the options you can add at this point, including the closing  </inSequence> element.

Creating an ESB Config Project

You can create an ESB Config Project to save all the EI related artifacts such as proxy services, endpoints, sequences, and synapse configurations.

To create an ESB Config Project:

  1. In Eclipse, click the Developer Studio menu and then click Open Dashboard. This opens the Developer Studio Dashboard.

  2. On the Developer Studio Dashboard click ESB Config Project.
  3. If you want to create this project from existing configuration files, select Point to Existing Synapse-configs Folder. Otherwise, leave New ESB Config Project selected. Click Next.
  4. Do the following:
    1. Type a unique name for the project.
    2. If you selected the option to point to an existing Synapse-configs folder in the previous step, click Browse and navigate to the folder containing the configuration files.
    3. Optionally, specify the location where you want to save the project (or leave the default location specified).
    4. Optionally, specify the working set, if any, that you want to include in this project.
  5. A Maven POM file will be generated automatically for this project. If you want to include parent POM information in the file from another project in this workspace, click Next, select the Specify Parent from Workspace check box, and then select the required parent project.
  6. Click Finish.
  7. If you specified a folder with existing configuration files, specify whether you want to open those files now.

The new project has now been created in the workspace. If you browse inside the project, you will see a project structure as follows, with folders created for different resources such as endpoints, inbound endpoints, local entries, message processors, message stores, proxy services, and sequences etc.

Creating an ESB Solution Project

You can create an ESB Solution Project to save all required project files you need for a particular configuration in one go. For example, if you need to create a project that requires an ESB Config‬ project, registry resource‬ project, connector exporter‬ project and composite application project, you can create an ESB Solution Project instead of creating each required project separately.

To create an ESB Solution Project:

  1. In Eclipse, click the Developer Studio menu and then click Open Dashboard. This opens the Developer Studio Dashboard.

  2. On the Developer Studio Dashboard click ESB Solution Project.
  3. Do the following:
    1. Enter a unique name for the project.
    2. Select the projects you want to create and specify names for each project that you selected (or leave the default project names).
    3. Optionally, specify the location where you want to save the project (or leave the default location specified).
    4. Optionally, specify the working set, if any, that you want to include in this project.
      A Maven POM file will be generated automatically for this project.
  4. If you want to include parent POM information in the file from another project in this workspace, click Next, select the Specify Parent from Workspace check box, and then select the required parent project.
  5. Click Finish. The new projects will be created in the workspace. If you browse inside each project, you will see each project structure as follows:

       

Importing a Synapse configuration

A Synapse configuration file contains one or more EI artifacts, such as endpoints and sequences. You can import an existing Synapse configuration to import all its EI artifacts in one step.

Follow the steps below to import an existing Synapse configuration into an EI Config project. 

  1. Open the Developer Studio Dashboard (click Developer Studio > Open Dashboard) and click Synapse in the Enterprise Service Bus area.
  2. Specify the Synapse configuration file by typing its full path name or clicking Browse and navigating to the file.
  3. In the Save Synapse Configuration in field, specify an existing EI Config project in your workspace where you want to save the configuration, or click Create new EI Project to create a new EI Config project and save the Synapse configuration there.
  4. Select the artifacts you want to import.
  5. Click Finish. The artifacts you selected are created in the subfolders of src/main/synapse-config folder under the EI Config project you specified, and the first artifact appears in the editor.

Creating a Smooks configuration artifact

Smooks is an extensible framework for building applications that process data, such as binding data objects and transforming data. To create a Smooks configuration artifact, you must first create a registry resource as described in Creating Governance Registry Artifacts. When creating the registry resource, select the From Existing Template option and select Smooks Configuration as the template.

The smooksconfig.xml file is created. Double-click it in the Project Explorer to open it in the embedded JBoss Smooks editor.
 



Click Input Task, create the data mapping, and save the configuration file. 

Before you can run the Smooks configuration, you must add libraries from the Smooks framework to your registry resources project.

  1. Right-click the registry resources project in the Project Explorer and click Properties.
  2. In the list on the left, click Java Build Path, and then click the Libraries tab.

  3. Click Add Library, click WSO2 Classpath Libraries, and then click Next.
  4. In the WSO2 Classpath Libraries dialog box, click the Smooks tab, click Select All, and click Finish.
  5. In the Properties dialog box, click OK.

All the Smooks-related libraries have been added to the project classpath. You can now run the Smooks configuration file by right-clicking the file and choosing Run As > Smooks Run Configuration. If your Smooks configuration is correct, the console displays the results according to the input model and output model you specified.

You can now add the Smooks configuration artifact to a proxy service or sequence to use it in the EI. To do so, create a proxy service. Drag and drop a Log mediator and a Smooks mediator to the InSequence. Double-click on the Smooks mediator to see the Property view. Click the button at the right hand corner of the Configuration Key field.

The Resource Key Editor dialog box appears. Specify from where you should select the resource file.

Select Workspace option since we have the created Smooks Configuration in our workspace. Browse for the Smooks Configuration file that we have created and click OK.

Now you have successfully referred to the Smooks configuration within your proxy service.

Moving EI artifacts between projects

To move an EI artifact from one project to another, right-click on the artifact (in this instance, Sequence123.xml ), click Move and then select the folder to which you want to move the artifact. It is also possible to simply drag and drop the artifact.

         

 

Deploying the ESB Config project

Once you create all the EI components such as sequences, proxy services, endpoints, local-entries, you can create a Composite Application Project to group them and create a Composite Application Archive. Before creating the CAR file, make sure that the server role is set to EnterpriseServiceBus. 

 

For more information, see Packaging Artifacts into Composite Applications.

  • No labels