Java Reference
In-Depth Information
Right-click on the Service Assembly file under the CustomerCASA project in the project
view, and choose Edit. This will show you a partitioned canvas that is used to lay out the com-
ponents in the assembly in a graphical view of the JBI file.
Building the assembly
Click the hammer icon (Build Project) to build the project. This will reveal the partner links
available on the process WSDL. NetBeans will automatically wire up your inputs and outputs
appropriately to indicate that the message will come in from the BPEL Service Engine, do its
work, and come back out again.
If the build is successful, you should see output indicating that it successfully created a Cus-
tomerCASA.zipfile. In an unusual format for Java projects, it is this ZIP file that represents
the deployable artifact.
Deploying the assembly to the BPEL service engine
This is where you can have validation problems, so despite the fact that you've built your
BPEL and CASA successfully, you might not be out of the woods quite yet. Click the wrench
and paper icon to deploy the project. If successful, you should see output like this:
//...
[deploy-service-assembly]
Deploying a service assembly...
host=localhost
port=4848
file=/home/ehewitt/soacookbook/repository/code/chapters/
CustomerCASA/dist/CustomerCASA.zip
[start-service-assembly]
Starting a service assembly...
host=localhost
port=4848
name=CustomerCASA
BUILD SUCCESSFUL (total time: 1 second)
To verify your installation, open the Glassfish web administration console and expand the
JBI→Service Assemblies node. This is illustrated in
Figure 9-14
.
NOTE
You need to have the BPEL Service Engine installed and running in your OpenESB installation with
Glassfish for this example to work. Expand the JBI→Components node to verify that it is present and
running.
