Business Space:

1. What is Business Space? Business Space powered by WebSphere provides an integrated user experience for business users across the IBM WebSphere Business Process Management portfolio. Business Space provides a customizable and collaborative environment for monitoring, reviewing, and administering common business processes, such as human task flows, modeling, and performance indicators. Business Space is a browser-based graphical user interface that lets business users interact with content from products in the WebSphere Business Process Management portfolio. The business spaces you create are collections of related web content that provide you with insight into your business and the capability to react to changes in it. Business users can view the content they want to see in the way they want to see it by creating mashups. Mashups are combinations of web applications (widgets) configured on the pages of a business space that provide content from multiple sources. Business users can create as many mashup pages as they want to provide multiple views of their business. In addition to viewing content, business users can create mashups that act on their business by, for example, assigning people to various tasks or adjusting business rules for different outcomes. A business space groups related pages.

2. No. of ways to create business space You can create a business space in any of the following ways:

Creating a business space using the widget palette to define the tasks. Using a pre-configured template. Importing an existing business space.

A business space consists of pages that you define. Each page can contain one or more widgets that are configured to perform business tasks.Additionally, you can have many business spaces with each one having a different purpose. For example, a space with widgets from WebSphere Business Monitor can be used to monitor key performance indicators in your business. 3.Layout or various regions in Business Space

Business Space can display the contents of one business space at a time. This space is the open space. The open space consists of a banner area and a page area. The top of the banner contains

menus that contain options that affect the open business space or options for navigating to another space. The banner also contains a link to the documentation and a link to log out from Business Space. Below the menus, the banner area displays the name of the open space and tabs for the pages in the space. The page area is below the banner and displays an open page. The tab for the page is highlighted. 4.Working with Business Space You can create a business space, which makes you the owner of that business space. As the owner of a business space, you can modify it by, for example, creating pages in it and setting who can view or edit your business space. You can also delete the business space. If you are an editor of another person's business space, you can modify its properties and modify its content.

4.1 Creating Business Space To contain a collection of related pages, you can create a business space. Procedure(steps) for creating business space 1. Click Manage Spaces. The Space Manager opens. Note: You can also click Actions on the banner and then click Create Space to create a space. 2. Click Create Space. The Create Space window opens. 3. Type the name for the new space and a description. The name cannot contain the following characters: @ / \ : * ? " < > | 4. Select how you want to create the space: o Create a new space using a template, which creates a space that contains the pages and widgets that the template defines. Each template supports one or more scenarios by providing the widgets you need for the scenarios and organizing the widgets on the pages. You can also choose to create a blank space and add pages later. o Duplicate an existing space, which creates a space that contains the same pages and widgets as an existing space. 5. Select a style to set the look for the pages in the new business space. You can also select an icon for the space. In Business Space running on WebSphere Portal Server, the business space automatically has the default Business Space style and icon applied. You can select a different style only when you are editing a page and you can select a different icon only when editing the space settings. 6. Click Save. The Create Space window closes and the Space Manager lists the new space in Favorite Spaces. A default Page 1 is added to the space.

Note: If you want to remove the business space from Favorite Spaces, select the space, click Actions and then click Remove from Favorites. 7. To close the Space Manager, click Done. 2. With the pre-configured templates that come with Business Space, you can create a business space that contains pages and widgets.You can select a template when you create a business space. 3. There are two types of templates. Product templates have widgets from a single product. The Create Space window lists only the product templates for the products that your company has installed. Cross-product templates have widgets from more than one product. The Create Space window lists all of the crossproduct templates. If you create a space based on a cross-product template and there are widgets in it provided by products that are not installed or available, Business Space substitutes a placeholder image for widgets that are not available for use. A superuser can use the Space Manager to convert a business space into a template. The template can then be shared with other users

5. Business Space access levels

You can set whether a user can access a business space or a page and what the user can do within that space or page. If a user does not have a defined role (either assigned specifically or inherited by belonging to a group with an assigned role), that user is not able to access the page or space. The following table lists the roles within Business Space and what members of each role can do: Viewer This user can navigate the pages in a business space and see the widgets on a page. A viewer can also change the size of the widgets on the page. Resizing widgets is specific to each user so other users are not affected by this change. This user can add and modify pages in a space and add, configure, and delete widgets in a page. Additionally, an editor can do anything that a viewer can do. If an editor creates a page, they are the owner of that page, even if they are not the owner of the space containing the page. This user can delete, transfer ownership, and determine who has access to the space and individual pages and determine whether users have viewer or editor access. The initial owner of a space or page is the person who created it. Additionally, an owner can do anything that an editor can do. A space owner automatically has owner access to every page in the space.

