Connect EJB form - Completing the Service tab
Use the Service tab to identify the properties of the remote EJB service. Complete the Service tab first.
As you work with the form, the information on this tab is used to connect to the JNDI server and automatically complete fields on the Create and Remote tabs.
|Server name|| Select the JNDI server (instance of
Data-Admin-Connect-JNDIServer) that identifies the EJB
container with the bean you want to connect to. To connect to an EJB through its
local interface, select the JNDI server named
This field supports the Global
Resource Settings syntax (=
|Lookup name||Select a key to use to look up the EJB home object of the remote EJB in the JNDI server.|
|Java class||Enter the name of the EJB Home Interface class to use to create an instance of the EJB client stub. If the JNDI Server and Lookup Name values are valid, this value is automatically filled in.|
|Create method|| Optional. Enter the type-signature of the EJB Home Interface method that
creates an instance of the EJB client stub (for example:
Select how to initialize the EJB client stub:
|Java class||Enter the name of the EJB Remote Interface class that defines the remote methods that can be called on the EJB client stub instance. If the JNDI server and lookup names are valid, this value is filled in automatically.|
Enter the type-signature of the EJB Remote Interface method that is called
each time this connector is called. For example:
Select how to finalize the EJB client stub:
|Object handle property||Optional. Select a Single Value property for storing and/or recovering the serialized object handle of the EJB client stub instance. This field is not required if you select both the Create a new object every time option of the EJB Remote/Initialize Object field and the Remove object after method call option of the EJB Remote/Finalize Object field.|
Error handling and test
|Status value property||
Optional. Select a property for reporting the status of the remote service
request. You can use the standard property
@baseclass.pyStatusValue. The literal value
|Status message property||Optional. Select a property for providing more information about errors that occur when processing the remote service request. You can use the standard property @baseclass.pyStatusValue.|
|Invocation exception property||
Optional. Select a property of mode
|Error handler flow||Optional. Identify a flow rule that is to be started when this connector rule is started by a flow rule but fails. The default flow rule Work-.ConnectionProblem provides one approach for handling such problems. See Handling connector exceptions.|
|Test connectivity|| Click this button at any time after you have completed the information on this
tab to confirm that Pega Platform can connect to the JNDI server
identified and can validate the Home Interface and Remote Interface.
The Test connectivity button does not work if either the
The system presents test results in a separate window, identifying the parameters used in the test, the steps attempted, and the outcome of each step.
|Generate test client||
As a debugging aid, if your
is hosted on a
Java EE-platform (not Apache Tomcat) you can generate a stand-alone Java client
program that calls the EJB.
This produces a Java source file in the
|Simulations||Click to create a simulator for this connect rule.|