Select the Java class that will be created and invoked at runtime.
For details on setting up and designing a BPEL process with an EJB service, see
Creating a Java Interface
If you have developed a Web service implemented as an EJB, you can deploy the JAR files and other resources using the partner role invoke handler called EJB Service. Note that in the PDD Editor, the invoke handler detects your EJB project as a POJO and automatically selects Java Service. Be sure to select EJB Service.
Also note that an EJB Service cannot be used on Apache Tomcat. It is supported on other application servers.
The EJB Service handler performs a JNDI lookup to obtain the EJB home to instantiate the object used to call the method.
To fill in the EJB Service Invoke Handler Properties Dialog
For a JNDI Name, specify the JNDI name as defined in your application server's EJB file, such as the JBOSS ejb-jar.xml file, the WebLogic weblogic-ejb-jar.xml file, or the WebSphere ibm-ejb-jar-bnd.xml file.
For EJB Home, specify the home interface as defined in application server's ejb-jar.xml file.
This property is required for WebSphere, but is optional for JBoss and WebLogic.
In the Classpath box, select the Java classpath that is used when instantiating and invoking the Java class. The classpath includes not only the JAR (or local "src" workspace directory) that contains the class being invoked, but also any JARs that contain classes referenced directly or indirectly by that class.
Note that the Inherit server classloader checkbox is selected by default. If you disable this option, you will only have access to the JARs on your classpath, not the JARs that are deployed to the server.
When you select an EJB invoke handler for the partner role implementing the EJB interface, the Java resources are added to the resource catalog and deployed with the process. This includes all of the JARs included in the classpath.
Also, there is no endpoint reference information needed for an EJB service.