Win a copy of Practice Tests for OCP Java 17 Certification Exam (1Z0-829) this week in the OCPJP forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Tim Cooke
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Rob Spoor
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Scott Selikoff
  • Piet Souris
  • Jj Roberts
  • fred rosenberger

Portal Server Administration Problem

Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Under Portal Administration, I created some pages(only page definations), in between my partner deployed new skins & themes over the server. After that I continued ((i re-logged in to portal server as my peer was deploying stuff into server)) with custom unique names and assigned protlets and themes & skins to newly created pages. But I forgot to give resource permission to portlets.

After everything completed(apart from resource permissions), I ran my application but it didnt worked due to some reason.

I tried to enter portal administration but did not able to make it. My admin page stopped responding and now i am not able to get into portal administration.

What is the reason?? Is it the reason that after page defination my partner deployed skins and themes or is there any other reason. Or is it forgetting to assign resource permission to portlets?

Gaurav Sharma
author and cow tipper
Posts: 5006
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If you didn't change a theme, there shouldn't be a problem. Maybe someone edited the default theme, and took away the link to render administrative links or something.

For WebSphere, if major problems happen, you can always rerun the xmlaccess tool with the initial install options. That'll take the portal back to the initial configuration. Of course, that doesn't help if the actual files for a skin or theme, physically sitting on the hard drive, have been messed around with. But it would sorta restore any configuration issues.

On a sandbox server, or your own dev environment, this might be an option. Definitely not something you want to do on a prod or pre-prod server though.

Good luck!

-Cameron McKenzie
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic