Work List Manager Sample ImplementationHolger Paffrath

April 2009

Create the Worklist Manager DatabaseThe worklist manager supports a number of databases.

• Oracle 8.1.7

• Oracle 9i

• Sybase 12.5

• SQL Server 2000

• DB2

• Oracle 10g

• Oracle 11g

In this tutorial, Oracle 9i will be used.

• From the project explorer, expand “CAPS Components Library/Business Process Manager/WorkListViewer”

• Right click the WorkListViewer as highlighted above and click “CheckOut”.• Right click “Database Scripts” and select Properties.

The Properties Dialog box will appear

• Configure the database properties for your database and press OK.

Note : The user whose login information you enter must have DBA privleges to create the new Worklist Manager user.

• For Oracle Databases only : • Right click the Oracle Install script and select “Open”

• Modify the location of the tablespace data to the location where you want the file to reside.For Example : create tablespace WLM6USERdb datafile 'C:\oracle\oradata\Worklist\WLM6USERdb.dat' size 500k reuse autoextend on next 500k maxsize UNLIMITED;

becomes

create tablespace WLM6USERdb datafile 'C:\oracle\oradata\Worklist\WLM6USERdb.dat' size 500k reuse autoextend on next 500k maxsize UNLIMITED;

• Save the file.

• To execute the script, Right click the Oracle Install Script and select “Run”

• Check the directory specified above on the oracle server and a new .DAT file will appear.

Configuring SecurityThe Worklist Manager and task assignment window both require a connection to an LDAP directory for user information and authentication. You can optionally configure SSL on the LDAP server to encrypt information.The primary requirement for the Worklist Manager is a mechanism that clearly defines a user hierachy so managers and supervisors can view the tasks of their subordinates and users can escalate tasks to their superiors.There are several LDAP Implementations supported by the Worklist Manager...

• Open LDAP• Sun Java System Directory Server• Microsoft Active Directory

For this tutorial, the LDAP Server being used is Sun's Java Directory Server. This server has been pre-installed and several usernames already added. If you wish to configure the LDAP server yourself, see the References section on how to configure the Worklist Manager.

Sun Java System Directory ServerThe Worklist Manager can adapt to your existing Sun Java System Directory Server structure. You will need to define the reposting structure if this has not been done already. There are a variety of ways to define the reporting structure. Sun provides a default attribute “manager” that you can use to define the upward reporting structure, but you must also use an attribute that defines subordinates. You can also create custom attributes that indicate a user's managers and subordinates, or define hierachies in the “entrydn” attribute of the user. For example, if user “hpaffrath” reports to “mczapski” who reports to “skotlyar” the entry attribute “hpaffrath” will be similar to:

uid=hpaffrath,uid=mczapski,uid=skotlyar,ou=people,dc=sun,dc=com

When you define the LDAP directory structure, not the Naming Attribute used in the distinguished name for each user. This is typically the uid attribute or the cn attribute. This value is specified in the Worklist Manager External System properties in the Environment Work List Manager login credentials for each user are defined by the vsalue of the Naming Attribute and the value of the userpassword attribute. You will need to create an administrator user that the Worklist Manager will use as the security principle.

Creating the Project and EnvironmentThis tutorial will go through the steps required to create a sample Worklist Manager implementation.

This project will be divided into 3 parts.

The first part will pick up the file and place it on a queue.

The second part will retrieve the message from the queue, place it on the worklist. When the message is assigned to a user, the user will then approvie or disapprove the discharge.

The final result will then be placed on a second queue.

Thirdly, messages on the second queue will then be written to a file.

The input file being used for this project is an simple message that only contains the name. Holger Paffrath

Create a New Project• In Netbeans, Select “File” then “New Project”.

• Select “CAPS/ESB”, “CAPS Repository-based Project”

• Give the project the name “WLMTutorial” and click “Finish”

• A new Project will appear in the Projects Window called WLMTutorial.

• Right Click this project and create a new Project called “Pages”

A new entry will appear.

• Repeat the above process to create the following entries:

• OTD

• Deployment

• Business Process

Create the Page LayoutsFor this tutorial, two web pages will be created. The first page is the data entry page, the second page will appear once the task is complete. The second page will allow you to close the the web page and exit the application.

Creating the Data Entry Page• In the Project explorer, right click Pages and select “New” then “Page Layout”. A new page

layout dialog box will appear.

