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 config path.

Once Communications Express configuration is completed, the following configuration directories are created in your system:

• uwc-deployed-path/WEB-INF/config

• uwc-deployed-path/staging/WEB-INF/config

• uwc-basedir/SUNWuwc/WEB-INF/config

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 configurator 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 defaut this option is enabled.

UWC applications startup failed and web container logs shows exceptions.

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

Work around.

• Make sure you have completed all the post configuration steps. For the post configuration steps, refer to the Post Configuration Instructions in Chapter 1, Overview of Communications Express

• Make sure you have specified correct values to all the configuration questions asked by the configuration wizard.

• Check whether the web container user and group specified in the configuration wizard are correct.

The “chown” commands have failed during configuration.

Work around.

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.

Work around.

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

Although the directory manager credentials may 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 Communication Express depends on to function properly.

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

The configurator does not support modification of web-container configuration for Access Manager SDK integration.

Work around.

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

Messaging SSO is not supported in SSL.

Work around

To support Messaging SSO with SSL perform the following steps:

How to enable Messaging SSO with SSL

Steps

1. Configure Web Server in SSL mode.

2. Configure Communications Express for SSL port of Web Server.

3. Set uwcauth.ssl.enabled=true.

4. Set uwcauth.https.port to SSL port of Web Server.

5. Enable Messaging Server in SSL mode.

6. Set the webmail.port in uwcconfig.properties to SSL port of Messaging Server.

7. Provide messagingsso.ims.url to Non SSL port of Messaging Server

8. Install the Certificate Management Server root Certificate Authority (CMS root CA) on both Web Server and Messaging Server.

9. Restart Web Server.

10. Provide a value to local.webmail.sso.ims.verifyurl pointing to Non SSL port of Messaging Server.

11. Restart Messaging Server.