Editor

Owner

Superuser This user has administrative rights and has owner access to all spaces and pages. A superuser can share access to a space or page with selected users or all authenticated users. A superuser can also create and manage templates.

6. Changing the owner of a business space

If you own a business space, you can transfer ownership of that business space to another person. When you create a business space, you are automatically the owner of that business space. You can change the ownership of that space to another person. That person gains the owner role. If you are in the viewer or editor list, you have that role. If you are not on either list, you do not have a role and you might not be able to access the space. To share a space:

Procedure:
1. Click Manage Spaces. The Space Manager opens. 2. For the space you want to share, click Actions > Edit Settings. The Edit Settings window opens. 3. Where the window displays the space owner, click Change. The Change Ownerwindow opens. 4. Type the name or partial name into the search field and click Search. The Search Results field displays the user names that contain the search field text anywhere in their name or ID. 5. Select the new owner of the space. 6. Set the type of access that you will have after you have transferred ownership. The default value is that you will not be able to edit or view the space after you have transferred ownership. This means that if you need to access the page again, you will need to contact the new owner or a superuser to give you the appropriate level of access. 7. Click Save. The Change Owner window closes. In the Edit Settings window, the space owner field displays the name of the new owner. 8. To close the Space Manager, click Done.

7. Managing Human Task Tutorials

7.1Tutorial: Managing your work This tutorial describes how you can use a business space to manage the work that is assigned to you in a timely manner. The tutorial is an example of how to use Business Space to manage your work using the Tasks List and Task Information widgets. In this example, you are responsible for sending out quotations for orders. Each quotation request is a separate task. One of the customer satisfaction requirements is that a customer must receive a quotation within 24 hours of asking for one. Imagine that your responsibilities include checking the queue of quotation requests and handling the requests in a timely manner. To perform these responsibilities, you use Business Space to complete the following steps.

Procedure 1. You log onto Business Space and open the space that you use for checking quotation requests. Your Tasks List widget shows the requests that are waiting for you. You want to see which of these requests are urgent so that you can work on them first. 2. You sort your list of tasks by priority. 3. After reviewing the list, you edit the most urgent task in your list. The Task Information widget displays the details of the task. You have the information that is needed to complete the task available to you. You enter the required information and submit the task. The Tasks List widget is updated to remove the completed task from your task list. You continue to work on the remaining tasks in your task list. 4. After you complete the tasks in your task list, you filter the Tasks List so that you can review the tasks that are available to you. These tasks do not have anybody working on them yet. You accept and edit some of the tasks in the list. The Task Information widget displays the details of all of the selected tasks. If you filter the tasks using Tasks I Own, the Tasks List widget is also updated to include these tasks. 5. You review the details of the tasks and notice that some of these tasks are outside of your area of expertise, so you return them to the available tasks. The Tasks List widget is automatically updated to remove theses returned tasks from your Tasks I Own list. 7.2 Tutorial: Processing work using page flows This tutorial describes how to work with page flows. A page flow is a type of business process that controls the sequence in which you interact with tasks in the process. When you complete a task, the next task in the flow is automatically displayed. For example, a claims handling process has a specific set of steps, or tasks, that you need to do to handle the claim. You can use a page flow to control this sequence of steps. A page flow is also referred to as a single person workflow or a screen flow.

The tutorial uses the pages and widgets of a space that was created from the Advanced Managing of Human Tasks and Workflows template. Some of the steps and information might not apply for your situation. Adapt the tutorial to fit your needs. Page flows require that the human task activities that comprise the flow have the following properties set in the process model:

Each of the human tasks in the page flow must have the htm.hasNext custom property set to true, except the last human task in the sequence. This task must have the htm.hasNext custom property set to false.

Because the next human task in the page flow must be made available in the transaction of the human task that completed, the transactional behavior of all the human tasks must be set to participates.

About this task

The tutorial is an example of how to use Business Space to complete a sequence of tasks in a page flow. In this example, you are responsible for handling insurance claims. Imagine that you are responsible for all of the work involved in handling an insurance claim. To perform this responsibility, you use Business Space to complete the following steps. Procedure 1. You log on to Business Space and open the space that you use for handling claims. Your Tasks List widget shows the claims that are waiting for you to work on. 2. You review the list of claims, and accept the most urgent claim to work on. The Task Information widget displays the details of the claim. 3. You have the information that you need to complete this step of the claims handling process. You enter the required information, submit the task, and click Next. The task that represents the next step in the claims handling process is automatically shown in the Task Information widget. 4. Again, you have the information that you need to complete this step of the claims handling process. You enter the required information, submit the task, and click Next. The task that represents the next step in the claims handling process is automatically shown in the Task Information widget. 5. This time, you do not have the information you need to complete this step of the process, and you close the task. The task is displayed in the list of tasks in the Tasks List widget. You continue working on other claims in your list. 6. After a while, you get the information that you need to complete the unfinished claim. In your Tasks List widget, you select and edit the claim. The Task Information widget displays the details of the task that you were working on when you interrupted your work on the claim. You enter the required information and submit the task to complete the processing of the claim.

7.3 Tutorial: Working continuously on tasks This tutorial shows how to use the working-continuously pattern to interact with tasks without using a Tasks List widget to explicitly select the next task to work on. When you complete a task, the next task is automatically displayed. The working-continuously pattern is also referred to as the get-next pattern. This tutorial uses widgets that contain content from WebSphere Process Server. To run the tutorial, WebSphere Process Server must be installed. The tutorial uses the pages and widgets of

a space that was created from the Advanced Managing of Human Tasks and Workflows template. Some of the steps and information might not apply for your situation. Adapt the tutorial to fit your needs. In this scenario, the Task Information widget on the Work Continuously page of the space is configured to use a custom query table. This query table contains a filter to return only travel approval tasks. Additionally, the query table includes a query property that provides the start date of the business trip. This property was specified in the process model and it is used as the order criteria for the next task.

About this task

The tutorial is an example of how to use Business Space to continuously work on tasks. In this example, you are a manager of a department. One of your responsibilities is to approve travel requests for the employees in your department. Three of your employees have submitted travel requests for your approval; one is for a business trip starting tomorrow, another is for a business trip starting in three days time, and the final request is for a business trip that is scheduled to start next week. Imagine that it is your responsibility to approve the requests. To perform this responsibility, you use Business Space to complete the following steps. Procedure 1. You log on to Business Space and open the space that you use for reviewing and approving travel requests. 2. You switch to the Work Continuously page, your Task Information widget shows the first request that is waiting for your approval. Because of the configured order criteria, the approval request for the business trip starting tomorrow is shown. 3. You review the information that your employee provided about the business trip, and decide to approve the travel request. You submit the task, and the next travel approval request is displayed automatically. Because of the configured order criteria, the approval request for the trip that is due to start in three days is shown next. 4. You review the information and add some notes to the task before you call your employee to get some additional information. To ensure that you do not lose the notes you have just made, you save the request. 5. After you talk to your employee, you decide to reject the request. You submit your decision, and the next task is displayed automatically. The approval request for the trip that is due to start next week is shown. 6. You review this request and approve the business trip. You are notified that there are no further travel requests waiting for approval. 7. One of your employees tells you that he needs to visit a customer at the end of the week and that he has submitted a travel request for your approval. On your Work Continuously page, you click Accept available. The new request is displayed, and you can continue to work on it.

7.4 Tutorial: Creating tasks This tutorial describes how you can use a business space to create new tasks.This tutorial uses widgets that contain content from WebSphere Process Server. To run the tutorial, WebSphere Process Server must be installed. Some of the steps and information might not apply for your situation. Adapt the tutorial to fit your needs.

About this task

