IBM Proof of Technology Workshop WebSphere Business ......IBM Software Page 4 Discovering the value...

IBM Software Group

© 2009 IBM Corporation

IBM Proof of Technology Workshop

WebSphere Business Process Management für End-to-End Process Automation

Handbuch für die Übungen

Übung 1: Prozessmodellierung in WebSphere Business Modeler Übung 2: Prozessintegration mit WebSphere Integration Developer Übung 3: Publishing, Arbeiten mit dem Prozess, Monitoring, GUI

PoT.WebSphere.09.4.069.00

© Copyright International Business Machines Corporation, 2009. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM Software

Contents Page 1

Inhalt ÜBUNG 1 PROZESSDEFINITION UND MODELLIERUNG ............................................................................. 3

1.1 IMPORTIEREN EINER VISIO PROZESS-MAP ............................................................................................ 4 1.2 VERVOLLSTÄNDIGEN DES PROZESSMODELLS ..................................................................................... 13 1.3 KALENDER ........................................................................................................................................ 43 1.4 EINBETTEN DES FINAL LOAN REVIEW PROZESSES ALS UNTERPROZESS VOM UNDERWRITING

PROZESS .......................................................................................................................................... 52 1.5 LOTUS FORMS (OPTIONAL) ................................................................................................................ 58 1.6 SIMULATION (OPTIONAL) .................................................................................................................... 65 1.7 MODELLING FÜR DIE PROZESSAUTOMATISIERUNG............................................................................... 85 1.8 GESCHÄFTSKENNZAHLEN UND KPIS HINZUFÜGEN ............................................................................. 132

ÜBUNG 2 WEBSPHERE INTEGRATION DEVELOPER - PROZESSINTEGRATION ................................ 152 2.1 STARTEN DES SERVERS .................................................................................................................. 155 2.2 STARTEN VON WEBSPHERE INTEGRATION DEVELOPER .................................................................... 156 2.3 ERKUNDEN DER INTEGRATIONS-ARTEFAKTE IM WEBSPHERE INTEGRATION DEVELOPER .................... 157 2.4 SERVICES AUS WEBSPHERE SERVICE REGISTRY AND REPOSITORY EINBINDEN ................................. 163 2.5 REVIEW DER NOTIFYCUSTOMEROFDECISION SCHNITTSTELLENSPEZIFIKATION IN RATIONAL ASSET

MANAGER (OPTIONAL) ..................................................................................................................... 171 2.6 KOMPLETTIEREN DER IMPLEMENTIERUNG DES FINAL LOAN REVIEW PROZESSES ................................ 181 2.7 AUFRÄUMEN ................................................................................................................................... 188

ÜBUNG 3 PROZESSDARSTELLUNG UND MANAGEMENT – ERSTELLEN UND KONFIGURIEREN SIE BUSINESS SPACES, PAGES UND WIDGETS IN EINER WEB-ANWENDUNG ............... 190

3.1 STARTEN DES SERVERS UND ÖFFNEN DES BUSINESS SPACE DASHBOARDS ...................................... 195 3.2 NAVIGIEREN IM BUSINESS SPACE .................................................................................................... 197 3.3 FACHLICHE ROLLE: ERKUNDEN DER EXISTIERENDEN WIDGETS FÜR DAS BUSINESS ACTIVITY

MONITORING .................................................................................................................................. 203 3.4 ERSTELLEN EINES NEUEN BUSINESS SPACE UND SEITEN FÜR COLLABORATION ................................. 216 3.5 FACHLICHE ROLLE: KONFIGURIEREN DER WIDGETS FÜR COLLABORATION UND PUBLISHING .............. 218 3.6 ERSTELLEN EINES NEUEN BUSINESS SPACE UND SEITEN FÜR EINEN BENUTZER, DER DEN

PROZESS AUSFÜHRT ....................................................................................................................... 237 3.7 FACHLICHE ROLLE: KONFIGURIEREN DER WIDGETS, UM DIE HUMAN TASKS BEI DER

PROZESSAUSFÜHRUNG DURCHZUFÜHREN ........................................................................................ 242 3.8 BUSINESS SPACE UND SEITEN FÜR EINEN IT USER ........................................................................... 247 3.9 TESTEN DES PROZESSES ................................................................................................................ 248 3.10 AUFRÄUMEN ................................................................................................................................... 249

IBM Software

Page 2 Discovering the value of Business Process Management for End-to-End Process Automation

THIS PAGE INTENTIONALLY LEFT BLANK

IBM Software

Lab 3 – Process Visibility and Management Page 3

Übung 1 Prozessdefinition und Modellierung

Lab Introduction This lab will be your first introduction to the Better Financials scenario. Better Financials is a lending institution, primarily focused on mortgage lending but also interested in expanding their business into other types of lending. Key to their business is Underwriting, the process in which potential customers are assessed in order to confirm the financial security of providing a product to them. Underwriting reviews are generally broken up into three parts: Credit, Capacity, and Collateral. A Credit assessment includes a look at the loan applicant’s history of paying off other debts, which helps Better Financials to determine the likelihood that the applicant will repay the loan. A Capacity review looks at the applicant’s ability to repay the loan by looking at their employment history and potential, as well as their current debts and assets. A Collateral review is concerned with determining how Better Financials will be able to respond should the loan not be repaid, in terms of what assets or property the applicant has that could be seized. An applicant does not need to have an outstanding performance in all three of these areas. However, if an applicant is particularly deficient in one area, they may need to be particularly strong in another area in order to receive the loan that they are requesting.

In our simplified Underwriting process, a loan application is submitted in order to start the process, after which a manual Credit review is performed. After the Credit review, both a Capacity review and a Collateral review occur in parallel. Based on the results of the credit review, the Capacity and Collateral reviews may need to be more detailed than normal to account for any deficiencies in the Credit review. There are a number of ways we could implement this variability, and these implementation details will change throughout the workshop, as we examine different concepts. In some cases, there will be no variability. Once all three reviews have been completed, a final decision must be made on the application. This is where much of the work in this lab begins.

In the current Better Financials Underwriting process, a Senior Underwriter performs a manual final review in all cases. However, Better Financials would like to change this. They want to introduce greater control and scrutiny over high-value loans, and so they would prefer that a Vice President handle the review of all loans with a value higher than some threshold. They also want to ensure that there is a mechanism in place to notify the customer of the loan decision as soon as it is made. They do not wish to keep their customers waiting any longer than is absolutely necessary.

The Business Analysts at Better Financials have put together a Microsoft® Visio® map of the new Final Loan Review flow, which you will implement in this lab. You must take this from a simple picture of the process and turn it into a very dynamic model, one that can be used to communicate the details of the process to stakeholders, to analyze and make changes in the process should they be required, and to implement the process effectively in a Business Process Management (BPM) runtime environment. This is what Business Analysts working with BPM face every day in realizing the value of process for their organizations.

IBM Software


1.1 Importieren einer Visio Prozess-Map

1.1.1 Importieren eines Prozesses von MS Visio

We have prepared a business process map in MS Visio.

This could very well have been done by any business analyst, and looks like the following:

__1. Open a Windows® Explorer window, go to C:\labfiles\2.03, and double click on the file ‘Final Loan Review.vdx’

__2. Microsoft Internet Explorer® opens and shows the diagram. You may have to zoom in to better see the process model.

Dauer der Übung ca. 10 Minuten

IBM Software


__3. In MS Visio you can create your own shapes to represent various process objects types. In our scenario we have only used standard shapes, and these shapes have the following meaning:

__4. Now, you will import this MS Visio process map into IBM® WebSphere® Business Modeler

__5. Double-click the Business Modeler icon on your desktop to start WebSPhere Business Modeler with the right workspace.

IBM Software


__6. When IBM WebSphere Business Modeler is open, you will see the following:

__7. In order to import a MS Visio process map, select the project named ‘Better Financials’, click the right mouse button and select ‘Import’

IBM Software


__8. Select ‘Microsoft Visio (.vdx)’ and click next

IBM Software


__9. Go to the directory C:\labfiles\2.03, select the MS Visio File ‘Final Loan Review.vdx’ and import it into this project, click Next.

__10. On the next panel, select from the ‘Available Visio pages’ container the ‘Final Loan Review’ page and click Add.

IBM Software


__11. Click Next

__12. On the next panel you would see what MS Visio shapes are not yet known by the IBM WebSphere Business Modeler, but as this list is empty; all shapes used in the process map to be imported are known. You may however browse through the ‘Current mappings’ list to see how MS Visio shapes are mapped to WebSphere Business Modeler process objects. In order to move on with the lab, simply Click Finish.

IBM Software


__13. The import completes without any errors / warnings, simply click OK on the message box.

__14. After the import, open the ‘Processes’ Folder in your project ‘Better Financials’. The imported MS Visio process map is now available as a new process named ‘Final Loan Review’.

IBM Software


__15. Double click on the process ‘Final Loan Review’ to open the process diagram, which should look like this:

__16. In order to have it look better as presented after the import, right click on the diagram area (be sure not to have a process element selected), and click Auto-Layout Left to Right.

__17. Finally, in order to introduce the new Change Diagram Settings dialog, please verify that WebSphere Business Modeler presents the process diagrams in BPMN style. In the diagram editor, on the icon list at the top, click on the ‘Change Diagram Settings’ icon (this is by the way a new feature in IBM WebSphere Business Modeler v62 to have all diagram settings at one place).

IBM Software


__18. On the ‘Change Diagram Settings’ dialog box, verify that the radio button ‘BPMN’ in the ‘set style’ section is set, and finally click OK.

__19. Now your process diagram looks like that:

__20. Depending on some default settings in WebSphere Business Modeler, the process diagram enlarges more than one page (when printing it). To indicate this, WebSphere Business Modeler shows Page breaks. However, during the course of this exercise, Page breaks do not matter and therefore we will switch them off. To do click the Change Diagram Settings icon again, uncheck the Page breaks checkbox and click OK.

__21. Click Ctrl + S to save the process. This is the result after the import from MS Visio. In the next steps, we will complete this process to be used as a sub-process in the ‘Underwriting’ process.

IBM Software


1.2 Vervollständigen des Prozessmodells

1.2.1 Details der Aktivitäten definieren

Importing process maps from MS Visio is a powerful feature, simply because many process maps were developed in MS Visio. However, in terms of process completeness, almost all process maps developed in MS Visio only include activity name, decision nodes, and the connectors between activities and decision nodes. Information about relevant data – even when included here – is rare.

But – in order to use the process map for proper documentation, and / or process analysis (simulation) and process execution, more information is required.

In this part of the lab, you will therefore perform the following to complete the business process:

● Add a business item to the process input and output ● Assign this business item to all connections and activities ● Add a ‘Merge’ node to indicate the control flow ● Change the types of the activities to indicate whether these are done by business rules, or

humans, or by external services ● Assign roles to human tasks ● Assign duration information to all human tasks to prepare this process for analysis and

simulation

Now, let’s get started.

__22. First of all, if you think your diagram area is too big, right click in the canvas and click on ‘Compact Diagram’ – this actually is a new feature in WebSphere Business Modeler v62 to quickly compact the process diagram.

__23. If you have compacted the process diagram, it should look like this:


IBM Software


__24. The work product of this process ‘Final Loan Review’ is a mortgage application. Therefore we have to assign the data describing the mortgage application to the process. In order to speed up this exercise, we have already created a business item named ‘Mortgage Application’ – you can find it in the Business Items catalogue in your project:

__25. In order to assign the business item ‘Mortgage Application’ to the process, click in the process diagram (be sure not to click on any process object), then click on the ‘Inputs’ tab of the attributes view of the ‘Final Loan Review’, and click Add.

__26. Now, the default input is created.

__27. This is not the business item type we need, therefore click on the right hand side of the Associated data field, then click on the white box on the right-hand side of the Associated data field.

IBM Software


__28. On the ‘Type Selection’ dialog select ‘Complex type’, and select the business item ‘Mortgage Application’. Then click OK.

__29. Repeat last 4 steps in the ‘Outputs’ tab for the process ‘Final Loan Review’.

__30. If you look at the process diagram now you can see that the process looks like this:

IBM Software


Now, we will further complete the business process by looking at the tasks.

The first thing to do is to convert the activities imported from MS Visio to tasks of specific types in WebSphere Business Modeler. The three activities we will convert are: The activity named ‘Approval Level Required Rule’ has to be converted into a ‘Local Business Rules Task’, the two activities named ‘VP Review’ and ‘Senior Underwriting Review’ will be converted ‘Local Human Tasks’.

__31. Select the activity ‘Approval Level Required Rule’, click the right mouse button, then select ‘Convert to’, then select ‘Local Business Rules Task…’ command.

__32. Accept the defaults as presented in the upcoming dialog, and click OK.

IBM Software


__33. Now select the activity ‘VP Review’, click the right mouse button, then select ‘Convert to’, then select ‘Local Human Task…’ command:

__34. Accept the defaults on the upcoming dialog, add a description (e.g. the following: ‘Review results of the various reviews and decide to accept or reject the loan application.’), and click OK.

__35. Repeat the last 2 steps for the activity named ‘Senior Underwriting Review’ to convert this to a local human task as well, and add a description. (e.g. the following: ‘Review results of the various reviews and decide to accept or reject the loan application.’).

__36. Save your process model (Ctrl + S).

Now, in terms of specifying the task types we need to complete the process model, we’re done.

IBM Software


1.2.2 Einen globalen Service hinzufügen

Before we start to enhance / complete the imported process model, we will create a new service that will finally (at runtime) notify the customer about the decision taken by the reviewers. This service will later be implemented in Java™ – here in WebSphere Business Modeler we just prepare the process for this implementation.

As this service is not yet available in a service directory, as e.g. in WebSphere Services Registry and Repository, we will create this service right here in WebSphere Business Modeler.

__37. In the project tree, right click on the ‘Better Financials > Processes’ folder and select New and select Service.

__38. Name the service ‘Notify Customer of Decision’ and click Finish.

IBM Software


__39. All we need to specify at this point is the data input and output information. In order to do so, select the ‘Input’ tab in the Specification dialog of the ‘Notify Customer of Decision’ dialog.

__40. On the right hand side in the ‘Input settings’ section, click Add.

__41. The default business item ‘Text’ is assigned as Input. This is not the one we want, therefore click on the right side of the ‘Associated data’ field, and then click on the white box on the right-hand side of the field to specify the business item that should be assigned input.

IBM Software


__42. In the new dialog, select ‘Complex type’, select the ‘Mortgage Application’ business item and click OK.

__43. The business item is now assigned as input to this service:

__44. Now, repeat last 5 steps to specify the output settings. When done, the output settings look like this:

IBM Software


__45. Now, save the new service object.

__46. And close the service object.

__47. You will now have this new service object listed in the project tree:

IBM Software


__48. Now we will use this new Global Service in the process. Therefore, delete the activity called ‘Notify Customer of Decision’ by simply selecting the activity, then hit the ‘Delete’ key on your keyboard.

__49. Now, select this service ‘Notify Customer of Decision’ in the project tree and drag and drop it into the process diagram, best to the position where you have just deleted the activity. When done, your process looks like this (you may have to resize the task to see its full name).

__50. Finally, with all process tasks added to the process model, in order to finally complete the process, you will add a merge node. Add a merge node just before the service ‘’Notify Customer of Decision’ to merge the two branches that were opened by the decision ‘Who should review?’. To do so, select the ‘Merge’ node in the ‘Gateway’ section of the palette, and drag and drop it before the service ‘Notify Customer of Decision’.

