This section contains a list of known issues in the Configurator tool for Communications Express.
The Communications Express Patch Configuration Program Prompts Users for the Webmail SSL Port Number Even if SSL is Not Enabled
When the patch-config program is executed on a Communications Express installation, it first checks if webmail is deployed. If it is deployed, the users are prompted to enter the SSL port number. Users can choose to install webmail with or without SSL. The patch-config program prompts the users to enter the SSL port number for webmail even if webmail is not enabled with SSL.
Workaround: If webmail is not configured in SSL mode, ignore this message by pressing the Enter key and proceed with the patch configuration.
Communications Express Does Not Allow Users to Log in After a Patch is Backed Out
Communications Express brings back the login page when users try to log on to Communications Express with valid credentials, after a patch is backed out. This issue is seen when users upgrade Communications Express by installing a patch using the patch-config and install-newconfig commands but later run the backout-newconfig to back out of a patch. The backout-newconfig utility does not warn users that some of the JSP files may have been cached by the web container.
Workaround: Remove the ClassCache directory for your web container and restart the web container on which Communications Express is deployed. The ClassCache directories for Web Server and Application Server are:
Web Server: /opt/SUNWwbsvr/https- <servername>/ClassCache/https- <servername>, where <servername> is the domain on which Communications Express is deployed.
Application Server: /var/opt/SUNWappserver/domains/domain1/generated/jsp/j2ee-modules/ <uwc_module_name>, where <uwc_module_name> is the name of the module deployed on the Application Server.
JSESSIONID Does Not Get Destroyed when Access Manager SSO is Configured With Communications Express
When Communications Express and Access Manager are installed on different machines, a user can view the calendar of a previously logged in user. This is because the JSESIONID cookie does not get destroyed.
Workaround: The following settings in the IS-SDK-BASEDIR/SUNWam/lib/AMConfig.properties file should be changed on the Access Manager machine that Communications Express runs on:
com.iplanet.am.session.client.polling.enable=false com.iplanet.am.notification.url= <url-to-access-web-container-of-CommunicationsExpress> /servlet/com.iplanet.services.comm.server.PLLRequestServlet
Configurator Tool for Communications Express Does Not Support the `Unconfigure' Option
The Communications Express Configurator does not allow you to undeploy, remove files at the time of configuration, and remove files created during runtime.
Workaround: To Unconfigure Communications Express:
Remove the Communications Express package. For example on Solaris type:
Remove the deploy directories.
Remove the WEBAPP entry from Web Server or Application Server server.xml file.
Silent Configuration Does Not Work.
Communications Express allows configuration to be executed only interactively, and does not allow silent configuration. When you try to configure in a silent mode, the following error is displayed, “The Directory name cannot be left blank. This is a mandatory field. Please enter again.”
Communications Express Configurator: devinstall Dumps Core for Unresolved Host Aliases
Communications Express configuration wizard fails to complete the configuration process if your system is not configured for host name aliases.
Workaround: Ensure that you have configured one or more host name aliases for your system.
To configure one or more host name aliases on UNIX systems:
Provide the configuration for the hosts in /etc/nsswitch.conf file:
hosts: files dns nis
This configuration indicates to the name service the lookup order it should use to resolve host names and host aliases. The name service lookup order is: files, dns, and nis.
Ensure that the /etc/hosts file contains two or more host names defined against your machine’s IP address.
For example, if your system IP address is 18.104.22.168, then in /etc/hosts file, you can configure the IP address as:
22.214.171.124 budgie.siroe.varrius.com budgie
126.96.36.199 budgie.siroe.varrius.com budgie loghost
Example of an incorrect IP address:
GUI Configuration Input Fields are Truncated because Input Fields are Right Aligned
The field names and browser buttons are truncated or not visible when the configuration wizard is invoked in a language other than English.
Workaround: Resize the configuration panels to view its contents properly.
The Components for Communications Express are Shown to be Zero Bytes
The configurator tool for Communications Express shows the component size as 0 bytes while displaying the Mail and Calendar components for Communications Express.
Java Exception on Web Server Startup after Configuration of Communications Express
In an installation scenario where Communications Express and Access Manager are installed and configured on separate nodes, the Web Server installed on the node containing Communications Express throws a Java exception on restart. This is due to the incorrect settings in the Web Server's classpath (on the node where Communications Express is installed).
Workaround: Edit the web-svr-base /config/server.xml file on the Web Server instance of the node where Communications Express is installed, and ensure that the following entries are available in the Web Server's classpath:
opt/SUNWam/lib:/opt/SUNWam/locale:/etc/opt/SUNWam/config: /opt/SUNWam/lib/am_sdk.jar:/opt/SUNWam/lib/am_services.jar: /opt/SUNWam/lib/am_logging.jar
Unable to Configure Communications Express on Linux due to Self Referencing Symbolic Links
The Communications Express configurator creates a self referencing symbolic link on Linux under the /var/opt/sun/uwc/staging directory.
Workaround: Remove all self referencing symbolic links from the /var/opt/sun/uwc/staging directory and redeploy Communications Express.
Communications Express Configurator Fails to Validate Application Server Port and as a Result the Configuration Hangs
The Communications Express configurator does not validate the Application Server port during configuration and thus the configuration hangs if a wrong Application Server port number is specified.
Configuration of Communications Express Hangs if Web Server is Running
The configuration of Communications Express hangs when the Web Server is running. This is due to an UnsatisfiedLinkError error.
Workaround: Gracefully shutdown the Web Server by executing the command /web-svr-base/web-svr-domain_name /stop. This will allow the Communications Express configuration to proceed.
Cannot Configure Communications Express in a Multiplexor Environment.
This problem occurs when Messaging Server is configured in a locale other than English. When users try to configure Communications Express using the configuration tool, on the Messaging Server panel when users provide the credentials, the configuration tool passes this on to the Messaging Server and waits for the response. If you configured Messaging Server in Japanese, on authenticating the user correctly, Messaging Server returns a string ja/mail.html to Communications Express. Communications Express on the other hand checks for the response and then proceeds further. However, there is a problem on the Communications Express configuration end which expects a string en/mail.html. Since the response received from Messaging Server is different from what the configuration wizard expects, the following error is displayed:
The Webmail Server credentials are wrong or Server misconfigured
Cannot Go Back in Command line Mode Configuration.
The configuration wizard for Communications Express provides a functionality for users to go back by typing the < symbol. This does not work as desired. As a result of this users cannot go to a previous page or screen by typing the < symbol.