The tutorial is an example of how to use Business Space to create tasks for other people. Imagine that you work in the customer support department of a communications company. You have just received a call from a customer representative that you urgently need to travel to a customer site to investigate a network problem. Before you can make your travel arrangements, you need to get approval from your manager for the trip. Procedure 1. You log on to Business Space and open the space that you use for creating travel approval requests. 2. You switch to the Create Tasks page and create a travel approval request using the Task Definitions List widget. 3. In the Task Information widget, you enter the user ID of the approver, who, in this case is your manager, and explain that you need approval within 24 hours, and you attach a document with a detailed travel itinerary. 4. After 24 hours, you check the progress of your approval request using the Tasks List widget with the filter Tasks I Created. You filter the tasks that are shown in the All tasks list to show only those that are finished. You notice that your manager has not approved the request. 5. Because your company's travel policy requires that your manager approves the request before you can confirm your travel arrangements, and you need to go to the customer site urgently, you decide to escalate the request. You select the request from the Tasks List widget, then select Escalate from the Actions. The approval is escalated to your manager who receives e-mail notification so that he knows he needs to take action. . 7.5 Tutorial: Dynamically changing a workflow This tutorial describes how you might use Business Space to dynamically change the path through a workflow, for example, to skip tasks that are not needed in a particular context. This tutorial uses widgets that contain content from WebSphere Process Server. To run the tutorial, WebSphere Process Server must be installed. The tutorial uses the pages and widgets of a space created from the Managing Tasks and Workflow template. Some of the steps and information might not apply for your situation. Adapt the tutorial to fit your needs.

The tutorial is an example of how to use Business Space to dynamically change the workflow using the Tasks List, Task Information, Task Definitions List, and Human Workflow Diagram widgets. In this tutorial, you are responsible for handling enquiries about mobile phone contracts. Imagine that you work in a call center for a mobile phone company and are responsible for handling enquiries about phone contracts. A customer has just called to say that she wants to cancel her current contract. You need to find her current contract and check whether she can cancel the contract at this time. To perform these responsibilities, you use Business Space to complete the following steps. Procedure 1. You log onto Business Space and open the space that you use for working with customer contracts. 2. You switch to the Create Tasks page and you use the Task Definitions List widget to create a task for processing the cancellation of the customer's contract. You enter the phone details in the Task Information widget and submit the task. 3. You switch to your Tasks List widget, and edit the task that allows you to continue to process the cancellation request. a. You enter the customer information in the Task Information widget. b. Usually, when a contract is cancelled, you must send the customer information about the company's latest offers. However, the customer stated that she did not want any information sent to her. So, you switch to the Human Workflow Diagram widget, skip the task for preparing a new offer, and submit your updates. 4. You refresh your Tasks List widget and find a request to check the details of the cancellation request. 5. You edit the task and check the PDF of the contract that is attached to the form in the Task Information widget. You see that the contract is just over 12 months old. However, you are not sure whether this particular contract type must run for at least 24 months before it can be cancelled. 6. You decide to ask one of your colleagues for help on the contract conditions. To get this additional information, you perform the following steps: a. In the Task Information widget, you create an Inquiry task for your colleague to get the information that you need. The Tasks List widget updates to show that the check details task is pending. The Human Workflow Diagram widget shows the new dependent task for the check details task. b. You save the changes that you have done on the task so far and continue to work on other tasks. Your check details task is pending until your colleague gives you the information. c. When your colleague completes the dependent task, your Tasks List widget is updated to show that check details task is no longer pending. d. You edit the check details task and check the Related Tasks in the Task Information widget to see your colleague's answer.

e. Based on this answer, you decide that you can cancel the contract and you submit the check details task. 7. You prepare the confirmation letter for the customer but notice that there are some inconsistencies between the letter and the contract. You decide that it is better if one of the contract specialists reviews the contract details again. You go to the Human Workflow Diagram widget and redo the check details task. You add the information about the problem in the Task Information widget and transfer the task to your colleague. 8. Your colleague opens the review contract details task and checks the information about the contract, including the attached documents, in the Task Information widget. He sees the discrepancies and makes the necessary corrections and then submits the task. 7.5 Tutorial: Managing human tasks This tutorial describes how you can use a business space to assign tasks to a member of your team. This tutorial uses widgets that contain content from WebSphere Process Server. To run the tutorial, WebSphere Process Server must be installed. Some of the steps and information might not apply for your situation. Adapt the tutorial to fit your needs.

About this task

