More on Installing a Comms 5 Calendar Server 6.3 Deployment (Front End and Back End)

Update, 4/9/07:

A co-worker has correctly pointed out in the comments that I have this not quite right. It is the configurator.sh script itself that is causing the problem. You do not have the option while running the script to choose between IP address and hostname. The script basically choose the IP address rather than the hostname. But again, the fix is afterwards to manually update the ics.conf file for the parameter mentioned below.

- Factotum Management

4/6/07:

As I mentioned in a previous post this week, there's a Calendar Server 6.3 install issue that I want to make folks aware of.

When you use the configurator.sh script to configure your Calendar Server front end, in a front end/back end deployment, as described here, your are supposed to use a fully qualified domain name for the back-end host the front end is pointing to that you will use DWP to commmunicate with. If by mistake you put in an IP address of the host instead, which evidently the script lets you do, the configuration will not work. And then you'll have to manually go back and enter the FQDN of the host instead of the IP address for caldb.dwp.server.backend.ip in the ics.conf file.

And yes, we do have a bug (CR) filed for this.

Comments:

Correction: The bug is with the configuration script internals. There is nothing the user can do to input the wrong information in the script. The script never asks for either the host name or IP address for the back-end server. To fix the problem, the configuration file can be edited manually after the configuration script completes. The configuration file is a text file found in the /config directory. The file name is ics.conf.

The parameter that needs to be fixed is the following: caldb.dwp.server.hostname.ip

Where "hostname" is the fully qualified name of the host server. Thus, in your own ics.conf file, if your back-end host fully qualified host name is "backend.sesta.com", then the parameter should look like the following: caldb.dwp.server.backend.sesta.com.ip = "backend.sesta.com"

This is a simple workaround and to my knowledge there is no hot fix being planned.

Posted by Bonnie Quigg on April 09, 2007 at 11:11 AM MDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Reporting about Unified Communications Suite Documentation, including news, Comms 101, documentation updates, and tips and tricks.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today