The BP Server requires the initial context factory name, URL, principal and credential of the application server to communicate to the EJB. You can provide these properties in oebpsjndi.properties file using any name for the application server. Use this name in the performer string as <server-id>.
Example of <server-id>:
For the performer of format jndi://<server-id>/<jndi name of EJB >:<method name>, you need to specify the following entries in oebpsjndi.properties file, located in OEBPS_HOME\conf folder.
oebps.<server-id>.factory.initial=<fully qualified class name of initial context factory>
oebps.<server-id>.provider.url=<jndi url>
oebps.<server-id>.principal=<username>
oebps.<server-id>.credentials=<password>
You can also provide an alias-name in the oebpsjndi.properties file for the application server name used to describe the properties, and then use this alias name in the performer string as <alias-name>. The alias-name hides the details of the context factory, URL, principal and credential from the performer string and thus isolates the process definition from communication channel.
Example of <alias-name>
For the performer of format jndi://$<alias-name>/<jndi name of EJB>:<method name>, you need to specify the following entries in oebpsjndi.properties file:
oebps.myappserver.factory.initial =<fully qualified class name of initial context factory>
oebps.myappserver.provider.url=<jndi url>
oebps.myappserver.principal=<username>
oebps.myappserver.credentials=<password>
<alias-name>=myappserver
BP Server also provides an additional facility to connect to the EJBs that are deployed on the same application server instance on which the BP Server is running. For this purpose, the server-name/alias-name is predefined as DEFAULT and the format of performer string is as follows:
