Troubleshoot business process integration

---

 

Problem: After staff resolution has been changed in the process model and the process been redeployed, no changes can be recognized

This problem can occur when the staff query has not been updated.

Solution: Force an update of the staff resolution by executing the following command:

  refreshStaffQuery.jacl -server server1 -template templatename

 

Problem: The staff resolution is not working

This problem can manifest itself in the My Tasks portlet if the task list is not showing the correct tasks for the user. This problem can occur from one of the following possible causes:

• Wrong security settings, possibly in LDAP. For more information, see Enable WebSphere Application Server security for WebSphere Portal.
• Wrong verb settings or incorrect name/value pairs for a staff activity or the input (receive) node, as described under the security settings in Create the process. The process designer should check the settings for the process in Application Developer Integration Edition.
• Wrong JNDI name for the staff plugin specified, as described in Configure the business process container for portal.
• Because of a bug in Application Developer Integration Edition, the <process>.component file of the business process specifies wrong JNDI name for the staff plugin and needs to be manually adapted. The process designer should check the value of thye staffPlugin attribute of the <process/> element.
• No Potential Owner is defined for the input node as described under the security settings in Create the process. The process designer should check the settings for the process in Application Developer Integration Edition.

Solution: After checking and correcting these settings, force an update of the staff resolution by executing the following command:

  refreshStaffQuery.jacl -server server1 -template templatename

 

Problem: The LDAP system has been changed and staff resolution is not performed correctly anymore

This problem can occur from one of the following possible causes:

• Wrong filter settings in WebSphere Application Server.
• The security settings in the business process need to be updated with the LDAP changes.
• Wrong verb settings for the staff activity in the business process. This could be the search attribute changed from uid to cn or vice versa.

Solution: After checking and correcting these settings, force an update of the staff resolution by executing the following command:

  refreshStaffQuery.jacl -server server1 -template templatename

 

Problem: The process template is not available

This problem can occur from one of the following possible causes:

• The process EAR has not been installed correctly.
• The process EAR has not been started.

Solution: After checking and correcting these settings, force an update of the staff resolution by executing the following command:

  refreshStaffQuery.jacl -server server1 -template templatename

 

Problem: The process cannot be deployed/started

This problem can occur from one of the following possible causes:

• The process EAR file does not contain the right relational database (RDB) mappings as described under database support in Create the process.
• The checkbox for table creation was not selected when the business process was deployed. See Deploying the business process application for more information.
• During database creation for the business process container, tables have been created within a different schema as the database user specified in bpeconfig.properties. Check the settings in bpeconfig.properties and run the ddl scripts described in Configure the business process container for portal.

Solution: After checking and correcting these settings, force an update of the staff resolution by executing the following command:

  refreshStaffQuery.jacl -server server1 -template templatename

 

Problem: After the process has been initiated it jumps to the FAILED state

This problem can occur from one of the following possible causes:

• Wrong security settings in the process EAR.
• Wrong verb settings or verb JNDI specification for the staff activity in the process model.

Solution: After checking and correcting these settings, force an update of the staff resolution by executing the following command:

  refreshStaffQuery.jacl -server server1 -template templatename

 

Problem: UnexpectedFailureException is thrown during process initializaiton

This problem can occur from one of the following possible causes:

• Wrong security settings in the process EAR.
• Wrong verb settings or verb JNDI specification for the staff activity in the process model.

Solution: After checking and correcting these settings, force an update of the staff resolution by executing the following command:

  refreshStaffQuery.jacl -server server1 -template templatename

 

Exception: UserID must be less than 12 characters long

This problem can occur when the J2C authentication alias specified contains more than 11 characters. If this is because it has been specified with its full DN, setting a filter and using the shortname should solve the problem.

Solution: Check and eventually correct all settings.

 

See also

• Business process integration scenario
• Integrating business processes
• installation scenarios
• Configure the business process container for portal
• Defining the task page
• WebSphere Business Integration Server Foundation Information Center

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.