EJB invoker is designed to invoke the method of Enterprise Java Bean. EJB invoker is a special
POJO invoker. So the rules of POJO invoker also applies to EJB invoker.
EJB invoker calls the EJB by jNDIName, which is the traditional way
for calling EJB 2.0, and calling EJB 3.0 by jIDName is also supported.
Following is a code example:
<EJB id="logoninvoker" jNDIName="ejb/ejbs/EJBProvierHome"
beanName=" com.ibm.btt.samples.html.business.SignIn "
method="execute" >
<parameters>
<parameter id="userId" type="java.lang.String"/>
<parameter id="password" type="java.lang.String"/>
</parameters>
</invoker>
where beanName and method stand
for the EJB's class and method.
EJB invoker has the following optional properties:
- jNDI: This property is mandatory. It specifies
the JNDI name of the EJB.
- eJBHome: This value is optional. If it is not
specified, the default value is beanName plus Home.
- initialContext and eJBLocation:
These two properties are optional. If they are not specified, the WebSphere® default initialContext
factory and EJB location will be used. In WebSphere Application Server, the EJB location
and EJB factory are not required if they are not in one WAS instance
application. The EJB location and EJB factory are needed when they
are used across different WAS applications and each WAS application
might have different configuration.