The tutorial is an example of how to use Business Space to assign tasks to other people. Imagine that you are team leader in the claims department of an insurance company. It is your responsibility to ensure that your team handles claims efficiently. You have vacation tomorrow so you need to assess the current claims and delegate them to one of your team members to work on in your absence. Procedure 1. You log on to Business Space and open the space that you use to manage claim reviews. 2. You select the process definition for managing claims from the Process Definitions List widget. The Task Definitions List lists all the task templates defined as part of this process. 3. You select Review Claim from the list of task templates. All instances of the type Review Claim are displayed in the Tasks List widget. You define a filter on the owner column so that you display only those tasks that are assigned to you. 4. You want to transfer all of the claims assigned to you to one of your team members, so in the Tasks List you select all tasks, then Transfer from the Actions list. You then enter the name of the team member to whom you want to transfer your claims. 7.6Tutorial: Managing human workflows This tutorial describes how you can use a business space to check the status of your tasks.

This tutorial uses widgets that contain content from WebSphere Process Server. To run the tutorial, WebSphere Process Server must be installed. Some of the steps and information might not apply for your situation. Adapt the tutorial to fit your needs.

About this task

The tutorial is an example of how to use Business Space to check the status of your tasks. Imagine that you work in the claims department of an insurance company. A customer, Mr. Smith, contacts you to find out the status of a claim, which you filed last week. Procedure 1. You log on to Business Space and open the space you use to track the status of claims you have filed. 2. You select the process definition for managing claims from the Process Definitions List widget. The Processes List lists all the processes for managing claims. 3. You set a filter on the processes list to display all instances for customers called Smith. 4. This filter returns too many entries, but as you know that you filed the claim last week, you decide to add the filter Date range. In the field Since you specify a date for the Monday of last week. 5. This reduces the number of processes returned to a manageable size and you can find the process for Mr. Smith's claim. You open the claim in the human workflow diagram to check its status. 6. You decide you want to view more details about the claim, such as the history, additional notes, and related tasks. To do this, you open the Review Claim task in the Task Information widget, where you can review all the detailed information about the claim. 7.7 Tutorial: Managing my team's tasks This tutorial describes how you can use a business space to assign tasks to a member of your team. This tutorial uses widgets that contain content from WebSphere Process Server. To run the tutorial, WebSphere Process Server must be installed. Some of the steps and information might not apply for your situation. Adapt the tutorial to fit your needs.

About this task

In this tutorial, your team is responsible for sending out quotes for orders. As a supervisor, you need to balance your team's workload and ensure that high-priority tasks are handled quickly. To perform these responsibilities, you use Business Space and complete the following steps: Procedure 1. You log onto Business Space and open the space that you use for supervising your team.

2. In the Managed Team Tasks page, set the My Team's Tasks widget to display open tasks organized by owner so that you can see your team's workload. To do this, set the Group by field to owner and set the Show field to In progress. Note: If a team member does not have any in progress tasks, My Team's Tasks does not display that person. Additionally, that person is not included in the calculation of team workload. For example, if a team has three members and two of the members have one task each, My Team's Tasks displays just the two members and shows each member has 50% of the tasks. 3. You notice that one team member has too many tasks to complete them on time, so you decide to transfer a critical task to another team member. a. Select the task. The Team List updates to show the users who are eligible to work on the task. b. Select Transfer from the Actions list, then enter in the name of the user to whom you want to transfer the task. When that user opens a business space containing a Tasks List widget, the user will see the task.

Example: (a) Create a new module File>New>Module In the Module Name field enter 'HumanInteraction' and then click Next and select Eager Parsing mode for the module and then click finish.

(b)Define the interfaces

This sample requires two interfaces: one for the process and one for the human task. To create each interface, complete the following steps:

1. 2. 3. 4. 5. 6.

In the Business Integration view, right-click HumanInteraction > Interfaces. From the context menu, select New > Interface. The New Interface Wizard window opens. In the Folder field, enter bpc/samples/task. In the Name field, enter ProcessInterface. Click Finish. Repeat the steps above for the second interface. for Folder=bpc/samples/task andName=Question. Use the following values

Now, add operations to your interfaces. To add operations to an interface, complete the following steps:

1. 2. 3. 4. 5.

In the interface editor, click the Add Request Response Operation button . To edit the name of the operation, click the operation name. See the table below for the operation names you need to specify. To edit the name of an input message, click the message name. See the table below for the message names you need to specify. To edit the type of an input message, click the message type, and select a type from the list. See the table below for the types you need to specify (in this sample, all types are string, which is the default). Repeat steps 4 and 5 to edit the name and type of the output message.

