Reader expected need to be familiar with Websphere Lom bardi Edition V7.2, Websphere Application Server V7.0 and DB2 version 9.

Transcription

1 Websphere Lombardi V7.2 and SQL Integration service Introduction WebSphere Lombardi Edition V7.2(Author Envir) provides Integrated Service to connect to the database management system (DBMS) that was specified during installation time Microsoft SQL server, DB2, or Oracle. This tutorial illustrates how to manipulate data in the DBMS using Lombardi Edition by using JNDI in Websphere Application Server. In this tutorial we use DB2 version 9.7 Fix pack 1 Objectives In this tutorial, you will learn how to: Work with the Authoring Environment in WebSphere Lombardi Edition. Create a Toolkit, a re-used library can be used across numerous process applications Create variables: input, output, private, and complex structure Create an Integrated Services interacting with database by using SQL Integration Using parameter in SQL integration Debug Create a Human Service Integrate the Human Service with the Integration Service Create database, table and configure authority. Create a custom data source that you can use in WebSphere Lombardi Edition. Test the custom data source. Prerequisites Reader expected need to be familiar with Websphere Lom bardi Edition V7.2, Websphere Application Server V7.0 and DB2 version 9.7 Fix pack 1 System requirements You need WebSphere Lombardi Edition V7.2 running on Windows XP or Windows 7 with access to DB2 V

2 Create a Toolkit in Authoring Environment A Toolkit is a collection of library items which can be re-used in variety of process applications. The Image below is a good illustration of toolkits Step 1: Login into Lombardi Authoring Environment(Author Envir) with tw_admin user Step 2: Create a new Toolkit in Lombardi Authoring Environment Fill in the pop up dialog as below and click Create button 2

3 Step 3: Open the Designer perspective Step 4: Create an Integration Service to connect to DB2 We need to have a connection to DB2 for extracting data from db2 purpose. Therefore, we need to have an Integration Service to do it. Fill in popup dialog as below, then click Finish button: 3

4 Step 4: Design the workflow for the new Integration Service On the right Common pallet, drag 2 components(server Scriptlet and Server Script), which run at server side, into the diagram as below. 4

5 Step 5: Connect with SQL Execute Statement. In Author Envir, The SQL Integration services are Java-based integrations that bind to a specific method in the teamworks.sqlconnector Java class. It means that we have many built in services in the System Data toolkit enable us to have interaction with database. In this tutorial we use SQL Execute Statement Under Toolkits, expand System Data and select All, then start typing SQL Execute to filter the components, Drag the SQL Execute Statement into the diagram Step 6: Wire all the component together and set reasonable names for the components a. To set the name for Untitled1, Please click on Untitled 1, in the Properties panel, select Step and type Set Query for the name property b. Set the name for Untitled2 as Set Parameter At this state, we can have a brief overview about the workflow of our new toolkit. Further next step, we need to have data to store. Click Save(Ctrl + S) button to save the new toolkit Create Variables for the toolkit Step 1: Select the Variables tab, and click on Add Input button to add an input The Default data type is String. Check the Has Default check box and input the PO_1234_56 as default value 5

6 Step 2: Add Output Click on Add Output button to add Output data. Our integration service is retrieving data from database, it s not right if our service does not return any value. Hence, we need to add Output to return data from the service. a. Set the name for output as policydetails. b. In Variable Type click on New button policydetails contains a lot of user defined data such as: policy number, policy issue date, etc. In Author Envir, we definitely does not have any data type sound similar like it. That s the reason we need to create a Complex Structure Type c. Put PolicyDetails as the name for the new Complex Structure Type and click Finish to bring an assist window for the new data type. 6

7 d. In the Parameter section, click on Add button and fill in Name property as PolicyNum. The default data type is String, we do not need to select e. Click on Add button(in the Parameter section), fill in the Name property as PolicyIssueDate. Click on Select button to select data type Select Date as date type f. Add new parameters for this complex data as the image below 7