IBM Software


__51. After that, your process looks like this:

__52. Now we will assign the business item to the Merge node. Click on the Merge, on its attributes view click on the output tab, and assign the business item ‘Mortgage Application’.

__53. This time, in order to speed up the business item assignments, the business item ‘Mortgage Application’ is automatically assigned for the inputs as well.

IBM Software


1.2.3 Ressourcen definieren und zuordnen

__54. You may notice that we have not yet added the people required to perform the human tasks yet. In order to do so, we assign roles as ‘primary owners’ for these human tasks. For the ‘Senior Underwriting Review’ task this will be the role named ‘Senior Underwriter’, and for the ‘VP Review’ task it will be the role named ‘Vice President’. Now, in your process tree, look at the ‘Resources’ folder, open the ‘Process Roles’ folder to see all available roles in the project:

__55. As you see that there is no ‘Vice President’ yet, that’s the one we create right now. To do so, right click in the ‘Process Roles’ folder and select the command ‘New ► Role’

IBM Software


__56. In the ‘Create a new role’ dialog, name the role ‘Vice President’, and then click on the button next to ‘Assign color’.

__57. On the ‘Color’ dialog, select a color, and then click OK.

__58. Click Finish on the ‘Create a new role’ dialog.

__59. Close the ‘Vice President’ role property window, as we do not have to add any further specifications to that role.

IBM Software


__60. Now we can assign the new role Vice President to the local human task VP Review. To do so, click on the task VP Review, open the Primary Owner tab in the Attributes view. When open, assign that role by selecting the Role radio button, and clicking Browse...

__61. Select the Vice President role and click OK.

__62. The Vice President just needs five minutes to work on that task. In the Time required section, specify 5 minutes.

IBM Software


__63. These 5 minutes defined above are for the time that the Vice President spends working on the task. We must also define the elapsed time for the task, which might be different. In this case, the durations are the same. Select the Duration tab of the task’s Attributes view, open the section for the Processing time, and specify 5 minutes.

You may wonder why you have to specify two values here. The reason is the following: The task processing time is the time the task takes to complete, whereas the resource required time is the time a resource is required for that task. In reality very often a task does not immediately complete once the resource is done, the task may have to wait for external events, or anything else. In order to model more accurate process models, the task processing time and the resource required time have to be modeled separately.

There is a slight chance that you won’t see the Duration tab. If this is the case, then you first need to select the More tab.

__64. Repeat last 4 steps for the Senior Underwriting Review local human task, but this time assign the role Senior Underwriter, and specify 5 minutes for the Time required in both the Primary Owner and Duration tabs.

__65. If you want to see that these changes are immediately effective in the process diagram, color the process by clicking on the Color by pull-down in the process editor toolbar, and then selecting Role.

IBM Software


__66. These two local human tasks are now colored with the color assigned to the roles and the process does look like that:

__67. In order to understand the meaning of the colors, click on the Color by pull-down again, then select Show Color Legend.

__68. Press Ctrl + S to save your work. (You may move the ‘Role Legend’ to a convenient place on the process diagram). We’re done with the specifications and assignments of the resources.

IBM Software


1.2.4 Den Datenfluss definieren

There are several ways to assign business items to connectors and tasks, and as your experience with WebSphere Business Modeler grows, you will notice that some business item assignments are even propagated automatically – depending on various modeling situations. In the course of this section of the lab we will do as few direct business item assignments as possible.

WebSphere Business Modeler comes with a number of modeling modes. All we have done so far was done in the modeling mode ‘basic’ – this is the entry modeling mode of WebSphere Business Modeler. Now, let’s switch to modeling mode ‘advanced’.

__69. In order to change to the Advanced modeling mode, go to the menu bar, click on Modeling ► Mode ► Advanced.

You will see, that on the process diagram the input and output stubs are added to the tasks. Now, let’s complete the process model by connecting the tasks and process control objects with each other.

__70. The first connection is the connection from the process input to the first task named ‘Approval Level Required Rule’. To do so, move the mouse over the process input pin, then click the left mouse button and connect the process input to the first task. Release the left mouse button when you are right over the task input pin:

IBM Software


__71. When done, the connection is shown, and the business item ‘Mortgage Application’ is automatically assigned to that connection:

Hint: If your process diagram is too compact, enlarge it horizontally by using this command:

Hint: If you need to move multiple process objects to the left, select all by simply drawing a frame around them while holding the left mouse button down, when all object are select, select one with the left mouse button and move the mouse to the left

Hint: if you need to change your mouse pointer from ‘Selection tool’ to ‘Create connection’ or vice versa, click on the corresponding icons on the palette:

IBM Software


__72. The Approval Level Required Rule task already connects to the decision node, but the Mortgage Application business item is not yet assigned. In order to assign Mortgage Application, drag and drop Mortgage Application from the Business items catalog onto this connector. After that, you will see that the tasks VP Review and Senior Underwriting Review are connected to the unassigned outputs of the decision node. This did happen because there was no data assigned on the connectors when imported from MS Visio:

__73. We will fix this, simply by re-connecting the two connectors to the black output stub created on each branch of the decision node. Do so by selecting the connector connecting the empty decision output to the input of ‘VP Review’, then re-link the connector’s start point from the upper stub to the lower stub:

The difference in the color of the input and output stubs (black / grey or white) indicates whether data is assigned to the stub or not: Black / grey indicates an assigned business item, white indicates that there is no business item assigned.

__74. Repeat this for the connector connecting the empty decision output to the input of Senior Underwriting Review.

__75. Now select the empty un-connected upper output pin of the decision and hit the delete key. Repeat this for the lower empty output stub. When done, the decision is correctly connected to the local human tasks, and the business item Mortgage Application flows via the decision node from the business rules tasks to the two human tasks.

__76. Connect VP Review to the merge node. You will see that the business item Mortgage Application is automatically assigned to all inputs as well as to the output of the merge now.

IBM Software


__77. Connect Senior Underwriting Review to the merge node.

__78. Connect the merge output to the Notify Customer of Decision service task.

__79. Connect the Notify Customer of Decision with the process output, and connect it with the Process End node.

__80. Finally, we want to better visualize at the decision output branches on the process diagram. Select the decision node, and in the Attributes view select the Output branches tab.

__81. Specify a new name Vice President for the first output branch, and the name Senior Underwriter for the second output branch.

IBM Software


__82. Now right click in the process canvas and select from the popup menu Auto layout left to right, and your process should look like this:

Hint: In order to better understand the process, we need to take care that all task names are fully displayed. This can be achieved by manually resizing the tasks. Select the business rules task, and resize the task e.g. by moving the lower right corner of the task to the right:

Repeat this for all the other tasks, until all task names are completely displayed.

__83. Next, we want to display more task details directly on the diagram. We can do so by displaying labels for each task. Click on the Change Diagram Settings button in the process editor toolbar.

IBM Software


__84. In the Change Diagram Settings dialog, select Labels and check the Display information labels on the diagram check box.

__85. Remember that the process element types in the process used are ‘Local business rules task’, ‘local human task’, and ‘Global Service’. For each of these element types, specify for the top label Roles, and for the bottom label Processing time. When done, this dialog looks like this:

IBM Software


__86. Scroll down in the dialog and uncheck the Include the attribute name in the label checkbox.

__87. Click OK when done.

__88. The process diagram now is very large. We can shrink the diagram if we agree not to display the business items on the connectors. To do so, click on the Change Diagram Settings button in the process editor toolbar, and have the check boxes in the Show on connections section checked as shown here.

__89. Click OK.

__90. Now, compact the process diagram again by selecting the Compact Diagram command from the popup menu.

IBM Software


__91. Press Ctrl + S to save your work. Your process will look like this:

IBM Software


Das folgende Kapitel 1.2.5 ist optional. Sie können es aus Zeitgründen auslassen, wenn Sie möchten. Es zeigt, wie individuelle Klassifizierungsmerkmale erstellt werden, um Aktivitäten im Prozess mit Klassifizierungsattributen zu versehen. Wenn Sie dieses Kapitel überspringen möchten, fahren Sie bitte bei „1.3 Calendars“ auf Seite 43 fort.

1.2.5 Arbeiten mit Klassifizierungsmerkmalen als Eigenschaft von Aktivitäten (opt.)

Now let’s look at another powerful feature of WebSphere Business Modeler: Classifiers. Classifiers can be used to classify tasks for whatever customizable reasons. Commonly used classifiers include whether a task is done manually, or automated, or if a task is outsourced and therefore we (as process owners) do not care much about the tasks implementation. Classifiers as well are used to indicate whether a task is important for the overall process quality, or process compliance, etc.

__92. Have a look at the classifiers made available in your project. In the project tree, scroll down to the Classifiers catalog and expand all sub-catalogs.

__93. In the ‘Final Loan Review’ process, we want to make use of the Classifier ‘User Role’ to better indicate the user role assigned to the tasks of the process. One of the tasks (VP Review) is assigned to the Vice President, which comes with the user role ‘Business Leader’. This classifier value is not yet available for the Classifier User Role and needs to be created first.

__94. Select the classifier User Role, click the right mouse button, and select New ► Classifier Value.

IBM Software


__95. In the Create a new classifier value dialog, enter the name Business Leader and click on the Assign color button.

__96. Select one of the green colors and click OK.

__97. Click Finish on the Create a new classifier value dialog.

IBM Software


__98. Now we will assign the classifier values of that classifier User Role to the tasks of the ‘Final Loan Review’ process, we do this from left to right. Select the Approval Level Required Rule activity, and in the Attributes view click on the Classifiers tab.

__99. Click Add.

__100. On the Select Classifier Value dialog, select the classifier value Automated for the User Role classifier and click OK.

You can see the result on the Classifiers list in the attributes view:

IBM Software


__101. Repeat last 3 steps and perform the following classifier value assignments for the User Role classifier:

● Assign Business Leader to the VP Review task. ● Assign Process Owner to the Senior Underwriter Review task. ● Assign Automated to the Notify Customer of Decision task.

__102. Now, all the tasks have a classifier value assigned, and we can color the tasks using the colors of the classifier values. Click on the Color by icon in the process editor toolbar and select Classifier ► User Role.

Your process now is colored with the classifier value colors, and the color legend has changed accordingly:

__103. Now, click Edit ► Undo, and the process is colored by role colors again.

IBM Software


__104. You can also use classifiers to place the tasks in swimlanes that correspond to classifier values. To do so, click on the Swimlane icon in the process editor toolbar and select Classifier…:

__105. On the Select classifier dialog select the classifier User Role and click OK.

__106. Accept to save the process if requested.

IBM Software


__107. Your process will look like this, now with the swimlane names assigned to the left hand side of the process diagram:

Depending on your audience when presenting and discussing the process, you will choose to color the process, to present the process using the swimlanes, and to add labels to the tasks – all the things you’ve done right here in the lab. Remember: Process models should allow your audience to immediately understand what it wants to understand, you as the process modeler know the process best.

__108. Now, switch back to free-form layout again.

IBM Software


1.3 Kalender

1.3.1 Working with Calendars – Creating the lunch exemption period

Comment – Please notice that calendars are called ‘timetables’ in WebSphere Business Modeler, but are called calendars in WebSphere Integration Developer and WebSphere Process Server. For the course of this workshop we will therefore use the term calendar wherever possible.

__109. In order to specify the working time of the resources, we need to assign calendars (called timetables in WebSphere Business Modeler) to the resources, in our case to the roles we have defined in WebSphere Business Modeler, as well as to the task’s schedule. We have already created one timetable for you, named the Standard Work Schedule. You may have a look at the timetable by simply double clicking on it.


IBM Software


__110. Have a look at the timetable Standard Work Schedule to understand its definition. You will detect that the working time starts at 8am, lasting for 9 hours, repeated every day. If you click on the Exemption periods tab, you will see that the weekends are excluded, which basically means that this timetable defines a working time from Monday to Friday, 8am to 5pm. (you may have a look at the ‘x_Weekend’ timetable by clicking on the timetable listed in the project tree)

__111. Now you will create a new timetable to exclude the lunchtime as an exemption period to the Standard Work Schedule. In the project tree, right click on the Process Timetable catalog and select New ► Timetable.

IBM Software


__112. Add the name x_Lunch and click Finish.

__113. In the x_Lunch timetable, specify that lunchtime is from 12pm to 1pm, repeated every day. To start, specify the repetition time for the timetable, just click on Select Time button. Accept the pre-selected defaults, namely ‘Number of times to repeat = Forever and ‘Repetition period’ = 1 day(s).

IBM Software


__114. Define that the start time is January 1st, 2009, 12am, GMT +1, when done, click OK.

__115. Next, specify the timetable’s start time, again to January 1st, 2009, this time 12pm.

__116. Next, we specify the time interval. Select Time interval from the list and click the Select duration button.

IBM Software


__117. In the Select duration dialog, specify one hour and click OK.

__118. That’s all we need to do, click Ctrl+S to save the new timetable ‘x_Lunch’, and close the timetable.

__119. In order to use this timetable x_Lunch as exemption time table for the Standard Work Schedule timetable, we need to add it as exemption timetable. Therefore, open the Standard Work Schedule timetable (if not open already), and click on the Exemption periods tab.

__120. On the Exemption periods tab, click Add.

IBM Software


__121. On the Select Timetable dialog, select x_Lunch and click OK.

__122. Press Ctrl + S to save your work. Once assigned, the ‘Standard Work Schedule’ timetable looks like that:

__123. All roles we have created for that lab have the Standard Work Schedule assigned. The only role that has not yet assigned that timetable is the one you have created, which was the role of Vice President. Open the Vice President role by double clicking on the role from the Project Tree.

IBM Software


__124. Click on the Availability tab, and click the Add… button.

__125. On the Select Timetable dialog, select the Standard Work Schedule timetable, and click OK.

IBM Software


__126. Click Ctrl + S to save the role. You have now assigned the time table to the Vice President role.

__127. As well, for the local human tasks, we want to specify when this task is made ready for people to work on. Therefore, select the local human task VP Review and in the Attributes view on the General tab in the Schedule section click on the Add button.

__128. Select the Standard Work Schedule timetable and click OK.

__129. Repeat last 2 steps for the Senior Underwriter Review local human task.

IBM Software


__130. Press Ctrl + S to save your work. The last thing to do is to use the new process Final Loan Review with the Underwriting process. We will do this in the next part of the lab.

IBM Software


1.4 Einbetten des Final Loan Review Prozesses als Unterprozess vom Underwriting Prozess

1.4.1 Using the new process Final Loan Review in the Underwriting process

__131. Finally, all we need to do is to use this process as a sub-process in the Underwriting process. Therefore, open the Underwriting process from the project tree by double clicking on the process Underwriting.

__132. In the Underwriting process, delete the human task named Final Application Review.

__133. From the Project Tree, select the Final Loan Review process and drag and drop it into the Underwriting process just before the Process End node.

__134. Now connect the Join output to the Final Loan Review process, accept to connect it to the Mortgage Application input, if asked.

__135. Connect the Final Loan Review process to the Underwriting process output, and create a second connection to the Process End node.


IBM Software


__136. Press Ctrl + S to save your process model. The final Underwriting process looks just like this:

__137. Now, compact the process diagram again by selecting the Compact Diagram command from the popup menu.

__138. Save the Underwriting process. (Ctrl + S).

When saving the Underwriting process, you will see that we have now one error in our project, displayed in the errors view:

