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 JMS 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-jms-3.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 JMS parameters
This page defines information which are specific to the Petals JMS component.
The required parameters are all about the JNDI properties and the JNDI-configuration of the JMS server.
The meaning of all the parameters can be read in the documentation of the [Petals-BC-JMS|petalscomponents:Petals-BC-JMS] component.
\\ !petals-studio-tuto-import-jms-4.jpg!
\\
Click *Next*.
h2. Specifying the CDK parameters
The CDK is the Petals framework to develop JBI components.
The Petals-BC-JMS component was developed with this framework.
This page requires information related to the CDK.
By default, you have nothing to do here.
The meaning of all the CDK parameters for JMS can be found in the documentation of the [Petals-BC-JMS|petalscomponents:Petals-BC-JMS] component.
\\ !petals-studio-tuto-import-jms-5.jpg!
\\
Click *Finish* to complete the wizard.
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-jms-6.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 JMS 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 JMS 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-JMS 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-JMS 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 JMS component cannot be used as it.
It needs to be configured to use the shared-library associated with your JMS server.
You may also have to create this shared-library, in case where your JMS 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 JMS (or any other Petals) component to use a shared-library can be achieved with the [Petals Maven plug-in|petalscomponents:Maven Petals Plug-in].
E-mail
...