Consider GlassFish ESB v2 for SOA Tooling

Select the "String Literal" from the "String" menu and drag it into the middle column.

Click here for a larger image.

Figure 45: Select Literal String for Mapper assignment

Enter a literal value of "TicketSubmitted", and map the literal value to the part1 element of the SubmitTroubleTicketOperationOut message.

Click here for a larger image.

Figure 46: Map Literal String to Reply message.

You now have provided a stubbed out value for the SOAP Reply message to send back to the consumer of the service. A future iteration of this example could be extended to demonstrate accessing a database, invoking another service, or routing a message to a JMS Queue to store a Trouble Ticket as well as generating a unique Trouble Ticket Number to be returned in the SOAP Reply. However, the goal for this article is to simply provide a relatively high-level overview and introduction to the GlassFish ESB.

Save and Validate BPEL

By clicking the Source tab, your BPEL generated code should look like the following:

Click here for a larger image.

Figure 47: View BPEL Source

Build the Service Unit (JAR)

Right-click the CaptureTroubleTickets BPEL project root node and select the "Build" menu option (to build a jar file for the project)

Click here for a larger image.

Figure 48: Map Literal String to Reply message.

Within the context of a JBI container, the resulting jar is known as as a "Service Unit"—which is the smallest unit that can be deployed to a JBI container.