Migration Issues and Resolutions

Below are the list of issues and resolutions that we came across during WPS 7.0.0.4 to BPM 8.5.0.1
migration.

Issue 1:
com.ibm.websphere.sca.ServiceRuntimeException: java.lang.IllegalArgumentException: The specified url
cannot be null: caused by: java.lang.IllegalArgumentException: The specified url cannot be null.
Caused by: java.lang.IllegalArgumentException: The specified url cannot be null.at
com.ibm.ws.al.ArtifactHelper.getArtifactInfo (ArtifactHelper.java:186)at
com.ibm.ws.sca.internal.jaxws.deployment.resource.WSResourceLocator.loadArtifactInfo(WSResourceL
ocator.java:135)

Resolution:
Verify EAR is building properly and all the dependent resources (JAR and WAR files) with in the EAR are
available. If not present, clean and rebuild the EAR and deploy.

Issue 2:
Customers using BPM 8.5.0.1 will have two issue related to indexing. One is Artifact Index and other is
Task Index which will create issues and server will become un-responsive because of "Too many open
files" and server creates to many locks and not sharing the index.

Resolution:
Issue can be resolved by applying below ifix :

JR50794 ( fix for Task Index) Which requires the prerequisite ifix as well
APAR JR49040 is required by 8.5.0.1-WS-BPM-IFJR50794.
APAR JR50335 is required by 8.5.0.1-WS-BPM-IFJR50794.
APAR JR47860 is required by 8.5.0.1-WS-BPM-IFJR49509.
JR51223 (fix for Artifact Index lock issue).

If the customer migrates directly to 8.5.5 then the above ifix are included in that. Also they need to
monitor that bpm.lock open files don't keep increasing.

Issue 3:
Changes in the Bus names in BPM 8.5 can lead to ContextStore destinations not being created correctly
at deploy time. This will lead to seeing the following in the logs when module is run:
WSIT0019E: No suitable messaging engine is available on bus PM.<cellname>.Bus that matched the
specified connection

Resolution:
Issue can be resolved by applying below ifix :

iFix 8.5.0.1-WS-BPM-IFIT00409

Issue 4:
Some warning messages are seen during the migration of Mediation artifacts which includes Fan In/Fan
Out primitive.

Resolution:
PMR is still open for this issue.

Issue 5:
During the migration of XSLT maps which includes Merge transform , it is automatically

changes to JOIN transform and map fails to work as expected.

Resolution:
Issue is not yet resolved.