Students who take the ATG Portal course often have serious problems tracking down and solving 404 errors in portal pages: as the portal works by dynamically including many JSP fragments, there may be multiple concurring causes for those errors and few of them have to do with an true typing mistake of an include tag. I use the following checklist to solve those problems:
-
look in the http://localhost:8840/nucleus/atg/dynamo/service/j2ee/J2EEContainer/ component to see if the portlet webapp is correctly started; if the portlet is not
there, edit its J2EEContainer.properties file and add it, like
applications+={atg.dynamo.root}/MyPortlets/j2ee-apps/myportlet_war - check the portlet.xml file for any typos in the JSP mode mappings, re-run the portletDeployTool script and redeploy the portlet
- check the dynamoJ2EESpecifier.xml file to see if there is a web-application-mapping for the portlet webapp, if not then add it
- check the web.xml and the dynamoJ2EESpecifier.xml file again to see if all the taglibs have the correct definitions