---

Enterprise Pack Overview (30 Minutes)

This demo provides an overview of BPEL, XML Schema, Refactoring, and Testing facilities in the NetBeans Enterprise Pack 5.5.

Setup

The Enterprise Pack 5.5 should be installed along with the runtime installer. Before beginning the demo, the app server should be started. The BPEL service engine (accessed through Runtime tab -> App Server -> JBI -> Service Engine -> bpelse should be started in the debug mode).

Demo

BPEL

• Create new Synchronous sample project. This project contains a simple BPEL process which simply returns the incoming message.
• The synchronous sample project will create both a BPEL project and a composite application project. Use the Add JBI action of the composite application project to add the BPEL project to the composite application.
• Open the BPEL editor for the synchronous process. This should be the only BPEL file in the BPEL project. Take a minute here to explain the palette, the editor, and the navigator. Of course, also explain what the process does.
• Ensure that the mapper window is displayed.
• Either delete the current assignment statement or modify the current assignment statement in the BPEL mapper. The mapper provides a way to automate the XPath expressions required when orchestrating web services. This is a common scenario in BPEL, so this is heavily used. Add a concat component to create a hello world mapping between the input and output.
• Use the deploy action on the composite application to deploy the process.
• Open the runtime tab to show the JBI integration into the App server node tree. Showing the information available such as the service engines as well as the Service Assemblies such as the one just deployed is useful.
• Add a test case to the composite application project and point to the wsdl for the synchronous bpel process.
• Run the test case and explain that the unit tests are based on the difference between the expected and actual output values. Confirm the dialog to capture the first test case output. Run the test again, things should pass.
• Now modify the BPEL process again (changing the concatenation) to show the test failure. Test should now fail. Explain the Test driven development approach.
• Add a breakpoint to the BPEL process.
• Attach the debugger using the BPEL debugger to the BPEL service. The BPEL debugger is in the list along with the JPDA option.
• Run the test case again. The process should stop on the breakpoint, where the BPEL variables window can show the input/output XML messages. Also mention, the process and watches support.
• Optional here is to create an EE 5 web service (and deploy this) to show the drag and drop of the web service onto the BPEL canvas. It is best to predeploy this service but if you have time it is worthwhile to show this scenario.

XML Schema

• Open the travel reservation schema, this is found in the travel reservation BPEL sample project. Show the source view. This is a large schema 17K lines of ASCII text. Understanding this schema is difficult without tools.
• Show the schema view and explain the columns view. This view provides a drill down facility that always allows context to be maintained. This view also provides additional navigation not available in a pure structural view, such as inline inheritance view, navigation. Show the breadcrumbs on top to navigate.
• Show the design view. The design view provides a virtual instance document view. You can see in the OTA schema that the design view allows a developer to visual what an instance document would look like (and edit).
• Optional is to show the search facility here, there are many ways to search locally within the file (by namespace ...).
• Have an empty schema up and switch to the design view here (if you are using Coke) to show the editing capabilities. You can easily drag and drop elements and attributes to create complex structures.
• Use the Apply Design Pattern menu on the Project view node to demonstrate the power of the design pattern support. By checking a few radio buttons, the design pattern can be transformed. Also, show the power of the Undo/Redo feature by going back and forth to several design patterns.
• Go back to the schema view and select the itineraryRef schema element and use the where used capability. This shows the power of the XML refactoring when applied to BPEL, XML Schema, and WSDL documents.
• Demonstrate the zoom (ctrl - right mouse) the expand, collapse and the navigation features. Also mention the UML like notation used to describe the usage.