IBM BS029ML - WebSphere Portal Server Self Help Manual page 180

– Some vi editors of UNIX systems cause problems when handling large files. This
depends on the implementation of the vi editor. For example, if you use a vi editor to
modify an XML script with more than 40.000 lines, parts of the file contents might get
truncated. Use a different editor to modify such large files.
– You have a problem with your HTTP communication setup, for example, your input is
relayed through a HTTP server that truncates it. In this case, you can check for
communication problems by specifying the -echo command-line parameter when you
call the XML configuration interface 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 "LDAP: error code 49 - Invalid Credentials".
If you try to connect to the portal with security and LDAP enabled, but if the LDAP server is
not available, the error message shown in Example 5-2 is returned in the XML response
file.
Example 5-2 LDAP error message
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.
Message "LDAP: error code 50 - Insufficient access".
This message is returned when the user does not have proper access to the users. The
admin account used to run the task should have at least read access to the LDAP tree.
Message"XMLC0142E: Unique name unique_name is already used in the portal".
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 5-3 shows an example XML export request snippet.
Example 5-3 XML export example
<content-node ...
<component uniquename="component_1"...
</component>
</content-node>
Cannot use the XML configuration interface if it is externalized in security.
If the virtual resource XML_ACCESS that represents access to the XML configuration
interface is put under the 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
166
IBM WebSphere Portal V6 Self Help Guide
<component uniquename"component_2"...
<component uniquename"component_3"...
. . . . .
</component>
</component>