Showing posts with label federated portal. Show all posts
Showing posts with label federated portal. Show all posts

Monday, April 1, 2013

Update the remote producer handle

How to update the remote producer handle?
There are multiple ways to update the remote producer handle, two of them are given here:
1. By accessing the Portal Admin Console
2. By updating the Portal database directly

Both of these methods has pros and cons.
Updating via path 1 is a standard procedure and lot of documentation can be found on the web and oracle technical documentation website. It may take lot of time to update the remote producer handles depending upon the network, firewall and number of handles itself, since every update attempted via console will try to connect to the incorrect url first and should return error as a result before one can update it.

However going via path 2 requires little courage and technical expertise. Make sure you have a database backup before you attempt this path.
Steps to update the remote producer handles directly through database:
- Find all the producer details that need to be updated
- Verify along the table pf_consumer_registry to see if you need to update the producers
- Find the PRODUCER_ID and WSDL_URL from pf_consumer_registry table
- Update the WSDL_URL for the PRODUCER_ID that needed to be updated.
- Commit the transaction and verify the same using portal admin console.

If things go wrong, feel free to restore the database.

Note: WebLogic Portal 10.3.2 & WebLogic Portal 10.3.4 has been used and tested while writing this post and they were successfully updated.

Sunday, November 22, 2009

Oracle Weblogic Simple Producer

Oracle Weblogic Simple Producer (Version 10.3)

Oracle Weblogic Simple producer is a light version of Oracle Weblogic Portal + Oracle Weblogic Federated resources. From here onwards simple producer will be used to indicate Oracle Weblogic Simple Producer. Remote portlets deployed on producer can be consumed by the consumer portal using WSRP protocol.

A simple producer can be created using the following steps:

Step 1: Create the simple producer domain
Step 2: Create the simple producer project
Step 3: Move the existing application to simple producer project or create new application as required.
Step 4: Generate simple producer portlets, books, pages etc.
Step 5: Deploy the simple producer application on simple producer domain
Step 6: Consume the simple producer portlets and you are done.

Following features are supported by Simple Producer:
- Page flow & struts portlets can be created and published as remote portlets
- URL Rewriting is supported

Following features are not supported by Simple Producer:

  • Java, JSP, HTML, Clipper or Iframe portlets are not supported
  • Registration of remote portlets are not supported
  • No portal administration is available for simple producer
  • No Backing file support is available for simple producer
  • No event support is available for simple producer and thus inter portlet communication is also not available.
  • Render dependency file is not supported by simple producer
  • Portal APIs are not supported by simple producer