h1. Completing the Sun Java System Communications Express 6.3 Installation: Initial Configuration
This chapter describes the configuration and migration steps you must perform, after installation, before you can use Communications Express.
This document includes the following sections:
{toc:minLevel=2|maxLevel=2}
h2. {anchor:GAXST} Before You Begin
Before you configure Communications Express, make sure you have the following dependent components installed and configured:
* Directory Server.
* Messaging Server and Calendar Server. Make sure you have recorded the relevant details about the installations, such as the hostname, port number, administrator username and password.
* Be sure you have run the Comm Directory Server set-up script, {{comm_dssetup.pl}}.
h2. {anchor:ABZBO} Communications Express File Directory Layout
After you install and configure Communications Express, the related files and directories are arranged in the organization as shown in [Table 2-1|#GAXUP]. The table is not exhaustive. It shows only the required directories and files for typical server administration tasks.
h6. {anchor:GAXUP} Table 2-1 Communications Express Directories and Files
||Directory and Legends||Default Location and Description||
|Communications Express Base\\
\\ {{uwc-basedir}}|Default location:\\
\\Solaris™: {{/opt/sun/comms/ce/}}\\
\\Linux: {{/opt/sun/comms/ce/}}\\
\\Communications Express is installed in this directory.\\
\\Note: On Solaris OS 10, the Communications Suite installer allows multi-installation of Communications Express; you can install multiple Communications Express base directories per machine. On Linux, only one Communications Express base directory is permitted.|
|Deployed Directory\\
\\ {{uwc-deployed-dir}}|Default location:\\
\\Solaris: {{/var/opt/comms/ce/}}\\
\\Linux: {{/var/opt/comms/ce/}}\\
\\Communications Express is deployed in this directory. The web container takes the files from this location while loading Communications Express.|
|Web Applications Root Directory\\
\\ {{WEB-INF}}|_uwc-deployed-dir_/{{WEB-INF}}\\
\\ {{WEB-INF}} directory of Communications Express web application|
|Webmail directory|{{uwc-deployed-dir/webmail}}\\
\\Contains all the webmail related files that Communications Express uses.|
|Configuration\\
\\ {{config}}|_uwc-deployed-dir_/{{WEB-INF/config/}}\\
\\Contains all the Communications Express configuration files|
|Domain\\
\\ {{domain}}|_uwc-deployed-dir_/{{WEB-INF/domain/}}\\
\\Contains per domain localization and Customization files|
|Skin\\
\\ {{skin}}|_uwc-deployed-dir_/{{WEB-INF/skin/}}\\
\\Contains per domain themes|
|Logs\\
\\ {{logs}}|_uwc-deployed-dir_/{{logs/}}\\
\\Contains the Communications Express log files. By default log messages are saved to the Web Server's error log file. You can change this location by setting the {{log.file}} configuration parameter in the {{uwcconfig.properties file}}.|
|System Administrator Programs\\
\\ {{sbin}}|_uwc-basedir_/{{sbin/}}\\
\\Contains the Communications Express system administrator executable programs and scripts|
|Help\\
\\ {{help}}|_uwc-deployed-dir_/{{help}}\\
\\Contains Communications Express help files|
h2. {anchor:ABZBH} Prerequisites for Configuring Communications Express
Before running the Communications Express configuration wizard, make sure you:
* Choose your schema. Refer to the section on [Schema Choices|#ABZBI] for information on the available schema.
* Ensure that you have the following entry in the {{/etc/hosts}} file on your Solaris system:\\
\\ _ip-of system_ _Fully-Qualified-Hostname_\\
\\For example,\\
\\ {{129.158.230.64 budgie.siroe.varrius.com budgie}}
* Ensure that the following components are up and running before you configure Communications Express. Make sure that the configuration of the products for Communications Express is done in the following order:
** Directory Server
** Application Server or Web Server
** Access Manager, if Communications Express wants to participate in SSO (Single Sign On) with other products (For example, Portal Server).
{info:title=Note}
The Web Server that is hosting Communications Express should be running as {{root}} when configuring for Remote AM SDK deployment.
{info}
** Messaging Server
** Calendar Server
** Delegated Administrator if you have chosen Sun Java System LDAP Schema, v.2
* Verify whether users are able to log in to the following servers correctly:
** Messaging Server
** Calendar Server
** Access Manager (formerly known as Identity Server), if you want Communications Express to participate in SSO with other products
h2. {anchor:ABZBI} Schema Choices
Prior to installing and configuring, you will need to decide on the schema model you wish to adopt. You have two schema and web container options available when deploying Communications Express.
* Sun Java System LDAP Schema, v.1
* Sun Java System LDAP Schema, v.2
The configurator screen displayed for each schema and web container combination varies depending on your schema and web container selection. [Appendix A, Configuration Panel Sequence|http://docs.sun.com/app/docs/doc/819-4440/gaxwm?a=view], in the _Sun Java System Communications Express 6.3 Administration Guide_, lists the screens that are displayed for each schema and web container combination.
h2. {anchor:ABZBK} Invoking Configuration Wizard
This section describes how to invoke the configuration tool
h6. {anchor:GAXTL} To Invoke the Configuration Wizard
# Log in as Administrator ({{root}} for UNIX or Linux).
# Before invoking the configuration wizard set the display settings.
# Go to _INSTALLROOT_{{/ce/sbin}} directory.
# Type the following at the command prompt to invoke the configuration wizard:\\
\\ {{./config-uwc}} to invoke the configuration tool in the GUI mode.\\
\\ {{./config-uwc -nodisplay}} to invoke the configuration tool in the console mode.
{info:title=Note}
This chapter discusses configuration of Communications Express in GUI mode.
{info}
{info:title=Note}
This version does not support the silent installation mode.
{info}
h2. {anchor:ABZBL} Configuring Communications Express
The following steps walk you through configuring Communications Express.
{info:title=Note}
If you are invoking the configuration wizard in a language other than English, resize the configuration screen to view its contents properly.
{info}
h6. {anchor:GAXWI} To Configure Communications Express
# Run the configuration wizard by following the steps in [Invoking Configuration Wizard|#ABZBK]. \\
The Welcome screen appears. Click Next. The Select the Directory to Store Configuration and Data Files screen appears.\\
\\
# Select the directory in which the configuration and data files for Communications Express should be deployed. \\
For example, {{/var/opt/sun/comms/ce}}. This directory is referred as _uwc-deployed-path_ throughout this guide. \\
Click Next. The Select Components to be Configured screen appears.\\
\\
# Select the components you want to configure and deselect those components you do not wish to configure.\\
The following components are available:
#* Mail Component
#* Calendar Component
{info:title=Note}
You have to select at least one component from the Select Components to be Configured screen.\\
\\Although the component size is displayed as zero, the Mail and Calendar components are installed.
{info}
Click Next. The Network Connection screen appears. The configuration program tries to establish network connection by using the host name and the DNS domain name displayed in this screen.\\
\\ *Host Name*: Displays the host name on which Communications Express is being configured\\
\\ *DNS Domain Name*: Displays the DNS domain name maintained by the DNS Server\\
Click Next. The Select a Web Container screen appears.\\
\\
# Select the web container you want to use.
The options available are:
#* Web Server
#* Application Server
Click Next.\\
If you have selected Web Server as your web container, the following screens appear.\\
\\
#* Configure the Web Server by performing the following steps.\\
\\The Web Server Configuration Details screen appears first.
\\
##* Specify the local Web Server instance details.
###* *Server Root Directory*: Browse to select the installation root of the Web Server. Default location is {{/opt/SUNWwbsvr7/}}.
###* *Server Instance Identifier*: Enter the Web Server instance on which Communications Express is to be deployed. For example, {{budgie.siroe.varrius.com}}.
###* *Virtual Server Identifier*: Enter the virtual server identifier on which Communications Express is to be deployed. For example, {{https-budgie.siroe.varrius.com}}.
###* *HTTP Port*: Enter the HTTP port number Web Server listens to. The Web Server listens to this HTTP port number when Communications Express is accessed.
{info:title=Note}
If you want to configure a secure HTTP port number, specify it after configuring Communications Express. To configure a secure port number see [Configuring Secure Socket Layer|#ABZBZ].
{info}
Click Next. The configuration wizard checks if the Web Server connection instance is alive. If the Web Server instance is not up and running, an error message appears. Refer to [Prerequisites for Configuring Communications Express|#ABZBH] to know more about the prerequisites required before configuring Communications Express.
The Web Server Administration Instance Details screen appears.
##* Specify the Administration Instance Details.
The following options are available
###* *Administration Server Port*: Enter the Web Server administration server port number.
###* *Administration Server User ID*: Enter the Web Server administrator user ID.
###* *Administration Server Password*: Enter the Web Server administrator password.
You will see a small popup window indicating that the Web Server Instance is being verified. This may take a few minutes.\\
\\If the configuration wizard is unable to connect to the Web Server Instance, an error message is displayed. Click Accept, to continue with the installation process, or click Choose New, to specify different Web Server configuration details.\\
\\Click Next. The Web Container User and Group screen appears.\\
\\
##* Specify the identity, the web container uses to run the services.
###* *Web Container User ID*: Displays the web container user identifier from the user database.
###* *Web Container Group ID*: Displays the web container group identifier from the group database.
Click Next. The configuration wizard installs some files and directories containing sensitive data, such as passwords. The ownership of these files and directories are given to web container user and group mentioned in this screen. Only the web container user is given read and write permissions to the files and directories containing sensitive data.
{info:title=Note}
Ensure you enter the correct web container User ID and Group ID values in this screen. Entering wrong values may result in startup failure of the Communications Express.
{info}
Click Next.
#* If you have selected Application Server to be your web container, the following screens appear:\\
\\Configure Application Server by performing the following steps. The Application Server Configuration Details screen appears first.
##* Specify the Application Server Configuration Details that the configuration wizard can use to configure Communications Express with Application Server.
###* *Install Directory*: Browse to select the local directory in which Application Server is installed.
###* *Domain Directory*: Browse to select the domain directory of the Application Server.
###* *Document Root Directory*: Browse to select the document root directory of the Application Server.
###* *Server Target Name*: Enter a name for the Application Server target, for which Communications Express is to be configured. The Communications Express configuration wizard supports only the Domain Administration Server (DAS) deployment for Application Server .
###* *Virtual Server Identifier*: Enter the virtual server identifier for which Communications Express is to be configured.
###* *Server Instance HTTP Port*: Enter the Application Server port number where an HTTP service is available. This is the HTTP port from which Communications Express application will be accessed.
{info:title=Note}
Specify the HTTP Port number here. If you want to configure a secure HTTP port number, specify it after configuring Communications Express. To configure a secure port number, refer to the post configuration steps provided in the section [Configuring Secure Socket Layer|#ABZBZ].
{info}
Click Next. You will see a popup window indicating that the Application Server Instance is being verified. This may take a few minutes. An Error message is displayed if the configure tool is unable to connect to the Application Server Instance. Click Accept, to continue with the installation process, or click Choose New, to specify the Application Server Configuration Details again. When the configuration wizard successfully verifies the Application Server instance, the Application Server instance Details screen is displayed.
##* Specify the administration instance details of the Application Server.\\
\\ The administration instance details are used by the configuration wizard to deploy Communications Express on Application Server:
###* *Administration Server Port*: Enter the Administration Server port number.
{info:title=Note}
The administration port of the Application Server that you specify must be available for configuring Communications Express on Application Server.
{info}
###* *Administrator User ID*: Enter the administrator’s user identifier.
###* *Administrator Password*: Enter the administrator’s user password.
###* *Secure Administration Server Instance*: Select this option to specify that the Application Server’s administration instance is running in the secure mode. Deselect the checkbox, to specify that the Application Server’s administration instance is running in the normal mode.
Depending on the selection, a popup window confirming the mode in which the Application Server’s administration instance is running appears. Click OK to exit the popup window.
{info:title=Note}
When deploying Communications Express on the Application Server, two files, {{server.xml}} and {{server.policy,}} are modified. Before modifying the {{server.xml}} and {{server.policy}} files, a backup of these files is maintained by the configuration wizard. The backup files are stored in the directory: _DOMAIN-DIRECTORY_/ _SERVER-INSTANCE-NAME_/{{config/.CommsExpress_YYYYMMDDhhmmss}}
Here:
* DOMAIN-DIRECTORY is the Application Server’s domain directory.
* SERVER-INSTANCE-NAME is the Application Server Instance Name for which Communications Express is being configured.
* YYYYMMDDhhmmss is the time stamp of the backup directory.
{info}
Click Next. The Module Name for this Web Application screen appears.
##* Enter the module name with which Communications Express should be deployed on Application Server.
The configuration wizard has now collected the required parameters to configure Communications Express with the web container of your choice.\\
\\Click Next. The Web Container User and Group screen appears.\\
# Specify the identity, the web container uses to run the services.
#* *Web Container User ID*: Displays the web container user identifier from the user database.
#* *Web Container Group ID*: Displays the web container group identifier from the group database.
Click Next. The configuration wizard installs some files and directories containing sensitive data, such as passwords. The ownership of these files and directories are given to web container user and group mentioned in this screen. Only the web container user is given read and write permissions to the files and directories containing sensitive data.
{info:title=Note}
Ensure you enter the correct web container User ID and Group ID values in this screen. Entering wrong values may result in startup failure of the Communications Express.
{info}
Click Next. The URI Path Setting screen appears.
# Enter the URI where Communications Express should be deployed.\\
\\For example, {{/uwc}}
{note:title=Caution}
If you are using an existing URI to deploy Communications Express, the configuration tool first removes any previous application data before deploying Communications Express on that URI. For example, if you are deploying Communications Express on a URI such as /uwc that has a web application deployed in it, Communications Express configurator first removes the existing web-application from {{/uwc}} before deploying Communications Express. This could result in the loss of the previous application’s data and accessibility of the application.
{note}
Click Next. The Do you want Hosted Domain Support? screen appears.
# Select the option to enable hosted domain support for Communications Express.\\
\\Select this option only if you have enabled hosted domain support in Calendar Server.\\
\\Click Next. The User/Group Directory (LDAP) Server Details screen appears.
# Enter the following details:\\
\\ *LdapURL*: Specify the user or group LDAP URL in the format {{ldap://}}_UG-LDAP-HOST_{{:}}_UG-LDAP-PORT_ where:
#* _UG-LDAP-HOST_ is the LDAP hostname
#* _UG-LDAP-PORT_ is the LDAP port number
*Bind DN*: Enter the LDAP distinguished name of the User/Group administrator.\\
\\ *Bind Password*: Enter the bind password for User/Group administrator.\\
\\Click Next. The DC Tree Suffix screen appears.
# Enter the base distinguished name for the DC tree suffix.\\
\\This suffix is used by the Communications Express to search for domain lookup.\\
\\Click Next. The Default Domain Name screen appears.
# Enter the default domain name.\\
\\Each domain has certain properties. When a user logs into a domain that does not have the required properties, the properties are picked up from the default domain name.\\
\\Click Next. The Enable Access Manager for Single Sign-on screen appears.
# Select Enable Identity Support for Communications Express if you want to enable Access Manager for Single Sign-on. \\
\\Only if you have enabled Identity Support for Communications Express, the Access Manager Preferences screen is displayed.\\
\\Enter the Access Manager Preferences such as the login URL, Access Manager Administrator DN and Password in this screen.
#* *Admin DN*: Enter the complete LDAP DN (distinguished name) of the Access Manager Administrator, such as {{DN=uid=amAdmin, ou=people,}} _Access Manager-_ _root suffix_.
#* *Admin Password*: Enter the password for the Access Manager administrator.
Click Next. The Messaging Express Port screen appears.
# Specify the Messaging Server related parameters.
This screen appears only when the mail component is selected in the Select Components to be Configured screen.
The following options are available:
#* *Webmail Server Hostname*: Specify the hostname where the webmail server is installed.
#* *Webmail Server Port Number*: Specify the port number which the Messaging Server HTTP ({{mshttpd}}) port number listens to. For example, the default is: {{8990}}.
#* *Enable login in secure mode*: Select this option if you want users to log in secure mode.
#* *Webmail Server SSL Port Number*: If you have configured Webmail Server to run in SSL mode, enter the SSL port number.
#* *Webmail Admin User ID*: Specify the administrator user ID for the Webmail Server.
#* *Admin Password*: Enter the administrator password for webmail.
Click Next. The Calendar Server Host and Port Configuration screen appears.
# Specify the Calendar Server host and port.
This screen appears only when calendar component is selected in the Select Components to be Configured screen.
The options available are:
#* *Calendar Server Host Name*: Enter the Calendar Server’s host name.
#* *Calendar Server HTTP Port Number*: Enter the Calendar Server’s HTTP port number.
Click Next. The Calendar Server Administration Details screen appears.
# Enter the Calendar Server user ID and password.
#* *Administrator User ID*: Enter the Calendar Server’s administrator’s name. For example, calmaster.
#* *Administrator User Password*: Enter the Calendar Server’s administrator’s password.
{info:title=Note}
Ensure that the Calendar Admin User ID value you have entered here is the same as the {{service.admin.calmaster.userid}} value mentioned in Calendar Server’s {{ics.conf}} file.
{info}
Click Next. The PAB Directory Server Details screen appears.
# Specify the details where the PAB entries are stored in the LDAP server.
The Personal Address Book LDAP Server is the store where users personal address books are located. Enter the following details in this screen:
#* *LDAP URL*: Specify the LDAP host and port for the PAB Store. The URL should be in the format: {{ldap://PAB-ldap-hostname:PAB-ldap-portnumber}}
#* *Bind DN*: Enter the LDAP DN to be used to bind to the PAB Store. The Bind DN specified here should have appropriate privileges to manage the data under root suffix {{o=PiServerDB}}.
#* *Password*: Enter the bind password.
Click Next. The Ready to Configure screen appears.\\
\\The configuration program checks for enough disk space on your machine and then lists the components it is ready to configure.
#* Click Configure Now, to configure Communications Express.
#* Click Back, to change any of your configuration variables.
#* Click Cancel, to exit from the configuration program.
If you clicked Configure Now, a summary of tasks and the sequence status is displayed. Click Next. The Configuration Summary screen lists the status of the configuration program. Click Details button to view the log.\\
\\The Post Configuration Instructions screen appears only when the configuration is successful. This screen may display warning messages when the required shared components are not installed. In order to complete the configuration process, follow the post-configuration instructions provided here.
h2. {anchor:ABZBM} Post Configuration Instructions
To complete the configuration process, follow the post configuration steps.
{info:title=Note}
Make sure you are familiar with the location of the Communications Express files. Refer to the section on [Default Paths and File Names|http://docs.sun.com/app/docs/doc/819-4440/6n6jfgch1?a=view] in the _Sun Java System Communications Express 6.3 Administration Guide_.\\
\\Refer to [Chapter 3, Configuration Details|http://docs.sun.com/app/docs/doc/819-4440/abzbp?a=view] in the _Sun Java System Communications Express 6.3 Administration Guide_ for more details on the configuration parameters.
{info}
h6. {anchor:GAXWF} To Configure Communications Express After Installation
After installing Communications Express, ensure that for a setup using Access Manager single sign-on, the Core and LDAP services are added. For more information, refer to the section on [Tuning LDAP Related Configuration Parameters|http://docs.sun.com/app/docs/doc/819-4440/6n6jfgcj6?a=view] in the _Sun Java System Communications Express 6.3 Administration Guide_. \\
\\After you have configured Communications Express, perform the following steps:
# Enable the Mail component in Communications Express by configuring Single Sign-On. \\
\\Refer to [Chapter 1, Overview of Communications Express|http://docs.sun.com/app/docs/doc/819-4440/6n6jfgcgs?a=view] in the _Sun Java System Communications Express 6.3 Administration Guide_ for information on configuring Messenger Express and Communications Express.
Use the {{configutil}} command to set the following parameters in the Messaging Server configuration file, {{msg.conf}}.
For details about these parameters, see [CommSuite:Messaging Server Configuration]. For details about using the {{configutil}} command, see the [_Sun Java System Messaging Server 6.3 Administration Reference_|http://docs.sun.com/app/docs/doc/819-4429].
#* {{local.webmail.sso.uwccontexturi =}} _context-uri-for-communications-express-installation_
#* {{local.webmail.sso.uwcport =}} _uwc-port-for-communications-express-installation_
#* {{local.webmail.sso.uwcsslport =}} _uwc—ssl-port-for-communications-express-installation_
#* {{local.webmail.sso.uwcenabled =}} 1
# Go to _calendar-server-install-directory_{{/SUNWics5/cal/bin/config}} (For example, {{/opt/SUNWics5/cal/bin/config}} ).
Edit the {{ics.conf}} file and set the following:
#* {{service.http.allowadminproxy =}} {{"yes"}}
#* {{service.http.admins =}} _proxy-admin-for-calendar-http-service_
#* {{service.admin.calmaster.userid =}} {{the-value-specified-for- calendar.wcap.adminid-in-uwcconfig.properties}}
#* {{service.admin.calmaster.cred =}} {{the-value-specified-for- calendar.wcap.passwd-in-uwcconfig.properties}}
#* {{service.wcap.anonymous.allowpubliccalendarwrite =}} {{"yes"}}
#* {{service.http.allowanonymouslogin =}} {{"yes"}}
#* {{service.calendarsearch.ldap =}} {{"no"}}
#* {{service.http.ui.enabled =}} {{"yes"}}
If you have edited the {{ics.conf}} file, restart Calendar Server for the changes to take effect.
# To enable Communications Express for Access Manager SSO, see [Setting up Access Manager Single sign-on|http://docs.sun.com/app/docs/doc/819-4440/6n6jfgci5?a=view].
# Type the following commands to restart the Messaging Server.\\
\\ _msg-svr-base_{{/sbin/}}{{stop-msg}}\\
\\ _msg-svr-base_{{/sbin/s}}{{tart-msg}}
# Type the following commands to restart the Calendar Server.\\
\\ _cal-svr-base_{{/cal/sbin/}}{{stop-cal}}\\
\\ _cal-svr-base_{{/cal/sbin/}}{{start-cal}}
# Restart the web container.\\
\\Communications Express is now ready and you can access the application from:\\
{{http(s)://}}_Web-Container-host_{{:}}_Web-Container-port_{{/}}{{URI}} {{path}}\\
\\where:
#* _Web-Container-host_ is the host name of the web container instance in which the Communications Express application is configured.
#* _Web-Container-port_ is port number of the web container instance in which the Communications Express is configured.
#* {{URI path}} is the path specified in the URI Path Setting screen.
h2. {anchor:ABZBQ} Customizing the Landing Page of Communications Express
The landing page displayed after login can be customized by using a parameter called {{gotoUri}}. You can customize the landing page to display the Calendar, Address Book, or Options page. By default, the landing page of Communications Express displays the Mail page.
{info:title=Note}
This feature is available only if you have applied the patch version of Communications Express 6.3.
{info}
You can customize the landing page by using one of the following options:
* Modifying the browser URL
* Modifying the LDAP attribute
* Modifying the server configuration parameter
h6. {anchor:GAXWH} Customizing the Landing Page by Using the Browser URL
To customize the landing page, you should add the {{gotoUri}} parameter to your browser URL in the following format:
{{http://}}_host name_{{:}}_port number_{{/uwc/?gotoUri=}}_landing page choice_
For example, to customize the landing page to display the Address Book page, type the URL in the following format:
{code}
http://xyz.com:8080/uwc/?gotoUri=/abclient/AddressBook
{code}
{info:title= Note}
This customization applies only to the current session and needs to be reset for every session.
{info}
h6. {anchor:GAXWJ} Customizing the Landing Page by Modifying the LDAP Attribute
The user LDAP (or Sun Java System Directory Server) entry has a multivalued attribute called {{sunUCExtendedUserPrefs}}. You can customize the landing page by adding the following value to the attribute:
{{landingPage=}}_landing page choice_
For example, {{landingPage=/abclient/AddressBook}}
{info:title=Note}
This customization applies to the user whose entry has been modified with the attribute, and needs to be added only once. However, you can override this customization by setting the {{gotoUri}} parameter in your browser URL.
{info}
h6. {anchor:GAXWK} Customizing the Landing Page by Modifying the Server Configuration Parameter
You can customize the landing page by adding the following configuration parameter in the {{uwcconfig.properties}} file:
{{uwc.gotoUri=}}_landing page choice_
For example, {{uwc.gotoUri=/abclient/AddressBook}}
The configuration file is located in the _uwc-deploy-dir_{{/WEB-INF/config}} directory on the server.
{info:title=Note}
This customization applies to all users and the configuration parameter must be added only once. However, you can choose to override the customization by using the previous options.
{info}
You can use the following configuration parameter values to set the landing page:
* {{/abclient/AddressBook}} - to set the Address Book page as the landing page
* {{/base/UWCMain?forwardtodefview=true}} - to set the Calendar page as the landing page
* {{/base/MailOptions}} - to set the Mail Options page as the landing page
* {{/base/CalendarPreferences}} - to set the Mail Options page as the landing page
* {{/base/ABPreferences}} - to set the Address Book Options page as the landing page
* {{/base/UserPreferencesSettings}} - to set the Global Options page as the landing page
{info:title=Note}
When you use more than one option to set the {{gotoUri}} parameter, the system takes the following configuration precedence:
# Browser URL
# User LDAP attribute
# Server configuration parameter
{info}
h2. {anchor:ABZBN} Undeploying Communications Express
To undeploy Communications Express from Web Server or Application Server, you need to undeploy the Communications Express web application. Please refer to the relevant documentation for Web Server and Application Server on how to undeploy an application.
This chapter describes the configuration and migration steps you must perform, after installation, before you can use Communications Express.
This document includes the following sections:
{toc:minLevel=2|maxLevel=2}
h2. {anchor:GAXST} Before You Begin
Before you configure Communications Express, make sure you have the following dependent components installed and configured:
* Directory Server.
* Messaging Server and Calendar Server. Make sure you have recorded the relevant details about the installations, such as the hostname, port number, administrator username and password.
* Be sure you have run the Comm Directory Server set-up script, {{comm_dssetup.pl}}.
h2. {anchor:ABZBO} Communications Express File Directory Layout
After you install and configure Communications Express, the related files and directories are arranged in the organization as shown in [Table 2-1|#GAXUP]. The table is not exhaustive. It shows only the required directories and files for typical server administration tasks.
h6. {anchor:GAXUP} Table 2-1 Communications Express Directories and Files
||Directory and Legends||Default Location and Description||
|Communications Express Base\\
\\ {{uwc-basedir}}|Default location:\\
\\Solaris™: {{/opt/sun/comms/ce/}}\\
\\Linux: {{/opt/sun/comms/ce/}}\\
\\Communications Express is installed in this directory.\\
\\Note: On Solaris OS 10, the Communications Suite installer allows multi-installation of Communications Express; you can install multiple Communications Express base directories per machine. On Linux, only one Communications Express base directory is permitted.|
|Deployed Directory\\
\\ {{uwc-deployed-dir}}|Default location:\\
\\Solaris: {{/var/opt/comms/ce/}}\\
\\Linux: {{/var/opt/comms/ce/}}\\
\\Communications Express is deployed in this directory. The web container takes the files from this location while loading Communications Express.|
|Web Applications Root Directory\\
\\ {{WEB-INF}}|_uwc-deployed-dir_/{{WEB-INF}}\\
\\ {{WEB-INF}} directory of Communications Express web application|
|Webmail directory|{{uwc-deployed-dir/webmail}}\\
\\Contains all the webmail related files that Communications Express uses.|
|Configuration\\
\\ {{config}}|_uwc-deployed-dir_/{{WEB-INF/config/}}\\
\\Contains all the Communications Express configuration files|
|Domain\\
\\ {{domain}}|_uwc-deployed-dir_/{{WEB-INF/domain/}}\\
\\Contains per domain localization and Customization files|
|Skin\\
\\ {{skin}}|_uwc-deployed-dir_/{{WEB-INF/skin/}}\\
\\Contains per domain themes|
|Logs\\
\\ {{logs}}|_uwc-deployed-dir_/{{logs/}}\\
\\Contains the Communications Express log files. By default log messages are saved to the Web Server's error log file. You can change this location by setting the {{log.file}} configuration parameter in the {{uwcconfig.properties file}}.|
|System Administrator Programs\\
\\ {{sbin}}|_uwc-basedir_/{{sbin/}}\\
\\Contains the Communications Express system administrator executable programs and scripts|
|Help\\
\\ {{help}}|_uwc-deployed-dir_/{{help}}\\
\\Contains Communications Express help files|
h2. {anchor:ABZBH} Prerequisites for Configuring Communications Express
Before running the Communications Express configuration wizard, make sure you:
* Choose your schema. Refer to the section on [Schema Choices|#ABZBI] for information on the available schema.
* Ensure that you have the following entry in the {{/etc/hosts}} file on your Solaris system:\\
\\ _ip-of system_ _Fully-Qualified-Hostname_\\
\\For example,\\
\\ {{129.158.230.64 budgie.siroe.varrius.com budgie}}
* Ensure that the following components are up and running before you configure Communications Express. Make sure that the configuration of the products for Communications Express is done in the following order:
** Directory Server
** Application Server or Web Server
** Access Manager, if Communications Express wants to participate in SSO (Single Sign On) with other products (For example, Portal Server).
{info:title=Note}
The Web Server that is hosting Communications Express should be running as {{root}} when configuring for Remote AM SDK deployment.
{info}
** Messaging Server
** Calendar Server
** Delegated Administrator if you have chosen Sun Java System LDAP Schema, v.2
* Verify whether users are able to log in to the following servers correctly:
** Messaging Server
** Calendar Server
** Access Manager (formerly known as Identity Server), if you want Communications Express to participate in SSO with other products
h2. {anchor:ABZBI} Schema Choices
Prior to installing and configuring, you will need to decide on the schema model you wish to adopt. You have two schema and web container options available when deploying Communications Express.
* Sun Java System LDAP Schema, v.1
* Sun Java System LDAP Schema, v.2
The configurator screen displayed for each schema and web container combination varies depending on your schema and web container selection. [Appendix A, Configuration Panel Sequence|http://docs.sun.com/app/docs/doc/819-4440/gaxwm?a=view], in the _Sun Java System Communications Express 6.3 Administration Guide_, lists the screens that are displayed for each schema and web container combination.
h2. {anchor:ABZBK} Invoking Configuration Wizard
This section describes how to invoke the configuration tool
h6. {anchor:GAXTL} To Invoke the Configuration Wizard
# Log in as Administrator ({{root}} for UNIX or Linux).
# Before invoking the configuration wizard set the display settings.
# Go to _INSTALLROOT_{{/ce/sbin}} directory.
# Type the following at the command prompt to invoke the configuration wizard:\\
\\ {{./config-uwc}} to invoke the configuration tool in the GUI mode.\\
\\ {{./config-uwc -nodisplay}} to invoke the configuration tool in the console mode.
{info:title=Note}
This chapter discusses configuration of Communications Express in GUI mode.
{info}
{info:title=Note}
This version does not support the silent installation mode.
{info}
h2. {anchor:ABZBL} Configuring Communications Express
The following steps walk you through configuring Communications Express.
{info:title=Note}
If you are invoking the configuration wizard in a language other than English, resize the configuration screen to view its contents properly.
{info}
h6. {anchor:GAXWI} To Configure Communications Express
# Run the configuration wizard by following the steps in [Invoking Configuration Wizard|#ABZBK]. \\
The Welcome screen appears. Click Next. The Select the Directory to Store Configuration and Data Files screen appears.\\
\\
# Select the directory in which the configuration and data files for Communications Express should be deployed. \\
For example, {{/var/opt/sun/comms/ce}}. This directory is referred as _uwc-deployed-path_ throughout this guide. \\
Click Next. The Select Components to be Configured screen appears.\\
\\
# Select the components you want to configure and deselect those components you do not wish to configure.\\
The following components are available:
#* Mail Component
#* Calendar Component
{info:title=Note}
You have to select at least one component from the Select Components to be Configured screen.\\
\\Although the component size is displayed as zero, the Mail and Calendar components are installed.
{info}
Click Next. The Network Connection screen appears. The configuration program tries to establish network connection by using the host name and the DNS domain name displayed in this screen.\\
\\ *Host Name*: Displays the host name on which Communications Express is being configured\\
\\ *DNS Domain Name*: Displays the DNS domain name maintained by the DNS Server\\
Click Next. The Select a Web Container screen appears.\\
\\
# Select the web container you want to use.
The options available are:
#* Web Server
#* Application Server
Click Next.\\
If you have selected Web Server as your web container, the following screens appear.\\
\\
#* Configure the Web Server by performing the following steps.\\
\\The Web Server Configuration Details screen appears first.
\\
##* Specify the local Web Server instance details.
###* *Server Root Directory*: Browse to select the installation root of the Web Server. Default location is {{/opt/SUNWwbsvr7/}}.
###* *Server Instance Identifier*: Enter the Web Server instance on which Communications Express is to be deployed. For example, {{budgie.siroe.varrius.com}}.
###* *Virtual Server Identifier*: Enter the virtual server identifier on which Communications Express is to be deployed. For example, {{https-budgie.siroe.varrius.com}}.
###* *HTTP Port*: Enter the HTTP port number Web Server listens to. The Web Server listens to this HTTP port number when Communications Express is accessed.
{info:title=Note}
If you want to configure a secure HTTP port number, specify it after configuring Communications Express. To configure a secure port number see [Configuring Secure Socket Layer|#ABZBZ].
{info}
Click Next. The configuration wizard checks if the Web Server connection instance is alive. If the Web Server instance is not up and running, an error message appears. Refer to [Prerequisites for Configuring Communications Express|#ABZBH] to know more about the prerequisites required before configuring Communications Express.
The Web Server Administration Instance Details screen appears.
##* Specify the Administration Instance Details.
The following options are available
###* *Administration Server Port*: Enter the Web Server administration server port number.
###* *Administration Server User ID*: Enter the Web Server administrator user ID.
###* *Administration Server Password*: Enter the Web Server administrator password.
You will see a small popup window indicating that the Web Server Instance is being verified. This may take a few minutes.\\
\\If the configuration wizard is unable to connect to the Web Server Instance, an error message is displayed. Click Accept, to continue with the installation process, or click Choose New, to specify different Web Server configuration details.\\
\\Click Next. The Web Container User and Group screen appears.\\
\\
##* Specify the identity, the web container uses to run the services.
###* *Web Container User ID*: Displays the web container user identifier from the user database.
###* *Web Container Group ID*: Displays the web container group identifier from the group database.
Click Next. The configuration wizard installs some files and directories containing sensitive data, such as passwords. The ownership of these files and directories are given to web container user and group mentioned in this screen. Only the web container user is given read and write permissions to the files and directories containing sensitive data.
{info:title=Note}
Ensure you enter the correct web container User ID and Group ID values in this screen. Entering wrong values may result in startup failure of the Communications Express.
{info}
Click Next.
#* If you have selected Application Server to be your web container, the following screens appear:\\
\\Configure Application Server by performing the following steps. The Application Server Configuration Details screen appears first.
##* Specify the Application Server Configuration Details that the configuration wizard can use to configure Communications Express with Application Server.
###* *Install Directory*: Browse to select the local directory in which Application Server is installed.
###* *Domain Directory*: Browse to select the domain directory of the Application Server.
###* *Document Root Directory*: Browse to select the document root directory of the Application Server.
###* *Server Target Name*: Enter a name for the Application Server target, for which Communications Express is to be configured. The Communications Express configuration wizard supports only the Domain Administration Server (DAS) deployment for Application Server .
###* *Virtual Server Identifier*: Enter the virtual server identifier for which Communications Express is to be configured.
###* *Server Instance HTTP Port*: Enter the Application Server port number where an HTTP service is available. This is the HTTP port from which Communications Express application will be accessed.
{info:title=Note}
Specify the HTTP Port number here. If you want to configure a secure HTTP port number, specify it after configuring Communications Express. To configure a secure port number, refer to the post configuration steps provided in the section [Configuring Secure Socket Layer|#ABZBZ].
{info}
Click Next. You will see a popup window indicating that the Application Server Instance is being verified. This may take a few minutes. An Error message is displayed if the configure tool is unable to connect to the Application Server Instance. Click Accept, to continue with the installation process, or click Choose New, to specify the Application Server Configuration Details again. When the configuration wizard successfully verifies the Application Server instance, the Application Server instance Details screen is displayed.
##* Specify the administration instance details of the Application Server.\\
\\ The administration instance details are used by the configuration wizard to deploy Communications Express on Application Server:
###* *Administration Server Port*: Enter the Administration Server port number.
{info:title=Note}
The administration port of the Application Server that you specify must be available for configuring Communications Express on Application Server.
{info}
###* *Administrator User ID*: Enter the administrator’s user identifier.
###* *Administrator Password*: Enter the administrator’s user password.
###* *Secure Administration Server Instance*: Select this option to specify that the Application Server’s administration instance is running in the secure mode. Deselect the checkbox, to specify that the Application Server’s administration instance is running in the normal mode.
Depending on the selection, a popup window confirming the mode in which the Application Server’s administration instance is running appears. Click OK to exit the popup window.
{info:title=Note}
When deploying Communications Express on the Application Server, two files, {{server.xml}} and {{server.policy,}} are modified. Before modifying the {{server.xml}} and {{server.policy}} files, a backup of these files is maintained by the configuration wizard. The backup files are stored in the directory: _DOMAIN-DIRECTORY_/ _SERVER-INSTANCE-NAME_/{{config/.CommsExpress_YYYYMMDDhhmmss}}
Here:
* DOMAIN-DIRECTORY is the Application Server’s domain directory.
* SERVER-INSTANCE-NAME is the Application Server Instance Name for which Communications Express is being configured.
* YYYYMMDDhhmmss is the time stamp of the backup directory.
{info}
Click Next. The Module Name for this Web Application screen appears.
##* Enter the module name with which Communications Express should be deployed on Application Server.
The configuration wizard has now collected the required parameters to configure Communications Express with the web container of your choice.\\
\\Click Next. The Web Container User and Group screen appears.\\
# Specify the identity, the web container uses to run the services.
#* *Web Container User ID*: Displays the web container user identifier from the user database.
#* *Web Container Group ID*: Displays the web container group identifier from the group database.
Click Next. The configuration wizard installs some files and directories containing sensitive data, such as passwords. The ownership of these files and directories are given to web container user and group mentioned in this screen. Only the web container user is given read and write permissions to the files and directories containing sensitive data.
{info:title=Note}
Ensure you enter the correct web container User ID and Group ID values in this screen. Entering wrong values may result in startup failure of the Communications Express.
{info}
Click Next. The URI Path Setting screen appears.
# Enter the URI where Communications Express should be deployed.\\
\\For example, {{/uwc}}
{note:title=Caution}
If you are using an existing URI to deploy Communications Express, the configuration tool first removes any previous application data before deploying Communications Express on that URI. For example, if you are deploying Communications Express on a URI such as /uwc that has a web application deployed in it, Communications Express configurator first removes the existing web-application from {{/uwc}} before deploying Communications Express. This could result in the loss of the previous application’s data and accessibility of the application.
{note}
Click Next. The Do you want Hosted Domain Support? screen appears.
# Select the option to enable hosted domain support for Communications Express.\\
\\Select this option only if you have enabled hosted domain support in Calendar Server.\\
\\Click Next. The User/Group Directory (LDAP) Server Details screen appears.
# Enter the following details:\\
\\ *LdapURL*: Specify the user or group LDAP URL in the format {{ldap://}}_UG-LDAP-HOST_{{:}}_UG-LDAP-PORT_ where:
#* _UG-LDAP-HOST_ is the LDAP hostname
#* _UG-LDAP-PORT_ is the LDAP port number
*Bind DN*: Enter the LDAP distinguished name of the User/Group administrator.\\
\\ *Bind Password*: Enter the bind password for User/Group administrator.\\
\\Click Next. The DC Tree Suffix screen appears.
# Enter the base distinguished name for the DC tree suffix.\\
\\This suffix is used by the Communications Express to search for domain lookup.\\
\\Click Next. The Default Domain Name screen appears.
# Enter the default domain name.\\
\\Each domain has certain properties. When a user logs into a domain that does not have the required properties, the properties are picked up from the default domain name.\\
\\Click Next. The Enable Access Manager for Single Sign-on screen appears.
# Select Enable Identity Support for Communications Express if you want to enable Access Manager for Single Sign-on. \\
\\Only if you have enabled Identity Support for Communications Express, the Access Manager Preferences screen is displayed.\\
\\Enter the Access Manager Preferences such as the login URL, Access Manager Administrator DN and Password in this screen.
#* *Admin DN*: Enter the complete LDAP DN (distinguished name) of the Access Manager Administrator, such as {{DN=uid=amAdmin, ou=people,}} _Access Manager-_ _root suffix_.
#* *Admin Password*: Enter the password for the Access Manager administrator.
Click Next. The Messaging Express Port screen appears.
# Specify the Messaging Server related parameters.
This screen appears only when the mail component is selected in the Select Components to be Configured screen.
The following options are available:
#* *Webmail Server Hostname*: Specify the hostname where the webmail server is installed.
#* *Webmail Server Port Number*: Specify the port number which the Messaging Server HTTP ({{mshttpd}}) port number listens to. For example, the default is: {{8990}}.
#* *Enable login in secure mode*: Select this option if you want users to log in secure mode.
#* *Webmail Server SSL Port Number*: If you have configured Webmail Server to run in SSL mode, enter the SSL port number.
#* *Webmail Admin User ID*: Specify the administrator user ID for the Webmail Server.
#* *Admin Password*: Enter the administrator password for webmail.
Click Next. The Calendar Server Host and Port Configuration screen appears.
# Specify the Calendar Server host and port.
This screen appears only when calendar component is selected in the Select Components to be Configured screen.
The options available are:
#* *Calendar Server Host Name*: Enter the Calendar Server’s host name.
#* *Calendar Server HTTP Port Number*: Enter the Calendar Server’s HTTP port number.
Click Next. The Calendar Server Administration Details screen appears.
# Enter the Calendar Server user ID and password.
#* *Administrator User ID*: Enter the Calendar Server’s administrator’s name. For example, calmaster.
#* *Administrator User Password*: Enter the Calendar Server’s administrator’s password.
{info:title=Note}
Ensure that the Calendar Admin User ID value you have entered here is the same as the {{service.admin.calmaster.userid}} value mentioned in Calendar Server’s {{ics.conf}} file.
{info}
Click Next. The PAB Directory Server Details screen appears.
# Specify the details where the PAB entries are stored in the LDAP server.
The Personal Address Book LDAP Server is the store where users personal address books are located. Enter the following details in this screen:
#* *LDAP URL*: Specify the LDAP host and port for the PAB Store. The URL should be in the format: {{ldap://PAB-ldap-hostname:PAB-ldap-portnumber}}
#* *Bind DN*: Enter the LDAP DN to be used to bind to the PAB Store. The Bind DN specified here should have appropriate privileges to manage the data under root suffix {{o=PiServerDB}}.
#* *Password*: Enter the bind password.
Click Next. The Ready to Configure screen appears.\\
\\The configuration program checks for enough disk space on your machine and then lists the components it is ready to configure.
#* Click Configure Now, to configure Communications Express.
#* Click Back, to change any of your configuration variables.
#* Click Cancel, to exit from the configuration program.
If you clicked Configure Now, a summary of tasks and the sequence status is displayed. Click Next. The Configuration Summary screen lists the status of the configuration program. Click Details button to view the log.\\
\\The Post Configuration Instructions screen appears only when the configuration is successful. This screen may display warning messages when the required shared components are not installed. In order to complete the configuration process, follow the post-configuration instructions provided here.
h2. {anchor:ABZBM} Post Configuration Instructions
To complete the configuration process, follow the post configuration steps.
{info:title=Note}
Make sure you are familiar with the location of the Communications Express files. Refer to the section on [Default Paths and File Names|http://docs.sun.com/app/docs/doc/819-4440/6n6jfgch1?a=view] in the _Sun Java System Communications Express 6.3 Administration Guide_.\\
\\Refer to [Chapter 3, Configuration Details|http://docs.sun.com/app/docs/doc/819-4440/abzbp?a=view] in the _Sun Java System Communications Express 6.3 Administration Guide_ for more details on the configuration parameters.
{info}
h6. {anchor:GAXWF} To Configure Communications Express After Installation
After installing Communications Express, ensure that for a setup using Access Manager single sign-on, the Core and LDAP services are added. For more information, refer to the section on [Tuning LDAP Related Configuration Parameters|http://docs.sun.com/app/docs/doc/819-4440/6n6jfgcj6?a=view] in the _Sun Java System Communications Express 6.3 Administration Guide_. \\
\\After you have configured Communications Express, perform the following steps:
# Enable the Mail component in Communications Express by configuring Single Sign-On. \\
\\Refer to [Chapter 1, Overview of Communications Express|http://docs.sun.com/app/docs/doc/819-4440/6n6jfgcgs?a=view] in the _Sun Java System Communications Express 6.3 Administration Guide_ for information on configuring Messenger Express and Communications Express.
Use the {{configutil}} command to set the following parameters in the Messaging Server configuration file, {{msg.conf}}.
For details about these parameters, see [CommSuite:Messaging Server Configuration]. For details about using the {{configutil}} command, see the [_Sun Java System Messaging Server 6.3 Administration Reference_|http://docs.sun.com/app/docs/doc/819-4429].
#* {{local.webmail.sso.uwccontexturi =}} _context-uri-for-communications-express-installation_
#* {{local.webmail.sso.uwcport =}} _uwc-port-for-communications-express-installation_
#* {{local.webmail.sso.uwcsslport =}} _uwc—ssl-port-for-communications-express-installation_
#* {{local.webmail.sso.uwcenabled =}} 1
# Go to _calendar-server-install-directory_{{/SUNWics5/cal/bin/config}} (For example, {{/opt/SUNWics5/cal/bin/config}} ).
Edit the {{ics.conf}} file and set the following:
#* {{service.http.allowadminproxy =}} {{"yes"}}
#* {{service.http.admins =}} _proxy-admin-for-calendar-http-service_
#* {{service.admin.calmaster.userid =}} {{the-value-specified-for- calendar.wcap.adminid-in-uwcconfig.properties}}
#* {{service.admin.calmaster.cred =}} {{the-value-specified-for- calendar.wcap.passwd-in-uwcconfig.properties}}
#* {{service.wcap.anonymous.allowpubliccalendarwrite =}} {{"yes"}}
#* {{service.http.allowanonymouslogin =}} {{"yes"}}
#* {{service.calendarsearch.ldap =}} {{"no"}}
#* {{service.http.ui.enabled =}} {{"yes"}}
If you have edited the {{ics.conf}} file, restart Calendar Server for the changes to take effect.
# To enable Communications Express for Access Manager SSO, see [Setting up Access Manager Single sign-on|http://docs.sun.com/app/docs/doc/819-4440/6n6jfgci5?a=view].
# Type the following commands to restart the Messaging Server.\\
\\ _msg-svr-base_{{/sbin/}}{{stop-msg}}\\
\\ _msg-svr-base_{{/sbin/s}}{{tart-msg}}
# Type the following commands to restart the Calendar Server.\\
\\ _cal-svr-base_{{/cal/sbin/}}{{stop-cal}}\\
\\ _cal-svr-base_{{/cal/sbin/}}{{start-cal}}
# Restart the web container.\\
\\Communications Express is now ready and you can access the application from:\\
{{http(s)://}}_Web-Container-host_{{:}}_Web-Container-port_{{/}}{{URI}} {{path}}\\
\\where:
#* _Web-Container-host_ is the host name of the web container instance in which the Communications Express application is configured.
#* _Web-Container-port_ is port number of the web container instance in which the Communications Express is configured.
#* {{URI path}} is the path specified in the URI Path Setting screen.
h2. {anchor:ABZBQ} Customizing the Landing Page of Communications Express
The landing page displayed after login can be customized by using a parameter called {{gotoUri}}. You can customize the landing page to display the Calendar, Address Book, or Options page. By default, the landing page of Communications Express displays the Mail page.
{info:title=Note}
This feature is available only if you have applied the patch version of Communications Express 6.3.
{info}
You can customize the landing page by using one of the following options:
* Modifying the browser URL
* Modifying the LDAP attribute
* Modifying the server configuration parameter
h6. {anchor:GAXWH} Customizing the Landing Page by Using the Browser URL
To customize the landing page, you should add the {{gotoUri}} parameter to your browser URL in the following format:
{{http://}}_host name_{{:}}_port number_{{/uwc/?gotoUri=}}_landing page choice_
For example, to customize the landing page to display the Address Book page, type the URL in the following format:
{code}
http://xyz.com:8080/uwc/?gotoUri=/abclient/AddressBook
{code}
{info:title= Note}
This customization applies only to the current session and needs to be reset for every session.
{info}
h6. {anchor:GAXWJ} Customizing the Landing Page by Modifying the LDAP Attribute
The user LDAP (or Sun Java System Directory Server) entry has a multivalued attribute called {{sunUCExtendedUserPrefs}}. You can customize the landing page by adding the following value to the attribute:
{{landingPage=}}_landing page choice_
For example, {{landingPage=/abclient/AddressBook}}
{info:title=Note}
This customization applies to the user whose entry has been modified with the attribute, and needs to be added only once. However, you can override this customization by setting the {{gotoUri}} parameter in your browser URL.
{info}
h6. {anchor:GAXWK} Customizing the Landing Page by Modifying the Server Configuration Parameter
You can customize the landing page by adding the following configuration parameter in the {{uwcconfig.properties}} file:
{{uwc.gotoUri=}}_landing page choice_
For example, {{uwc.gotoUri=/abclient/AddressBook}}
The configuration file is located in the _uwc-deploy-dir_{{/WEB-INF/config}} directory on the server.
{info:title=Note}
This customization applies to all users and the configuration parameter must be added only once. However, you can choose to override the customization by using the previous options.
{info}
You can use the following configuration parameter values to set the landing page:
* {{/abclient/AddressBook}} - to set the Address Book page as the landing page
* {{/base/UWCMain?forwardtodefview=true}} - to set the Calendar page as the landing page
* {{/base/MailOptions}} - to set the Mail Options page as the landing page
* {{/base/CalendarPreferences}} - to set the Mail Options page as the landing page
* {{/base/ABPreferences}} - to set the Address Book Options page as the landing page
* {{/base/UserPreferencesSettings}} - to set the Global Options page as the landing page
{info:title=Note}
When you use more than one option to set the {{gotoUri}} parameter, the system takes the following configuration precedence:
# Browser URL
# User LDAP attribute
# Server configuration parameter
{info}
h2. {anchor:ABZBN} Undeploying Communications Express
To undeploy Communications Express from Web Server or Application Server, you need to undeploy the Communications Express web application. Please refer to the relevant documentation for Web Server and Application Server on how to undeploy an application.