This happened because we have deleted the Final Application Review task which was important for the definition of one of the instance metrics we have defined in the monitor model of the Underwriting process.

IBM Software


__139. Double click on the error to see the full error description. Read the description, when done, click OK.

IBM Software


__140. You will now repair this instance metric and assign it to the ‘Final Loan Review’ process. In the Business Measures view, in the instance metrics section, double click on the instance metric in error. The instance metrics name is Final Loan Review Processing Time.

IBM Software


__141. The Business Measure Details dialog opens. This is a dialog that comes with quite some settings, and you will learn more about it later in the lab when you specify new business metrics and work on existing ones. This time, all we quickly do is to repair this instance metric to finally complete this part of the lab with an error-free project. Look at the dialog, and you see the error is again displayed at the top. When scrolling down you see which part of the definition is broken:

IBM Software


__142. In the Instance Metric Calculation Details section you will see that the process element we have used before was deleted. We have to select a process element that is available to perform the calculation, and this element is our imported and updated Final Loan Review process. Expand the Process element drop down list and select Final Loan Review

.

__143. At the bottom of the Business Measure Details dialog, click OK when done.

__144. Save your changes (Ctrl + S). Look at the error view – the error is fixed!

IBM Software


1.5 Lotus Forms (optional)

In dieser Übung werden einige kleinere Änderungen dem Formular der Benutzermaske getätigt. Aus Zeitgründen haben wir die Änderungen bereits in der Übungsumgebung durchgeführt. Das Kapital 1.5 ist deshalb optional. Auf Wunsch können Sie mit dieser Übung die Formulare und den Editor anschauen und die Übung nachvollziehen. Wenn Sie möchten, können Sie gerne auch andere Änderungen am Design der Maske vornehmen. Spätere Übungen sind davon nicht abhängig.

1.5.1 Update the existing Lotus Form

__145. Open the Final Decision Form in the project tree by double-clicking it.

__146. The form should open, and launch a new Eclipse perspective, the Standard Lotus Forms Designer perspective. This perspective is intended for form layout adjustments only. We want to dig deeper into the formatting for this form. To do so, click the Open Perspective button in the upper right-hand corner and select Advanced Lotus Forms Designer.

__147. The first thing that we want to do is to ad a custom logo to the form. This is a great thing to do in any customer-facing demo, to show some personalization of the interface. We’ll place the logo on the left-hand side of the form title, moving the title text further over to the right. To start with, we must make some room for the logo. Click somewhere in the text atop the form that says Final Loan Review to select the text box.


IBM Software


__148. In the Properties view, go to the Appearance section and find the justify setting. From the pull-down, select right.

__149. The text is now right-justified, but it goes to the very edge of the form, which doesn’t look so good. Click the text again, which should allow you to edit the text. Place the cursor to the right of the “w” in “Review”, and enter a space. This space after the text will help pad the label from the edge of the form.

IBM Software


__150. Back in the Properties view, click in the fontinfo field, and click the T button to launch the Font dialog. Change the Size to 14, and click OK. We’ve now got enough room atop the form to fit the logo that we’ll use.

__151. From the Palette, select Image, and then click anywhere on the form editing canvas (the location that you click doesn’t matter, as we’ll move the image to the proper location after). When you click, a dialog should pop up.

IBM Software


__152. In the Image field, click the Browse button.

__153. Browse C:\Labfiles\2.03\Better Financials Logo.jpg, and click Open.

IBM Software


__154. Accept all other defaults by clicking OK.

__155. The logo should now be on your canvas, selected. In the Properties view, go to the General section and expand the itemlocation setting as far as you can.

IBM Software


__156. Change the x value to 9 and the y value to 13. These locations have been devised based on the spacing of the form and the size of the image. When you build a form, you’ll have to deal with location settings like this quite a bit, with some trial and error to find ideal locations for each element in the Form. Feel free to adjust these values if you think you can make it look better.

__157. Click on the white field to the right of the Credit Results label. This is the field where an underwriter enters their findings during the credit review. While it might be tempting to leave this field blank when we’re testing this process, in the actual implementation we should have this information provided by the time we get to the final review of the application, and subsequent people working on the process instance should not have the ability to change the value at all. Thus we need to ensure that there is some data in this field, and that it cannot be edited.

__158. To ensure that the field is always filled in, go to the Properties view and in the Format section drill down through format and constraints to find the mandatory field. Change the value of this field to on.

IBM Software


__159. To ensure that the field cannot be edited, move to the General section in the Properties view and find the readonly field. Change this value to on.

These mandatory and read only settings are appropriate for using the Final Loan Review process as a sub-process called by the Underwriting process. For the lab when we deploy Final Loan Review directly from Modeler, we will not set mandatory and readonly fields, as we’ll be running the process stand-alone and will need to fill in these fields at some point. We’ll use a different workspace for this, with the Form defined appropriately.

__160. Repeat last 3 steps for the Capacity Results and Collateral Results fields.

__161. Press ctrl + s to save your work. Close the editor for the form and return to the Business Modeling perspective.

IBM Software


1.6 Simulation (optional)

WebSphere Business Modeler enthält eine sehr mächtige Simulations-Engine. In der Übung wird diese verwendet, um den Prozess zu simulieren und mit Analysen auszuwerten. Die Übung nimmt ca. 25 Minuten in Anspruch. Aus zeitlichen Gründen ist diese Übungung 1.6 optional, wir werden im Wrap-up der Übung im Workshop kurz nochmals auf die Simulation eingehen und diese zeigen. Sofern Sie die Zeit haben, ermuntern wir Sie, die Simulation durchzuführen, andernfalls können Sie in Kapitel 1.7 auf Seite 85 fortfahren.

Now it’s time to run some simulations. Business users can use simulation to identify process bottlenecks and areas for improvement in current processes, and to prove that future state processes meet needs and expectations. Here we’ll keep things pretty simple, simulating our process and doing some basic analysis. In practice, customers would likely create a separate copy of the process to perform simulation on, leaving the initial process documentation model intact. But for simplicity, including the reduction of complexity when demonstrating this process to a customer, we’ll stick with a single version of the process model.

1.6.1 Präparieren des Prozesses für die Simulation

__162. The Underwriting process contains a Fork and a subsequent Join. While this is the proper visual modeling construct, it creates an issue that the Fork with two output paths has essentially created two process instances for every one input that it receives. The Join is only a control flow element, so it cannot combine the two business items (one from each path) into one. The subsequent activity in the process, in this case the Final Loan Review process, must be updated to expect two unique Mortgage Application business items, one from each input path of the Join. This is something that must be done when simulating a process with a Fork and Join, which is not too common (in many situations with parallel activities, a form and join can be avoided). To make updates to the input settings of the Final Loan Review process, we must open it. Do so now if it is not already open.

__163. Click in the whitespace of the process model, and then select the Attributes view and the Inputs tab.


IBM Software


__164. In the table, change the value in the Minimum column to 2. Also, change the Maximum value to 2.

__165. We’ve now changed the number of inputs required to activate the Final Loan Review process to 2, one each from the Collateral Review and Capacity Review tasks.. However, we still will pass two copies of the business item in to the first task in the process. That task needs to be prepared to receive two copies of the business item, but output only one copy. Start this by selecting the Approval Level Required Rule.

__166. In the Attributes view, select the Inputs tab. Like you did for the process itself in step d, change both the Minimum and Maximum values to 2.

__167. Press Ctrl + s to save your work. Once the save is complete, you should see an error on the Underwriting process. This is because we’ve changed the I/O details of the Final Loan Review process, which is contained inside of the Underwriting process. Switch back to the Underwriting process to resolve this issue.

IBM Software


__168. Right-click on the Final Loan Review process inside of the Underwriting process, and select Update Global Element.

__169. Click OK at the dialog that pops up.

__170. Press Ctrl + S to save your changes to the Underwriting process. The error should now be resolved.

IBM Software


1.6.2 Erstellen eines Simulation Snapshots

__171. In the Project Tree, right click the Underwriting process and click Simulate…

__172. We do not need to add any optional elements to the simulation snapshot, so on the window that pops up just click OK.

Note: These optional elements are in the modeling project, but are not directly used by the process being simulated. You may want to include them if they will be used indirectly in a simulation.

IBM Software


__173. Click Yes in order to test to ensure that all paths in the process have a stop node. This is important for the simulation to complete successfully, so although we know that we have all of the necessary stop nodes, always checking this is a good habit to get into.

__174. When the validation is complete, click OK.

The simulation snapshot should open, and in the attributes you should first see the Overview tab. The contents of the Overview tab used to be located in a tab within the process editor pane, but those tabs have been completely removed from Modeler 6.2 to reduce process editor complexity. As a result, this information has been moved to the Overview tab. This tab is intended to allow you to quickly make common changes to a simulation, like adjusting task durations and decision percentages, all from a single place. We’re not going to make any of these changes,

__175. Move on to the General tab. Next to the Process availability begins field, click the Edit… button.

IBM Software


__176. Change the date to January 1, 2009. This is the date that the simulation becomes available to run.

IBM Software


__177. Click OK when you’re done.

__178. Further down in the General tab, change the Random number seed to 2. This will ensure that each simulation is seeded the same way, and thus the same set of process cases will be executed.

__179. Change the Use resources’ time required as a task processing time radio button to No. We have introduced some wait times into some of the tasks to make them more realistic, but this means that we want to use the elapsed duration defined for each task, not the working duration for the roles associated with the task, when performing calculations.

IBM Software


__180. Select the Inputs tab, and click on the Input in the table. The default setting is for a single token (process instance) to be simulated. To begin changing this, click on the Edit… button next to the Number of tokens per bundle.

__181. The scenario we are simulating calls for 160 new mortgage applications per week, with a new batch delivered each day. There is the same number of new applications each day, so 160 divided by 5 equals 32 new applications each day. Under Use a specific number of tokens for all bundles, enter the value 32. This means that each time a set of new process instances is created, we’ll create not one but 32 unique instances of the process. Click OK.

IBM Software


__182. Next, click on the Edit… button next to the Total number of tokens.

__183. Under Generate a specific number of tokens in each simulation run, enter the value 160. This means that we’ll simulate 160 total instances of the process. With 32 tokens per bundle, we’ll create five bundles of 32 tokens to reach our 160 total tokens. Click OK.

__184. Scroll down to where the Time trigger radio button is already selected. Next to the Start time field, click Edit…

IBM Software


__185. Change the date to January 5, 2009, 8:00:00 AM. This is the first Monday of 2009, and we want to start receiving our new loan applications on Monday morning to simulate one work week. Remember your time zone settings from the General tab, and adjust here accordingly. Click OK when you’re finished.

__186. Click on the Edit… button next to Time between bundles.

IBM Software


__187. Change the value to 1 Day, being sure to change the default value of 1 in the Minutes field to a zero. Click OK when you’re finished.

You have now created a situation where 32 process instances will be created each morning at 8 AM. Since we have 160 total instances to create, this means that 32 instances will be created each morning for 5 days.

__188. Switch to the Resource Pool tab.

__189. Select the Loan Officer role, and to the right, under Quantity to generate for the selected role, de-select the Unlimited check box. This will enable the input field, where you should change the value to 5, so that there are 5 Loan Officers available to perform work in the process.

IBM Software


__190. Repeat last step for the other roles, entering the following values:

Role Value

Senior Underwriter 1

Underwriter 3

Vice President 1

__191. Press Ctrl + S to save your work.

IBM Software


1.6.3 Simulation ausführen

__192. Click on Simulation Control Panel tab.

__193. Simulations can be animated so that you may visualize the simulation behaviors inside the process model in real time. While this looks nice, it makes the simulations run far more slowly. Before running the simulation we should turn off this feature. From the menu in the upper right-hand corner of the Simulation Control Panel, select Setting.

IBM Software


__194. Under Animation settings, de-select the Display animation during simulation option. Click OK.

__195. Click the Run simulation button, which looks like a “play” button on a video player.

__196. The simulation should have ended around Friday, January 16, 2009 11:55:02 AM GMT+1, with an average duration of 3 days 17 hours 52 minutes 28 seconds 81 milliseconds. Your results may differ slightly, which is perfectly OK.

IBM Software


1.6.4 Analysieren der Simulations-Ergebnisse

We’ve run a simulation, but that alone doesn’t tell us too much. In our case, what it does tell us is that it’s taking too long to process loan applications, and we want to know why. We can perform Dynamic Analysis to get more information about what is really going on in this process. In the Project tree, you should see the simulation results that have been created (the name that you see on your machine will differ from the screen shot here, as the name includes the date and time the simulation was run).

__197. Right-click on these results and select Dynamic Analysis ► Aggregated Analysis ► Activity Duration.

__198. Click Yes when the Preprocessing Dynamic Analysis Data message pops up.

IBM Software


__199. You should see the Dynamic Analysis results in Modeler’s lower-right pane. Feel free to expand the column widths of the analysis results so that you can read all of the entries clearly. We generally look in the Average Delay Duration column, which tells us which activities in the process have the longest average wait from the time that a process instance is available to be worked on to the time that work actually commences. High delay duration is a sign of a potential bottleneck in the process.

Clearly the highest delay duration is for Underwriting, but that is the high-level process and thus is an aggregation of all delay throughout the process. We need to look at individual process activities.

__200. Look further down the analysis results, and you’ll notice that the three Review tasks (Review Capacity, Review Collateral, and Review Credit) each have a far greater average delay duration than other tasks in the process. Recall that each of these tasks is performed by an Underwriter, of which there are only three. Maybe this is part of the problem. Again, your results may vary slightly.

IBM Software


1.6.5 Prozess modifizieren und Simulation erneut ausführen

__201. Let’s see if a simple change to the Underwriting process will yield improved performance (in this case, we’re looking to decrease the average process duration). Based on the results of our analysis in the last section, it appears that there are not enough Underwriters available to the process. To create a few more, we don’t even need to change the model, just the simulation settings. Go back to the Attributes view and select the Resource Pool tab.

__202. Select Underwriter, and change the Quantity to generate for the selected role to 5.

__203. Press Ctrl + s to save your work.

__204. Switch to the Simulation Control Panel, and click the Run simulation button.

__205. When the simulation completes, you should see an Average duration that is very close to 1 day, which is a marked improvement over the previous simulation.

IBM Software


1.6.6 Verbesserungspotential für den zukünftigen Prozess

__206. To quantify just how much of an improvement this change to the process has made, right-click the results of your first simulation run, and select Dynamic Analysis ► Process Comparison Analysis ► Process Duration Comparison…

__207. In the Select Simulation Results window that pops up, select the results of your second simulation run, and click OK.

IBM Software


__208. In the next window, select All process instances, and click Finish.

__209. Click Yes when the Preprocessing Dynamic Analysis Data message pops up.

__210. In the results of the dynamic analysis, look in the Average Elapsed Duration column. The updated process took about 2 days 17 hours 24 minutes 24.356 seconds less on average, for a 72.78 percent improvement. Your results may vary slightly.

__211. Close the Dynamic Analysis view.

IBM Software


__212. Close your simulation snapshot

.

IBM Software


1.7 Modelling für die Prozessautomatisierung We now know what our future state process looks like, and it’s time to make the changes required to implement this process. The intention here is that the Underwriting process will be updated further in WID, but we’re preparing the Final Loan Review process to be deployed directly from Modeler, using the Interactive Process Design approach. As with the simulation section above, we would normally consider a separate copy of the process to define our implemented process in Modeler, but we’ll stick to a single model here.

