Direct link to fix
APAR status
Closed as program error.
Error description
In the web IBM Process Designer, when you convert a heritage integration service that contains a Java integration step the conversion completes but shows the following message: "The following converted service flows have unsupported artifacts that are converted into placeholder service tasks. Test and edit the service flows in the web Process Designer to ensure they work correctly." When you open the converted service flow, you notice the Java integration step is annotated with the following text: "An error occurred while trying to convert the 'Call SOAP w/Auth' Java Integration component. See SystemOut.log for details." In the SystemOut.log file, you see that a java.lang.IndexOutOfBoundsException error is logged. You might also notice one or all of the issues after the conversion: - There are two or more newly created external services that are named similar (such as with a number appended to the name) and each of the external services wrap the same Java class. - At the service activity that has the converted Java integration, the operation binding is lost. - At the service activity that has the converted Java integration, the parameter mapping is lost. For reference, this is the stack trace of the java.lang.IndexOutOfBoundsException: [7/30/19 9:26:57:132 CEST] 00000171 TWProcessItem W com.ibm.bpm.tools.repo.client.transform.twprocess.TWProcessItemS rvConvVisitorImpl visit Error converting Java Connector in Service Flow: Index: 6, Size: 6 java.lang.IndexOutOfBoundsException: Index: 6, Size: 6 at java.util.ArrayList.rangeCheck(ArrayList.java:668) at java.util.ArrayList.get(ArrayList.java:444) at com.ibm.bpm.tools.repo.client.transform.twprocess.TWProcessItemS rvConvVisitorImpl.visit(TWProcessItemSrvConvVisitorImpl.java:790 ) at com.ibm.bpm.tools.repo.client.transform.twprocess.TWProcessWalke r.walk(TWProcessWalker.java:96) at com.ibm.bpm.tools.repo.client.transform.TWProcessTransformer.tra nsformToDomainObjectInTransformationContext(TWProcessTransformer .java:382) at com.ibm.bpmsdk.tools.repo.client.RepositoryAccessHelper.convertS erviceCommon(RepositoryAccessHelper.java:3860) at com.ibm.bpmsdk.tools.repo.client.RepositoryAccessHelper.convertS ervice(RepositoryAccessHelper.java:3768) at com.ibm.bpmsdk.model.repository.facade.RepositoryAccessFactory.c onvertService(RepositoryAccessFactory.java:710) at com.ibm.bpmsdk.rest.pub.conversion.ConversionResource.convertSer vice(ConversionResource.java:886) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.java:90) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:508) PRODUCTS AFFECTED IBM Business Automation Workflow IBM Business Process Manager (BPM) Advanced IBM BPM Standard IBM BPM Express
Local fix
Before you convert the services, ensure that you have a backup (snapshot) that you can view in the desktop Process Designer. After the services are converted, go through each of the services and each of the activities that has an error annotation, choose the intended method, re-enter the data mapping from the values in the backup in the desktop Process Designer, change the color of the activity to gray, and remove the error annotation from the diagram.
Problem summary
During a service conversion, the Java integration step is replaced by a new external service with Java binding and a service task bound to the external service. The operation and parameter mappings of the service task are based on the newly created external service. The assignment might fail if the Java class has two methods with the same name but only the method parameters are different. PRODUCTS AFFECTED IBM Business Automation Workflow IBM Business Process Manager (BPM) Advanced IBM BPM Standard IBM BPM Express
Problem conclusion
A fix that corrects the algorithm used during service conversion will be available in a future release of Business Automation Workflow.
Temporary fix
Comments
APAR Information
APAR number
JR61320
Reported component name
BUS AUTO WORKFL
Reported component ID
5737H4100
Reported release
I00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-07-30
Closed date
2020-09-09
Last modified date
2020-09-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BUS AUTO WORKFL
Fixed component ID
5737H4100
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18.0.0.0"}]
Document Information
Modified date:
10 September 2020