Updating producer handle deletes all remote portlet instances
Platform: WebLogic Portal (Oracle formerly BEA)
Version: 10.3.7 (may be in earlier version too)
Description: When producer handle is updated using Portal Admin Console (with or without checking the Re-register Producer), it deletes all the remote portlets associated with the handle. This has been reported and Oracle has created a bug for this issue.
Solution: There are various ways to avoid deleting the associated remote portlets, when trying to update the remote producer handle:
1. Update the remote producer handle directly in the portal database table by running the following query:
update PF_CONSUMER_REGISTRY set WSDL_URL = 'http://myNewProducer.com/webApp/producer?wsdl' where PRODUCER_ID = XXXX;
Warning: This seems pretty simple however involves touching the portal database directly, one small mistake and you can corrupt your portal database, so take extreme precaution! Don't forget to commit after you ran the query.
2. Get the patch for the bug from Oracle, here is the detail:
Bug 25227539 : Reregister of ProducerHandle deletes the existing portlets from DVT & PATconsole.
This requires a lot of work, but is safe and will fix the issue. After the patch is applied, producer handle can be updated using portal admin console without checking the re-register handle check box.
PS: If you are following any of the above solutions, please leave your comments.
Platform: WebLogic Portal (Oracle formerly BEA)
Version: 10.3.7 (may be in earlier version too)
Description: When producer handle is updated using Portal Admin Console (with or without checking the Re-register Producer), it deletes all the remote portlets associated with the handle. This has been reported and Oracle has created a bug for this issue.
Solution: There are various ways to avoid deleting the associated remote portlets, when trying to update the remote producer handle:
1. Update the remote producer handle directly in the portal database table by running the following query:
update PF_CONSUMER_REGISTRY set WSDL_URL = 'http://myNewProducer.com/webApp/producer?wsdl' where PRODUCER_ID = XXXX;
Warning: This seems pretty simple however involves touching the portal database directly, one small mistake and you can corrupt your portal database, so take extreme precaution! Don't forget to commit after you ran the query.
2. Get the patch for the bug from Oracle, here is the detail:
Bug 25227539 : Reregister of ProducerHandle deletes the existing portlets from DVT & PATconsole.
This requires a lot of work, but is safe and will fix the issue. After the patch is applied, producer handle can be updated using portal admin console without checking the re-register handle check box.
PS: If you are following any of the above solutions, please leave your comments.
No comments:
Post a Comment