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 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

    ---

    Note –

    After this step, run the Directory Preparation Script comm_dssetup.pl to update the schema details in the User/Group Directory Server.

    To run Directory Preparation Script (comm_dssetup.pl) type:

    cd /root -of -the -directory -preparatory-script /SUNWcomds/sbin. By default, the directory preparation script can be found at the following path:

    • Solaris: /opt/SUNWcomds/sbin

    • Linux: /opt/sun/comms/dssetup/sbin

    perl comm_dssetup.pl

    ---

  • Access Manager, if Communications Express wants to participate in SSO (Single Sign On ) with other products (For example, Portal Server).

    ---

    Note –

    The Web Server that is hosting Communications Express should be running as rootwhen configuring for Remote AM SDK deployment.

    ---

  • 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