This topic applies only to the IBM Business Process Manager Advanced configuration.

Invoking a synchronous subprocess in another EAR file fails

When a long-running process calls another process synchronously, and the subprocess is located in another enterprise archive (EAR) file, the subprocess invocation fails.

Example of the resulting exception:

com.ibm.ws.sca.internal.ejb.util.EJBStubAdapter com.ibm.ws.sca.internal.ejb.util.EJBStubAdapter#003 
Exception: 
java.rmi.AccessException: CORBA NO_PERMISSION 0x49424307 No; nested exception is: 
org.omg.CORBA.NO_PERMISSION: The WSCredential does not contain a forwardable token. 
Enable Identity Assertion for this scenario. 
vmcid: 0x49424000 minor code: 307 completed: No
at com.ibm.CORBA.iiop.UtilDelegateImpl.mapSystemException(UtilDelegateImpl.java:202)
at javax.rmi.CORBA.Util.mapSystemException(Util.java:84)

Reason

Because the subprocess invocation leads to a remote EJB method call, Common Secure Interoperability Version 2 (CSIv2) identity assertion must be enabled when calling a synchronous subprocess in another EAR file.

Resolution

Configure CSIv2 inbound authentication and CSIv2 outbound authentication.

For CSIv2 inbound authentication, see Configuring Common Secure Interoperability Version 2 inbound communications
For CSIv2 outbound authentication, see Configuring Common Secure Interoperability Version 2 outbound communications