Configure virtual portals for process integration

You can enable a virtual portal for business process integration by running a setup task or by manually creating the My Tasks page, placing the Task List portlet on this page, and specifying the parent page for the task pages that will open from within the virtual portal.

To enable virtual portals for business process integration in a virtual portal, choose to run the setup task described in Step 1 or to perform the manual procedure described in Step 2:

1. To enable a virtual portal for business process integration programmatically, complete the following steps:

   1. Required: Before you begin Step b, make sure that you have run the task setup-wp.processintegration.config to enable business process integration for the portal environment using the appropriate procedure for your deployment scenario: single-cell or cross-cell. If you have not already run the task setup-wp.processintegration.config, the task described in the next step will fail.

   2. Open a command prompt, change the directory to profile_root/ConfigEngine and type the following command:

      Windows: ConfigEngine.bat setup-vp-wp.processintegration.config -DWasPassword=password -DVirtualPortalContext=virtual_portal_url_context

      UNIX: ConfigEngine.sh setup-vp-wp.processintegration.config -DWasPassword=password -DVirtualPortalContext=virtual_portal_url_context

2. To enable a virtual portal for business process integration manually, complete the following steps:

   1. Log in into the virtual portal.

   2. Click Administration > Portal User Interface > Manage Pages.

   3. Create a new page to contain the Task List portlet for the virtual portal and set a unique name of this page.

   4. Place the Task List portlet on that page.

   5. From the Task List portlet menu, click Configure and type in the unique name of the page that will be used as the parent page for all task pages opened from the given Task List portlet. Typically you use the page that created in Step c and specify the corresponding unique name.

   6. To enable the page identified in Step e for dynamic page display, open a command prompt, change the directory to profile_root/ConfigEngine, and type the following command:

      Windows: ConfigEngine.bat action-enable-page-as-extension-node-wp.dynamicui.config -DWasPassword=password -DPageUniqueName=task_page_container_name -DVirtualPortalContext=virtual_portal_url_context

      UNIX: ConfigEngine.sh action-enable-page-as-extension-node-wp.dynamicui.config -DWasPassword=password -DPageUniqueName=task_page_container_name -DVirtualPortalContext=virtual_portal_url_context

   7. To use the pending tasks tag within a virtual portal, use the identical unique name for the page that contains the Task List portlet in all virtual portals in which the pending task tag should be used.

Processes and tasks controlled by a given WebSphere Process Server installation are not automatically scoped for virtual portals. This means that users will see their personal tasks in all virtual portals where they are members.

Parent topic:

Customize process integration

Related tasks

Enable process integration

---