Gen 8.6 remote EJB execution with JBoss EAP 7.1 "Initial Factory Class"

Products

• Gen
• Gen - Run Time Distributed

Issue/Introduction

Gen 8.6 supports JBoss EAP 7.1.

When a Gen Web client is installed on one instance of an Application Server and the Gen EJB server is installed on a second of an Application Server the transaction routing in the commcfg.properties file needs to include the "{Initial Factory Class}" to enable the remote EJB to be loaded successfully.

Environment

Release: 8.6
Component: Gen Java EJBs
Application Server: JBoss EAP 7.1

Resolution

WildFly 10.1 (WildFly Core 2.0.10.Final) used to be supported by Gen 8.6 and uses the older org.jboss.naming.remote.client.InitialContextFactory  

JBoss EAP 7.1 (WildFly Core 3.0.10.Final-redhat-1) uses org.wildfly.naming.client.WildFlyInitialContextFactory.

NOTE: In the WildFly Core version 3.0.10 used by JBoss EAP 7.1 org.jboss.naming.remote.client.InitialContextFactory is deprecated so in the short term it will still work but should not be relied upon long term. If it is used the JBoss server.log will contain message: 
"INFO  [org.wildfly.naming] (com.ca.gen.smrt.ServletSession) WFNAM00025: org.jboss.naming.remote.client.InitialContextFactory is deprecated; new applications should use org.wildfly.naming.client.WildFlyInitialContextFactory instead" 

Additional Information

Working With Distributed Processing > Overriding Communications Support at Execution Time  - see section "CCF Comm Config Files" and file commcfg.properties.