In the folder bpc/samples/task, create the interfaces that are listed in the following table: Interface Namespace Operation Name Message Name Input Output Question http://bpc/samples/task/Question ask Input Output input output Type string string

ProcessInterface http://bpc/samples/task/ProcessInterface process

question string answer string

3.Develop the business process Create a new business process

To create the new business process, complete the following steps:

1. 2. 3.

4. 5. 6. In the Name field, enter HumanInteractionProcess. 7. Accept the default value for the namespace. 8. Click Next. 9. In the Select a Business Process Type panel, select Long-running process. 10. Click Next. 11. In the Select an Interface panel, select Select an interface. 12. Click Browse. The Interface Selection window opens. 13. Select ProcessInterface, then click OK. 14. Make sure that process is selected as operation. 15. Click Finish. The business process editor opens.

Switch to the Business Integration view. In the navigation tree, right-click HumanInteraction > Integration Logic. From the context menu, select New > Business Process. The New Business Process window opens. Select the radio button New default Business Process. In the Folder field, enter bpc/samples/task.

16. Open the Properties view and proceed to the Details section. 17. From the Automatically delete the process after completion list, select No. 18. Keep the remaining default values.
Add a human task activity to the process
To add a human task activity to your process, follow theses steps:

1. 2.

Click the human task activity icon on the palette. In the business process editor, click the connection between Receive and Reply:

The human task activity will be added and the Interface Selection window opens automatically. 3.Select Question, and click OK. The Human Task editor opens: Since you've already selected the Question interface, the ask operation is chosen by default (it's the only operation defined).

1. 2. 3. 4.

Close the HumanInteractionProcessTask1 editor. In the HumanInteractionProcess editor, select the HumanTask component. Rename the human task activity from HumanInteractionProcessTask1 to AskQuestion. On the toolbar, click the Save button .

Implement the human task activity

To complete the implementation of our human task activity, you have to specify the process variables for the activity. Follow these steps:

1. 2. 3. 4. 5. 6. 7.

In the business process editor, click AskQuestion. In the Properties view, click the Details tab. Click none under Read From Variable. A popup with available variables opens. Select input. Click none under Store Into Variable. A popup with available variables opens. Select output. On the toolbar, click the Save button

Adjust Business Space Settings

Enable the human task activity for Business Space

Use Business Space to work with the human task. For this, we have to enable the human task activity for Business Space. Follow theses steps:

1. 2. 3. 4. 5. 6. 7. 8. 9.

In the business process editor, click AskQuestion. In the Properties view, click the Details tab. Click Open next to HumanInteractionProcessTask1. The human task editor opens. Expand the User Interface section. Click the + symbol next to User Interface and select HTML-Dojo (for use in Business Space). In the Properties view of the HTML-Dojo, click New. In the popup window, click New Web Project button. In dialog, enter HumanInteractionWebproject as Project name button. Make sure the EAR Project Name is HumanInteractionApp.

10. Accept all other defaults and click Finish. Do not switch to the Web perspective. 11. Click OK to save the HTML file 12. On the toolbar, click the Save button
to save the human task changes

Enable the business process for Business Space During runnning the sample you will as well use Business Space to start an instance of this business process. Because Business Space will render the display name of the first activity, here we specify a name for the Receive activity that can be easily recognized. Follow theses steps:

1. 2. 3. 4. 5.

In the business process editor, Right-click the Receive activity. Select Show in Properties. In the Properties view, change Display Name from HumanInteractionProcess.

Receive

to Start

the

Optionally, add a description text that will as well show up in Business Space windows later on. Here, we usemy first business process with a human interaction inside as description text. On the toolbar, click the Save button .

For starting an instance of this process using Business Space, it is required to specify an inline invocation task for the first activity. Follow these steps:

1. 2. 3. 4. 5. 6. 7. 8.

In the Properties view of the first activity, select the Authorization tab. Click the New button. The Human Task editor opens. Expand the User Interface section. Click the + symbol next to User Interface and select HTML-Dojo (for use in Business Space). In the Properties view of the HTML-Dojo, click New. In the popup window, select the existing folder WebContent of the previously created web project. Click OK to generate the HTML file. On the menu bar, select File > Save All to save both the invocation task and the business process.