• Select “Blank Page” , give the page a name “dataEntry” and click “OK”.A new Tab will appear with the Page Layout.

• There are 3 sections to the Page Layout screen. The first is the “Palette” where all the objects for a web page are available. These are simple “Drag and Drop” to the Canvas area which is the second area. The third area is the properties window for the selected object.

• Create a Page Title

• In the Object Palette, click the Label object and drag it to the top centre of the page.

• Name the label “Discharge Approval”

• In the properties window, select “label0” and change it to “DischargeApp” in the LName property.

• Create a Lable that will be populated by the name entered in the input file.

• In the object palette, click the Label Object and drag it to the canvas under the “Discharge Approval” label.

• Give the lable the name “Name”

• In the Properties section, select “label1” and enter the new name of “Name” for he LName property.

• Create a Radio button to approve or disapprove the discharge

• Drag a Radio from the object palette to the canvas.

• Double click the Radio button to bring up the Options.

• Enter the lable “Approve” with value “Approve” and marked “Checked” then click “Add”

• In the new entry, give it the label “Disapprove” with the value “Disapprove” - Do not check the “Checked” box.

• Click OK to save the changes.

• In the properties window, select “LName” and change the name to “RdoApprove”.

• Create a Submit Button

• In the object palette, drag the “Submit button” to the canvas.

The pages should be similar to the following :

Around the canvas, you will see toolbar buttons to help with the layout of the web page. There is even a preview button and a print button to print out the page.

Once finished, save your changes.

Creating the Exit Page• Using the above method, create a new Page Layout. This time give it the name “exitPage”.

• From the object palette, drag “link” across to the canvas and enter the name “Close Window”

• In the property sheet, scroll down till you see “On Click”. Its located under “JavaScript”.

•

• Click on the “[...]” button when you click on the “On Click” property. In the dialog box that comes up, enter the following :

javascript: void window.close()

Click OK to close the dialog box.

• Save your changes.

Creating the Web Service Definition Object• In the project explorer, right click the OTD project and select “New” then “Web Service

Definition”.

• Give the WSDL the name IOWSDL. This is for I/O (Input/Output) WSDL.

• The WSDL editor window will appear and the WSDL will be visible under the OTD project.

• Configure the Input Message

• In th eWeb Services Definition Panel, expand “PortTypes” and “PortType” then click on Operation.

• Right click “Operation” and select “Add Input”

• Click on “InputMessage1” and select “Message Type”. Click on the […] button to select the type for this message.

• Give the message the name “IP_Message” and then select “xsd:string” as the message type as indicated and click “Add”

• Click OK to accept the changes.

• Configure the Output Message

• In th eWeb Services Definition Panel, expand “PortTypes” and “PortType” then click on Operation.

• Right click “Operation” and select “Add Output”

• Click on “OutputMessage1” and select “Message Type”. Click on the […] button to select the type for this message.

• Give the message the name “OP_Message” and then select “xsd:string” as the message type as indicated and click “Add”

• Click OK to accept the changes.

Click “Save”. Your WSDL should look like the following :

Creating the Business Process

Creating the File Input Business Process• Right Click the “Business Process” project and select “New/Business Process”

• Give the Business Process the name “bpFileIn”.

• Expand “CAPS Components Library/Adapters/File/FileClient” and Drag the “receive” to the canvas.

• Expand “CAPS Components Library/Enterprise Service Bus/JMS” and drag the “send” to the Canvas.

• Link the components together and click on the link between “FileClient.receive” and “JMS.send”.

• Right click the link and select “Add Business Rule”. A little blue icon with a red dot will appear in the link.

• Double click the blue icon to bring up the business rule edtor.

• Expand out the “FileClient.receive.Output” and the “JMS.send.Input./JMS/Message” and drag the link between “FileClient.receive.Output/text” to “JMS.send.Input/JMS/Message/TextMessage”

• If you wish to add Logging to your business process, see the appendicies on how to add logging to a Business Process.

• Save your changes.

Creating the File Output Business Process

• The process is similar to the bpFileIn business process, just using the “JMS.receive” and the “FileClient.write” components.

Create the Sub ProcessThe Main Business process will contain a user activity that requires a sub-process to define the data flow and logic of the user activity.

This sub-process will contain the page layouts and the WSDL object created earlier. The sub-process will be called from the user activity in the main Business Process and defines the processes that need to be carried out in order to complete the user activity.

• Right click on the Business Process project and select “New/Business Process” and give the business process the name “subBusinessProcess”

• Expand out the “OTD” project and expand out “IOWSDL/PortTypes/PortType” and drag “Operation” to the canvas.

• Select “Implement the operation (Server Mode) option in the dialog box that comes up.

• Under “Pages/DataEntry” drag the “show” operation onto the canvas.

• Under “Pages/exitPage” drag the “show” operation onto the canvas.

• Your canvas should look like the following.

• Link the components end-to-end

• Right click the link between “PortType.Operation.Receive” and “DataEntry.show” and select “Add a Business Rule” a blue icon with a red dot will appear.

• Double click the icon with the red dot. This should bring up the business rule editor.

• Expand the output to show “DataEntry.show.Input/Input/Form0/Name/text”. Expand the input to show “PortType.Operation.Output/value1” and drag “value1” to “text”.

• Right click the link between “exitPage.show” and “PortType.Operation.Reply” and select “Add a Business Rule” a blue icon with a red dot will appear.

• Double click the icon with the red dot. This should bring up the business rule editor.

• In the business rules editor, click on “String/concat”. This will add a concat operator to the business rules editor.

• Map the value node under “PortType.Operation.Output/value1” to the String parameter of the concat method.

• In the next String entry double click and enter “:”

• Expand out the “DataEntry.show.Output/Output/Form0/RdoApprove” and drag the value link to “str(String) node in the concat box.

• In the concat box, drag the “return string” to the “PortType.Operation.Input.value1” node.

•

• Save your changes.

Note : If you expand out the DataEntry.show.Input and the DataEntry.show.Output OTDs above, you will notice that the nodes match the components that we created earlier on the web page. That is because Java CAPS maps the properties of the components to an OTD allowing you to change values during runtime.

Creating a New PartnerWhen you use a sub-process in a business process, you need to create a partner to associate with the implement and reply activities on the sub-process. This step creates the partner.

• In the Project Explorer, right click “subBusinessProcess” and click “Properties”

• The Business Properties window will appear, click the “Partners” tab.

• Click “New” and enter “wlmpartner” as the name and click “OK”.

Once the partner has been created, it needs to be associated with activities.

• In your sub-business process, select the “PortType.Operation.Receive” component and select the “Show Property Sheet” button.

• For the “Partner” property, change the value from “PortType” to “wlmpartner”.

• Repeat the process for the “PortType.Operation.Reply” component.

• Save your changes.

Creating the Main Busness Process• Right click the “Busness Process” project and select “New/Business Process”

• Give it the name “mainBusinessProcess”

• From the “CAPS Components Library” expand “Enterprise Service Bus/JMS” and drag a “receive” and a “send” to the canvas.

• Bring the “JMS.receive” close to the “Start” and the “JMS.send” close to the “End”

• In the “Business Process“ designer, drag a user activity to the canvas. Its the icon with the orange man on it.The icon will come on the canvas with a red circle with a line through it. This means that there is no activity associated with it. To fix this:

• Expand “subBusinessProcess” and drag “Operation” on top of the ”User Activity”. The icon will now not show the red circle.

•

• Link the components together.

• Click the link between “JMS.recieve” and “User Activity”, right click the link and select “Add a Business Rule” then double click the blue icon.

• Expand out the “JMS.receive.Output” and the “subBusinessProcess.Operation.Input” and map “JMS.receive.Output/Message/TextMessage” to “subBusinessProcess.Operation.Input/value1”.

• Click the link between “User Activity” and “JMS.send”, right click the link and select “Add a Business Rule” then double click the blue icon.

• Expand out the “subBusinessProcess.Operation.Output” and the “JMS.send.Input” and map “subBusinessProcess.Operation.Output/value1” to “JMS.send.Input/JMS/Message/TextMessage”.

• Save your changes.

Configure the User ActivityNow that the business rules have been defined, you need to connect to the LDAP server to select the users to whom the user activity tasks can be assigned in the Worklist Manager.

• In “mainBusinessProcess” right click the “User Activity” and select “Edit Task Assignment Panel”

• The “Worklist Manager” assignment window will appear.

The condition tab allows the user to specify the rules to who gets assigned what tasks.

In this tutorial, all tasks will go to the specified list of recipients.

• Click “Add”, then click the condition tab.

• Click on “Boolean” then “true”.

• Map the “True” method to the “Result”. This in effect means this condition is always true.

• Click on the “Assignments” tab. Here we assign users to the condition.There are two types of assginments methods:

The first is static. This is where you specifically associate an LDAP user instance with an an assignment.The second is dynamic where the user is defined by a value in the incoming message. For this tutorial we are going to use the static method.

• Click the “Connect” button. Here we specify the LDAP server we are connecting to,

• Specify the parameters to connect to the LDAP server.

In our case, we're connecting to a server of base DN (Distinct Name) of dc=wa,dc=gov,dc=ssc. Role and Group have been left empty, but could be populated with required values if any. Click OK to connect.

• If connection is successful and there are entries in the LDAP database, then you should have a list of users/groups/roles available.

• Add your users by selecting the user and clicking the “Assign” button.

• Click on the “Default” entry and assign a particular user to be used as the default user.Default will never be used in this instance as Order 1 takes precedence and will always return “true”.

Although not used in this tutorial, the “Timeout” tab allows you to automatically escalate a task to a manager when a task “times out”.

Email notifications can be set on various conditions. The email address is static and set in the Work List Environment.

The Page Flow Mapper allows parameters from the worklist manager screen to be passed to a web page

• Click OK and save changes.

Create the Connectivity MapThis tutorial will assume that the user knows how to make a simple connectivity map. Therefore we will skip the creation of the File-In and the File-Out connectivity maps.

For competeness, they will be shown :

cmFileIn

cmFileOut

Create the Main Business Process Connectivity Map• Right Click Deployment and select “New/Connectivity Map”

Give it the name “cmMain”

• Drage the business prcess “mainBusinessProcess” onto the connectivity map canvas and double click to open up.Repeat for “subBusinessProcess”

• Drag the queues “qReceive” and “qSend” onto the canvas. Place them either side of the mainBusinessProcess.

• Drag a “Web Connector” and a “WorkListManager “ connector onto the canvas.

• Link the components up as shown.

• Double click the red circle between the “WebConnector1” and the “mainBusinessProcess” and click “OK” the red circle will go.

• Save your Connectivity map.

Creating The EnvironmentThe encironment represents the physical resources to run the business process project.

The Basics• Click on the Services TAB. There you will see the CAPS Environments node.

• Right Click “CAPS Environments” and select “New Environment”. Give it the name “WLManager”.

• Right click “WLManager” and select “New/LogicalHost” Give this the name “lhWLManager”

• Right Click “lhWLManager” and select “New/Sun Java System Application Server”Rename this to “Domain1”

• Right Click “Domain1”, Select “Properties”. Verify the URL and the Password to the application server. Once done, click OK.

• Right Click “lhWLManager” and select “New/Sun Java System Message Queue”Rename it to “mqWLManager”

• Right click “mqWLManager” and verify the host/port, username and password. Once done, click OK.

• Right Click WLManager and select “New/File External System”. Give it the name “ewFile”.

• Right Click “ewFile” and select “Properties”.

• Set the Inbound Parameter settings to a directory to pick up the file. In this case “C:\INDATA”

• Set the Outbound Parameters Settings to a directorty to write the file. In this case “C:\OUTDATA”

• Click OK and Save.

Composite Page Designer• Right click “WLManager” and select “New/Composite Page Designer...” and give it the

name “cpdWLManager”

• Right click “cpdWLManager” and select “Properties”. Set the User Role to the entityDN from your LDAP server. In this example, the value is “dc=wa,dc=gov,dc=ssc”. Then click OK.

WorkList Manager• Right Click the “WLManager” environment and select “New/Work List Manager...” and

give it the name “wlmWLManager”.

• Right Click “wlmWLManager” and select “Properties”.

• Click on “WLMConnector External System Configuration”. Here we set up the database connectivity to the tablespace we configured earlier in this tutorial.

• For “Connection Parameters” We need to change the value from “OpenLdapConnection” to “Sun Java System Directory Server”

• Expand out “WLMConnector External System Configuration” and click on “Sun Java System Directory Server/ADS”

• Here Details are populated with regards to the LDAP server and where to find entries. See

the “Sun Java System Directory Server Configuration Properties” section for more information on the fields.

ass

• sexy Click OK and Save your changes.

Create the Deployment Profile• Click back on the “Projects” tab

• Expand out “WLTutorial/Deployment” and right click “Deployment”.

• Select “New/Deployment Profile”

• Give the Deployment profile the name “dpWLManager” and change the environment to “WLManager” and click “OK”.

• Click “Automap” to map all your components and select “Build” to build your project.

• Start your application server and select “Deploy” to deploy your project onto the server.

Add the log level for “com.stc.bpms.bpelImpl” to “FINEST” to see your log statements for the business process in the log file.

A Restart of the application server may be required for changes to take effect.

Running Through A Scenario• Place File in Directory, in this case the directory is C:\INDATA where its looking for a file

of type Input#.txt where # is a sequence number.The file should contain a name. For example “Holger Paffrath”

• Check the Worklist for an entryGo to http://<hostname>/<port>/wlmwhere <hostname> is the hostname of the application server.<port> is the port number where web based apps run. By default its 8080You will be asked for a login name and password. Use the details set up in the LDAP server.

• You will then see the main activity window.

• Click on a pending task and click the “Checkout” button. The task will now be assigned to you.

• Click the “Execute” button. The task will now execute by bringing up the web page we created earlier.

• Select “Approve” or “Disapprove” and click Submit. This is the user activity portion of the business process. Thjis can be more complex, this is just a simple example.

• The Close Window will appear, click “Close Window” to close the Window.

• Once you have completed your task, go back into the “Worklist Manager” window and click the “Complete” button. This will complete the task.

Note : The sub-business process will not compelte until the “Complete” button is pressed. So if you are waiting for a result – check that your task has been completed.

• Finally, go to your Outbound Directory, in this case it is “C:\OUTDATA” and you should see a new “output1.dat” file. Inside you should see your input data and approve or disapprove depenmding on the radio button selection. For exampleHolger Paffrath : Approveor Holger Paffrath : Disapprove

In the Worklist Manager Screen, you have the added option to re-assign tasks to subordinates. To re-assign a task.

• Change the user in the “Reassign selected task to:” dropdown box to the user you wish to assign a task to.

Note : You can only assign tasks to subordinates. These subordinates need to be configured in your LDAP server.

• Click the “Re-assign” button.

• To Escalate a task to management, Press the “Escalate” button. You will then be prompted for confirmation.

Sun Java System Directory Server Configuration PropertiesThe following is the details required for configuring the WorkList Manager Component in the environment, specifically for LDAP Connectivity.

Property DescriptionJava Naming Provider URL The URL of the LDAP server. The format of the URL is

ldap://<host>:<port>, where <host> is the name of the computer hosting the LDAP server, and <port> is the port number on which the LDAP server is listening for requests.

Java Naming Factory Initial The fully qualified name of the factory class that creates the initial context. The initial context is the starting point for JNDI naming operations.

Java Naming Security Authentication

The security level to use in JNDI naming operations. Enter one of the following values:

• none: Authentication is not required. Use this for anonymous access.

• simple: Authentication requires a user name and password. You must enter the security principal and credentials below.

Java Naming Security Principal The DN of the security principal used for connecting to the LDAP server.

Java Naming Security Credentials

The password of the naming security principal.

Users ParentDN The parent DN of the user entries. This property specifies the root entry of the Users portion of the LDAP directory; for example, ou=People,dc=sun,dc=com.

UserDN Attribute Name In User Name In User

The name of the attribute in a user entry where the user’s DN is defined. The default value is entrydn, which is the default name for the Sun Java System Directory Server attribute.

UserId Attribute Name In User The name of the naming attribute in each user entry. The default name for this attribute in the Sun Java System Directory Server is uid, but can also be cn.

Roles Parent DN The parent DN of the role entries. This property specifies the root entry of the Roles portion of the LDAP directory; for example, dc=sun,dc=com.

Role Name Field In RoleDN The name of the attribute in a role entry that specifies the name of the role. The default name for this attribute in the Sun Java System Directory Server is cn.

Role Name Attribute Name In User

The name of the attribute in a user entry that specifies the DNs of the roles to which a user is assigned. The default value is nsroledn, which is the default attribute name in the Sun Java

System Directory Server. Group ParentDN The parent DN of the group entries. This property specifies the

root entry of the Groups portion of the LDAP directory; for example ou=Groups,dc=sun,dc=com.

Group DN Attribute Name In Group

The name of the attribute in a group entry that specifies the name of the group. The default value is entrydn, which is the default name for the Sun Java System Directory Server attribute.

Group Name Field In Group DN The name of the attribute in a group entry that specifies the name of the group. The default name for this attribute in the Sun Java System Directory Server is cn.

