The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Using the SQL integration service with WebSphere Lombardi Edition V7.2 and WebSphere Application Server V7

Danh Ngoc Phi (phidn@vn.ibm.com), IT Specialist, IBM

Danh Ngoc Phi is a Software Developer with the IBM Software Group in IBM Vietnam. He has more than five years of experience in software development, maintenance, deployment, and support as an IT Specialist, Technical Team Leader, and Technical Architect.

Summary: This tutorial provides steps to help you create a connection with DB2® and manipulate the database by using the Java™ Naming and Directory Interface (JNDI) in WebSphere® Application Server and using it in WebSphere Lombardi Edition V7.2. In Lombardi Edition, you learn how to create a human service to support interaction with end users. Moreover, you learn how to design data structure to represent business data and to control the work flow in a business process application.

Date: 12 Oct 2011
Level: Intermediate
PDF: A4 and Letter (2346 KB | 34 pages)Get Adobe® Reader®

Activity: 24686 views
Comments:

Debugging a process application

Assume that you have successfully configured the JNDI jdbc/sampleDB in WebSphere Application Server and the database is set up already. You will now debug the Retrieve Policy Details integration service to test whether the new service functions properly.

If you have not set up the database, see the Create the database and configure the database authority section.

If you have not created the JNDI, see the Set up the data source (JNDI) in WebSphere Application Server section.

Figure 21. Component diagram of Retrieve Policy Details
Component diagram of Retrieve Policy Details

Click on the debug button of this service (Figure 21). In the web browser, you will see a new window specified for debugging. In the browser, there are two buttons, Step and Run. The Step button is used to debug every step in the service (Figure 22). By contrast, the Run button is purely an execution to the next break point or to the end of the work flow.

Figure 22. Debug on the web browser
Click on the Step button in the web browser to examine all the parameters and values of the service.
Go back to your Lombardi Authoring Environment to look over the token and data inside each component. The Lombardi Authoring Environment navigates to the Inspector perspective.
You can see the token, indicating the current flow of the process. In the Inspector view, you can examine more details and the data flow of the current service.
1. In the Execution State panel, click on Server Script to display the variables of the current Flow Object.
2. In the Variables panel, click on policyNum to retrieve its value, as shown in Figure 23.
  
  Figure 23. Debug window in Lombardi Edition
In the web browser, click the Step button. In Lombardi, the token moves to the SQL Execute Statement component.
In the web browser, click the Step button, not the Step Over button, to debug inside the SQL Execute Statement component. In Lombardi Edition, the token moves into this component as shown in Figure 24.

Figure 24. Token
In the web browser, click the Step button. You can see the returned results similar to what is shown in Figure 25.

Figure 25. Debug in web browser
In the web browser, click the Step button to debug the next flow. Click the Step button to finish debugging.

By going through these steps, you can understand and analyze the data flow behind the scenes and monitor the token flow among the activities and flow objects.

Comments