Fix (APAR):  PQ93191

Status:  Fix

Release:  5.1.1

Operating System:  All

Supersedes Fixes:  

CMVC Defect:  PQ93191

Byte size of APAR:  4962

Date: 2004-11-29

Abstract:  When installing an enterprise application containing a BPEL process, the installation can fail with an assertion error.

Description/symptom of problem:  1) Symptom:
   --------

   When installing an enterprise application that contains business processes the installation of the processes
   can fail with an assertion error.
   The stack trace looks similar to the following:

   [8/23/04 17:23:08:336 CEST]  8404012 SystemOut     O -------------------------- Assertion Failure ----------------------------
   [8/23/04 17:23:08:336 CEST]  8404012 SystemOut     O 
   [8/23/04 17:23:08:336 CEST]  8404012 SystemOut     O Assertion violation !(bpelMyRole != null) in method >>	
	at com.ibm.bpe.deployment.bpel.importer.impl.PartnerLinkMapper.install(PartnerLinkMapper.java:141) <<
   [8/23/04 17:23:08:336 CEST]  8404012 SystemOut     O 
   [8/23/04 17:23:08:336 CEST]  8404012 SystemOut     O -------------------------------------------------------------------------
   [8/23/04 17:23:08:336 CEST]  8404012 TraceBPE      <  com.ibm.bpe.deployment.bpel.importer.impl.PartnerLinkMapper.install(PartnerLinkMapper.java:235) Exit
   [8/23/04 17:23:08:597 CEST]  8404012 TraceBPE      d  com.ibm.bpe.util.TraceLog.trace(TraceLog.java:82) The following exception was logged
                                 com.ibm.bpe.util.ProcessAssertionError: Assertion violation !(bpelMyRole != null) in method >>	
	at com.ibm.bpe.deployment.bpel.importer.impl.PartnerLinkMapper.install(PartnerLinkMapper.java:141) <<
	at com.ibm.bpe.util.Assert.assertion(Assert.java:79)
	at com.ibm.bpe.deployment.bpel.importer.impl.PartnerLinkMapper.install(PartnerLinkMapper.java:141)
	at com.ibm.bpe.deployment.bpel.importer.impl.ImporterImpl.install(ImporterImpl.java:181)
	at com.ibm.bpe.deployment.BPELDeployer.installBPEL(BPELDeployer.java:207)
	at com.ibm.bpe.admin.AdminService.installProcessComponent(AdminService.java:445)
	at com.ibm.bpe.processarchive.ProcessComponentInstallTask.performTask(ProcessComponentInstallTask.java:181)
	at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:215)
	at java.lang.Thread.run(Thread.java:567)


2) Problem:
   --------

   The cause of this problem is having a role on an partner link that is not associated with a concrete endpoint. When using
   WebSphere Studio Application Developer Integration Edition, it is possible to model a BPEL process that has these
   kind of partner links which will cause this asserition error.
   
   
3) Solution:
   ---------

   This interim fix makes it possible to install an enterprise application that contains business processes 
   with partner links that are not associated with concrete endpoints, as was possible in WebSphere Business Integration
   Server Foundation 5.1.

   With this fix it is possible to install an enterprise application containing BPEL processes which have 
   partner links which are not associated with concrete endpoints. 

NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
       The Update Installer can be downloaded from the following link:
       http://www-3.ibm.com/software/webservers/appserv/support/index.html

Directions to apply fix:  NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
       The Fix Installer can be downloaded from the following link:
       http://www-3.ibm.com/software/webservers/appserv/support/index.html

1) Create temporary "fix" directory to store the jar file:
             UNIX: /tmp/WebSphere/fix
          Windows: c:\temp\WebSphere\fix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix.

5) Restart WebSphere

6) The temp directory may be removed.

Directions to remove fix:  NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS
     ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be
          removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.


1) Shutdown WebSphere

2) Follow the instructions that are packaged with the Fix Installer on how to uninstall the Fix.

3) Restart WebSphere

Directions to re-apply fix:  1) Shutdown WebSphere

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere

Additional Information: