In the Oracle 10.1.3.3.x BPEL server there is an issue with tasks disappearing from everyone's task list after the server has been switched to use OID as the security provider.
The issue is that along with user ID's, the worklist application maintains the user's identity context in several of the workflow data base tables, including: WFTASK, WFTASKHISTORY, WFUSERPREFERENCE, WFUSERTASKVIEW, WFUSERTASKVIEWGRANT, WFUSERVACATION, and WFNOTIFICATIONSTATUS. The column in each of these tables is IDENTITYCONTEXT
Oracle is working an active bug for the issue where the migration scripts do not change the identity context columns, but until then you may want to think about manually updating the column values. This is not recommended by Oracle support, but was the only way I found to get existing tasks to show in user's task lists and task history again....
Friday, September 12, 2008
Wednesday, September 10, 2008
Switch OC4J from OID back to File Based Security
The switch from file based security to OID (or LDAP) based security is well documented by Oracle, but what if you ever need to switch back?
The obvious thing to do it do go into Enterprise Manager and change all of the providers back to "File Based Security". This will get you close, but not quite there.
The next thing you need to do is to roll back the changes to the jazn.xml files that were made for each container during the original switch to OID. Hopefully, you saved a copy of these! Don't forget to roll back jazn.xml for each container.
The last thing, if you are using BPEL, is to check the is_config.xml file for the BPEL container. This file is in $SOA_HOME/bpel/system/services/config. If you didn't save a copy of this file, there should be a clean one present in is_config.xml.BPM.
Finally, restart the application serrver and you should be back to file based security.
The obvious thing to do it do go into Enterprise Manager and change all of the providers back to "File Based Security". This will get you close, but not quite there.
The next thing you need to do is to roll back the changes to the jazn.xml files that were made for each container during the original switch to OID. Hopefully, you saved a copy of these! Don't forget to roll back jazn.xml for each container.
The last thing, if you are using BPEL, is to check the is_config.xml file for the BPEL container. This file is in $SOA_HOME/bpel/system/services/config. If you didn't save a copy of this file, there should be a clean one present in is_config.xml.BPM.
Finally, restart the application serrver and you should be back to file based security.
Subscribe to:
Posts (Atom)