Module assembly To finish the implementation of the human interaction process, you have to create the module assembly. Complete the following steps:

1. 2. 3.

In the Business Integration view, double-click HumanInteraction > Assembly Diagram. Drag and drop the HumanInteractionProcess process to the assembly editor. On the toolbar, click the Save button.

Testing the Sample:

Run the sample Because the business process and the human task were enabled for Business Space in the previous section, one can use Business Space to run this sample

1. Using Business Space for running the sample

In the following all steps are described to set up Business Space for human tasks and to start and complete a business process. Note: If you run this sample in a cluster configuration where Business Space and WPS run on different nodes, make sure that the WAR (Web Archive) module is mapped to both the server running WPS and the server running Business Space. To start Business Space in the integrated test environment of your WebSphere Integration Developer, follow these steps:

1. 2. 3.

In WebSphere Integration Developer, switch to the Servers view. In the table, right-click WebSphere Process Server v7.0. From the pop-up menu, select Launch > Business Space.

To start Business Space on WebSphere Process Server, follow these steps:

1.

In a web browser, open URL http://yourhost:yourport/BusinessSpace. Note: Replace yourhost with your server's internet address and replace yourport with the port of your server's HTTP transport, for example http://localhost:9080/BusinessSpace .

If security is enabled, Business Space opens with a login screen:

1. 2.

Enter a valid User ID and Password. The default User ID is admin. Click Login.

Depending on whether you have already worked with Business Space, a Business Space start screen is displayed, for example this one:

Create new Business Space

If you have not worked with human tasks in Business Space yet, do a one-time setup on your WPS server (this step can be skipped if you run this sample again later). Follow these steps:

1. 2.

In the Getting Started widget of the Welcome Business Space, click Manage Business Spaces: In the Business Space Manager, click the symbol + for creating a new Business Space:

3. 4.

In the popup menu, select a name for your Business Space, for example, my Business Space. Switch to From a template and select Advanced Managing of Human Tasks and Workflows.

5. 6.

Click OK. Click Done.

After clicking on Go to Spaces in the upper menu, your new Business Space is displayed:

Now you are ready to work on your human tasks with Business Space.

Start the sample business process

To start the human interaction process, follow these steps:

1. 2. 3.

Make sure HumanInteractionApp is installed on the server. Switch to Business Space. Proceed to the Manage Human Tasks tab.

4.

In the Manage Human Tasks widget, select the task template Start HumanInteractionProcess and click the symbol for creating a new instance.

the

In the Task Information widget, the form for completing the input data is displayed:

5. 6.

In the input field, enter a value of type string. Click Submit.

Now a business process is started, and the human task activity of the business process (in this sample: AskQuestion) is available for the userids specified in the task template of the human task (in this sample: everybody).

Work with the human task of the sample business process

This sample business process requires a human to enter a string into a data field. This string can be used in later steps of the process. In this example, there are no later steps; instead, we will browse the persisted output (i.e. the output message) after the process is finished. You can use either Business Space or the BPC Explorer to work with the generated human tasks. To use Business Space for working with human tasks, follow these steps:

1.

In Business Space, switch to the Work on Tasks tab.

2.

In the Tasks List widget, select AskQuestion and click the symbol for accepting and editing the task:

A form for processing the task is displayed in the Task Information widget; here, the output field is prefilled with the input that was entered by the user when starting the process instance, and then passed from the process instance to the task instance.

3.

Replace the text in the answer field by a text of your choice, for example, John Doe.

4.

Click Submit. The task is now completed and is removed from the Tasks List widget again.

Verify output

Output message
The human interaction process is a long-running business process, and the process output message is computed asynchronously. To display the process output message, follow these steps:

1.

In Business Space, proceed to the Create Tasks tab.

2. 3.

Select the most recent process instance with name Start the HumanInteractionProcess. Select Actions > Open:

In the Task Information widget, both the process input message and the process output message are displayed:

WebSphere Representational State Transfer (REST) APIs

WebSphere business process management servers provide a set of APIs that are implemented using the Representational State Transfer (REST) services. The Uniform Resource Identifiers (URIs) in these APIs are a set of REST services that access business process and task data.

