IBM Support

Error 404 when trying to render the Login page

Troubleshooting


Problem

An error 404 is thrown when you try to render the Login page from WebSphere Portal 6.1

Diagnosing The Problem

The SystemOut.log reports the following error:

[5/20/09 9:04:21:387 BRT] 0000003d Servlet       E com.ibm.wps.engine.Servlet handleException EJPEJ0069E: URL parsing problem, URL= http://hostname:port/wps/portal

Resolving The Problem

This error can happen when both Login and Edit My Profile pages have been inactivated.
In order to see if this is the case, export both pages using xmlaccess:


1. Create a file called ExportPages.xml with the following content:

<?xml version="1.0" encoding="UTF-8"?>

<request
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="PortalConfig_1.4.xsd"
    type="export">

    <portal action="locate">
   
        <content-node action="export" uniquename="wps.Login"/>
        <content-node action="export" uniquename="wps.Selfcare"/>

    </portal>
</request>

2. Copy the just created file, ExportPages.xml, to the <PortalServer>/bin directory.
3. Export both pages using the following command:

<PortalServer>/bin/xmlaccess.bat(sh) –in ExportPages.xml –url http://hostname:port/wps/config -user <portal_admin_id> -pwd <portal_admin_password> -out Login_Selfcare.xml

Note: Replace the hostname:port with the correct value for your Portal URL. Both options –user and –pwd must contain the correct values for the Portal Administrator user and password, respectively.

The xmlaccess command above will create a file called Login_Selfcare.xml under <PortalServer>/bin directory.
4. Edit the Login_Selfcare.xml file and search for the following lines:

<content-node action="update" active="false" allportletsallowed="true" content-parentref="6_000000000000000000000000A0" create-type="explicit" domain="rel" objectid="6_CGAH47L008DF802B56IQ0D00M6" ordinal="350" themeref="J_61LA1AG098QD10IGQINU0A3000" type="page" uniquename="wps.Login">


<content-node action="update" active="false" allportletsallowed="true" content-parentref="6_000000000000000000000000A0" create-type="explicit" domain="rel" objectid="6_CGAH47L008DF802B56IQ0D00E2" ordinal="1400" type="page" uniquename="wps.Selfcare">

The tags active="false" indicates the pages are not active.

It is important to notice that in this particular case, the Login page should not be inactivated. If this is your case, activate the page using xmlaccess:

1. Edit Login_Selfcare.xml file and replace the tag active="false" to active="true" for the 2 lines above, or at least for the Login page, which is the line that indicates uniquename="wps.Login".
2. Save and close the file
3. Import the XML file using xmlaccess command:

<PortalServer>/bin/xmlaccess.bat(sh) –in Login_Selfcare.xml –url http://hostname:port/wps/config -user <portal_admin_id> -pwd <portal_admin_password>

Note: Replace the hostname:port with the correct value for your Portal URL. Both options –user and –pwd must contain the correct values for the Portal Administrator user and password, respectively.

It is now possible to render the login page using Portal URLs:
http://hostname:port/wps/portal
http://hostname:port/wps/myportal

[{"Product":{"code":"SS8KYD","label":"WebSphere Portal End of Support Products"},"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.1.0.2;6.1.0.1;6.1","Edition":"Enable;Extend;Server;Express","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 June 2018

UID

swg21386605