{section}
{column}

h1. Summary

This tutorial explains how you can make expose a EJB (2.x or 3.x) as a service in Petals ESB.
Notice that this is mainly interesting with EJB 2.x, as EJB 3.x can directly be exposed as web services with application servers.

\\
To enable communications between the EJB and Petals ESB, you will need a JNDI.
The EJB will have to be configured to use this JNDI.

\\
Technically, this tutorial shows the creation of a service-unit for the [Petals-BC-EJB|petalscomponents:Petals-BC-EJB] component in *provides* mode.

{info}
*Level:* Easy
*Estimated time:* 10 minutes the first time, 5 minutes then
*Expected skills:* know the EJB project to import
{info}
{column}
{column:width=350px}
{panel:title=Table of contents}{toc}{panel}
{column}
{section}

h1. Creating the Service-Unit project

h2. Getting started

A wizard opens up, showing three drop-down lists.

\\
In the scope of this tutorial, we are going to work with the version 3.1 of the EJB component.
Which gives us:

!petals-studio-tuto-import-ejb-1.jpg!

\\
Click *Next*.


h2. Preparing the WSDL generation

To expose an EJB as a service in Petals, a WSDL has to be generated from the EJB's remote interface.
This way, the Petals SQL component is able to convert XML messages into Java objects that can be passed to the EJB as arguments.
The WSDL generation is prepared by the first page in the wizard.

!petals-studio-tuto-import-ejb-2.jpg!

\\
The *EJB libraries* contain the EJB specific classes. They will be copied in the created project.
The *Server libraires* contain the required classes to compile the EJB classes. They will be used in the WSDL generation but will not be imported in the created project.

\\
Once the libraries have been selected, the EJB's remote interface must be set. This can be done by selecting *Browse...*. A list of the classes located inside the EJB libraries will be displayed. The selection of the remote interface also completes the WSDL file name. Obviously, this name can be changed.

!petals-studio-tuto-import-ejb-3.jpg!

{note}
Note that there is no page to define the JBI fields (interface, service and end-point names).
These values will be deduced from the generated WSDL definition.
{note}

h2. Defining the project name

This page defines the name and the location of the project that will be created.
Indeed, this wizard will result in the creation of a project containing all the required elements for a EJB service-unit.

\\
Enter a project name for your project.
If you do not want your project to be created in the default workspace, uncheck *Use default location*.
Then click *Browse...* and select the location where the project will be created.

!petals-studio-tuto-import-ejb-4.jpg!

\\
{note}
Petals service-units have a naming convention.
For a service-unit which provides a service, the convention is *su\-*_<Protocol or Technology>_*\-*_<Service name>_*\-provide*
{note}

\\
Then, click *Next*.


h2. Specifying the EJB parameters

This page defines information which are specific to the Petals EJB component.
The required parameters are mostly about the JNDI properties of the EJB.
The meaning of all the parameters can be read in the documentation of the [Petals-BC-EJB|petalscomponents:Petals-BC-EJB] component.

\\ !petals-studio-tuto-import-ejb-5.jpg!

h2. Checking the result

When the wizard has completed, a new project has been created and is visible in your workspace.

It contains a jbi.xml file, located under *src/main/jbi*.
This hierarchy allows you to work with Apache Maven then (a pom.xml was also created at the root of the project).
In the same directory, and if you provided a WSDL in the wizard, you can see your WSDL interface, which was imported with all its dependencies (e.g. referenced XML schemas or other WSDL interfaces).

\\ !petals-studio-tuto-import-ejb-7.jpg!


h1. Updating, packaging and deploying

h2. Further edition and packaging

After completion, the newly created jbi.xml file has been open in the Service-Unit editor.
Regarding EJB configurations, the wizards are complete and provide all the options.
Thus, you do not need to edit the jbi.xml.

\\
The project contains everything the EJB component needs.
You can now package it before deploying it.

\\
The created project being a [Service-Unit project|Working with Service Unit projects], you can [package it as any Service-Unit project|Working with Service Unit projects#Export for Petals].
It results in the creation of a Service Assembly for the Petals-BC-EJB component. Its location depends on your export choices.

h2. Deployment

The deployment of the created service assembly can be achieved with the Petals web console.
Or you can do it by dropping the service assembly in the *install* directory of your Petals installation.
This second option should only be used in development steps.

\\
First, make sure the Petals-BC-EJB is installed in your Petals environment.
Then, install the service assembly in your Petals, using one of the two ways indicated above.

\\
Be careful, the Petals EJB component cannot be used as it.
It needs to be configured to use the shared-library associated with your EJB server.

You may also have to create this shared-library, in case where your EJB server is not supported by the Petals team.
Do not worry, creating a shared-library is very easy with the [Petals Maven plug-in|petalscomponents:Maven Petals Plug-in] (provided you are familiar with Maven).
And configuring the EJB (or any other Petals) component to use a shared-library can be achieved with the [Petals Maven plug-in|petalscomponents:Maven Petals Plug-in].