Calendar Server Initial Configuration

Skip to end of metadata
Go to start of metadata

< Back to Installation Scenario - Calendar Server

Oracle Communications Calendar Server Initial Configuration
Version 7 Update 2

After you install the Calendar Server software by using the Communications Suite installer, you must configure Calendar Server to complete the installation. You perform this initial runtime configuration by running the Calendar Server configuration program, init-config.

  1. If you haven't done so already, run the comm_dssetup.pl script, which is installed by the Communications Suite installer, to prepare the LDAP Directory Server.
    See Communications Suite Directory Server Setup Script (comm_dssetup.pl).
    Note
    You can use either LDAP Schema 2 or Schema 1. For information on how Calendar Server uses Directory Server, see Calendar Server and Directory Server Integration.
  2. Configure Calendar Server by running the init-config command and responding to the prompts.
    Running the init-config command completes the Calendar Server software installation.
    1. Log in as or become superuser (root).
      Note
      Log in as "su -" when running init-config if you installed GlassFish Server with secure mode.
    2. Change to the cal-svr-base/sbin directory.
      The default installation directory is /opt/sun/comms/davserver.
    3. Run the script.
      See Oracle Communications Calendar Server init-config Syntax for more information.
      ./init-config
      

      For example, to run the configuration script in command-line mode, run the following command:

      ./init-config -nodisplay
      
    4. Respond to the prompts that appear on each screen.
      Note
      For the text of the information contained in the various questions presented by the script, refer to the Configuration Worksheets - Calendar Server.
      1. Screen 1: Select the Directory to Store Configuration and Data Files.
        The default directory is /var/opt/sun/comms/davserver.
      2. Screen 2: Select Components to be Configured.
        Currently, there is only the Calendar Server component.
      3. Screen 3: Network Connection.
        Type your host name then DNS domain name.
      4. Screen 4: Select type of database for back end.
        Choose MySQL database or Oracle database.
      5. Screen 5: MySQL Server Configuration Details or Oracle Database Server Configuration Details
        Type the following information, depending on whether you chose MySQL database or Oracle database:
        • MySQL Server Details
          • Server Host (default: localhost)
          • Server Port (default: 3306)
          • Database User (default: caldav)
          • Password
          • Calendar DB Name (default: caldav)
          • iSchedule DB Name (default: ischedule)
            Note
            The iSchedule protocol (currently in draft) defines how to handle scheduling between two different calendar servers. In general, the architecture accounts for a global calendar inbox/outbox for invitations. However, because iSchedule is still in draft form and not a standard, general adoption of the protocol has not yet taken place. Calendar Server currently handles invitations through the iMIP protocol (that is, by email). You need to configure the iSchedule database even though it is not currently used. If you remove the iSchedule database configuration, Calendar Server 7 Update 2 does not function correctly without it.

            A pop-up message appears if you do not have the correct value entered for the MySQL Server:

            Unable to connect to the MySQL server: <hostname>:3306. This may result in an incomplete configuration, if you accept the current MySQL server host and port details. Select Accept if you want to continue configuration using the current values.
            

            You can click either the Accept or Choose New button. Then continue with Screen 6 to configure the document store.

        • Oracle Database Server Details
          • Server Host (default: localhost)
          • Server Port (default: 1521)
          • Service Name (default: orcl.domain)
          • Calendar DB User (default: caldav)
          • Password
          • iSchedule DB User (default: ischedule)
          • Password
            A pop-up message appears if you do not have the correct value entered for the Oracle Database:
            Unable to connect to the Oracle Database Server: <hostname>:1521. This may result in an incomplete configuration, if you accept the current Oracle Database server host and port details. Select Accept if you want to continue configuration using the current values.
            

            You can click either the Accept or Choose New button. Then continue with Screen 6 to configure the document store.
      6. Screen 6: Select the Document Store Directory.
        The default is /var/opt/sun/comms/davserver/db.
        Note
        You configure the document store as part of the Calendar Server post-configuration steps. See Configuring the Calendar Server Document Store for more information.
      7. Screen 7: Application Server Configuration Details.
        Type the following information:
        • Install Directory (default: /opt/SUNWappserver)
        • Domain Directory (default: /opt/SUNWappserver/domains/domain1)
        • Document Root Directory (default: /opt/SUNWappserver/domains/domain1/docroot)
        • Server Target Name (default: server)
        • Virtual Server Identifier (default: server)
        • Server Instance HTTP Port (default: 8080)
      8. Screen 8: Application Server: Administration Instance Details.
        Type the following information:
        • Administration Server Port (default: 4848)
        • Administrator User ID (default: admin)
        • Administrator Password
        • Secure Administration Server Instance (yes selected by default)
          This setting specifies if the specified administration server port is setup for HTTPS access.
      9. Screen 9: URI Path.
        The default URI path is /. You should use / (root) as the default context URI for deployment. The purpose of this recommendation is for better client compatibility and ease of client configuration. If the base URI is not /, users are more likely to have to use their advanced client configuration and type a long cumbersome URL versus just being able to enter a host name. Using / as the URI path replaces the GlassFish Server's main index.html, thus, the GlassFish welcome page is no longer displayed at http://host:port.
        Note
        For information about using a .well-known URI, such that access to / (root) or /.well-known/caldav/ is redirected to the /dav/principals/ URI, see Support for CalDAV and CardDAV Autodiscovery.
      10. Screen 10: User/Group Directory Server Details.
        Type the following information:
        • LDAP URL (default: ldap://hostname:389)
        • Bind DN (default: cn=Directory Manager)
        • Bind Password
          A pop-up message appears if you do not have the minimum required version of comm_dssetup installed. You must use at least comm_dssetup 6.4 version 1.04.
          A pop-up message also appears if you do not have the correct value entered for the Directory Server:
          Could not connect to LDAP server.  Error code 91. Connect Error.
          

          If this message appears, click Choose New.

          Note
          Use the LDAP URL that points to the non-SSL LDAP port. If you need SSL communication between Calendar Server and Directory Server, you can do so as a post-configuration step.
      11. Screen 11: DC Tree Suffix.
        The default value results from when you ran comms_dssetup.pl against the Directory Server.
      12. Screen 12: LDAP Unique ID attribute.
        Type the LDAP attribute whose value serves as the unique identifier for each calendar account in the calendar database. The default is nsuniqueid if you are installing Calendar Server 7 Update 2, but has changed to davUniqueId for Calendar Server 7 Update 3.
        Caution
        This attribute defines the unique value used as the database identifier for each account. This value is used internally to identify a user in other user's access control entries, subscription entries, and so on. The attribute chosen as the unique ID attribute must be present in all user, group, and resource LDAP entries for the deployment. Do not use the default value of nsuniqueid in a production deployment. See Changing User uuid for more information on choosing a production-ready value.
      13. Screen 13: Default Domain Name.
        Type the Domain Name for the LDAP users in the deployment.
      14. Screen 14: Organization DN for the Default Domain
        Type the organization DN under which all users and groups that belong to the default domain are located in the LDAP tree.
      15. Screen 15: Notification Mail Server Configuration Details.
        Type the following information:
        • Mail Server Host Name (default: hostname.domainname)
        • Mail Server Port Number (default: 25)
      16. Screen 16: Calendar Server Administrator.
        Type the user name (the default is calmaster) and the password.
        Notes
        • To enable SSL communication between Calendar Server and Directory Server, you can do so as a post-configuration step. See Oracle Communications Calendar Server Post Configuration for more information.
        • Currently, the default setting for the timezone (davcore.serverdefaults.tzid) is configured based on the tzid of the host where Calendar Server is deployed.
  3. Click Configure Now to configure Calendar Server.
    Up to now the screens have been gathering data needed for the configuration and performing some validity checking. You can go back and redo the configuration information at this point, or start the configuration.
  4. The Sequence Completed Screen appears.
    This screen provides a running update of all tasks if they have passed or failed. When the message "All Tasks Passed" is displayed, the configuration has finished. Check the specified log files for any error messages.
  5. Click Next when the configuration program completes.
    The Configuration Summary Screen appears.
  6. Click Details to view the details of the configuration log or Close to exit the configuration program.
  7. In GlassFish Server, enable Connection Validation for the connection pools (both CalDav back-end and iSchedule pools) to enable Calendar Server to automatically reconnect to the back-end database if it goes down.
    1. In the Admin Console, choose Resources, then JDBC, then Connection Pools.
    2. Select the pool.
    3. Check the Required box for Connection Validation.
    4. Choose table for the Validation Method.
    5. Type DUAL for Table Name.
    6. Click Save.
    7. Click the Advanced tab.
    8. Type 60 for Validate Atmost Once.
    9. Click Save.
      This configuration then issues the command "select count(*) from DUAL;" on every connection, at most one time every 60 seconds. (If the connection is not being used, it is not checked.)
      Note

      Use these settings as a starting point and adjust where necessary. For example, if validation is not important, you can turn it off. Additionally, you might want to adjust the "Validate At Most Once" time duration or validate each time a connection is requested (by setting the value to 0). HA deployments might also use different values.

  8. Restart GlassFish Server, for example:
  9. Return to the Installation Scenario - Oracle Communications Calendar Server to verify the installation.
Labels:
caldavserver caldavserver Delete
configuring configuring Delete
guide guide Delete
cs73 cs73 Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.