Configure the business process container for portal

The default installation configures the business process container for you. However, you might need to manually configure the business process container in the following circumstances.

  • Install WebSphere Portal to an existing appserver.

  • Moving to a production-level database.

  • Install WebSphere Process Choreographer to a machine without portal.
Before you can manually configure the business process container for portal, verify that the Human Task Manager fix (PQ90654) is installed. If not, follow these steps:

  1. Install the interim fix for the human task manager to the appserver. For cluster configurations, install the interim fix to each node in the cluster. After installation, the human task manager application (task.ear) resides in the /installableapps directory of the appserver.

  2. Deploy the task.ear file by selecting Applications then click Install New Application in the administrative console. For cluster configurations, deploy the task.ear file only on the primary node.

  3. Set the human task manager JNDI name property in ConfigService.properties to the jndi name of the HumanTaskManager EJB, for example, 
    processintegration.htmJndiName = corbaname:iiop:localhost:2809#com/ibm/task/api/TaskManagerHome

    For cluster configurations, this change must be made on each node in the cluster.

After confirming that the Human Task Manager is installed, follow these steps to manually configure the business process container for portal.

  1. Edit the bpeconfig.properties file, located in the wp_root/config/helpers directory, and complete the missing values for each key. Refer to the file comments for more information.

  2. If you have an existing business process container configured for portal, first unconfigure the existing container by issuing this command. 
       WPSconfig.{bat | sh} bpe-unconfig

  3. If you use a database other than Cloudscape, execute the appropriate ddl files for creating the database. You can find the ddl files needed in the was_root/ProcessChoreographer directory. For example, for DB2, execute the createDatabaseDb2.ddl (which implicitly executes createSchemaDb2.ddl) and optionally execute the createTableSpaceDb2.ddl. The scripts contain short descriptions of how they are invoked. For more information, see this topic in the Information Center for WebSphere Business Integration Server Foundation, V5.1.x:

    http://publib.boulder.ibm.com/infocenter/ws51help/topic/com.ibm.wasee.doc/info/ee/workflow/tasks/t2data.html

     

  4. Configure the business process container by issuing this command. 
       WPSconfig.{bat | sh} bpe-config

  5. Configure the WMM Staff Plugin as follows:

    1. Ensure that the following properties are set corrently in the wpconfig.properties

      • WmmSystemId

      • WmmSystemIdPassword

      • WmmDbUser (if using a database other than Cloudscape)

      • WmmDbPassword (if using a database other than Cloudscape)

    2. Navigate to wp_root/config and enter the following command. 
      WPSconfig.{bat | sh} wpc-membermanager-cfg

    3. To verify the configuration in the appserver's Administrative Console, as follows:

      1. Click Resources.

      2. Click Staff Plugin Provider.

      3. Click Member Manager Staff Resolution Plugin.

      4. Select Staff Plugin configuration.

      5. Click custom properties and verify the correctness of the values that have been set.

 

See also

Home |

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.