1.7.1 Änderungen für die Simulation rückgängig machen

Dieser Abschnitt 1.7.1 ist nur notwendig, wenn Sie die Übung 1.6 Simulation durchgeführt haben. Andernfalls überspringen Sie 1.7.1 und fahren mit 1.7.2 auf Seite 89 fort.

Since we’re now preparing the processes for eventual execution in WebSphere Process Server, you should switch to Modeler’s WebSphere Process Server mode. You’ll see some errors, but don’t worry. These are a result of the process not yet conforming to the requirements for WPS mode. We will resolve these errors in the next few parts of the lab. There will still be errors on the simulation snapshot, but those can be safely ignored.

__213. From the Modeling menu in the menu bar atop the window, select Mode ► WebSphere Process Server.


IBM Software


__214. We made changes to the minimum and maximum inputs of a few activities in order to ensure proper simulation, but we must now reverse them. Open the Final Loan Review process and click in the whitespace of the process model, and then select the Attributes view and the Inputs tab.

__215. In the table, change the value in the Minimum column to 1. Also, change the Maximum value to 1.

__216. Select the Approval Level Required Rule.

IBM Software


__217. In the Attributes view, select the Inputs tab. Like you did for the process itself in step b, change both the Minimum and Maximum values to 1.

__218. Press Ctrl + S to save your work. Now, switch back to the Underwriting process to resolve the I/O mismatch that has been created.

__219. Right-click on the Final Loan Review process inside of the Underwriting process, and select Update Global Element.

__220. Click OK at the dialog that pops up.

IBM Software


__221. Press Ctrl + S to save your changes to the Underwriting process. The error that showed on the Final Loan Review process inside the process editor should now be resolved, and we’re back where we started before running a simulation. This is what we need to properly execute the process, as the executable process will map the two copies of data into one single piece of data before passing it along in the process.

Troubleshooting Ignore any other errors, they will get fixed in the later steps of this lab.

IBM Software


1.7.2 Definition der Task, um den Prozess zu starten

Still working in the Underwriting process, note that the first task in the process is called Provide Loan Information. This is where the initial information about the loan is entered into the system. We’ve documented this as a task because it is an activity that occurs in the process. From a business user’s perspective, it must be documented as part of the process, and it also must be accounted for during simulation. But at runtime, how will we implement this task? In our situation, it is the act of someone inputting this information that starts off our process. Thus, it is not a human task in the process, it is a process-initiating human task. We must delete it from the process diagram.

__222. Select the Provide Loan Information task, and press the Delete key on your keyboard.

__223. The next task, Review Credit, is now the first task in our process, and we must connect it to the input of the process. To do so, make a connection from the input of the Underwriting process to the input of the Review Credit task.

__224. But we still need a way to indicate the manual initiation of the process. Click in the whitespace of the Underwriting process, and select the Forms tab.

IBM Software


__225. What we can do is define the Lotus Form that was used in the Provide Loan Information task and associate it with the Underwriting process itself, so that the Form can still be used to initiate the process. In the table, select Input Criterion.

__226. Scroll down a bit, and next to the Input form field, click Browse…

__227. In the Select Form dialog, select the Loan Info Form, and click OK.

__228. Scroll back up to the table and expand Input Criterion. A new line is displayed below, that lists the corresponding output criterion for the process. Select Output Criterion.

IBM Software


__229. Select the Use input form as output form check box.

__230. In the dialog that pops up, click OK. This will ensure that the Form is associated with the process.


We have now done all that we can do in Modeler to define initiation details for a process. You may be surprised that the task we deleted, Provide Loan Info, was performed by a specific role, and yet we’re unable to provide a role or resource restriction to the process initiation activity. The ability to associate Forms to processes was designed with Interactive Process Design (aka Direct Deploy) in mind. To make it easy for any tester to initiate processes, it was decided that any user would be able to work with the process-initiating human tasks. Since we’re exporting the Underwriting process to WebSphere Integration Developer and will refine the technical details of the process further, we’ll make appropriate adjustments in WebSphere Integration Developer.

__232. Open the Final Loan Review process. We should associate a Form with this process as well, as it may be invoked independently of the Underwriting process. Repeat last 8 steps for the Final Loan Review process, but this time selecting the Final Decision Form.


IBM Software


1.7.3 Ersetzen des Join durch eine Map

Switch back to the Underwriting process. Recall back to the Simulation section of the lab, where we mentioned how a Join was the appropriate construct to use after the Review Capacity and Review Collateral tasks in the Underwriting process. While that statement was true for documentation and simulation of the process, the situation is different now that we plan on executing the process in WebSphere Process Server. Think about the behavior here. Review Capacity and Review Collateral take place in parallel. They can’t both work on the same piece of data at the same time, so each is working on a separate copy of that data. However, Review Capacity and Review Collateral will each modify one data field, Capacity Results and Collateral Results respectively. We need to merge these two results, from two different copies of the data, into a single business item (or variable, if you want to think about this in WebSphere Integration Developer terms).

__234. To start, delete the Join in the Underwriting process.

__235. In the Palette, expand the Data drawer (if it is not already open), and select the Map element. Drop it on the editing canvas in the spot where the Fork was previously located. Rename it as Map Data.

IBM Software


__236. Make connections from Review Capacity to Map Data, from Review Collateral to Map Data, and from Map Data to Final Loan Review, so that the end result looks like the screen shot below. In making the connections, be very careful to utilize the existing outputs of Review Capacity and Review Collateral, and the existing input of Final Loan Review, by pointing to the output or input itself, not the entire activity. You do not want to create new inputs or outputs on those activities.

__237. Make sure the Map Data is selected, and in the Attributes view select the Mapping tab. Click the Open Map editor button. A new editor will open in the upper right-hand pane.

IBM Software


This map will transform into a Business Process Execution Language (BPEL) Assign element, so keep that in mind. If we think about this the way it would behave in WebSphere Integration Developer, the first input listed would use the same variable that is passed on to the first output (in this case, the only output). Unlike in Modeler, we have variables in WebSphere Integration Developer, and since the same variable will be used for the first input and the output of the map, there is no need to do any mapping from the topmost input to the output. All that we need to do is identify what data we need out of the second output. Recalling back to the Underwriting process, Review Capacity is the first (topmost) connection to the map, and Review Collateral is the second. This means that we need to map the results of the collateral review to the output of the map.

__238. On Input:2 Mortgage Application, hover over the Collateral Results field and create a new wire that goes to the Collateral Results field of Output Mortgage Application. The default behavior on the connection is Move, which is what we want. Since this is the only piece of data that we need to get from the Review Collateral task, we’re done.

__239. Press Ctrl + S to save your changes in the Map Data editor, and close the editor.

IBM Software


__240. Also, press Ctrl + S to save your changes to the Underwriting process. At this point, we’re done with the Underwriting process.

Troubleshooting You don’t need to worry about the warnings on the Review Capacity and Review Collateral tasks, those will be addressed in WebSphere Integration Developer, as the tasks will be implemented differently depending on which lab we’re doing.

__241. Right-click in the white space of the process and select Auto-Layout Left to Right, to clean up the look of the alignment of the various process elements.

__242. Right-click in the white space again, and select Compact Diagram. This will ensure that the process model takes up minimal space on the canvas, and thus is easier to see all of the process at once on the screen.


__244. In a little while, we’re going to be using WebSphere Service Registry and Repository, so this would be a good time to start your server in anticipation of that. To do so, double-click the Start WPS shortcut on your desktop.

IBM Software


1.7.4 Definieren einer Geschäftsregel-Vorlage

__245. Open the Final Loan Review process. The first task in the process is the Approval Level Required Rule. We need to pass the result of that business rule, the determination of who will perform the final review and approval of the loan application, to the decision immediately after the task. We don’t have a field in the Mortgage Application business item to contain this value, because we don’t want it to show up in the various Forms throughout the process. So we need to create a second output from the task to the decision.

__246. Make a new connection from Approval Level Required Rule to Who should review? Be sure that the source of your connection is not the existing output of the task, but the task itself. By doing this, Modeler will create the new task output and decision input for you.

__247. By default, the new connection has no data associated with it. To fix this, right-click on the new connection and select Associate Data…

IBM Software


__248. Accept the default value, which is Text (string). Click OK. This is all that we need to do to ensure that there is a text variable output from the business rule, and available to be evaluated by the decision.

__249. Select the Approval Level Required Rule task. We need to create the actual business rules for this task. In the Attributes view, select the Business Rules tab. Click Add to create a new rule.

IBM Software


__250. In the Define Business Rule window, change the name of the rule to Approval Assignment Rule and the description to Defines who should be assigned to review a loan application.

__251. The basics of the rule that we’re trying to create is that, by default, all applications are reviewed by the Vice President. However, if the loan value is less than or equal to 10,000, the application will be reviewed by the Senior Underwriter. That value of 10,000 that denotes that point where the approver changes should be able to be modified at runtime, in Business Space. If we want the rule to be exposed to Business Space, we have to base it off a rule template, so we’ll start there. Select the Rule Templates tab, and then click the Add Template button.

__252. Change the Template name to Approval Value Threshold.

__253. The rule condition and action cannot be defined until we have some parameters to use in them, so we will skip past these fields and come back to them later. Move down to the Rule Parameters section. We’ll need to define parameters to use in our template. Click Add.

IBM Software


__254. Change the Parameter name to Threshold Value and the description to The loan value above which a Senior Underwriter can no longer perform approvals.

__255. In the Type field, change the value to Integer.

__256. Move down to the Rule template presentation section, and select the Customize the text for the rule template presentation radio button. In the field below, enter the first part of the custom text, If the value of the loan' is less than

__257. Enter a single space after the text you have entered, and then right-click and select Insert >> Threshold Value

__258. Enter another space, and then enter the remainder of the custom text, then review can be performed by the Senior Underwriter. The entirety of the custom text should look like the image below. This is the text that will be presented to the user at runtime if they wish to alter the business rule by manipulating the parameters.

IBM Software


__259. Now move back up to the Rule templates table, and click in the Rule condition field. Click the … button on the right-hand side of the field to launch the expression builder.

__260. In the Expression Builder, click Add to create a new expression to define the conditions for evaluating the rule.

__261. In the pull-down under First term, select Modeling artifact.

IBM Software


__262. In the First term details section, drill down to select Approval Level Required Rule ► Input - > Loan Value.

__263. Under Operator, select is less than or equal to.

__264. For the Second Term, select Modeling Artifact, and in the details section select Approval Level Required Rule ► Threshold Value.

IBM Software


__265. Click Apply, and then click OK.

__266. Now click in the Rule action field. Click the … button on the right-hand side of the field to launch the expression builder.

__267. In the Details section, scroll down and select Output:2.

IBM Software


__268. Under Value specification, select the Specific value radio button and enter the value SrUnderwriter.

__269. Click OK to return to the Define Business Rule window. We’ve now defined the business rule template that will allow the rule to be viewed and edited in Business Space.

IBM Software


1.7.5 Definieren der Geschäftsregeln

__270. In the business rule editor, switch to the If-Then Rules tab. Now we’ll start defining the actual rules that must be implemented.

In WebSphere Integration Developer we have the ability to create an Action Rule, which will allow us to initialize the rule with default behavior. While there is no formal Action Rule capability in Modeler, we can essentially do the same thing by creating a rule that is always evaluated. We’ll do so now.

__271. Click the Add Rule button, and name the new rule Default Rule. This rule will not utilize the template that we just created.

__272. Select the Rule condition field, and click the … button on the right-hand side of the field to launch the expression builder.

IBM Software


__273. In the Expression Builder, click Add.

__274. In the pull-down under First term, select Boolean, and underneath that the value True.

__275. Under Operator, select is equal to.

__276. For the Second term, select Boolean, and in the details section select True. We’ve created a condition that is always true, and so the action that we are about to define will always be executed.

IBM Software



__278. Now click in the Rule action field. Click the … button on the right-hand side of the field to launch the expression builder.

__279. In the Details section, scroll down and select Output:2.

__280. Under Value specification, select the Specific value radio button and enter the value VP.

IBM Software


__281. We also need to, in general, copy the input of the rule to the output. Since this rule will always be true, we can do so here. In the Details section, click Output, and under Value specification select the Expression radio button. Click Edit… to proceed with editing the expression.

__282. In the pull-down under First term, select Modeling artifact. Under First term details, select Approval Level Required Rule ► Input.

__283. Click Apply, and then OK.

IBM Software


__284. Back in the Specify Rule Action dialog, click OK to return to the Define Business Rule window. By default, the Vice President will be selected for review.

__285. In the Rule description field, enter By default, VP performs approvals.

__286. Move down to the Rule presentation section, and select the Customize the text for the rule presentation radio button. Again here, enter the text By default, VP performs approvals.

__287. We must create another rule that determines when the Senior Underwriter should approve the loan. Click the Add Rule button again, and name this rule Sr Underwriter Rule.

IBM Software


__288. Under Template name, select Approval Value Threshold from the pull-down.

__289. Click somewhere else, and a warning will appear. Click OK. The rule conditions and rule actions are pre-populated from the template definition.

__290. In the Rule parameter values section, change the Value field to 10000. This means that the Senior Underwriter will handle approvals for loans with a value of less than or equal to 10,000.

__291. Click OK.

IBM Software


__292. Back in the Business Rules tab, scroll down to the Default business rule pull-down, and select Approval Assignment Rule.


IBM Software


1.7.6 Definieren der Bedingungen bei den Entscheidungen

__294. Select the Who should review? decision, and in the Attributes view select the Output Branches.

__295. Select the Vice President output branch, and under the Expression section, click the Edit… button.

IBM Software


__296. In the Expression Builder, click Add to create a new expression.

__297. In the pull-down under First term, select Modeling artifact. Under First term details, drill down to select Processes > Final Loan Review > Who should review? > Input:2.

__298. Under Operator, select Is equal to.

__299. Under Second term, select Text. In the Text value field, enter VP.

IBM Software



__301. Repeat last 6 steps for the Senior Underwriter branch, this time producing the expression 'Processes.Final Loan Review.Who should review?.Input:2' is not equal to "VP". This is the negation of the first expression we defined, which ensures that all possible values will be handled by one of the two decision branches.


IBM Software


1.7.7 Formulare den Human Tasks zuordnen

__303. In the process editor, select the VP Review task. In the Attributes view, select the Forms tab.

__304. Next to the Input form click Browse… to look for an existing form to associate with the human task.

IBM Software


__305. In the dialog that opens, drill down to select the Final Decision Form. This is the form that we edited earlier in the lab. Click OK.

__306. We only want to have one form for the human task, not separate forms for the input and output. We’re able to do that because the human task uses the same business item for both its input and its output, and that same business item has also been used to define the data structure of the form. To define this preference, check the Use the input form as the output form check box.

IBM Software


__307. Repeat last 4 steps to associate the Final Decision Form to both the input and output of the Senior Underwriter Review human task.


IBM Software


1.7.8 Eskalationen für Human Tasks definieren (optional)

Dieser Übungteil 1.7.8 ist optional. Er zeigt, wie für die Personen-gebudenen Prozessschritte Eskalationen definiert werden können. Der nächste Übungsteil ist 1.7.9 ab Seite 121.

__309. Again select the VP Review task. In the Attributes view, select the Escalations tab.

__310. Click the Add button to create a new escalation.

__311. Change the name of your new escalation to One Business Day Escalation and the description to Escalate if not completed after one business day (8 business hours).

IBM Software


