VERIFIED SOLUTION i

Resolve issue where the createEJBStubs script appears in the server/websphere directory for EngageOne

Product Feature: Installation / Upgrade

Operating System: All

Database: All

Configuration: WebSphere
 

Issue

At the end of an EngageOne installation in a WebSphere environment, non-fatal errors are reported and a script called createEJBStubs is created in the server/websphere directory of the EngageOne installation.
Further inspection of the EngageOne_Install.log show errors returned from the WebSphere createEJBStubs script.
 

Cause

The batch and purge processes in EngageOne in a WebSphere environment require additional classes to be injected into three of the libraries in order for these processes to communicate with the WebSphere instance. These classes are referred to as EJB stubs. The EngageOne installer calls the required script within WebSphere to inject these classes. If these classes are not present, then the batch and purge processes will fail with error messages referencing the failed EJB connection. The EJB jar files are:
server/lib/config-framework.jar
server/lib/eventmonitor-core.jar
server/batch/lib/tds.jar
 

Resolution

UPDATED: August 3, 2017
If such errors are reported, the relevant jar files should be inspected using 7Zip for the following classes:
In server/lib/config-framework.jar:
com\pb\config\iface\ejb\_ConfigRemote_Stub.class
In server/lib/eventmonitor-core.jar:
com\pb\eventmonitor\iface\ejb\_EventMonitorRemote_Stub.class
In server/batch/lib/tds.jar:
com\pb\engageone\server\tds\api\ejb\_DeliveryRemote_Stub.class
com\pb\engageone\server\tds\api\ejb\_RepositoryPurgeRemote_Stub.class
com\pb\engageone\server\tds\api\ejb\_RepositoryRemote_Stub.class

If these classes are all present, then no further action is required.
If not, then rectify the error as reported in the EngageOne_Install.log and run the script in the server/websphere to inject the stubs.