Clicking Next brings you to the JBoss ESB Project wizard page where a project name, ESB version and target JBoss Runtime are to be specified. Specify, for example, helloworld as a Project name and accept the default ESB version.

Figure 2.2. JBoss ESB Project wizard

Clicking Next brings you to the ESB facet installation page where you can specify Java Source Directory and ESB Content Directory. ESB Content Directory is a folder that contains the most of artifacts that an ESB archive needs. You also can configure ESB libraries to the project by selecting a ESB runtime using one of the options:,

1. Use Server Supplied ESB Runtime

2. Select a ESB runtime from the JBoss ESB runtime list predefined in the preferences

If you choose the first option, make sure that the project has the Target JBoss Runtime set and this runtime has a ESB runtime installed.

Figure 2.3. Install ESB facet step

Click Finish and a ESB project with the default jboss-esb.xml will be created.

Figure 2.4. The generated ESB project structure

2.3. Creating ESB Project using JBoss Tools Project Examples Wizard

JBoss Tools provides a Project Example wizard that is an easy way for users to create some kinds of projects to be used as examples with some predefined structure. Let's start creating a ESB project using this wizard.

Before creating a ESB project example create JBoss Runtime with name JBoss 4.2 Runtime, it will be used by your ESB project example.

Select File >New > Others , in the main menu bar or context menu for selected project and then JBoss Tools > Project Examples in the New dialog:

Figure 2.5. Select a wizard - Project Examples

Clicking Next brings you to the wizard page where you can select a ESB project example from the example list. Every ESB example has two projects, one is a ESB project and another is a Java project used to test the ESB project.

Figure 2.6. JBoss Tools ESB Project Examples

Select JBoss ESB HelloWorld Example ESB and Client project, and then click Finish, then you will get two projects created.

Figure 2.7. JBoss ESB Project Examples: helloworld and helloworld_testclient

Deploy the HelloWorld ESB project and run a test class in the client Java project to see the test result in the Console view.

2.4. Deploying a ESB Project

In this chapter youwill see how to deploy a ESB project using the WTP deployment framework.

Before deploying the project, open the JBoss Server View by selecting Window > Show View > Other > Server > JBoss Server View, create a JBoss Server in the Server view and start it, and then right click the created JBoss server, select Add and Remove Projects, and add the ESB projects you want to deploy from the left side to the right side in the opened dialog.

Figure 2.8. Add and Remove Projects

Click Finish to add the project to the server. You also can drag the ESB project from the Project View to the server.

Figure 2.9. JBoss Server View

Thus, you have just added the ESB project to the JBoss server module list. Right click the JBoss Server and select Publish to publish the project on the server. You can check the deploying result in the Console view.

2.5. Creating a ESB File

In this chapter we suggest a step-by-step walk-through of creating your own simple file. Let's try to organize a new ESB file.

We will show you how to use the Creation wizard for creating a new ESB file.

At first you should open any project. Select File >New > Other... in the main menu bar or context menu for selected project and then ESB > ESB File in the New dialog:

Figure 2.10. Select a wizard - ESB File

Clicking Next brings you to the wizard page where a folder, a name and a version for the file should be specified. Choose, for example, jboss-esb.xml as the name and accept the selected projects folder and the default version.

Figure 2.11. Folder, Name and Version for ESB file

Thus, your file will be created in the selected projects folder by default. If you want to change the folder for your future file click Browse... button to set needed folder or simply type it.

Clicking on Finish results in the file being generated. The wizard creates one xml file.

2.6. Configuring ESB Runtime in Preferences

In this chapter you will know how to predefine a JBoss ESB runtime on the Preferences page.

You may already know, there are two ways to set JBoss ESB runtime when creating a ESB project, one is to use the project target JBoss runtime, and another is to select a JBoss ESB runtime predefined in JBoss Tools preferences. Let's configure it.

Select Window >Preferences > JBoss Tools > JBoss ESB Runtime , to open the JBoss ESB Runtime Preferences page where you can add, remove and Edit a JBoss ESB runtime.

Figure 2.12. JBoss ESB Runtimes

Select Add to open a dialog where you can specify the JBoss ESB runtime location, name and version number. You also can customize the libraries of the runtime by checking the Customize JBoss ESB Runtime jars checkbox.

Figure 2.13. Configure new JBoss ESB Runtime

The new JBoss ESB Runtime will be configured. Click OK to finish and save the preferences. You can use the configuration when creating a JBoss ESB project.

When a ESB runtime is configured for your ESB project you are able to change it to any other using the classpath container page for ESB runtime. To do that, turn to the Package Explorer view and right-click the "JBoss ESB Runtime" library. Select Properties and a table listing all available JBoss ESB runtimes will appear:

Figure 2.14. Classpath Container Page to change ESB runtime

Choose one of them to set to the ESB project and click Ok.

ESB container allows Source and JavaDoc locations to be set via the Properties dialog on each contained .jar: right-click on any .jar file, select Properties. Choose Java Source Attachment and select location (folder, JAR or zip) containing new source for the chosen .jar using one of the suggested options (workspace, external folder or file) or enter the path manually:

Figure 2.15. Classpath Container: Java Source Attachment

Click on Apply and then on Ok.

To change Javadoc Location choose Javadoc Location and specify URL to the documentation generated by Javadoc. The Javadoc location will contain a file called package-list:

Figure 2.16. Classpath Container: Javadoc Location

Click on Apply and then on Ok.

2.7. Using and Configuring SOA Platform

In this chapter you will know what is JBoss Enterprise SOA Platform and how you can configure it to use for your ESB projects.

JBoss Enterprise SOA Platform delivers a flexible, standards-based platform to integrate applications, SOA services, business events and automate business processes. The SOA Platform integrates specific versions of JBoss ESB, jBPM, Drools and the JBoss Enterprise Application Platform that are certified to work together in a single supported enterprise distribution.

Having configured JBoss Enterprise SOA Platform for your ESB project you don't need to install and configure ESB server and runtime as they are already included.

Check here to find more details on the platform: JBoss Enterprise SOA Platform and JBoss Enterprise SOA Platform Component Details.

You can find out what is SOA here: Basics of SOA and SOA and EOA.

To configure the JBoss Enterprise SOA platform select Window > Preferences > Server > Runtime Enironments, that will open the Server Runtime Environments Preferences page where you can add, remove and edit a Server Runtime Environment.

Figure 2.17. Configure new Server Runtime Environment

Select Add, choose JBoss 4.2 Runtime as a type of runtime environment, check the Create a new local server checkbox and click Next:

Figure 2.18. Type of Server Runtime Environment

On the next step you can specify a name of the server runtime environement and browse to its location. Click Finish to add the server runtime environment.

Figure 2.19. New Server Runtime Environment Details

Now you have your SOA platform configured. To check the configuration create a ESB Project using instructions described here. As a result you will have two projects created:

Figure 2.20. Helloworld Projects Created

Then you will need to add JBoss ESB libraries to your projects to configure the SOA server runtime exactly for your projects. Right-click on your project, select Build Path > Add Libraries:

Figure 2.21. Add Libraries

Choose JBoss ESB Libraries and click Next:

Figure 2.22. ESB Libraries

Select the necessary runtime to add to the project classpath:

Figure 2.23. Select a ESB runtime

Click Finish.

Now you can deploy your Helloworld project to the server and run a test class in the client Java project to see the test result in the Console view.

Chapter 3. ESB Editor

3.1. ESB File Editor

3.2. ESB Editors Features

3.2.1. ESB syntax validation
3.2.2. Support for XML Schema
3.2.3. Content Assist for ESB XML file
3.2.4. Synchronized Source and Visual Editing

ESB editor has lots of useful features, they are described in details in this chapter. In addition you'll get to know with how ESB Editor uses combined visual and source editing of esb files.

3.1. ESB File Editor

ESB File Editor is a powerful and customizable tool. ESB File Editor allows developing an application using ESB technology.

ESB file editor has two tabs: Tree and Source.

You can switch to Tree. The Tree view for the editor displays all ESB artifacts in a tree format. By selecting any node you can see and edit its properties which will appear in the right-hand area. For example, a Provider:

Figure 3.1. Tree View

You can easily switch from Tree to Source by selecting the Source tab at the bottom of the editor and work in Source view.

Figure 3.2. Source View

The Source view for the editor displays a text content of the ESB file. It is always synchronized with Tree view, so any changes made in one of the views will immediately appear in the other.

No matter what view you select, you get full integration with Outline view. For example, you can work in the Source view with the help of the Outline view. The Outline view shows a tree structure of the ESB file. Simply select any element in the Outline view and it will jump to the same place in the Source editor, so you can navigate through the source code with Outline view.

Figure 3.3. Outline View

Adding, editing or deleting of some artifacts operations are available right in the Tree view . Right-click any node and select one of the available actions in the context menu. For example, you can easily add a new Provider:

Figure 3.4. Adding New Provider

You can easily add a new Service too:

Figure 3.5. Adding New Service

The same way you can create a listener for service and other elements of ESB:

Figure 3.6. Adding New Listener for Service

The same actions can be done in the right part of Tree view tab (Form editor) using Add, Edit and Remove buttons.

In order to add a new generic Action to your ESB XML file you should select the Actions node under the Services, then right-click and choose New > Generic Action.

Figure 3.7. Adding New Action in the Tree View

Or instead make use of Add... button in the Form editor on the left.

Figure 3.8. Adding New Action in the Form Editor

As you can see on the bath figures above, the context menu will also prompt you to insert one of the Actions that are supplied out-of-the-box with JBoss ESB. After choosing one an appeared New Action wizard will ask you to fill out a name field and other fields specific for each Action property. For example, for Content Based Router Action the wizard looks as follows:

Figure 3.9. New Action Wizard

After confirming creating the Action you can see it in the Tree under the Actions node and preview as well as edit its settings in the Form editor on the left.