Portlet not appearing in Admin Portal in 1/3 environments

Question

All Windows 2000 environments were recently patched from Platform 8.1SP1 to 8.1SP3 (via 8.1SP2). The procedures followed were virtually identical.
I've added a new JSP Portlet to my portal web application. It's a simple .portlet file pointing to a simple .jsp file.
I've added a new page to my portal. It's a simple page with only the new portlet in it.
I've redeployed the entire enterprise app enclosing the web app with these new items. I've also restarted all servers.
On my local machine (single server), this new page and portlet appear fine in my Portal Administration's Library. When I rebuild my desktop (replacing components), the new page and its portlet show up fine. When I execute my portal and navigate to the page, it shows up fine.
In our test lab (Admin server and a one node cluster), this new page and portlet appear fine in my Portal Administration's Library. When I rebuild my desktop (replacing components), the new page and its portlet show up fine. When I execute my portal and navigate to the page, it shows up fine.
On our staging server (Admin server and Managed Server, no cluster), the new page appears in the Library, but the new portlet does not. When I rebuild the desktop (replacing components), the new page appears but the new portlet does not. When I execute my portal and navigate to the page, it shows up but is empty.
The Admin portal gives no errors, nor can I find any in the server log.
Looking at the portal database in staging, the new portlet is NOT in the PF_PORTLET_DEFINITION table. I've enabled JDBC logging--no errors there.
Where can I look to determine why this environment is not loading the .portlet file appropriately?
Message was edited by tpierzina at Aug 19, 2004 9:38 AM

Answer 1

I had a similar problem in loading new pages / portlets into the admin console. It appears that if you have a conflict with definition labels / instance labels / even look and feel properties then the admin console fails quietly without error and does not load.
By conflict I mean properties such as the definition label / instance label / markup name (nything in the library list!) are already being used by the portlets in the library, so if you bring a new one in with the same name it will cause a conflict.
Try checking all the definition labels, instance labels, and markup names in look and feel and shells.
If you search for something like, 'console fails quietly when loading a portlet' you should get more info.
Hope this helps,
Alex