8 g. Click save and press close button to navigate to Retrieve Policy Details toolkit We need an SQL string for the SQL Integration to execute, I bring up some questions: Where is this SQL string defined: inside this integration service or can be dynamically set as an input? Does it contain any parameter? If yes, what kinds of parameter they are? What sort of data return after executing this SQL? What kinds of data type the return values(a list, a string or a number, etc)? Where do we store the return data for the SQL execution? Depending on your requirements, you will have different answers and they affect the way you design the toolkit and application. For this tutorial, we just need to define the SQL string inside the toolkit, the return values is a PolicyDetails type. This is the reason we need to have a private variable to store SQL string, a private variable to store a parameter, and a private variable to store the returned result list of the SQL string. We will discuss further details in next section. 8

9 Step 3: Add private variables: a. Add a private variable named SQL with data type as String b. Add a private variable named params with data type as SQL Parameter. Check Is List c. Add a private variable named policydetailslist with data type as PolicyDetails. Check Is List d. Click Save 9

10 Implement the components of Retrieve Policy Details Integration Service Step 1: Implement the Set Query component a. Click on Set Query component, and click on Implementation b. In the Script section, input the SQL String: SELECT POLICYNUM as POLICYNUM, POLICYISSUEDATE as POLICYISSUEDATE, POLICYSTATUS as POLICYSTATUS, POLICYCOMMENCEMENTDATE as POLICYCOMMENCEMENTDATE, POLICYMATURITYDATE as POLICYMATURITYDATE, PROPOSERNAME as PROPOSERNAME,FIRSTLIFEASSURED as FIRSTLIFEASSURED, FIRSTLIFEASSUREDNAME as FIRSTLIFEASSUREDNAME, GENDERFIRSTLIFEASSURED as GENDERFIRSTLIFEASSURED, SECONDLIFEASSURED as SECONDLIFEASSURED, SECONDLIFEASSUREDNAME as SECONDLIFEASSUREDNAME, GENDERSECONDLIFEASSURED as GENDERSECONDLIFEASSURED, VIP as VIP, CLAIMNUMBER as CLAIMNUMBER, CLAIMSTATUS as CLAIMSTATUS FROM DB2ADMIN.POLICYDETAILS WHERE POLICYNUM=? c. In the Binding section, click on Select button to select the variable to store the SQL String into private variable, select private sql variable Step 2: Implement the Set Parameter component a. Select on Set Parameter component, click on its Implementation property b. In the Script section, input script as below c. Step 3: Implement the SQL Execute Statement component 10

11 d. We have already defined the SQL string and keep in a private variable named sql. For this component, we need to pass the SQL string into this component as one of the inputs. Furthermore, this SQL Component also requires parameters list, return type, data source name, and etc as inputs. Fortunately, we have planned for the return type, data source name and parameters list e. Click on the SQL Execute Statement component, select the Data Mapping property. f. Click the button to map the SQL String as the picture below g. Unchecked the Use default checkbox of parameters to enable edit its content, Click on mapping button to map data to private variable named params. h. Unchecked the Use default check of returntype, and put "PolicyDetails" as its value. i. Enable edit the datasourcename and insert "jdbc/sampledb" as its value j. For the results(any) field of mapping output section, we choose policydetailslist as output 11

12 Debug Assumed that we have configured the JNDI jdbc/sampl edb In Websphere Application Server successfully and database is setup already, we will debug the Retrieve Policy Details Integration service to test our new service whether its service function properly. If you have not setup the database, please refer to Create database and configure Authority section to setup database If you have not created the JNDI, please refer to Setup data source(jndi) in Websphere Application Server section to configure the JNDI properly Step 1: Click on debug button of this service. In web browser, we will see a new window specified for debugging. In the browser, there are two buttons Step and Run. Step button is useful for debugging for every step in our service. By contrast, the Run button is purely execution to the next break point or the end of the work flow 12

13 Step 2: Click on Step button in the web browser to examine all the parameters and values of our service. Step 3: Go back to our Lombardi Authoring Environment to look over the token and data inside each component. The Lombardi Authoring Environment navigates to Inspector perspective. You can see the token,, indicating the current flow of our process. In the Inspector view, we can examine more details, data flow of our current service. a. In the Execution State panel, click on Sever Script to display the Variables of the current Flow Object. b. In the Variables Panel, click on policynum to retrieve its value. Step 4: In Web Browser, click on Step button, In Lombardi, out token moves to SQL Execute Statement 13