WebSphere Process Server REST Interface WebSphere Process Server provides a set of APIs that are implemented using Representational State Transfer (REST) Services. The URIs are a set of REST services that access business process, human task.

Resource URLs
The URIs of the Business Process Choreographer REST resources have the following format:
http://{host}:{port}/rest/{component}/v1/{anyResource}?{query}

where:

"http://{host}:{port}" contains the host address and port "/rest/{component}" is the configurable context root, where component (providing a resource set) is e.g. bpm/htm. "/v1/{anyResource}?{query}" represents the logical resource

Resource Versioning
Each resource URL has a version identification (/v1) for handling changes to the REST API set that would break compatibility with existing REST clients. The following changes are considered compatible and must be expected by clients:

Adding new REST resource relationship to the resource model, without affecting existing navigation Adding additive information to REST representations that won't affect existing clients Adding a new MIME type / representation support Adding new properties to existing JSON objects returned to a client (ignored by backlevel clients) Adding new properties to existing JSON objects received from a client (defined as optional)

HTTP Methods
The WebSphere Process Server REST interface provides the following HTTP methods:

POST - create a resource GET - read a resource PUT - update a resource DELETE - delete a resource

Content Types
The data sent or returned by the HTTP methods has one of the following content types:

JSON ("Content-Type: application/json") is used for most WebSphere Process Server resources; for the detailed format of each returned object, see the JSON schema specifications for each operation XML ("Content-Type: application/xml") is used for customer data, that is, input, output, or fault data of processes or tasks, or variable data of a process; the actual format of each expected or returned object is defined in the XML schema provided by the individual process or task Other MIME types can be used for Business Process Choreographer binary custom properties

Simple-Typed XML Data

Some XML data objects represent WSDL message parts or BPEL variables that are defined with an XML schema simple type. In this case, a simple-typed value (which is not a valid XML document by itself) is wrapped within an XML element provided by the Business Process Choreographer REST interface. This wrapper is defined as follows:
<xsd:element name="simpleTypeWrapper" type="tSimpleTypeWrapper"/> <xsd:complexType name="tSimpleTypeWrapper"> <xsd:sequence> <xsd:element name="value" type="xsd:anySimpleType" nillable="true"/> </xsd:sequence> </xsd:complexType>

JSON Lists of Name/Value Pairs

Some JSON data objects contain a nested object with a list of name/value pairs such as { "a" : "Athens", "b" : "Belgrade", "c" : "Cairo" }. In the JSON schema descriptions below, these objects (in custom properties, client settings, and properties of users/groups) simply appear as generic {"type":"object"}.

Content Localization
For task descriptions, documentations, etc., a client should send the list of preferred languages in the "Accept-Language" HTTP header (example: "Accept-Language: da, engb;q=0.8, en;q=0.7" - "I prefer Danish, but will accept British English and other types of English"). The server responds with a "Content-Language" HTTP header (example: "Content-Language: en").

Content Encoding
HTTP request and response messages may contain compressed data. This is indicated by the "Content-Encoding" HTTP header (example: "Content-Encoding: gzip"). If the request message has a content encoding that is not recognized by the server then an HTTP status code 415 Unsupported Media Type is returned. A client may indicate which content encodings are acceptable by using the "AcceptEncoding" HTTP header (example: "Accept-Encoding: gzip"). If the server is unable to respond with any of the listed content encodings then an HTTP status code 406 Not Acceptable is returned. If no "Accept-Encoding" HTTP header is specified in the request message then by default the content encoding of the response message is "identity" (no encoding), indicated by the absence of the "Content-Encoding" HTTP header.

Error Handling
For errors recognized during processing of a WebSphere Process Server REST request, an appropriate HTTP status code is returned to the calling client (e.g., 200 OK or 404 Not

Found, see the individual operations for details). Additional error information is provided depending on the error type. For Business Process Choreographer exceptions, the corresponding Business Process Choreographer error number and error message is returned. For severe errors (HTTP status code 500 Internal Server Error), additional information about the problem is returned. You can send this information to IBM service personnel if required.

Security Considerations
Some firewalls do not allow HTTP PUT/DELETE traffic to traverse the firewall because of security considerations. As a workaround, PUT and DELETE requests can be 'tunneled' through a POST using the "X-Method-Override" or "X-HTTP-Method-Override" HTTP headers. The two headers are synonymous.