Troubleshooting Business Process Service Development Errors

Problem: Development errors in a business process service.

Most errors in the business process service are caused by incorrect interaction with the data.

Solution: Use the following sequence when troubleshooting problems during the development of a business process service:

  1. Review all Assign activities in the business process logic to ensure that all input variables to invoked services are initialized prior to use and that all output interface variables are initialized prior to the Reply activity.
  2. Review all Assign activities to ensure the product of the assignment conforms to schema for the target variable.
  3. Assign activities in the business process service tooling do not validate that the product of the Assign conforms to the schema associated with that variable. If they do not conform to the schema, this type of problem can manifest itself as a failed service or produce a response message from the service in an incorrect format.
  4. Review the assignment operations and logical expressions to ensure they are valid. Changes to underlying services consumed by the business process service can cause errors. This is especially true if the interface of the consumed service is changed, causing Assign operations and logical expressions in the business process to become invalid.
  5. Review all logical expressions to ensure that they are valid and generate the expected result. Invalid logical expressions in the business process can result in unexpected results, infinite loops, or even business process errors.

Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com

Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.