14 component. Step 5: In Web Browser, click on Step button, NOT the Step Over button, to debug inside the SQL Execute Statement component. In our Lombardi, the token will move into this component as below Step 6: In Web Browser, click on Step button. We can see the return results. Step 7: In Web Browser, click on Step button to go next. Click on Step button to finish debugging By going through these steps, we can understand and analyze the data flow behind the scenes, monitoring the token flow among the activities, flow objects. 14

15 Refine the output of our Integration Service As we can see the results in the debugging mode, the result is a list. However, our SQL Integration Service retrieves the PolicyDetails data by the policynum, which is a Primary key of the PolicyDetails table. Hence, the output of our service is a single record, not a list. Step 1: Drag the Server Script into the diagram, between the SQL Execute Statement and the end Step 2: Rename the new component as Refine Output and wave the new component, Step 3: Click on the End line.unchecked the Show End State Step 4: Click on the Refine Output Server Script, Select the Implementation and put the script as below into its Script field. This script is used to assign the first record in the return result list to output variable.if(tw.local.policydetailslist.listlength > 0){ tw.local.policydetails = tw.local.policydetailslist[0]; } 15

16 Design a Human Service (Coach) to capture the return data from our database integration service We can design a Human Service in a process application. But in this tutorial, I choose to design the Human Service inside this toolkit because i need to re-use this Human service in many process applications. Putting it into your toolkit or process application is up to your specific requirements Step 1: In Designer view, click + button of User Interface, and select Human Service Step 2: Input Select Policy in the new popup dialog and click Finish button. Step 3: In the Select Policy service, switch to Variables tab Step 4: Click on Add Private button, and put policydetails as its name and select PolicyDetails as its variable type. Check Has Default 16

17 Step 5: Go back to Diagram view, drag a Coach into the diagram Step 6: Click Save, double click on the new Coach to navigate into Coach view. Step 7: Drag the policydetails variable in the Variables panel into the Coach 17

18 Step 8: Select the Policy Details panel, In the Properties panel, select Section, and increase # of Columns to 2. Step 9: Drag the Button Group in the Controls panel right below the Policy Num, re-arrange the GUIs Step 10: Select the new button(button), select Presentation, and change the label of this button into Search 18

19 Step 11: Drag the OK button into the Policy Details Section, and select the Section Title and press Delete button. Step 12: Go back to Diagram view, and wave all the objects together Step 13: Select the Coach, and change its name to Main GUI Step 14: Select the Implementation, and drag the Retrieve Policy Details Integration Service into our Human Service s diagram 19

20 Step 15: Select the Sequence Flow button, and draw the diagram as below: Step 16: Select the Retrieve Policy Details, In the Data Mapping, map the input to tw.local.policydetails.policynum and output to tw.local.policydetails. Step 17: Press Save button and Click the Run button,, to test our product Result after clicking on Search button 20

