+

Search Tips   |   Advanced Search

Portal, V6.1

 

Modify process integration

If modify the default configuration of business process integration within the portal environment, you can perform some optional steps: Adjust the settings of the common process and task portlets that are provided by the automated setup task or edit the IBM WebSphere Portal Configuration Service, WP ConfigService, parameters for business process integration. Before you perform any of the optional modification tasks, be certain to verify that the automated setup task for process integration has completed successfully. Also consider having one or more process templates installed on the IBM WebSphere Process Server. Having a process template installed and deployed on the integrated process server allows you to see and work with the portlets that support process integration: Task List, My Processes, and Task Processing. Some preliminary work with these portlets will help you determine what adjustments you might need to make to the default configuration. You can modify the default settings of your process portal environment by performing one or more of the following optional steps:

  1. Change the values of the parameters that control the connections between the Human Task Manager and the Business Flow Manager of the WebSphere Process Server and the WebSphere Portal portlets that allow you to manage the workflow of business process applications. Edit one or more parameters in the Portal Configuration Service, WP ConfigService:

    processintegration.bfmJndiName

    Default value is cell/persistent/pi/BFMHome and points to either an Indirect Binding in a cross-cell setup or an EJB reference in a single-cell setup that points to the Business Flow Manager EJB that should be used.

    processintegration.htmJndiName

    Default value is cell/persistent/pi/HTMHome. This value points to either an Indirect Binding in a cross-cell setup or an EJB reference in a single-cell setup that points to the Human Task Manager EJB component that should be used.

    If change the names or locations of the referenced EJB components in a cross-cell setup, perform the following steps:

    1. From the Administrative Console of the portal server, click Environment > Naming > Name Space Bindings.

    2. Select _HTM_Binding or _BFMBinding.

    3. Change the Provider URL setting if the location of the EJB component should be changed

    4. Change the JNDI name setting if the name of the EJB component should be changed.

    If change the names or locations of the referenced EJB components in a single-cell setup, perform the following steps:

    1. From the Administrative Console of the deployment manager, click Environment > Naming > Name Space Binding.

    2. Select _HTM_Binding or _BFMBinding.

    3. If the location of the EJB component should be changed, perform the following steps:

      1. To connect to a single server, type the node name in the Node field and the server name in the Server Input field.

      2. To connect to a cluster, type the cluster name into the Server Input field.

    4. To change the name of the EJB component, modify the JNDI name setting.

      If, for some reason, change the name cell/persistent/pi/HTMHome or cell/persistent/pi/BFMHome, make sure that you change the value of processintegration.htmJndiName and that you also update the values in the EJB references of the portlet application PA_ProcessTemplates. From the Administrative Console of the portal server, if you have a cross-cell setup, or the deployment manager, if you have a single-cell setup, click Enterprise Applications > PA_ProcessTemplates > EJB References.

  2. Change the values of the parameters that control the pending tasks tag:

    • processintegration.pendingtasks.lifetime

      This property controls the lifetime (in seconds) of cache entries in the pending tasks cache being used by the portal-dynamicui:pendingTasks JSP tag. Each cache entry represents the pending tasks for a given user as queried from the process server. Increasing the lifetime will improve performance by reducing the number of queries against the process server while increasing the time lag until new pending tasks appear in the alert notifications for individual users.

    • processintegration.myTasksPageUniqueName

      This property specifies the page containing the Task List portlet. This setting is evaluated by the portal-dynamicui:pendingTasks JSP tag that allows users to navigate directly to the Task List from an alert message.

 

Parent topic

Customizing process integration

 

Related tasks


Customizing the process integration theme