Group Of User Filter Under Groups ParentDN

The LDAP search filter used to retrieve all of a user’s groups. This property follows the syntax supported by the java.text.MessageFormat class with {1} marking where the user’s DN should be inserted. For example, uniquemember={1}.

UserId Attribute Manager The name of the attribute in a user entry that specifies the person the user reports to. The default value is manager, which is the attribute the Sun Java System Directory Server provides for this purpose. You can also use the entrydn for this purpose, or you can create custom attributes to define an upward reporting structure.

Note: To enable task escalation and re-assignment, this value must be manager and each user entry in the LDAP directory must include a manager attribute that specifies the supervisor by their entrydn.

UserId Attribute Subordinate The name of the attribute in a user entry that specifies the people who report to the user. The default value is directReports, which is not used in the Sun Java System Directory Server. You can use a default attribute for Sun, such as secretary or entrydn, or you can create custom attributes to define the downward reporting structure.

Note: To enable task escalation and re-assignment, this value must be entrydn and the reporting structure for each user must be defined in their entrydn attribute in the LDAP directory.

UserId Attribute Email The name of the attribute in a user entry that specifies an email address. The default value is mail, which is the attribute the Sun Java System Directory Server provides for this purpose. This is used for email notifications (as defined in the Worklist Manager window for a user activity in the BP).

UserId Attribute Given Name The name of the attribute in a user entry that specifies a user’s first name. The default value is givenName, which is the attribute the Sun Java System Directory Server provides for this purpose. This is used during email notification.

Add Logging to a Business Process• In your business process canvas, click on the component you wish to add logging to.

In the example, the business process is clicked, but just about any component can have logging added to it.

• Click on the Show Properties button to show the properties for the component.

• The properties window will appear. There should be one property we are interested in. “Logger Properties” Click on the […] button to configure.

• A Window will appear that is similar to the BPEL editor, but it has different logging levels on the right side. These are the logging levels that log entries will be written to. So using the tools available to the BPEL process, you can add logging to your business process.

The example below adds the entry “[===] File In Business Process” at logging level “Information”.

• Click OK and save your business process.

Creating Sample Users in Sun Java Directory ServicesLog into the Sun Directory Server using the url http://hostname:port/dscc.For example http://10.20.20.47:38080/dscc

Enter the User name and password. By default, the “admin” password is “adminadmin”.The following screen will appear.

Select the Directory Services Tab.

Then the Server Name. In this case its port1.wa.gov.ssc:30380

The following screen will appear.

Select “Entry Management”

What appears is a view of the current LDAP entries in the Sun Directory Server. In our case, we have some entries pre-configured for another application, these are not set up for Java CAPS.

The Hierachy we are going to set up is as follows• wladmin1

• wluser1• wluser2

Here wladmin1 is the manager and wluser1, wluser2 are the subordinates.Wladmin1 can assign tasks to wluser1 and wluser2.Wluser1 and wluser2 can escalate to wladmin1.

Now lets create a new user.

Select the “dc=wa,dc=gov,dc=ssc” (for wluser1 and wlusser2 use “uid=wladmin1,dc=wa,dc=gov,dc=ssc) entry and press the “New Entry” button.

The “Entry Parent DN” is displayed.

Click “Next”

We are going to create the user now, so select “User – inetOrgPerson” and click “Next”.

Here we enter the attributes for the person. All that is required is a First Name and a Last Name. We need to add more to this. We need to include a User ID and Password.In the above example, I've added the user name for the worklist administrator wladmin1.(For wluser1 and wluser2, an additional attribute to signify the manager needs to be specified. Scroll down for the manager attribute and put in the entitydn for wladmin1. This is uid=wladmin1,dc=wa,dc=gov,dc=ssc)

Once all the details for the user are entered, click “Next”Again we see the summary screen for the user. Click Finish to Continue

Our new user is created.

Repeat the above process to create wluser1 and wluser2 under the wladmin1 user.

ReferencesUsing the Sun Business Process Manager Worklist Manager for User Activitieshttp://docs.sun.com/app/docs/doc/820-3405/ueiswm_intro?a=view

eInsight Business Process Manager User Guide, Appendix C “Audit Processing Tutorial”http://dlc.sun.com/pdf/820-0957/820-0957.pdf

Configuring the Worklist Managerhttp://developers.sun.com/docs/javacaps/configuring/jcapsconfec.ggqyz.html