Troubleshooting the XML configuration interface

 

Troubleshooting

The following gives administrators information to assist them with preventing, identifying, and correcting possible problems that might occur when using the XML configuration interface.

 

Error response "Unknown schema or reference" when importing an XML file

Problem: The attempt to import an XML file results in an error response that contains the following message: 

     <message>com.ibm.wps.command.xml.XmlFormatException: XMLC0050E: 
        Input syntax error: the XML input does not conform to the XML schema</message>
     <message>org.xml.sax.SAXException: 
        Unknown schema or reference -//IBM//DTD Portal Configuration 1.1//EN  --  PortalConfig_1.1.dtd</message>

Suggested solution: Your XML file is in the format used by WebSphere Portal Portal 4.1 or 4.2. You need to convert your input file to the new format used by WebSphere Portal Version 5.0.2.

 

Unexpected syntax errors

Problem: Although the XML input file seems to be valid, inexplicable syntax errors are reported, for example unclosed XML tags.

Suggested solution: A possible reason is that your files are being truncated before they are processed by the portal. This can typically occur for two reasons:

  1. Your input file contains invalid UTF-8 characters. A good way to check your input files is to view them with Microsoft Internet Explorer. Microsoft Internet Explorer shows errors if your input contains invalid characters.
  2. You have a problem with your HTTP communication setup, for example, your input is relayed through a HTTP server that truncates it. You can check for communication problems by specifying the -echo command line parameter when you call the xmlaccess tool. When this parameter is specified, your request is not processed, but simply returned as it is read by the server. If the output is different from your input file, your request was modified somewhere along the communication path.

 

Message: "XMLC0091E: The servletref attribute is required to create a portlet clone . . ."

Problem: The attempt to deploy a portlet in a XML request results in the error message given above.

Suggested solution: There is a mismatch between the name, uid and refid attributes that are given in the XML request and those that were specified in the portlet.xml deployment descriptor for your portlet or portlet application. Therefore XML processing tries to create new portlets where it should only update those that have been created as part of the WAR file deployment. Use the Install portlet to deploy your WAR file, export the portlet application (package), and compare the export with your XML request, or compare your XML request with the portlet.xml. Make sure that the names and IDs for portlets and portlet applications are identical.

 

Message "XMLC0049E: Input syntax error ...", followed by "org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'request'."

Problem: The attempt to import an XML file results in the error messages given above.

Suggested solution: Your XML file contains an invalid schema or namespace declaration. Check the request element for typographical errors or missing attributes. The request must have the following form: 

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

 

Message "LDAP: error code 49 - Invalid Credentials" is misleading

Problem: If you try to connect to the portal with security and LDAP enabled, but if the LDAP server is not available, the following error message is returned in the XML response file: 

     
     com.ibm.websphere.wmm.exception.WMMSystemException: 
     The following Naming Exception occurred during processing: 
     "javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]".

This message can be misleading.

Solution: The LDAP error message Invalid Credentials means that the user name or password are wrong. It can also mean that the LDAP server is not available at all.

 

Importing a page with wires is unsuccessful

Problem: After a page containing wires between cooperative portlets is imported, the portlet actions and properties are registered, but the wires themselves are not created.

Solution: Run XMLAccess again to completely import the page. A simpler workaround is available if the portlets use WSDL to declare their actions and properties. See Known issues and restrictions with cooperative portlets for further information.

 

User data not exported as specified

Problem: User name data are not exported as specified by the user tag attributes firstname, lastname, or name. The reason is that the values of some attributes of the tag user correspond to settings in included parameter tags. If you include both in your export request, but specify different values for them, then the value set by the parameter tag overwrites the value set by the attribute, and is exported as the attribute.

Suggested solution: Use only one of the two ways to specify the user data, either the attribute or the parameter tag. For more information about this, see the description of the user tag under XML reference, Types of portal resources.

 

Message: "XMLC0142E: Unique name unique_name is already used in the portal."

Problem: One or more nested elements were not created properly.

Suggested solution: When you create a nested element, for example a component, with a uniquename attribute, the whole hierarchy upward from that element must also have uniquename attributes. Example XML export request snippet: 

     <content-node ...
          <component uniquename="component_1"...
               <component uniquename"component_2"...
                    <component uniquename"component_3"...
                         . . . . .
                    </component>
               </component>
          </component>      
     </content-node>

 

Cannot use the XML configuration interface if it is externalized in security

Problem: If the virtual resource XML_ACCESS that represents access to the XML configuration interface is put under protection of an external security manager, you can no longer use the XML configuration interface.

Solution: If the access rights of WebSphere Portal are externalized to an external security manager, such as Tivoli Access Manager, make sure that the XML configuration interface virtual resource is not externalized.

See also