Saturday, October 3, 2009

Steps to use OBIEE JSR168 Portlets in WebLogic Portal

Someone told me they were having trouble getting the OBIEE JSR 168 portlets to run in WLP. Since WebLogic Portal has excellent support for all published portal standards, I figured that the best thing to do is provide illustrated,  step-by-step instructions.

Deploy the JSR168 WAR to the WebLogic Server


Add the JSR168 WAR as a Shared Library to the Application Workspace


[caption id="attachment_268" align="aligncenter" width="438" caption="Figure 1: Add the JSR168 WAR as a shared library to the application Workspace Step 1"]Figure 1: Add the JSR168 WAR as a shared library to the application Workspace Step 1[/caption]

[caption id="attachment_269" align="aligncenter" width="438" caption="Figure 2: Add the JSR168 WAR as a shared library to the application Workspace Step 2"]Figure 2:  Add the JSR168 WAR as a shared library to the application Workspace Step 2[/caption]

[caption id="attachment_270" align="aligncenter" width="300" caption="Figure 3: Add the JSR168 WAR as a shared library to the application Workspace Step 3"]Figure 3:  Add the JSR168 WAR as a shared library to the application Workspace Step 3[/caption]

Add Shared Library To Portal Project


Figure 4: Add shared library to Portal project Step 1Figure 4: Add shared library to Portal project Step 1




[caption id="attachment_272" align="aligncenter" width="438" caption="Figure 5: Add shared library to Portal project Step 2"]Figure 5: Add shared library to Portal project Step 2[/caption]

[caption id="attachment_273" align="aligncenter" width="438" caption="Figure 6: Add shared library to Portal project Step 3"]Figure 6: Add shared library to Portal project Step 3[/caption]

[caption id="attachment_274" align="aligncenter" width="443" caption="Figure 7: Add shared library to Portal project Step 4"]Figure 7: Add shared library to Portal project Step 4[/caption]

[caption id="attachment_275" align="aligncenter" width="438" caption="Figure 8: : Add shared library to Portal project Step 5 (Check Allow newer versions unless need explicit version control)"]Figure 8: : Add shared library to Portal project Step 5 (Check Allow newer versions unless need explicit version control)[/caption]


Add Library Reference To Weblogic.Xml In The Portal WEB Project


<wls:library-ref>

<wls:library-name>sawjsr168portlets</wls:library-name>

</wls:library-ref>

Add <wls:specification-version> and <wls:exact-match> nodes if required.

Un-check Build Automatically, Clean The Workspace Without A Build And Exit Workshop


[caption id="attachment_276" align="aligncenter" width="448" caption="Figure 9: Uncheck Build Automatically; Clean The Workspace Without A Build And Exit Workshop Step 1"]Figure 9: Uncheck Build Automatically; Clean The Workspace Without A Build And Exit Workshop Step 1[/caption]

[caption id="attachment_277" align="aligncenter" width="443" caption="Figure 10: Uncheck Build Automatically; Clean The Workspace Without A Build And Exit Workshop Step 2"]Figure 10: Uncheck Build Automatically; Clean The Workspace Without A Build And Exit Workshop Step 2[/caption]

Restart workshop, build, deploy.

Log-in To Portal Admin Console


Go to Portal\Portal Management. The portlet will be listed for use on streaming portals.

[caption id="attachment_267" align="aligncenter" width="438" caption="Congradulations!"]Congradulations![/caption]

3 comments:

  1. Had to add a first step, which is to deploy the JSR 168 portlet. Never occurred to me that someone might expect it to work without being deployed, but then it is easy to forget to obvious, so glad it was pointed out to me.

    ReplyDelete
  2. After performing the above steps ,I have got the below error, suggest me how to resolve.




    Regards
    RaviBhuma

    ReplyDelete
  3. No error shown below. What error are you getting?

    ReplyDelete