__312. We want to escalate if the human task is not claimed after 8 business hours. Thus, the default settings for the next two fields are acceptable. What we do need to change is the amount of time before escalation. In the After field, change the duration to 8 hours.

__313. We want the escalation to notify the Loan Officer. This may not be the most plausible approach possible, but it works for our simple scenario here. Next to Notify, click the Select… button.

__314. From the Name pull-down, select Members by role name.

__315. Select the Attribute value field next to *Name. Click the … box on the right-hand side of the field.

IBM Software


__316. In the dialog that opens, select Better Financials > Resources > Process Roles > Loan Officer, and click OK.

__317. Click OK in the Select Person to Notify dialog.

IBM Software


__318. Change the Notification type to Item on work list. We’ve now defined the escalation for the VP Review human task

__319. Repeat last 10 steps to create an identical escalation for the Senior Underwriter Review human task.


IBM Software


1.7.9 Web Service aus WebSphere Service Registry and Repository importieren (opt.)

Der Übungteil 1.7.9 und 1.7.10 ist optional. Er zeigt, wie bereits im Modeler ein Service aus der Service Registry eingebunden werden kann.

We currently have a Modeler service element in place to indicate the Notify Customer of Decision step in the Final Loan Review process. This is essentially a black box, tied to no actual implementation. However, we have a web service already in WebSphere Service Registry and Repository that will perform the step for us. We need to add that web service to our process model, which means that we will fully define the call to the web service right here in Modeler. There is no need for further elaboration or modification in WebSphere Integration Developer. We could also directly deploy the process to a test environment because we have used the definition for the actual service sitting in our repository.

__321. Select the Notify Customer of Decision element, and click Delete on your keyboard.

__322. If your server has not yet started, do not proceed until it does so. Once it is completely started, go to the Project Tree, right-click on the Better Financials project and select Business Service Search…

IBM Software


__323. A WebSphere Service Registry and Repository connection has already been created for you in your workspace, so just click Next.

IBM Software


__324. We will be searching for a business service, so keep the default setting of Business service (WSDL) selected. Since we have so few services in our registry, we can simply search on the wild card (*). In the search field, type *, and click Search.

IBM Software


__325. In the search results, select the NotifyCustomerofDecisionInterface.wsdl, and click the > button to add this interface to the list of files to be imported.

IBM Software


__326. Click Finish.

__327. Once the import is completed, go to the Project Tree and drill down as far as you can through the Business Services catalog, until you find the NotifyDecision service. Drag that service over onto the process model editor, dropping it in the same spot that you deleted the Notify Customer of Decision service.

IBM Software


__328. We have the web service within our process editor, but must connect it up to the process. Make a connection starting at the output of the Merge, being sure to grab the small circular output pin, and going to the input of the NotifyDecision service, being sure to target the small circular input pin. You will be unable to make the connection, and Modeler should display a message indicating that Input data and output data do not match. This is because the web service that is imported brings along its own, read-only business item called a Business Service Object that it uses to define its interface. Thus, we have a mismatch between the Mortgage Application business item we’ve used in the process, and the business service object that the web service uses to define its input and output. We’ll deal with this issue in the next section of the lab.

__329. Press Ctrl + S to save your work. You may stop WebSphere Process Server now (by pressing on Stop WPS shortcut on the desktop), if you like.

IBM Software


1.7.10 Geschäsftobjekt auf die Web Service Schnittstelle mappen (opt.)

Diesen Übungteil 1.7.10 sollten Sie nur ausführen, wenn Sie den optionalen Teil 1.7.9 durchgearbeitet haben. Wenn Sie 1.7.9 (Import eines Services aus WSRR) übersprungen haben, so brauchen Sie 1.7.10 auch nicht durchführen. We have two methods available for resolving the data mismatch issue between the business item we use in our process and the business service object that is used to define the NotifyDecision service interface. We can change part or all of the process to use the business service object, but that leads to some more problems. In addition to the rework this would require, we would have a situation where Modeler users cannot change the details of the data flowing through any part of the process that uses the business service object, as it is read only and defined by IT. The better option is to use data maps both before and after the web service, to map the interface to our existing business item. That way, the interfaces of no other activities need to change.

__330. To start, right-click in the space between the Merge and NotifyDecision, and select Insert Space > Horizontal to make room for one new map.

__331. Repeat previous step, but this time inserting space just to the right of the NotifyDecision service.

__332. Go to the palette and open the Data drawer, if it is not already open. Select the Map element, and drop one on the process editor, just to the left of the NotifyDecision service.

IBM Software


__333. Name the map BI to Service.

__334. Make connections from the Merge to BI to Service, and from BI to Service to NotifyDecision.

__335. Repeat last 3 steps to add another map between NotifyDecision and the process output. Call the map Service to BI.

__336. Make a connection from Service to BI to the Terminate (process end) node.

IBM Software


__337. Click the BI to Service map, and in the Attributes view, select the Mapping tab. Click the Open Map editor button.

__338. The mapping editor should open. The individual fields of the Mortgage Application business item and the MortgageApplication business service object are actually identical, other than the fact that the business service object has all spaces removed from the names. Unfortunately, because the objects themselves are not identical, we must map each individual field from one object to the other. On Input Mortgage Application, hover over the Customer Name field and create a new wire that goes to the CustomerName field of Output MortgageApplication. The default behavior on the connection is Move, which is what we want.

IBM Software


__339. Repeat previous step for all other fields in the input/output objects. The result should look like the screen shot below.

__340. Press Ctrl + S to save your work, and close the map editor.

__341. Repeat last 4 steps for the Service to BI map.

__342. Press Ctrl + S to save your work in the Final Loan Review process.

IBM Software


1.7.11 Aufräumen

__343. Click the white space of the Final Loan Review process, and in the Technical Attributes View, select the General tab.

__344. In the Process name field, enter FinalLoanReview. This will help to alleviate an error that currently exists in Modeler when exporting to WID. A resolution will be delivered in an upcoming interim fix, but it is best to do this now in case the system you’re working on does not include that fix.


IBM Software


1.8 Geschäftskennzahlen und KPIs hinzufügen

Workshop: Dieser letzte Übungteil 1.8 ist optional. Er zeigt, wie im WebSphere Business Modeler Metriken und Kennzahlen für das Monitoring definiert werden. Im Wrap-Up zu diesem Übungsteil werden wir im Workshop kurz auf dieses Kapitel eingehen. Dies ist für den Modeler die letzte Übung. Der nächste Übungsbereich zum WebSphere Integration Developer beginnt ab Seite 152.

You can now specify additional details for your business measures in WebSphere Business Modeler, so that you can run the monitoring information on a WebSphere Business Monitor server without implementing the low-level technical details in the WebSphere Business Monitor development toolkit. To use this feature, you use predefined business measure templates to specify instance metrics, and you base your aggregate metrics and key performance indicators (KPIs) on those predefined business measures

In this part of the lab, you will therefore perform the following steps to add business measures to the Final Loan Review sub process:

● Add business monitored values to the Final Review process

These measures will collect actual values as the process runs to update later on the artifacts in WebSphere Business Modeler for accurate simulations.

● Add a KPI from the library to the Final Review process

As a sample we will add a KPI ‘Average e-mail response time’ from the new V6.2 KPI Library and base it on the duration of an external email service.

● Add basic metrics populated from the business item

As a sample for drilldown in the monitor widgets we will assign the ‘Loan Type’ field from the Business Item input to an instance metric. This metric is added as dimension to the aggregation metrics.

● Add KPIs with daily cycle periods

For management purpose it is important to know how many new reviews are initiated daily and how many cases needs Vice President review. We will add KPIs named ‘Number of VP Reviews per day’ and ‘Number of Loans Reviews per day’

● Check the measures and KPI’s already predefined in the main Underwriter process.

We have setup for you a set of useful KPIs for the Underwriting process. These KPIs and measures will be used in later labs for analysis to gain insights and act on certain situations.

Now, let’s get started.


IBM Software


1.8.1 Zu überwachende Werte definieren

__346. Open the Final Loan Review process and click on the ‘Business Measures’ tab. In addition click into the empty white space of the process view to get focus on process level. The empty Business measures summary view shows up.

IBM Software


__347. Click on the Monitored Values tab and mark the checkboxes for Processing Time on Final Loan Review, Senior Underwriter Review, VP Underwriter Review and in the % Per Branch column on Who should review?

Note: The Monitored Values tab is used to identify attributes so that WebSphere Business Monitor can collect actual values as the process runs. You can use the real-life values of those attributes to update the values of the attributes in WebSphere Business Modeler. This information improves the accuracy of your model and simulations by providing realistic and accurate data derived from running the process. These attributes generate business measures in your monitor model that can be generally used for monitoring business performance.

__348. Let’s have a look at the generated measures. Switch back to the Business Performance Indicators tab and expand the Instance Metrics and Aggregated Metrics tab. All average time values and branch percentage values used in modeler for simulation have been generated.

IBM Software


1.8.2 Eine KPI aus der KPI Bibliothek hinzufügen

__349. Let’s add a new KPI from the KPI Library. Click on KPI Library…

Note: The key performance indicator (KPI) library consists of a set of typically used KPIs that are hierarchically structured and categorized according to the type of process that they apply to. When you choose a KPI from the KPI library, it is added to your monitor model. The KPI library is based on APQC’s Process Classification Framework (PCF). APQC is a member-based nonprofit organization that provides benchmarking and best practices for approximately 500 organizations worldwide in all industries. PCF organizes operating and management processes into 12 enterprise-level categories and more than 1500 processes and associated activities. PCF gives organizations a shared language for communicating with each other. For more information, see http://www.apqc.org/.

__350. Expand 5.0 Manage Customer Service (10006) and select Mange Requests, Inquiries, Compliants and mark Average email response time in hours. Click OK to finalize the selection.

IBM Software


__351. Expand KPIs and select Average email response time in hours. Click the Edit Details button.

__352. Note, the generated KPI Average email response time in hours is not complete and has no KPI Calculation Details specified. In the next steps we will generated the basic measures for the KPI calculation. For now we will leave the KPI by clicking the OK button.

Note: Selections on the KPI Library (APQC process classification standard) generate just KPI definitions in Modeler. All the basic instance metrics needed to build the KPI are not generated! So in the next steps we need to build an Instance Metric that captures the e-mail response duration. Assumption: For this workshop simplification we assume here the external service ‘Notify Customer of Decision’ does implement send E-mail and wait for response. Therefore the elapsed duration to complete the service is a good enough approximated value for e-mail response KPI calculation.

IBM Software


__353. Right click in the process diagram on NotifyDecision Create Business Measure Predefined Elapsed Duration

IBM Software


__354. Check the Business Measure Details page. Click OK.

Note: Business Measures can be created right from elements in the process diagram as well as from the Business Measure summary page in the model. In the next steps we will assign ‘Notify Customer of Decision Elapsed Duration’ to the ‘Average email response time’ KPI

__355. Double click on the KPI Average email response time in hours

IBM Software


__356. In the Business Measure Detail page select Specify a target type and value and select Duration as Type. Select Target Value 2 days.

__357. In the section KPI Calculation Details mark Specify how to calculate the KPI select NotifyDecision Elapsed Duration. Click the OK button to close the KPI.

IBM Software


1.8.3 Eine Metrik hinzufügen, die auf dem Geschäftsobjekt basiert

Now we are going to add a new instance metric that contains the information on the Loan Type. This metric will later on be assigned as a dimension to all Aggregate metrics, to allow drilldown in the monitor reports and dimensions widgets (dashboards).

__358. Click on the Add... button in the in the Business Measures Summary table to open up the Business Measure Details page.

__a. Enter Loan Type for Name

__b. Select Type Instance metric.

__c. In the Instance Metric Calculation Details section mark Specify how to calculate the instance metric checkbox.

__d. For ‘Using a predefined business measure template for a process element’ select in the drill down boxes Business Item Input as the Template, Final Loan Review as the process element and Loan Type as the attribute.

__e. Finish the definition with the OK button.

IBM Software


Note: We have added an instance metric that gets populated at a defined point (input or output) in the flow by the actual value of the business item. This feature became first available with version 6.1.2.

IBM Software


1.8.4 Eine KPI definieren, die die Anzahl der Loan Reviews pro Tag überwacht


__a. As Name enter Number of Loans Reviews per day

__b. Mark the KPI check box as type.

__c. For Description enter This KPI shows how many new Loan Reviews are initiated per day

__d. In the Target Type and Value section mark the Specify a target type and value check box.

__e. As type select Number and enter 50 as Target value.

IBM Software


__360. In the section KPI Calculation Details mark Specify how to calculate this KPI. On ‘Instance metric to aggregate’ click the New… button and enter Loan Review State as name. Click OK to close the window. For Aggregation function select Count.

Note: Loan Review State is a new metric we will later on finalize to contain the process state of the sub process. Since we use this metric for aggregation just as count to sum up the daily number of cases the instance metric content is not relevant for the KPI calculation!

IBM Software


__361. In the section Time Period for Data Collection mark the checkbox Specify a time period over which the business measure will be monitored. Mark Repeating and select Daily as Period type. For Base period on mark the radio button Period in progress. To finalize the KPI click the OK button.

IBM Software


1.8.5 Eine KPI definieren, die die Anzahl der VP Reviews überwacht


__a. Enter for Name Number of VP Reviews per day

__b. Select KPI as type.

__c. Enter for Description This KPI shows the number of VP review cases per day

__d. In the Target Type and Value section mark the Specify a target type and value check box

__e. Select Number as Type and enter 4 as Target value.

IBM Software


__363. In the Range section select Specify range details and Actual value. Add the ranges as shown in the screenshot below. (Low 0 - 2, Normal 2 - 6, High 6 – 20)

__364. In the Alerts section select Specify when to send an alert and the action to take as a result. For a new alert click the Add button and use the default name Number of VP Reviews per day Alert.

Note: Alerts can not be finalized in WebSphere Business Modeler, this need to be done in the Monitor Toolkit.

IBM Software


__365. In the KPI Calculation Details section mark the checkbox Specify how to calculate this KPI and Based on an instance metric and an aggregation function. Select in the drop down box Who should review? Vice President Branch taken and Count as Aggregation function.

__366. In the section Time Period for Data Collection mark Specify a time period over which the business measure will be monitored and Repeating. Select Daily as Period type. For ‘Base period on’ mark the radio button Period in progress.

IBM Software


__367. In the KPI Data Filter section mark the checkbox Specify data filters to limit the values….. Click the Add button and select for instance Metric Who should review? Vice President Branch Taken. For operator select Equal to and for Values to include enter True. To finalize the KPI click the OK button.

Note: In the KPI Data Filter section you can specify filters to limit the instances that contribute to this KPI calculation.

IBM Software


1.8.6 Die Kennzahl ‘Loan Review State’ mit dem Prozessstatus verknüpfen

__368. In the Business Measures Summary table double click on the instance metric Loan Review State to open up the Business Measure Details page. In the Instance Metric Calculation Details section mark the checkbox Specify how to calculate this instance metric and Using a predefined business measures template.. Select in the drop down boxes State as Template and Final Loan Review as process element. Click the OK button to finalize it.

Note: The template State captures the WPS process or task state in the instance metric. Remember, we used this metric for counting in the KPI Number of loan Reviews per day.


IBM Software


__370. Add a Dimension to Aggregate Metrics: In the Business Measures Summary table double click on the Aggregate Metric Average Final Loan Review Processing Time. Scroll down to the Dimension for Analysis section and mark Specify the dimension that will be available..

