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.

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.

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 to know more about the prerequisites required
before configuring Communications Express. The Web Server Administration Instance Details
screen appears.

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.

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.

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.

Click Next.

If you have selected Application Server to be your web container,
the following screens appear:

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.

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 .

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:

The administration port of the Application Server that you specify
must be available for configuring Communications Express on Application Server.

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.

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.

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.

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.

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.

Click Next. The URI Path Setting screen appears.

Enter the URI where Communications Express should be deployed.

For
example, /uwc.

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.

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.

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.

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.