Sun Java System Communications Express 6.3 Administration Guide

Configuring Communications Express

Configuration changes are not reflected, even after restarting the web container.

Make sure the configuration changes have been applied to the files in the appropriate configuration path.

The following directories are created once Communications Express configuration is completed:

To ensure that the changes are reflected in your application, make configuration changes to uwc-deployed-path/WEB-INF/config.

The other two directories such as uwc-deployed-path/ staging/WEB-INF/config and uwc-basedir /SUNWuwc/WEB-INF/config are temporary place holders created and used internally by the configuration wizard during configuration. Changes made in them will not get reflected in the application.

Configuration tasks have failed.

To locate the problem, use the log file located at uwc-basedir /SUNWuwc/install/uwc-config _TIME-STAMP.log

where, TIME-STAMP is the time stamp of the configuration in the form YYYYMMDDhhmmss.

Configuration program is not working properly.

To identify the problem, invoke the configuration program with debug options enabled, using the following debug modes:

-debug : Use this option to generate general debug information

-debugMessage : Use this option to generate a log of errors and warnings

-debugWarning : Use this option to generate a log of warning messages and error messages

-debugError : Use this option to generate a log of error messages. By default this option is enabled.

Communications Express applications startup failed and web container logs show exceptions.

This error might have occurred due to an incomplete or incorrect configuration.

Workaround.

The “chown” commands have failed during configuration.

Workaround.

Run the configuration program and enter the correct web container user and group values in the “Web Container User and Group” panel of the configuration program.

The message, “An error occurred during this operation” appears when you access Communications Express with Access Manager enabled after authentication.

Workaround.

Ensure that the uwcauth.identity.binddn and uwcauth.identity.bindcred properties in the uwc-deployed-path /WEB_INF/config/uwcauth.properties are set to that of the amAdmin DN which was provided when installing Access Manager SDK. Refer to the section on Configuring Access Manager Parameters in the uwcauth.properties File.

Although the directory manager credentials might be provided to uwcauth.identity.binddn and uwcauth.indentity.bindcred for Access Manager SSO, the directory manager does not have the ACLs required to obtain certain domain specific attributes that Communications Express depends on to function properly.

No support to modify web container configuration for Access Manager SDK integration.

The configuration wizard does not support modification of the web container configuration for Access Manager SDK integration.

Workaround.

Manually invoke tools provided with Access Manager to modify web container configuration for Access Manager.