__a. Click on the Add button to add the entry in the table Final Loan Review Dimension. Select as instance metric Loan Type.

__b. Click on the Add button to add a second entry in the table. Select as instance metric Loan Review State.

__c. To finalize the dimension definition clicks the OK button.

Note: Now you can add and finalize dimensions to Aggregate Metrics in Modeler. This allows drilling down in the monitor dashboard on the collected data for analysis. When you add a dimension to one of the aggregate metrics it is added to all of them.

IBM Software


1.8.7 Betrachten der bereits definierten Kennzahlen im Underwriting Prozess

To save time in the workshop we have setup for you a set of useful KPIs for the Underwriting process. These KPIs and measures will be used in later workshop labs to analysis.

__371. Make yourself familiar with the already defined measures in the underwriting main process

__372. Close Modeler when you’re finished.

Herzlichen Glückwunsch! Die erste Übung ist damit abgeschlossen.

IBM Software


Übung 2 WebSphere Integration Developer - Prozessintegration

Lab Introduction In this exercise you will take on the role of the Integration Developer. The Business Analysts have designed a business process and provided as much implementation detail as they are able to. It is up to the Integration Developer to complete the implementation details. In this part of the lab, you will use IBM® WebSphere® Integration Developer 6.2 to replace an existing Java component implementation for the NotifyCustomerofDecision task in the Final Loan Review process with a Web Services implementation. After the implementation is complete you will deploy the process to the runtime environment and run tests against it. Your organization has already created several reusable business services and registered them with WebSphere Service Registry and Repository (WSRR). You will search WSRR for a service’s Web Services Description Language (WSDL) binding/endpoint document and import it into your project workspace for use to complete the implementation for the Final Loan Review process.

Once the WSDL document has been retrieved you will then look for the corresponding interface specification document that has been stored in Rational Asset Manager. This document will provide you specific information that is required to invoke the service. While WebSphere Service Registry and Repository manages and governs deployment artifacts and service metadata such as WSDL files, XML Schema Definition (XSD) files, and generic concepts representing service metadata, Rational Asset Manager provides the ability to manage development and design-time assets such as design documents, test documents, development artifacts, and other assets and provides governance for those assets.

Rational Asset Manager provides a means to organize assets to make them easily searchable and manageable for the enterprise. An asset consists of asset metadata and the asset artifacts themselves. Rational Asset Manager goes above and beyond the capabilities of version control systems by providing the ability to assign metadata to the asset and to group related physical artifacts under a given asset as well as the ability to associate related assts to facilitate searching and impact analysis. The NotifyCustomerofDecisionServiceDesign asset consists of associated asset metadata such as the description assigned to the asset, keywords, the categories the asset is assigned to, and related assets. The asset also contains physical artifacts including a Microsoft® Word document for the Service Specification and a UML diagram.

An asset that contains physical artifacts stored in Rational® Asset Manager can also have those individual physical artifacts for a given asset linked to versions in a version control system such as Rational ClearCase® or CVS. An asset is assigned a version number in Rational Asset Manager. For example, version 1.1 of the NotifyCustomerofDecisionServiceDesign asset may contain two physical artifacts: one artifact linking to version 1.0 of the UML model stored in Rational Clearcase and the other artifact linking to Version 1.1 for the Microsoft Word Service Specification document that is stored in Rational Clearcase. The diagram below illustrates an example of mapping physical artifacts within an asset version to versions of the artifacts in Rational ClearCase or CVS.

IBM Software


Below is the Final Loan Review process. As previously discussed, the NotifyCustomerofDecision task implementation will be changed to a Web Service implementation in this section of the lab.

IBM Software


Implementation:

1. Open a workspace that contains the model that was exported from Modeler and has implementations that have been partially completed in WebSphere Integration Developer. The workspace will also contain the associated Monitor model.

2. Search WSRR and get the WSDL binding/endpoint document for the NotifyCustomerofDecisionServiceLocal service.

3. Find an asset in Rational Asset Manager containing the interface specification documentation for the NotifyCustomerofDecision interface.

4. Wire the components replacing the NotifyCustomer Java™ component with the NotifyCustomerofDecisionServiceLocal Web service endpoint.

Results: The Better Financials business process will be implemented to the point where it can be deployed and executed.

The student will gain the following experience retrieving design time and runtime service artifacts to complete the implementation for the Final Loan Review process.

1. Searching WebSphere Service Registry and Repository to find service endpoints. 2. Retrieving an asset from Rational Asset Manager that contains interface specification

documentation and using the documentation to understand how to invoke the service endpoint.

IBM Software


2.1 Starten des Servers

2.1.1 Sicherstellen, dass DB2 Datenbank gestartet ist

__373. On the taskbar, right click on the DB2® icon and select Start (DB2) as shown below. If Start (DB2) is grayed out and the DB2 icon is all green with no red line thru it, then the DB2 instance is already started. If prompted by the Check Point Integrity Client firewall, check to allow this action and remember this setting.

__374. Wait until DB2 is started (The DB2 icon is all green with no red line thru it).

2.1.2 Starten von WebSphere Process Server (if falls noch nicht in Übung 1 gestartet)

__375. Click the Check WPS Status icon on the desktop to see if WPS is already started.

__376. If WPS is not started, then click the Start WPS icon on the desktop.

__377. Wait for WPS to start. The command window below will disappear once WPS is started.


IBM Software


2.2 Starten von WebSphere Integration Developer

2.2.1 Starten von WebSphere Integration Developer

__378. Start WebSphere Integration Developer by double-clicking Integration Developer on the desktop:

__379. Wait for the workspace to start before you proceed to the next step.


IBM Software


2.3 Erkunden der Integrations-Artefakte im WebSphere Integration Developer

Im WebSphere Business Modeler haben Sie bereits etliche Dinge definiert, die sich nun im WebSphere Integration Developer wiederfinden. Dazu gehört z.B. die Prozesslogik, die Human Tasks, die Business Rules, eingebundene Web Services etc. All diese Dinge könnten Sie auch direkt im WebSphere Integration Developer implementieren. Der Grundsatz ist: es werden so viele Elemente wie möglich aus der Prozessmodellierung übernommen, um die IT Integration so zügig wie möglich durchführen zu können.

In diesem Kapitel entwickeln Sie nicht selbst die gesamte Integration, sondern Sie können die wichtigsten Elemente des WebSphere Integration Developer anhand des Beispielprozesses kennenlernen und sehen, was beim Import von Modeler in WID erzeugt wurde.

2.3.1 Projektstruktur im WebSphere Integration Developer

__380. Auf der linken Seite sehen sie unter zwei Bereiche: Integration Solutions und Projects. Für umfangreichere Integrationsanwendungen können Sie unter Integration Solutions Übersichten der gesamten Integrrationslösungen erstellen. Dies ist in diesem einfachen Szenario nicht erforderlich. Unter Projects befinden sich die Projekte aus unserer Übung:

für die eigentliche Prozessintegration und

für die implementierung des NotifyCustomer Services

__381. Eine Best Practise ist, die Entwicklungsprojekte wie in der klassischen Entwicklung mit Namenskonventionen zu benennen. Häufig wird dabei folgendes Prinzip angewendet:

• BetterFinancials ohne Zusatz ist das Hauptmodul der Integrationslösung und enthält den Prozess.

• BetterFinancials_impl bezeichnet das Modul, das zusätzliche Serviceimplementierungen enthält. Dadurch werden diese vom Prozess entkoppelt.

• BetterFinancials_lib ist ein Library-Modul

• BetterFinancials_Monitor enthält die Artefakte die für das Prozessmonitoring relevant sind und vom Modeler erzeugt wurden (Event-Definitionen und Monitor-Modell)

__382. Sie können die Projektstruktur erkunden und z.B. einmal das Modul BetterFinancials öffnen.


IBM Software


2.3.2 Assembly Diagramm

Jedes Modul (außer Lib-Module) enthält als zentrales Element ein einziges sog. Assembly Diagramm. Dieses repräsentiert letztlich eine ablauffähige Integrationsanwendung, die auf dem Process Server Deployed warden kann. Im Assembly Diagramm werden die unterschiedlichen Komponenten (Adapter, Prozess, Rules, Web Services, Messaging Schnittstellen etc.), die bei der Integration beteiligt sind „zusammengesteckt“.

__383. Öffnen Sie das Modul Better Financials im Projektbaum und klicken Sie doppelt auf Assembly Diagram.

__384. Es öffnet Sich das Assembly Diagram unserer Better Financials Prozessanwendung. Sie können die einzelnen Elemente erkunden und sehen die Struktur der Integrationsanwendung:

Underwriting BPEL Prozess

Prozess-Interface

Final Loan Review BPEL Prozess

Business Rule Komponente

Integrationspartner Interface

Aufruf eines externen Service

IBM Software


__385. Im Assembly Diagramm hätten Sie die Möglichkeit, weitere Integrationskomponenten anzubinden oder die bestehenden Integrationslösung zu verändern. Dazu steht Ihnen auch die unterschiedlichsten Technologien in der Palette und bei der Definition der Schnittstellen zur Verfügung:

IBM Software


2.3.3 BPEL Prozesseditor

Neben dem Assembly Diagramm ist für die Prozessintegration natürlich der Prozess-Editor ebenfalls sehr wichtig. Mit Ihm läßt sich die ausführbare Prozesslogik mittels BPEL visuell definieren oder das vom Modeler importierte Prozessmodell verändern.

__386. Klicken Sie im Modul BetterFinancials im Assembly Diagramm doppelt auf FinalLoanReview

__387. Bestätigen Sie die Warnung mit einem Klick auf ‚Yes’. Die Warnung signalisiert, dass das Modell in WebSphere Business Modeler modelliert wurde. Es öffnet sich anschließend der Prozesseditor.

__388. Sie können den Prozesseditor erkunden. Die Attribute des jeweils selektierten Elementes werden unter dem Prozesseditor in der Sicht ‚Properties’ angezeigt.

BPEL Palette

Prozess- Logik

Prozess- Interface

Externe Partner-services

Prozess-variablen

Aufruf

Human Task

IBM Software


2.3.4 Human Task Editor

Der Editor für Human Tasks erlaubt es, alle Einstellungen zu personenbezogenen Aktivitäten im BPEL-Prozess zu definieren oder zu ergänzen. Wichtig ist dabei u.a.:

• Verantwortlichkeiten / Rollen bzgl. verwendeter User-Registry (People Assignment)

• GUI Settings

• Eskalationen

__389. Klicken Sie im Prozesseditor für FinalLoanReview doppelt auf die Human Task VP Review, um diese zu öffnen. Bestätigen Sie die Warnung mit einem Klick auf ‚Yes’. Die Warnung signalisiert, dass das Modell in WebSphere Business Modeler modelliert wurde. Es öffnet sich anschließend der Editor für die Human Task.

__390. Sie können die Einstellungen für diese Human Task erkunden. Die Attribute des jeweils selektierten Elementes werden unter dem Prozesseditor in der Sicht ‚Attributes’ angezeigt.

Interface der Human Task

Personen-zuordnung, Rechte

GUI Settings (falls notw.)

Eskalation definieren

Detail-Attribute

IBM Software


2.3.5 Weitere Elemente (optional)

Wenn Sie weitere Elemente erkunden möchten, die sich in unserem Beispiel im WID befinden, können Sie folgende Hinweise nutzen:

• Business Rule Gruppe: Doppelklick auf BetterFinancials (Modul) ► Integration Logic ► Rule Groups ► ApprovalLevelRequiredRule Business Rule: Doppelklick auf BetterFinancials (Modul) ► Integration Logic ► Rule Logic ► ApprovalAssignmentRule

• Datentypen, hier: MortgageApplication Objekt unter BetterFinancials_lib ► Data Types ► businessitems ► MortgageApplication

• Alle Schnittstellen-Definitionen sind unter BetterFinancials_lib ► Interfaces zu finden.

IBM Software


2.4 Services aus WebSphere Service Registry and Repository einbinden

2.4.1 Die WSRR Verbindung überprüfen

__391. Open the Resource perspective. Click the OK button.

__392. Go to Window ► Preferences ► Service Registry ► WSRR Locations.


IBM Software


__393. Examine the Preferences display to ensure a WSRR location is configured for the WSRR Eclipse plug-in as shown below.

__394. Close the Preferences display.

IBM Software


2.4.2 In WSRR nach WSDL Dokumenten suchen

__395. Navigate to the Service Registry view. Note, if the Service Registry view is not visible, then select Window ► Show View ► Other and select Service Registry. Click on the OK button. The Service Registry view should then appear at the bottom right.

IBM Software


__396. Right click on WSDL Documents and select Retrieve WSDL documents.

__397. The Querying WSRR window appears. Click the OK button.

IBM Software


__398. The Service Registry view is now populated with the list of WSDL Documents from WSRR. You can see that you can now expand WSDL Documents in this view.

The BetterFinancials_impl module in the workspace is currently incomplete and requires the addition of the service endpoint that has been previously published to the WSRR server.

2.4.3 Einen Web Service aus der WSRR importieren in das BetterFinancials_lib Modul

For the BetterFinancials_lib module we need to add the NotifyCustomerofDecisionServiceLocal service endpoint. If you are not planning to use WSRR in your company, it should be clear, that any WSDL / XSD / Web Sevice can be used and integrated by importing the corresponding WSDL / XSD / WS-* file.

__399. In the Service Registry view, expand WSDL Documents and right click NotifyCustomerofDecisionServiceLocal.wsdl. Select Import Document.

IBM Software


__400. Navigate to BetterFinancials_lib ► Processes ► notifycustomerofdecision in the project tree.

__401. Click Finish.

__402. Close the Resource perspective.

IBM Software


__403. Open the Business Integration perspective. The WSDL file should now appear under Web Service Ports within the BetterFinancials_lib project in the Business Integration perspective.

IBM Software


__404. Expand BetterFinancials_lib ► Web Service Ports ► processes/notifycustomerofdecision. The imported WSDL port appears as NotifyCustomerofDecisionLocalPort.

IBM Software


2.5 Review der NotifyCustomerofDecision Schnittstellenspezifikation in Rational Asset Manager (optional)

Prior to replacing the NotifyCustomerofDecision task with a Web Service implementation, the integration developer may need to review the interface specification document to ensure an understanding of the service interface. You will now review the interface specification document for the NotifyCustomerofDecisionServiceLocal service. Rational Asset Manager is used in this section of the lab to search for design-time and development-time artifacts.

2.5.1 Starten von Rational Asset Manager

__405. Click the Start RAM icon on the desktop.

__406. A command window will appear while RAM is starting. The command window will disappear once RAM is started.


IBM Software


2.5.2 Review der Service Spezifikation für den NotifyCustomerofDecisionLocal Service.

__407. Open the Asset Management perspective where you will have access to the RAM repository using the Eclipse interface.

IBM Software


__408. The Asset Management perspective is displayed. There may be no assets initially displayed in the list of assets below. This is fine as you will enter asset search criteria in the next step.

IBM Software


__409. To search for an existing service implementation related with the NotifyCustomerofDecisionServiceLocal service endpoint, go the “Asset Search” view, and search for the phrase “NotifyCustomerofDecision”. Additional assets may show up in your list. Rational Asset Manager will also display assets related to the asset you searched for.

__410. Right click on the asset and click on import.

IBM Software


__411. Click on the Next button on the Import related assets screen. This Import related assets screen gives you the opportunity to select which related assets you want to import as well. You will not import any of the related assets.

