Do’s and Don’ts for BPEL Compliance in BizTalk

The following list contains pointers and best practices that will help ensure that your BizTalk solution is BPEL compliant.

• Do not use the Call Orchestration shape or the Start Orchestration shape.

• Do not use the Transform shape.

• Do not invoke methods on custom .NET components.

• Do not apply a timeout to a long-running transaction.

• Do not pass parameters to Orchestration.

• Do not pass parameters to Callable compensation handlers.

• Do not use the Suspend shape.

• Do not declare local variables, correlations, or messages in an inner scope.

• Do not use Relational operators with type ‘Char’.

• Do not perform any actions between a Send shape and a Receive shape that use the same outbound request-response port.

• Literal values must be one of the following types:

  • Boolean

  • Char

  • Byte

  • SByte

  • Int32

  • UInt32

  • Int64

  • UInt64

  • Single

  • Double

  • String

• Arithmetic operators are allowed only on operands of the following numeric types:

  • Byte

  • SByte

  • Int32

  • UInt32

  • Int64

  • UInt64

  • Single...