tag:blogger.com,1999:blog-5874979429188093780.post1238437521705961896..comments2024-03-18T06:46:54.352+01:00Comments on Andrej Baranovskij Blog: Running Oracle BPM 11g PS5 Worklist Task Flow and Human Task Form on Non-SOA DomainAndrej Baranovskijhttp://www.blogger.com/profile/04468230464412457426noreply@blogger.comBlogger42125tag:blogger.com,1999:blog-5874979429188093780.post-42066044549563812142016-10-31T07:43:33.290+01:002016-10-31T07:43:33.290+01:00Hi Andrejus,
Great post as usual. We successfully...Hi Andrejus,<br /><br />Great post as usual. We successfully created custom BPM worklist client in ADF using BPM Java API. I see there is a confusion between foreign JNDI server vs wf_client_config.xml file among many developers. Would like to clarify on this. <br /><br />Foreign JNDI - When your ADF app wants to show tasks from only 1 BPM instance - go for this.<br />wf_client_config - Lets say you have multiple BPM servers and you want to display tasks from all those servers, go for this configuration. Here you can specify multiple URLs. One more thing - go for REMOTE EJB. SOAP endpoint is meant to be used for internal purpose only (as per Oracle). Also, remember to set federatedMode = true.<br /><br />Thanks,<br />SaiAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-29938268681618617212015-04-24T13:25:46.380+02:002015-04-24T13:25:46.380+02:00Hey Andrejus this a noob developer
I did everythi...Hey Andrejus this a noob developer<br /><br />I did everything which is mentioned above but some how I am getting blank screen on running<br /><br />http://localhost:7101/custombpm/faces/main.jspx<br /><br />can u please suggest something<br /><br />Thanks Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-38071451225226265602015-03-17T20:34:15.699+01:002015-03-17T20:34:15.699+01:00If you are going to host only ADF Human Task Flows...If you are going to host only ADF Human Task Flows, yes - it makes more sense to have one domain with separate managed servers. I agree with you.<br /><br />Regards,<br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-4780624416023903532015-03-17T19:55:38.466+01:002015-03-17T19:55:38.466+01:00That may allow the (adf) domain to start more quic...That may allow the (adf) domain to start more quickly, but in the case of simply hosting human task UIs, what's the point? The ADF views are not usable without the process and the reverse is also true in this case.<br /><br />Given that dependency, the efficient architecture choice would be to deploy the ADF managed server VMs collocated in the SOA domain to reduce complexity on the premise that you have to wait for the SOA domain to start up to be useful anyway.<br /><br />Also, other than in DEV environments, restarting the domains is not a frequent activity outside of planned maintenance periods anyway.<br /><br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-71355838489251674762015-03-12T08:07:50.961+01:002015-03-12T08:07:50.961+01:00Hi,
Running separate domains is mainly for optimi...Hi,<br /><br />Running separate domains is mainly for optimisation. Having ADF app on separate domain allows to restart domain quickier, BPM admin server requires more resources. From architecture point of view, is better to have them separate.<br /><br />Of course, technically it would work fine in one domain.<br /><br />Regards,<br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-78250211114779832192015-03-11T16:45:54.534+01:002015-03-11T16:45:54.534+01:00Hi Andrejus,
Curious: Why an entirely separate d...Hi Andrejus,<br /><br />Curious: Why an entirely separate domain? what is the benefit here over simply adding additional managed servers to the soa domain and even another machine or two to isolate the adf server JVM(s) to unique hardware if need be?<br /><br />Completely separate domains and MW_HOME binaries would allow for isolating patching concerns, but one might argue that these are fairly dedicated UI components sufficiently correlated functionally to preclude the need for separate maintenance/patch outages.<br /><br />Thoughts?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-47527058089178535412014-08-20T21:02:08.314+02:002014-08-20T21:02:08.314+02:00Perfect !Perfect !Andrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-23328358366977299492014-08-20T18:13:36.445+02:002014-08-20T18:13:36.445+02:00Finally got it working. Implemented this on an env...Finally got it working. Implemented this on an environment with multiple domains.. it was a little bit more complicated.<br /><br />Thanks for the blog post, it was very helpful and much more clearer than Oracle documentation for this topic. ;)<br /><br />Regards<br />OnkarAnonymoushttps://www.blogger.com/profile/18021274017688685225noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-68955391723332800382014-08-20T13:38:57.835+02:002014-08-20T13:38:57.835+02:00I didn't had such error in my environment. But...I didn't had such error in my environment. But you should check, may be Worklist task flow still works, even with this error.<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-77413704792791933872014-08-20T12:18:32.893+02:002014-08-20T12:18:32.893+02:00Thanks for the reply.
However, after I do all th...Thanks for the reply. <br /><br />However, after I do all this, i get the following error in logs when accessing the worklist app:<br /><br />Access to internal workflow context is denied.<br />Requested access to internal workflow context is not allowed according to security policy.<br />Ensure that correct security policy is used. If the error persists, contact Oracle Support Services.<br /><br /> at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.registerTaskFlowWithTask(TaskFlowDeployerThread.java:371)<br /> at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.run(TaskFlowDeployerThread.java:142)<br /> at java.lang.Thread.run(Thread.java:680)<br />Caused by: ORABPEL-30515<br /><br />Access to internal workflow context is denied.<br />Requested access to internal workflow context is not allowed according to security policy.<br />Ensure that correct security policy is used. If the error persists, contact Oracle Support Services.<br /><br /> at oracle.bpel.services.workflow.verification.impl.VerificationService.createTaskDisplayInternalWorkflowContext(VerificationService.java:1364)<br /> at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread$1.run(TaskFlowDeployerThread.java:406)<br /> at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.getInternalWorkflowContext(TaskFlowDeployerThread.java:399)<br /> at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.registerTaskFlowWithTask(TaskFlowDeployerThread.java:277)<br /> at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.run(TaskFlowDeployerThread.java:141)<br /> ... 1 more<br />Caused by: java.security.AccessControlException: access denied (oracle.security.jps.JpsPermission VerificationService.createInternalWorkflowContext)<br /> at java.security.AccessControlContext.checkPermission(AccessControlContext.java:376)<br /> at java.security.AccessController.checkPermission(AccessController.java:549)<br /> at oracle.security.jps.util.JpsAuth$AuthorizationMechanism$3.checkPermission(JpsAuth.java:463)<br /> at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:523)<br /> at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:549)<br /> at oracle.bpel.services.workflow.verification.impl.VerificationService.createTaskDisplayInternalWorkflowContext(VerificationService.java:1357)<br /> at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread$1.run(TaskFlowDeployerThread.java:408)<br /> at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.getInternalWorkflowContext(TaskFlowDeployerThread.java:399)<br /> at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.registerTaskFlowWithTask(TaskFlowDeployerThread.java:277)<br /> at oracle.bpel.services.workflow.client.worklist.servlet.TaskFlowDeployerThread.run(TaskFlowDeployerThread.java:142)<br /> ... 1 more<br /><br />Do you have any idea how to fix this?<br /><br />Thanks<br />OnkarAnonymoushttps://www.blogger.com/profile/18021274017688685225noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-769917123002844752014-08-20T10:56:27.666+02:002014-08-20T10:56:27.666+02:00I already telling it clear - on non soa-domain, th...I already telling it clear - on non soa-domain, the one where you want to run SOA task flows :)<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-86835818983498469552014-08-20T10:52:52.157+02:002014-08-20T10:52:52.157+02:00Hey,
Could you also make clear exactly which syst...Hey,<br /><br />Could you also make clear exactly which system-jaxz-data.xml needs the bpm-services security grants... the one on the non-soa domain or the one on the soa domain?<br /><br />Your blog suggests change should be made on non-soa but oracle documentation seems to suggest on soa domain. Not clear!<br /><br />Thanks<br />OnkarAnonymoushttps://www.blogger.com/profile/18021274017688685225noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-17997150864157876782014-08-01T12:49:03.283+02:002014-08-01T12:49:03.283+02:00Great it worked for you :)Great it worked for you :)Andrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-81085398689164435992014-08-01T11:43:10.295+02:002014-08-01T11:43:10.295+02:00Thanks a lot for another of your great posts! That...Thanks a lot for another of your great posts! That little trick of the custom Lib was so specific I would never get there...<br />Thanks againAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-7628294647688581022013-08-15T15:53:49.290+02:002013-08-15T15:53:49.290+02:00Anyway,thankyou!Anyway,thankyou!elektra james diohttps://www.blogger.com/profile/03189844839332492865noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-81703625020734065442013-08-15T15:52:01.844+02:002013-08-15T15:52:01.844+02:00I didnt faced this particular error while configur...I didnt faced this particular error while configuring, so hard to advice something useful at this time...<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-27459428473856749622013-08-15T15:48:49.030+02:002013-08-15T15:48:49.030+02:00The problem is that I could not find the "wor...The problem is that I could not find the "work-flow-config.xml" file.elektra james diohttps://www.blogger.com/profile/03189844839332492865noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-38706719589310533962013-08-15T15:44:34.459+02:002013-08-15T15:44:34.459+02:00Hard to say... Looks like SOA server config issue....Hard to say... Looks like SOA server config issue.<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-82526546569536892072013-08-15T15:18:34.981+02:002013-08-15T15:18:34.981+02:00Hi Andrejus ,
SOA server displayed an error: Defa...Hi Andrejus ,<br /><br />SOA server displayed an error: Default configuration is not defined in configuration "workflow-identity-cofig.xml.<br /><br />How should I proceed?<br /><br />Regard,elektra james diohttps://www.blogger.com/profile/03189844839332492865noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-79207004710789280012013-05-14T17:09:35.889+02:002013-05-14T17:09:35.889+02:00My post wasn't showing the tag, here a second ...My post wasn't showing the tag, here a second version:<br /><br /><br /> <session-descriptor><br /> <cookie-path> your_app_context_path</cookie-path><br /> </session-descriptor><br />Anonymoushttps://www.blogger.com/profile/13603771161260362522noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-50023998645841156342013-05-14T16:58:21.319+02:002013-05-14T16:58:21.319+02:00Thanks for sharing your findings !
AndrejusThanks for sharing your findings !<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-19508146018261557972013-05-14T16:35:06.912+02:002013-05-14T16:35:06.912+02:00Ok.
I had to change the deployment descriptor &qu...Ok.<br /><br />I had to change the deployment descriptor "WEB-INF/weblogic.xml" and add the tag: <br /><br /> <br /> your_app_context_path<br /> <br /><br />Another thing is that the "source" server of foreign JNDIs must have the same "Identity Provider" than your local development environment or else you should to use "wfCtxId" parameter from "taskList-task-flow-definition.xml" and make user authentication using through API to retrieve that token.<br /><br />The last resource is don't configure foreign JNDIs on your local development environment - you don't see the worklist but the rest of the application will work as expected.Anonymoushttps://www.blogger.com/profile/13603771161260362522noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-31631240901234913772013-05-14T07:08:35.913+02:002013-05-14T07:08:35.913+02:00Please let others now what configuration specifica...Please let others now what configuration specifically it was.<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-38792974399297697872013-05-13T20:15:45.829+02:002013-05-13T20:15:45.829+02:00Hi,
I've found the solution.
It was a config...Hi,<br /><br />I've found the solution.<br /><br />It was a configuration on weblogic.xml deployment descriptor.<br />Anonymoushttps://www.blogger.com/profile/13603771161260362522noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-59738396565791274302013-05-08T02:27:12.088+02:002013-05-08T02:27:12.088+02:00Hi,
I came across your post and was very useful.
...Hi,<br /><br />I came across your post and was very useful.<br /><br />Testing the example code, I keep getting the message "ADF_FACES-30108:The view state of the page has expired because of inactivity. Reload the page." and the user has to authenticated again, again and again.<br /><br />Do you have any idea what might be the problem?Anonymoushttps://www.blogger.com/profile/13603771161260362522noreply@blogger.com