IBM Software


__412. Click on the Finish button on the Import Asset screen.

IBM Software


__413. If the following Workspace Migration prompt appears, click the Cancel button. There was no previous version of this project. This may be a potential bug introduced with the WID 6.2 iFix.

IBM Software


__414. The asset is imported into the workspace. Expand NotifyCustomerofDecisionServiceDesign > CreditManagementDesign > Docs.

__415. Review the interface specification document (ServiceSpec.doc) for NotifyCustomerofDecisionServiceLocal service endpoint. Right click on ServiceSpec.doc and select Open in Editor.

IBM Software


__416. Review the interface specification document for NotifyCustomerofDecisionServiceLocal service endpoint. An integration developer would review the interface specification document to gain an understanding of the inputs and outputs of the Web Service and the expected protocol.

__417. Close the Microsoft Word Viewer window for ServiceSpec.doc.

2.5.3 Stoppen von Rational Asset Manager

__418. Click the Stop RAM icon on the desktop.

IBM Software


__419. If prompted, with a login prompt, enter a username of admin and a password of admin.

IBM Software


2.6 Komplettieren der Implementierung des Final Loan Review Prozesses We will now complete the assembly of the Final Loan Review process.

2.6.1 Vervollständigen des Assembly Diagramms des Final Loan Review Prozesses

__420. Switch to the Business Integration perspective.

__421. In the Business Integration view expand BetterFinancials_impl and double click the BetterFinancials_impl Assembly Diagram. If the diagram is somewhat untidy you can fix this by right clicking in the diagram area and selecting “Arrange Contents Automatically”.


IBM Software


__422. Expand BetterFinancials_lib ► Web Service Ports in the navigator and drag the NotifyCustomerofDecisionLocalPort service endpoint onto the assembly diagram.

__423. Select Import with Web Service Binding on the Component Creation pop-up.

IBM Software


__424. Click on the OK button.

__425. On the next popup screen, click on the OK button to select SOAP 1.1/HTTP JAX-RPC as the transport selection. In WID 6.1.2, Web Services bindings supported the JAX-RPC protocol. This will continue to be supported as legacy bindings. WID 6.2 provides additional options listed here for the Java API for Web Services 2.0 (JAX-WS) transport. JAX-WS is a new option provided through the exploitation of the Web Services Feature Pack.

IBM Software


__426. Right click on the import, select rename, and change the name of the import to “NotifyCustomerofDecisionServiceLocal”.

__427. Right click on the NotifyCustomerofDecision Java component and select Delete.

IBM Software


__428. Your diagram should look as follows:

IBM Software


__429. Wire the NotifyCustomerofDecisionExport export to the NotifyCustomerofDecisionServiceLocal Web Service import. Right click on NotifyCustomerofDecisionExport and select Wire to Existing.

IBM Software


__430. Your diagram should looks as follows:

__431. Click on the Save icon in the menu bar to save your changes to the Assembly Diagram.

__432. Close the Assembly Diagram for BetterFinancials_impl.

__433. You have completed the Assemble portion of this lab. You searched WebSphere Service Registry and Repository for the WSDL binding/endpoint for the NotifyCustomerofDecision interface and imported the WSDL document into the BetterFinancials_lib project. You searched Rational Asset Manager for documentation about the service interface for the NotifyCustomerofDecisionLocalService Web service endpoint and retrieved and reviewed the document. You rewired the NotifyCustomerofDecision export to the NotifyCustomerofDecsionServiceLocal Web service endpoint.

IBM Software


2.7 Aufräumen

2.7.1 Stoppen des WPS/WSRR/WBM Servers

__434. Close all editors.

__435. Switch to the Servers view.

__436. Select WebSphere Business Monitor Server v6.2 and click the red stop server button.

__437. Wait until the server state becomes Stopped.

__438. Close WebSphere Integration Developer.

Herzlichen Glückwunsch! Die zweite Übung ist damit abgeschlossen.

Dauer der Übung ca. 1 Minute

IBM Software


IBM Software


Übung 3 Prozessdarstellung und Management – Erstellen und Konfigurieren Sie Business Spaces, Pages und Widgets in einer Web-Anwendung

Normally you would read the lab introduction first, but in this case, the suggestion is to kick off starting up the server because it takes some time. So, you will kick-off the start server, then read the lab introduction and carry-on with the lab.

Starten des Servers

__439. Click on the Start WPS short-cut on the desktop:

__440. A status window will open but please do not wait for the server to start… continue to the next section.

IBM Software


Lab Introduction The main purpose of this lab is to show how to provide visibility into the business process data and management capabilities of the automated processes. Business users are interested in the data from both an in-flight and from a history (trend) view. Information Technology (IT) users are interested in managing (restart, cancel, force finish, re-assign tasks, etc) the in-flight processes.

This lab will focus on configuring the Business Space Powered by IBM® WebSphere® from both a Business perspective and an IT perspective. Business Space is a Dashboard environment that contains one or more pages of widgets – widgets are simply views that allow us to “slice and dice” the data in a manner that is meaningful and useful. Some widgets also allow us to take action in the form of updating the information or managing the business. The widgets are grouped onto a page and pages are grouped into a business space.

WebSphere v6.2 supports Dashboards in both WebSphere Portal and non-Portal (web) environments. This lab will focus on creating a Business Space and pages in a non-Portal environment, then configuring several widgets. Dashboards using WebSphere Portal for version 6.2 are configured the same as versions 6.0.x and 6.1.x, so we will not cover them in this lab.

Dashboards are typically role-based so that a user sees only data and information of interest. There are pre-configured Dashboards in the vmware image that have been created for future purposes but this lab will have you create dashboards that may contain data and views of interest to both business user roles and IT roles.

This lab will not discuss in detail the purpose and usage of each of the widgets. It will focus mainly on setting up your Business Space dashboard environment and configuration guidelines.

Please note that the screen shots may not match exactly those that you will see in the current VMware image. Also, there may be a mix of screen shots from the Mozilla® Firefox® browser and the Microsoft® Internet Explorer® browser. Either browser will work for this exercise.

Helpful Links The following URLs may be helpful to you during this lab:

● Server administrative console: https://localhost:9043/ibm/console ● Web dashboard: https://localhost:9443/BusinessSpace/ or

http://localhost:9080/BusinessSpace/ ● Monitor info center:

http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/index.jsp?topic=/com.ibm.btools.help.monitor.doc/home.html

IBM Software


Der Geschäftsprozess This lab is based on the Better Financials business process:

Customers can apply for various loan types:

● No Doc ● Standard ● Zero Down

The countries your enterprise is monitoring are:

● Australia ● Brazil ● China ● Germany ● India ● Japan ● Spain ● UK ● USA

IBM Software


Organizationsstruktur und Authorisation The organization structure is defined as follows:

And the following users and groups have KPI-Administrator authority to the 2.10 monitor model and the Global HTMM model:

And the following users and groups are not authorized to the model:

IBM Software


Remarks about Lab Execution This lab is very comprehensive and shows you how to work with most of the widgets and many of the space templates available in Business Space.

You do not have to complete all parts of the labs – rather, we recommend that you select the parts of the lab that are most interesting to you or the parts that relate to questions you are being asked frequently by customers. The main table of contents is organized such that you can jump directly to the page or widget that is of interest to you.

All parts of this lab can be considered optional. You are free to start working on any of the parts in this lab, just be aware that you must create the corresponding business space and pages in order to configure the widgets:

● Part 2: Navigating Around the Business Space ● Part 3: Create a New Business Space and Pages for a Business User ● Part 4: Business Role: Configuring Widgets for Business Activity Monitoring ● Part 5: Business Role: Configuring Widgets for Daily Work Activities ● Part 6: Create a New Business Space and Pages for Collaboration ● Part 7: Business Role: Configuring Widgets for Collaboration and Publishing ● Part 8: Create a New Business Space and Pages for a User Participating in Human

Workflow ● Part 9: Business Role: Configuring Widgets for Participating in Human Workflow ● Part 10: Create a New Business Space and Pages for an IT User ● Part 11: IT Role: Configuring Widgets for use by IT Users

IBM Software


3.1 Starten des Servers und Öffnen des Business Space Dashboards

3.1.1 Starten des Server

__441. If you have not already kicked off starting the server, click on the Start Server short-cut on the desktop:

__442. A status window will open… server is successfully started when the window closes. Patience, it may take a few minutes to start up the server:

3.1.2 Starten des Business Space im Web Browser

__443. Open a browser window by clicking on the Mozilla Firefox shortcut:

__444. You may get a pop-up asking for a profile choice. Choose the default profile and click the Start Firefox button:


IBM Software


__445. Connect to the Business Space Powered by WebSphere by typing in the

__a. http://localhost:9080/BusinessSpace or https://localhost:9443/BusinessSpace/ URL or click on the Business Space dashboard shortcut:

__446. The Business Space login view will open. Type in the User ID of admin and a Password of admin, then click the Login button:

IBM Software


3.2 Navigieren im Business Space

3.2.1 Importieren eines vordefinierten Business Space

Initially, when you login, if you leave the Return to last visited page checked, you may not be placed in the Business Space Manger.

__447. If you are not in the Business Space Manager, click the Manage Business Spaces link in the upper right corner:

__448. Once in Business Space Manager, click the Import Business Space button

__449. In the Import Business Space wizard, click the Browse button.

__450. In the File Upload dialog, navigate to C:\Labfiles\2.10 and select the 2.10 Sample Dashboard.data file.


IBM Software


__451. Click OK to import the 2.10 Sample Dashboard business space definition:

__452. Take a look at the existing 2.10 Sample Dashboard. Peruse your options:

Initially, you will see the 2.10 Sample Dashboard. The idea is that a Business Space is created for a business analyst, or an IT manager, or a role, or an individual, or for whatever target audience you need. Different roles are interested in different subsets of data and an individual may be interested in personalizing his or her space.

Within each Business Space, you can have multiple pages to organize your activities and goals. This Business Space was created using the Monitor template and contains a number of standard pages (tabs) within the space as well as some pages that were added on top of the template. The drop-down provides an alternative list of the pages.

Navigate via the Manage Business Spaces link if you wish to add, change, delete, or rename Business Spaces, or, add or delete pages. Security authorization is also here.

The Widget Palette drop-down provides a list of widgets that you can drag and drop onto the pages.

IBM Software


__453. Navigate over to the Manage Business Spaces page by clicking on the link in the upper right corner:

3.2.2 Verwaltung der Business Spaces

__454. The Manage Business Spaces page lists all of your current Business Spaces so that you can add or delete pages, change sharing, add new Business Spaces, etc. Let’s take a look at the various features:

IBM Software


Buttons to create a new Business Space or a new page, or, import a Business Space or page.

Option to view the available Business Spaces and pages in various groupings:

The Business Spaces are listed with a “twisty” next to them which can be clicked to show/hide the pages. Note also that some detailed data is displayed by the name of the Business Space and page names. In this case, the owner of the Business Space and the number of pages… if you change the Group by option, it will display the appropriate detailed data for that view.

When you select a Business Space or page, the associated details are displayed and can be modified.

When you hover over a Business Space or page, the “x” option appears which allows you to delete that artifact.

Option to export the selected Business Space or page definition:

A quick link back to the last viewed Business Space exists in the upper right of the panel, or, you can click on the name of any Business Space:

or you can click on the name of any of the pages to jump directly to the page:

IBM Software


3.2.3 Hilfe öffnen

__455. Jump to the Welcome Business Space:

__456. This Business Space walks you through the WebSphere Business Space Concepts and Scenarios. It is a good starting point in understanding which scenario to choose to meet your needs and which widgets are associated with the scenarios. It also has links to tours and additional help:

IBM Software


Now you know how to navigate the Business Space environment, create basic Business Spaces and pages, and personalize the Spaces and pages. Next, you will take a look at some of the pages in the dashboard and see how easy it is to configure the widgets and personalize the environment.

IBM Software


3.3 Fachliche Rolle: Erkunden der existierenden Widgets für das Business Activity Monitoring

Nachdem Sie nun einen Überblick über den Business Space und dessen Navigation erhalten haben, werden wir einen Blick auf die unterschiedlichen Pages werfen und uns anschauen, wie sie konfiguriert werden.

Der erste Teil des Labs beschäftigt sich mit den Widgets die dem Business User für Monitoringzwecke zur Verfügung stehen.

3.3.1 Widgets auf der Analysis Seite

__457. Navigieren Sie auf den Business Space 2.10 BAM Dashboard und klicken Sie auf die Seite Analysis:

Jede dieser Seiten enthält Widgets, die dem jeweiligen Zweck der Seite. Die Analyseseite besteht zum Beispiel aus dem Dimensions view widget, dem Reports view widget, und dem KPI (Key Performance Indicators ) History and Prediction view widget.

Hinweis: Um ein Widget zu konfigurieren, klicken auf das Drill-Down Menu in der rechten, oberen Ecke des Widgets und wählen Sie “Configure”:

Achtung: Die Konfiguration wurde in diesem Workspace bereits für Sie übernommen!


IBM Software


Dimensions Widget Das Dimensions Widget stellt die geschäftsrelevanten Daten in Charts und Tabellen dar. Dabei lassen sich Abhängigkeiten multidimensional darstellen.

__458. Die Grafik zeigt die Kreditanträge der Better Financials insgesamt. Allerdings lassen sich hier noch mehr Informationen darstellen. Es wäre auch interessant zu erfahren wie sich die Anträge auf Länderebene verteilen.

__a. Um zu erfahren wie die Verteilung der Kreditanträge in den einzelnen Ländern der Better Financials aussieht, doppelklicken Sie auf den blauen Balken. Sie werden gefragt ob sie den Drill Down hinsichtlich der Länder oder der Art des Kreditantrages vornehmen wollen. Wir entscheiden uns für das Erste:

Die Tabelle auf der rechten Seite zeigt die entsprechenden Zahlenwerte.

__b. Über die Combobox “Measures” können wir andere Leistungsdaten auswählen.

__c. Untersuchen sie die Dimensionen nach eigenem Ermessen. Nutzen Sie den Drill Down um die Informationen zu detaillieren.

IBM Software


Reports Widget Das Report Widget stellt die Leistungsdaten in einen zeitlichen Kontext und ermöglicht die Erstellung von Reports. Es verfügt darüberhinaus ebenfalls über Drill Down Funktionalität.

Der dargestellte Report zeigt die durchschnittliche Kredithöhe pro Tag in einem 3 Monatsintervall.

KPI History, Prediction Widget und KPI Manager Widget Das Widget zeigt den Status und den Zielwert der modellierten KPI’s.

IBM Software


Navigieren Sie zur Operational Page

__459. Click on the Operational page tab:

Diagrams Widget – Monitoring Context Das Diagrams Widget zeigt den Business Prozess, de rim Modeler erstellt wurde.

IBM Software


Instances Widget Das Instanzen Widget zeigt die gewünschten Daten jedes Kreditantrages an.

Welche Daten angezeigt werden und wie diese sortiert werden (nach dem Erstellungsdatum, der Kredithöhe, usw.), kann konfiguriert werden.

IBM Software


Human Tasks Widget Das Human Task Widget zeigt alle Benutzertaskorientierten Informationen an.

Auch hier lassen sich andere Spalten hinzufügen wie z. B. Der Zeit, die der Benutzer benötigte um die Aufgabe zu erledigen, hinzufügen.

IBM Software


3.3.2 Widgets auf der KPIs Seite

