One of those items I always have to go look up the specifics for is creating the MANIFEST.MF file for WebLogic shared libraries.
Reference URL can be found here.

One of those things I ran across recently that I always forget between projects so I thought I would share here:

1 Set the Oracle Home

export ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/

2 SQL Plus – Idle Instance $ORACLE_HOME/bin/sqlplus /nolog

3 Connect as SYS User

connect sys/welcome1@xe as sysdba;

4 Create the WEBLOGIC_PORTAL

User CREATE USER WEBLOGIC_PORTAL IDENTIFIED BY WEBLOGIC1;

5 Grant Roles and Permissions

GRANT CONNECT, RESOURCE,DBA TO WEBLOGIC_PORTAL;

6 The WLS install seems to expect a table named SYSTABLES, so you will need to create it:

CREATE TABLE SYSTABLES (TEMP NUMBER);

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

Figure 1: Add the JSR168 WAR as a shared library to the application Workspace Step 1

Figure 2: Add the JSR168 WAR as a shared library to the application Workspace Step 2

Figure 3: Add the JSR168 WAR as a shared library to the application Workspace Step 3

Add Shared Library To Portal Project

Figure 4: Add shared library to Portal project Step 1

Figure 5: Add shared library to Portal project Step 2

Figure 6: Add shared library to Portal project Step 3

Figure 7: Add shared library to Portal project Step 4

Figure 8: : Add shared library to Portal project Step 5 (Check Allow newer versions unless need explicit version control)

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

Figure 9: Uncheck Build Automatically; Clean The Workspace Without A Build And Exit Workshop Step 1

Figure 10: Uncheck Build Automatically; Clean The Workspace Without A Build And Exit Workshop Step 2

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.

Congradulations!

A clip from the release notes:

Large Applications May Require Additional Memory Allocation If you are building and testing a large application, WebLogic Workshop may run out of memory, which can cause it to run slowly or shut down. Workaround: You can increase your memory allocation by modifying the Workshop.cfg file, located in the BEA_HOME\weblogic81\workshop\ directory. Add this flag to the command-line arguments: VM flag -Xmx512m