EJB Connector Public Documentations

 

MuleSoft's EJB Connector helps you to establish communication between your Mule app and EJB. The connector gives you access to implement EJB business logic integration across Weblogic and Jboss/Wildfly servers for all versions. The EJB connection is established based on the creation of initial context.
This connector:
(a) Provides a powerful solution to implement any EJB2 or EJB3 business logic and pass custom payload with a wide range of datatypes to support any business operations
(b) EJB connector is used to retrieve data from EJB to the Mule application. EJB connector allows you to run diverse operations on your servers that includes various business logics.
(c) Enables to easily leverage custom fields and custom entities such as lookup bean name and method name and home interface name to solve integration needs to your customer.
(d) The connector enables integrating custom EJB Service packages. Based on the server type, a user is required to configure the server properties.

 

In this first release EJB Connector implements the following features for the MuleSoft-based enterprise solutions:

EJB Connection:

  • Configuration: Setting up the environmental properties for Weblogic/Jboss.

  • Host : specifies the URL of the WebLogic/Jboss Server that provides the name service. Example: t3://localhost:7001 where host is localhost and port in 7001.

  • Port : specifies the URL of the WebLogic/Jboss Server that provides the name service. Example: t3://localhost:7001 where host is localhost and port in 7001

  • Initial Context factory :

  • User Name : specifies the identity of the User i.e who will be accessing the JNDI tree, for authentication purposes.

  • Password : specifies the identity of the User i.e who will be accessing the JNDI tree, for authentication purposes.

EJB 2 Connection:

  • sessionCreateMethod: After creating an initial context lookup in the JNDI tree.

  • homeInterface:—Is used by an EJB client to gain access to the bean. Contains the bean life-cycle methods of create, find, or remove. The home interface is called the EJB home.

  • remoteInterface: Provide the value for remote home interface.

  • JNDI Name: Contains all of the actual bean business logic. Is the class that provides the business logic implementation.

  • methodName: Methods in this bean class associate to methods in the component and home interfaces.

  • arguments: Argument values to pass to the methodName.

EJB 3 Connection:

  • lookupBean: Contains all of the actual bean business logic. Is the class that provides the business logic implementation.

  • methodName: Methods in this bean class associate to methods in the component and home interfaces.

  • arguments: Argument values to pass to the methodName.

More and more features will be covered release by release.

Application/Service

Version

Application/Service

Version

Mule Runtime

4.X

Java

1.8 and later

Highlights of EJB Connector Mule 4

Automate common business operations by integrating EJB with other business applications such as ERP, analytics systems and so on. Possibilities include:

  • ERP integration - Give the business team access to all relevant customer data from one system via real-time synchronization of data between EJB, Salesforce, database and finance applications such as SAP and NetSuite.

  • Data Aggregation – Collect data from multiple EJB servers, CRM systems, ERP systems, and databases and use that information to generate reports.

  • Deliver a consistent, connected customer experience across channels, increase customer satisfaction, and drive revenue growth by integrating EJB connector to other applications such as Salesforce, SAP, and others.

Add this dependency to your application pom.xml

1 2 3 4 <groupId>com.plektonlabs.mulesoft.connectors</groupId> <artifactId>mule-ejb-connector</artifactId> <version>1.0.0</version> <classifier>mule-plugin</classifier>

 

 

Need inspiration?