EBI Bug: Context Node in Collaboration Business Process Script

EBI Bug: Context Node in Collaboration Business Process Script

TAGS: 2.5 / EXTOL bug / EXTOL Business Integrator / EXTOL EBI / Business Process Script /


When using two transformations in the same we are expecting that we can take the Target Context from the 1st Transformation and use it as the Source Context in the 2nd Transformation.

This works except when the transformation is part of the Outbound Collaboration Template.

A. Set-up:

1. 1st Execute Transformation with Source_Context_Node_1 and Target_Context_Node_1.

2. 2nd Execute Transformation with Target_Context_Node_1 as Source Context.

This set-up works and the global variables from the 1st transformation are available in the 2nd transformation.

B. New Set-up:

Same set-up as above but business process script is part of the Outbound Collaboration Template. Following error occurred with env.var.Log_of_Message_Id:

This statement was aborted because it would have caused a duplicate key value in a unique or promary key contraint or unique index identifies by ‘LOG_OF_MESSAGE_PK"

EXTOL Log of Message ID error

C. Solution:

1. Use existing set-up from step #A

2. Create a task: Context Point - Set Value, between Execute Transformation 1 and Execute Transformation 2

2a. Context Point - Set Value with following Setttings:

  • Context Storage Node: Target_Context_1
  • Variable Name: env.var.Log_of_Message (constant)
  • Variable Value: *BLANK-SPACE* ’ ’

This will ensure the value from the 1st Execute Transformation will not be passed to the 2nd Execute Transformation.



Copyright 2012 @ www.seanhoppe.com


By: on

A free web counter provided by GoStats.