JR43730: MODIFYING A BPEL PROCESS RESULTS IN THE SNAPSHOT OF A TOOLKIT DEPENDENCY TO BE MARKED AS CHANGED, WHICH IS INVALID.

Version 8.0 Refresh Pack 1 for the IBM Business Process Manager products
8.0.1: IBM Integration Designer V8.0 Refresh Pack 1 for Windows
8.0.1: IBM Integration Designer V8.0 Refresh Pack 1 for Linux

APAR status

• Closed as fixed if next.

Error description

• Repro steps,
  1. Import the customer provided Process app into a Process
  Center and import it into a workspace.
  2. Import customer provided PI into the same workspace. Make
  sure it is referencing a snapshot of ZABA Data 1 Main
  3. Open Assembly diagram. Drop a new BPEL process and use
  interface IAgentManagementService.
  4. Double click to create the process and add an Assign node.
  5. Save.
  6. Examine the toolkit, it will have the [Changed] flag.
  

Local fix

Problem summary

• Fix planned for next IID V8 release, targetting 4Q2012.
  
  USER AFFECTED:
  ==> User editing a BPEL that has dependent artifacts (WSDL/XSD)
  in a dependent toolkit
  
  PROBLEM SUMMARY:
  ==> When you modify a BPEL process then the snapshot of a
  toolkit dependency is marked as Changed. Since it is a snapshot
  this is an invalid state.
  
  PROBLEM DETAILED DESCRIPTION:
  ==> When the BPEL editor performs a save it actually saves all
  of the files twice. The first time it loads the files, EMF marks
  the files as dirty and then marks them as non-dirty after
  they've finished loading. However in some files being loaded,
  they load files they reference and these referenced files aren't
  marked as non-dirty afterwards. During the 2nd save it saves all
  the files marked as dirty.
  
  PROBLEM CONCLUSION:
  ==> My solution for this is to only save all the files once when
  the BPEL editor performs a save (the 1st save wasn't really
  necessary, it was used to get a timestamp of a file which I can
  get without saving all of the files in the resource set).
  

Problem conclusion

Temporary fix

• Provided to customer originating the issue resulting in this
  APAR. Available on demand. Contact IBM support.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R801 PSY

     UP