Support for Foreign JNDI Names

Human workflow services can be integrated with J2EE applications through web services and remote method invocation (RMI). To simplify the remote lookup of Enterprise JavaBeans in other managed servers and clusters or even other Oracle WebLogic Server domains, Oracle WebLogic Server includes foreign JNDI providers that are configured with the remote server's host and port to link Enterprise JavaBeans from that remote server into the local server's JNDI trees.

Workflow services expose the Enterprise JavaBeans listed in Table 34-3 that must all be linked through the foreign JNDI providers to provide full support for the task query service, ADF task flow for human task registration, and embedded worklist region use cases.

To provide support for foreign JNDI names:

Log in to Oracle WebLogic Remote Console Provider.
Go to Edit Tree > Services > Foreign JNDI Providers.

There is one caveat when linking remote Enterprise JavaBeans names to the local JNDI namespace through a foreign JNDI provider from a SOA server to a managed server or cluster in the same Oracle WebLogic Server domain. The local JNDI names are exposed to all of the managed servers within that domain. This causes namespace collisions on the SOA server within that domain, which already has those Enterprise JavaBeans registered from the Oracle BPM Worklist. An alternative, which avoids collisions while keeping configuration to a minimum, is to use JNDI suffixing. This is done by appending a consistent suffix to the end of all the local JNDI links of the remote workflow Enterprise JavaBeans and creating a simple wf_client_config.xml file that contains the suffix key.

There are different ways to define client properties. For more information, see Configuration Option.
Append the JNDI suffix to each Enterprise JavaBeans name shown in Table 34-3 to register the foreign JNDI names.
- ejb/bpel/services/workflow/TaskServiceGlobalTransactionean_server1
- ejb/bpel/services/workflow/TaskServiceBean_server1
- ejb/bpel/services/workflow/TaskMetadataServiceBean_server1
- TaskQueryService_server1
- UserMetadataService_server1
- RuntimeConfigService_server1
- TaskReportServiceBean_server1
- TaskEvidenceServiceBean_server1
Define the remote name by specifying only the ejbJndiSuffix element value in the wf_client_config.xml file, as shown in the code sample below. You can also use the JAXB WorkflowServicesClientConfigurationType object or the CONNECTION_PROPERTY.EJB_JNDI_SUFFIX in the Map<CONNECTION_PROPERTY, String> properties.
```
<remoteClient>
      <ejbJndiSuffix>_server1</ejbJndiSuffix>
</remoteClient>
```