VERIFIED SOLUTION i

Error :"The following EJB could not be allocated: ConfigInterfaceEJB" during Batch execution in EngageOne

WebSphere Application Server version 7.x, 8.5.5

Issue

Batch fails with error message in the execution log:
The following EJB could not be allocated: ConfigInterfaceEJB"

Cause

This could occur due to missing configuration of CSIv2 inbound/outbound transport in case of EngageOne deployed over WebSphere.
 

Resolution

UPDATED: June 1, 2017
Follow these steps:

1) Select Security > Global security > RMI/IIOP > CSIv2 inbound communications
2) Select 'SSL-supported' from the Transport drop-down list and click Apply.

User-added image


3) Select  Security > Global security > RMI/IIOP > CSIv2 outbound communications  
4) Select 'SSL-supported' from theTransport drop-down list and click Apply.

User-added image