Group Calendar Group Calendar... · 2018-08-28 · allows for almost real time updates of the group...

© IntraVision ApS, 1997-2013 Revision: 001 318-02-2013 OnTime Group Calendar version 3.1

Group Calendar

Installation Manual Revision 1 OnTime® Group Calendar version 3.1

GROUP CALENDAR

Installation Manual Page 1

OnTime® Group Calendar Version 3.1

Installation Manual The main audience for this manual is Lotus Notes/Domino Administrators and users who have experience in administrating Lotus Notes databases. It is therefore expected that the reader of this manual is no stranger to the Domino environment and know how to configure server documents using the Domino Administrator client. The manual follows these font conventions:

• Bold – Group names • Underlined bold (Hyperlinked) – Section/chapter • [Bold in brackets] – Functions, buttons

• Italic – Information, Field • [Italic in brackets] – Checkboxes, access rights

Table of contents:

About OnTime® Group Calendar ...................................................................................................... 3

GC Topology ................................................................................................................................. 3

System requirements ......................................................................................................................... 5

Before installing GC .......................................................................................................................... 6

Installing GC ..................................................................................................................................... 7

Single GC Server installation ............................................................................................................. 8

Multiple GC Server installation ........................................................................................................ 11

Configuring GC ............................................................................................................................... 12

Adding users ................................................................................................................................ 12

Selecting users by Names/Groups/Hierarchy............................................................................. 12

Selecting users by Mail Server .................................................................................................. 12

Display Name of Users.............................................................................................................. 12

Base options ................................................................................................................................ 12

Directory of templates ............................................................................................................... 12

Keep/sync back......................................................................................................................... 13

Advanced Options ........................................................................................................................ 13

Schedule Information Only ........................................................................................................ 13

Disable ACLs ............................................................................................................................ 13

Encrypt Texts ............................................................................................................................ 13

Discovery .................................................................................................................................. 13

Business card photo source ...................................................................................................... 14

Users information ......................................................................................................................... 14

Legends ....................................................................................................................................... 14

User Categories ........................................................................................................................ 16

Access Control through Roles and Delegation profile ....................................................................... 18

GROUP CALENDAR


Granting access using calendar preferences in the personal calendar........................................... 19

Granting access using GC Roles .............................................................................................. 19

Display Groups ............................................................................................................................. 21

Static Groups ............................................................................................................................ 21

Dynamic Groups ....................................................................................................................... 22

Application.................................................................................................................................... 23

Default Settings......................................................................................................................... 23

Setting up GC Broadcast ................................................................................................................. 24

Creating Broadcast calendar entries ............................................................................................. 24

Collections.................................................................................................................................... 25

Installing the Notes calendar interface ............................................................................................. 26

Hosting the widget descriptor in a widget catalogue ...................................................................... 26

Hosting the update site on your network ....................................................................................... 26

Modifying the widget descriptor ................................................................................................. 27

Installing from widget on hard drive ............................................................................................... 27

Manually installing from widget catalogue ..................................................................................... 28

Installing from a widget catalogue using Lotus Domino policies ..................................................... 29

Uninstalling................................................................................................................................... 29

Uninstall after using drag’n’drop ................................................................................................ 29

Uninstall after using a widget catalogue ..................................................................................... 30

Enabling the “MyWidgets” sidebar panel ....................................................................................... 30

Troubleshooting ............................................................................................................................ 31

Enabling Logging ...................................................................................................................... 31

Disabling logging....................................................................................................................... 31

Enabling line numbers in trace logs ........................................................................................... 31

Setting up Discovery ....................................................................................................................... 32

Installing GC Web ........................................................................................................................... 33

Installation procedure ................................................................................................................... 33

Enabling GC Web as a widget in iNotes ....................................................................................... 33

Installing GC Mobile ........................................................................................................................ 35

Installation procedure ................................................................................................................... 35

Access the application from your device ....................................................................................... 35

Upgrading from previous versions of GC ......................................................................................... 36

Appendix A – ACL setup .................................................................................................................. 38

Appendix B – Console commands .................................................................................................... 40

Loading GC from a different path ................................................................................................. 40

Appendix C - Installation on Linux platforms ..................................................................................... 41

Support ............................................................................................................................................ 42

GROUP CALENDAR


About OnTime® Group Calendar OnTime® Group Calendar (hereafter GC) provides your organization with an overview of where people are, what they are doing right now and what they will be doing in the future. Further, GC provides you with a rich graphical interface, simple access and unmatched server compatibility. GC is configured and administrated through a set of Lotus Notes databases and a server task that allows for almost real time updates of the group calendar when a user, creates, updates or deletes a calendar entry in the personal Lotus Notes calendar. The OnTime® databases all need to have the ACL´s properly configured for the GC solution to work. (For more information about the ACL please refer to Appendix A – ACL setup)

GC Topology The diagram below shows the overall topology of the GC

GROUP CALENDAR


The table below lists the GC databases and their individual purpose in the overall solution.

OnTime® Group Calendar*

This is the central GC configuration database. In This database the administrator must configure:

Global settings

Server settings

Delegation of rights through roles

Specify display groups

Control and specify legends

Specify the default application settings This database is only used by administrators.

OnTime® API

The API database is an application which prevents the Calendar Configuration from overloading due to large dataflow.

OnTime® Log

This database is used to keep track of any errors and for performance measuring.

OnTime® Broadcast

OnTime® Broadcast is a calendar database from which you can broadcast (push) events and holidays to some or all employees’ calendars. This database is typically used by administration staff (receptionists and secretaries).

OnTime® Web

The Web database is used for configuring settings for accessing the GC database via the HTTP task. This database is also used for installation GC Mobile. Please refer to Installing GC Web.

OnTime® Time-off

This database is used for keeping a record and statistics of users’ time off. Through this database the users fill out a time off request and send it to a selected approver. When the Time Off request is approved, the time off is automatically send to the user’s personal calendar and from there, synchronized into the time off view in the OnTime Group Calendar.

*) The database also serves as the Discovery launcher for users who have been assigned the Discovery role in the ACL. For more information on this subject please refer to Appendix A – ACL setup.

GROUP CALENDAR


System requirements Lotus Domino 7.x servers or later are required to run GC. To run GC the central Lotus Domino server(s) running OnTime® Group Calendar and synchronising with mail servers must be running on IBM Lotus supported versions of Microsoft Windows operating systems. Although the central OnTime® server must run on a Microsoft Windows operative system, OnTime can easily collect and synchronise data from other Operative Systems supported by Lotus Domino. In the table below are the requirements for the various calendar user interfaces. GC does not support older versions of Lotus Notes than listed.

Notes 7.x

Notes 8.0.x Basic

Notes 8.0.x Standard

Notes 8.5.x Basic

Notes 8.5.x Standard

Notes √

Discovery √ √ √ √ √

Web – Supported internet browsers

Internet explorer Mozilla Firefox Google Chrome Safari (For Mac and Windows)

7.0 or later 3.6 or later 11.0 or later 5.0 or later

Mobile requires the following

A Smartphone with multi-touch gestures.

Enabling of JavaScript.

Enabling of cookies.

320 x 480 pixels, (approx. Standard IPhone3G size).

Notes 8 (Standard Configuration) is a culmination of new goals, and new technologies to support those goals; it makes use of the Java-based Eclipse technology to enhance existing Notes functionality (mail, calendar, contacts, etc.) and provides new features such as sidebars, etc. Eclipse architecture allows the integration of other applications, such as Productivity Tools and Composite Applications, into Notes. The GC – Notes client takes full advantage of this advanced platform. Notes 8 (Basic Configuration) is very similar in experience to the Notes 7 client. It is available for cases in which the client machine's memory is too low to run the standard configuration. As in previous releases of Notes, clients running the basic configuration can access only applications that reside on Domino servers, and can use only the 3.x implementation of embedded Lotus Sametime Contacts.

GROUP CALENDAR


Before installing GC Please make sure that you have received all of the files listed below before starting your installation process.

Template files:

ontimegc.ntf GC Configuration template file

ontimegcapi.ntf API template file

ontimegclog.ntf Log template file

ontimegcbroadcast.ntf Broadcast template file (Not required to run OnTime® Group Calendar )

ontimegcweb.ntf Web and mobile configuration database, template file (Not required to run

OnTime® Group Calendar )ontimegctimeoff.ntf Time Off template file

Calendar clients:

Widget Installer (HTTP) - OnTime Group Calendar .xml (OnTime Notes calendar interface)

Updatesite_Notes2011_x.y.z.zip

A required license key for GC can be obtained from your preferred OnTime® business partner. A list of OnTime® Business partners is available at www.ontimesuite.com Below are the steps you will need to complete in order to properly install GC. The server must have at least Editor Access to all users’ mail files and must be allowed to run “Unrestricted methods & operations” on the server. This is configured through the server document in the Directory (names.nsf). Also, when GC is configured to synchronize data from other mail servers, the GC server must be trusted by these miscellaneous mail servers, which are to be synchronised.

Before installing GC it’s recommended that you plan the assignment of roles and rights to view calendar information or create calendar appointments on behalf of other people very carefully. The assignments that you make can of course be changed at a later stage but you will benefit from reading Access Control through Roles and Delegation profile before you start installing.

GROUP CALENDAR


Installing GC GC is a very flexible solution which can be installed and deployed in a number of different scenarios ranging from a single OnTime® Group Calendar server installation (hereafter GC Server) to an environment with multiple GC Servers. Please select the scenario that best fits your organisations requirements and follow the described installation procedure. Definition of a GC Server: These are server(s) where GC is installed on. These server(s) can be any type of Lotus Domino server(s) within the domain running the appropriate version of Lotus Domino and Microsoft Windows as specified above. The mail servers which OnTime® collects it´s data from can be running any of the operating systems Lotus Domino supports.

Multiple GC Server installation

Installation on multiple replicated GC Servers each pulling calendar data from one or many mail servers. To install please go through step 1 to 4

Server Server Server


USA Europe

Domain

Single GC Server installation

Installation of GC on one server – pulling calendar data from one or many mail servers. To install please go through step 1 to 7

Server Server

Server

Domain

GROUP CALENDAR


Single GC Server installation

1. Templates

The first step of the process is to: Copy the template files to the Domino Data Directory: - ontimegc.ntf - Template for the Configuration database - ontimegcapi.ntf - Template for the API database - ontimegclog.ntf - Template for the Log database - ontimegcbroadcast.ntf - Template for the Broadcast database - ontimegntimegcweb.ntf - Template for the web and mobile database

ontimegctimeoff.ntf - Template for the time off database

We recommend that you place your template files in an ‘OnTime’ folder under the Domino data directory. If you choose another location, remember to edit the template path later, in your [Global Configuration] document.

2. Sign templates

After copying the templates to the data directory, sign the templates using an appropriate ID. It is recommended that it is the server’s ID that signs the OnTime® GC templates.

3. Create the OnTime® Group Calendar database

Create the Group Calendar database. Use the ontimegc.ntf as template for this database. The template title is ”NTF: OnTime® Group Calendar ver. #.#.#” (Where # is the current version number). [Inherit future design changes] is checked as default. This should be unchecked. ACL: Please refer to Appendix A – ACL Setup.

4. License key

GC needs a license key to run the server task and synchronise calendar appointments. The license key for GC is sent to you by your preferred OnTime® Partner when you purchase the product or you can use the temporary trial key which you received if you downloaded a trial version. The trial version is a full version only the license key is time limited.

Single GC Server installation Installation of GC on one server – pulling calendar data from one or many mail servers.

Server Server

Server

Domain

GROUP CALENDAR


Select “Enter License Key” from the Actions menu or click the key icon, both in the GC configuration database.

The license key includes the name of your server’s certifier and can only be used on servers registered with this certifier. The license key also contains information about the number of users that have been licensed. If the number of users in the OnTime® GC configuration exceeds the licensed number of users, rooms and resources, the GC server task will stop synchronising.

5. Create a Global Configuration document

Open the [Global Settings] view in the GC database. When the Global Settings is opened for

the first time, a Global Configuration document is created automatically. - In the field “Members” all users on your server(s) are included by default. This topic will be

described in depth later in this manual.

- Specify the directory where you have placed your GC templates

- Click [Save & Close] to save the document. Note: This step is important for later synchronisation even if no changes are made.

6. Create Server Settings

Open the [Server Settings] view in the GC database and add a server settings document:

- Click the [Add Server] button and enter the synchronisation server

- Specify which server(s) you want GC to monitor and retrieve calendar data from.

Remember to include the OnTime® GC server on this list if it contains mail files that shall

be part of the GC installation.

...or by a click on the key.

GROUP CALENDAR


- Specify the file path for the GC API database in the ‘API database’ file path field.

- If desired, specify the file path for GC Broadcast. By default the below example is entered.

- The GC log file is necessary should you need to troubleshoot in GC. Please be aware that the log file may take up a lot of disk space, depending on your environment and is not necessary for OnTime® to operate. Choose whether to log or not and if logging is enabled, specify the location of the log database.

- Click [Save & Close] to save the document. Before the document is closed you will be

asked whether to create the OnTime® API database, the OnTime® Broadcast database and the OnTime® Log database (if you have chosen to log to database. Click [Yes]. The

databases will then be created automatically in the directories you have specified.

7. Install/Update task

- Load the server task by clicking the [Install/Update Task] button in the upper right corner

within the Server Settings document which you have just created. o When the task is installed it appends the server task to the notes.ini file.

Note: The [Install/Update Task] feature only supports Microsoft Windows Operative Systems. Please refer to Appendix C - Installation on Linux platforms if you are

running on Linux OS.

8. Run server task commands

When the server task has successfully installed please be sure to run following commands, to apply users and initial settings: From the [Server Settings] view click the [OnTimeGC Commands] button and run the [Admin] command and thereafter the [FullSync] command.

Note: The [FullSync] command can take up to several minutes depending on how many

users are in your environment and how many documents are to be included.

GROUP CALENDAR


Multiple GC Server installation

1. Additional GC Servers

Repeat step 6 for Single GC Server installation for each additional GC Server you want to

add.

2. Replication

Replicate the GC database to the synchronisation server(s)

3. Install/Update task on additional servers

- Load the server task by clicking the [Install/Update Task] button in the upper right corner

to get the task running on the other GC servers. o When the task is installed it appends the server task to the notes.ini file.

Note: The [Install/Update Task] feature only supports Microsoft Windows Operatiing Systems. Please refer to Appendix C - Installation on Linux platforms if you are

running on Linux OS.

4. Run server task commands

When the server task has successfully installed please be sure to run following commands, to apply users and initial settings: From the [Server Settings] view click the [OnTimeGC Commands] button and run the [Admin] command and thereafter the [FullSync] command.

Note: The [FullSync] command can take up to several minutes depending on how many

users are in your environment and how many documents are to be included.

Multiple GC server installation

Installation on multiple replicated GC Servers each pulling calendar data from one or many mail servers.



USA Europe

Domain

GROUP CALENDAR


Configuring GC All configurations are done from the Group Calendar database. To immediately apply any changes that have been made please run the action [OnTimeGC Commands] [Admin] from the [Server Settings] view.

Note: The [OnTimeGC.Admin] task is scheduled to run every hour, it is therefore not necessary to

manually run the task command.

Adding users To add users open the [Global Settings] document.

Selecting users by Names/Groups/Hierarchy

When adding users by Names/Groups/Hierarchy you have the options to either import all users in your domain by typing asterisk (*) or by entering single users, Lotus Domino Directory groups or hierarchical structures such as */France/Acme in the Members field.

It is also possible to exclude certain users/groups if i.e. your Lotus Domino Directory groups are not a 100% match to the users you would like to add to the group calendar.

Selecting users by Mail Server

When adding users by Mail Server all users from the specified servers are included in the GC . Please note that you lose the option to exclude certain users or groups when adding all the users from an entire Mail Server.

Display Name of Users

In the different calendar interfaces of GC Persons and Resources can be displayed in different ways. The displaying of users’ names is set to the company’s preference. This can be specified in the Display Name of Users section. Note: Formulas are based on the document in the Domino Directory.

Base options

Directory of templates

Specify the directory where you have placed your GC templates. By default the entry is “ontime”, which is the recommended directory for the OnTime® templates.

Specify which

servers you want to

import users from

GROUP CALENDAR


Keep/sync back

On the global configuration document it is possible to set how many days GC should keep calendar activities. This means that GC stores and synchronises appointments for the specified number of days in the past. This also means that appointments in the specified time frame are synchronised. If a user edits a calendar activity in the past and the appointment is within that time frame, the appointment will be synchronised into GC with the changes. GC includes and shows all future appointments 10 years ahead in calendars for users who are configured for the OnTime® Group Calendar. Mark as Formulas

Mark as formulas provides additional privacy settings by allowing administrators to hide like details from people who aren’t invited to a meeting or appointment. An example would be that you could hide personal details in an email´s subject, so that you still would see the email, but the details would be blank.

Advanced Options

Schedule Information Only

When employees create calendar activities in their own calendar, they have the option to mark the activity as a private appointment.

Disable ACLs

The option to disable ACL’s provides GC the possibility to override ACL’s on individual mail databases. Disabling any ACL on mail databases optimizes the use of the GC role system. Note: Refer to section Granting access using calendar preferences in the personal calendar.

Encrypt Texts

In environments where some calendar entries may contain classified information, it is possible to let GC encrypt all text data in its internal database structure, to prohibit unauthorised users to gain access to the data. Enable encryption has a negative influence on overall performance; therefore this feature should only be enabled in scenarios where security is of critical importance.

Discovery

GROUP CALENDAR


Typically, Discovery will detach itself to the Notes Data directory. This may not be preferred in some environments (such as Citrix installations). The [Launch Only (No detach)] function will launch the application specified in the Filepath field. The GC administrator must ensure that the file exists and is available.

Business card photo source

When GC displays the employees’ calendar activities, it can also display the persons’ photo with other useful information, simultaneously. The photos displayed come from a Business card photo source. The business card photo source is a Domino database which holds the individual employee’s photos. It can be any type of employee database or it can be the servers native Domino Directory (names.nsf). Photos can be loaded and showed with other useful information when GC shows employees calendar activities. In the example below we use servers’ directory, but it can be any Lotus Notes database. ($Users) is the view in the database where information can be found.

When a co-worker, or a co-worker’s activity, is marked in Notes, the person’s information will appear at the bottom left side of the OnTime® Notes client. The person’s photo is loaded from the database specified above. The rest of the information is retrieved from the person document in the Domino Directory. Supported image file formats are .jpg, .gif (non animated) and .bmp either attached or inline.

Users information A user document is used to review a person’s information in a resume. By disabling a user, you will deactivate that user’s license and that license will now be available for another user.

Legends Each type of calendar entry can have its own category, icon, and bar colour in the group calendar interfaces. This feature provides the user of the calendar interfaces with a better overview of colleagues’ appointments and an ability to visually filter by type. When a user creates a new calendar entry, the user also selects a category for the entry. Depending on the

Server: If the field is not filled, GC chooses the

specified database on the server where GC is installed. This field can point to any server in

the domain.

Filepath: Is the servers’ directory in the

example, but can be any database. View: ($Users) is the view in the database

where information is retrieved from.

Key: The definition of how users should be

looked up in ($Users) Field: Indication of the field which contains

the picture.

Indication of a user

who has been disabled

in GC

Indication of a user

who has been deleted

in GC

To enable or disable users, mark

one or more and click [Select] then Enable or Disable

GROUP CALENDAR


selected category the calendar entry is displayed in the group calendar with the associated colour for the time bar.

When creating new legends in GC, there are a few steps to consider. Please refer to the following images.

The [Language] field contains the values which are set on the legends, in the calendar interfaces, depending on language the user has selected in the client. When customizing a Legend Configuration the format of different languages should look as following:

en: English text

da: Danish text

Background & Foreground: Here colors are

set for the appointments. Background: The color of the appointment bar.

Foreground: The color of the text in the bar.

Time Off: Appointments will be

shown in the Time Off view in Discovery and Notes.

Legend Name: A descriptive name, which will be shown in

the calendar views.

“ID” represents the current

Legend number. This is the third Legend created, ie (ID:

3).

Click [Add Legend]

to create a new one

These numbers define Legends priority

GROUP CALENDAR


de: German text

se: Swedish text If the users selected language is not in the list the Legend name will be used instead. When the new legend has been created, you can add one or more item(s). The item(s) are the recognition parameter for how a given calendar activity should be recognised in the miscellaneous group calendar interfaces.

The priority field is used to determine what legend color is the one to display, when multiple of the Legend Item configurations are in play. I.e. a user chooses to set a category on his calendar activity. This user also chooses to use a Character in his subject. Here is when the priority will determine which of the possible legends will be shown in the calendar interfaces. The priority field will also solve conflicts in cases where a user has set two different categories in his calendar activity. As mentioned before. By enabling Confidential the subject and those who are invited will be hidden from public view. The meeting will display as a blank meeting without any subject or invitees. Even selected invitees won’t be able to see the subject or any other people who is invited. This goes for the creator of the meeting as well. Note: Changes of Legend Items requires a run of the [FullSync] command.

User Categories

By default, custom categories are not listed in the end users’ private calendar when creating the various calendar entries. The User Categories feature provides the advantage of applying the different categories to users’ calendar where they will be ready to be utilized.

Char: Char is short for ‘character’. A character can be a symbol (I.e. #, ! or ?) or simply a letter. The

character is written in front of the subject in the

subject field in the calendar activity.

“?My Personal” or “? My Personal”

Category: A category can be added to a calendar

activity. If you create a category which is not in the

users’ calendars this should be considered as well.

Formula: A formula automatically calculates

how a given calendar activity should be processed and shown by a group calendar

interface. A formula can look as following: OrgConfidential=”1” & BookFreeTime=”1”

GROUP CALENDAR


Note: To remove an unwanted category it must be listed in the Remove field. It is therefore not

enough to delete the category from the Add field, once it has been applied.

Click [Edit Users Categories] to

add or remove categories from users’ calendars.

GROUP CALENDAR


Access Control through Roles and Delegation profile Almost all organisations need to differentiate the access level to group calendars. In most cases only a few users will be allowed access to all details for everybody’s calendar entries. GC grants access to calendar entries in three levels:

Access level Description

View schedule information

View schedule information is the lowest level of access to calendar entries a user can be granted. The equivalent for the user is the dialog a user sees when inviting somebody to a meeting from the personal calendar.

Users, in the standard configuration, can see whether the individuals are busy but not the subject of the meeting or any other details.

Read entries details This level allows users access to all details of a calendar entry. Private appointments still have all information hidden by default.

Create, Edit and Delete entries

This level allows users to Read, Create and Delete entries for the people that the users have been grated this access for. Private appointments still have all information hidden by default.

GC determines the individual user’s access to the entries in the group calendar based on a highly flexible model of combining:

Rights granted to individual users from delegation access in the personal calendars(ACL)

Roles defined in the Group Calendar configuration database. The rights of the GC user are cumulative and as such will grant the highest access level that one of the two methods allows for.

GROUP CALENDAR


Granting access using calendar preferences in the personal calendar Below is a list of how access rights granted by an individual user maps into GC.

Access level Access and Delegation level from the personal calendar

View schedule information Please note that delegation from the “Access To Your Schedule” tab in the personal calendar preferences is not supported by GC as this is not a true access control settings.

Read entries details Read any document

Read any Calendar Entry, To Do or Contact

Read/create any document, delete documents they create, send mail on your behalf


Read and create any document, send mail on your behalf

Read, edit, create, delete any document, send mail, enable Out-of-Office

Read, edit, create any document, send mail, enable Out-of-Office

Read, create, edit and delete any Calendar Entry, To Do or Contact

Performance hint: If your organisations do not

actively use assignment of access delegation from the personal calendar preferences the collection and maintenance of these access rights can be disabled in the “Global Settings” in the GC configuration database.

Granting access using GC Roles

GC Roles represents a set of system administrator configured access rights to calendar entries. These rights can be granted to a combination:

Lotus Domino Directory users

Lotus Domino Directory groups

A hierarchical name structure such as */Sales/Acme To allow for the greatest possible flexibility when defining the members of the role it is possible to use Lotus Domino Directory groups and then exclude specific users who will not be allowed this role. The exclude function is particularly helpful if you want to grant access to almost every user in a Lotus Domino Directory group or a hierarchical structure. By using the Lotus Domino Directory groups or a hierarchical structure to define access the GC will normally result in a minimal need for maintenance as users join or leave the organisation.

GROUP CALENDAR


To create a new role you need to:

1. Assign a name to the Role. 2. Specify the members of the group. This can both be Domino Directory users and/or groups, or

users by hierarchy. 3. Define which personal calendars this role should grant access to and at what level.

An example of a set of roles

Roles (Members)

Rights

All

(*) Board of Directors

(Lars) Receptionist

(Amanda) IT DK

(IT User) Sales DK

(Sales User)


* *

-Board of Directors IT DK Sales DK

Read entries

details * -Board of Directors

View schedule information

All in this example is a role which is used to grant everybody in the organisation the right to read

calendar entries for all users in the organisation The use of the asterisk (*) results in all users in the organisation being granted this access level. Remember that access levels are cumulative and therefore a user can be granted a higher access level from another role Lars is a Director in the company. Lars is in the role Board of Directors and All and can therefore

edit in all the employee’s calendars. Amanda Howard is a secretary and is a member of the roles Receptionist and All. She can edit everyone’s appointments except the ones for the Board of Directors. Through the Role All she has

read access to Board of Directors’ appointments. IT-User is a developer and in the group Sales DK and All. He can edit in the calendars for everyone who is a member of the Lotus Domino Directory group IT DK. Through the Role All he has read access to everyone’s, except Board of Directors’, appointments in the calendar interfaces.

Sales-User is a sales representative and in the roles Sales DK and All. He can read calendar

subjects for all users and edit access to appointments for employees who are members of the group Sales DK.

Top right: Gives the right, edit and delete appointments on behalf of the

specified users.

Medium right: Grants users the right to view detailed information about

other persons meetings and appointments.

Lowest right: Gives persons the possibility to view busy time, but are

not able to view any other details such as subject and participants.

GROUP CALENDAR


Display Groups Often, when viewing the full list of all users, the GC calendar interfaces present the user with an overwhelming amount of information. A group within the GC is in many ways considered as a fixed search or filter that presents calendar entries for a predefined set of users to the group calendar user. Groups are created and maintained from the [Display Groups] overview in the GC database.

Display Groups are available to all users of the GC system. The groups may however present different results to different GC users based on the access they have been granted to view calendar information. I.e. even though a GC user can use the Display Groups “Sales Worldwide” does not in any way mean that the user can see entries for all members of this Display Group. Display Groups do not control security they are merely used to segment groups into relevant business units.

Static Groups

When creating Static Display Groups it is possible to populate various groups statically, either by users individually or by utilizing Domino Directory groups.

The picture below illustrates the use of both groups and persons individually. This view shows a group which is created in GC, where Members are specified as a group from the Domino Directory. When the Admin task runs on the server, the Users field will be updated with the persons who are listed in the group in the Domino Directory. The maintenance of this group is done in the Domino Directory.

Limit to With the [Limit to] functionality GC administrators have the possibility to limit the visibility of the

created static groups to certain Domino Directory groups or specific persons. This is typically used in larger environments where one would reduce the visible noise to all of the users in the organization. Here we see a group which is created in GC, where persons are added into Members individually. Maintenance of this GC group has to be done via the GC database. When the OTGC.Admin task runs on the server, the Users field will be updated with the persons who are added in the Members field.

Click [Add Display Group]

to create a new group

In the example, a

Directory group has been excluded from

the GC group

Limit the visibility of the group to a

specific Directory group or user

GROUP CALENDAR


Dynamic Groups

When creating Dynamic Display Groups it is possible to populate various groups dynamically by utilizing the Domino Directory (names.nsf) or other lookup databases. By searching the desired lookup database, GC can create groups which are sorted from the desired columns, fields or by hierarchy. The groups which you create will be sorted depending on your Dynamic Group configuration.

This is the view from which you configure your Dynamic Group(s). The Subject field is merely the name of the Dynamic Group, to help distinguish between the various created groups, and not the actual display name of the group.

The function of the Category field is to easily create and identify any Dynamic Group names. Setting “Department / IT” will name the selected Dynamic Group “IT / Department”. The Dynamic Group will automatically create and populate groups depending on entries found in your desired lookup database. PS: It is strongly recommend to have the referred database on same server, for best performance.

Click [Add Display Group]

to create a new group

Enter the server name from

where you have stored your lookup database

Enter the name of

your lookup database

Choose which keyword to

search from in your lookup

database

Choose from which attribute you

wish to base your Dynamic groups

upon Enter the attribute from which you

wish to base your Dynamic

Group(s) upon

GROUP CALENDAR


Application

Default Settings

Default settings are used to specify how your group calendar will look when you launch it. You can specify which language is preferred in the group calendar interfaces as default. Each of these settings can be overruled by a user’s own specified settings. So if your organisation per default has set the language in the group calendar to be English (UK), but the user has set his user settings to be German, then the user settings will overrule the default settings. It is not possible for a user to be member of two different application settings. Consequently the first setting in the list will automatically be set as a default setting for that user. In such cases it would be advised to name the default settings with numbers to prioritise. Default settings can be set per application: Global: Global are default settings for every group calendar client and everything you set here will

impact all OnTime® group calendar interfaces. Notes: In Notes settings you can specify settings specific for the Notes client. Discovery: In Discovery settings you can specify settings specific for the Discovery client.

When creating a new Default Setting specify the following:

Click [Add Settings] to

create a new default setting

Specify the members of

the default setting

Specify if any users should be excluded from

the default settings

Language: The setting for which

language the calendar interfaces will load with

Region: This setting determines

which timezone the setting is located

Sametime: By enabling Sametime

awareness, users’ online status will be displayed in the miscellaneous

calendar interfaces

Altering the Line Height will determine

how many appointments will be shown with a subject in the view for

each member of the Group Calendar.

GROUP CALENDAR


Setting up GC Broadcast

The GC Broadcast calendar offers the ability to manage calendar entries centrally. The Broadcast

database is used to create calendar entries which are then synchronised to users’ personal calendar.

The main view of the Broadcast database displays which entries have been created on a selection of

dates.

Creating Broadcast calendar entries Calendar entries are created and administered from the calendar view of the Broadcast database.

Whichever button is selected, the entry can later be changed to another type in the broadcast entry document. Creating a broadcast entry is similar to creating an entry in the personal calendar, except for a few other requirements. These requirements include Members. When creating broadcast entries, it is recommended that broadcast administrators carefully consider who these entries will and should be applied to. In cases where broadcast entries are created for a large amount of people, broadcast administrators can benefit from Collections. For more information please refer to section Collections.

Specify the owner of the broadcast entry and

also others who have the right to edit if needed

If needed, specify which collection of people

should to receive the broadcast entry

Choose the entry type

Enter the subject of the entry

Choose the category of the entry

Members can be typed in manually or by GC groups, in this case the members of the entry is a Collection

Attachments can be added if needed

Click to create either

calendar entry

The [Filter] button gives you

the possibility to view entries

from certain selections

GROUP CALENDAR


Note: The Who field can also contain GC static/dynamic groups.

Collections Broadcast entries can be gathered in a group called a ”Collection”, which can help to ease the task of applying miscellaneous repetitive appointments, holidays or events in these users’ personal calendars. Collections are typically used for countries or workgroups, where to GC Broadcast administrators will apply the respective countries’ holidays or workgroups fixed events. Before creating a new Collection, GC administrators should consider if it is created for a workgroup or a country.

Broadcast collections can only contain people whom have been synchronised with GC. Broadcast administrators will therefore benefit from static and/or dynamic display groups created in GC, prior to creating Collections in the GC Broadcast database. In case the Collection is created for a county-group it is possible to remove the users’ imported holidays from the Domino Directory. When creating a new Collection specify the following:

Note: The Collection Name is only used to identify the Collection and is therefore not displayed in the

GC calendar interface(s).

Specify the name of

the Collection

Specify the members of the Collection. In this case

it is a mix of groups and individual persons

Specify whether to remove all

(*) or some imported holidays

from the Domino directory

Information: A list of dates which have been broadcasted

to the Collection

GROUP CALENDAR


Installing OnTime GC Notes client / TAAG The Notes calendar interface is a Java plugin based interface for the IBM Lotus Notes 8.5+ Standard client and is installed from an update site using a widget descriptor file. Think of an update site as an installation source (e.g. a CD or DVD) and the widget descriptor file as describing what to install from the installation source. The update site used may be that provided on the OnTime® server or a server on your network and is pointed to in the widget descriptor file. The widget descriptor file supplied in the install kit points to the OnTime® server and it follows from this that you need to modify the supplied widget descriptor file if you choose to host the update site on your own network. See the section below on hosting the update site on your own network for information on how to modify the widget descriptor file. Please note: We recommend that you always host the update site on your own network to avoid

network connectivity/firewall issues but for smaller deployments (less than 50 clients) you may choose to install from the OnTime® update site. Hosting the update site locally on your own network also affords you greater control when deploying the Notes calendar interface.

Hosting the widget descriptor in a widget catalogue The widget descriptor may either be kept on a hard drive, network share or hosted in a widget catalogue. You may choose to reuse an existing widget catalogue or create a new one for th purpose. For more information on how to create a widget catalogue database please refer to the Domino Administrator Help database. Once you have the database follow the steps below: 1. Open the widget catalogue database. 2. Click the [Add Widget to Catalogue] view action button.

3. Fill in the form: 1. Title: OnTime Group Calendar – Notes 2. Category: OnTime Group Calendar 3. Description: OnTime Group Calendar – Notes calendar interface 4. Click the [Attach...] button and select the widget descriptor file you wish to us

4. Click [Save & Close].

Hosting the update site on your network When choosing to host the update site locally you need to import the client code into an update site and then modify the supplied widget descriptor file to point to your update site. An update site is most easily created using the template supplied with the IBM Lotus Domino server. The template is called “Eclipse Update Site” and is an advanced template. For step-by-step instructions on how to create an update site database please refer to the “Creating and using an NSF-based update site” topic in the Lotus Domino Administration help (Notes Client Installation and Upgrade/Managing client plug-in deployment/Creating and using a NSF-based update site). Note: You may also choose to reuse an existing update site database.

You may have clients download the client from the update site using HTTP or the NRPC (Notes) protocol. Before proceeding decide on the protocol to use. If the server hosting the update site doesn’t have the HTTP task running choose NRPC. Once you have an update site database follow the below steps to import the plug-in supplied in the install kit into the update site:

1. Open the update site database in the Notes client. 2. Click [Import Local Update Site...] action.

GROUP CALENDAR


a. Click [Browse...] and choose the folder for which contains Notes

b. Browse to the location you noted above and select the site.xml. c. Click [OK] to complete the import.

3. Selection [Actions/Show URLs...]

a. Note the URL (or click the “Copy” button to copy to the clipboard) containing the address for the protocol you have decided to use for use in the widget descriptor.

Modifying the widget descriptor

In the Notes-directory of the supplied install kit you will find the widget descriptor. It’s called “” and is an XML file. To edit it you simply open it in your preferred text editor. When you open it the top of the file will look like the screenshot below. The URL-attribute highlighted in the screenshot points to the update site used. As you can see from the screenshot it points to the update site hosted on the OnTime® server. To change the installation source simply change the attribute to the value for your update site. See the section above on information on how to obtain this information.

Once you have edited the file save and close the file.

Installing from widget on hard drive Follow the steps below to install:

1. Locate the widget descriptor you want to use 2. Open the MyWidgets sidebar panel (if not visible refer to the section below on enabling the

MyWidgets sidebar panel)

3. Drag the widget descriptor to the MyWidgets sidebar panel to install the widget.

4. Your Notes client will now install the Notes calendar interface.

GROUP CALENDAR


5. When asked to restart the Notes client click [Restart Now]

6. When Notes has restarted you should see a shortcut to start the Notes calendar interface in

the [Open]-menu of your Notes client.

Manually installing from widget catalogue Decide on the widget catalogue database you want to use. If you do not have a widget catalogue database you need to create one. For more information on creating a widget catalogue refer to the Lotus Domino Administrator help in the “Deploying client plug-ins with widgets and the widget catalogue” topic. For information on how to import the widget descriptor into the widget catalogue see the “Hosting the widget descriptor in a widget catalogue” section. To install from a widget catalogue follow the steps blow:

1. Open your Notes client 2. Open the preferences (File/Preferences…) and switch to the Widgets-section 3. Fill in the fields as specified below

a. In the “Catalogue server” field specify server name of the Domino Server hosting the widget catalogue (e.g. Server1/Example)

b. In the “Catalogue name” field specify the path to the widget catalogue database (e.g. “notes2011_widgetcatalogue.nsf”)

4. Click [Apply] (Notes will now create a local replica of the widget catalogue on the local

workstation) and show a list of the widget categories available in the widget catalogue

5. Select the category you would like to install. In this example I choose the Notes category as

that's the name of category where I placed the Notes widget. 6. Click [OK] to install the selected components

7. Your Notes client will now start installing Notes.

GROUP CALENDAR


8. When asked to restart the Notes client click “Restart Now”

9. When Notes has restarted you should see a shortcut to start the Notes calendar interface in the “Open”-menu of your Notes client.

Installing from a widget catalogue using Lotus Domino policies Automatic provisioning of the Notes calendar interface is possible using Lotus Domino policies. A full description on how to do this is beyond the scope of this document but a high level description is provided below. To perform provisioning using Lotus Domino policies you need:

1. An update site (this may be the OnTime® server). 2. A widget catalogue with the widget descriptor and you should know the category name of the

category holding the widget in the widget catalogue. 3. A Lotus Domino policy and a Desktop settings document

Installation using policies is done by creating or editing the Desktop settings document for the users that should have the Notes calendar interface installed and on the “Widgets” tab specifying the server and path of the update site and the category name to install.

Uninstalling The steps for uninstalling are different depending on whether you installed OnTime® Notes as a widget by drag’n’drop or from a widget catalogue.

Uninstall after using drag’n’drop

Follow the below steps to uninstall Notes:

1. Open your Notes client. 2. Open the My Widgets sidebar panel. Select the icon representing the installed Notes

component. 3. Right-click the selection and choose [Remove Component and Actions].

GROUP CALENDAR


4. When asked if you want to remove the selected items answer [Yes].

5. Restart your Notes client to complete the operation.

Uninstall after using a widget catalogue

Follow the below steps to uninstall Notes: 1. Open your Notes client. 2. Open the preferences (File/Preferences…). 3. Switch to the “Widgets” preference page. 4. Uncheck the category holding the Notes calendar interface previously selected and click [OK].

5. After uninstalling the components restart Notes.

Enabling the “MyWidgets” sidebar panel To install the Notes calendar interface using drag’n’drop you need to have the “MyWidgets” sidebar panel visible. Follow the below steps to enable it:

1. Open your Notes client 2. Open the preferences (File/Preferences…) and switch to the “Widgets”-section

3. Make sure the “Show Widget Toolbar and the My Widgets Sidebar panel” is checked

4. Click [Apply] 5. Click [Close] to close the dialog box

6. Make sure you see the My Widgets sidebar plug-in in your sidebar Note: You may be restricted from enabling the MyWidgets functionality in a Lotus Domino policy.

GROUP CALENDAR


Troubleshooting To help troubleshoot or diagnose a problem you may be instructed to enable logging and/or enable line numbers in trace logs by OnTime® support.

Enabling Logging

Enabling logging is done on a client-by-client basis. Please note: If running IBM Lotus Notes on Microsoft Windows Vista or Microsoft Windows 7 you

need to do the below procedure as Administrator. To enable logging follow the below steps:

1. Make sure the Notes client is not running. 2. Locate the Notes data directory on the client machine e.g. c:\Program

Files\IBM\Lotus\Notes\Data 3. Open the workspace\.config directory 4. Edit the rcpinstall.properties file in an editor such as Notepad 5. At the bottom of the file add the following lines:

com.ontimesuite.gc2011.level=FINEST com.ontimesuite.sametime.level=FINEST

6. Save and close the file 7. Launch the Notes client and reproduce the issue

Go to the “Help/Support/View Trace” menu item and copy/paste the contents of the dialog box that appears. This is the support trace log. Please note: Logging may severely impact the client performance so it’s recommended only to enable logging if instructed to do so by support.

Disabling logging

To disable logging follow the below steps: 1. Make sure the Notes client is not running. 2. Locate the Notes data directory on the client machine e.g. c:\Program

Files\IBM\Lotus\Notes\Data 3. Open the workspace\.config directory 4. Edit the rcpinstall.properties file in an editor such as Notepad 5. Locate the below lines and delete them from the file

a. com.ontimesuite.gc2011.level=FINEST b. com.ontimesuite.sametime.level=FINEST

6. Save and close the file

Enabling line numbers in trace logs

Enabling line numbers in trace logs is done on a client-by-client basis.

1. Make sure the Notes client is not running. 2. Locate the Notes directory on the client machine e.g. c:\Program Files\IBM\Lotus\Notes. 3. Locate the jvm.properties file in the framework\rcp\deploy sub directory. 4. Locate the “vmarg.Xnolinenumbers=-Xnolinenumbers” line and put a hash character (#) in

front of the line. 5. Save and close the file. 6. Delete the class file cache file from normally in <Notes

data>\workspace\.config\org.eclipse.osgi – it’s called something like "C240D2A32P_xpdplat_.jvm_G07".

7. Launch the Notes client and reproduce the issue Go to the “Help/Support/View Trace” menu item and copy/paste the contents of the dialog box that appears. This is the support trace log. Please note: Enabling line numbers changes the memory footprint of the Lotus Notes client so it’s

recommended only to enable it if instructed to do so by support.

GROUP CALENDAR


Setting up Discovery The Discovery calendar interface is intended for users using the Lotus Notes 8.5 Basic client (or older), which does not support the Notes calendar interface. To open Discovery users must have assigned the Discovery role in the ACL of the GC database. For more information please refer to Appendix A – ACL Setup.

When the Discovery role has been assigned to the users, the GC database serves as the Discovery launcher. Note: The user has to be synchronized into GC, prior to being able to use Discovery. Distributing

access to the database should not be different from others.

GROUP CALENDAR


Installing GC Web OnTime GC Web is a calendar viewer which can be accessed from your preferred internet browser. Supported browser list is available in the System requirements section. Before installing GC Web please ensure that the HTTP server task is started on the Domino server where OnTime® GC Web is installed. For preparation purposes you must also acquire the Fully Qualified Domain Name of your OnTime® server. It is recommended to sign the database with the servers’ id file. OnTime® GC Web only supports session based authentication. Please consult Domino Admin guide regarding this.

Installation procedure

1. Creating the GC Web database

Start by copying the template file to the Domino Data Directory, sign the template and create the database as you have done with the other OnTime® GC databases.

2. Edit settings

Open the GC Web database and click [OnTime® Group Calendar Web Settings]. You can

now edit the settings document.

3. Configuring GC Web

- Specify the server on which the GC Config database is to be found. - Specify the file path for the GC Config database.

- Enter the Fully Qualified Domain Name of your OnTime server - If your setup requires to access GC Web via SSL check off [Yes]

Please note: SSL must also be enabled on the database: o Right click GC Web and click [Application] – [Properties]

o Enable [Require SSL connection]

Enabling GC Web as a widget in iNotes GC Web can be integrated in iNotes for easier access. Enabling GC Web as a widget is a task performed on the Domino server on which OnTime® GC is installed. The Domino server is supplied with a configuration file template which needs to be edited for GC Web to work in iNotes. The filename is inotes_config.xml.template and is located in the domino\html subdirectory of the Domino Data Directory.

GROUP CALENDAR


When you open it the top of the file will look like the screenshot below. By default the highlighted attributes points to an IBM website. To change the source, simply change the attributes to a value matching your server.

- Replace “imageUrl=xyz” with an entry matching your own server with

“ontimegcweb.nsf/favicon.ico at the end. - Replace “title=xyz” with an appropriate title (e.g. “GC Web”) - Replace “url=xyz” with an entry matching your own server. - Save and close the file in .xml format.

When the above task has been performed, a notes.ini value must also be appended. When the value has been appended, please be sure to restart the Domino server for the value to apply successfully.

- Locate the notes.ini file in the Domino Directory

- Append the value “iNotes_WA_Widgets=1” Save and close the file

GROUP CALENDAR


Installing GC Mobile OnTimeGC Mobile is a calendar viewer compatible with mobile devices running JavaScript supported browsers and a minimum width of 320 pixels. This feature requires a separate license. A required license key for GC Mobile can be obtained from your preferred OnTime® business partner. A list of OnTime® Business partners is available at www.ontimesuite.com To enter the license key, please refer to section Single GC Server installation, step 4.

Before installing GC Mobile please ensure that the HTTP server task is installed on the Domino server where OnTime® GC Mobile is installed. For preparation purposes you must also acquire the Fully Qualified Domain Name of your OnTime® server.

Installation procedure Please refer to the section Installing GC Web.

Access the application from your device To retrieve the path to the application open the GC Web database and click [Launch OnTime Group Calendar Web].

This opens the OnTime GC Web interface. Add “/mobile” to the path, and you have retrieved the Mobile launch file path. Bookmark this path on your mobile device.

GROUP CALENDAR


Upgrading from previous versions of GC Important! As GC is an individual product in the OnTime® product line, it is not possible to upgrade from GC

9.x.x (or earlier) to GC version 1.0.x (or later). !!! Do NOT upgrade from GC 9.x.x to a GC version. !!!Before you upgrade:Mark Personal og

Before you upgrade:

Mark Personal and Confidential is moved to Global Configuration.

In Display Groups, “Collumn” is removed. Remember to make adjustments so that groups use fields or formulas BEFORE upgrading.

To upgrade your current version of GC to the latest version, follow the steps below.

1. Shut down the OnTimeGC server task

From GC database, go to the [Server Settings] view. Choose the server(s) which you want to upgrade and click the [OnTimeGC Commands] button and choose [-Quit-].

You can also from the server console type: “tell ontimegc quit” or “te ontimegc q” for short. If you have installed OnTime® GC on multiple servers with replicated databases, the server tasks must also be shut down on the other server(s).

2. Copy the template files into the Domino Data directory

If you have followed our recommendation and placed the template files in an ‘OnTime’ folder, please replace these files. If you have placed them in another folder or in the root of the Domino Data directory remember to specify this in the [Global Configuration] document.

3. Sign templates

After copying the templates to the data directory, sign the templates using an appropriate ID. It is recommended that it is the server’s ID that signs the OnTime® GC templates.

4. Replace design on OnTimeGC databases

Replace Design on the GC, GC API, GC Log, GC Web and GC Broadcast databases with the templates you have received. [Inherit future design changes] is checked as default. This should be unchecked.

5. Update Language+Region

From the GC database open the Actions menu and click [2. Update Language+Region].

GROUP CALENDAR


6. Replicate databases

If you have not installed OnTime GC on multiple servers skip this point. Replicate the Group Calendar database to the synchronisation server(s). You must replace the design of the API and Log databases on the other server(s).

7. Control Global Settings and Server Settings documents

As the design may have changed in GC it is recommended that the GC administrator controls and re-saves both the Global Configuration and Server Settings documents

8. Install/Update the server task

Open the [Server Settings] document and click [Install/Update Task]. If the server task is

obsolete it will automatically be replaced and started. If your current server task is up to date the task will not automatically start. You should therefore be sure to start it manually from the server console. Please refer to Appendix C - Installation on Linux platforms for further information about [Install/Update] Task on Linux platform.

9. Load the OnTimeGC server task.

If the server task was not updated please be sure to start the task manually. Start the task from the [OnTimeGC Commands] menu or by typing “load ontimegc” in the server console.

10. Upgrading Notes.

The process of upgrading Notes is similar to a new installation. The one difference is that the Lotus Notes client will ask if it should update a previous vision of Notes if it has been installed. Please refer to Installing the Notes calendar interface for detailed information.

GROUP CALENDAR


Appendix A – ACL setup Below are the minimum criteria for what users should be delegated via the ACL.

OnTime® GC database

Admins & Servers Manager access with Admin role

Users Reader access Reader access – Discovery role*

Anonymous No access

Default No access

*) For users running the Lotus Notes Basic clients

API database

Admins & Servers Manager access with ReadAll role

Users Author access with Create rights

Anonymous No access

Default No access

Log database

Admins & Servers Manager access

Anonymous No access

Default No access

Broadcast database


Anonymous No access

Default Editor

Web database


Anonymous Author access with Create rights

Default Author access with Create rights

OnTime® Time-Off database

Admins & Servers Manager access with Admin role + Read All

GROUP CALENDAR


Users Author access with Create documents

Approvers Author access with Create and Delete

documents+ Approver & Read All roles

Anonymous No access

Default No access

Note: It is recommended that you only grant access to person groups and not users individually.

There are 2 Roles which can be assigned to the users of GC. The Admin role is only assigned to administrative personnel who have the responsibility of configuring GC. Discovery is a role which is assigned to employees who are in need of the Discovery calendar interface. The OnTime® Notes calendar interface builds on the eclipse platform in the Notes 8.5.x Standard client. If you have not deployed the Notes 8.5 Standard client you must deploy the OnTime® Discovery interface.

GROUP CALENDAR


Appendix B – Console commands The following commands can be used to trigger different events from the OnTimeGC task out of its normal cycle.

Console commands Function description

load ontimegc Loads the ontimegc server task

tell ontimegc admin Synchronises all the people and resources between the Domino

Directory and the OnTime® Calendar configuration. The admin

command also updates Roles, Display Groups, Application default

settings and reads ACL calendar documents which are synchronised

into GC .

NOTE: Scheduled to run every hour

tell ontimegc sync Synchronises all the people and resources on all mailservers

tell ontimegc sync name Synchronises all users starting with“name” (I.e. tell ontimegc sync

peter)

tell ontimegc server sync Synchronises the server with the name “server”.NOTE: This command

only reads common names and not canonical names. I.e. “Server3” and

not “Server3/OnTime”.

tell ontimegc server sync

name

Synchronises all users matching “name” on server matching “server”

(I.e. tell ontimegc sync server1 peter)

tell ontimegc fullsync Triggers a full synchronisation on all calendar documents – is used

when legends are modified

tell ontimegc fullsync name Triggers a full synchronisation on all calendar documents on a user(s)

matching “name” (I.e. tell ontimegc fullsync peter)

Tell ontimegc broadcast Triggers the broadcast command which applies all created broadcast

documents to the users’ calendars

tell ontimegc quit Shut down the ontimegc server task

Loading GC from a different path In cases where the GC configuration database has been installed in a directory different from the recommended or named different than “ontimegc.nsf”, the server task must be started manually via the server console by typing the full name and path to the GC configuration database. Fx. “load ontimegc path\ontimegc2011.nsf”. The server task can also be appended to the notes.ini file manually or by creating a program document in names.nsf.

GROUP CALENDAR


Appendix C - Installation on Linux platforms Installing OnTime Group Calendar on Linux is basically not different from installing OnTime Group Calendar on MS Windows. For System Administrators unaccustomed with the extra security facilities offered by the Linux operating systems some pitfalls exist. The intent of this document is to help avoid these pitfalls while installing OnTime® Group Calendar.

Installation

During installation on MS Windows the distribution/installation of the server task is performed by the action [Install/Update Task] button on Server Settings document. This is not possible on Linux due to

security measures. Therefore, installing the server task is a manual process. Be aware that Linux is case sensitive regarding file paths. It is therefore recommended to type all directories and database filenames in lowercase. Along with your OnTime® distribution you should have received the file ‘ontimegc’, in the folder ‘/tasks/linux’ in the .zip file.

Installation steps:

1. Establish writer-access privileges to the domino binary depository directory usually

/opt/lotus/notes/latest/linux/. on Linux,

2. Copy the file “ontimegc” to the directory by using FTP or any other method.

3. Ensure proper ownership of the tasks: This is critical

The owner:group for ‘ontimegc’ should be the same as for every other file in the /opt/lotus/

directory structure. Without proper ownership the server would probably freeze -- and would

have to be manually killed/system rebooted.

ex. as root: ‘chown lotus:lotus ontimegc’ (where “lotus” is the proper owner names)

4. Ensure proper mode of the tasks.

ex as owner or root: ‘chmod 755 ontimegc’ (-rwxr-xr-x)

5. Load the tasks by typing standard domino commands “load ontimegc”

Please be aware, that not all platform versions are supported by IBM Lotus Domino and hereby also

not OnTime® Group Calendar. Please refer to IBM’s website for a full list on supported platforms

regarding IBM Lotus Domino.

Please notice that OnTime® Group Calendar only supports Linux Server and not Linux clients. You

can therefore only install OnTime® Group Calendar on a Windows client.

GROUP CALENDAR


Support To receive support for OnTime® Group Calendar, contact your local OnTime® Partner. If you do not have an OnTime® Technical Support Contract, support must be obtained from an OnTime® reseller. The support service from the reseller is usually a payable service. If you have purchased OnTime® directly from IntraVision, refer to our website www.ontimesuite.com. Remember to state the following information:

o OnTime® Group Calendar version o Domino platform release o Notes platform release o Description of the issue o Log file if necessary

For further information about the OnTime® product please look at www.ontimesuite.com from where our manuals and guides can be downloaded.

Group Calendar Group Calendar... · 2018-08-28 · allows for almost real time updates of the group...

Documents

Transcript of Group Calendar Group Calendar... · 2018-08-28 · allows for almost real time updates of the group...