Click Apply when you have finished making your changes. Click Add variable.

Using Approval Management 26-77 ADE_VIEW_ROOTfmwtoolsfmwtools_ homejdevelopersoamodulesoracle.soa.workflow_11.1.1 .

d. Select oracle.soa.workflow.jar.

e. Click Finish.

f. Confirm that the oracle.soa.workflow11.1.1,11.1.1 library has an Active State. 2. Define the foreign JNDI on the non-SOA WLS server. Do the following: a. Navigate to http:remote_hostname:remote_portconsole, where remote_hostname and remote_port are the host name and port for the remote non-SOA WLS server.

b. Navigate to Domain Structure Services Foreign JNDI Providers.

c. Click New.

d. Enter the name ForeignJNDIProvider-SOA.

e. Click OK.

f. Click the ForeignJNDIProvider-SOA link. g. Replace soa_hostname and soa_port with the host name and port for the SOA WLS server. h. Enter the following values: - Initial Context Factory: weblogic.jndi.WLInitialContextFactory - Provider URL: t3:soa_hostname:soa_portsoa-infra - User: weblogic - Password: weblogic

i. Click Save.

3. Define the JNDI links on non-SOA WLS server. Do the following: a. Navigate to http:remote_hostname:remote_portconsole, where remote_hostname and remote_port are the host name and port for the remote non-SOA WLS server.

b. Navigate to Domain Structure Services Foreign JNDI Providers.

c. Click ForeignJNDIProvider-SOA.

d. Select the Link tab, then click New.

e. Enter the following values: - Name: RuntimeConfigService - Local JNDI Name: RuntimeConfigService - Remote JNDI Name: RuntimeConfigService

f. Click OK.

g. Repeat steps a through f to enter the following values for Name, Local JNDI Name, and Remote JNDI name: - ejbbpelservicesworkflowTaskServiceBean - ejbbpelservicesworkflowTaskMetadataServiceBean Note: The Provider URL is referring to the soa-infra application, not the domain. Do not change soa-infra to soa. 26-78 Modeling and Implementation Guide for Oracle Business Process Management - TaskReportServiceBean - TaskEvidenceServiceBean - TaskQueryService - UserMetadataService 4. Change system-jazn-data.xml on the remote non-SOA WLS server to include the grant for bpm-services.jar, as shown in Example 26–8 . If you are deploying the ADF Task Flow for Human Task to the integrated WLS server, then you can locate the system-jazn-data.xml file in ADE_VIEW_ ROOTsystem11.1.1.1.32.53.26DefaultDomainconfigfmwconfig . Important: Be sure to replace ADE_VIEW_ROOT with the actual path.. For example, scratchskaneshiview_storageskaneshi_ d7b4fmwtoolsfmwtools_ homejdevelopersoamodulesoracle.soa.workflow_ 11.1.1bpm-services.jar . Example 26–8 bpm-services.jar Grant Code grant grantee codesource urlfile:ADE_VIEW_ROOTfmwtoolsfmwtools_ homejdevelopersoamodulesoracle.soa.workflow_11.1.1bpm-services.jarurl codesource grantee permissions permission classoracle.security.jps.JpsPermissionclass nameVerificationService.createInternalWorkflowContextname permission permission classoracle.security.jps.service.credstore.CredentialAccessPermissionclass namecredstoressp.credstore.BPM-CRYPTO.BPM-CRYPTOname actionsread,writeactions permission permission classoracle.security.jps.JpsPermissionclass nameIdentityAssertionname actionsactions permission permissions grant 5. Restart the remote non-SOA WLS server. 6. Deploy your application containing the human task detail UI to the remote non-SOA WLS server. 7. Return to step 5 in Section 26.5.5.1, How to Embed the Task Listing Region in an Application.

26.5.5.1.2 How to Use the Task Flow in the Federated Mode If you are using the task flow in

the federated mode, you must put wf_client_config.xml in the class path of the Note: Specify ejbbpelservicesworkflow for ejbbpelservicesworkflowTaskServiceBean and ejbbpelservicesworkflowTaskMetadataServiceBean only.