21 Create database and configure Authority It depends on the DB2 front end, we can have numerous ways to create a dedicated database for business interaction. I do not really pay very high attention on database setup in this tutorial. However, I focus on some very important steps only. Step 1: Create database name : SAMPLE Step 2: Ensure the security of the SAMPLE database granting to appropriate user correctly: In this tutorial, I choose db2admin is granted user. Step 3: Create table and populate initial data into the new table a. Create table CREATE TABLE DB2ADMIN.POLICYDETAILS ( POLICYNUM VARCHAR (10) NOT NULL, POLICYISSUEDATE DATE, POLICYSTATUS VARCHAR (10), POLICYCOMMENCEMENTDATE DATE, POLICYMATURITYDATE DATE, PROPOSERNAME VARCHAR (10), FIRSTLIFEASSURED VARCHAR (10), FIRSTLIFEASSUREDNAME VARCHAR (10), GENDERFIRSTLIFEASSURED VARCHAR (10), SECONDLIFEASSURED VARCHAR (10), SECONDLIFEASSUREDNAME VARCHAR (10), GENDERSECONDLIFEASSURED VARCHAR (10), VIP 21

22 CHARACTER (1), CLAIMNUMBER INTEGER, CLAIMSTATUS VARCHAR (10), CONSTRAINT CC PRIMARY KEY ( POLICYNUM) ) ; b. Populate data INSERT INTO SYSIBM.POLICYDETAILS (POLICYNUM, POLICYSTATUS, PROPOSERNAME, FIRSTLIFEASSURED, FIRSTLIFEASSUREDNAME, GENDERFIRSTLIFEASSURED, SECONDLIFEASSURED, SECONDLIFEASSUREDNAME, GENDERSECONDLIFEASSURED, VIP, CLAIMNUMBER, CLAIMSTATUS) VALUES('PO_1234_56','VALID','DANH_PROP','FIRST_DANH','1ST_AS_N','MALE','2ND_ASS','2ND_AS_NA',' MALE','Y',1234,'VALID'); 22

23 Setup data source(jndi) in Websphere Application Server. 1. The assumptions are: a. DB2 is running and you have created a sample database to test with it. In this case, we are using the sample database that comes with the DB2 product. If the sample database does not exist, you may run the DB2 First Steps to create it. b. The WebSphere Application Server V7.0 ProcessCenter01 service is started. 2. In a web browser, bring up the WebSphere Administrative Console. For example, The port number may be different in your environment. You can look in the <WLE_HOME>/AppServer/profiles/Lombardi/logs/ProcessCenter01 Service.log file to determine the port number. 3. Log in as tw_user. The password is tw_user, as shown in Figure 1. Figure 1. WebSphere Administrative Console login 4. In the navigation pane go to Resources > JDBC > Data sources. 5. In All scopes, you see five data sources that were created during product installation. One is the default "Datasource" and the other four are related to Lombardi Teamworks. 6. You will create a new data source that points to the sample database: a. Change the Scope to Cell=LombardiCell01. b. Click New. c. Enter a data source name. We called it SampleDB Data Source. d. Enter a JNDI name, for example, jdbc/sampledb (Figure 2) and click Next. Figure 2. Data source information 23

24 e. You may choose to create a new Java Database Connectivity (JDBC) provider. Since one already exists for DB2, select an existing JDBC provider. f. Click Select an existing JDBC Provider. From the drop down list, select TeamWorks Process Server DB2 JDBC Driver as shown in Figure 3 and click Next. Figure 3. Select the JDBC provider g. For the driver type, choose 4. h. Enter the database name as SAMPLE. i. Enter the database server name as localhost. j. If the port number is not filled in, enter the database port number as shown in Figure 4. The default port number for DB2 is k. Click Next. Note: In production environments, we recommend that you use a fully qualified host name 24

25 rather than localhost. Figure 4. Database properties l. Choose the LombardiCell01/processdblogon alias (Figure 5) for all, except the mappingconfiguration alias. m. Click Next. Note: Typically, you create a J2C authentication alias. Since you are simply using a different database table in the same DB2 instance, you can use the existing J2C aliases. Figure 5. Security settings 25

26 n. On the Summary screen, double-check the values and click Finish, as shown in Figure 6. Figure 6. Data source creation summary screen 26

27 o. Save to the master configuration and restart the server. p. Select the newly created data source and click the Test connection button. Make sure the connection is successful. If there are errors, fix them before proceeding. 7. We need to add user and password to this JNDI. In the data source page, click on the link Sample Data Source Name 27

28 8. In the new window, click on Custom properties 9. Click on New button 10. Fill user to the name text field. Fill your db2 user in the value text field, In my environment, my db2 user is db2admin. Then, Click Apply 28

29 After this step, we have one property having db2 user name 11. We need to create another property containing the password as well. 29

30 12. Double check the overall Custom properties, and click Save 13. Test connection. 30

31 References: WebSphere Lombardi Edition 7.1 STEW Materials WB003 V 01.1 ENG 31