__460. Navigieren Sie zur KPIs Seite

Diagrams widget – KPI Context In diesem Kontext zeigt das Diagrams Widget das Business Modell im Kontext der definierten KPIs.

IBM Software


KPIs widget Das KPI Widget zeigt grafisch die gemessenen Werte des Prozesse im Zusammenhang mit den zuvor definierten KPIs an. So lässt sich kontrollieren, ob Schwellwerte (wie etwa die durchschnittliche Prozesslaufzeit) auch eingehalten werden.

(optional) General Configuration of KPIs In the configuration of the KPI widget, you may have noticed that when you selected the KPIs to add, that the “default” KPI was added. The labels and values are unique to each KPI but may be personalized by changing the KPI properties.

There are several places to invoke the KPI properties dialog, including from the KPI displayed in the KPIs widget. Note that the KPI properties are different than the KPI widget configuration properties. The KPI properties are the properties that are unique to the particular KPI measurement, and not the properties relating to the view widget itself.

Properties that may be changed here include range names, range values, colors, decorator icons, etc. Some properties are set at creation of the KPI and cannot be changed such as the process model of the KPI.

__461. Click on the drop-down arrow in the upper right corner of the KPI:

IBM Software


Four options exist in the list:

The KPI Properties option allows you to change the “default” properties of the KPI: Name, Definition, Range, Other, and Preview values. You can also mark the changes as personal which makes them only visible to you. The Alert Manager will pop open a dialog to allow you to change subscriptions to alerts associated with the selected KPI. The History and Predictive option allows you to configure the data collection criteria for this KPI that will be reflected in the KPI History and Prediction widget. The Show Instances is a cooperative option that allows you to drill-down to view the instances that comprise the KPI.

__462. Select the KPI Properties option:

IBM Software


__463. Note that there are 5 tabs of configurable values and on the Name tab is the option to make your changes Personal or Shared:

__464. Choose the Personal Access option, then click on the Range tab:

IBM Software


__465. Click in the center of the green color box for the Expected range. This will bring up a color palette. Select the light blue color and click the OK button:

__466. Repeat the color change for the slow range, changing the color to dark blue, then clicking the OK button:

__467. Click the OK button on the KPI Properties dialog to complete your changes:

IBM Software


__468. The KPI in the KPIs widget view will now reflect the blue colors:

IBM Software


3.3.3 Widgets auf der KPI Manager Seite

The KPI Manager Seite erlaubt das Manipulieren von KPIs, von zugehörigen Alerts und zum Erstellen von neuen KPIs

__469. Navigate to the KPI Manager Page: In the 2.10 BAM Dashboard business space, navigate to the KPI Manager page by clicking on the tab:

IBM Software


3.4 Erstellen eines neuen Business Space und Seiten für Collaboration

Erstellen einer “Publishing Server” Business Space

The recommended practice is to create Dashboards based on roles so that the person viewing the Dashboard only sees data of interest. The easiest way to collaborate on a model, is to publish it directly to a pre-created Business Space. Let’s create a Business Space for a Business role that will facilitate collaborating on the design and/or re-design of a business process model.

__470. In the Business Space Manager, click on the Create new Business Space button:


IBM Software


__471. Name the new business space 2.10 Process Collaboration. Remember the options that you previously had to create a space: an empty space, based on a template, or from an existing business space. Create your new business space based on an out-of-the-box template, the Reviewing template. The Reviewing template contains pre-defined pages and widgets designed for collaboration and final publication of a model of the business process(es) to the business space environment.

__a. Type a name for the new Business Space of 2.10 Process Collaboration

__b. From a template of Reviewing

__c. Then click the OK button:

IBM Software


3.5 Fachliche Rolle: Konfigurieren der Widgets für Collaboration und Publishing

This part of the lab will focus on the Business role and the widgets that may be of use to Business users who are collaborating on the design or re-design (continuous improvement) of the business process.

3.5.1 Publishing Server Zugrifsverwaltung

Grant Authority to Publish Next, you will need to authorize publishing rights to a specific user. This is done in the Business Space console.

__472. If not already open, navigate to the newly created 2.10 Process Collaboration Business Space by clicking on the name link:

__473. In the list of pages, click the Publishing Server Access Control page link:


IBM Software


__474. Expand the Users list by clicking on the plus sign:

__475. Select the admin user and in the Projects column, expand the Publishers list by clicking the plus sign:

__476. Check the box labeled Publisher Access:

IBM Software


__477. Click the Submit button:

__478. You will receive a message that Access rights have been set for admin. Click the OK button to dismiss the dialog box:

Anpassen des Geschäftsprozessmodells If you have lotus form(s) in your model, you will need to convert them to JPEGs and attach them to the model. Modeler does not publish the lotus forms directly at this time.

__479. Open the Lab Shortcuts folder on the desktop:

IBM Software


__480. Open (double-click) the 2.10 short-cut to start the WebSphere Business Modeler tool:

__481. In the Better Financials project, navigate the tree to Processes > Final Decision Form and double-click the form to open it:

IBM Software


__482. Double-click the Review Form.xfdl tab to maximize the form panel and click the right triangle in the Palette area to minimize the Palette panel:

IBM Software


__483. Since we only have limited tools available in the image, resize the window down to roughly the size of the form and take a screen shot (Alt-PrtSc) of the form:

IBM Software


__484. Save the form using the Microsoft Paint tool: Open Windows Paint tool (Start > All Programs > Accessories > Paint) and paste (Ctrl-v) the screen shot into the tool. You could take the time to eliminate the window border “stuff” around the form, but you do not need to do it for lab purposes.

__a. Navigate File > Save As…

__b. Save in: Desktop > My Documents > My Pictures

__c. Enter a File name: FinalDecisionForm

__d. Save as type: JPEG (*.JPG, *.JPEG, *.JPE, *.JFIF)

__e. Close the Paint tool.

__485. Return to the Modeler tool and double-click the Review Form.xfdl tab to return to the 4-pane view and close the Final Decision Form. In the real world, you might repeat the above steps in order to make JPEGs of the other forms. Since this is just for learning purposes, we do not need to convert the other two forms.

__486. Attach the JPEG to the model: Navigate the Better Financials > Processes and open the Final Loan Review process:

__487. The Final Decision Form is used for the VP Underwriting Review and the Senior Underwriting Review steps. Ensure the process is the focus (not an individual activity), then click on the Attributes tab and Add… an Attached file:

IBM Software


__488. Navigate to Desktop > My Documents > My Pictures, and select the FinalDecisionForm.JPG file and click the Open button.

__489. Save (Ctrl-S) the model.

Veröffentlichung des Modells

__490. Navigate the project tree Better Financials > Processes > Final Loan Review. Right-click on the Final Loan Review business process and select the Publish… option:

IBM Software


__491. In the Publishing Server Selection pop-up dialog click the Add… button to add a new Publishing Server:

IBM Software


__492. In the New Server – Add a publishing server pop-up:

__a. Name: Better Financials Pub Server

__b. Server address: localhost

__c. Port number; 9080

__d. User ID: admin

__e. Password: admin

__f. click the Browse… button to select a Space:

__g. Select the 2.10 Process Collaboration space

__h. Click the Finish button:

IBM Software


__i. Click Finish button.

__493. Select the Better Financials Pub Server to ensure the Space is properly set to 2.10 Process Collaboration. Accept the default check boxes to include the elements and overwrite elements on the server, then click the Finish button:

IBM Software


__494. Click the OK button on the Publishing Results pop-up:

3.5.2 Widgets auf der Publishing Server Manager Seite

Publishing Server Status Widget Verify Successful Publish Occurred

__495. In the 2.10 Process Collaboration Business Space, select the Publishing Server Manager page:

__496. The Publishing Server Status widget displays a list of publishing server activities along with information about the activities. The job type of Publish for the Final Loan Review process should show a state of Complete and a status of Successful:

Note: you can select one or more jobs and click the Delete Jobs button to remove them from the list (this only deletes the log entry, not the published model):

IBM Software


3.5.3 Publishing Server Zugriffssteuerung

Grant Authority to the Model

__497. Select the Publishing Server Access Control page in the 2.10 Process Collaboration Business Space:

__498. Expand the Users list by clicking on the plus sign:

__499. Select the admin user and in the Projects column, expand the Draft Projects list by clicking the plus sign:

IBM Software


__500. Check both boxes (View and Review) labeled Better Financials:

__501. Checking the high-level boxes causes a cascade effect so that all sub-components are also selected. Click the Submit button:

IBM Software


__502. Click the OK button to dismiss the message that Access rights have been set for admin:

3.5.4 Widgets auf der Draft Artifacts Seite

Draft Artifacts Widget View the Draft Model

__503. Select the Draft Artifacts page in the 2.10 Process Collaboration Business Space:

__504. In the Draft Project Tree, navigate Draft Projects > Better Financials > Processes and select the Final Loan Review business process:

IBM Software


__505. In the diagram, click the Show Attributes button:

__506. Select the Attachments option in the Attributes frame (the last entry in the list):

IBM Software


__507. Click on the FinalDecisionForm.JPG file link and Open the file:

__508. Select the Open with option and click the OK button:

IBM Software


__509. The JPEG of the form that you created earlier will be displayed in the Windows Picture and Fax Viewer tool. Click the icon in the upper right corner to close the form:

__510. Note that a download status window may open – close this window also.

IBM Software


__511. Click the Close button on the Attributes panel to dismiss the dialog:

IBM Software


3.6 Erstellen eines neuen Business Space und Seiten für einen Benutzer, der den Prozess ausführt

3.6.1 Erstellen des Business Space

The recommended practice is to create Dashboards based on roles so that the person viewing the Dashboard only sees data of interest. Let’s create a Dashboard for an end user who participates in Human Workflow and regularly works on tasks assigned to him, or creates new tasks.

__512. If you are not in the Business Space Manager, click the Manage Business Spaces link in the upper right corner:

__513. In Business Space Manager, click the Create new Business Space button:


IBM Software


__514. Name the new business space 2.10 Human Workflow and notice the various creation options – empty, from a template, or based on a previously created business space. Create your new business space as an Empty space. Click the OK button:

3.6.2 Erstellen der Seiten

__515. Add a new page to the newly created business space by clicking on the Create new Page button while the new business space 2.10 Human Workflow is selected

IBM Software


__516. Similarly to the business space creation, you can name the page and create it with a desired layout or based on a previously created page. Name the page My Work, create it Empty, choose the two column layout, then click the OK button:

__517. Create another page in the 2.10 Human Workflow. Name the page Create Tasks, create it again Empty, and choose the two column layout.

__518. Review your business space definition. It should match the following structure:

IBM Software


3.6.3 Zusätzliche Benutzer für den Business Space zulassen

Since there will likely be many users who will work on tasks assigned to them, we will share this Business Space with all users in the Loan Officer role.

__519. Make sure that the 2.10 Human Workflow space is selected in Business Space Manager then, click the Share this Business Space checkbox on the right-hand side of Business Space Manager.

__520. Click the button for the Editors section and select Add from the menu.

IBM Software


__521. Type loan in the text box, then click the Search… button

__522. Select Loan Officer from the Search results and click the OK button. Everybody in the group ‘Loan Officer’ is now authorized to use and edit the Business Space you are creating.

__523. Click the Save button to save your changes. Now you have created a Business Space for Human Workflow with two pages. Next, you will add widgets to the pages and learn how to use them.

IBM Software


3.7 Fachliche Rolle: Konfigurieren der Widgets, um die Human Tasks bei der Prozessausführung durchzuführen

In this part of the lab, we will focus on the widgets that are of use to people participating in Human Workflow.

3.7.1 My Work Seite

Set-up der My Work Seite

__524. Open the My Work page in the 2.10 Human Workflow space.

__525. Click the Add Widgets button on the middle of the page

__526. The widget palette opens. Select the My Tasks widget from the Tasks and Workflow section on the palette and drag it to the page.


IBM Software


__527. Since you have selected a two-column layout for the page, you can now add the widgets to either of the two columns of the page. Drop the widget to the left column on the page.

__528. Add additional widgets to the page according to the following scheme:

My Tasks Task Information

Available Tasks Human Workflow Diagram

Team List

__529. Resize the rows and columns on the page to match your desired layout. To resize a row or column, click on the row or column divider and drag it to match your desired column width or row height.

IBM Software


Available Tasks Widget Now let’s configure some of the widgets we have added to the My Work page. Business Users will use this page to discover tasks assigned to them – so we should make sure that new tasks show up in a timely manner, without requiring the user to manually refresh the page. We will also define our own priority scheme to determine which tasks should be considered high priority.

__530. Click the button for the Available Tasks widget and select Configure from the menu

__531. Open the Refresh tab in the configuration dialog for the Available Tasks widget.

IBM Software


__532. Select the Refresh content automatically radio button and type 1 in the refresh interval text field.

Human tasks can be assigned a priority. The priority specifies the level of importance of this task and is given by a numerical value, with lower numbers having a higher priority. The priority is assigned as a property to the task at development time in WebSphere Integration Developer and can be changed at runtime.

__533. We will now specify what values we want to denote a “high”, “medium” or “low” priority. Open the Priority tab in the configuration dialog for the Available Tasks widget.

IBM Software


__534. Scroll down, then type 3 as the maximum value for High priority tasks, and 8 as the minimum value for Low priority tasks.

__535. Click the OK button to close the configuration dialog and apply your changes.

3.7.2 Erstellen der Task Seite

Set-up der ‘Create Tasks’ Seite

__536. Open the Create Tasks page in the 2.10 Human Workflow space.

__537. Add widgets to the page according to the following scheme. All widgets are in the Tasks and Workflow section on the palette.

Create Tasks Task Information

Tasks I Created

__538. Resize the rows and columns on the page to match your desired layout

IBM Software


3.8 Business Space und Seiten für einen IT User

__539. Wechseln Sie auf den IT Dashboard Business Space

__a. Klicken Sie in der rechten oberen Ecke auf Manage Business Spaces

__b. Doppelklicken Sie auf 2.10 IT Dashboard

Auf dem IT Dashboard gibt es 2 Seiten, den Health Monitor und den Business Calendar Manager.

3.8.1 Health Monitor

Das Health Monitor Widget zeigt überwachte Server, Anwendungen und Queues.

3.8.2 Business Calendar Manager

Auf der Seite gibt es 2 Widgets. Der Security Manager ist für die Gruppen und Benutzerzuordnung da. Der Business Calendar Manager zeigt alle Zeitpläne eines Projektes und erlaubt es, sofern man über ausreichende Rechte verfügt, diese anzupassen.


IBM Software


3.9 Testen des Prozesses

Nun werden wir die Anwendung mit dem Business Space Testen. Dies ist eine Gemeinschaftsübung.

IBM Software


3.10 Aufräumen

Schließen des Business Space.

__540. Logout of the Business Space:

__541. And close the browser window:

Dauer der Übung ca. 1 Minute

IBM Software


Stoppen des Servers

__542. Click the Stop WPS short-cut on the desktop.

__543. You may get a status window and a pop-up asking for valid credentials to stop the server. Type in a user of admin and a password of admin. The server is successfully shut down when the window closes. Patience, it may take a few minutes to stop the server:

Herzlichen Glückwunsch! Die Übungen sind damit abgeschlossen.

IBM Proof of Technology Workshop WebSphere Business ......IBM Software Page 4 Discovering the value...

Documents

Transcript of IBM Proof of Technology Workshop WebSphere Business ......IBM Software Page 4 Discovering the value...