Cordaware Bestinformed Users Manual

Welcome to

Content

Reference Notes for this Manual 6 Introduction Cordaware bestinformed 9 New in version 4 11 1 Changelog ...... 13 IT-Security, Data-Security, Audit 15 1 IT-Security ...... 15 2 Data Security.. .and...... Privacy...... 16 3 Audit ...... 18 Additional Information 20 Quickstart 21 1 Infoserver Installation...... 21 2 Infoclient Installation...... 26 3 Create Group...... 27 4 Send Infos ...... 29 Infoserver General 30 1 Installation ...... 31 System Requirements...... 31 Hardware ...... 32 2 Configuration...... 33 Quick Configuration...... 33 Inifile ...... 36 Detailed Systeminfos...... 48 3 Server Update... .and...... Relocation...... 49 Server Update...... 49 Server Relocation...... 50 4 Web Interface...... 51 Login ...... 52 Session length...... 53 5 Licence ...... 54 6 Database and.. .Backup...... 55

Infoclient General 58 1 Installation ...... 59 Manual Installation...... 60 Autoinstall ...... 61 Configuration...... 62 Implementation...... 64 Filter ...... 67 Autoupdate ...... 70 Alternative Servers...... 72 NetInstall ...... 77 2 Configuration...... 78 Quick Configuration...... 78 Inifile ...... 80 Export Inifile ...... 88 InfoclientValues...... 90 Hotkeys ...... 92 Proxyserver ...... 94 3 Infogrid ...... 95 4 Connections...... 97 Filter ...... 98 Quickinfo ...... 100 Notice of receipt...... 101 Notice for Operation on Terminalservers 102 1 General ...... 102 2 Citrix ...... 103 3 Logon Screen...... 105 4 Static Display...... 106 5 Exclude Groups...... 107 Basis 108 1 Info Management...... 109 Create Infos ...... 109 WYSIWYG...... Editor...... 109 Minihtml. .Editor...... 110 ScriptVars...... 113 Time and.. .Environment...... Variables...... 117 Caption ...... 119 Multiple .Languages...... 120 All-Clear. .function...... 121 Content .Management...... 123 Templates...... 128 Default Template...... and...... Values...... 129 Release .as.... .Ticker...... 130

II III Cordaware GmbH Informationslogistik III

Active- and...... Displaytime...... 131 Recipient.. .selection...... 132 Recurring...... 134 Popup ...... 138 Desktop .and...... WinLogon...... 140 Sound ...... 142 Tab Mode...... 143 Administration...... 144 Infofilter and. ..Shared...... Whiteboard...... 147 Web Directory...... 157 Infos on the .Logon...... Screen...... 159 2 Statusinfo Management...... 160 Create Statusinfo...... 160 Create Status...... 161 Create Statusdetail...... 162 Run Statusinfo...... 164 3 Group Management...... 165 Create Group...... 166 Add Members...... 167 Simple Filter...... 168 Scriptfilter...... 169 4 Channel Management...... 170 Create Channel...... 171 Subscribe to. .Channel...... 172 5 Tools ...... 173 ISPerformancer...... 173 Professional 175 1 Domain Administration...... 176 Access Native.... .Domain...... 176 Additional Domains...... 179 Refresh Domain...... Groups...... 182 2 Interfaces ...... 183 MailToInfo ...... 183 Settings...... 183 Send ...... 185 Editor ...... 189 Testapplication...... 190 Send Scripts...... 191 Cancel Infos...... 193 Automate...... 194 Attach Files...... 196 Access Statusinfos...... 198 InfoToMail ...... 200 InfoToAnywhere...... 211 Infos to external...... networks...... 212 Infos to SMS...... recipients...... 216

InfoToFax...... 218 API ...... 219 Header ...... 220 Example...... 233 3 Extendend Groupmanagement...... 234 Scriptfilter Functions...... 234 Groupmanager...... 236 Autogroups ...... 242 4 Infoscenarios...... 251 Introduction...... 251 Setting up Infoscenarios...... 252 Execute Infoscenario...... 256 Examples ...... 258 5 Reports ...... 262 Introduction...... 262 Default Reports...... 263 Report Generator...... 266 Introduction...... 266 Report with...... tabular...... analysis...... 279 Report with...... graphical...... analysis...... 282 Enterprise 289 1 Multiuser ...... 290 Hierarchy ...... 292 Poweruser.... .Profiles...... 292 Poweruser.... .Clones...... 293 Poweruser.... .Hierarchy...... 295 Poweruser.... .Container...... 296 Roles ...... 299 Sub-Admin...... 300 Editors ...... 310 Read Only...... 312 Logon Groups...... 314 Additional Notes...... 318 2 Dynamic Distribution...... 319 Dynamic InfoClientValues...... 321 Types of. .Clientproperties...... 321 Allocate .Clientproperties...... 324 Application...... in.. .Infoservergroups...... 326 Dynamic Channels...... 329 Configure... .Dynamic...... Channels...... 329 Scripteditor...... -. .Quick...... Configuration...... 335 Further Examples...... 341 3 Several Servers...... 347 Additional Servers...... 347 Infoserver Grid...... 349

IV V Cordaware GmbH Informationslogistik V

Cordaware TED 352 1 Introduction...... 352 2 Create Surveys...... 353 Basic Settings...... 353 Questions ...... 356 Options ...... 364 Survey as Question...... Library...... 365 3 Test and Start...... 367 4 Results ...... 369 5 Random Samples...... 371 6 Corporate Design...... 372 7 Export and .Import...... 373 8 History ...... 375 9 Privacy ...... 376 Remote Access 377 1 Operation ...... 378

1. Reference Notes for this Manual

This manual provides the documentation on the installation, configuration and operation of the software Cordaware bestinformed®. The manual is provided in the PDF format to ensure the best posssible access to the documentation.

Chapters 2 (Introduction) through 9 (Terminalserver) are dealing with general topics on architecture, installation and configuration of Cordaware bestinformed®. The functions decsribed in these topics are generally applicable in all editions of bestinformed.

Chapters 10 (Basis), 11 (Professional) and 12 (Enterprise) are dealing with the documentation of the features provided by each respective edition. All functions of the Basis Edition are also available in the Professional and Enterprise Editions, respectively all features of the Professional Edition are also available in the Enterprise Edition. If, for example, you are using Enterprise Edition and you want to view the topic dealing with synchronisation of AD groups, then you will need to go to the respective topic in the chapter Professional.

The documentation of the Add-Ons TED and Remote Access can be found in chapters 13 and 14. These Add-Ons are available only for the Professional and Enterprise Editions of bestinformed.

Handling this PDF document

By using the Bookmarks function of the Adobe Reader®, you can instantly access single chapters and topics of this document. In case the bookmarks are not displayed automatically after opening this document, then you can open the bookmarks with these buttons:

Adobe Reader 7

Adobe Reader 8

The Adobe Reader® also provides a search-function. If, for example, you would like to know more about the MailToInfo API, then insert this keyword into the search-textbox. The search- result will deliver all topics, which contain the search-word in its text. The search-function can be accessed with following buttons:

Adobe Reader 7: Delivers a list of links to topics, which contain the searched keyword in its text.

Adobe Reader 8: By clicking the Next- and Back- buttons, you can browse through all topics in this document which contain the searched keyword in its text.

The topics often contain cross-references to other topics in this document in form of a hyperlink. By clicking on such a hyperlink, you will be redirected to the referenced topic.

For getting back to the previous topic containing the cross-reference, you can use the "Back" function of the Adobe Reader®. In Adobe Reader 7, you can find the respective buttons next to the page browser on the bottom of the window.

In Adobe Reader 8, you will need to press the key-combination Alt + Left Arrow, respectively choose the desired action from the context-menu of the PDF file which is accessible by right- clicking the document.

2. Introduction Cordaware bestinformed

Cordaware bestinformed is an advanced information- and messaging system for distributing high-prority messages to affected users. Messages are distributed instantly, group-specifically and are displayed in a dynamic ticker without delay on the user's desktop.

The recipient is able to instantly view the information, you don't need to wait for the recipient to read his/her message with a delay of time, as it is the case e.g. with emails.

In contrast to pop-up systems, the recipient is not interrupted in his work. The user's focus can remain on his current task and he's not obliged to click on a OK button in order to resume his current occupation.

Because of the swift and easy-to-use administration of groups, messages can be distributed purposefully at cyberspeed.

In addition to displaying messages directly on the user's desktop, it is possible to display messages on the Windows logon-screen, i.e. if the user has locked his computer or has logged himself off.

Further, you can arrange time-steered and periodically recurring messages.

For urgent messages, it is possible to play a system-sound or any other wav-file upon receiving a message.

If a user is not at his desktop, then the messages are being saved and can be displayed again any time later.

For optimizing the viewability, the messages can be formatted. Also, a text of several lines is possible.

Additionally, the display of a message can not only be visualized as a ticker, it also is possible to install persistently displayed Statusinfos, and for particular cases of emergency it even is possible to create pop-ups.

The API and MailToInfo interfaces enable a migration into other systems. If desired, the Infoserver can be administered with alternative applications.

In addition to its basic functionalities, bestinformed offers you numerous further possibilities to optimize your information-management.

Remote Access

Cordaware Remote Access offers you sample possibilities for remote maintenance and administration.

Contrary to other remote-maintenance and tracking tools, Cordaware Remote Access is not limited to single functions or single computers, but offers a Remote Shell, which enables you to perform any action on any computer in your entire network.

Cordaware TED

Cordaware TED enables you to quickly and economically perform empolyee-surveys. This offers you a variety of possibilities to acquire a client-feedback and to react accordingly.

3. New in version 4

This is an overview of the new features in Cordaware bestinformed version 4:

· Windows Vista compatibility · Conversion of the internal data-structure from XML to database · Autoinstall: Exclude Infoserver groups from the Autoinstall process (Basic) · Release Info as ticker (Basic) · Infofilter and Shared Whiteboard (Basic) · Info to ID (Basic) · Send Info in multiple languages simultaneously. (Basic) · Background colors for Infos. (Basic) · Content management (Basic) · Caption in newsticker. (Basic) · Popups: Extended content and display options (Basic) · Infoserver AutoBackup (Basic) · Acknowledgement of receipt for Infos. (Basic) · Tab-Mode: easier access to Info detail settings. (Basic) · Statusinfos: Cascading status (Basic) · AD Computergroups: New scriptfilter function for AD computergroups (Professional) · Autogroups (Professional) · All Clear function (Professional) · InfoToMail with SMTP: Direct distribution over SMTP now possible (Professional) · Reports (Professional) · Infoscenarios: Several Infos now can be sent at once in a predefined scenario. (Professional) · New Poweruser Hierarchy (Enterprise Edition) · New Server Grid (Enterprise Edition) · New performance options for surveys (Cordaware TED)

Tabular overview of new functions and availability

Basis Professional Enterprise Windows Vista compatibility Internal database Exclude groups from Autoinstall Release Info as ticker Infofilter and Shared Whiteboard Info to ID Multiple languages Background colors Content management Caption in newsticker Popups: Extended display options Infoserver AutoBackup Acknowledgement of receipt Tab-Mode Statusinfos: Cascading status AD Computergroups Autogroups All Clear function InfoToMail using SMTP Reports Infoscenarios New Poweruser Hierarchy New Server Grid New performance options for surveys

The chapter InfoToAnywhere contains practical example of use for sending Infos to external networks, as well as to SMS and Fax recipients.

3.1 Changelog

Version 4.7.0.3

Infoserver

MailToInfo: Powerusers can access templates of other Powerusers.

Infoscenarios: Global ScriptVars in templates allow faster editing.

TED: New copy function enables users of TED to use surveys as question libraries.

Infoserver Grid: New options for Client-Infoservers for better performance.

Info Overview/Infofilter & Shared Whiteboard: Default font-size editable with InfoSameSizeValue= when applying InfoSameSize=true.

ScriptVars: When copying an Info with a ScriptVar, then the ScriptVar will be preserved and it is configurable, if the default value or the value from the copied Info are to be used as suggestion when saving.

Statusinfos: It is now possible to switch the Status of Statusinfos via MailToInfo.

Detailed Systeminfos: The Infoserver displays system values for more detailed information.

Infohistory: When viewing the details of an Info in the Infohistory, then user-relevant data collected in the Audit-Mode will be displayed as well.

Infoclient

The release of version 4.7.0.3 includes minor bugfixes.

Version 4.6.0.0

Infoserver:

InfoToMail: Content of Infos inserted in multiple languages now can be accessed with functions Infos(LANG_INDEX), Captions(LANG_INDEX) and Backgrounds(LANG_INDEX).

API: Default setting for release of Infos submitted through the API now can be configured in the Infoserver.ini.

Infofilter & Shared Whiteboard: It is now possible to set a socalled UDF-Filter, which allows you to define customized filter-rules similiar to a WHERE clause in a SQL statement.

Audit Mode: The Infoserver now can be set to run in Audit Mode, in which the Infoserver will protocol all user actions.

RSA Encryption: The login to the web administration now is RSA encrypted. The encryption length can be set as desired in the Infoserver.ini, default is 1024 bit.

Infoclient:

The Infoclient now is configured to automatically deactivate running screensavers upon receiving a new Info.

Version 4.5.0.0

Infoserver:

Multiuser Mode: Classification in Profiles, Clones and Container. Login mechanism for logging on in a child-profile and as a substitute in a logon group.

Ellipsis and link to detail-view of Infos in an Infofilter/Shared Whiteboard.

Globale time in a Servergrid.

Disable the use of the Infoclient for certain usergroups on Terminalserver.

List of SMTP-server addresses for InfoToMail SMTP-script.

Infoclient:

Halting the ticker through right-click with mouse.

Disable view of Infodetails in the Infogrid.

Time and environment variables in the Infotext.

Cordaware TED:

Sort, edit, copy and delete multiple questions simultaneously.

Allocating the result-view.

Comments in survey results.

4. IT-Security, Data-Security, Audit

4.1 IT-Security

Reserverd IP Ports

Following TCP/IP ports are used by the Infoserver by default:

Port Application 800 Port for the communication with the Infoclients 801 Web-Administration over HTTP 802 Web-Interface of the survey module 825 SMTP-port of the Infoserver for the MailToInfo interface 808 Report generator 16000 Database

Alle ports can be customized.

Notice for IP-filter / firewalls

If an IP-filter/firewall is in use, then port 800 on the Infoserver must be released for all inbound connections. The same accounts for port 802, if the survey module is in use. The ports 801 and 808 can be configured to accept connections only from those workstations, from which administrators of bestinformed are to access the administration interface. Port 16000 must be configured to accept connections from the localhost and, if used, from Client-Infoservers in the Servergrid. If it is necessary to access the bestinformed database over ODBC from different computers, then these need to be included in the release of port 16000.

Port IP-Filter / Release Application 800 All IP addresses Infoclient.exe, Internet Explorer for access to web-administration 801 All IP addresses or only Admin Internet Explorer workstations 802 All IP addresses Internet Explorer 808 Servers/workstations which are to use Internet Explorer, biReporter.exe the report generator 825 Servers/workstations on which All applications, which are to use MailToInfo is to be used MailToInfo 16000 Localhost, computers in the Servergrid, Infoserver.exe, ODBC applications workstations with ODBC-access to the Infoserver database

4.2 Data Security and Privacy

Data Security

By using the Autobackup function, a backup can be performed within an automized interval. The Autobackup creates a full copy of the Infoserver database at the turn of each interval. This copy can be used for creating a recovery after a sever error (e.g. hardware failure) or when creating a new installation on a new system.

The Infoserver generates all pages of the web-administration dynamically, a manipulation of HTML source-files is impossible.

Privacy

With every newly created dataset in the database, the creating user is included in the dataset. The visibility of this information can be deactivated on Poweruser level. Therefore, in principle this information is only visible for the admin user and for users with access to the database.

Data submitted in surveys is always anonymous, a principle association of participant and answer is not possible.

Password Security

All admin and domain passwords used by the Infoserver are saved encrypted. Powerusers must use their domain password for logging in. The passwords of Powerusers are not saved in the Infoserver, but a compare request is sent to the domain and a succesfull login is only granted, if an "OK" is returned. The login in the administration interface is RSA encrypted, default- length is 1024 bit. The bit-length of the encryption can be adjusted in the configuration file Infoserver.ini.

The Infoserver admin password is saved encrypted in the configuration file Infoserver.ini. The admin's password can only be decrypted by the Infoserver. The admin's password can be edited in the Infoserver administration website. For editing the admin's password, select the item Additionals->Password->Admin Password. On the following page, you can set a new password for the Infoserver admin. If the password was edited, it is necessary to relogin.

In case the Infoserver admin password was lost or is unknown, then you can reset the password by deleting the encrypted value of the admin password in the configuration-file Infoserver.ini and restarting the Infoserver thereafter. Resetting the admin password with this method is only possible for users with the appropriate authorization for the file Infoserver.ini.

Passwords of the domain-administration are saved encrypted in the Infoserver database and can only be decrypted by the Infoserver. These passwords can only be edited from the administration interface of the Infoserver. A reset in the database is only possible for those users, which have access to the database and the right to write to the appropriate table.

Therefore, passwords are only saved in the Infoserver.ini (Admin) and in the table "Domains" of the domain-administration in the database. For the domain-administration, the user and his password can be set up in the domain solely for bestinformed for avoiding the use of a productive user.

4.3 Audit

In activated Audit-Mode, the Infoserver can protocol any user-activity. For this, the tables Audit and Auditdetail are included in the Infoserver database.

Activating the Audit-Mode

The Audit-Mode must be activated by editing the configuration-file of the Infoserver. For this, the configuration-file contains the items AuditOn=, AuditdetailOn= and AuditResolveHostOn= . The values of the items AuditOn, AuditdetailOn and AuditResolveHostOn can either be true (default) or false. If the Audit-Mode is activated (AuditOn=true respectively AuditOn= ), then the actions on the Infoserver are protocolled in the table Audit. The table Audit provides following fields/columns:

ID: Primary key of the dataset in the table Audit.

ID_Record: Primary key of the dataset (= foreign key), which was affected by the action.

Tablename: Tablename in which the editet dataset is located.

Currentuser: Name of the user, who edited the dataset.

Logonuser: Name of the profile, in which the user has logged on to the Infoserver (applicable only in the Multiuser Mode).

Action: The performed SQL-action that applies to the action on the edited dataset. Can only be INSERT, UPDATE or DELETE.

Timestamp: Date and time of the action.

Server: Name of the Infoserver, on which the action was performed (relevant only for Server Grid).

TCPIP: IP-address, from which the user did access the Infoserver administration.

Host: The name of the host, that is associated to the IP-address. The host is only resolved, if the item AuditResolveHostOn was activated in the Infoserver.ini.

In case the item AuditdetailOn is activated in the Infoserver.ini, then the Audit-Mode will also protocol the actions on the affected fields/columns of the respective dataset. These actions are protocolled in the table Audtitdetail.

ID: Primary key of the dataset in the table Auditdetail (PK).

ID_Master: Primary key of the referenced dataset in the table Audit (FK).

Colname: Name of the edited column in the dataset, which is defined by the reference Auditdetail[ID_Master] (FK) <-> Audit[ID] (PK) + Audit[Tablename] + Audit[ID_Record] (FK) <-> $Tablename$[ID] (PK).

IntValue: If the original datatype of the edited field in the affected recordset is of type Integer, then the value will be inserted in this field.

DateValue: If the original datatype of the edited field in the affected recordset is of type Timestap, then the value will be inserted in this field.

StringValue: If the original datatype of the edited field in the affected recordset is of type String, then the value will be inserted in this field.

Display of Audit-Data

The data collected in active Audit-Mode can be viewed in the Infohistory. For viewing the data, you must click on the hyperlink Detail in the row of the desired Info.

By clicking, a new page opens, displaying all properties and details of the Info inlcuding the collected Audit data.

5. Additional Information

Operating system compatibility

Cordaware bestinformed is compatible to following operating systems:

· Cordaware bestinformed 3: Windows 95, Windows 98, Windows ME, Windows NT, Windows 2000, Windows 2003 and Windows XP · Cordaware bestinformed 4: Windows 2000, Windows 2003, Windows XP and Windows Vista

Exclude database files from virus-scan routines

For avoiding interferences with the Infoserver's performance, you should exclude the directories of the active database and of the (auto-)backups from all virus-scan routines. The active database is located in the directory Data in the installation directory of your Infoserver. See also chapter Backup.

Notice for operation under Windows Vista

When a user logs off under Windows Vista, then this is equivalent to a reboot. Canceled and read, yet active, Infos will be displayed again in this case. If you use the Environment variable %Username% under Vista, it will only provide the computername because of the session-properties.

Index Web directory for fast filesearch

The directory Web in the installation directory of the Infoserver must be indexed for the fast filesearch. If this is not the case, then it can occur that images and scripts hosted in this directory can't be loaded properly by the clients.

6. Quickstart

6.1 Infoserver Installation

For installing the Infoserver, please proceed as following:

1. Run the installation-file bestinformed.exe

By running the file bestinformed.exe, the installation-routine is kicked off.

On the start-screen, click on Next to progress with the installation.

2. Confirm Licence Agreement

For installing bestinformed, you must accept the Licence Agreement.

3. Select the installation-path

By default, the path Program Files\Cordware\Infoband on the primary disk of the computer is suggested by the program for the installation-path.

4. Select components

Select the component Infoserver in order to install the Infoserver on your computer and click on Next.

5. Define the Infoserver port

Here you must define the port of the Infoserver, to which the Infoclients will need to connect. This is necessary for the smooth distribution of Infos. By default, this is port 800.

6. Set the administrator's password

Insert the desired password for the user "admin" and confirm it before proceeding with the installation.

7. Set startmenu items

Here you can define, if and in which folder in the startmenu the items for Cordaware bestinformed are to be created.

8. Extraction and installation of program-files

After the basic setup of the Infoserver is completed, you now can proceed with the final phase of the installation process.

9. Completion of the installation

After the installation is completed you can instantly access the website of the Infoserver and log into the administration. Additionally, you can acces the Quick Configuration of the Infoserver by clicking on its taskbar-icon:

For further information on installation and configuration of the Infoserver, please see chapter Basic->Infoserver.

6.2 Infoclient Installation

The installation of the Infoclient is also done with the installation-file bestinformed.exe. The sequence of the work steps is analogue to the installation of the Infoserver. Yet, you will need to consider the differences in steps 4 and 5:

For installing the Infoclient, you will need to select the appropriate component in step 4.

In step 5, you will need to insert the address of the Infoserver and its port.

The address of the Infoserver can be its computername (also NetBIOS), DNS-name or IP- address. The port is the one defined during the installation of the Infoserver, default is port 800. During the following installation-process, the Infoclient is configured to run immediately and to connect to the Infoserver automatically. After the installation is finished, you now can access the Quick Configuration of the Infoclient by clicking on its taskbar-icon:

For further information on installation and configuration of the Infoclient, please see chapter Basic->Infoclient.

6.3 Create Group

For setting up a recipient-group in the Infoserver, please proceed as following:

1. Login Administration Interface

Open the website of the Infoserver, e.g. from the Quick Configuration and log yourself in.

2. Access the Group Management

Click on the button Group Management on the startpage of the Infoserver.

This will open the overview of recipient-groups of the Infoserver.

3. Create new group

Click on the hyperlink New group in the group management.

The form for creating a new group now opens.

Insert a desired name and select the group to be of the type Infoclient. Save the group, it then will be listed in the group management.

4. Set group-membership

Click on the hyperlink add in the column Username in the row of the newly created group. This will open the form for the membership-definition.

Insert your username in the field Username and save the information. You are now a member of this recipient-group. If an Info is addressed to this group, you will receive it.

For more information on this topic see chapter Basic->Group Management.

6.4 Send Infos

1. Open Infoeditor

Click on the button New info on the startpage of the Infoserver administration. This will open the Infoeditor.

2. Compose and save Info

Insert any desired text into the Infoeditor and click on the tab Save.

You now will see a preview of the Info. For saving and sending the Info, click on the button Save beneath the Info content in the preview.

You can find more information on this topic in chapter Basic->Info Management.

7. Infoserver General

The Infoserver is the agent that distributes your messages to the computers with installed Infoclient. Next to distributing messages, the Infoserver holds the information on recipient- groups, domain-registration, Powerusers and many more. All information is stored in an internal database (transactional NexusDB), which also can be accessed via ODBC. Files of the Content Management are stored, per user, in a directory which is open for public access via HTTP. The configuration of the Infoserver is stored in a configuration-file, the Infoserver.ini. When accessing the Quick Configuration, certain configuration parameters can be edited live.

The administrator-interface is accessed via a webpage. Among many advantages, one is that adminstrators can log themselves onto the Infoserver from any computer in the network.

7.1 Installation 7.1.1 System Requirements

Cordaware bestinformed consists of the Infoserver and the Infoclient. The version bestinformed 3 ist compatible to Windows® operating systems from Windows 95 to Windows XP (Win95, Win98, WinNT, WinME, Win2000, Win2003, WinXP and Terminalserver). The newest version bestinformed 4 is compatible to Windows operating systems from Windows 2000 to Windows Vista (Win2000, Win2003, WinXP, WinVista and Terminalserver).

For each connected Infoclient, the Infoserver needs approximately 20kB of memory (RAM), i.e. if you have 1000 clients connected, you will need ca. 20MB of RAM on the server.

You do not need to install ISS, Apache or any other webserver technology on the Infoserver.

If your Infoserver supplies up to some hundred clients, the server can be installed on any "regular" workstation, otherwise it is recommended that you use a system with installed Win2000 or Win2003 Server.

To configure the Infoserver, you only need a functioning webbrowser. This has the advantage, that you can adminstere the Infoserver from anywhere in your network.

7.1.2 Hardware

Depending on the number of clients, the following minimum hardware-setup is recommended:

Less than 1000 clients

Processor Pentium III 700 Mhz or equivalent

main storage : 512 MB RAM

1000 – 10 000 clients

Processor Pentium III 1500 Mhz or equivalent.

main storage : 1 GB RAM

10 000 – 50 000 clients

Processor Pentium IV 1500 Mhz or equivalent.

main storage: 2 GB RAM

More than 50 000 clients

Processor: Pentium IV Dual Core CPU

Per 50 000 Clients 1 network interface card

main storage: 4 GB RAM

7.2 Configuration 7.2.1 Quick Configuration

All settings of the Infoserver can be edited in the configuration file Infoserver.ini, which is located in the installation directory of your Infoserver (e.g. C:\Program Files\Cordaware\Infoband).

In addition, it is also possible to edit different settings in the quick-configuration. The quick- configuration can be accessed by clicking on the Infoserver-icon in the taskbar.

Here you can set following values:

Port

The port of the Infoserver. The port must be identical to the port set for the Infoclient. In order to edit the port, the box active must be unselected.

Infotime

Editing this value sets the default timespan for which an Info will be active on the server.

Clienttime

Sets the default timespan, for which an Info will be displayed on the client.

Example: You are generating a new Info, the default values are set to

Infotime: 100 and Clienttime: 5.

In this case, every addressed client which logs on to the Infoserver in the timeframe of 100 minutes from the start of the Info will receive the Info, and the Info will be displayed for 5 minutes on the clients screen.

Important: In the quick-configuration you can edit only default values. These default values are applied, when creating a new Info. Of course you can always edit these values individually when creating a new Info. When creating the next Info thereafter, the values will be reset to the default values as defined in the quick-configuration.

Language

Here you can set the language in which the user interface of the Infoserver will be displayed by default. Select your desired language and click on Configuration in order to access the Infoserver administration page.

User desktop

Here you can set the following default values.

1. Show Info

If this box is not checked, the default configuration of a new Info is to not show the Info on the user desktop.

2. User can close Info

This sets the default, if an user can close an Info or not. If the user is allowed to close an Info, on the right hand side of the ticker a symbol will be shown which can be clicked in order to close the Info.

Logon desktop

Here you can set the same defaults as for the user desktop.

Cancel Info

on closing

If this option is activated, Infos will be aborted on the client upon closing and won't be displayed for its remaining lifetime.

Example:

A user receives a message which is active for 10,000 minutes on the server. After having read the message, the user is closing it by clicking. If he is to receive a further message, the old message will be shown again in regular, because it is active for 10,000 minutes. If you have checked Cancel Info on closing in the quick configuration, you are preventing the ticker from showing old messages again, because the ticker now will only display new messages if the user has closed an old message by clicking on the closing-symbol.

On Hyperlink click

This option will force the ticker to behave analogously when clicking on a hyperlink in a message. If you have selected Cancel Info on hyperlink click in the quick configuration, an Info will be closed after clicking on a hyperlink in the Info and won't be displayed again during its lifetime.

Notice: This option can be set individually for each new Info upon creating. Therafter, any new Info will be equipped again with the default values as set in the quick-configuration.

Domain

Refers to the current domain, in which the Infoserver resides.

Currently connected

Here you can see the number of clients, which are currently connected to the Infoserver.

The max value indicates the maximum number of possible connections, which can be established in accordance with your licence key.

A detailed overview of the connections can be accessed on the Infoserver administration page.

7.2.2 Inifile

In the configuration-file Infoserver.ini, all parameters of the Infoserver can be set and edited. The file is located in the installation directory of the Infoserver (e.g. C:\Program Files\Cordaware\Infoband\Infoserver.ini).

This is an overview of all currently possible Infoserver.ini items:

[General]

************** Port ****************

Port=Default 800, Is the port to which Infoclients connect to.

*************InfoTime**************

InfoTime=Default 1 minute, the active time of a new Info.

*************ClientTime****************************

ClientTime=Default 1 minute, default time for which the Info is running on the screen.

************.....LastID****************************

.....LastID=Saves the last iserted ID of a dataset in the respective table (internal use).

***********ShowOnUsersDesktop*******************

ShowOnUsersDesktop=true/false (default=true) Default setting for the property User desktop: Show Info in a new Info.

**********ShowOnWinlogonDesktop*****************

ShowOnWinlogonDesktop=true/false (default=true) Default setting for the property Logon desktop: Show Info in a new Info.

**********CanCloseOnUsersDesktop*****************

CanCloseOnUsersDesktop=true/false (default=true) Default setting for the property User desktop: User can close Info in a new Info.

**********CanCloseOnWinlogonDesktop**************

CanCloseOnWinlogonDesktop=true/false (default=true) Default setting for the property Logon desktop: User can close Info in a new Info.

************* Password******************

Password of the Admin. Password is encrypted.

************DBVersion*****************

DBVersion=20705 Version number of the database.

************Infoserverversion************

Infoserverversion=4.5.0.0 Version number of the Infoserver.

************ Language *****************

Language=German or English, Selection of the default-language for the web administration.

****************Domain********************

Domain=LOCALHOST or domain-name of the PC where the Infoserver is running. A PDC can also be entered here.

***************Threadpool*************************

Threadpool=Default 100, is used under Win9x, Server view.

***************Singleuser*********************

SingleUser=Default true, to switch the reminder on/off.

***************Domaincontroller************************

Domaincontroller=Reserved.

************** MaxBeepCount***************************

MaxBeepCount=Default 10, for the limitation of the number of beeps.

************** MailToInfoPort*********************

MailToInfoPort=Default 825, SMTP-port of the Infoserver SMTP for the MailToInfo interface.

************* MailToInfoActive*************************

MailToInfoActive=Default true, switches the SMTP function for MailToInfo on/off.

************* RefreshGroupsTime***************

RefreshGroupsTime=Default 1440, in minutes - Refresh intervall of domain groups registered in the Infoserver.

************ Debug ***********************

Debug=Default false, switches the debug mode on/off.

*********** KeepAlive *******************

KeepAlive=Reserved.

********** HistoryDeleteLink***************

HistoryDeleteLink=Default true, switches the "delete" link in the history of the admin on/off.

********* ImagesDir***********************

ImagesDir=Default /Images relative to the Infoserver web-directory, folder where the images of the WYSIWYG editor are provided.

************CancelOnClose*****************

CancelOnClose=true/false (default=true) Default value for the option Close: Cancel Info on closing ticker in a new Info.

************CancelOnClick******************

CancelOnClick=true/false (default=true) Default value for the option Click: Cancel Info on hyperlink click in a new Info.

*************SurveyDeleteLink**************

SurveyDeleteLink=Default true, switches the "delete" link at admin's surveys on/off.

*************SurveyResultDeleteLink**************

SurveyResultDeleteLink=Default true, switches the "delete" link at admin's survey-results on/off.

************MtITCP*********************

MtITCP=Default empty, list of TCPIP-addresses with Wildcharts, separated by ";". From these addresses, it is allowed to submit Infos via MailToInfo.

***********MtIAuth*****************

MtIAuth=Authentification of the MailToInfo interface for the admin Default 0; Passwordauthentification 1; TCPIP-adress-authentification 2; Password and TCPIP-adress Authentification 3; Authentification by signed mails

************MtIPassword****************

MtIPassword=Default empty, Password of the Admin for the MailtoInfo interface, empty Password requires the use of the Web-login Admin password.

***************HTTPTCP*********

HTTPTCP=Default empty, list of TCPIP-Addresses with Wildcharts, separated by ";". From these addresses, the web access is allowed.

****************** MtI**********************

MtI=Default true, defines wether the admin is authorised to use MailToInfo.

***************ShowOnTaskbar****************

ShowOnTaskbar=Default true, show/hide the Inforserver's icon on the taskbar.

************** BrowserPort *******************

BrowserPort=Default 801, port of the web-access.

************** SurveyPort****************

SurveyPort=Default 802, port of the web-access of surveys.

**************AuthPowerusersOnWin9x********************

AuthPowerusersOnWin9x=Default true, no password query for Powerusers on Win9x.

************** SessionTimeOut*********************

SessionTimeout=Default 30, in minutes. Time until reauthentification on the web-frontend is necessary.

*************** Autoupdate***************

Autoupdate=Default true, Autoupdate on/off. If it is off, it also can't be switched on in the web-frontend.

**************Autoinstall *****************

Autoinstall=Default true, allow Autoinstall or not.

******************AutoinstallInterval*****************

AutoinstallInterval=reserved.

*****************AutoinstallScanInterval***************

AutoinstallScanInterval=Default 10, in minutes, if autoinstalling whole domains, the interval, in which the network is scanned for new PCs.

****************AutoupdateOnVersionNotEqual******************

AutoupdateOnVersionNotEqual=Default FALSE!, Autoupdate if version numbers are unequal, not only the latest version "Inverse Autoupdate".

****************ShowInfoSummary**************

ShowInfoSummary=Default true, Info-summary after creating an info on/off.

****************FullCPUusing**************

FullCPUusing=Default True, available CPUs are loaded maximally , setting to "false" reduces the load.

****************OptimizeInfoOut*****************

OptimizeInfoOut=Default True, optimizes the sending of Infos before the confirmations of the clients are handled.

****************SendOkAlwaysToClient******************

SendOkAlwaysToClient=Default FALSE!, if there is no active Info, an "OK" package is not sent to the Infoclients in order to reduce load.

****************ShowConnectionFilterIfCountGreaterThan*****************

ShowConnectionFilterIfCountGreaterThan=Default 1000, if there are more connections than the default, a filter is shown first when accessing the overview of client connections.

****************UseCustomCharset**************

UseCustomCharset=Default true, to handle with Unicode in the web interface, necessary to enable "backwards-compatibility".

****************DCVCount*******************

DCVCount=Default 5, Number of empty rows at the configuration of dynamic infoclientvalues at the Inifile export.

***************ADUsername*************

AdUsername=Default empty, default value of the username to access the Infoserver's native domain.

**************AdPassword**************************

AdPassword=Default empty, default value of the password to access the Infoserver's native domain. Password is encrypted.

**************AdminDisplayName**************

AdminDisplayName=Default Admin, display name of the admin in the Infoclienthistory.

*************AutoupdateBandwidth****************

AutoupdateBandwidth=Default 0, value in KByte/second which regulates the bandwidth of the Autoupdate.

**************NotAutoupdateGroupID*************

NotAutoupdateGroupID=Default -1, ID of the Not-Autoupdate Group.

**************NotMainAutoupdate****************

NotMainAutoupdate=Default 0, allow main Autoupdate =1, or not =0.

***************MaxAutoupdates*************

MaxAutoupdates= Integer value for maximum number of simultaneous Autoupdates.

***************AdminDefaultInfoFilter********

AdminDefaultInfofilter= ID of the default-Infofilter of the Admin

***************NotAllowedDuplicateUserList*******

NotAllowedDuplicateUserList=true/false (false=default) If set to true, then per User only one Infoclient will be allowed in multiple Terminal-Sessions.

***************NotAllowedDuplicateComputerList********

NotAllowedDuplicateComputerList= Comma separated list of computers, for which the setting NotAllowedDuplicateUserList exclusively applies. Computers must be defined with prefixed domain, e.g. CORDAWARE\wts_srv_arp32,CORDAWARE\wts_srv_arp64

***********FTPPort************

FTPPort=821 (default=821) FTP-Port for the content management over FTP.

***********FTPActive***********

FTPActive=true/false (default= false) Defines, whether FTP ist activated or not.

****************ReleaseAsDefault*******************

ReleaseAsDefault=false (default) / true, Preselection of the "Release" option when creating a new info.

*****************ShowRelease*******************

ShowRelease=true (default) / false, defines, if the option "Release" is to be shown when creating a new info.

*************MailToInfoReleaseAsDefault*************

MailToInfoReleaseAsDefault = false (default) / false, defines how incoming MailToInfo emails are to be handled, if the release as ticker option (Enabled=1/0) is not set in the email.

******************BackupTime*********************

BackupTime=60 (default), time intervall for the automatic backup in minutes.

******************BackupPath*********************

BackupPath= C:\...\Cordaware\Infoband\Data (default), complete path to the backup directory. If empty, then the Data folder in the installation directory of the Infoserver is used.

****************BackupFolderFormat****************

BackupFolderFormat=dd.mm.yyyy hh_mm_ss (default), datetime format for naming the backup directories, wrap additional words and characters in quotation marks " ".

*******************BackupOn**********************

BackupOn=true (default), false deactivates the automated backup.

*************ReportPort**********

ReportPort=808 (default=808) Port of the Report Generator.

*************ReportserverOn***********

ReportserverOn=true/false (default=true) Defines, whether the Report Generator is switched on or not.

**************EditInfoClassic************

EditInfoClassic=true/false (default=false) true activates the classic Infoeditor. By default, the Infoeditor runs in Tab Mode.

**************DBSessionTimeout*********

DBSessionTimeout= (default=30) Integer value in seconds, which signals a timeout of the database.

***********MaxClients**********

MaxClients= Integer value, defines the maximum number of Infoclient-connections accepted by the Infoserver.

*******************DBServer**********************

DBServer=true (default), false: defines, whether the Infoserver is the main Infoserver (true) in a Servergrid, or a subordinate Infoserver.

******************DBAddress**********************

DBAddress=Computername or IP address of the main Infoserver in a Servergrid, value is only mandatory for subordinate Infoservers.

********************DBPort***********************

DBPort=16000 (default) TCP/IP port of the database of the main Infoserver in a Servergrid, value is only mandatory for subordinate Infoservers.

******************DBAliasPath*********************

DBAliasPath= Local path to the database directory of the Infoserver. By default, this is the "Data" directory in the installation directory of the Infoserver, e.g. C:\Program Files\Cordaware\Infoband\Data. If needed, the database directory can also be moved to a different directory or drive, e.g. E:\CordawareDB\Data. When setting up a subordinate Infoserver in a Servergrid, then this value is mandatory. In this case, you must also use the local path of the database on the main Infoserver.

********************DBMaxRam********************

DBMaxRam= (optional) Value in whole numbers for reserverd memory in MB for the Infoserver database. By default, the Infoserver uses 50% of built-in RAM for caching the database. In case this is not sufficient, then the reserved RAM can be increased with this option.

******************DBTempStoreSize*****************

DBTempStoreSize= (optional) Value in whole numbers for the maximum database size in MB. Please mind: if this value is set too low, then the Infoserver can not operate.

******************DBTempStorePath*****************

DBTempStorePath= (optional) Directory for the temporary database tables. By default, this is the directory Temp in the installation directory of the Infoserver.

***************LDAPsamAccountName***************

LDAPsamAccountName= Possible values are samAccountName and UID (Novell only). If left empty, the account-type will queried from the domain.

******************LDAPRootDSE********************

LDAPRootDSE= Enables the specification of the mount-point of the AD. Value must be submitted in LDAP-Syntax, e.g. DC=cordaware,DC=com. It is also possible to set an OU as mount-point, e.g. OU=germany,DC=cordaware,DC=com.

********************LDAPOnly*********************

LDAPOnly=false(default)/true: If the value "true" is set, then only LDAP functions will be used for domain queries. If empty or false, then AD proprietary functions will be used if LDAP functions fail.

*************AntiFreezeInterval*************

AntiFreezeInterval= (default=30) Integer value in seconds, defines the timespan after which the Infoserver will start to perform a rollback on occurance of an operation-timeout.

*****************DomainListOfServers***************

DomainListOfServers=bdc1,bdc2,bdc3: List of domaincontrollers. List is processed from first to last item, the first domaincontroller to accept a connection then will be used for domain queries.

************InfofilterRows************

InfofilterRows= Limits the number of Infos displayed in the overview of Infos to the here specified integer value. Must be larger than 10 to become effective.

********************InfoSameSize*******************

InfoSameSize=true(default)/false: Defines, whether all Infos are to be displayed with uniform font-size or not in the Info overview and Infohistory.

************TSHaltGroup*************

TSHaltGroup= Name of an Infoserver group, for whose members the Infoserver will halt the Infoclient in Terminal Sessions.

************LogonGroup**************

LogonGroup= Name of an Infoserver group, whose members can login in the profile of the Admin user.

************ParentLogonGroup*********

ParentLogonGroup= Name of an Infoserver group, whose members can login in the profiles of their Child-Powerusers. Therefore, for Powerusers who are not members of this group, this function is automatically disabled.

************AuditOn****************

AuditOn=true/false (default=true) Defines, if the Audit-Mode of the Infoserver is switched on.

************AuditdetailOn************

AuditdetailOn=true/false (default=true) Defines, if the Infoserver is to protocol detailed information while running in Audit-Mode.

************AuditResolveHostOn*******

AuditResolveHostOn=true/false (default=true) Defines, if the appropriate hostname belonging to each protocolled IP address is to be resolved and saved with each action while running in Audit-Mode.

************MoveToHistoryOneDayLater*********

MoveToHistoryOneDayLater=false/true (default=false). Defines, if Infos are to be moved to the History at 12pm the day after the Info was activated. By default, Infos are moved to the history at 12pm on the day they were activated.

**************APIReleaseAsDefault*************

APIReleaseAsDefault=true/false (default=true) Default setting for the release of Infos created in the Infoserver by the API.

******************RSAKeyLen*****************

RSAKeyLen=1024 (default=1024) Bitlength of the encryption-key used for the login to the Infoserver administration page. The RSA key is generated anew each time the Infoserver is rebooted. Generating the RSA-key with 1024 bits length consumes about 10 seconds during the boot-process. When doubling the bitlength, then this will increase the generating-time by a factor of eight.

*************InitScriptvarOnCopyInfo***********

InitScriptvarOnCopyInfo=true/false (default=true) This option defines, which value is to be used for ScriptVars when copying an Info. When set to true, the ScriptVar value of the copied Info is going to be used, otherwise (case false) the default value of the ScriptVar will be used as defined.

**************DistinctInfoCount*************

DistinctInfoCount=true/false (default=false) Defines whether the absolute number of recipients is to be displayed in the overview of Infos (va_distinctinfocount=true), or, next to the absolute number, the sum of recipients is to be displayed as well (va_distinctinfocount=false).

*********ShowInfoCountsAfterInfoSaved*********

ShowInfoCountsAfterInfoSaved=true/false (default=false) Defines whether the recipient numbers are to be displayed or not in the overview of Infos, that is displayed instantly after saving a new Info. This option affects only the standard overview of Infos and is only temporarily valid immediately after creating a new Info. This setting is useful, when several Infos are to be sent to a larger number of users in a short period of time.

****************ForceFailSafe****************

ForceFailSafe=false/true (default=false) This option raises the level of security for the database consistency with enhanced protocolling. Usually, this option can remain disabled, but is recommendable for systems which are generally instable, for example due to hardware malfunctions such as defective harddisks or RAIDs.

***************ProcessPriority****************

ProcessPriority= idle,below_normal,normal(default),above_normal,high,timecritical With this option, it is possible to influence the process priority of the Infoserver threads.

**************TextIsEmptyHtmlTags***********

TextIsEmptyHtmlTags=

***************HeartbeatInterval*************

HeartbeatInterval=10(default) Internal communication-interval between database and Mainserver, respectively Clientserver (ServerGrid), in seconds. Default value is 10 seconds. If the respective Infoserver registers that the connection to the database was lost after the heartbeat interval has passed, then a new connection will be opened. If the option RestartOnLostCommunication=true was set, then the Infoserver will re-start.

*************OverlappedGroupAllowed*********

OverlappedGroupAllowed=false(default),true With this option you can define, if a Poweruser is able to send Infos to groups which were allocated by the Admin and not by its parent Poweruser and which are outside of the recipient-base as defined in the parent profile.

***********DomainPasswordCheckOnly*********

DomainPasswordcheckOnly=false(default),true With this option you can define, that the login procedure for Powerusers will only check the submitted password only against the appropriate AD object (no local user accounts).

**********RestartOnLostCommunication********

RestartOnLostCommunication=false(default),true With this option you can define, that a Clientserver in a ServerGrid will always perform a re-start after it has lost its connection to the Mainserver and its database.

********ServerGridSendMaxReceivedCount******

ServerGridSendMaxReceivedCount=500(default) This option is only effective on Clientservers in a Servergrid. With this option, you can define the sum of acknowledgements sent by the Infoclients after receiving an Info, which causes the Clientserver to send the recipient-list instantly to the Mainserver. If the number of recipients of an Info does not exceed the defined sum, then the Clientserver will send an updated list in an interval of 10 seconds.

********ServerGridSendMaxReceivedValue******

ServerGridSendMaxReceivedValue=524288(default=>500KB) This option is only effective on Clientservers in a Servergrid. With this option, you can define the file-size of the Info recipients in Bytes. If the file exceeds the indicated size, then the recipient list will be sent instantly to the Mainserver. Otherwise, the Clientserver will send the updated recipient information in an interval of 10 seconds.

************InfoSameSizeValue**************

InfoSameSizeValue=4(default) With this option you can define the font-size (HTML format, values 1-7), which will be applied to all Infos in the Info Overview in case the option InfoSameSize=true is set.

7.2.3 Detailed Systeminfos

When accessing the item Info from the Help menu in the main-navigation of the administration-website, the Infoserver will display extended and detailed information on important system and runtime values.

7.3 Server Update and Relocation 7.3.1 Server Update

General Information

An update of the Infoserver may become necessary, if a major or minor release of the Infoserver is available. When updating the Infoserver, the file Infoserver.exe will always be affected. In conjunction with this alteration, in general the configuration-file Infoserver.ini and the database will experience some updates as well. By running the installation-file of the version of the Infoserver to which you want to upgrade, all operations will be performed automatically.

Performing the update

For performing the update of the Infoserver, please proceed as following:

1. Create backup copy (optional)

Creating a backup copy of the Infoserver is not mandatory, yet we recommend to do so, because it allows to easily perform a rollback to an earlier version. For creating the backup copy, it is necessary to first stop the Infoserver. Then copy the entire installation directory of the Infoserver to your desired backup directory. The Infoserver must be stopped before copying, in order to assure the consistency of the database.

2. Run installation file of the new version

Now run the installation file bestinformed.exe of the new version (minor or major release). Select the component Infoserver and complete the installation process as instructed. The installation routine now will update all affected files and perform necessary changes to the database automatically. Existing records in the database will be adopted automatically, it is not necessary to import previous database records, e.g. from a backup.

7.3.2 Server Relocation

Following approach is recommended when relocating the Infoserver:

1. Copy the installation directory to the new location

Copy the entire installation directory of the Infoserver (e.g. folder C:\Program Files\Cordaware\Infoband) to the new computer into the appropriate path and directory. It is necessary to apply the same path, which is the folder Cordaware in the default program directory. Please mind, that the path on the new computer is not necessarily completely identical, as for example the drive-letter may be different or the default program directory of the operating system may have a different label, eg. Program Files(x86) instead of Program Files. Also, it is important to halt the Infoserver before copying, in order to provide consistency of the database.

2. Run installation-file bestinformed.exe

After the installation directory was copied to the new location, it is now necessary to run the installation-file bestinformed.exe. The installation routine now will register the Infoserver to the Registry and all necessary alterations in the configuration of the Infoserver will be performed in order to provide its instant operability.

3. Switch Infoserver address

When relocating the Infoserver, its IP address, respectively its computername will change. This change also must be communicated to the Infoclients.

3.1 Infoserver address as DNS-alias

In case you are using a DNS-alias for the Infoserver and this alias is set as address in the Infoclient configuration, then you will only need to remap the alias to the new IP address in your DNS.

3.2 Infoserver address without DNS-alias

In case you are not using a DNS-alias for the Infoserver and/or the Infoclient configuration uses the IP address or the computername of the Infoserver as address, then you will need to reconfigure the address in the Infoclient configuration by sending an Inifile-Info with the appropriate information.

7.4 Web Interface

The administration of the Infoserver is operated through a web interface. To acces the web interface, you can click on the Infoserver's tray-icon in the taskbar. The quick configuration opens. Now click on the hyperlink configure in order to open the web interface. Alternatively, to access the web interface, you can enter the computername and Infoserver port in the address field of your browser.

Example: http://Infoserver:800

7.4.1 Login

When accessing the administration website, the page requires a username and a password, which you have defined during the Installation of the Infoserver.

On the login-page, you can select the language of the website. Currently, languages English and German are available.

IMPORTANT NOTICE OF OPERATION: The links on the Infoserver webpages do not require any confirmation. For example, if you click a delete hyperlink, the relevant item will be deleted without asking for a confirmation! If you delete groups from the Infoserver, and these groups are assigned to an Info, then these groups will also be deleted from the list of recipients of the respective Info. If, after deleting a group, an Info is without an assigned group, then the Info will be deleted too! Also, a deleted group is deleted from any other user's accumulation of groups. An Info without an assigned group is orphaned and wont't be displayed any longer. Deleting a group effects the deletion of all users assigned to this group.

7.4.2 Session length

Due to security reasons, the length of a session is limited. After a defined interval, you will be automatically logged out. In this case, you will have to relogin.

How to edit the default setting

The default setting for the duration of a session is 30 Minutes.

You can change this setting as follows:

1. Open the file Infoserver.ini in the installation directory of the Infoserver

2. Edit the value of the item SessionTimeout=

The value has to be numeric and defines the session-length in minutes.

For Example, if you set SessionTimeout=60 the session will time out after 60 minutes.

Notice: If the session has timed out while you are working, then the Infoserver will automatically perform your last action. This way, you don't have to repeat previous actions.

7.5 Licence

For replacing the current licence key (e.g. when upgrading or after trial version expires), please proceed as following:

1. Stop the Infoserver.

2. Open the installation directory Infoband of the Infoserver.

3. Copy the new licence-file bestinformed4.regkey to the installation directory.

4. Restart the Infoserver.

Notice: We recommend, not to overwrite the expired or old licence key, but to rename it (e.g. bestinformed.regkey.old) before copying the new licence key into the installation directory. This way, the obsolete licence won't get lost.

7.6 Database and Backup

The Infoserver's internal database is a NexusDB, a transactional SQL:2003 database. The database collects all data registered in the Infoserver, like e.g. Infos, Templates, Groups, Powerusers or Surveys and their Results. With the help of the Report Generator, you can access the existing data stored in your database and create your own evaluations and statistics on the use of bestinformed. The tables of the database are stored by default as *.nx1 files in the folder Data in the installation directory of the Infoserver. It is well possible to alter the location of the database by editing the item DBAliasPath= in the Infoserver.ini.

Important: Choose only local harddisks as location of the Infoserver database! Choosing a network drive as location of the Infoserver database will definitely lead to a performance loss!

In case a virus-scanner is active on the Infoserver, then all database-files must be excluded from the scan-routine, otherwise you will also experience a performance loss of the Infoserver.

Tool: NxEnterpriseManager

In case you need to have a look at the inventory of the database, then you can use the NxEnterpriseManager for accessing the database. The NxEnterpriseManager is located in the folder Web/Infoband/Users/Admin/Tools/ in the installation directory of the Infoserver.

When running the NxEnterpriseManager, it will automatically search for available Infoserver databases in your network. These databases are listed in a tree-structure.

By expanding the structue, you can access the individual tables.

ODBC access to the database

In case you want to access the database with a third-party application, then you will need to install the appropriate ODBC driver. You can find this driver in the folder ODBC in the installation directory of the Infoserver.

When accessing the database, please keep in mind that the Infoserver database uses the alias bi.

Notice: Further information on the database can be found in the official documentation of the software producer. Modifications of the database via NxEnterpriseManager or other programs are at your own risk!

Backup Database

For backing up your Infoserver data, Cordaware bestinformed offers the possibility to perform this backup in a self-defined interval.

Important: Please mind, that the backup function will make a copy of the Data folder in your installation directory. The Data folder contains all data except script results (Remote Access), Autoupdate data and filegroups. These exceptions have to be backed up manually.

Configuring the automatic backup

The configuration of the automatic backup is made in the file Infoserver.ini in the installation directory of your Infoserver.

For configuring the backup, open the file Infoserver.ini and edit following items:

BackupTime=

Here you can define the intervall in minutes, in which a new backup is to be made. Default value is 60, this means that every 60 minutes a backup will be created.

BackupPath=

This item defines the path to the directory, where the backup is to be stored (e.g. BackupPath=c:\cordaware\infoband\backup). If no BackupPath is defined, then the backups will be stored in the Data folder in the installation directory of your Infoserver.

BackupFolderFormat=

This item defines the format for naming the single backups. Every backup is stored in a separate folder. By default, every backup folder is named by date in the format dd.mm.yyyy hh_mm_ss. In case you want to add words or characters, then these have to be wrapped in quotation marks. Please note, that the foldernames only may contain characters which are valid in Windows.

Example:

BackupFolderFormat="Backup on "dd.mm.yyyy hh_mm_ss

Notice: If you choose the current day only (dd) for naming the backup folder, then please mind that it will be overwritten the following month, because the Infoserver then will only create folders named 1 to 31!

How to utilize the backup data

In case you want to use the data stored in the backup folders, you will need to halt the Infoserver and copy the data from the relevant backup folder into the Data folder in the installation directory of your Infoserver.

Attention: This will overwrite all current data stored in your Infoserver!

After you have copied the data from your backup, you can restart your Infoserver.

8. Infoclient General

The Infoclient receives new messages from the Infoserver and is displaying these on the screen.

Datatransfer

The size of transfer between Infoserver and Infoclient depends on the message size.

The query data when connecting to the Infoserver sums up to about

Infoclient -> Infoserver 100 Byte

and

Infoserver -> Infoclient 30 Byte (without messages).

After the connection was set up, the Infoclient will only send KeepAlive packages (one at a time) in a defined intervall.

Winlogon & Userdesktop

It is possible to display messages on the userdesktop (e.g. if a user has logged onto the computer) as well as on the WinLogon screen (WinNT or higher), i.e. if the computer is locked or no user has logged onto the computer (this also applies to Terminalservers).

Infos that are displayed on the WinLogon screen are visible to everybody.

A few examples:

Info on Winlogon and Userdesktop:

If no user has logged on, the Info will be displayed on the WinLogon screen. If an user now logs on, he will continue to see the message, presumed he is a member of the group to which the Info is assigned.

Info on Winlogon:

If no user has logged on, the Info will be displayed on the WinLogon screen. If an user now logs on, the message won't be displayed anymore.

Info with WinLogon and Userdesktop and certain group:

If an user is logged on who is not a member of group, the message won't be displayed to him. If no user is logged on, the Info is visible on the WinLogon screen.

Attention: If now an user logs on, who is not a member of the recipient-group, he will see the info on the WinLogon screen.

See also chapter Quickstart.

8.1.2 Autoinstall

With the Autoinstall function, you can easily and quickly install Infoclients throughout your entire network, without the need of any further distribution software. You can install the Infoclient to all computers of one domain, as well as on single computers. A useful side effect is, that you can instantly see, on which computers the client already is installed.

8.1.2.1 Configuration

Activation and deactivation

The Autoinstall function is activated by default. To deactivate the function, open the configuration file Infoserver.ini in the installation directory of the Infoserver and set Autoinstall=false. In case you want to reactivate the function, proceed analogously and set Autoinstall=true.

Providing the installation file

For the autoinstallation of the Infoclient, you must deploy the installation file bestinformed.exe in the folder Autoinstall in the installation directory of your Infoserver.

Important: The directory which contains the installation file, must be a network share of the user-account, under which the installation is performed (e.g. \\anypc\$admin).

Further settings in the Inifile

For a further configuration of the Autoinstall function, the Inifile contains following items:

AutoinstallInterval=5

and

AutoinstallScaninterval=10

AutoinstallInterval

With this item, you can define the timespan between the Infoserver's installation routines in minutes.

The installation routine is called every 5 minutes by default. If you want to change the interval, simply enter the corresponding number value.

AutoinstallScanInterval

With this item, you can define the timespan in minutes, after which the server will scan the network for newly registered computers. This scan is initialized every 10 minutes by default. If you want to change this interval, simply enter the corresponding number value.

Example:

AutoinstallInterval=5 AutoinstallScanInterval=3

Using this setting, the server will initialize a network scan to register any changes every 3 minutes. Every 5 minutes, a new installation routine will be initialized.

8.1.2.2 Implementation

Notice: In order to run the installation routine on the client, the client must be operated by Win NT 4.0 or higher.

Please proceed as following in order to install the bestinformed Infoclient in your entire network:

1. In the main menu, select Clients > Autoinstall.

2. Now click on the hyperlink New Autoinstallation on the top right of the Autoinstall overview.

3. Select the type of installation, i.e. whether you want to run an installation or a deinstallation routine.

4. Enter a description if necessary.

5. If desired, you can install a predefined Inifile on the client along with your regular installation. This enables you, to define certain default settings at once and to distribute them automatically, without the necessity of having to edit each single Inifile for each client. Just copy your predefined Inifile-text into the designated textfield. If you leave the textfield blank, the default Inifile will be used.

6. Your next option is to include a Infoclient.inf syntax to define further settings, e.g. the installation path on the client. You can use the Infoclient.inf file in the NetInstall directory in the installation directory of the Infoserver as a sample.

Please note: During client installation, a new item is also added to the start-menu of the client computer by default. If you do not want the item added, please write the following in the field for the .inf file:

7. Now click on Save.

8. Click on the link edit in the Computer column of your newly created installation.

9. Now you have the possibility to set a filter for your domain request. (You can find a description of the syntax in the chapter Autoinstall > Filter). If you don't want to set a filter, leave both input boxes empty).

10. Click on Filter in order to get to the computerlist.

11. Select the desired domains and computers and enter the username and password of the administrator of the respective domain.

You can either choose domains on the left hand side or single computers on the right hand side.

Important: If you select a domain, then all computers of this domain will automatically be selected.

Enter the domain's, respectively the computer's, administrator username and password. When selecting a domain, it is necessary to enter the administrator's username and password only once in the corresponding field.

Enter the administrator password for the domain.

12. Click on save, you will return to the Autoinstallation overview.

13. Clicking on the Start button will initialize the installation routine.

Clicking the link Refresh enables you to call the current status of your network installation.

It is possible to simultaneously run several installation routines.

Installation projects can be moved to the history by clicking on the move hyperlink in the column to history. Clicking the hyperlink show history enables you to view previous projects again.

Important notice: If you receive the error message overlapping IO pending in process, then this indicates active firewalls!

8.1.2.3 Filter

Filtering domains and computers

The first filter option is available to you by clicking on edit in the Autoinstall overview.

If you are already in the domain overview, it is possible for you to create or add a new filter by clicking on the filter link. Select your desired domains, respectively computers, and click on save. You can repeat this procedure as often as you like by clicking on edit again, creating the appropriate choice of domains/computers and saving this selection. This selection will be added to the already existing domains/computers.

The filter:

The filter offers several options:

1. Scanning the network

Scans the entire network. All domains and computers will be listed. Depending on the size of the network, this could take a few minutes.

2. File

Reads out a file with domain and/or computernames.

The file-syntax must be in the following format:

[Domain] Computer 1 Computer 2 ...

Enter the path to the file into the textfield (e.g. C:\Programs\Cordaware\Infoband\Autoinstall\Computers.txt).

3. Domaingroup

Here you can filter the domaingroups and OUs. Format for domaingroups is domain1\group1;domain2\group2;... In case you want to filter for computers in an OU in your AD/directory service, then you will need to specify the organization-unit in LDAP syntax: OU=Desktops,OU=Location,DC=ThirdLD,DC=SecondLD,DC=TopLD

4. Domain and Computer

Here you can enter domains and computers. It also possible to use the * and ? wildcards.

5. No Autoinstall for computers in group

Here you can select a group, which will be excluded from the Autoinstallatio routine. The members of this group need to be defined using the Computername.

Wildcard syntax:

Using the "*" will substitute any number of any characters, the "?" will substitute exactly one character.

Example 1:

You would like to find all computers in all domains with computernames including the characters cw.

Enter the following:

Domain: * Computer: *cw*

Example 2:

You would like to find all computers that begin with ax and reside in all domains beginning with BW.

Enter the following:

Domain: BW* Computer: ax*

All filter-rules are logically AND connected.

If you're not able to filter all desired computers in a single step, it is advisable to perform the autoinstall several times with individual filter-rules.

Example 3:

You want to install the Infoclients on all computers except servers. The servers are defined as an Infoserver group by using the Computername (eg. srv_*). You now can exclude these servers by selecting the group from the dropdown menu No Autoinstall for computers in group.

8.1.3 Autoupdate

The Autoupdate module of bestinformed automatically updates all clients in your network, as soon as a new version is available.

When an Infoclient connects to the server and recognizes that a new version is available, then the client automatically will download the file and update itself.

This module helps you save time, which would be spent on manually updating the Infoclient, i.e. creating a script which would automatically update your version.

Activating and deactivating the Autoupdate function

Important Notice: The Autoupdate function is deactivated by default. To activate the function, please proceed followingly:

Open the configuration file Infoserver.ini in the installation directory of your Infoserver and set Autoupdate=true

To deactivate the function, proceed analogously and set Autoupdate=false

Providing a new version

When a new version of the Infoclient.exe is available, you must deploy it in the folder "web/autoupdate" in the installation directory of your Infoserver.

Performing the Autoupdate

After activating the Autoupdate in the Inifile, the Autoupdate process can be switched on in the Browser.

Clock on the Setup hyperlink for further configuration options, e.g. bandwith or alternative Autoupdate servers.

More information can be found in the following chapter Alternative Servers.

Important notice: By switching on the Autoupdate, the process starts immediately without further confirmation!

8.1.4 Alternative Servers

If necessary, it is possible to set up one or more alternative servers for the Autoupdate process. If the Autoupdate then is started, certain clients will be provided with the installation-file from alternative servers. This way, the network load can be balanced between different servers.

Important notice: If an alternative Autoupdate server is not accessible by an allocated client, this client will automatically query its installation-file from the main server!

Implementation of alternative servers

Please proceed as follows, to set up an alternative Autoupdate server:

1. Select Clients > Autoupdate in the main menu of the Infoserver administration.

2. Open the Setup and add your alternative servers.

Configuration

Bandwidth per Autoupdate (main server)

Here you can reduce the bandwidth of the file transfer. Enter the preferred value in kbyte/s.

Notice: This setting relates only to the main server and refers to one Autoupdate process (one client)!

Number of Autoupdates at the same time

Here you can define the maximal number of simultaneous autoupdates. (Main and alternative servers).

No Autoupdate of clients in group

On demand, you can exclude some clients from the Autoupdate process.

No main Autoupdate

If this option is selected, Autoupdate will use only the alternative servers. In this way, it is possible to update e.g. single clients, or special client groups.

Tip regarding groups: It is recommended, to create special Autoupdate groups, instead of using the normal Infoserver groups!

Alternative Autoupdate server

Here you can enter your alternative Autoupdate server. If selected it will be activated.

FTP-Server or UNC-Path

If you start alternative Autoupdate, the main server copies the new version of the file Infoclient.exe into a specified path on the alternative server. From this path, the file will be copied to the client. You can either enter a FTP-Server, or a UNC-Path.

Username and Password

Enter a username and a password to access the alternative server.

Important notice: If you are using an UNC-Path, please enter the username as follows:

Domain or computer\user (Example: workstation20\carlson)

Download from HTTP, UNC or FTP

Depending on the server system, there are different ways to download the file to the client. If the server is not a webserver, it is necessary to enter the FTP- or UNC-Path of the server. If it is a webserver (e.g. an additional Cordaware Infoserver), http can be used. In this case, please enter the http-address of your specified FTP-Server or UNC-Path on the alternative server. From this address, the client downloads the file.

Example for the HTTP-Download

Download from: http://Adress:Port/Path

Username and Password

If necessary, enter a username and a password to access the alternative server.

For Infoclients in group

Select your Autoupdate group. It is recommended, to create one or more special Autoupdate groups.

You can use several alternative servers. Select the servers, you want to use for your Autoupdate and click on Save.

Remove a server

On order to delete an alternative server, select the server and click on the hyperlink delete.

Example: How to implement an alternative server

In our example we have set up two alternative Autoupdate servers:

1. Download and Upload via FTP

Both, download and upload of the file, are handled with FTP.

2. Upload into a UNC-Path - Download from HTTP

If HTTP is to be used, a webserver is required. In our example, we are using an alternative server on which a second Infoserver is installed. We have created the folder myautoupdate in the Web-directory of the Infoserver. In this case we can enter the http-address as follows: http://servername:800/myautoupdate.

Folders in the Web-directory are automatically made available for HTTP by the Infoserver.

Important notice: If an alternative Autoupdate server is not accessible by an allocated client, this client will automatically query its installation-file from the main server!

3. Switch Autoupdate On

Notice: If you switch on the Autoupdate, the Autoupdate process will start immediately on all clients (not only on the clients which are allocated to an alternative server). Other clients will automatically be updated by the main server.

If you want to exclude some clients from the Autoupdate, you have to specify them in the option No Autoupdate of clients in group. The other possibility is to deactivate the main server with the option No main Autoupdate.

8.1.5 NetInstall

As an alternative to bestinformed Autoinstall, it is possible to use any other distribution software, such as Netinstall, or the Windows Login Script function to install bestinformed throughout a network.

For this, the file Infoclient.bat is at your disposal in the Netinstall directory in the installation directory of your Infoserver.

Installation

For this installation routine, it is necessary to open the file InfoClientInstall in your Windows Server login script. This file will call the installation file Infoclientsilentinstall.bat. Please mind that the file paths must be correct in both files. Please ensure, that the indicated installation path is identical to the path included in the Infoclient.inf file, which contains the installation settings.

Before installing, you should configure the inifile for the client settings, which is included in the same directory.

Administrator rights are mandatory for the installation!

8.2 Configuration 8.2.1 Quick Configuration

The default settings of the Infoclient are to be configured in configurationfile Infoclient.ini in the directory .../Cordaware/Infoband. Additionally, certain settings can be made in the quick configuration of the Infoclient. Any changes to the settings in the quick configuration are saved to the inifile. To access the quick configuration, click on this symbol in the taskbar.

You can set following values:

Serveradress:

The Serveradress must be entered as following: http://infoserveraddress (the infoserveraddress is either the computername or the IP address of the computer on which the Infoserver is running).

Important! Please mind to enter the correct serveradress for the client, otherwise no connection can be established.

Port

Enter the corresponding port, to which the infoserver is set to.

Speed

Here you can adjust the speed of the ticker. The higher your entered value is, the slower the ticker will progress, because the entered value resembles the refresh-time in milliseconds. Due to this and depending on the operating system, non-linear jumps may appear. This means, that the intervals of the ticker-speed regulation can be irregular.

Background

Here you can set the background color of the ticker. If you choose the setting background, then the background of the ticker will adapt to the desktop color. Optically the ticker will appear on a transparent background. If the user has an image as desktop background, the background color of the ticker will be set to the background color and not be adapted to the image.

Font Type

Select your desired default font type.

Status

Displays the connection status between client and server. Must always be on OK. Otherwise you must check your connection settings.

Show in taskbar

Here you can set, if the Infoclient symbol shall be shown in the taskbar or not.

New Infos in taskbar

Here you can set, if you can access active Infos by clicking on a symbol in the taskbar (see Infogrid).

As Taskbar

Important: selecting this checkbox will let the ticker appear as a taskbar, i.e. all active applications and desktop symbols are moved down analoguely to the height of the ticker for the duration of the Info.

If you don't select this option, the ticker will hover above symbols and applications.

Align on bottom

Selecting this checkbox will align the ticker on the bottom of the screen.

Configure

Users with the corresponding authorities can access the Infoserver administration page from this link.

Save

Saves your settings.

8.2.2 Inifile

The file Infoclient.ini is located in the installation directory of the Infoclient Cordaware/Infoband/ directory. In this file, the basic settings of the Infoclient are defined. Administrators can determine whether users can modify these settings or not. Settings which are effected in the quick configuration menu, are saved in this file.

Following settings can be made in the Inifile:

[General]

Address=http://S01

Enter the infoservers address.

Port=800

Enter your desired port. Port 800 is used by default.

ShowOnTaskbar=True

Here you can define, whether the red Infoclient taskbar symbol shall be shown on the infoclient or not. Set the variable to "False" if you want to hide the symbol from the taskbar.

Taskbar=True

This setting defines whether the ticker shall be shown as a taskbar, or if the ticker shall overlap all running applications and active windows.

Speed=20

Here you can set the ticker speed. The lower your value is, the faster the ticker will progress because the value resembles the ticker progression in milliseconds.

Color=clInfoBk

The optinon Color defines the default background-color of the ticker.

Font=font type

The option Font contains the information on default font-size and font-type in hexadecimal encryption. Modifications of these settings can be made in the quick configuration menu. Click on this symbol in the taskbar and configure your desired settings.

ShowNewInfosInTaskbar=False

With this setting you can define, if the infogrid shall be displayed in the taskbar upon receiving a new info. More to this in the "Infogrid" section of this manual.

ShowOnTaskbar=True

Show Infoclient icon on taskbar

ShowInfoClientValuesOnTaskBar=False

Show Infoclientvalues icon on taskbar

ShowNewInfosMenu=True

Show menu of NewInfo icon

ShowNewInfosDoubleClickPlaysAllActiveInfos=True

Double click, on NewInfo icon, plays all active Infos, again

ShowNewInfosHint=True

Show hint of the NewInfo icon

ShowNewInfosHintText=True

Hint text of the NewInfo icon

Bottom=False

This setting defines, whether the ticker shall be shown on the bottom of the screen. If you want to display the ticker on the bottom of the screen, set the variable to True.

Channels and Clientvalus

Furthermore, the channels and clientvalues to which the client has subscribed to, as well as the specific key combinations are saved in this file.

Further Settings

Following settings can not be edited in the client quick configuration menu, but can be edited manually.

PollingTime=Seconds

If no entry is found, the default value is 10, i.e. 10 seconds.

Example:

PollingTime=120 defines that the Infoclient trys to connect to the Infoserver every 120 seconds until a permanent connection is established. After the Infoclient has connected to the Infoserver, the Infoclient remains silent and waits for Infos. If KeepAlive is set to false, then

Infoclient will connect repeatedly to the Infoserver in the defined PollingTime interval to query for new messages.

Consider:

If you change this value, you should synchronize the value of the active time of the Infos. If you set the value to 120 seconds, then the Info active time should be at least 2 minutes, otherwise some Infoclients will not inquire in this time.

ScrollAmount=1

The number of pixels for which the ticker progresses. Please mind: when entering large values, the ticker optically seems to tear apart.

DefaultUrlColor=clBlue

The default color value for hyperlinks.

Moving=true

Indicates, if the user can move the ticker.

MovingWinlogon=False

User can move the Infoband on Winlogon

WaitOnHyperLink=10

Value is in seconds. For this timespan, the ticker stops when the mouse is hovering above a hyperlink.

RepaintOnCancel=true

Indicates, whether the ticker immediately stops displaying an info, if an info is canceled by clicking on a hyperlink.

RepaintOnCancel=true

Repaint the Infoband on cancel by user, means canceled Info disappears immediately

RepaintOnServerCancel=true

Repaint the Infoband on cancel by Infoserver, means canceled Info disappears immediately

LastInfoFirst=True

New Infos appears first otherwise add on the end

LeftToRight=False

Direction, of the ticker, from left to right

UseResizeButtons=True

Buttons to resize the Infoband to half size

ResizedTime=10

Time, in seconds, to realign the Infoband after resized

Debug=True

Switch on the debug mode - create InfoclientDebug.log - helpful looking for errors

RepaintOnNewInfo=true

Repaint the Infoband on new Infos, means new Infos appears immediately

ShowTaskbarOnWinlogon=True

Show Taskbar on winlogon desktop, helpful using StatusInfos

UserDesktopOnly=True

Infoclient on user desktop only, running on terminalservers

HistorySameSize=true

Defines, if the Infos in the Infogrid are to be displayed with uniform font-size.

TimerResolution=1

Resolution of scroll timer, in ms, must at least half value of speed or 1

BottomWinlogon=True

Infoband on winlogon desktop align to bottom

ShowChannelsOnTaskbar=False

Show Channel icon on taskbar

HistoryAllowExpanding=false

Defines, if the detail-view in the Infogrid is permitted.

OffsetOnNewInfo=False

Offset in pixels on new Infos

Monitor=False

Using multi monitor pcs, Primary means the primary monitor, All means all monitors or a comma separated list of monitor numbers starting at 0, e.g. 1,2 2. and 3. monitor

OnlyQueryIfOnline=False

Connect to Infoserver only if online, helpful using laptops

IgnoreIPs=

Semicolon separated list of IP addresses which will be ignored while checking the clients online status.

DComGroupName=

If the installation folder has no execute rights, you have to insert one domain group, which has execute rights, otherwise the DComServer on clientside will not work, after using Autoupdate

AdditionalInfoServers=

List of additional Infoserver hosts or addresses, format Host:Port, NO http://, using Host without :Port, port will set to 800, separated by ; without http://. Starts new Infoclients, Enterprise Edition requiered!

PresentationOverlapped=true

Defines, if the ticker is to be displayed during active slide shows. When set to false, the ticker won't be displayed.

NoDefaultShell=False

If you use no default shell, for example, Citrix terminal server and using "published application", then set this item to true, otherwise the ticker will not be visible.

ProxyEnabled

Enabled Proxy

ProxyHost

Host or Address of Proxyserver

ProxyPort

Port of Proxyserver for SOCKS

ProxyUsername

Username, if required

ProxyPassword

Password, if required

ProxyNotUseList

Hosts or Addresses separated by ",", the proxyserver will be not used

KeepAlive=True

Connection keep alive

KeepAliveInterval=600

Time in seconds after which a KeepAlive packet will be sent to the Infoserver. With KeepAliveInterval=0, the procedure is off.

WaitOnStopTicker=

Value in seconds. By right-clicking on the ticker, the ticker will halt for the specified number of seconds. The default value is 10 seconds. When setting the value to 0, then the ticker will stop for an infinite time. By right-clicking again, you can restart the motion of the ticker. Setting the value to -1 will deactivate this function.

ScreensaverOff=true/false (default=true)

Defines, if the Infoclient is to automatically deactivate a running screensaver upon recieving a new Info.

AllowedHyperlinkClickOnWinlogon=true/false (default false)

With this option you can define, if any action allocated to a hyperlink (e.g. running a Script) in the Infotext can also be performed on the logon-screen. If this option is activated and the hyperlink refers to a website, then the useraccount "System" must have a defined default- browser.

ScriptOnlyOnHyperlinkClickOnWinlogon=true/false (default true)

With this option you can define, that hyperlinks can only perform allocated Scripts. This means, that hyperlinks to websites or files are disabled.

Edit the separator

The separator is the character string which is displayed between messages in order to separate them. The default characters are three "+".

You can use any other character instead the "+" character, or an image. If, for example, you want to use small Santa Clauses as separators at christmas time, this can be accomplished very easily.

How to edit the separator:

1. Open the info editor 2. Enter following text

[General]

Separator=new separator

If you want to insert an image, these options are available to you: If you are using Microsoft Internet Explorer 5.5 or higher, simply click on the insert image button in the WYSIWYG editor and select the corresponding image.

Note: Images which are to be inserted by the use of this button must be located in your Cordaware/Infoband/Web/Images directory.

When using a different browser than IE 5.5 or higher, simply embedded the picture by using the Minihtml syntax and entering the URL for the image.

Example: Separator=

It is also possible to embedded remote images from the internet. Click on this symbol in the Minihtml editor and enter the URL for the image.

Example: http://www.yourcompany.com/images/your_logo.jpg

3. In the details section, select the Inifile checkbox. 4. Click on save.

ShowNewInfosMenu=false

Hide the menu of the history of the Infoclient.

ShowNewInfosDoubleClickPlaysAllActiveInfos=true

Plays all active infos again on double click. The one click that opens the history is turned off.

ShowNewInfosHint=false

Switch off the hint for new infos.

ShowNewInfosHintText=YOURTEXT

For example: "Double click plays all active infos again".

8.2.3 Export Inifile

Modifications of the Inifile on the client computers can be accomplished quickly and easily from the server.

The reduction of time and work which results from this method is enormous, because you can administrate an arbitrary number of clients from one central position.

The Inifile editor

You can use the inifile editor in order to make changes to the inifile quickly and easily

1. Open the Info editor (new info)

2. Open the details and click on IniFile:

3. The IniFile editor opens.

In the first column you choose whether or not you would like to change this setting. Enter the desired value in the second column.

Example:

You would like all messages on certain clients to be displayed in cursive writing. Mark the FontUnderline box as well as the Style underline box.

Please note! Every time the editor is opened, it loads with the standard settings. So if you want to reset the Inifile setting to standard, reopen the editor and mark all of the boxes in the left column.

Sending

When you have made all the desired settings, click on insert. The editor now writes the Inifile syntax in the Info editor and performs all the necessary settings.

Now choose the desired groups and click on save. The Inifile is immediately rewritten.

Manual Editing

You can also edit the Inifile Settings manually:

1. Go to the Info overview and create a new info. 2. Enter the following syntax:

[General]

Your modifications

3. Check the Inifile box in the details section.

4. Select the corresponding groups and click on save.

Example:

You want to adjust the ticker speed.

1. Open the info editor and enter your modifications:

2. Select the Inifile checkbox in the tab Clientbehaviour section.

3. Select the corresponding groups and click on save.

8.2.4 InfoclientValues

InfoClientValues serve as an additional method for identifying an Infoclient. In contrast to channels, which address a whole group of users, clientvalues offer an individual identification. The user can create e.g. a clientvalue named "ID" and set the value to his customer number.

The query of the customer number i.e. the value of the clientvalue "ID" is then configured as a scriptfilter in a group.

This offers the possibility to spread messages targetly out of office because of the identification of the clientvalues.

In addition it can be secured, that certain messages will only be sent to users that "own" the corresponding key.

Creating a channel with ID (Clientvalue)

To create a channel with ID act as following:

1. Open the group administration by clicking Groups > Group Management 2. Select a group to which you want to add an ID to, or create a new group, e.g. "Infoclientvalues" , and click on Add in the column Scriptfilter

Modify the scriptfilter followingly:

1. Delete the comment characters in the line:

// Res := InfoClientValue('Name') = 'YourValue';

is then

Res := InfoClientValue('Name') = 'YourValue';

2. Enter a name and a value:

Example:

Res := InfoClientValue('test') = '5000';

3. Set following line as a comment

Res := true;

changes to

// Res := true;

Subscribing to ID-Channels

Important: Like "regular" channels, "ID-Channels" can be subscribed to by either clicking the tray icon or by entering a certain key combination.

Example:

Your corresponding Infomanager will forward a name and a value to you. Enter these properties as following:

1. Open the client quick configuration 2. Click on the "Edit Infoclientvalues" symbol 3. Click on Add 4. Enter name and value 5. Save > Close

8.2.5 Hotkeys

It is possible to call certain Infoclient functions via key combinations. This function comes in handy, if e.g. on your network's computers the taskbar is disabled.

To configure the key combinations, click on the symbol on the left hand side of the server address in the infoclient quick configuration menu.

Following functions can be accessed via key combinations:

1. The Infoclient quick configuration menu 2. Version and system informations 3. Subscribe channels 4. Subscribe Infoclientvalues 5. The hotkey menu 6. The infogrid (client history) 7. Restart Info 8. Login for server configuration

How to activate a key combination:

1. Select a combination of one or more modifiers and a virtual key for your desired function. Example: Ctrl + Alt + D. If you don't apply any changes, the activation of the hotkeys will remain as in the predefined combination.

2. Select the desired function from the window below.

3. Mark the checkbox Enabled

4. Click on Modify and finally on Save.

The key combinations are instantly available to you.

8.2.6 Proxyserver

If you use a proxy for external connections, you can set up the proxy settings in the inifile of the client.

Open the inifile-remote configuration

New info > details > IniFile:

Here you can setup the different proxy settings

Now click on insert, and send the info to your clients.

8.3 Infogrid

All incoming Infos are saved in a history on the client, the socalled Infogrid. The Infogrid can be accessed by clicking on the symbol in the taskbar.

This symbol only is visible if new messages were received and if in the configuration of the Infoclient the option New Infos in taskbar is selected.

After an Info has finished, it can be replayed from the Infogrid.

In the Infogrid, received Infos are listed chronologically. With each Info, it is listed who has sent the Info and who has received next to the Info text itself.

Infos that were addressed to a previously logged-in user are listed in the Infogrid as well, but the text won't be available and the Info can't be played anew.

If you want to hide the Infogrid symbol, act as following:

Rightclick on the symbol > Hide until next Info

The symbol now will be hidden and will be shown again only upon receiving a new Info. You can use this feature, e.g. if you have left your desktop and want to be informed if in your absence a new Info has arrived.

In order to facilitate the use of the Infogrid, all Infos are displayed in the same font-size by default, regardless of the font-size configured in the Info. In case it is needed that all Infos in the Infogrid are displayed in their original font-size, then this feature can be disabled by sending an Inifile-Info. For disabling the uniform font-size display, please proceed as following:

1. Create a new Inifile-Info.

2. Set following text in the WYSIWYG editor:

[General] HistorySameSize=false

3. Save and send the Infile-Info.

For enabling the uniform font-size again, simply send an Infile-Info and set the value HistorySameSize=true.

By clicking on the + symbol in front of each Info, you an expand the detail-view of the Info.

If the detail-view is not desired, then you can disable it by inserting HistoryAllowExpanding=false in the Inifile of the Infoclient.

8.4 Connections

To access the view of the current connections, select Clients > Connections curent in the main navigation of the Infoserver administration page.

Here you can see a detailed overview of all current connections of the Infoserver. Shown are the domain, username, computername and IP-adress and language of the client, as well as the time at which the connection was established.

Right to the connection time, the Infoclientvalues and dynamic Infoclientvalues (requires Enterprise Edition) of the clients are listet. These values are inscribed into the inifile of the client.

8.4.1 Filter

When there are a great number of connections, it is possible to filter the indicated connections when, for example, you only want to see the connections of one branch office or one department.

Click on the link filter in order to get to the configurations of the filter:

1. Configuring filters

You can set the filter to all criteria that are indicated in the connections overview.

If, for example, you only want to see whether the user Smith is online, enter "Smith" as the username and * in all the other fields.

Syntax:

- * means any number of arbitrary characters - ? means any arbitrary character

Example: This filter shows all computers that have names containing "cw", have a language beginning with "d" and that were connected with the server on the 25th.

2. Displaying filter first

In the case of very large networks with several thousands of clients, it is advisable to view the filtering options before the connections overview. This way, you have the possibility to only display certain connections, without having to wait until your browser has made all the connections. In addition, you can access the desired connection in order to, for example, send a quick info.

Settings

In the inifile, you can change the setting that indicates as of which number of clients the filter is shown before the overview of connections.

Open the infoserver.ini file in ...\Cordaware\Infoband and choose the entry:

ShowConnectionFilterIsCountGreaterThan=1000 and enter the number of your clients.

The default setting is 1000. This means, if you have 1000 Connections or more, the filter configuration is displayed before the connections.

You can now enter your filter options. If don't want to set a filter, simply click on Filter to indicate all existing connections.

8.4.2 Quickinfo

Here, you have the possibility of sending a message directly to the indicated user.

Choose the desired connections and click on new info to selected connections on the upper right. Now you will see the info editor and can create your message or use a template.

Important notice for the multiuser mode (requires Enterprise Edition): The sending of quick messages doesn't allow powerusers, to address users beyond their allocated groups.

Example:

Poweruser is allowed to adress user1, user2 and user3.

If he addresses now user1 and user4, only user1 will get the message.

8.4.3 Notice of receipt

In the Info Overview you can review and verify if an Info was sent succesfully. To get to the Info Overview, select it from the navigation menu or on the start page of the Infoserver administration.

In the standard view, the recipient number is shown in the field "Info". The recipient number is divided into two values:

1. The absolute recipient number 2. The sum of reciepients in the following bracket

The absolute recipient number shows the total number of users who have received the Info. The sum in brackets indicates how often the Info was received by these recipients.

An example: An Info was created with an active-time of three days (72 hours, respectively 4320 minutes) and was addressed to 80 persons. This Info was received three times by each person. The notice of receipt will show following result:

Received: 80 (240)

By clicking on the hyperlink Received, you will be presented an overview of the recipients, which is set up equally to the connection overview, but additionally you will see time and date of reception with each Infoclient.

9. Notice for Operation on Terminalservers

9.1 General

Cordaware bestinformed ® can easily be integrated on a terminalserver environment.

Installation

Run the installation file bestinformed.exe on a terminalserver, select the component Infoclient for installation and finish the installation process. After the installation is completed, the Infoclient service will be available for all terminal-sessions.

Now, in each new terminal-session, the Infoclient will start automatically for the user-desktop as well as for the logon-screen. Please mind, that an Info adressed to any logon-screen on a terminalserver will be displayed on all logon-screens on that terminalserver. All Infoclients in all sessions of a terminalserver register with the same computername and IP address on the Infoserver. Additionally, all Infoclient instances will use the same Infoclient.ini configuration file. Therefore, if any changes are made to the Infoclient.ini on a terminalserver, then these changes will apply to all sessions, individual settings on a per user basis are not possible!

Notice: When running a different shell than the Windows default shell (e.g. as is the case with Citrix), then you need to set NoDefaultShell=true in the Infoclient.ini, otherwise the ticker of the Infoclient can't be displayed. This setting can be made manually or by sending an Inifile Info.

9.2 Citrix

Please note the following when using bestinformed in combination with Citrix:

No default Windows shell in Citrix

Because Citrix uses it's own shell instead of the default Windows shell, it is necessary to set NoDefaultShell=true in the Infoclient's configuration file Infoclient.ini.

Desktopticker can't be displayed as taskbar in Published Applications

When you start a Published Application on a client, the Infoclient starts automatically, too. When using Published Application, the Infoclient can't display the newsticker as a taskbar, because only an application window will be displayed on the client. In this case, you will need to deactivate the display of the newsticker as taskbar by setting the item Taskbar=false in the Infoclient.ini.

Notice for Terminalservers with Load Balancing

If application publishing with load balancing on a serverfarm is in use, then a user most probably will have several application sessions on multiple servers. In order to avoid, that with each session of one user an Infoclient is initiated, you can configure the Infoserver to accept only one Terminalserver-Infoclient per user in total. This can be achieved by configuring the Inifile of the Infoserver:

NotAllowedDuplicateUserList=True/False (default) Per user, only one Infoclient will be accepted from the Infoserver. So, if a user already has an active Infoclient in one of his sessions, then in any additional session, no further Infoclient will be started.

NotAllowedDuplicateComputerList=DOMAIN\servername Here you can insert a comma separated list of computers, for which the setting NotAllowedDuplicateUserList exclusively applies. Computers must be defined with prefixed domain, e.g. CORDAWARE\wts_srv_arp32.

Problems with unterminated Sessions

In some Citrix environments with Published Application, it can occur that user-sessions remain active on the server, even though the user has closed the application. This is a known problem in Citrix. It can occur, that Citrix isn't able to close all background-processes that were initiated with a new user-session. In case this problem occurs with the Infoclient, then it is possible to include the Infoclient, respectively the process Progman.exe (this is the process, that initiates the Infoclient in terminal-sessions) in the list of background-processes, that will always be terminated automatically when a terminal-session is closed by the user. For this, it is necessary to edit the registry.

For adding the application Progman.exe to the list of automatically terminated processes, please proceed as following:

1. Open the Registry-Editor and search for the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI

2. Open the item LogoffCheckSysModules (type: REG_SZ) and add the string Progman.exe to the value (value is list of processes that will be terminated automatically).

Attention: Editing the registry improperly can lead to severe errors! Please be cautious and careful, when editing the registry. It is generally advisable to make a backup of the registry before any editing is performed.

More informationen on this topic can be found in the support-database of Citrix: http://support.citrix.com/ Article: CTX891671

9.3 Logon Screen

For performance and security reasons, it is advisable to deactivate the Infoclient for the WinLogon screen on Terminalservers. This can be achieved by setting the item UserdesktopOnly=true in configuration file if the Infoclient. In case you want to explicitely send Infos to WinLogon screens, see more in this chapter.

9.4 Static Display

If required, the infoband can be displayed statically on the userdesktop. In this case, the ticker won't continuously progress, but "jumps" along the whole screen width. The optical impression for the user is, that the ticker remains static for a certain time and then changes its content in certain intervals.

In some certain incidents, this can enormously decrease your terminalservers' network load.

Settings

To statically display the ticker, you have to set following options

1. Open the configurationfile Infoclient.ini in the .../Cordaware/Infoband directory. 2. Insert following line in the [General] section:

ScrollAmount=0

This value indicates the Pixelstep of the ticker, i.e. the progression-value of the ticker in pixels. Entering the value 0 implements the screen resolution.

3. Change the value of the ticker-speed in the Infoclient.ini too.

Speed=10000

This value resembles the refresh-rate in milliseconds. Value 10000 therefore resembles a refresh-rate of 10 seconds. The effect now is, that the ticker is moved every 10 seconds for the width of your screen-resolution, the ticker now is practically static.

Impact on your network

Using this setting, the network-traffic of the infoband is decreased by a factor of 1000. Factor 1000 results from the standard value of the ticker-progression of 10ms. This means, when using a screen resolution of 1024*768 and ScrollAmount=1, the ticker needs about 10 seconds to scroll from right to left on your screen.

This is now accomplished every 10 seconds.

9.5 Exclude Groups

In some cases, it may be desired that only certain users of terminal-services need to be equipped with an Infoclient in their terminal-sessions. For this, you can use the item TSHaltGroup= in the Infoserver.ini configuration file. You can assign one or more comma separated Infoserver groups to this item. Now, for the members of these groups, the Infoclient won't be available in terminal-sessions.

Black- & Whitelisting of TSHaltGroup

The function of TSHaltGroup always perfoms a blacklisting, since generally the syntax of a group definition aims at setting the membership by a positive result.

Example for Blacklisting:

program Scriptfilter; var A: Boolean; begin A:= MemberOFNTGroup(User,'Accountancy'); SetResult(A); end.

If, for example, the AD group Accountancy was imported into the Infoserver using the groupmanager, then the Scriptfilter is configured to make only those users a member of the group, for which the attribute "Is a member of the AD group Accountancy" is true.

If this group now were allocated in TSHaltGroup, then the members of this AD-group would not have an Infoclient in their terminal-sessions. This, of course, can be desired, if actually the requirement exists, that only a smaller part of terminal-services users must be without Infoclient.

In cases, in which the opposite is required, namely that only a small part of all terminal- services users are to be equipped with an Infoclient, then it is necessary to use the whitelisting method. This can be achieved by negating the logic of the group definition.

Example for Whitelisting:

program Scriptfilter; var A: Boolean; begin A:= NOT MemberOFNTGroup(User,'Accountancy'); SetResult(A); end.

In this scriptfilter, the group membership is defined by the argument, that a user actually is not a member of the AD group Accountancy. If, like in this example, TSHaltGroup is allocated with the Infoserver group Accountancy (TSHaltGroup=Accountancy), then the Infoclient will be available only to the actual members of the respective AD group.

10. Basis

In the following chapters you can find information on installing and configuring Infoserver and Infoclient, as well as an overview of the functions available in the Cordaware Basis Edition.

10.1 Info Management 10.1.1 Create Infos

10.1.1.1 WYSIWYG Editor

When using Internet Explorer 5.5 or higher, a HTML editor is available to you in your browser.

Notice: When setting the font-size, please mind that sizes 1-7 are compliant to the HTML Format for font-sizes. From size 8 on up, all size values are pixel values. The Editor as well as the preview will display font-sizes only to HTML size 7, nevertheless the Infoclient will display all font sizes correctly.

The WYSIWYG Editor offers several options for formatting the message text, inserting hyperlinks, contentlinks and images as well as lodging the message-text in multiple languages.

10.1.1.2 Minihtml Editor

To format the messages, a part of the HTML syntax is in use.

Access the Mini HTML-Editor

1. Tools > Mini HTML Editor 2. Click New Info > click the link MH to the left of the message text input field.

The use of the Mini HTML editor is recommended for those users, who use a browser other than MS Internetexplorer 5.5 or higher.

Please mind, that some views in your browser may be different from the view in the infoband.

Attention: Be careful when entering a hyperlink's url or address, if the address was inserted falsely or is not available, the ticker will come to a halt because it takes some time to inspect an invalid address.

Mini Html Syntax:

Here is an overview of the Mini HTML syntax:

B : Bold tag : Begin bold text : End bold text

Example: This is a test => This is a test

U : Underline tag : Begin underlined text : End underlined text

Example: This is a test => This is a test

I : Italic tag : Begin italic text : End italic text

Example: This is a test test => This is a test

S : Strik-through tag ~~: Begin strike-through text~~ : End strike-through text

Example: This is a ~~test~~

FONT : font specifier tag

: Font type, size and color.

- face : Font name - size : HTML style if smaller than 5, otherwise in pixels. - color : Font color in hexadecimal red, green, blue value (example: FF0000 = red) or color- name with prefixed "cl", e.g. clRed,clYellow,clWhite,...etc. - bgcolor : Background color : Ende

Examples: This is a test This is a test

P : paragraph

: Creates a new paragraph. Text can be aligned and a background color for this paragraph can be defined.

: end of paragraph

Example:

This is a test

Example:

This is a test

Example:

red background

Example:

yellow background

HR : horizontal line

: Creates a new text-line with a horizontal line as divider to the previous text.

BR : linebreak
: Creates a new text-line.

SUB : subscript tag _{: Begin subscript text} : End subscript text

6SUP : superscript tag ^{: Begin superscript text} : Ende superscript text

Example: 2³ equals 8. H₂O is water.

UL : list tag

: Begin list tag : Ende list tag

LI : list entry

: new entry Example:

Entry 1
Entry 2
- Subentry A
- Subentry B
Entry 3

SHAD : Shadowed text

: Begin shadowed text : End shadowed text

HI : hilight * : Begin highlighted : End highlighted

E : Error marking * : Begin error marker : End error marker

Special Characters These HTML-standard characters are allowed

< : smaller than > : larger than & : AND " : quotation mark : blank ™ : Trademark symbol * € : Euro symbol * § : Section symbol * © : Copyright symbol * ¶ : Paragraph symbol *

10.1.1.3 ScriptVars

Scriptvariables (ScriptVars) are wildcards in the Infotext. With ScriptVars, it is possible to create preformatted messages, in which, in general, only little text changes. ScriptVars in Infotexts are queried when saving the Info. ScriptVars are very effective in combination with templates. Predefined messages with variable content can be created and sent at once.

The syntax in the text: message text [ScriptVar=ScriptVarsName]

Example

1. Create a new info.

2. Enter your text, e.g. Breakdown of ExchangeServer at

3. Add your ScriptVar:[ScriptVar=Location]

4. Save this message as a template.

Every time you access this template for creating a new Info, you will be asked to insert a value or a text for this variable upon saving. Before sending the Info, the complete text will be display again in the preview.

Manage ScriptVars / Predefined Values

ScriptVars can be defined freely with each Info. Additionally, it is possible to create a preset of ScriptVars with default values. These values can either be fix or dynamically generated, like e.g. current date and time. The default value of a preset ScriptVar is defined in a small program script in the ScriptVar Management. You can access the ScriptVar Management from the main menu as well as from the Infoeditor:

The ScriptVar Management lists all preset scriptvariables. For creating a new preset ScriptVar, click on the hyperlink New scriptvariable. On the following page, you can set the name of the ScriptVar and define the default value per Scriptfilter.

Scriptfilter for default values

For defining a fixed default value for a ScriptVar, you can use following program script:

program Scriptvar; var Res: String; begin Res := 'YOURVALUE' // set result SetScriptVar(Res); //result must be a string end.

This code will always use the string YOURVALUE as default value for the ScriptVar in the Infotext. For the dynamic value allocation, you can also use the result of a function. Possible functions are:

Res := FormatDateTime(Dateformat,Timestamp): The function FormatDateTime() expects two parameters, namely the date-/timeformat as string and the timestamp as integer (UNIX timestamp). For using the current date or time, you can also use the expression Now instead of a specific timestamp.

program Scriptvar; var Res: String; begin Res := FormatDateTime('mm/dd/yyyy hh:mm',Now); // set result SetScriptVar(Res); //result must be a string end.

Res := Loadfromfile(Path to file): Reads the content of the specified file. The file must be provided in plain text format. The path always must be related to the Infoserver. If the path begins with a drive-letter, then this must be a local drive on the Infoserver. It is also possible to use a network path in UNC notation.

program Scriptvar; var Res: String; begin Res := Loadfromfile('C:\path\to\file.txt'); // path to file on local drive // oder Res := Loadfromfile('\\Computer\\path\to\file.txt'); // path to network share in UNC notation // set result SetScriptVar(Res); //result must be a string end.

Preservation of ScriptVars when copying an Info

If an Info containing a ScriptVar is copied, then the Infoeditor will display the ScriptVar and not the value that was assigned in the original Info. When saving the copied Info with the ScriptVar, there are two options available for the value-handling of this wildcard. The definition of which option is to be applied camn be set in the Infoserver.ini. The name of the option is InitScriptVarOnCopyInfo:

1. InitScriptVarOnCopyInfo=true: If set, then the default value of the ScriptVar (if defined) will be used as predefined value in the copy.

2. InitScriptVarOnCopyInfo=false: If set, then the value that was assigned in the original Info will be used as predefined value in the copy.

Example: InitScriptVarOnCopyInfo=false

Precondition: The ScriptVar Date is predefined, which uses the current date as default value:

program Scriptvar; var Res: String; begin Res := FormatDatetime('mm-dd-yyyy',Now); SetScriptVar(Res); end.

Create a new Info and insert the ScriptVar Date into the text:

Now click on Save to switch to the preview of the Info. The field for the ScriptVar now contains the current date as value. Edit the value and save the Info.

The Info now will be displayed on the recipients screen and in the overview of Infos.

Now click on the hyperlink copy in the row of the recently created Info. The Infoeditor will open and the previous text will be displayed, including the ScriptVar:

Click on Save. In the preview, the value for the ScriptVar Date now contains the value of the previous Info instead of the default value (current date).

10.1.1.4 Time and Environment Variables

It is possible, to use certain time and environment variables in the Infotext. These will be processed from the Infoclient and substituted through locally valid values. This offers the possibility to have customized, individual values in an Info for each user.

Environment variables

%Username%: When using the environment variable %Username% in the Infotext, then the receiving Infoclient will substitute it with the currently logged on user. However, this variable only provides the username under windows vista.

%Computername%: When using the environment variable %Computername% in the Infotext, then the receiving Infoclient will substitute it with the current computername.

%Time%: When using the environment variable %Time% in the Infotext, then the receiving Infoclient will substitute it with the current local time.

%Date%: When using the environment variable %Date% in the Infotext, then the receiving Infoclient will substitute it with the current local date.

Time variables

Next to the current local time and date on the client, it is also possible to calculate general time values of the timezone of a client. If, for example, maintenance work begins at 16:00 in one location, then another location in a different timezone needs to know at which local time they will be affected. For this, you can use the so-called UTC*-tag, which is similiar to the ScriptVar-tag:

[UTC=Date/Time(local) -Offset]

* UTC = Universal Time Coordinated, is conform to GMT at the zero meridian

Comment on syntax:

In our example, maintenance begins at 16:00 local time in Berlin. Berlin is in the timezone UTC +1, ergo the offset is +1 (UTC plus one hour). For getting from local time to UTC, it is necessary to substract the offset of one hour from the local time:

[UTC=16:00 -1:00:00]

It is also possible to use date and time (date-format dd.mm.yyyy):

[UTC=14.02.2008 16:00 -1:00:00]

In case the appropriate UTC time is known, it can be inserted directly:

[UTC=15:00]

The Infotext now contains the information, that a certain UTC-value has to be substituted by the appropriate value in the timezone of the Infoclient. If, for example, an Infoclient is in New York, then his local timezone is UTC -5. In this case, the UTC-tag [UTC=16:00 -1] would be subtituted with the value 10:00:00 by the Infoclient in New York.

The offset must be defined in the format hh:mm:ss. If the UTC offset negative (which means west of the UTC), then the offset must be added.

Example:

UTC-Tag in Infotext Display in UTC +1 (e.g. Berlin) Display in UTC -5 (e.g. New York) [UTC=12:00 -1:00:00] 12:00:00 06:00:00 [UTC=09:00 +5:00:00] 15:00:00 09:00:00 [UTC=01.03.2008 22:00 02.03.2008 04:00:00 22:00:00 +5:00:00]

10.1.1.5 Caption

The caption is a headline running in front of the message in the newsticker, which will stop at the end of the line.

The input field for the caption is on the top right of the WYSIWYG editor.

You can also use HTML for formatting the caption text. Use the Minihtml Editor, for generating the HTML code for a desired formatting. Furthermore, you can insert environment variables into your caption.

10.1.1.6 Multiple Languages

It is possible to provide the message text of one Info in multiple languages. If the recipient uses an operating system in one of the defined languages, then he will receive the message with the text intended for him.

By default, an Info is composed language-independent (All languages). If you want to set the Infotext for a certain language, then you can select this language from the dropdown menu on the top left of the WYSIWYG editor.

If the language selection is set to All only, then all recipients will receive the same message text. If you select an additional language, then the text in the WYSIWYG editor will be resetted for the selected language and you can enter a new message text. Message texts in different languages will be saved and can always be viewes by selevting the language.

Example:

An Info is to be sent to several locations in the UK and France. Open the form for creating a new message and enter the message text for All languages in English. Now select French from the language selection. The message text will be resetted, you now can enter the text in French. For reassuring yourself, select All languages again. The original message will be displayed again in the text editor. You now can proceed, make further settings and save the Info.

10.1.1.7 All-Clear function

With the All Clear function you can easily set an all-clear message for an Info and distribute this message with little effort when needed.

Predefined all clear message

The all-clear message can be defined for each language individually.

Select the laguage(s) for the all-clear messages and insert individual texts and captions in the WYSIWYG editor. You now can save the Info as template or for immediate distribution.

Execute all clear

In the overview of the Infos, the column edit contains the hyperlink all clear.

Click on this hyperlink to perform the all clear function for the respective Info. After clicking, the form for creating a new message will open. If text and caption were already predefined, then these will be displayed in the WYSIWYG editor. For addressing the recipients, the ID of the to be cleared Info will used (see chapter Recipient selection). This way, it is sensured that exactly the same recipients of the to be cleared Info will be addressed.

Clearing Scenarios (Professional Edition)

If several Infos were sent in a Scenario, then the hyperlink Scenario all clear will be displayed additionally to the all clear hyperlink in the overview of Infos. By clicking this hyperlink, all Infos of the Scenario can be cleared simultaneously. If in the templates of the Scenario all clear values were saved, then these will be displayed and they can be distributed immediately.

Notice: For succesfully using the All Clear function in scenarios, in each used template the All Clear message must be defined for at least All Languages.

10.1.1.8 Content Management

By using the Content Management, you can easily upload files to the Infoserver and link to these with a few mouseclicks in the WYSIWYG editor.

Notice: The maximum filesize is 10MB per upload.

Fileupload and -management

For accessing the Content Manager, open the menu Additionals > Content Manager or open a new Info and click on the hyperlink Cnt to the left of the WYSIWYG editor.

A new browser-window for the Content Management opens. Directories and files of the Content Management are listed in a tree-structure, the Filetree.

In the Content Management, you can manage all directories and files within the Web-directory in the installation directory of the Infoserver. By default, the Web-directory contains the subdirectories Images, Sound, Users and Web.

For linking to the contents of the directories via URL, the directory- and filename are added to the Infoserver Web-URL according to their position in the Filetree.

e.g. http://infoserver/Images/cordaware.jpg

For creating a new file or subdirectory, click on the directory in the Filetree, in which you want to insert the new content. Now, on the right hand side of the page, the available options and actions will be displayed.

Name

In the field Name you can insert a label for a directory. The label of the current directory will be used by default.

Save directory

With the button Save directory, you can edit/rename the current directory.

Delete directory

With the button Delete directory, you can delete the current directory. If the directory still contains files and subdirectories, then the operation can not be executed. This is a safety- mechanism to prevent the unwanted deletion of whole directory-contents.

New directory

With the button New directory, you can create a new directory. The label for the new directory is the value of the field Name. The new directory will be inserted hierarchically as a child-element of the current directory in the Filetree.

Fileupload

To upload a file to the current directory, click on the Browse... button and select the desired file. By clicking the Upload button, the file will be copied to the current directory.

For renaming or deleting a file, click on the respective file in the Filetree. Now the available options and actions will be displayed on the right hand side of the page.

Name

In the field Name, the current filename is displayed..

Save file

With the button Save file, you can rename the current file to the value given in the field Name.

Delete file

With the button Delete file you can delete the current file.

Notice for users of the Multiuser Mode (Enterprise Edition): Every Poweruser has a private directory in the default-directory Users. Powerusers can manage files only within their private directory. Nevertheless, when inserting a Content-Link in an Info, Powerusers can access all directories and file in the Web-directory, including all files of any other Poweruser. If a Poweruser was created in the format Domain\User, then the Users-directory will contain a subdirectory Domain, in which the private folder of the Poweruser will be located. Please mind, that the folder Domain will be generated not before the first login of a Poweruser of the respective format.

Inserting Content-Links

After a file was uploaded, it is possible to create a hyperlink to this file by using the Filebrowser in the WYSIWYG editor. For opening the Filebrowser, click on the following icon in the editor:

A new browser window will open, containing the Filebrowser.

The file-browser will not only show the uploaded files in the user-directory, but also all directories and files located in the Web-directory of the Infoserver. Click on a folder to get a listing of all subdirectories and files within.

For creating a hyperlink to a file, select the word in the editor which is supposed to be the hyperlink and then select the file from the Filebrowser. The hyperlink now will be generated automatically by the WYSIWYG editor.

Alternative: External File

You can also link to a file, which is not located on the Infoserver. For creating an external file link, click on following icon:

After clicking this icon, you can specify the path to the external file in a new browser-window.

Notice: When linking to an external file, please make sure that all users can access this file (network share). For this reason, please enter the file-location in the UNC format. When using the Browse... button, then you can specify the file by using the operating system's file browser. Nevertheless, you should make sure that the file is located on a globally equally mounted network drive.

10.1.1.9 Templates

With templates you can save once defined Infos as a master copy of text.

In combination with ScriptVars, you need to format the text only once and enter the modification only when needed.

Templates are user-dependent.

Please note: If you save a template, all settings, inclusive recipients are saved!

In the Multiuser mode, administrators can assign several write-protected templates to single Powerusers.

To grant a fast access, you can group templates.

Example: how to create a new template

Create a new Info. > Open the Details section > Set the Info's properties as desired and assign the groups to the Info (you can edit the assignment any time later).

> Enter a name for your template into the field Templatename on the bottom of the page and click on Save Template.

Templategroups

On the top left side of Info input field, click on the link Groups next to Templates (above, left).

By clicking on New Templategroup you can create new templategroups. These will be shown on the left hand side of the list.

Click on Edit templates to assign the different templates to the groups.

10.1.1.10 Default Template and Values

For a fast paced creation process, you can define a template as the default template. For this, open the form for creating a new Info and set the values (e.g. time, ScriptVars) you would like to use. Now scroll to the end of the page and save the settings as a template.

The settings are saved as template. To define this template as default template, scroll to the bottom of the page and click on the button Default template.

This template now will be used as default when creating a new Info. You can also reset the allocation as default template by clicking on the button Reset default template.

Additionally to the default template, you can also set default values in the quick configuration of the Infoserver.

10.1.1.11 Release as Ticker

The option Release as Ticker defines, if an Info is enabled for distribution or not. This option lets you decide, if an Info is intended only for display in a Shared Whiteboard, e.g. for registering current incidents, or is intended for distributing urgent messages to your clients. This option can be set individually in every new Info, it can be predefined in a template or it can be proconfigured in the Inifile of the Infoserver. For the preconfiguration in the Inifile, following definitions are at hand:

ReleaseAsDefault:

Values: true / false

Property: This entry defines, if the option Info as ticker is selected by default when editing a new message.

ShowRelease:

Values: true / false

Property: This entry defines, if the option Info as ticker is to be displayed in the form for new Infos.

MailToInfoReleaseAsDefault:

Value: true / false

Property: This entry defines, how MailToInfo emails are to be handled, in which the property Enabled is not included and therefore don't contain any information, if the Info is enabled for distribution.

Example:

The option Info as ticker is to be used always and must not be edited by any user. Infos from MailToInfo must only be distributed and displayed, if explicitly defined in the email-text. In this case, you must set your entries in the Inifile as following:

ReleaseAsDefault=true ShowRelease=false MailToInfoReleaseAsDefault=false

10.1.1.12 Active- and Displaytime

In the Quick Configuration of the Infoserver you can set default values for active and display time of an info. These values can also be set individually with each info. For setting active and display time, following parameters are available to you in the details-setting of an info:

Minutes

Here you can set the number of minutes, for which the Info will be displayed on the clients screen. Example: if you enter a "5", then the info will be displayed for five minutes on the clients screen.

Active

Here you can set the period of validity for the Info. Example: if you enter "60" as value, then the Info is valid for 60 minutes from the start of the info, clients assigned to this info, which register themselves to the infoserver in this period of time, are supplied with the info.

Begin

Here you can set the start value for your Info in the format DD/MM/YYYY:HH:MM. If you leave this space blank, then the Info will be initialized instantly. You can not set a start value, which lies in the past.

End

Here you can set the end value for your Info in the format DD/MM/YYYY:HH:MM. If you have left the "Begin" space empty to initialize an instant Info, then you must leave this space blank too. You can not set an end value which lies in the past.

Globale time

Calculates begin and end of an Info on the Mainserver into the local time on a Clientserver (only for Servergrid in Enterprise Edition). Is used for avtiavting global Infos simultaneously.

Open End

Here you can define the validity of the info to be without limitation.

Once

If you choose this option, every client will receive this info only once.

Offline

Here you can determine, if the Info shall be available to clients which are offline. For this action to take place, it is mandatory that the client must be connected at least once to the Inforserver between creation and begin of the Info. Additionally, you can define whether the time of start refers to the local server time or to the local client time. Example: if you want to send an Info to users working in a different time zone, you can define this parameter here. This option, if enabled, remains enabled even if the "Offline" parameter is turned off.

10.1.1.13 Recipient selection

In Cordaware bestinformed you have several possibilites of setting recipients of an Info.

Language

The selection of a language for defining the recipients of an Info can be found in the detail- settings of the Info.

Here you can set a language dependent filter. If you select a language, only those Infoclients will receive the Info, for which that certain language is set in the operating system profile. If you select all, then this filter is inactive.

Channel

The choice of channels for the recipient selection can be found in the details-setting of the Info.

Channels can be subscribed to by users, similiar to a newsletter.

Groups

The choice of groups for the recipient selection can be found in the details-setting of the Info.

Here you can define, to which existing groups the Info will be sent. Read here more about setting up groups.

Quickuser

With the Quickuser-function, you can send Infos to single users. When creating a new Info, you can enter one or more users in the textfield Users.

Notice: A user is always set up by a combination of username, computername and IP address divided by a ";". Several users are separated by a comma ",".

You also can substitute all properties with wildcards:

* substitutes an arbitrary number of characters ? substitutes one arbitrary character

Example:

any.user;workstation12;192.168.1.23

If you select the option These users only, without groups below., then the Info will only be sent to the users specified, otherwise the Info will be sent to these users additionally to another recipient selection.

Send Info to ID

Every Info has an ID with which the recipients of an Info are saved. If you have sent an Info to several groups, then you can send a new Info to the same recipients by using the ID of the previous Info. This is helpful for addressing the recipients of an all-clear message after a warning, e.g. a storm-warning.

For sending an Info using the ID, you will need to use the Quickuser function. For addressing the recipients of a previous Info, type following into the user textfield:

ID=XYZ (replace XYZ with the ID of the previuos Info)

Example

An Info was sent to three different groups and additionally five single users. The Info's ID is 217. To address the same recipients in a sequencing Info type ID=217 into the textfield Users and select the option These users only.

How to get the ID

When moving the mouse over a hyperlink (e.g. copy or edit) in the row of the Info, then your browser will show the hyperlink address with attached ID on the bottom of its window.

As you can see, the ID of the Info is attached to the URL of the hyperlink. The number of the ID can be used for addressing the identical recipients in further Infos.

Another method of getting the ID, is to create an Infofilter which contains the ID of an Info in an extra column.

10.1.1.14 Recurring

Ticker messages can be displayed in periods and intervals. You also have the possibility to send messages as Interval - Info's with Global Time. However, this is not possible with Periodical Infos.

I. Periodical Infos

Periodical Infos are Infos, which are displayed several times within a defined time period.

Example 1

Every Friday afternoon, all employees shall be reminded, to shut down their PC orderly.

The settings:

1. Define begin and end of the period

Example:

Begin: 24.05.2005 10:00:00 End: 24.05.2006 11:00:00

Notice: At periodical Info's, the time values refer to the active time of the Info at every appointed day. In our example, the Info is active every Friday between 10:00 and 11:00.

2. Select the option recurring.

3. Select the following check boxes:

All week(s), year and Friday in the next line

4. To get a preview of your settings click on the link period on the left.

Result: The periodical Info now is active, every Friday between 10:00 an 11:00

Example 2

On every tenth day of each month, the ticker should display an automatically message about some maintenance works. The Info should start on the tenth and be active for two days.

1. Define begin and end of the period:

Begin: 24.05.2005 10:00:00 End: 24.05.2006 11:00:00

2. Select the option recurring

3. Now, do the following configuration:

4. To get a preview of your settings click on the link period on the left.

II. Interval - Info's

With the interval-option you have the possibility, to run Info's, which are recurring periodic within one day.

Example:

A ticker message should be displayed all 15 minutes and run for 2 minutes on the screen.

1. Define begin and end of the period.

Example:

Begin: 24.05.2006 15:00:00 End: 24.05.2007 17:00:00

Depending on the period-settings (day, week, etc..), the time-period for this interval-Info is two hours. Within this time-period, the Info should be displayed all 15 minutes and run for 2 minutes on the screen. The entire active period is one year.

Notice: You can select the option open end. In this case, the entire period of the Info is active until it is canceled.

2. Select the option recurring.

3. Configure the settings of your period (days, weeks, etc...)

4. Enter your values for the interval:

Result: In our example, the entire period is 1 year. During this period, the ticker is displayed daily between 15:00 and 17:00 every 15 minutes and is active for 2 minutes. The display-time of the Info has to be set with the Minutes property.

Starting options:

There are two options to define the starting time of an interval-ticker.

a. "starts at Begin" - If this option is selected, the ticker will be displayed for the first time at the begin of the interval (in our example at 15:00)

b. "x minutes to the hour" - If this option is selected, the ticker will be displayed for the first time x minutes after the last hour.

Example: The ticker now is displayed for the first time at 15:15 and is active for two minutes. Next time it will be displayed at 15:30 etc...

10.1.1.15 Popup

The philosophy of bestinformed is to generally avoid popups, because they are very aggressive and interrupt a user in his present actions. Nevertheless, for a certain reasons, e.g. alert, warnings etc., it may be necessary to send popups. In this case, you can select the option Info as popup in the details of an Info.

Layouting Popups

To layout Popups, we recommend to use the Minihtml editor.

Fullscreen Popups

By selecting the extra option Fullscreen, the Popup will cover the whole screen.

This is a very powerful option, because in a severe situation, you can automatically lock the user's screen and instruct him at the same time. Possible scenarios are fire-alerts, extreme weather conditions, floods, earthquakes or bomb threats. See chapter Scenarios for an example of use.

Popup using Internet Explorer

When selecting the option use IE, then the Popup-window will activate an Internet Explorer instance, which will display the Infotext.

This allows you to use e.g. script-sections or to embed Flash animations.

Notice: HTML-Tags, which do not serve for formatting text or for displaying hyperlinks and images can be used only in Popups with the enabled option use IE. The HTML-code of the Info will be inserted exclusively in the body-section of the Popup.

Define width and height of a Popup window

By entering integer values into the input-fields Width and Height, you can define the dimensions of your Popup window in pixels.

Example for Popup with multimedia content

In this example, we will show you how you can include multimedia content in a Popup by applying the use IE option.

Open the form for creating an Info. Select the option Edit HTML in the WYSIWYG Editor. You now can enter HTML code into the WYSIWYG editor. Insert following example-code, for including a multimedia element:

This code will embed a Flash-object, which will display a Cordaware movieclip from a popular multimedia website.

Now deselect the Edit HTML option to return to the preview mode of the WYSIWYG editor. Now go to the tab Clientbehaviour and edit the settings for displaying this Info as Popup using IE, with a window-size of 480px width and 400px height.

Save the Info. The preview will already show the start-screen of the multimedia content. After distribution, a Popup window will open on the client, displaying the multimedia content.

Fields of application:

In security-management, it is e.g. possible to display a CCTV picture on several desktops after a motion- detector trigger.

Intra-corporate, it is e.g. possible to distribute video messages or tutorials.

10.1.1.16 Desktop and WinLogon

It is possible to display an Info either on the userscreen, i.e. if a user has logged on to a system, or on a WinLogon screen (WinNT or higher), i.e. if the computer is locked or no user has logged on to the system (this also applies to terminalservers).

Infos that are displayed on the WinLogon screen are visible to everybody!

Here a few examples:

Info with WinLogon and UserDesktop

If no user is logged on, the message will be displayed on the WinLogon screen. If an user now logs on the system, the Info will continue to be displayed, provided that the user is element of the group assigned to the Info.

Info with WinLogon

If no user is logged on, the Info will be displayed on the WinLogon screen. If an user now logs on, the message no longer will be displayed on the screen.

Info with WinLogon and UserDesktop and specified group

If an user is logged on, who is not member of the group, he won't receive the Info. If no user is logged on, the Info is visible on the screen to everybody.

Caution

If an user now logs on who is not a member of the group, he will see the message, because on the WinLogon screen an Info is visible to everybody.

Settings

To display the message on the Logonscreen, click

New Info > Details > Logondesktop - mark the check box show info.

If you want to display the message solely on the WinLogon screen, deactivate the check box Userdesktop > Show Info.

If you want to address all computers, on which no user has logged on, you have the following options:

1. Creating a group

Create a new group by the name "Logonscreen". Go to the group administration, click on new group, enter a name and a description and click on save. Now select this new group from the group overview and click on add in the username section. Now delete the * wildcard from the field username and click on save. Now you have created a group, which represents all computers on to which no user has logged on, therefore messages addressed to this group will be sent to all computers with no logged on user.

2. Using the "Users" field

When creating a new info, simply enter following value in the Users field: ;*;* Please mind, that the first character has to be the semicolon. Now the message will be sent to all computers, to which no user has logged on.

10.1.1.17 Sound

There are two methods of playing an audio signal along with an Info: Beep and Sound.

Beep

By selecting this option, you can play the standard warning signal of the computer on the receiving desktop or notebook. This is the signal, which is generated by the motherboard or built-in speakers. You can also define the number of beeps to be played.

Sound

If there are speakers connected to the computer, than you can also play a soundfile upon receiving an info.

You can deploy the sound-files in the Web directory of the Infoserver. In the "Sound" directory of your Web directory some default sounds are already included. For allocating a sound-file to an Info, you need to enter the correct URL to the sound-file.

Example:

http://infoserver:801/Sound/Siren.wav

If the option Sound only is selected, then the Infoclient won't display the message and play the sound-file only.

10.1.1.18 Tab Mode

In the Tab Mode, you can access the different properties of a setting by using the different tabs. The tabs are sorted by:

· Editor: Here you can set and format the message text. · Zeiteingabe: Here you can set start, end, active-time, display-time and periodicity. · Sound · Clientbehaviour · Infofields · Recipients: Assign Groups, Channels and Users. · Save: Here you can see a preview of the Info before saving finally.

10.1.2 Administration

Info Overview and History

By clicking on the hyperlink Info Overview in the Infoserver administration you will be directed to the overview of current Infos. In this overview, all active and recently finished/cancelled Infos are listed. After a period of 24 hours after an Info has finished or was cancelled, it will be moved to the Infohistory.

In the Info Overview, all Infos are listed in a table, sorted by descending creation date. Each line shows the text, properties and administration hyperlinks of the respective Info. By default, all Infos are displayed with the same font-size (uniform display), regardless of the Info's individual settings. For disabling the uniform display, proceed as following.

1. Open the Infoserver configuration-file Infoserver.ini.

2. Search for the item InfoSameSize= and assign the value false (InfoSameSize=false).

3. Save the Infoserver.ini und restart the Infoserver.

For enabling the uniform display, proceed simultaneously and reset the item "InfoSameSize": InfoSameSize=true. If the uniform display is active, then you can set the font-size with the item InfoSameSizeValue= in the Infoserver.ini.

From the Info Overview, you can also access the Infohistory, which displays all sent Infos in chronological order.

Infos in the Infohistory offer a detaillink. By clicking this link, all properties of the respective Info will be listed. In case the Audit mode is active, the collected data on user-activity will be displayed as well.

Edit

Only active, respectively waiting Infos can be edited. To edit an Info, click on the hyperlink edit in the row of the desired Info in the overview.

The Info form opens with all previously defined values. The Info now can be edited as desired.

Notice: if an active Info is edited, then the changes won't be displayed by Infoclients, which already have recieved and displayed the Info.

Copy

To copy an Info, simply click on the hyperlink copy in the row of the Info in the overview.

The Info form opens in which all values from the Info to copy are adopted. When saving, a new Info will be generated.

Cancel

To cancel an Info, simply click on the hyperlink cancel in the row of the Info in the overview.

Following, the Info will be canceled. Clients, which haven't displayed the message, won't display the message any more.

It is also possible to cancel an active Info and create a new copy from it. Simply click on copy and cancel and the Info form will open, all values in this form then are identical to the values in the cancelled Info.

History

For keeping your Info Overview well organised, you can move finished Infos to the Infoserver's history. For moving an Info to the history, click on the hyperlink to history.

For accessing the history, select it from the navigation menu. In the history, you can examine, copy and delete previous Infos.

Delete

For deleting an Info from the Infoserver, go to the Info history and click on the hyperlink delete in the row of the relevant Info.

10.1.3 Infofilter and Shared Whiteboard

In addition to the standard view of the Info Overview, you can create your own views, the socalled Infofilters. Also, you can create Additional Infofields, which offer the possibility to add extra input options when creating an Info, such as e.g. an incident token. These Infofields are not allocated to any function, but the possiblity to lodge additional information with an Info.

When creating an Infofilter, you can utilize all options and values of an Info, as well as all Infofields. When using the Enterprise Edition, you can also allocate Infofields and -filters to Powerusers. This enables you to set up public infofilters as an application of the Shared Whiteboard.

Administrate Infofields

In the Info Overview, on the top right corner of the table you can find the hyperlink Additonal Info Fields. By clicking this hyperlink, you can enter the Infofield administration.

For creating a new Infofield, click on the hyperlink New Infofield. The form for creating a new Infofield opens. Here you must select a name and the type and optionally insert a description.

Following Infofield types are available:

· Text: Produces a single line textfield. · Number: Produces a single line textfield for numerical values. * · Datetime/Zeit: Produces a single line textfield for datetime values. * · Email: Produces a single line textfield for an email address. * · URL: Produces a single line textfield for an URL. * · Checkbox: Produces a checkbox. · Memo: Produces a multiple line textfield for a longer text. · Combobox: Produces a dropdown-menu. Items of the menu can be defined language dependently.

* = All values inserted will be checked for type and validity.

You can now save the Infofield.

The new Infofield now is listed in the administration. For setting up an alternative language title, click on the hyperlink edit and enter the alternative translation.

If the Infofield is of the type Combobox, then you will have to define the items in each language separately. For this, a multiple line textfield is at hand. Insert every item in a separate line. To create an empty item, you must enter a blank line.

Administrating Infofilters

In the head-row of the Infotable in the Info Overview is a dropdown list of the available Infofilters, as well as the hyperlink Filter which will take you to the form for creating a new Infofilter. If currently a self-defined Infofilter is selected, an edit hyperlink is also available which will allow you to edit the currently selected filter.

The checkbox to the left of the hyperlink Filter offers the possibility, to select the currently selected Infofilter as the standard Info Overview.

Click on the hyperlink Filter in order to create a new Infofilter. The form for creating an Infofilter will open. This form consist of five basic elements:

1. Basic settings: Here you can define the name, a description and a refresh rate for the Infofilter, as well as the option if in this filter all Infos of all allocated user-views are to be displayed instantly (Enterprise Edition only, see chapter Multiuser).

2. Table header: Here you can set the background, font and border color for the table-header of the Infofilter.

3. Table detail: Here you can set default colors for the background, font and border color of the Info Overview content table.

4. Detail link: You can access a page with detailled information on an Infos properties by clicking on the detail link. This detail link can be allocated to any column in your Infofilter. The hyperlink to the detail page then will be set on the content of the respective colum.

5. Select cols: Here you can define the options, values and Infofields, which are to be the columns of the new Infofilter. Select the desired items from the list and insert, if needed, an alternative headline (alias) for the item. You can also define a custom cell-width with pixel or percentage values.

For limiting the length of a column's content automatically, you can use the option Ellipsis. With this option, the content of a tablecell in the selected column will be cut off in order to keep the set boundaries.

6. Filter: Here you can define diverse filter rules. Select the property to be filtered from the list and enter the value(s), which are to be filtered. For combining several values with a logical "OR", enter these as a comma separated list in the value text-field. Example: "value1,value2,value3" = "value1 OR value2 OR value3". If you set more than one filter rules, then these can be combined with logical AND / OR. You can use the wildcards "*" and "?" in the filter values as placeholders for any text. If you want to use the NOT logic for a certain value, than you can use the ! operator as a prefix for the desired value.

In case the available options don't serve your needs, then you can also create a socalled UDF-Filter (user defined filter). For this, select the item __user_defined_filter__ from the list of Info properties. Now you can insert your own filter-rule in the textfield which is similiar to a WHERE clause in a SQL statement.

The labels of the Info properties can be considered as fieldnames of a database table. String values must be wrapped in single-quotes, otherwise they will be considered as fieldnames, which of course won't deliver the expected result. An exact listing of operators and expressions available for the UDF-Filter can be found here.

7. Sorting: Here you can define the sorting sequence. Select the properties which are to be used for sorting and the sequence direction: ascending or descending. If you select more than one property for sorting, then the sorting options will be combined with a logical AND. If no sorting was selected, then the Infofilter will sort by descending datetime by default.

8. Format: Here you can set a background color for single columns or entire rows depending on certain values in an Info. Select the Info-property, insert the determinant value, set column or row and select a background-color. You can also use the wildcards "*" , "?" and "!" in the determinant values.

You can also apply an UDF-Filter on the formatting. Simply select the desired field, for which the formatting has to become active. Now insert UDF= plus an applicable definition as value and select the desired format.

In an Infofilter, the defined formatting will be shown in a legend at the bottom of the Infofilter.

List of properties / options for an Infofilter:

Timestamp = Datetime of creation End = End of active time Begin = Begin of active time Min = Displaytime of the Info Text = Infotext ID = Recordset ID of the Info Continue = Indicates if Info is recurring Groups = Indicates the recipient groups ShowOnUsersDesktop = Indicates if Info is set for display on the desktop ShowOnWinlogonDesktop = Indicates if the Infos is set for display on the logon screen CanCloseOnUsersDesktop = Indicates if the user can close the Info on the desktop CanCloseOnWinlogonDesktop = Indicates, if the user can close the Info on the logon screen Soundfilename = Shows filename of allocated sound file Beep = Shows, if system beep is to be played Canceled = Indicates if Info was cancelled CountBeep = Shows number of system beeps to be played User = Shows Editor of the Info CloseOnClick = Indicates, if Info can be closed by clicking on hyperlink CancelOnClose = Inicates, if the Info will be cancelled on client after closing Days = Shows days of periodic Infos IsScript = Indicates, if Info is allocated to a Remote Access script IsSurvey = Indicates, if Info is allocated to a survey SurveyMasterID = Shows internal ID of the survey SurveyResultID = Shows internal ID of the survey result ScriptFilename = Shows filename of the script to be run (Remote Access) ScriptIniFile = Shows Inifilename of the script to be run (Remote Access) ScriptDir = Shows directory of the script to be run (Remote Access) ScriptIniInfo = Shows configuration of the script to be run DayPeriod = Offline = Indicates, if Info is available offline SetClientTime = Indicates, if client-time is to be used in an offline Info Language = Shows language as recipient selection in Info Channel = Shows channel as recipient selection in Info SurveyIniInfo = OneTime = Indicates, if Info is to be shown only once Popup = Indicates, if Info is to be displayed as popup QuickUsers = Shows single addressed users ShowDetails = Description = Shows description of the Info IsIniFile = Indicates, if Info was set as Inifile export

SoundOnly = Indicates, if Info is to play sound only MyID = Shows value of property MyID SurveyPowerusersList = SurveyPowerusersAll = MinPeriod = MinPeriodInterval MinPeriodActive MinPeriodStart MinPeriodRun Enabled = Indicates, if Info was released for display Caption = Shows caption of the Info BackgroundColor = IDParent = HasChildren = IDTemplate = Detail = Generates a hyperlink for viewing Info details edit = Generates a hyperlink for editing the Info Cancel = Generates a hyperlink for cancelling the Info delete = Generates a hyperlink for deleting the Info Status = Indicates Status of the Info (e.g. active, waiting) __user_defined_filter__= Possibility to create a selfdefined filter-rule similiar to a WHERE clause in an SQL statement Infofields... = Shows value of the selected Infofield

List of valid operators and expressions in UDF-Filters

Comparison Operators

Operator Example Comment = Status = 'active' is equal with <> Status <> 'finished' is not equal with >= Timestamp >= '1/1/2008' is larger tahn or equal with <= Timstamp <= '12/31/2008' is smaller than or equal with > Timestamp > '12/31/2007' is larger than < Timestamp < '1/1/2009' is smaller than BLANK Caption = BLANK Filters also datasets, where the content is blank (e.g. linefeed) IS NULL Priority IS NULL Field has no value IS NOT NULL Priority IS NOT NULL Field has any value

Logical Operators

Operator Example Comment and Continue = 1 and Status = 'waiting' logical AND or Continue = 1 or Status = 'active' logical OR not not (Status = 'finished') logical NOT

Arithmetic Operators

Operator Beispiel Kommentar + Timestamp + 7 > '1/1/2008' Addition (Number, String, Date/Time + Number) - Timestamp - 7 < '1/8/2008' Subtraction (Number, String, Date/Time - Number) * Multiplication (Numbers only) / Division (Numbers only)

String Functions

Operator Example Comment Upper Upper(Caption) = 'ATTENTION' Transforms value to upper-case Lower Lower(Status) = 'active' Transforms value to lower-case Substring Substring(Caption,1,4) = 'Info' Delivers the part of the string (parameter 1), which is defined by begin (parameter 2) and end (parameter 3). Trim Trim(Caption) = 'Attention' Deletes whitespaces at begin and end of a string. If an optional second parameter is given, then this will be trimmed instead of whitespaces. TrimLeft TrimLeft(Info,'

') = 'Hello *' Trims whitespaces, respectively a partial string, from the begin of the specified value. TrimRight TrimRight(Info, '

') = '* world' Trims whitespaces, respectively a partial string, from the end of the specified value.

Date & Time Functions

Operator Example Comment Year Year(Timestamp) = 2008 Determines the year Month Month(Timestamp) <> 12 Determines the month Day Day(Timestamp) < 7 Determines the day Hour Hour(Timestamp) > 8 Determines the hour (24 hour format) Minute Minute(Timestamp) <= 30 Determines the minute Second Second(Timestamp) > 0 Determines the second GetDate GetDate < Begin GetDate determines the current date and time Date Date(Timestamp) < Date(GetDate) Determines the date of the parameter Time Time(End) > Time(GetDate) Determines the time of the parameter

Miscellaneous

Operator Example Comment LIKE Caption LIKE '%Attention%' Comparison operator for partial match IN Date(Timestamp) IN (1,2,3,4,5,6,7) Comparison operator for match with one of the specified parameters * Info = 'Notice *' Wildcard for any number of characters

Example of use Shared Whiteboard

In the following example of use, a simple Infofilter will be created, which is to be available for public access as a Shared Whiteboard.

Notice: This example uses features of bestinformed Enterprise Edition.

1. Create Infofield "Priority"

In the Info overview, open the Infofield administration by clicking on the hyperlink Infofields. Create a new Infofield named "Priority" and select Combobox as type.

After saving this Infofield, it is shown in the list of the Infofields in the administration. Now click on the hyperlink edit in the line English of the Infofield.

Now enter a blank line and the words low, medium and high (each in a separate line) in the textfield Items. Save the settings.

2. Create Infofilter

Now go back to the Info overview and click on the hyperlink filter for creating a new Infofilter. Label the new Infofilter "Shared Whiteboard", set the refresh rate to "60" and select the option Show all Infos of all users.

Now select following Infoproperties for display in the Infofilter:

- Text - Timestamp (caption -> created:) - User (caption -> by User:) - Status - Priority

Now set the properties for the filter:

Property: priority -> Value: low,medium,high ( -> OR combination!)

Now set following formatting options:

Property: priority -> Value: low -> Colored cell: green Property: priority -> Value: medium -> Colored cell: yellow Property: priority -> Value: high -> Colored cell: red

Now save the Infofilter.

3. Setup Infofilter as Shared Whiteboard

Open the Poweruser administration and allocate the Infofilter to a Poweruser. Set this Infofilter to be his standard filter.

The Infofilter now can be used by the Poweruser and will automatically be shown to him upon accessing the Info overview.

Notice: In the Multiuser chapter, you can read more on how to setup a Poweruser with read- only rights and how to set the access to a Shared Whiteboard.

10.1.4 Web Directory

The Web directory is located in the installation directory of the Infoserver.

In the Web directory, you can find several subdirectories in which you can save files for distribution. For example, the directory Images contains image-files, which you can insert into your Infos using the WYSIWYG editor.

10.1.5 Infos on the Logon Screen

If, for example, you want to address an Info to all computers on which no user has logged on, following options are available to you:

1. Creating a group

In the group administration, create a new group, e.g. by the name "logonscreen" and click on save. Now select your newly created group from the group overview and click on add in the username section of your group. Now delete the * wildcard from the field username (field username must be empty) and click on save. You have created a group, which includes all computers to which no user has logged on, therefore the messages will be displayed on all these computers.

2. Using the "Users" field

Statusinfos on the WinLogon Screen

In case you want to display a tray icon on the WinLogonscreen as a statusinfo, bestinformed enables you to do so. By this means, you can also display a status on a locked screen.

Procedure

To show a taskbar on a locked screen, please proceed as following:

1. Open the configurationfile Infoclient.ini in the directory .../Cordaware/infoband

2. In the general section, enter following line:

ShowTaskbaronwinlogon=True

3. Stop both clients and start them anew.

Start>Programs>Cordaware>Infoband> a. Stop Client (Winlogon) b. Stop Client (User) c. Start Client(Winlogon) d. Start Client (User)

Alternatively, you can also set this configuration in an Inifile export.

10.2 Statusinfo Management 10.2.1 Create Statusinfo

Statusinfos enable a permanent display of a certain status. Affected users therefore can instantly perceive and react to changes.

The display of status informations is effected either as a taskbar and/or as a window on your monitor.

Creating a new status information

For creating a new Statusinfo, select Status -> New Status from the navigation menu of the Infoserver. The form for creating a new Statusinfo will open.

In this form, you can set following properties:

· Name · Description · Reset StatusQuo after seconds: In this property, you can set a numeric value, which defines after how many seconds a currently active status will be reset to neutral (deactivation of the Statusinfo). · Groups: Here you can define the groups, which are to receive the Statusinfo.

Example:

In a Statusinfo "Databackup", the group of administrators is to be informed about the begin of the daily/weekly databackup. 60 minutes after a change of the StatusQuo, the Statusinfo is to be reset.

After the relevant properties of the Statusinfo (Name, Status Quo Reset, Recipients) are set, the Statusinfo can be saved.

10.2.2 Create Status

For creating a Status for a Statusinfo, click on the hyperlink Add status in the row of the respective Statusinfo in the overview of Statusinfos.

The form for setting up a Status will open.

In this form, you can set following properties:

· Name · Description · Change Status: In this option, you can define that this status will switch to another status after a certain number of seconds. · Restart main status infotime: If this option is selected, then the countdown for resetting the Statusinfo is started anew.

Example:

For the Statusinfo "Databackup", the status "Backup in progress", "Initiate daily backup" and "Initiate weekly backup". The status "Initiate daily backup" and "Initiate weekly beackup" are supposed to switch to status "Backup in progress" ten minutes after activation. The status "Backup in progress" is supposed to be active for 60 minutes before the Statusinfo is reset. Now, first create the status "Backup in progress" and activet the reset.

Now create the status for "daily" and "weekly" backup and set the successor status for each.

Save the Status. Now you can set the Statusdetails for each Status, in which the messagetext and other display-options can be set.

10.2.3 Create Statusdetail

Open the Statusinfo administration and click on the hyperlink Add Statusdetail next to the desired Status.

Now you can set following options:

Language:

Select a language. The language refers to the operating system of the recipient.

Type:

Select a message type. Depeding on the type, the background-color of the Statusinfo will vary.

Caption:

The caption is the headline of your Statusinfo.

Info:

Defines the text of the Statusinfo. You can format and add links or images to your message as usual.

Trayicon:

In addition to your Statusinfo, which is displayed as a small window on your screen, you can also set an icon to be displayed in your taskbar.

To display an icon in your taskbar, it is necessary to provide the icon-file in the *.ico format in the web folder of the Infoserver.

The path of the desired trayicon needs to be inserted as URL, e.g. http://infoserver:800/images/status_ok.ico. It is possible to browse for icon-files using the Content Management of bestinformed.

In case you want to use the image, simply type "default" as value for the trayicon URL.

Notice - Trayicon Only: In case you want to display a trayicon only, then you will need to set the time for display to "0" and deselect the unlimited checkbox.

Hint:

You can insert a description as hint for the Statusdetail. This will appear, e.g. when hovering with the mouse-pointer over an trayicon.

Sound:

You can also include an soundfile, which will be played upon display of the Statusinfo. The path to the soundfile must be provided as URL. For this, you can also use the Content Management of bestinformed. In case the specified soundfile can't be found, then a sytem-beep will be played instead.

Example:

The Status "Initiate daily backup" is to be displayed for two minutes. The Info is for All Languages and should be accessible by a trayicon.

Notice: Statusinfos and their status are sorted alphabetically. Statusdetails are sorted by language.

Further Settings

When setting the properties for the userdesktop, you can define whether a trayicon is to be displayed in the taskbar or not. Further on, you can set if the message is to be displayed on the desktop by clicking or by hovering with the mouse over the trayicon.

Set the displaytime to define the timespan for which the status window is to be visible. You also can set the time to unlimited while giving the user the option to close the window.

Tip!

In case you want to show a tray icon instead of a pop-up when releasing a new statusinfo, then simply leave Displaytime in seconds blank. The unlimited checkbox must be unchecked too.

10.2.4 Run Statusinfo

To start a Statusinfo, select a Status from the dropdown menu in the column Status quo. The Info will be dislayed instantly. To switch the Status, choose a different item from the dropdown.

Please note: The Statusinfo starts immediately after selecting a status!

Statusinfos on the WinLogonscreen

In case you want to display the trayicon of a Statusinfo on the WinLogons creen, please proceed as following:

1. Create a new Inifile Info.

2. Insert following line in the [General] section:

ShowTaskbaronwinlogon=True

3. Select the desired recipients, then save and send the Info.

10.3 Group Management

The Infoserver enables you to deliver messages group-dependently. To administer the groups, please click on the link Groups. Now you will see the Group Overview. Here you can edit existing groups or add new groups to your Infoserver.

10.3.1 Create Group

To create a group, please klick on the hyperlink New group.

Define a groupname and optionally a description. Save the group.

10.3.2 Add Members

Members of a group can be built over two functions:

1. By indication of user name, Computername and IP address

2. By a scriptfilter

10.3.2.1 Simple Filter

A user is a combination of username, computername and TCP/IP adress. You also can substitute these properties with wildcards:

* substitutes an arbitrary number of arbitrary characters ? substitutes one arbitrary character

If you don't want to set a specific value for one specific point, just simply always enter a * instead.

Only exception: if you want to send a message to all computers which do not have a logged-on user, you have to create a group which consists of one user with the following properties:

Username: Computername: * Adress: *

When creating this Info, please mind that you uncheck the Show Info option for Userdesktop, otherwise the user still will see the message after logging on to his computer.

The username should remain empty. When the Infoclient logs on to the Infoserver and no user is logged on to the computer, the infoclient always will transfer an empty username! All other fields are always different from null.

Attention:

When adding a new group member, you should avoid specifying strictly all three properties. If, i.e. the IP address of a device has changed in DHCP, the specified group member cannot receive messages anymore on that certain device. Therefore, we recommend, when combining device and user in a group member, to strictly define only two properties and to use a wildcard for the third property.

Examples:

john.doe;workstation12;* erica.miller;*;192.168.1.24

10.3.2.2 Scriptfilter

When using the ScriptFilter, you can define the groupmembers using a code-script. If, for example, you have assigned an InfoClientValue to a certain group of people, then you can merge these into an Infoserver group using the ScriptFilter.

Example:

program Scriptfilter; var Res: Boolean; begin Res := InfoClientValue('name') = 'yourValue'; SetResult(Res); end.

10.4 Channel Management

Next to groups, channels offer an additional possibility to address Users. Users can subscribe to channels, they don't have to be assigned by the administrator.

Using Channels

Channels serve for spreading information, when the Infoclient, i.e. the combination of computername, IP-address and username can't be uniquely identified. This always happens, when the Infoclient is not logged on to a domain, e.g. when connecting over the internet.

If you want to distribute the most recent special offers or company news to your costumers, then create a channel "Special Offers" or "Recent News".

The user of the Infoclient then can subscribe to this channel and will always be up to date.

Channels can be created language dependently, this enables an user to be informed in his mother tongue.

Please mind the correct choice and insertion of the languages.

10.4.1 Create Channel

1. In the navigation bar, click on Additionals > Channels

2. Click on New Channel and choose a name, description and language of the channel.

When clicking Edit, existing channels can be modified.

Addressing Channels

If you want to send a new Info to a channel, you have to operate as following:

1. Infos > New Info. 2. Open the Details. 3. Select the corresponding channel and save the message.

10.4.2 Subscribe to Channel

Important: The manner in which users can subscribe to channels depends on the user's authorities.

If, for example, tray icons are allowed, the user can subscribe to channels by clicking on the infoclient icon in the taskbar.

Click on the icon in the taskbar, the Infoclient interface will open. On the top of the interface, next to the serveraddress, are three symbols, simply click on the center symbol .

Choose a channel and click on Subscribe > Save > Close.

If no tray icons were permitted, the subscription menu can be accessed via a key combination.

Key combinations can be defined individually. For further information see Key Combinations.

10.5 Tools 10.5.1 ISPerformancer

In order to simulate the performance and the speed of the infoserver in networks of different sizes, we have developed the tool ISPerformancer. This application opens a defined number of clients and gives several values back.

Starting the application

To start the ISPerformancer, please logon to the infoserver and choose Tools > ISPerformancer in the navigation bar.

Implementation of a simulation

If you want to perform a simulation, proceed as follows:

1. Enter the address of the server in the line "Server adress". If you have several network interface cards, you can separate them by a ",".

2. Enter the port of the infoserver. The standard port is 800.

3. In the input field Connection Count you can enter the number of connections, you want to open.

4. Start the application with the button start.

5. Now create a new info and send it to a test group.

Now, you can follow the process of the simulation and see the result.

Now, you can see the return values of the test.

OK=Conformation of the server Infos=sent messages of the server Sent=Sent informations from client to the server

Additional, you see the arised traffic of these actions.

Below, you see the total duration of sending the message and the average number of delivered messages per second. (The value in brackets relates to maximal number during the simulation)

11. Professional

In the Professional Edition you can access all functions available in the Basic Edition. Additionally, following functions are now available:

Domain administration:

You now can register additional domains in the Infoserver. This is necessary for accesing groupmembers outside the Infoserver's domain and refreshing these automatically.

Interfaces:

Bestinformed now offer an API interface for external applications. This can be used, e.g. for sending message from your familiar ticketing system. By default, the MailToInfo and InfoToMail interfaces are already implemented and ready for use.

Extended Groupmanagament:

You now can reproduce your domain groups in the Infoserver and easily synchronize its members. For this, you can exclusively use the Groupmanager tool, which allows you to easily import and synchronize groups from one or more domains. The functions used by the groupmanager can also be used manually in the scriptfilter. Additionally, you can also use the filegroup-function in the scriptfilter. With Autogroups, you can automate the creation-process of groups by using special Inifiles.

Infoscenarios:

With Infoscenarios, you can send several different messages at once by merging templates into an Infoscenario.

Report Generator:

With the report generator, you can access the internal database of bestinformed and create individual datasheets of the stored information. It is possible to create tabular and graphical analyses of the stored information.

11.1 Domain Administration 11.1.1 Access Native Domain

For querying the ActiveDirectory or any other dirctory service, it is necessary to register at least one domain in the Infoserver. The access to the domain can performed with either AD- proprietary functions or LDAP functions. Access to the directory service is necessary for the synchronization of AD-groups in the Infoserver and for using the interface InfoToMail. Additionally, access to the domain is needed for the Multiuser Mode in the Enterprise Edition.

Access to the native domain with AD functions

Allocation to the domain

By default, the Infoserver sets up the allocation to its native domain during installation. If the domain can't be resolved, or if the Infoserver is installed on the primary domaincontroller, then the domain LOCALHOST will be allocated. This allocation can be changed in the configuration- file Infoserver.ini. For changing the allocation, you will need to edit the item Domain= in the Infoserver.ini and assign the name of the new domain as value. For applying the changes, save the file and restart the Infoserver.

Notice: The allocation of the domain must be edited only in case the domain couldn't be resolved during installation or in case you want to use a different domain as native domain for the Infoserver.

Authentification at the domain

In order to read information from the domain, the Infoserver needs the appropriate authorization. This autorization is only granted, if the Infoserver can authenticate himself on the domain with a valid user account. For authentification on the domain, you can register an user account in the Infoserver administration.

For registering an user account, select Extras > Password > AD Password from the navigation.

The username and the password, which now are registered for domain-authentification, are saved to the configuration-file Infoserver.ini. The username is saved in clear text, the password is saved encrypted:

AdUsername=Username

AdPassword=Password (encrypted)

Access to the native domain with LDAP functions

Next to AD-proprietary functions, you can also use only LDAP functions for the access to the directory service. Among other, this offers the advantage that queries to the directory service can be processed much faster, thus raising the performance of the Infoserver in particular in this section.

Activate LDAP access

For activating the LDAP based access to the domain, you will need to edit the item LDAPOnly= in the configuration-file Infoserver.ini and assign the value true.

LDAPOnly=true

Now it is necessary to specify the authentification-parameter samAccountName and the mount-point (RootDSE) of the domain. For this, the items LDAPsamAccountName and LDAPRootDSE are available in the configuration-file:

LDAPsamAccountName=samAccountName or UID (Novell)

You can assign the values samAccountName or UID to the item LDAPsamAccountName. The value UID is only necessary, if your directory service is from Novell. In any other case, only samAccountName is a valid value. In case you are not sure which value is necessary, you can also leave the value blank. In this case, the desired value wil be queried from the domain. Please mind that this can delay all LDAP based operations.

LDAPRootDSE=DC=MyDomainName,DC=ToplevelDomain

The value of the item LDAPRootDSE is the mount-point in the domain-tree. This mount-point must be defined in LDAP syntax. The value DC=Cordaware,DC=Local for example specifies the hierarchically highest node in the domain cordaware.local. The mount-point can also be allocated to an organisation-unit. The value OU=London,DC=Cordaware,DC=Local for example specifies the organisation-unit London of the domain cordaware.local as mount- point and therefore as the Infoserver's native domain. In this case, the Infoserver will only be able to resolve those groups and users as members of it's native domain, who are also allocated to this organisation-unit. In case no value is assigned for the item LDAPRootDSE, then the Infoserver will try to locate the highest hierarchical node in its native domain. Please mind, that this can delay all LDAP based operations.

Authentification

When using the LDAP functions, the user-data registered in AdUsername and AdPassword will be used for authentification.

Define domaincontrollers for LDAP queries

By default, the Infoserver will use the primary domaincontroller for it's queries. In case you are using the LDAP functions, then you will need to specify a list of one or more domaincontrollers in the configuration-file Infoserver.ini. This list will be processed from the first to the last item, the first domaincontroller from this list which accepts a connection will be used for the LDAP operations. For the list-definition, you will need to assign the domaincontrollers as comma- separated values to the item DomainListOfServers=. You can use either IP addresses or computernames:

DomainListOfServers=102.30.45.6,srv2_domainhosts,bdc3.mydomain.com

If this item has a blank value, then the Infoserver will search for the primary domaincontroller. Please mind that this can delay all LDAP based operations.

11.1.2 Additional Domains

Manage Additional Domains

In the navigation menu, under Server > Configure domains, you can register and manage additional domains. This function is needed in case:

- The Infoserver must synchronize groups from other, non-native domains. - The interface InfoToMail is to send emails by using a mailprofile/SMTP.

Implementation

1. Select Server > Configure Domains in the main menu.

2. The domain-overview will open. Click on the hyperlink New Domain, to add a new domain.

3. Following options are available when registering (and editing) an additional domain:

Domain (Alias): Here you can enter the domain-name or an alias (new!). If an alias is entered and you want to access a domain, then it is mandatory to specify an appropriate

domain-controller in the "Servers" list. When selecting the option Use for domain access, then this account will be used for access.

Username: Enter the login-name of the designated user, which is to be used for domain- access.

samAccountName: Here you can specify, if the samAccountName or the UID (Novell only!) of the user is to be used. Default is samAccountName. The value "UID" is only to be used, if your directory service is from Novell.

RootDSE: In case you want to use a certain OU object, or set a specific mount-point for the synchronisation of groups, then you can enter the RootDSE path. The RootDSE path must be entered in LDAP syntax, e.g. OU=Pfaffenhofen,dc=cordaware,dc=com. If no RootDSE is given, then the infoserver will automatically search for the hierachically highest mount-point in the domain.

Servers (PDC or BDCs): Here you can explicitely set one or more domain-controllers (primary and backup), which are to be used for the synchronization access. The Infoserver will process the list top-down and use the server wich allows access first. If a domain-alias is in use, than at least one domain controller must be defined.

Passwort: Enter the user's password in the fields "Password" and "Confirm password" for authentification purposes.

Annex: Inifile settings for the native domain

In the Infoserver.ini inifile of the Infoserver, the properties mentioned above can be set and edited as well for the native doaminof the Infoserver. The native domain of the Infoserver does not need to be registered among the Additional Domains, because the Infoserver can access it's native domain automatically as member. Yet, this access process can be accelerated and, if necessary, an OU can be defined as mount-point of the domain.

LDAPsamAccountName=samAccounName: samAccountName or UID (Novell only). If no value is given, then the type is queried from the domain.

LDAPRootDSE=dc=domain,dc=local: RootDSE path to the domain / OU. If no value is given, then the path to the domain-root is queried from the domain-controller. This item can

also be used, to limit the snychronization-process to a specific OU in the domain, e.g. when bestinformed is used only in a certain part of a company.

LDAPOnly=true: If the value true is set, then only functions of the LDAP protocol will be used. If empty or false, then Windows functions will be used additionally if LDAP functions fail.

DomainListofServers=bdc1,bdc2,bdc3: List of domain-controllers. List will be processed from first to last item. The first domain-controller to accept a connection will be used for the synchronization process.

11.1.3 Refresh Domain Groups

With bestinformed Professional Edition, it is possible to use and synchronise groups from your directory in the Infoserver.

After importing the domain groups with the group manager, these groups are available for addressing in the Infoserver.

In order to avoid permanent access and queries to the domain-controller, the members of these AD groups are saved for 24 hours (by default) in the temporary cache of the Infoserver. When addressing one or more of the AD groups, the Infoserver is using this image to address the recipients.

This causes, that only after the automtic refresh-interval any changes in your AD will be known to the Infoserver.

If the bestinformed administrator is aware of crucial changes in the AD, then he can reset the cached image manually by clicking on Server -> Refresh AD usergroups in the navigation of the Infoserver administration.

In this case, the temporary image will be cleared and the Infoserver will refresh the information of a group's members the next time it is addressed in an Info.

11.2 Interfaces 11.2.1 MailToInfo

11.2.1.1 Settings

The MailToInfo interface enables you to transform emails into Infoserver messages.

For this, you can send specially formatted emails to the Infoserver. This function can be used in many scenarios: automated messaging from a triggered event in an application (e.g. database) or sending messages from your known trouble-ticket system. Through the combination with MailToInfo, you can inform immediately.

How to configure an email client

If you want to send messages to the Infoserver, then you will need to setup a new email account which uses the Infoserver as the outgoing SMTP server:

SMTPServer: Infoserver-address SMTPPort: port 825 by default, if not set differently during installation POP3: any (e.g. pop.test.com) Sender address: any (e.g. [email protected]) Recipient address: any (e.g. [email protected])

Important Notice: Some email clients require, that you set the message-format to text only. Also, you need to consider automatic linebreaks. An automatic linebreak will lead to data-loss, if it appears in a property value (e.g. message text). Therefore, we urgently suggest to increase the character-length of a text-line before an automatic linebreak will be inserted.

Consider to exclude the MailToInfo account from the automatic synchronistaion routine, otherwise you will receive error-messages for this account when querying for new messages from the MailToInfo account.

Mail help

You can send an email from your mail-client to the Infoserver with the subject help. The Infoserver then will reply with an error message, which contains a quick overview of the property-syntax for sending messages.

Password

You can define, if the MailToInfo authentification is conducted with the regular admin password, or if you want to use an additional MailToInfo-only password. For setting the MailToInfo password, select Extras > Password > MailToInfo from the navigation menu in the administration interface.

Notice: The MailToInfo password is only valid for this function, you can not use it for logging into the administration interface.

Additionally, you can also set the MailToInfo authentification to TCP/IP. This has to be set in the Infoserver.ini configuration file.

Testapplication

In the MailToInfo folder in the installation directory of your Infoserver, you can find the MailToInfoDemo.exe. This small application is intended for testing the functionality. Also, you can use it, if setting up a new MailToInfo account can't be done easily. See also chapter Automate.

11.2.1.2 Send

This is a small guide on how to send an email to the Infoserver with your MailToInfo account.

1. Open a new message and insert an arbitrary recipient address.

2. Insert newinfo as subject for the message.

3. Now enter the username (admin) and the (MailToInfo, if set) password in the body text.

4. Insert a blank line and afterwards in separate lines Infotext and additional seetings.

The minimal message

The message body must contain at least user, password and Infotext.

Example:

username=admin password=dHg6v8K1 Info=Infotext

Using Info-Templates

Instead of setting each property individually, you can also address an Info-Template. For this, you will need to insert the property templatename= and assign the desired Info-Template.

Example:

username=admin password=xyz

templatename=ExchangeBreakdown

Now, the Infotext and all detail-settings will be applied as set in the template. When inserting further properties, they will overwrite the respective setting of the template.

Notice for Multiser-Mode: In the Multiuser-Mode, it is possible to use your own templates and templates of other Powerusers as well. For using templates of other users, first of all, access to these templates must be configured in the respective Poweruser's profile. Additionally, it is necessary to append the owner's name to the template's name. The appended name must be wrapped in brackets.

Example:

username=poweruser password=zyx

templatename=ExchangeBreakdown(ADMIN)

Using ScriptVars in Info-Templates

When addressing a template in the MailToInfo-syntax which contains ScriptVars, then you can also add content to these ScriptVars in the MailToInfo-syntax. Simply enter the @-symbol followed by the name of the ScriptVar and assign a value.

Example:

username=admin password=xyz

templatename=CurrentDisturbance @Starttime=13:00 @Endtime=15:00

In this example, the ScriptVars [Starttime] and [Endtime] in the Infotext of the template will be substituted with the assigned values in the Info-syntax.

Further settings

Here is a listing of properties you can set in an Info.

Notice: Properties which can not have an alphanumeric value are activated by assigning the value ON (Boolean). In the following listing of properties, you can also see which value-types are accepted by the different properties: Numeric, Alphanumeric/String, Date or Boolean (=ON).

Example:

Minutes=10 Popup=ON

Minutes= Defines the display-time of the Info. Numeric value.

Begin= Defines the begin of the active-time. Format is DD.MM.YYYY HH:mm:SS or just HH:mm:SS. Leave blank if Info is to be active immediately. Date value.

End= Defines the end of the active-time. Needs same formatting as begin. Date value.

Infinity= Defines if Info is infinitely active. Boolean value.

Active= Defines the active-time of the Info in minutes. Numeric value.

Beep= Defines if Info plays system-beep. Boolean value.

OneTime= Defines that client displays Info only once during active time. Boolean value.

Popup= Defines if Info is to be displayed as popup. Boolean value.

Groups= Here you must specify one or more groups, separated by a comma ",". If left empty, the Info will be sent to all clients by default. String value.

QuickUsers= Here you can specify single users / Infoclients as a String value. Every user is setup by a combination of username, computername and IP address. For example, if you want to address John Doe, then you have to type follwing argument:

Quickusers=john.doe;*;*

In case yo want to address a single computer, then type following argument:

Quickusers=*;computerXYZ;*

Several quickusers are separated by a comma:

john.doe;*;*,mitchel.burke;*;*,*;computerXYZ;*

Channel= Here you can address the channel for the Info. Example: Channel=Cordawarenews

ShowOnUsersDesktop= Defines, if the Info is to be displayed on the users desktop. Boolean value. If you don't define a value, then the Info will be displayed on the logon-screen only, if defined.

ShowOnWinLogonDesktop= Defines, if the Info is to be displayed on the logon-screen. Boolean value.

CanCloseOnUsersDesktop= Defines, if users can close Infos displayed on their desktop. Boolean value. If no value is given, then the user can't close the Info.

CanCloseOnWinLogonDesktop= Defines, if users can close Infos displayed on the logon-screen. Boolean value. If no value is given, then the user can't close the Info.

Days Defines the weekdays, on which periodical Infos are to be displayed. Numerical value. Use one or more comma separated numerical values.

Monday=1 Tuesday=2 Wednesday=3 etc.

Continue= This option generates a periodically recurring Info. Boolean value (On). Length of the period is defined by begin and end of the active-time.

Example:

For setting up a periodic Info, which will be displayed every Tuesday and Wednesday at 15.00 with 60 minutes active-time and 10 minutes display-time, you would have to type following syntax into the mailbody:

username=admin password=xyzxyzxyz info=periodic Info begin=09.07.2007 15:00:00 end=09.07.2008 15:00:00 active=60 minutes=10 continue=ON days=2,3 groups=Group1,Group2

Offline= Defines, if Info is to be available offline too. Boolean value (On).

See also Active- and Displaytime.

IsIniFile= Defines, if the Info is to alter the recipient clients Inifile. Boolean value (On). More information to the syntax of Inifile Infos can be found in chapter Export Inifile.

11.2.1.3 Editor

For quickly generating the MailToInfo syntax, e.g. for templates in external applications, you can use the MailToInfo editor function of the WYSIWYG editor.

1. Create a new Info and set all paremeters as desired.

2. Click on the M2I hyperlink to the left of the WYSIWYG editor.

3. The M2I editor now will display the MailToInfo syntax of your Info. you can now copy the syntax and use it e.g. in an external application.

4. If you click on the hyperlink open mailclient, then your default mailclient will open and the syntax will be inserted automatically in the mailbody.

A premise for sending the Info via mailclient is, that you have configured an email account using MailToInfo (see chapter Settings).

11.2.1.4 Testapplication

With the testapplication MailToInfoDemo.exe in the folder MailToInfo in the installation directory of your Infoserver, you can quickly and easily test the MailToInfo functionality of your Infoserver. Simply enter the correct MailToInfo port, servername and syntax of your Info.

11.2.1.5 Send Scripts

If you hold a licence for Cordaware Remote Access, you can also distribute scripts over the MailToInfo interface.

How to initiate

At first, you will need to generate the MailToInfo syntax for the script. For this go to the Script Overview and initiate the desired script. As you get to the WYSIWYG editor, click on the M2I hyperlink for generating the Info syntax for distributing this particular script. You now can copy the MailToInfo syntax and use it in an external application.

Important notice: When sending a script with an email client, then the bodytext must not contain additional linebreaks, otherwise the information within a property and its value will get lost.

11.2.1.6 Cancel Infos

When distributing Infos via MailToInfo, it is also possible to cancel Infos using MailToInfo. For cancelling an Info via MailToInfo, proceed as following:

1. Insert an ID

When creating a new Info via MailToInfo, you need to insert a unique ID as a property in the mailbody. The unique ID has to be assigned as value to the property myid: myid=uniquevalue. The value of the property myid has to be unique (can't be used repeatedly), alphanumerical and can contain up to 100 characters.

Example:

subject: NewInfo

username=admin password=xyzxyzxyz myid=12345 info=This is a periodical Info begin=04.02.2005 15:00:00 end=04.02.2006 15:00:00 active=60 minutes=10 continue=ON days=2,3 groups=Group1,Group2

2. Cancel Info

For cancelling an Info via MailToInfo using the property myid, you will need to send a new email to the Infoserver with subject cancelinfo. The mailbody must contain the authorization (username and password) and the property myid with the unique ID of the Info which is to be cancelled:

Subject: CancelInfo

username=admin password=xyzxyzxyz myid=12345

Important: Please mind to use the correct subject CancelInfo instead of NewInfo.

11.2.1.7 Automate

You can also use the MailToInfo function without using an email client. By using the MailToInfoDemo.exe in the MailToInfo folder in the installation directory of your Infoserver, you can generate quickly accessible and preconfigured messages. This allows you to distribute messages with a simple double-click, e.g. in emergencies, without accessing the administration or using a mailclient.

Example:

You want to distribute an urgent message in an emergency (e.g. server-crash) as quick as possible to a selection of users.

Step 1 - Create a simple textfile which uses following syntax

Host=InfoserverHostName // enter the host name or IP address of the Infoserver Port=825 // default port is 825, use your own value if you have selected a different port number during installation subject=newinfo // MailToInfo subject for initiating a new Info // This blank file has to be inserted in the text! username=username // From here on, you can use the known MailToInfo syntax (see send, you can also use the M2I editor)

Step 2 - Save the file, e.g. as sytemcrashQuickMessage.txt.

Step 3 - Create a shortcut on your desktop

Right-click on your desktop and creat a new shortcut. You then will be asked to specify the file for the shortcut. Here you will need to enter the path to the MailToInfoDemo.exe. After you have entered the path, insert a whitespace and then you will need to specify the path to the previously created textfile (this textfile the will be passed as an argument to the application). Set the name as desired and save the shortcut.

Example:

...\MailToInfo\MailToInfoDemo.exe C:\cordaware\Infoband\MailToInfo\systemcrashQuickMessage.txt

Now you can use this shortcut to quickly initiate the Info specified in the textfile, using the MailToInfo interface.

Notice: Please mind, that path values have to be wrapped in double-quotes "..." when using a path, that contains whitespaces.

Example:

"C:\cordaware\emergency messages\systemcrashQuickMessage.txt"

An example for an automated Info can be found in the folder OneClickDemo in the installation directory of the Infoserver.

11.2.1.8 Attach Files

The MailToInfo interface offers the additional possibility, to attach files and to link to these files in the on-screen ticker. Many practical fields of application result from this feature.

Notice: For using the MailToInfo functions, the sending email client needs to be configured appropiately. For setting up a proper email account, please see chapters Settings and Send.

Linking the attached file

For accesing a file via HTTP, the file needs to be lodged on a webserver. For this reason, attachements in MailToinfo emails are copied to the Infoserver. Then, these files can be accessed by inserting a hyperlink to the file in the message.

File attachements are copied by default to the ...Cordaware\Infoband\Web\Web\ directory, also for all users in the Multiuser Mode of the Enterprise Edition.

Setting up the email:

We recommend to create a template with the desired parameters by using the MailToInfo- Editor.

The only difference to an ordinary MailToInfo template is, that an attachement is added to the email and that the link to the attachement is inserted into the message text.

Example for setting up a MailToInfo template:

1. Create a new Info, set the parameters as desired and insert a sample text with a hyperlink.

Important notice for creating hyperlinks

When inserting a hyperlink to the attached file in the MailToInfo messagetext, then the filename needs to be wrapped in curly braces { }.

By wrapping the filename in curly braces, the Infoserver will link only the currently attached file, even if a file with the same name already exists in the specified directory. In this case, the existing file will be renamed by adding an internal version number.

Example: The file myAttachement.pdf already exists in the user-directory. This file therefore will be renamed myAttachement_01.pdf. The hyperlink to the attached file must be inserted in the following format:

Format of hyperlink "http://servername:800/Web/{myAttachement.pdf}"

By linking the file via HTTP, the recipients browser will handle the file-access. If the browser recognizes the MIME-Type of the file, then the file will be opened with the default program registered in your operating system (e.g. *.xls will be opened with MS Excel).

2. Click on the hyperlink M2I for opening the MailToInfo Editor.

The editor will generate the message syntax. You now can copy the text as mailbody template.

3. Open your email client and insert the mailbody template

Example:

Subject=NewInfo

Username=admin Password=info Info=New masterticket, please click here Minutes=10 Begin= End= Active=10 ShowDetails=ON ShowOnUsersDesktop=ON ShowOnWinLogonDesktop=ON CanCloseOnUsersDesktop=ON CanCloseOnWinLogonDesktop=ON CloseOnClick=ON CancelOnClose=ON Groups=All

5. Attach the desired file with your mail client. (In our example: "myAttachement.pdf")

6. Send the email.

The attachement now will be copied to the user-directory on the Infoserver, the hyperlink will direct to the copied file. In our example, all recipients will receive an on-screen message with a hyperlink, which will open the file "myAttachement.pdf".

11.2.1.9 Access Statusinfos

bestinformed offers the possibility to change the status of a Statusinfo with the MailToInfo interface. The setup is almost identical with MailToInfo for Infos, except for different keywords.

Keywords and Functions

First of all, the subject of the email to the Infoserver has to be statusquo. This is an indication for the Infoserver, that you are accessing the Statusinfo component. In the email- text, it is mandatory to give the ID of the Statusinfo and the ID of the StatusQuo (statusquoid), to which you want to switch. The authentication doesn't change.

In this example, the item ID is allocated to the Statusinfo with ID 16. This is the Statusinfo itself. The item StatusQuoID is allocated to the Status with ID 45. By sending this email to the Infoserver, the Infoserver will perform a status-switch.

Resetting the Statusinfo

You can reset the Staus of a Statusinfo by setting StatusQuoID=0 in the MailToInfo text.

How to get the Statusinfo-ID and the Statusquo-ID

You can get the needed IDs from the Statusinfo Overview. When moving the mouse on the edit hyperlink of a Statusinfo, it will show the ID in the URL at the bottom of the browser- window:

If you click on the + hyperlink in the row of the desired Statusinfo, the Status-tree will expand

and you can access the available Status of the Statusinfo.

Now move the mouse on the edit hyperlink in the row of the desired Status. You can get the ID of the Statusquo from the URL as shown at the bottom of the browser-window:

Advanced: How to get the IDs from the Database

In case you want to get the appropriate IDs from the database (e.g. via ReportGenerator, NxEnterpriseManager or ODBC), you can use following sample SQL query-string:

SELECT StatusInfos."ID" AS "ID", StatusInfos."Name" AS "StatusInfoName", StatusInfosDetail."ID" AS "StatusQuoID", StatusInfosDetail."Name" AS "StatusQuoName" FROM StatusInfos, StatusInfosDetail WHERE StatusInfosDetail."ID_Master" = StatusInfos."ID" ORDER BY StatusInfos."Name" ASC;

11.2.2 InfoToMail

The integrated InfoToMail interface additionally allows you to send Infos as emails.

For sending Infos as emails, you will have to set up special email groups, which are built similar to regular Infoserver groups. When addressing an Info to this group, the Infoserver will distribute the emails to the designated recipients by using the defined method.

There are two possible method definitions:

1. Using a mailclient with user-profile

In this method, a locally installe email client is accesed by using a user-profile.

2. Direct distribution by accessing a SMTP-server

In this method, the scriptfilter is establishing a direct connection to a SMTP-server.

Setting up an email group for the mailclient interface

Requirements

- An installed email-client application on the Infoserver host, e.g. Outlook Express - A valid user-account, registered to the domain. Best is to setup a domain localhost in the Infoserver with this user.

Setting up an email group

1. Create new group

In the administration, go to the groupmanagement and click on the hyperlink New group.

Enter the group's name and optionally a description. Select Info2Mail as Type and save the new group.

2. Configure the new group

Go to the groups overview and click on the hyperlink add in the Scriptfilter column of the new group.

Now the form for setting up the scrpitfilter opens. Click on the script hyperlink to the left of the scriptfilter textfield and start the Scripteditor application.

In the scripteditor, select to create a new serverscript from the SendMail template.

You now can adjust the template and insert your values.

Overview of the configurable values

mDomain := 'YourDomain';

Important: The domain you are using must be registered in the Infoserver. For more information, see chapter add domain. When using the '.' for localhost, you must also register the domain localhost with a valid user.

mUsername := 'YourUsername';

This is the username registered with the domain you are using.

mProfile := ' ';

Here you must insert the name of the email profile you want to apply, when using Outlook. If you want to use Outlook Express, then you can leave the profile empty.

mTo := '[email protected]'; mCC := '[email protected]'; mBCC:= '[email protected]';

Now you can insert the email addresses that you want to address. You can use Cc. and Bcc. as well. If you have saved the recipients to a file, you can also use the function LoadFromFile(). You will need to insert the absolute path of the file.

Example: mTO :=LoadFromFile ('c:\email_addresses.txt');

Important: When addressing a list of email addresses at once in either mTo, mCC or mBCC, each email address must be wrapped in angle brackets < and > and the addresses must be separated by a semicolon or a comma. Additionally, it is possible to add a name to an email address. Added names must be wrapped in doublequotes.

Example: mTo := ';"Martha Miller" ';

When loading from a file, where each email address is in a separate line, then you can use following syntax to replace the linebrakes:

mCC :=LoadFromFile('c:\asdresses.txt'); mCC := StrReplace(mCC,#13#10,';');

mSubject := 'Mail sending from Cordaware bestinformed';

The subject of your email, e.g. "Important notice from the UHD".

mBody := 'Hallo,' + #13#10 + 'new info' + #13#10 + '%Info%'; mBody := StrReplace(mBody,'%Info%',Info); //

The variable mBody contains the mailbody of the email. You can set a constant mailbody and/or use the Info text by applying the variable Info. The function StrReplace(string Subject, string Search, string Replace) offers the possibility to replace a placeholder in a predefined bodytext with the text of the current Info. You can use HTML syntax for the mailbody. In case you need assistance, you can use the miniHTML editor for generating a valid syntax.

mAttachments :=' '

You can also attach a file to the email. Simply set the absolute path to the file you want to attach. When using an attachement, the same file will be used every time you address this group. Instead of editing the group, we suggest you rename and replace files when distributing a new file with the Info to the group.

Notice: If a caption and a background color were set in an Info, then you can access the values with the variables Caption and Background in the scriptfilter, e.g. for the subject: mSubject:= Caption;

3. Save the group.

4. You now can use the group for distributing emails from the Infoserver.

Examples - How to create templates

Example 1 - Simple Template

a. Create a new "InfoToMail-Group" and open the scriptfilter-editor.

b. After opening the default template, we customize it as follows:

c. We save the group

Commentary:

Our domain is localhost '.'. Username is "administrator". "Outlook" is the name of our email profile We send the message to "[email protected]". In the body, we entered the tag

to create a paragraph. After that, the individual info %info% (created in the info-editor), will appear. With "mBody := StrReplace(mBody,'%Info%',Info);", the variable %info% is replaced with the infoticker message, created in the info-editor.

Now, if we send a message to our email group, it looks like this:

The text after the salutation is the individual message %Info%.

Example 2 - Enhanced template

- Loading mail lists and mailbody from a file - adding an attachment.

Advised procedure:

1. Providing the needed files

- mail list as .txt file - mailbody as .txt file - attachment (any file)

a. Mail list

Your email addresses have to be separated by ';'. If your email addresses are listed one below the other, you can use the following syntax to separate the addresses within the mail client by ';' (valid for mTO, mCC, or mBCC)

mTO :=LoadFromFile('c:\adressen.txt'); mTO := StrReplace(mCC,#13#10,';');

b. Mailbody-Template

You can use HTML tags, to create your body. (e.g., by using the Cordaware mini HTML editor)

In our example, we create the following default body for our mail group:

%info% is the placeholder for the Info.

We save our body with the name "MyBody.txt"

c. Attachment

You can use any attachment. We use for example the file "myattachement.pdf"

2. Create your group

We create a new "Info2Mail" group named "applications a-m" Please note, that you select the group-type "Info2Mail".

3. Editing the default template

In our new group, we open the script-editor (column scriptfilter > add) and customize the default template as follows:

Commentary:

Our domain is "localhost". (It must be a valid domain at the infoserver. Further information about that, you can find in the chapter Domains > Add Domains)

We load our email lists "mTO" and "mCC" from the path where we have saved it. E.g.: "c:\...\". The mail addresses in our mail list are already separated by ';'. So, we don't need the function "mCC := StrReplace(mCC,#13#10,';');", and comment it out.

Further we have entered the subject, the path of our mailbody and of the attachment.

Notice:

To check your code, you can use the syntax check of the scripteditor.

4. We save our new group.

5. Sending the message

Now we create a new info with the following text:

"Actually it is not possible to logon the application xy"

6. Selection of our group

After creating the message, we select our new "Info2Mail" group.

7. Save

After clicking on save and ok at the following confirmation, the following message will be sent.

Setting up an email group for the SMTP interface

In InfoToMail groups, which directly access the SMTP sever, a local mailclient or mailprofile is not necessary. The selection of the SMTP server and the authentification parameters are set in the scriptfilter of the group. You can access the script-template for the SMTP sendmail script in the Scripteditor.

The variables and functions used in the script-template mostly are equal to the ones used in the scriptfilter for the mailclient interface. Yet, you will need to pay special attention to the variables for the connection to the SMTP server and their significance.

Methods of connecting to the SMTP server

Because of the history and the development of email, today two types of authentification obligations exist: The authentifictaion with necessary, previous connection to a POP3 account and the authentification at the SMTP server without the necessity of previous POP3 authentifictaion. Due to this, bestinformed offers the possibility to use both connection mechanisms.

Because both connection mechanisms require the SMTP host and the authentification thereon, following variables are at your disposal:

· mHost: Here you will need to specify the full domain-name (FQDN) or the IP address of the SMTP server. It is also possible to define a comma-separated list of SMTP servers. When using a list, then the Infoserver will use the server wich is the first to accept a connection. · mSMTPDomain: Here you will need to specify the domain registered in the Infoserver. The domain of the SMTP host needs to be equal to the reigstered domain. · mSMTPUsername: Here you will need to specify the user, which is set in the Infoserver for the domain access. · mSMTPPort: Here you will need to specify the SMTP port of the SMTP host. Default is port 25.

The SMTP server will demand a password for a succesful authentification. For this, the password of the domain user registered in the Infoserver will be used. This way, it is avoided that the password can be read in cleartext and it is protected from misuse.

In the variable mPop3BeforeSMTP, you now can define whether a connection to the POP3 account is mandatory or not. If the connection is not mandatory, you can set the value false. If the connection is mandatory, you will need to set the value true and use valid authentifictaion data in the following variables:

· mPop3Domain: Here you will need to specify the domain registered in the Infoserver. The domain of the SMTP host needs to be equal to the reigstered domain. · mPop3Username: Here you will need to specify the user, which is set in the Infoserver for the domain access. · mPop3Port: Here you will need to specify the POP3 port. Default is port 110.

The password needed for the authentification will also be taken from the domainuser registered in the Infoserver.

Example:

In the following example, the authentification at the SMTP server with previous connection to the POP3 account is configured:

mHost := 'smtp1.cordaware.com,smtp2.cordaware.com,10.150.115.25'; mSMTPDomain := 'CORDAWARE'; mSMTPUsername := 'USR_BESTINFORMED'; mSMTPPort := '25'; mPop3BeforeSMTP := true; mPop3Domain := 'CORDAWARE'; mPop3Username := 'USR_BESTINFORMED'; mPop3Port := '110';

Important notice for InfoToMail when using Infos in multiple languages

If an Info was composed in multiple languages, then the variables Info, Caption and Background will provide only the information that was inserted for All Languages in the Info. In case you also want to access the content that was inserted for specific languages, then you can use the functions Infos(), Captions() and Backgrounds(). For defining the language, you will need to pass the language-index as parameter to the function. The language-index is the index which is used internally by the Infoserver for languages. In case you are using the script-presets in the scripteditor, then these language-indeces are listed as constants.

This allows you to use the constant as parameter when querying for a specific language:

In case you want to send several emails to different languages in one scriptfilter, then the language-index must be passed to the functions SendMail() and SendSMTPMail() at the position of the parameter mReserved:

11.2.3 InfoToAnywhere

Using the MailToInfo and InfoToMail interfaces, it is possible to distribute Infos nearly everywhere. Using the combination of InfoToMail and MailToInfo, it is possible to distribute Infos to external networks using bestinformed.

In the following examples, we are showing you three possibilites of how you can distribute messages nearly everywhere.

11.2.3.1 Infos to external networks

As an external service provider, usually one can not access a customers network for security reasons. Nevertheless, providing Infos with bestinformed is wanted from the customer. At a first look, this objective is a hard to solve problem. Nevertheless, it can be solved easily and with little effort. All that is needed, is that both parties are using bestinformed in the Professional Edition or higher. Then, the service provider can distribute messages to the customer by sending an email to the customer, which is composed in the MailToInfo syntax. All the customer needs to do, is to configure the receiving account to forward the message automatically to his own Infoserver, which then is able to translate the email into an Info.

Example: Setting up an InfoToMail group

In the following example, we are demonstrating how such a group could be set up on the service provider side. All we need to do, is to configure a group member via scriptfilter, which will automatically send an email to the customer providing the correct syntax for an Info.

1. Create a new group of type Info2Mail

2. Add a new member to this group using the scriptfilter

In the scriptfilter, you now must set the mailbody to include the MailToInfo syntax. We recommend you to store a template for the mailbody in a textfile and to load it using the LoadFromFile() function.

program ServerScript; var mDomain, mUsername, mProfile, mTo, mCC, mBCC, mSubject, mBody, mAttachments: String; Res:Boolean; begin // First we need an account, using Domain accounts mDomain := 'YourDomain'; // '.' means localhost // Username mUsername := 'YourUsername'; // MailProfilename mProfile := 'cordaware'; // write your profilename when you use outlook, leave it empty using outlook express // sendto mTo := '[email protected]'; // customers bestinformed account! // IMPORTANT! SUBJECT MUST BE NEWINFO mSubject := 'newinfo'; mBody :=LoadFromFile('C:\Programs\Cordaware\MailToInfo\customer_b_M2I.txt'); // StrReplace replace string, insert Infotext into the mailbody mBody := StrReplace(mBody,'%Info%',Info); // Info is a variable containing the info // no Attachments mAttachments :=''; // Sending e-Mail Res := SendMail(mDomain,mUsername,mProfile,mTO,mCC,mBCC,mSubject,mBody,mAttachments); // SetResult SetResult(Res); end.

The scriptfilter now already is configured for sending the email to the customer.

3. Set up mailbody in template file

Now you have to configure the mailbody template, using the MailToInfo syntax. Simply create a new textfile and insert the parameters you want to use.

Example for a minimal configuration:

username=admin password=xyzxyzxyz

Info=%Info% groups=administrators,teamleaders quickusers=john.doe;*;*

As you can see, we've already defined the recipients in the template. Since we haven't defined any other parameters, the customer's Infoserver will use its own default settings. The placeholder %Info% will be replaced with the original Infotext by the scriptfilter function.

You now could set up further group members or compose new groups with different recipients. As a part of an Infoscenario, you then could set different messages for different recipeints on customer side.

4. Implementation on customer side

The receiving customer now must configure the receiving email account to automatically forward the message to his own Infoserver using the MailToInfo interface.

Notice: when forwarding an incoming email, you need to make sure that the subject and the bodytext are not altered in any kind. Adding a FW: prefix to the subject will lead to failure as well as any changes in the bodytext.

11.2.3.2 Infos to SMS recipients

In some very urgent cases, it may become necessary to inform a group of users via SMS as a part of your information strategy. Most SMS providers offer an SMTP gateway for forwarding incoming emails via SMS. With bestinformed, you can use this interface too. This way, your messaging can be done with one tool, Cordaware bestinformed.

Simply setup an Info2Mail group or group-member, which is configured to forward the Info to your SMS provider.

Example:

In our example, we assume that the SMS provider will read the sender and recipients of the SMS from the bodytext of the email. Also, the bodytext is included in the email's bodytext, which will need to be plain text. An example scriptilter for the Info2SMS group could look like this:

program ServerScript; var mDomain, mUsername, mProfile, mTo, mCC, mBCC, mSubject, mBody, mAttachments: String; Res:Boolean; begin // First we need an account, using Domain accounts mDomain := 'YourDomain'; // '.' means localhost // Username mUsername := 'YourUsername'; // MailProfilename mProfile := ''; // write your profilename when you use outlook, leave it empty using outlook express // sendto mTo := '[email protected]'; mSubject := 'newsms'; // replace with subject needed from provider // LOADING PRECONFIGURED MAILBODY FROM FILE mBody :=LoadFromFile('c:\Programs\Cordaware\bestinformed\MailToInfo\sms_body.txt'); // insert info into mailbody mBody := StrReplace(mBody,'%Info%',Info); // Info is a variable containing the info // Sending e-Mail Res := SendMail(mDomain,mUsername,mProfile,mTO,mCC,mBCC,mSubject,mBody,mAttachments); // SetResult SetResult(Res); end.

As you can see in our example, we are using a template-textfile again for the mailbody. Depending on your provider, it could look like this:

from:+491712345678 to:+491719876543;+491717654321

message:%Info%

In the template-textfile, we are using the placeholder %Info%, which will be substituted with the Infotext.

Notice: When sending an email, which is intended to be forwarded to a SMS recipients, you must be aware that you must not perform any formatting, because SMS is simple ASCII text, any HTML tags won't be interpreted by the receiving cellphone. The cellphone will display the HTML tags as clear text. Also one should always keep in mind, that a maximum of 160 characters can be sent in one message. If the message is longer than 160 characters, it will need to be splitted up.

11.2.3.3 InfoToFax

Many communication-service providers offer the possibility, to generate fax messages from emails. Most commonly, the fax message is either defined in the mailbody, or the fax message can be attached as a file (e.g. price-list as PDF file).

Our script-example shows, how you can set up an Info2Mail group-scriptfilter, which will send an email to a service-provider with the fax message attached as a file

program ServerScript; var mDomain, mUsername, mProfile, mTo, mCC, mBCC, mSubject, mBody, mAttachments: String; Res:Boolean; begin // First we need an account, using Domain accounts mDomain := 'YourDomain'; // '.' means localhost // Username mUsername := 'YourUsername'; // MailProfilename mProfile := ''; // write your profilename when you use outlook, leave it empty using outlook express // sendto // recipient in example is composed as faxnumber@service-provider mTo := '[email protected]'; // mind to use the correct syntax for the mail recpient as needed from provider mSubject := 'new fax from Cordaware'; // or set subject as needed from provider mBody := 'New fax from Cordaware'; // Or insert full text // attach file for fax-body if supported by service-provider mAttachments := 'C:\Programs\Cordaware\bestinformed\faxfile.doc'; // Sending e-Mail Res := SendMail(mDomain,mUsername,mProfile,mTO,mCC,mBCC,mSubject,mBody,mAttachments); // SetResult SetResult(Res); end.

11.2.4 API

When using bestinformed Professional Edition edition or higher, the API interface is included.

With this module, you can access the Infoserver from an external application.

If, for example, you are using a programme to guard over your mail server and if this programme generates error messages upon a crash down, you can send this message to the Infoserver, and the Infoserver will distribute the Info to all administrators so they are informed and can react instantly.

This function has to be programmed by yourself through the help of the API. On demand, our development team can advise you in the interface implementation.

Notice: In version 4, the release of Infos submitted to the Infoserver through API must be set in the configuration file Infoserver.ini: APIReleaseAsDefault=true/false

11.2.4.1 Header

Here you can see the prototype functions of the API.

**************************** Consts ********************************* INFO_SERVER_ERROR = -1;

INFO_OK = -2; INFO_YES = -3; INFO_NO = -4;

INFO_EOF = -5; INFO_BOF = -6;

INFO_BAD_RESULT = -9; INFO_UNKOWN_ERROR = -10;

INFO_AUTHENTICATION_FAILED = -99; INFO_PASSWORD_WRONG_PASSWORD = -60;

INFO_GROUP_NOT_FOUND = -100; INFO_GROUP_ALREADY_EXISTS = -101; INFO_GROUP_NAMEMUSTHAVEAVALUE = -102; INFO_GROUP_GROUPNAME_RESERVED = -103;

INFO_USER_NOT_FOUND = -10; INFO_USER_ALREADY_EXISTS = -11; INFO_USER_ALL_VALUES_EMPTY = -12;

INFO_INFO_STATUS_UNKOWN = -999; INFO_INFO_NOT_FOUND = -1000; INFO_INFO_NOT_EDITABLE = -1001; INFO_INFO_STATUS_WAITING = -1002; INFO_INFO_STATUS_ACTIVE = -1003; INFO_INFO_STATUS_FINISHED = -1004; INFO_INFO_STATUS_CANCELED = -1005; INFO_INFO_INFOMUSTHAVEAVALUE = -1100; INFO_INFO_SHOWONUSERSORWINLOGONDESKTOP = -1101; INFO_INFO_BEGIN_NOT_VALID = -1102; INFO_INFO_END_NOT_VALID = -1103;

++++++++++++++++++++++++ INFO ++++++++++++++++++++++++

*********************************************************************

function info_serverok(address,port,username,password: pchar): Integer;

------

Check if server is found and running

If the function succeeds, the return value is INFO_OK

If the function fails, the return value is INFO_SERVER_ERROR

*********************************************************************

function info_changepassword(address,port,username,password,newpassword: pchar): integer;

------

Change the password on infoserver

If the function succeeds, the return value is INFO_OK

If the function fails, the return value is INFO_SERVER_ERROR

*********************************************************************

function info_infonextid(address,port,username,password: pchar; id: integer): integer;

------

Get the next ID of infos

If the function succeeds, the return value is the next ID > 0

If the function fails, the return value is INFO_SERVER_ERROR or INFO_EOF or INFO_BOF

*********************************************************************

function info_InfoGetID(address,port,username,password,info: pchar): integer;

------

Return the ID of Info

If the function succeeds, the return value is the ID of Info > 0

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_InfoCanceled(address,port,username,password: pchar; id: integer): integer;

------

Return if the info was canceled

If the function succeeds, the return value is INFO_YES or INFO_NO

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_InfoStatus(address,port,username,password: pchar; id: integer): integer;

------

Return the status of the given info with ID = id

If the function succeeds, the return value is INFO_INFO_STATUS_UNKOWN or INFO_INFO_STATUS_WAITING or INFO_INFO_STATUS_ACTIVE or INFO_INFO_STATUS_FINISHED or INFO_INFO_STATUS_CANCELED

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_InfoRunningOnClient(address,port,username,password: pchar; id: integer): integer;

------

Return if the info may be running on some clients

If the function succeeds, the return value is INFO_YES or INFO_NO

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_InfoValues(address,port,username,password, Info, ABegin, AEnd, Soundfile, GroupList: PChar; var Minutes, Infinity, ActiveMinutes, Continue, ShowOnUsersDesktop, ShowOnWinLogonDesktop, CanCloseOnUsersDesktop, CanCloseOnWinLogonDesktop, BeepEnabled, BeepCount, AllGroups, ID: Integer): Integer;

------

Return the values of given info with ID = id

If the function succeeds, the return value is INFO_OK

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_InfoAdd(address,port,username,password, Info, ABegin, AEnd, Soundfile, GroupList, Days: PChar; Minutes, Infinity, ActiveMinutes, Continue, ShowOnUsersDesktop, ShowOnWinLogonDesktop, CanCloseOnUsersDesktop, CanCloseOnWinLogonDesktop, BeepEnabled, BeepCount, AllGroups AllDays, CloseOnClick, CancelOnClose): integer;

------

Add info with given values

If the function succeeds, the return value is the ID of added info

If the function fails, the return value is INFO_INFO_INFOMUSTHAVEAVALUE or INFO_INFO_SHOWONUSERSORWINLOGONDESKTOP or INFO_INFO_BEGIN_NOT_VALID or INFO_INFO_END_NOT_VALID

*********************************************************************

function info_InfoEdit(address,port,username,password, Info, ABegin, AEnd, Soundfile, GroupList, Days: PChar; Minutes, Infinity, ActiveMinutes, Continue, ShowOnUsersDesktop, ShowOnWinLogonDesktop, CanCloseOnUsersDesktop, CanCloseOnWinLogonDesktop, BeepEnabled, BeepCount, AllGroups, AllDays, CloseOnClick, CancelOnClose ID: Integer): Integer;

------

Edit info with given values for ID = id

If the function succeeds, the return value is the ID of the info

If the function fails, the return value is INFO_INFO_INFOMUSTHAVEAVALUE or INFO_INFO_SHOWONUSERSORWINLOGONDESKTOP or INFO_INFO_BEGIN_NOT_VALID or INFO_INFO_END_NOT_VALID or INFO_INFO_NOT_FOUND

*********************************************************************

function info_InfoDelete(address,port,username,password: pchar; id: integer): integer;

------

Delete the info with ID = id

If the function succeeds, the return value is INFO_OK

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_InfoCancel(address,port,username,password: pchar; id: integer): integer;

------

Cancel the info with ID = id

If the function succeeds, the return value is INFO_YES or INFO_NO

If the function fails, the return value is INFO_INFO_NOT_FOUND

++++++++++++++++++++++ History +++++++++++++++++++++++

*********************************************************************

function info_Historynextid(address,port,username,password: pchar; id: integer): integer;

------

Get the next ID of infos

If the function succeeds, the return value is the next ID > 0

If the function fails, the return value is INFO_SERVER_ERROR or INFO_EOF or INFO_BOF

*********************************************************************

function info_HistoryGetID(address,port,username,password,info: pchar): integer;

------

Return the ID of Info

If the function succeeds, the return value is the ID of Info > 0

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_HistoryCanceled(address,port,username,password: pchar; id: integer): integer;

------

Return if the info was canceled

If the function succeeds, the return value is INFO_YES or INFO_NO

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_HistoryStatus(address,port,username,password: pchar; id: integer): integer;

------

Return the status of the given info with ID = id

If the function succeeds, the return value is INFO_INFO_STATUS_UNKOWN or INFO_INFO_STATUS_WAITING or INFO_INFO_STATUS_ACTIVE or INFO_INFO_STATUS_FINISHED or INFO_INFO_STATUS_CANCELED

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_HistoryRunningOnClient(address,port,username,password: pchar; id: integer): integer;

------

Return if the info may running on some clients

If the function succeeds, the return value is INFO_YES or INFO_NO

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_HistoryValues(address,port,username,password, Info, ABegin, AEnd, Soundfile, GroupList: PChar; var Minutes, Infinity, ActiveMinutes, Continue, ShowOnUsersDesktop, ShowOnWinLogonDesktop, CanCloseOnUsersDesktop, CanCloseOnWinLogonDesktop, BeepEnabled, BeepCount, AllGroups, ID: Integer): Integer;

------

Return the values of given info with ID = id

If the function succeeds, the return value is INFO_OK

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_HistoryAdd(address,port,username,password, Info, ABegin, AEnd, Soundfile, GroupList, Days: PChar; Minutes, Infinity, ActiveMinutes, Continue, ShowOnUsersDesktop, ShowOnWinLogonDesktop, CanCloseOnUsersDesktop, CanCloseOnWinLogonDesktop, BeepEnabled, BeepCount, AllGroups AllDays, CloseOnClick, CancelOnClose): integer;

------

Add info with given values

If the function succeeds, the return value is the ID of added info

If the function fails, the return value is INFO_INFO_INFOMUSTHAVEAVALUE or INFO_INFO_SHOWONUSERSORWINLOGONDESKTOP or INFO_INFO_BEGIN_NOT_VALID or INFO_INFO_END_NOT_VALID

*********************************************************************

function info_HistoryEdit(address,port,username,password, Info, ABegin, AEnd, Soundfile, GroupList, Days: PChar; Minutes, Infinity, ActiveMinutes, Continue, ShowOnUsersDesktop, ShowOnWinLogonDesktop, CanCloseOnUsersDesktop, CanCloseOnWinLogonDesktop, BeepEnabled, BeepCount, AllGroups, AllDays, CloseOnClick, CancelOnClose ID: Integer): Integer;

------

Edit info with given values for ID = id

If the function succeeds, the return value is the ID of the info

If the function fails, the return value is INFO_INFO_INFOMUSTHAVEAVALUE or INFO_INFO_SHOWONUSERSORWINLOGONDESKTOP or INFO_INFO_BEGIN_NOT_VALID or INFO_INFO_END_NOT_VALID or INFO_INFO_NOT_FOUND

*********************************************************************

function info_HistoryDelete(address,port,username,password: pchar; id: integer): integer;

------

Delete the info with ID = id

If the function succeeds, the return value is INFO_OK

If the function fails, the return value is INFO_INFO_NOT_FOUND

*********************************************************************

function info_HistoryCancel(address,port,username,password: pchar; id: integer): integer;

------

Cancel the info with ID = id

If the function succeeds, the return value is INFO_YES or INFO_NO

If the function fails, the return value is INFO_INFO_NOT_FOUND

++++++++++++++++++++++++ GROUPS ++++++++++++++++++++++

*********************************************************************

function info_GroupNextId(address,port,username,password: pchar; id: integer): integer;

------

Get the next ID of groups

If the function succeeds, the return value is the next ID > 0

If the function fails, the return value is INFO_SERVER_ERROR or INFO_EOF or INFO_BOF

*********************************************************************

function info_GroupGetID(address,port,username,password,aname: pchar): integer;

------

Get the ID of groups with Name = aname

If the function succeeds, the return value is the group ID > 0

If the function fails, the return value is INFO_GROUP_NOT_FOUND

*********************************************************************

function info_GroupValues(address,port,username,password,aname,adescription: pchar;id: Integer): integer;

------

Get the values of groups with ID = id

If the function succeeds, the return value is INFO_OK

If the function fails, the return value is INFO_GROUP_NOT_FOUND

*********************************************************************

function info_GroupAdd(address,port,username,password,aname,adescription: pchar): integer;

------

Add new group with given values

If the function succeeds, the return value is the new group ID > 0

If the function fails, the return value is INFO_GROUP_ALREADY_EXISTS or INFO_GROUP_NAMEMUSTHAVEAVALUE or INFO_GROUP_GROUPNAME_RESERVED

*********************************************************************

function info_GroupEdit(address,port,username,password,aname,adescription: pchar; id: Integer): integer;

------

Edit group with given values for ID = id

If the function succeeds, the return value is the group ID > 0

If the function fails, the return value is INFO_GROUP_ALREADY_EXISTS or INFO_GROUP_NAMEMUSTHAVEAVALUE or INFO_GROUP_GROUPNAME_RESERVED

*********************************************************************

function info_GroupDelete(address,port,username,password: pchar; id: Integer): integer;

------

Delete the group with ID = id

If the function succeeds, the return value is INFO_OK

If the function fails, the return value is INFO_GROUP_NOT_FOUND

++++++++++++++++++++++++ USERS +++++++++++++++++++++++

*********************************************************************

function info_UserNextId(address,port,username,password: pchar; idgroup,id: integer): integer;

------

Get the next ID of users

If the function succeeds, the return value is the next ID > 0

If the function fails, the return value is INFO_SERVER_ERROR or INFO_EOF or INFO_BOF

*********************************************************************

function info_UserGetID(address,port,username,password,ausername,acomputername,aaddress: pchar;idgroup: Integer): integer; stdcall; external 'InfoApi.dll';

------

Get the ID of user with given values and Group with GroupID = idgroup

If the function succeeds, the return value is the group ID > 0

If the function fails, the return value is INFO_GROUP_NOT_FOUND

*********************************************************************

function info_UserValues(address,port,username,password,ausername,acomputername,aaddress,ascrip tfilter: pchar;id,idgroup: Integer): integer;

------

Get the values of user with ID = id and GroupID = idgroup

If the function succeeds, the return value is INFO_OK

If the function fails, the return value is INFO_USER_NOT_FOUND

*********************************************************************

function info_UserAdd(address,port,username,password,ausername,acomputername,aaddress,ascriptfilt er: PChar;idgroup: Integer): integer;

------

Add new user with given values for Group with GroupID = idgroup

If the function succeeds, the return value is the new user ID > 0

If the function fails, the return value is INFO_USER_NOT_FOUND or INFO_USER_ALREADY_EXISTS INFO_USER_ALL_VALUES_EMPTY

*********************************************************************

function info_UserEdit(address,port,username,password,ausername,acomputername,aaddress,ascriptfilt er: PChar; id,idgroup: Integer): integer;

------

Edit user with given values for ID = id and GroupID = idgroup

If the function succeeds, the return value is the user ID > 0

If the function fails, the return value is INFO_USER_NOT_FOUND or INFO_USER_ALREADY_EXISTS INFO_USER_ALL_VALUES_EMPTY

*********************************************************************

function info_UserDelete(address,port,username,password: pchar; id,idgroup: Integer): integer;

------

Delete the user with ID = id and GroupID = idgroup

If the function succeeds, the return value is INFO_OK

If the function fails, the return value is INFO_USER_NOT_FOUND

++++++++++++++++++++++++ END +++++++++++++++++++++++++

11.2.4.2 Example

In the folder API_Delphi_Example in the root folder of bestinformed, you can find an example written in Delphi. Please use this example as an orientation.

11.3 Extendend Groupmanagement 11.3.1 Scriptfilter Functions

AD / LDAP Usergroups

The function

MemberOFNTGroup(User,'WINNTGroupname')

grants you access to your AD (Active Directory), respectively LDAP, Usergroups.

If, for example, you want to know if a certain user is a member of the group "Administrators", you have to type:

A := MemberOFNTGroup(User,'Administrators') and assign A to the result: SetResult(A);

Also "and" and "or" relations are possible:

A := MemberOFNTGroup(User,'Administrators'); B := MemberOFNTGroup(User,'Office'); A := A or B; SetResult(A);

Indicates whether the user is in the group Administrators or Office.

The Infoserver automatically updates the groups every 24 hours. If this interval is to long for you, simply open the infoserver.ini and set the value RefreshGroupsTime= [int value] in minutes. The default value is 1440, which equals the number of minutes in 24 hours.

AD Computergroups

The function

MemberOFNTComputerGroup(Computer,'WINNTGroupname')

grants you access to Computergroups in your Active Directory.

Notice: This function supports only Computergroups in Active Directory. Computergroups in other LDAP based directory services are not supported.

Filegroups

The function

MemberOFFLGroup(Address,User,Computer,'FileNameInFolderFileGroups')

enables you to query so called Filegroups, which are located in the folder Filegroups.

You can create these groups either manually or automatically.

This is very useful if you want to access groups which are not WinNT or AD groups, as for example database groups.

The format is: user;computer;address in a separate line.

The Infoserver will always load this file automatically if it was edited.

If you have, e.g. an Oracle database with different users, you can save these in the file OracleGroups.txt in the folder Filegroups.

Use following query:

A := MemberOFFLGroup(Address,User,Computer,'OracleGroups.txt'); SetResult(A);

Notice: The usernames in the filegroup-file must be composed in the same manner, as shown in the connection overview. The format user@domain is an invalid syntax!

Arranging Groups

The function

MemberOFISGroup(address,user,computer,'groupname')

enables you to access existing groups on the Infoserver.

For example: with this function you can create a new group from existing groups on the Infoserver.

Address, user and computer are respectively the up-to-date properties of the user, who queries if the info is destined for him.

11.3.2 Groupmanager

The Groupmanager enables you to add and synchronize users, computers and groups from a domain as recipient-groups in the Infoserver.

Important Information for users of Win9x: The Group Manager does operate under Win9x, but you can't connect to your domain. The administration of users and groups on the Infoserver still is possible.

How to access the groupmanager:

In the navigationbar:

1. Groups > Groupmanager 2. Tools > Groupmanager

After starting the application, you first must connect to the Infoserver.

Username: Admin Password: your password Adress: the address of your Infoserver e.g. 192.168.0.40 or computername Port: the Infoserver port

In the next step, you will need to access the domain. For this, following options are available:

Username: Insert the username, with wich you want to authenticate yourself in the domain.

Password: Insert the appropriate password for the user-authentification.

If no username and password are given, then these values will be taken from the current user- session.

Address - Computer - Domain: Here you can insert the IP address or the computername of the desired domain-controller. If only the domain-name is given, then the PDC of the domain will be searched for automatically.

samAccountName: Here you can define, if the samAccountName or the UID (Novell only!) of the user is to be used. Default is samAccountName. UID is to be used only, if your directory service is from Novell.

RootDSE: Here you can define the RootDSE in LDAP syntax (e.g. DC=intern,DC=cordaware,DC=com). Alternatively, you can also use an OU (e.g.OU=Germany,DC=intern,DC=cordaware, DC=com). In this case, it is mandatory to select the option Is OU!

Selection(LdapOnly): Here you can select, which branches of the domain are to be browsed and displayed: groups, users and/or computers.

Group, User, Computer Filter: In case you want to make a preselection of which elements are to be displayed, then you can insert your desired values in the filter. Also, the "*" wildcard is available for replacing any additional characters in the name/value.

Additional Domains: In case Additional Domains with AD access were regisetred in the Infoserver, then these will be listed. By selecting an additional domain from the list, it will be shown additionally to the domain selected above. For the connection to the domain, the settings will be used as defined in the Infoserver.

After a succesful log-on you can start the synchronisation.

To synchronise, click on the Synchronize symbol on the top right hand side of the Group Manager.

The symbol will only be active, if you have selected an Infoserver and a domain, i.e. you must have selected a "branch" in the particular "trees" which belong to an Infoserver, respectively a domain.

A window with synchronisation options opens.

Full

All groups and users are deleted from the infoserver, which are not element of your selected domain.

Smart

Only those users and groups will be deleted, that cannot be element of a domain. The groupmanager files a user always as "Username,*,*", i.e. except for the username all other values are preallocated with wildcards. Does a group contain a user "Username,COM*,*", then this user cannot be created by the groupmanager and therefore wont be deleted.

Simple

No deletion on infoserver side, only groups and users are added that are missing in the infoserver.

After clicking on Start, the result will be displayed as a "tree". Now you can delete some "branches" which you have not added or want to be deleted.

By clicking the SAVE button the comparison is transferred to the Infoserver.

Manual Comparison

You also can execute a manual comparison. Simply select one or more objects from your domain-tree and drag and drop these into the Infoserver-tree.

You can add groups to the Infoserver, users to Infoserver-groups and computername to Infoserver-groups.

It also is possible to edit or add self-defined groups and users to the Infoserver-tree, simply double-click on the particular element.

Editing several users simultaneously

If desired, it is possible to edit several users simultaneously.

Select several users for this (select the first user, by holding down the shift-key you will select every further user up to the last user selected by you, holding down the Ctrl-key and clicking on single users will add or deselect these users from your selection), now click the Edit button, a new window will open in which the modifications can be inserted.

Please mind that a field always must be unique, otherwise the OK button is not available.

Example:

You have created a new group by adding the computers in your network. The users in this group are of the type "*,Computer1,*"..."*,Computer100,*". You went to replace the entry in the username (here: *) with a blank space to ensure, that infos to this group only are displayed on the WinLogon screen, i.e. if a user hasn't logged onto the system. Now click on the Edit button, a new window will open. In this new window, delete the "*" in the field username and click OK. Your entries now should be of the type " ,Computer1,*"..." ,Computer100,*".

With this procedure you can quickly edit some hundred entries in a few moments.

Please note: In large networks of over 1000 users, the display of the domain-tree may take some time. Further on, no subgroups will be displayed but dissolved into single users.

Example:

Group I: Users: Meier,Huber Group II: User: Schmidt Group II -> results in the domain-tree as Group II: Users: Schmidt,Meier,Huber.

The username with which you log on must have the property to register via a network connection! Also, you can execute the groupmanager directly on the domain.

ATTENTION: If you delete groups from the Infoserver, and these groups are assigned to an Info, then these groups will also be deleted from the list of recipients of the assigned Info. If, after deleting a group, an Info is without an assigned group, then the Info will be deleted to! Also, a deleted group is deleted from any other users accumulation of groups. An Info without an assigned group is orphaned and wont't be displayed any longer. Deleting a group effects the deletion of all users assigned to this group.

Infoserver with domaingroups from different domains

When creating a group for the Infoserver, whose members are from different domains, then the scriptfilter for the members from the external domains will be completed by adding the domain-prefix to the group-name:

program Scriptfilter; var A: Boolean; begin A := MemberOfNTGroup(User,'DOMAIN2\GroupXYZ'); SetResult(A); end.

Please mind, that additional domains must be registered in the Infoserver, which are needed for the read-only access.

11.3.3 Autogroups

Introduction

With the Autogroup-mechnism, it is possible to automate the administration of Infoserver groups. This automation is defined in an Inifile, in which the respective actions are defined.

The benefit of Autogroups is, that (alike filegroups) groups can be created from files, yet Autogroups are registered directly on the Infoserver by using the "automatic Filegroup".

The directory for Autogroups is located in the Filegroup folder in the Installation directory of your Infoserver. The Autogroups folder contains three further directories:

Groups: This is the folder, where the Autogroup Inifiles are to be stored for processing

Logs: In this folder, you can find the log-files for Autogroup processes.

Results: This folder contains the results of the group queries (see Assistance).

If a new Autogroup-Inifile is placed in the Groups directory, then the Infoserver will register this automatically and perform the defined actions in the Inifile.

Important: You can save Inifiles directly to the Groups directory from your text-editor. The Infoserver then will create a copy of this file and rename it before processing, so that changes to the original file will not lead to an access conflict.

Please mind, that newly inserted files will be processed only once. This means, that in contrast to Filegroups, any changes to an already processed Autogroup-Inifile will be ignored. Processed Inifiles will be renamed after processing (*.ERROR on failure, *.DONE on success). For this cause, when using the Autogroup mechanism, any changes to existing Infoserver groups have be to placed in a new Inifile.

Attention: If a syntax-error occurs in the Inifile, then all defined processes will be aborted. If the error was found and corrected, then you will to insert the corrected new Inifile into the Groups directory. Changes to the erroneous Inifile will be ignored.

If an error has occured during processing (file-extension *.ERROR), then you can look up the error-message in the respective log-file in the Logs directory. The log-file will use the same filename of the Autogroup-file, using the file-extension *.log.

Setup of the file:

The filesyntax is equivalent to that of any other bestinformed Infile. It is divided in five mainsections, of which every single one must not be duplicate!

[CreateGroups] = Section for creating and configuring new groups.

[UpdateGroups] = Section for editing existing groups.

[DeleteGroups] = Section for deleting existing groups.

[EmptyGroups] = Section for emptying existing groups.

[GetGroups] = Section for retrieving the Autogroup-syntax of existing groups.

In the mainsections, the groups that are to be edited have to be inserted each in a single line. The inserted groups can either be real "groupnames", as well as a label for a groupsection in which the groupname is defined separately.

Example: [CreateGroups] Group_A <- label for groupsection Group_B [Group_A] Name=OfficeUsers ... [UpdateGroups] Group_XY Group_YZ ...

For every group label, you must insert a groupsection of the same name within the respective mainsection.

Example: [CreateGroups] <- mainsection Group_A ... [Group_A] <- groupsection for Group_A within mainsection ... [UpdateGroups] <- mainsection ...

In the section [CreateGroups], every groupsection must use following setup:

[Group_A] Name= Description= Type=Infoclient;Info2Mail Users=Group1Users Powerusers=Powerusers1 UsersFormat=Address;Username;Computername;Description;Script

Name: Here you can define a groupname. If left empty, the label of the groupsection will be used.

Description: Description of the group.

Type: Infoclient or Info2Mail group.

Users: Here you can define the label for the usersection, in which each user (groupmember) has to be defined separately in a new line.

Powerusers: Here you can define the label for the powerusersection, in which each Poweruser, who is to gain the right for addressing this group, has to be defined separately in a new line.

UsersFormat: Here you can define the format and the items, which are to be used when configuring a user in their usersection. Possible items are Address (IP-address), Username, Computername, Description and Script. You must always use at least Username, Computername and Address. If you are using the Script item, then you will have to insert a label for a scriptsection in the user-configuration. Also, the use of the Description item becomes mandatory then.

The setup of the mainsection [UpdateGroups] is equal to the setup of [CreateGroups], additionally you can define actions for already allocated users and Powerusers:

[Group_A] Action=AddUsers;DeleteUsers;ExchangeUsers;AddToPowerusers;DeleteFromPowerusers

The mainsections [DeleteGroups] and [EmptyGroups] don't require any further sections, since the affected groups are listed directly in the mainsection.

Example 1: Creating simple Usergroups

1. Create a new textfile an your desktop.

You can use any desired name, e.g. autogroups.txt or autogroups.ini. In this file, now the Ini-syntax for creating groups via Autogroup mechanism has to be inserted.

Following groups are to be created: Group1 and Group2. Therefore, in the section [CreateGroups] these two groups have to be listed, each in a separate line. Followingly, the group configurations will have to be inserted.

[CreateGroups] Group1 Group2

[Group1] Name=AllBUS Description=Group of BUS Type=Infoclient UsersFormat=Address;Username;Computername Users=Group1Users

[Group1Users] 192.*;*;* 193.*;*;* 194.*;*;cw_*

[Group2] Name=AllAdmins Description=Group of Admins Type=Infoclient UsersFormat=Address;Username;Computername Users=Group2Users

[Group2Users] *;ad_*;* [UpdateGroups] [DeleteGroups]

2. Save the file and copy it to the Groups directory.

The Infoserver now will perform the creation of the configured groups.

Example 2: Create groups with scriptfilter

In the following example, another group is created, in which the memberships are defined via two scriptfilters.

1. Create a new textfile an your desktop and insert the follwoing configuration.

[CreateGroups] Group3

[Group3] Name=ScriptFilterGroup Type=Infoclient UsersFormat=Username;Computername;Address;Script;Description Users=UserDefinition

[UserDefinition] *;*;*;ScriptFilter1;filegroup *;*;*;ScriptFilter2;domaingroup

[ScriptFilter1] program Scriptfilter; var Res: Boolean; begin Res := MemberOFFLGroup(Address,User,Computer,'trainees.txt'); SetResult(Res); end.

[ScriptFilter2] program Scriptfilter; var Res: Boolean; begin Res := MemberOFNTGroup(User,'instructors'); SetResult(Res); end.

[UpdateGroups] [DeleteGroups]

2. Save the file and copy it to the Groups directory.

The Infoserver now will perform the creation of the configured group.

Attention: When using a scriptfilter, the use of the Description item in the UserFormat- syntax is mandatory.

Notice: The items for the user-syntax are lodged in the groupsection (UserFormat=). If one of these items is left out in the user-definition within the usersection (with exception of the username), then this counts as a syntax error.

Example:

[GroupA] Name=AllOAS Description=Group of OAS members Type=Infoclient UsersFormat=Username;Computername;Address Users=UserDefGruppeA

[UserDefGruppeA] *;oas_laptop*;* <- correct syntax ;oas_laptop*;* <- also correct, because an empty username equals logon screen *;oas_laptop* <- defective syntax, because the definition of the IP address item is missing! *;;* <- defective syntax, because the definition if the computername item is missing!

Example 3: Update of a group

In the following example, a new member is added to the to group ScriptFilterGroup created in Example 2. For this, the action AddUsers will be applied.

1. Create a new textfile on the desktop and insert following configuration:

[CreateGroups]

[UpdateGroups] ScriptFilterGroup

[ScriptFilterGroup] Action=AddUsers UsersFormat=Username;Computername;Address;Script;Description Users=UsersDefinition

[UsersDefinition] *;*;*;ScriptDefinition;Infoclientvalue

[ScriptDefinition] program Scriptfilter; var Res: Boolean; begin Res := InfoClientValue('TrainingPC') = 'X'; SetResult(Res); end.

[DeleteGroups]

2. Save the file and copy it to the Groups directory.

The Infoserver now will perform the update of the configured group and add an additional member.

As you have seen in the introduction, there are five types of Actions:

AddUsers = Adds new users to the already existing users.

DeleteUsers = Deletes the specified users from the list of users previously defined.

ExchangeUsers = Exchanges the existing users for a set of new users.

AddToPowerusers = The group is allocated to further Powerusers for addressing. (Enterprise Edition needed)

DeleteFromPowerusers = The addressing-allocation is taken away from the Powerusers specified. (Enterprise Edition needed)

Example 4: Performing two actions on a group-update

If you want to perform two Actions in an update of one group, then you will need to perform these actions in two separate groupsections. The course of action would be, to insert two virtual groupnames as labels in the section [UpdateGroups]. In the groupsections, the real name of the group then has to be inserted. Now you can define different actions in each groupsections.

[UpdateGroups] Update1 <- label for groupsection 1 Update2 <- label for groupsection 2

[Update1] Name=AllBUS <- label of the real group Action=AddUsers <- individual Action 1 UsersFormat=Username;Computername;Address Users=UserDef

[UserDef] john*;*;*

[Update2] Name=AllBUS <- label of the real group Action=AddToPowerusers <- individual Action 2 Powerusers=PowerDef

[PowerDef] john.doe

Example 5: Emptying groups

1. Create a new textfile on your desktop and insert following configuration:

[EmptyGroups] AllBUS

2. Save the file and copy it into the Groups directory.

Now all members/users of the group AllBUS will be deleted yet the group will continue to exist in the Infoserver.

Example 6: Deleting a group

1. Create a new textfile on your desktop and insert following configuration:

[CreateGroups] [UpdateGroups] [DeleteGroups] AllBUS

2. Save the file and copy it to the Groups directory.

The Infoserver now will delete the group "AllBUS" created in Example 1.

Attention: If a group is deleted, then all associations to this group will be deleted as well. For example, the group will be deleted from the recipient list of active Infos, the group will be deleted from templates or it will be deleted from the addressing-rights of a Poweruser as well.

Assistance

To get the Autogroup-syntax of existing Infoserver groups, you can insert the section.

[GetGroups]

in an Inifile.

This section needs an identifier for the groups, which are to be inspected. This is done by inserting.

Groups=

as element of the section.

As argument for the identifier, you can either set All or a label for another groupsection. In the groupsection, you must define each group for inspection in a separate line.

[GetGroups] Groups=All <- inspects all groups

respectively

[GetGroups] Groups=GroupsDef <- label for the groupsection

[GroupsDef] ScriptFilterGroup AllAdmins

Also, the section [GetGroups] can be standalone in an Infile, it is not bound to another mainsection.

The result-file of the section [GetGroups] is saved to the Results folder using the original filename. If a file with the same name already exists, then the name of the current result-file will be extended with an internal number.

11.4 Infoscenarios 11.4.1 Introduction

Infoscenarios are a feature, which enable you to send several Infos simultaneously. In many cases when a problem occurs, different groups need to be provided with different information. Until now, in such a case, every Info had to be composed separately. Now with Infoscenarios it is possible to affiliate several templates into one Infoscenario. When using a scenario, you will only need to edit the message text, respectively ScriptVars in a template, all other settings saved in the template will automatically apply. Infoscenarios are structured hierachically. This allows you to create and maintain the Infoscenarios according to your workflow.

11.4.2 Setting up Infoscenarios

You can access the Infoscenario administration in the top navigation of the Infoserver administration.

In the Infoscenario overview, existing scenarios are displayed in a tree structure to the left of the page. You can collapse the tree structure by clicking on the " + " symbol at the tree-nodes.

There are two types of scenario items:

1. The Infoscenario folder: This item is a node for further scenarios, which are saved as child-items in the tree structure. It doesn't contain any template affiliations. The Infoscenario folder can contain further nodes below its hierarchical position.

2. The Infoscenario single item: The single item contains the template affiliations and is executable. A single item is always at a leaf-position in the hierarchical tree and can not act as a node, as long as template affiliations are existing.

On the right hand side, you can either create a new scenario or edit the currently selected. When creating a new scenario, it will be saved as a child item of the currently selected (if the currently selected can act as a node).

Creating a new scenario

In the Infoserver administration, go to the Infoscenario overview. Here you can create a new Infoscenario directly on the root level of the Infoscenarios. If you already have created an Infoscenario-node, you can also click on that certain node and create a new Infoscenario as a child-item. For a new Infoscenario, you can set following parameters:

Title: This is the label of the Infoscenario. The label is mandatory.

Description: Here you can enter an optional descriptive text.

Color: You can select one of the colors from the dropdown menu. The selected color will be used as background color for the Infoscenario in the overview.

Active: This option defines, if the Infoscenario can be executed or not. If, e.g. a node is inactive, then the branches below this node can not be executed.

After saving the Infoscenario, it is added in tree structure below the (root-)node prviously selected.

Insert template affiliations

Go to the Infoscenario overview and click on an Infoscenario in the hierarchy-tree on the left hand side. After clicking, the settings for this Infoscenario will open on the right hand side. If the selected Infoscenario is not a node, you can affiliate templates by marking the checkbox of the desired templates.

Global Scriptvariables

In templates intended for Infoscenarios, it is possible to use socalled Global ScriptVariables. A Global Scriptvariable is distinguished by the suffix _global attached to its name, e.g. [ScriptVar=Time_global]. If a Global Scriptvariable is used in a scenario, then the value can be adjusted during execution only in the template in which the Scriptvariable has its first occurance. This value will automatically be applied to all occurances of the Scriptvariable in all templates within the scenario. Global Scriptvariables can be equipped with predefined values just like regular Scriptvariables.

Example of use for a Global ScriptVar:

Let's assume the ScriptVar Server_global is given without a default value. Additionally, for pursuing an escalation process in case of a server failure, the templates A, B and C are defined and all of these templates include the mentioned Scriptvariable. Finally, the templates are merged into the Infoscenario Problem Escalation X. Now, when posting the scenario, only template A offers a textfield to insert the a value for the Scriptvariable Server_global. In all other templates in the scenario, the value can't be edited and all occurances of the Scriptvariable use the value defined in template A.

11.4.3 Execute Infoscenario

To execute a scenario, go to the main navigation and click on the hyperlink Scenarios -> Post Scenario.

In the tree-structure to the left, all active scenarios are displayed. Click on the desired scenario in the tree-structure.

On the right hand side of the page, now a list of the templates associated with the scenario is shown. In this list, for each template (and its languages), inputfields are available for editing the background-color, the caption, the Infotext and ScriptVars.

Please mind following rules for editing:

Background-Color: Here you can set the background-color for the Infotext. If a background- color was already set in the template, then it is preselected in the dropdown-menu.

Caption: Here you can edit the Caption saved in the template. If the template was composed using multiple languages, then you can edit the Caption for each language.

Infotexts: If the Infotext was saved in the template without using ScriptVars, then the Infotext will be displayed in its HTML notation (provided that it was formatted). You now can edit the Infotext. If the Infotext was composed in multiple languages, then you can edit the Infotext for each language.

ScriptVars: If the Infotext of a template uses oner or more ScriptVars, then you can only edit the value of the ScriptVars in the scenario. The Infotext is unavailable for editting. If a ScriptVar is used equally in multiple languages, then it must be edited only once. The inserted value then will be used automatically in all equal ScriptVars. If different ScriptVars are used in multiple languages, then each is editable.

The distribution of the Infos is initiated by clicking the Save button. The Infos now are distributed to the recipients as specified in the respective templates.

Important notice for the use of Infoscenarios in the Multiuser-Mode (Enterprise Edition): In the Multiuser Mode, you can give Powerusers the right to execute Infoscenarios as well as the right to create and edit Infoscenarios. In this case, please be mind that a Poweruser will need the right to access the Templates and ScriptVars used in a scenario, as well as the right to address the recipients (groups, channels, users) and functions saved in the templates in use. If the Poweruser lacks the necessary authorizations, then the Infoscenario will not be entirely executed. This will lead to an unwanted loss of information on the recipient side.

Notice for using the All Clear function in Scenarios: For succesfully using the All Clear function in scenarios, in each used template the All-Clear message must be defined for at least All Languages.

11.4.4 Examples

1. Example: Evacuation of a building in case of emergency

In this example, a scenario is created, which is to be used in an emergency (e.g. a major fire on the factory premises). The employees need to be prompted to abandon their desktops and which escape route is safe. Additionally, supervisors need to be informed to guide the evacuation according to their role in the emergency plan. At last, all PC screens in the factory workshop need to be locked.

For these measures, it is necessary to provide appropiate templates:

1st Template > Group 1 - Evacuate on escape route 1

2nd Template > Group 2 - Evacuate on escape route 2

3rd Template > All supervisors - Support evacuation according to emergency role

4th Template > Lock all PC screens in factory workshop

Go to the Scenario Overview und create a new scenario named Evacuation Major Fire.

Now click on the newly created scenario in the tree-structure.

Select the respective templates and save the associations.

Now it is possible to quickly inform the affected employees in an emergency by utilizing the scenario. To send the scenario, click on Scenarios > Send Scenarios in the navigation. Select the scenario Evacuation Major Fire. On the right hand side of the page, the inputfields for editing the Info values from the templates will be displayed.

You now can save the scenario. The messages will be distributed to the recipients according to the settings in the template.

2. Example: Use Case Helpdesk

Situation: Application-Server 3 has crashed. The server hosts two value-adding applications, called application 1 and application 2 in the following. Server administrators predict, that the fix will take up to 40 minutes of time

Now following Infoscenario is applied:

1st Message: To all users of application 1:

Text: Application 1 is affcted by a malfunction and will be available again in approximately 40 minutes.

2nd Message: To all users of application 2:

Text: Application 2 is affcted by a malfunction and will be available again in approximately 40 minutes.

3rd Message: To all helpdesk agents:

Text: Application-Server 3 has crashed - recovery completed in approximately 40 minutes.

4th Message: Message to supervisors:

Text: Job processing of application is not available at the moment, please delegate alternative jobs.

5th Message: Intervall message to Second Level - Every 10 Min until recovery of the application-server is completed

Text: Application-Server 3 not yet available.

11.5 Reports 11.5.1 Introduction

General

The integrated Reporting function provides the integral overview of all data in Cordaware bestinformed. Any information from the bestinformed database can be used for illustration and report preparation.

Common examples:

- Reports all around the Info distribution (e.g. failures, fault clearance, alarms, Statusinfos, Scenarios etc.) - Reports and analyses of Cordaware TED surveys

Default Reports and Report Generator

For using the Reporting functions, Cordaware bestinformed offers two features:

1. Default Reports

Default Reports can be accesed directly from the main menu of the Infoserver administration. The Default Reports offer the possibility, to generate standardized reports with a few mouseclicks directly from the Infoserver-frontend. Example reports are included for your use.

2. Report Generator

For creating individual reports and report-templates, the bestinformed Report Generator is at your disposal. Report projects from the Report Generator can be added to the Default Reports in the Infoserver administration. In general, you can generate any kind of analysis with the Report Generator. Please read our introduction to the generation of report templates.

11.5.2 Default Reports

The Default Reports are the reports, which you can manage and run on the Infoserver administration website. The advantages of these reports are:

· Quick and easy operation · Repeatable · Standardized data queries · Uniform summaries · Improved comparability · Export results to PDF and share instantly

Configure Default Reports

To access the configuration of the Default Reports, click on Reports > Reports management in the menu of the Infoserver administration.

The Default Reports are displayed in a Filetree to the left of the page. You can browse through the Filetree by clicking on the nodes. In the Filetree, you can manage directories and files.

Manage directories

When clicking on a directory, you can perform several actions displayed on the right hand side of the Page.

Save directory = Renames the current directory to the value in the textfield Name.

Delete directory = Deletes the current direcory. If the current directory is not empty, then it can not be deleted.

New directory = Creates a new directory with label as given in Name. The new directory will be created hierarchically as a child element of the current directory.

File upload = Browse for a file and upload it to the current directory by clicking the button Upload.

Manage files

The Default Report files contain the information on: what data is queried and how is it prepared for display. The information stored in these files is processed by the Infoserver and the result is displayed as defined in the report-file. When clicking on a file in the Filetree, following options are displayed on the right hand side of the page.

Save file = Renames the current file to the value given in Name.

Delete file = Deletes the currently selected file.

Notice: Any delete process will be performed without asking for confirmation. Directories can only be deleted, if they are empty.

Execute Default Reports

For executing a Default Report file, click on Reports > Reports execute in the menu of the Infoserver. Browse through the Filetree to the left on the page an click on the desired report- file.

Now the Infoserver will begin to process the report. When finished processing the report, the Infoserver will display the result on the right hand side of the page.

By clicking on the Print button in the result, the report will be exported as a PDF document. You now can either save the PDF document or you can print it right away.

Notice: For distributing the exported report-file with bestinformed, we recommend to save the report-file locally and to upload it then to the Web-directory using the Content- Management.

11.5.3 Report Generator

11.5.3.1 Introduction

With the report generator you can create and design your own reports. This allows you, e.g. to create an analysis of sent Infos or to generate a report of survey results. The datasource for these reports is the internal database of Cordaware bestinformed, which is located in the folder Data in the installation directory of your Infoserver. Reports can be created with tabular and graphical analyses as well. Data-queries, layout-design and export-formats can be self- defined.

In the following, you will be presented the basic steps for operating the Report Generator.

Starting the Report Generator

For starting the Report Generator, execute the file biReporter.exe, which is located in the directory Web\Infoband\Tools in the installation directory of the Infoserver.

When the application has started, select File > New Report from the program-menu of the Report Generator for creating a new report-file.

Connection settings in the Report Generator

For getting the desired data, you will need to set up a connection to the database of Cordaware bestinformed. For setting the connection-data click on the tab Data of the current report project.

On the item-bar to the left of the page, you cand find several connection-elements. For setting up a connection to the bestinformed database, you will need the elements NXWinsockTransport, NXRemoteServerEngine, NXSession, NXDatabase and NXQuery.

For inserting an element in your data-sheet, you will need to select the desired element in the item-bar by clicking on it. When moving the cursor to the datasheet, it will show the outline of the element. Choose the position for the element and insert it by clicking on the position.

After inserting the data-objects, you will need to set the Properties of each element by using the Object Inspector. You can open the Object Inspector by pressing the F11 key or by selecting from the main menu Views > Toolbars > Object Inspector. From the same menu, you can also access the Data Tree and the Report Tree. These are needed for creating the report pages.

NXWinsockTransport1

The object NXWinsockTransport defines the connection type for the database connection. In Cordaware bestinformed, this the TCP/IP proticol over WinSock. In the field ServerName, you will need to insert the comptername of the Infoserver.

ServerName =

Notice: If you enter the value infoserver instead of the comptername of the Infoserver, then the Infoserver will be selected by a DNS lookup.

NXRemoteServerEngine1

The object NXRemoteServerEngine is the client, which handles the connection and the communication to the database. In the field Transport, you will need to insert the object, which defines the communication protocol. In the case of Cordaware bestinformed, this is the object NXWinsockTransport. If a connection-protocoll (NXWinsockTransport object) already exists in the Data sheet of the report, then this will be available for selection in a dropdown menu for the property Transport of the NXRemoteServerEngine.

Transport =

NXSession1

For keeping the communication to the database alive, the NXRemoteServerEngine needs a Session. The association of session to client has to be set in the ObjectInspector of the Session. If a client-object (NXRemoteServerEngine) already existst in the Data sheet of the report, then this will be available for selection in a dropdwon menu when setting the property ServerEngine in the Session object.

ServerEngine = NXRemoteServerEngine1

NXDatabase1

In the database object NXDatabase it is necessary to insert the directory (AliasPath) of the database and to define the Session of the client (NXRemoteServerEngine). You can browse for the AliasPath (by clicking on [...]), the Session is available for selection in a dropdown menu, if it already exists in the Data sheet of the report.

AliasPath = (e.g. C:\Programs\Cordaware\Infoband\Data) Session = NXSession1

Notice: If you execute the ReportGenerator locally, but the Infoserver is run on a remote computer in your network, then you still need to define the local path of the Data directory on the remote computer. Inserting a UNC path is invalid.

NXQuery1

You can create one or more NXQuery objects for a report. In a NXQuery object, a SQL- Query (database-query) is defined. The result of the query can be used for generating the report-content. For creating a succesful query, it is necessary to define the Database and a SQL-string for the query. If a database object (NXDatabase) already exists in the Data sheet of the report, then ist is available for selection in a drowdown menu for the property Database. For inserting a SQL-String, you will need to click on [...] in the row SQL of the NXQuery object.

The SQL-Editor opens in a new window. Here you can insert the SQL string.

By clicking the

button, you can open the Fast Query Builder. In the Fast Query Builder, you can select the tables and fields from the database, which you want to use in your query.

Notice: When opening the Fast Query Builder, the connection to the database will automatically be activated.

When you have finished the assembly of tables and fields for your query, you can create the query string and insert it into the SQL-Editor by clicking the green hook.

Click on the green hook in the SQL-Editor again, to save the query string to your NXQuery object.

Important notice to the SQL Syntax : If you want to read from specific fields of a table only, then it is advisable to wrap the fieldnames in double-quotes " ". This way, a mix-up with with a SQL command can not occur.

Example

SELECT I."Begin", I."End", I."Text", I."Min" FROM InfoHistory I

If a syntax error occurs in the SQL-string, the NXQuery object will deliver no, or a false, result. If, e.g. a fieldname is identical with a SQL command, then this is a syntax error and the fieldname will be displayed bold in the SQL-Editor.

When creating complex queries, which will take some time for processing, you can set an individual timeout in the query.

Example

#T 600000; SELECT * FROM InfoHistory IH ORDER BY IH.ID ASC;

By using the argument #T [time in miliseconds: integer]; you can set in individual timeout. Please notice, that this and all SQL-commands thereafter must be terminated by a semi-colon ";".

When all relevant objects and their properties were set in the Data sheet of your report, then you can manually activate the database connection. The objects NXWinsockTransport, NXRemoteServerEngine and NXSession are activated by setting the property Active on True in their ObjectInspector. The connection to the databse NXDatabase is established by setting the property Connected = True in the ObjectInspector.

Notice: We recommend to save a project as a template for future projects, which already contains the relevant connection-configuration without a specific query object.

In the Report Tree, you now can see all objects of the report as elements of the Data and Page contents.

In the Data Tree, you now can see all queried fields of the SQL-query defined in the NXQuery object.

If multiple NXQuery objects were created in the Data sheet, then these will be shown in the Data Tree as well. In the Data Tree, you can quickly check for a valid result of your SQL- query because the NXQuery object won't contain any child elements, if the query has an error.

Defining the Page layout

By clicking on the tab Page, you can access the Layot-Mode of the current report file.

The Page Layout-Designer offers many options for designing a report. The ReportGenerator offers the possibility, to include predefined layout objetcs in your page design. Some of these layout objects are the ReportTitle, PageHeader, MasterData or the PageFooter as well. You can insert one of these objects by clicking on following button in the vertical menu on the left hand side:

After clicking this button, the second level of the menu opens, in which you can select the desired layout object.

An object is selected by clicking on it in the second level menu. After selecting the desired object, move the cursor to the layout-sheet und insert the object by clicking on the desired position. As a minmal setup for a report-layout, we recommend to use the layout-objects ReportTitle, PageHeader, MasterData and PageFooter.

For adding text to a layout-object, click on following button in the vertival menu on the left:

Now, when moving the cursor to the layout-sheet, then you can see the outlines of a textfield. Move the cursor to the desired layout-object and insert the textfield by clicking on the desired position.

After positioning the textfield, the Memo window will open, in which you can insert the text for this field.

Insert your desired text and click on OK. Followingly, you can adjust position and size of the textfield by moving the coordinates.

Inserting data into the report

When inserting the MasterData layout-object, the program will prompt you to specify a dataset (NXQuery object) as source (DataSet) for the data. Select the desired NXQuery object. For filling your report with data, you will need to pick the desired fields from your NXQuery and insert them into the MasterData layout-object. For this, open the Data Tree and drag the desired field from the NXQuery to the desired position in the MasterData layout- object.

Text formatting

For formatting text and data-fields, the buttons above the layout-sheet are at your disposal.

Preview and export of the report

You can always view the preview of the report by clicking on the Preview tab in the ReportGenerator. You can also acces the preview from the menu File > Preview, or by using the key-combination Ctrl + P.

If the Preview of the report is opened, then several export functions and formats are at your disposal. You can either print the report right away, or you can export the report. Among others, you can use the formats PDF, HTML, OLE, XML, RTF, JPG, BMP, GIF or TXT for exporting to a file.

For further options for designing a report, please see our examples creating tabular and graphical analyses.

11.5.3.2 Report with tabular analysis

In the following example, we will show you how to create a simple report which lists the 20 most recently created Infos from the Infohistory in a table.

1. Setup connection to the database

Create the elements NXWinsockTransport, NXRemoteServerEngine, NXSession, NXDatabase in the Data sheet of your report and set the object properties as described in the introduction.

2. Configure SQL-query in object NXQuery

The report is supposed to list an overview of the 20 most recently created Infos from the Infohistory, displaying begin, end and infotext of each Info in a table. For getting the respective datasets, create a NXQuery and assign the databse NXDatabase to it. Now create following SQL statement for the NXQuery object in the SQL Editor:

SQL statement:

SELECT TOP 20 IH."Begin", IH."End", IH."Text" AS Info FROM InfoHistory IH ORDER BY IH.ID DESC

Now activate the elements NXWinsockTransport, NXRemoteServerEngine and NXSession and connect the database NXDatabase.

3. Configure Page layout

Go to the Page view and create the layout objects ReportTitle, PageHeader, MasterData and PageFooter. Assign the object NXQuery as source to the MasterData object.

Now the layout-objects have to be filled with content.

ReportTitle

Insert a textfield in the object ReportTitle. Adjust the dimensions of the textfield, so that it fits the whole width of the page and format the text as desired (e.g. font-size 22px, centered and underlined).

PageHeader

Insert three textfields and insert into these the values Begin, Ende and Infotext. These teaxtfields serve as tableheads. Add a frame to each textfield.

Arrange the textfields in such a manner, that they will provide enough space for the expected values from the database.

MasterData

The fields from the SQL query are now positioned in the MasterData object. For this, click on the field NXQuery > Begin in the DataTree and move it to its position in the MasterData object per drag'n'drop.

Now move the fields End and Info to the MasterData object in the same manner. Adjust the dimensions and positions of the datafields, so that these match the dimension and position of the respective field in the PageHeader. Add a frame to each field.

To make the datafields self-adjusting to their content, you will need to rightclick an each datafield and select the properties Shift and Stretch to Max Height. Additionally, you will need to right-click on the MasterData object and select the property Stretch.

PageFooter

The footer of the report pages is supposed to display the current page number. For this, click on Varibales in the DataTree and pull the System variable > Page# into the PageFooter.

4. Exporting the report

The report now can be exported (key combination Ctrl + P) as described in the introduction.

11.5.3.3 Report with graphical analysis

This example report extends the report of the first example. In this example, we will create a report, which displays in a bar-chart how many people have received the 20 latest Infos. The source for our data is the Infohistory again, as well as the table ClientInfosDetail from the bestinformed database.

1. Setup connection to the database

Create the elements NXWinsockTransport, NXRemoteServerEngine, NXSession, NXDatabase in the Data sheet of your report and set the object properties as described in the introduction.

2. Configure SQL-queries in NXQuery Objects

For this example report, we will need two SQL-queries (NXQuery objects). In the first SQL- query (NXQuery1), the 20 most recent Infos will be identified from the Infohistory (table InfoHistory). In the second SQL-query (NXQuery2), the respective recippient numbers of these Infos will be determined from the table ClientInfosDetail.

Insert two NXQuery objects in the Data sheet of your report. Edit the respective object- properties by using the ObjectInspector.

NXQuery1

Database = NXDatabase1

Open the SQL-Editor and insert following SQL statement:

SQL Statement:

SELECT TOP 20 IH."Begin" AS Beginn, IH."End" AS Ende, IH."Text" AS Info, IH.ID AS ID FROM InfoHistory AS IH ORDER BY IH.ID DESC

NXQuery2

Database = NXDatabase1 Master = NXQuery1

Open the SQL-Editor and insert following SQL statement:

SQL Statement:

SELECT COUNT(ID) AS MyCount FROM ClientInfosDetail WHERE (ID_Info=:ID_Info)

At this moment, there is no association which parameters are to be handed to NXQuery2 from the Master NXQuery1. For this, you will need to edit the property Params in the ObjectInspector of NXQuery2.

After clicking on [...], the Parameters Editor wil open. In the ParametersEditor, you will need to edit the Parameter ID_Info of NXQuery2 by assigning the DataType Integer and the Value . For assigning the Value, click on the Functions-button in the ParametersEditor.

The ExpressionEditor will open.

In the tab Data, doubleclick on the field ID of the NXQuery1 and save the expression.

The expression now will be assigned to the parameter Info_ID in the ParametersEditor.

Now save the parameters and activate the connection to the database.

3. Configure Page layout

Click on the tab Page for switching to the layout mode of your report. Insert the layout-objects ReportTitle, PageHeader, MasterData and PageFooter as described in the introduction. Assign the NXQuery1 object as source for the MasterData object.

ReportTitle

The ReportTitle contains a textfield with the text Info Overview.

PageHeader

This time, the PageHeader is the headline for the bar-chart. Insert a textfield with content How many people have received the 20 most recent Infos?.

MasterData

In the MasterData, you will need to create the bar-chart. For this, click on the diagram- symbol in the vertical menu.

Insert the chart-field in the MasterData object. Now the Chart Editor will open.

Chart Editor

Click on the symbol AddSeries.

Now you can select from different chart types. Select the type Bar and confirm with OK.

Now, on the right hand side of thr Chart Editor, you can find the sections Data Source, Values and Other Options. Select Dataset as type of Data Source and select the NXQuery1 object from the dropdown menu as the source of the DataSet. The values of the 20 Info IDs are supposed to form the x-axis. For this, select NXQeury1."ID" as value for the Label in the Values section. For the y-axis, the number of recipients is needed. For this, insert NXQuery2."MyCount" as value for Y in the Values section.

Now you can save the chart-settings by clicking on OK. In the next step, you will need to adjust the size of the MasterData object and of the chartfield to provide enough space for the chart. For labeling the x- and y-axis, you can insert a textfield for each.

4. Preview and export of the report

The report now can be exported (key combination Ctrl + P) as described in the introduction.

12. Enterprise

In the Enterprise Edition of Cordaware bestinformed, you can access all functions and features of the Basic and Professional Edition. In addition, following features are available exclusively:

Multiuser Mode

Enables you to setup socalled Powerusers with individual rights. Dynamic Distribution

Dynamic Infoclientvalues for groups with scriptfilter and dynamic channels.

Several Servers

Allows you to setup several additional Infoservers with multiple client-connections as well as a redundant Server-Grid.

12.1 Multiuser

The Multiuser Mode of bestinformed enables you to create and manage so-called Powerusers. These can be created and configured in such a manner, that they meet the requirements of certain roles/positions in your company. Which role is covered by a Poweruser is dependent on the configuration of the Poweruser's profile. Furthermore, it is important to consider the strict hierarchy of the Multiuser Mode, in which the originator of a Poweruser generally has access to all private data of his Powerusers.

Poweruser Hierarchy

Depending on its position in the hierarchy, a Poweruser has various authorizations and views. If, for example, a Poweruser is in parent relation to another Poweruser, then he can not only administer the Poweruser, but can also access all of its private data (vertical relation=inner view). If Powerusers are in a brother-sister relation, then they can not mutually access each others private data, they can only be configured to be able to view the Infos composed by their siblings (horizontal relation=outer view).

Vertical Relation: Inner View - View of all data of a Poweruser below own hierarchical position.

Horizontal Relation: Outer View - Only view of Infos of other Powerusers.

Roles / Ranks of Powerusers

Basically, there are three types of Powerusers:

Sub-Admins: Can use the administrative functions for user- and groupmanagement, as well as the editorial functions of the Infoserver.

Editors: These Powerusers are intended to use the editorial functions.

Read-Only: These Powerusers don't have any administrative or editorial rights, they can only access a Shared Whiteboard / Infofilter for reading.

Overview of functions intended for role:

Admin Sub-Admin Editors Read Only Info overview Create Info Create Infofilter MailToInfo Surveys Statusinfos Distribute Scripts Edit Scripts Edit groups Groupmanager Dynamic Channels Manage Powerusers Manage Domains

Legend:

= Function intended for role

= Function not intended for role

In chapter Roles, you can view a showcase configuration of three different Powerusers.

12.1.1 Hierarchy

12.1.1.1 Poweruser Profiles

The hierarchical setup of the Multiuser Mode will be clearified in the following by the use of a practical example.

Requirement: The manager of the Service Desk is supposed to organize the distribution of Infos through bestinformed to the end-user. Since he's not obliged to maintain the application, he only needs access to certain functions. These functions must include the administration of Powerusers for the Service Desk agents, the maintenance of templates, scenarios and recipient groups as well.

Solution: The administrator of bestinformed creates a Poweruser Profile for the manager of the Service Desk, which includes all necessary functions, authorizations and access.

Profile: Each Poweruser is defined by a profile in the User Management of the Infoserver. The profile contains the properties and functions for the user. In general, the profile's name is also the login-name of the Poweruser. In case the profile name is equal to a valid AD username, then the user can login using his domain password. If the profile's name is not equivalent to an AD user, then a login is possible only under certain circumstances. Hence:

Each Poweruser is defined through its Profile, which contains the properties and authorizations of the Poweruser.

In case of the example, the Poweruser profile be could setup like this:

Functions: Can create Powerusers, send & edit Infos, configure additional Infofields & Infofilters etc.

Access To: Various groups, templates, channels etc.

12.1.1.2 Poweruser Clones

Requirement: The agents of the Service Desk are supposed to send Infos to the end-users through bestinformed. Since all agents supervise the same group of users, they need equivalent authorizations and access. This means, that the Powerusers for the agents must be configured equally in bestinformed.

Solution: The Service Desk manager logs on to the Infoserver with his Poweruser and creates a new Poweruser Profile for the Service Desk agents in the User Management console of bestinformed. The profile of the Service Desk Agents is equipped with all necessary functions and authorizations. Following the configuration, the Service Desk manager is creating so-called Clones of this profile by using the function New User. These clones are independent Powerusers which inherit the configuration of their profile.

Clones: A Clone is a part of a profile. A Clone adds a Poweruser to the profile, who can login using his own name and has access to all properties and authorizations of the profile. However, depending on the configuration, a profile and its clone may have their own private data which is only accessible for themselves. Private data can be self-composed infofilters, templates, groups or further Poweruser Profiles. A profile and its clones have restricted Outer View on each other. The profile can view the Infos created by its clones by default. The clones again can only see the Infos of other Powerusers as configured in the extended access of the profile. Infos submitted by the profile are not visible to the clones. Hence:

A Clone extends a profile by an additional Poweruser, which is equipped with all properties and authorizations of the profile. Depending on the configuration of the profile, a Clone can have its private data.

A profile and its clones have limited Outer View on each other.

By default, the name of a clone is also its login-name. Therefore, if a clone is equivalent to an AD-user, then he can login on the Infoserver using his AD password and username. If a clone is not equivalent to an AD-user, then a login is possible only under certain circumstances, e.g. by using a Login-Link.

In the case of the example, the Poweruser Profile of the Service Desk Agents can be configured in the following way:

Functions: Create & edit Infos, send scenarios etc.

Access To: Groups, templates, scenarios etc.

Now, for adding clones to the profile of the Service Desk Agenst, it is necessary to click on the hyperlink New user in the row of the profile.

In the following form, it is only necessary to define the identity of the Poweruser. Functions and access are inherited from the profile.

In the overview of the Powerusers, the name of the profile is displayed in the column Name, the clones of a profile are displayed in the column Users.

12.1.1.3 Poweruser Hierarchy

Requirement: The Poweruser profile of the Service Desk manager was setup in such a way, that the Service Desk can manage their own groups in addition to the groups that were allocated originally by the administrator. Yet, it is necessary that the administrator of bestinformed also has access to the Service Desk's own groups, since he's not able to see them in his view of the Groupmanagement.

Solution: The Multiuser Mode is built hierarchically. If a Poweruser is the originator/owner of another Poweruser profile, then he can view all of his hierarchically secondary Powerusers in the User Management. Additionally, he can log on to bestinformed in his secondary Poweruser profiles and clones. This grants him access to the private data of his secondary Powerusers.

Hierarchy: In general, a Poweruser can create and manage his own Poweruser profiles, which generates a parent-child relationship between him and his own Poweruser profiles and clones. Also, a parent Poweruser in general has the ability to log on to bestinformed in the identity of his children. By adopting the identity of his Poweruser children, the parent can access the children's private data like groups, templates, infofields etc. Therefore, a Poweruser parent has, next to the Outer View, the Inner View on his children! In principle, there are no limits on the nesting-depth of the hierarchy, a poweruser can own any number of children and grand- children, including the ability to adopt their identity. Hence:

A Poweruser, who is in a parent-child relationship to other Powerusers, generally has the Outer and Inner View on his children and grand-children, which grants him administrative access to their private data.

The Admin account is the hierarchically highest Poweruser. He can see and edit all Poweruser profiles and adopt their identities operatively.

Inner View - Adopting a childs identity: For adopting the identity of a secondary Poweruser, it is necessary to apply a special login-syntax. This syntax is characterized by the operator :: , which has to be inserted into the field Username between the Poweruser and the identity he wants to adopt. To the left of the operator, you must insert the name of the parent Poweruser and to the right of the operator, you must insert the name of the Poweruser whos identity you want to adopt. The password must be the password of the parent Poweruser, the password of the Poweruser whos identity you want to adopt is invalid.

Example: The admin wants to adopt the identity of the profile ServiceDesk. For this, he inserts his name followed by the operator :: and the name of the profile he wants to adopt. In the field Password, the admin now must insert his own password in order to login succesfully.

12.1.1.4 Poweruser Container

Requirement: The manager of the Service Desk has asked the administrator of bestinformed, if he could have a look at his Powerusers.

Solution: The admin can browse through the various levels of the hierarchy in the User Management of bestinformed. This enables him to view the configuration of the secondary Powerusers in the Service Desk manager's Container.

Container: The Container resembles the Poweruser overview of previous versions of Cordaware bestinformed, but with the difference that it is possible to browse through all levels of the Poweruser hierarchy now. The container is the view of a Poweruser on his direct descendants (profiles and clones) in the next lower level of hierarchy. In his container, a Poweruser can go to the containers of his children. This enables him to view and edit (if configured) the profiles of his grand-children. Hence:

In general, every Poweruser in bestinformed has his own Container. The container lists all Powerusers, which are hierarchically direct descendants of the current Poweruser. By clicking on the name of a Poweruser, it is possible to switch to the container of the selected Poweruser and to see all of his direct descendants.

red: Container blue: Profile green: Clones

For switching into the container of a child Poweruser, you need to click on its name in your container.

Next to the name of the profile is the number of Powerusers in this profile. This sum is made up of the number of clones of the profile and the direct children of the profile itself. Children of the clones are not added to the number of Powerusers in the profile, but listed separately as a number next to the clone.

By clicking on the name of the Poweruser, in whose container one currently lodges, it is possible to return to the container on the next highest level of the Poweruser hierarchy, but ultimately only into the container of the Poweruser as which one is logged in.

Creating a Poweruser profile in the container of a child Poweruser

Requirement: The administrator of bestinformed wants to create a new Poweruser in the container of the Service Desk manager, however this Poweruser must have access to a group which is not allocated to the Service Desk.

Solution: The administrator of bestinformed logs on to the Infoserver in his own account and switches to the container of the Service Desk manager in the User Management. There, he creates a new Poweruser profile and allocates a group, to which the Service Desk has no access.

If a Poweruser is in the container of one of his child Powerusers, then he can create and manage further Powerusers in this foreign container. However, he can only pass on the authorizations with which he's equipped himself! Through this mechanism, the Poweruser can create new Powerusers on any position in the hierarchy beneath his own. Hence:

A Poweruser can create new Powerusers on any position in the containers of his children and grand-children. He can hand down all properties and authorizations which he owns.

12.1.2 Roles

In this chapter, we will guide you through the process of creating three different Powerusers in order to illustrate the previously introduced role-concept. For this illustration, following fictious situation is given:

The administrator of bestinformed is instructed to create a Poweruser for each department- supervisor, so that these can distribute messages in their departments. One of these supervisors is Karen Miller, she is the head of the helpdesk. She is to create and manage Powerusers for her helpdesk agents, so that these can distribute information companywide. In addition, she is to create a public Shared Whiteboard, on which all employees can inform themselves on current announcements and incidents.

From this fictious situation results following approach:

1. Administrator creates the Sub-Admin "Karen Miller".

2. Sub-Admin "Karen Miller" creates Powerusers with editorial rights.

3. Sub-Admin "Karen Miller" creates Poweruser with read-only access and allocates Shared Whiteboard.

In the following examples, we will use the approach of the fictious situation. Roles and persons can be adjusted to the initial position in your company.

12.1.2.1 Sub-Admin

As mentioned previously, a Sub-Admin can hold extensive rights and can access a large number of the Infoserver functions.

1. Create Poweruser with Sub-Admin rights

The first step is the creation of a Poweruser and the allocation of Infoserver functions. These are configured in the form for creating a new Poweruser.

There are two methods of accessing the form for creating a new Poweruser:

1. In the navigation menu of the Infoserver

2. In the User Management

Open the form for creating a new Poweruser.

Enter the username of the employee, for whom the Poweruser is intended. Description and displayname are optional.

You can also define an individual sessiontimeout. The entered value is in minutes. If no value is entered, then the default sessiontimeout of the Infoserver will be used (see also Infoserver Inifile).

Important: In the field "Displayname" you can insert an alias for the username. This alias is used for displaying the editor of an Info in the Info Overview and the Infogrid. This alias can also be used to comply with possible reporting and privacy guidelines by inserting a job-title instead of a username, e.g. "Servicedesk Agent". With this alias, a login is not possible!

Now the functions must be activated, which make this Poweruser a Sub-Admin.

Next to the caption Poweruser admin are the two functions, which define the basic properties of a Sub-Admin:

Can create powerusers, with no rights higher than his

The selection of this option effects, that the Poweruser becomes a Sub-Admin. He can now create and manage Powerusers.

Attention: As you can see from the caption of this option, the Sub-Admin can only hand down functions, properties and allocations which he owns or were allocated to him.

Creating groups NOT allowed!

If this option is enabled, the Sub-Admin can't create and manage own groups, but only access those groups allocated by the originator. The use of the groupmanager is an exclusive right of the administrator, a Sub-Admin cannot access the groupmanager.

Notice: In the following, you are presented a list of the remaining properties and authorizations in this form. Please mind continously, that only the authorizations defined in this mask can be handed down by the Sub-Admin. This may cause, that some functions need to be activated which the Sub-Admin won't necessarily need, but the Powerusers created by the Sub-Admin.

Can login using hyperlink = By selecting this option, a hyperlink will be generated and shown in the user overview. By using the URL of this hyperlink, a Poweruser can log onto the Infoserver without entering username and password. Nevertheless, a login with username and password is still possible.

For our example, this option has to be selected, because it will have to be used when creating the Read Only Poweruser.

Website:

By selecting the Website borders invisible option, only the main input frame will be displayed after logging in. This is useful, when setting up a read-only user with shared whiteboard or an editor with restrictive rights, because the navigational menu will be hidden.

Info:

Allowed to create Infos = This option defines, if the Poweruser can create Infos.

Allowed to delete own Infos = This option defines, if the Poweruser can delete his own Infos.

Allowed to change (edit/delete/cancel) Infos of other users = This option defines, if the Poweruser can edit and delete Infos of other Powerusers.

Beep allowed = This option defines, if the Poweruser can perform a system beep on the client PC when sending an Info.

Sound allowed = This option defines, if the Poweruser can play a soundfile on the client PC when sending an Info.

Minihtmleditor allowed = This option defines, if the Poweruser can use the Minihtmleditor.

Tabview on edit Info = This option defines, if the Poweruser can utilize the tab-mode when creating and editing Infos.

Wysiwyg-Editor allowed = This option defines, if the WYSIWYG editor is available for the Poweruser in order to format Infos.

Offline Infos allowed = This option defines, if the Poweruser can send Infos in offline mode.

Recurring allowed = This option defines, if the Poweruser can setup recurring Infos.

Language allowed = This option defines, if the Poweruser can use the language selection for defining recipients.

Channels allowed = This option defines, if the Poweruser can use Channels for defining recipients.

Popup allowed = This option defines, if the Poweruser can send an Info as Popup. This also includes the function for creating a full-screen popup.

Single users allowed = This option defines, if the Poweruser can address single users.

For our example, all options are to be selected.

Inifile:

Info as inifile allowed = This option defines, if the Poweruser can edit the clients' inifiles by sending an Info. This is necessary for e.g. defining the Info-separator, setting Infoclientvalues or proxy settings.

For our example, this option is to be selected.

History:

History view NOT allowed = This option defines, if the Poweruser can access the Info history.

Menu view NOT allowed = This option defines, if the Poweruser can access the navigation menu.

Attention: This option has an exceptional behaviour: If you select this option when creating a Sub-Admin, this option won't be available for him when creating a Poweruser. Furthermore, the access to the navigation will be blocked for him AND his Powerusers.

For our example, keep this option unselected. The Sub-Admin though will be able to select this option when creating Powerusers.

Infofilter:

Select info filter allowed = This option defines, if the Poweruser can select between allocated Infofilters.

Create info filter allowed = This option defines, if the Poweruser can create own Infofilters.

Info default view allowed = This option defines, if the Poweruser can access the Info default view, which is generated by the Infoserver.

Default Info Filter = This option defines, which allocated Infofilter is to be shown by default when accessing the Info overview.

For our example, all options have to be selected because the Sub-Admin has to use all these functions. Because the creation of the Poweruser is not yet finished, no Infofilters are allocated. As soon as an Infofilter is allocated, you can set a default Infofilter.

Status messages:

Configure status messages = This option defines, if the Poweruser can configure status messages.

For our example, accessing status messages is not necessary.

Scenarios:

Scenario management = With this option, you can assign the right to access the Infoscenario- Overview and create own or edit allocated Infoscenarios.

Can post scenarios = With this option, you can assign the right to execute allocated (and own) scenarios.

Notice: For succesfully executing a scenario, the Poweruser must have acces to the templates and their properties (e.g. Info functions, recipients, groups).

Connections:

Can see connections = This option defines, if the Poweruser can access the connections overview. This is necessary, for checking e.g. which clients have received a message or are currently connected.

For our example, this option is needed because the helpdesk agents need to be able to check, if an Info was received by a client.

Script:

Allowed to send script = This option defines, if the Poweruser can perform scripts with the add- on Remote Access. The scripts need to be allocated to the poweruser. Editing scripts is an exclusive right of the administrator, this function is not available for Powerusers.

For our example, Remote Access is not needed.

Scriptvars:

Allowed to edit Scriptvars = This option defines, if the Poweruser can edit allocated and create own Scriptvars. The use of allocated Scriptvars remains unaffected by this option.

For our example, this option is to be selected, because the Sub-Admin will need to create own Scriptvars.

Survey:

Allowed to create survey = This option defines, if the Poweruser can create own, edit and perform existing surveys.

Allowed to delete surveys = This option defines, if the Poweruser can delete existing surveys.

Allowed to delete analyses = This option defines, if the Poweruser can delete survey results.

User can use his own corporate design = This option defines, if the Poweruser can integrate a Coprorate Design in the survey pages.

For our example, the use of surveys is not necessary.

MailToInfo:

MailToInfo allowed = This option defines, if the Poweruser can use the MailToInfo interface for distributing Infos.

For using the MailToInfo interface, the email to the Infoserver needs to provide a method of authentication. This is achieved by submitting the username and one of the following four methods:

Authentification with Password = This option defines, that additionally to the username a password has to be included in the email text.

Authentification with TCPIP Address = This option defines, that additionally to the username the IP address of the submitter will be checked.

Authentification with Password and TCPIP-Address = This option defines, that additionally to the username a password has to be included in the email text and that the IP address of the submitter will be checked.

Authentification with signed Email (S/MIME) = This option defines, that a signed email has to be used for authentification.

For our example, the authentification must be performed by checking the IP address of the submitter.

MailToInfo access:

After setting the authentification method, it is possible to restrict the access. You can enter one or more values in the text, which act as a filter. If several values are entered, they will need to be separated with a ";". It is also possible to use the wildcards "*" and "?".

In our example, access is restricted to IP addresses ranging from 192.168.1.30 to 192.168.1.39. When receiving a MailToInfo email, the Infoserver will check and accept only those emails which were originated from one of the IP-addresses allowed.

Browser access:

In this text field, you can enter a list of IP addresses from which the Poweruser can access the administration website of the Infoserver. If several values are entered, they will need to be separated with a ";". It is also possible, to use the wildcards "*" and "?". In our example, the Poweruser can access the Infoserver from IP addresses ranging from 192.168.1 to 192.168.1.254 (192.168.1.0 and 192.168.1.255 are reserved for network and broadcast address).

To finish the creation of the Sub-Admin, click on save.

The new Poweruser is now listed in the user overview in the user management.

2. Extended acces rights

After the Poweruser was created and the available functions were configured, the extended access rights must be allocated.

Attention: The originator can only hand on the acces rights he owns (or is allocated to) himself.

Following access rights can be allocated:

Groups = Access to existing groups.

Grouped groups = Access to existing grouped groups. If a grouped group contains a group, which is not allocated to the Poweruser, he also can't access it in the grouped group.

Info Filter = Access to existing Info filters.

Template groups = Access to existing template groups. If a template group contains a template which is not allocated to the Poweruser, he also can't access it in the template group.

Templates = Access to existing templates.

Infoview = Access to Infos of other Powerusers for viewing/editing.

Channels = Access to existing Channels.

Infofields = Access to existing Infofields.

Domains = Access to existing Domains.

Scriptvars = Access to existing Scriptvars.

Scenarios = Access to existing Infoscenarios.

Status messages = Access to existing Status messages.

To allocate an extended access right, you must click on the hyperlink Edit [access] in the related column in the row of the user.

Following, an overview of the available elements opens. Here you can select between the dynamic access to all elements available, or access to single elements.

For our example, please select the dynamic access to all elements for following allocations.

· Groups · Grouped groups · Template groups · Templates · Infoview · Channels · Infofields · Domains · Scriptvars

Notice: If you are using a LDAP based directory service other than ActiveDirectory, you must point out to your Powerusers, that they will need to use their domain and a backslash "\" as prefix to their username for logging onto the Infoserver.

12.1.2.2 Editors

In the following steps, the Sub-Admin is to create the Powerusers for the helpdesk agents. For this, a sample will be created. By using the New User function, an arbitrary number of identical Powerusers then can be derived from this sample.

1. Create Poweruser "Editors" as sample

Log onto the Infoserver with the previously created Sub-Admin and go to the user management. Now create a new Poweruser named "Editors" (see previous Chapter). For configuring the role of an editor, it is necessary to activate following functions:

Info:

· Allowed to create Info · Allowed to delete own Infos · Allowed to change (edit/delete/cancel) Infos of other users · Beep allowed · Sound allowed · Minihtmleditor allowed · WYSIWYG-Editor allowed · Offline Infos allowed · Recurring allowed · Language allowed · Channels allowed · Popup allowed · Single users allowed

Infofilter:

· Select Info filter allowed

Connections:

· Can see connections

Now save the Poweruser and allocate the extended access-rights as needed. As soon as one or more Info filters were allocated, you can edit the Poweruser and select a default Info filter.

2. Derive Poweruser from sample

In order to derive a new Poweruser from the just created sample, you simply need to click on the hyperlink New user in the row of the new user.

Now a simplified form for creating a Poweruser will open.

In this form, it is only necessary to save a username and optionally a description and displayname. Functions and allocations then are inherited from the sample.

Notice: If a Poweruser was derived from a sample, then it is not possible to individually set functions and allocations, they are always taken from the sample.

The added Poweruser now is shown in the column Users in a new row beneath the sample. This Poweruser now can log onto the Infoserver using his username and domain password.

12.1.2.3 Read Only

The last step of our example is the creation of a "Read-Only" Poweruser.

1. Create Poweruser "Read Only"

Log onto the Infoserver as Sub-Admin and open the user management. Create a new Poweruser named "Read Only".

Now set following functions:

- Can login using hyperlink

Info Filter:

Deselect all options.

Notice: As soon as an Info filter (e.g. Shared Whiteboard) is allocated, it will automatically be set as the default Info filter.

History:

- History view NOT allowed - Menu view NOT allowed

All other options must be deselected before you save the new Poweruser.

Now set following extended access rights:

Info Filter:

Shared Whiteboard (or any other Info filter designed for public view)

Info view:

Editors (Poweruser Read-Only is supposed to view only Infos created by the helpdesk)

2. Distribute Login Link

Right-click on the Login Link of the Read-Only Poweruser in the user overview and copy the link URL.

The URL of the hyperlink is now saved. Now create a new Info and enter a text with hyperlink, use the copied URL as URL for the hyperlink.

Now you can send this Info with hyperlink to all users, who are to read current messages from the helpdesk. By using the hyperlink in the Info, the users now can access the Shared Whiteboard.

12.1.3 Logon Groups

General

Requirement: The Service Desk manager is on vacation and wants to confide his sub-agent with the supervision of his occupation in bestinformed during his absence. His sub-agent needs access to all data and functions of the Service Desk manager. However, for security reasons the Service Desk manager can't disclose his AD password.

Solution: The admin allocates a Logon Group to the Poweruser profile of the Service Desk manager. The members of the Logon Group can log on to the Infoserver in the profile of the Poweruser they were allocated to.

The Logon Group of a Poweruser profile enables various users to log on to the Infoserver and to adopt the Powerusers identity without the need to have an equivalent Poweruser. The logon group of a Poweruser profile can be allocated in the extended access rights of the profile as well as in the Inifile of the Infoserver. The logon group of a profile can only be allocated by the admin Poweruser of bestinformed. Other Powerusers can not access this function. It is also possible to define a logon group for the admin Poweruser. However, this is a configuration which can only be set in the Inifile of the Infoserver.

Only groups which exist in the Infoserver can be allocated as logon groups for Poweruser profiles. Is a person a member of a logon group, then he can log on to the Infoserver in the profile he was allocated to, just like a parent Poweruser can log on to the Infoserver in any of his childrens Poweruser profiles. Yet, in contrast to a parent Poweruser, the members of a logon group can only adopt the identities of the profile, they can't adopt the profiles and identities of any of the profiles children. Hence:

Members of a logon group can exclusively log on only the profile they are allocated to. The allocation can only be performed by the admin Poweruser. Only Infoserver groups can be allocated which were created by the admin Poweruser.

Logon group for the Admin

The admin Poweruser has a very particular rank in bestinformed. First off, he's hierarchically at the highest position in the hierarchy of Powerusers in bestinformed, which allows him to view and edit all Powerusers. Also, the admin has access to functions which ultimately can't be allocated to Poweruses, e.g. the administration of domains. It is not possible to create one or more clones of the admin Poweruser. Nevertheless, it possible to grant access to the admin profile for a selected group of people. This can be achieved by defining a logon group for the admin Poweruser in the Inifile of the Infoserver.

For defining a logon group in the Infoserver.ini, you must edit the item LogonGroup=. Allocate the name of an Infoserver group as value to this item. If the value of the item LogonGroup is empty, then no user can log on to the Infoserver in the admin profile.

Example:

LogonGroup=DomainAdmins

Logon groups for Poweruser profiles

Logon groups for Poweruser profiles can be allocated directly in the appropriate profile, however only by the admin Poweruser. Please mind, that the admin can only allocate those groups, which were created by him personally.

Example:

Groupdefinition of Logon Groups

In the groupdefinition of logon groups, it is advisable to apply user-related values and functions.

Examples:

1. LogonGroup=DomainAdmins

Groupdefinition:

Name: DomainAdmins

Address: * Username: * Computername: *

Scriptfilter of the group:

program Scriptfilter; var Res: Boolean; begin Res:= MemberOFNTGroup(User,'Domain-Administrators'); SetResult(Res); end.

With this groupdefinition, all members of the AD group Domain-Administrators are authorized, to log on to the Infoserver in the profile of the admin Poweruser.

2. Logon group "SDAgents" for Poweruser profile "Service Desk Agents"

Groupdefinition:

Name: SDAgents

Address: * Username: * Computername: *

Scriptfilter:

program Scriptfilter; var Res: Boolean; begin Res:= MemberOFNTGroup(User,'Service Desk'); SetResult(Res); end.

With this groupdefinition, all members of the AD group Service Desk are authorized to log on to the Infosever in the Poweruser profile Service Desk Agents.

3. Logon group "vacation substitute" for Poweruser profile "craig.newton"

Name: vacation substitute

Address: * Username: sharon.mckey Computername: *

Scriptfilter: None

In this configuration, only the user sharon.mckey is authorized to log on to Infoserver in the Poweruser profile of craig.newton.

If a user is member of a logon group, then he can use the identical syntax for logging on in a chid Poweruser profile:

Username: myusername::poweruserprofile

Password: [Password of myusername]

12.1.4 Additional Notes

Please mind following notes to the Multiuser Mode:

Specific Settings in the Infoserver.ini

Singleuser=true(default)/false

With this option you can define, that any user who is not registered as Poweruser in the Infoserver, can login with his domain account and is able to send Infos exclusively to her/himself.

LogonGroup=GroupA,GroupB

Name of an Infoserver group, whose members can login in the profile of the Admin user. More to this function and the login-syntax can be found in chapters Poweruser Hierarchy and Logon Groups.

ParentLogonGroup=Group1,Group2

Name of an Infoserver group, whose members can login in the profiles of their Child- Powerusers. The members of these groups must be registered in the Infoserver as Powerusers in the role Subadmin. More to this function and the login-syntax can be found in chapters Poweruser Hierarchy and Logon Groups.

OverlappedGroupAllowed=false(default)/true

With this option you can define, if a Poweruser is able to send Infos to groups which were allocated by the Admin, and not by its parent Poweruser, and which are outside of the recipient-base as defined in the parent profile. The re-allocation by the admin overrides and replaces all previous group-allocations by the parent.

DomainPasswordCheckOnly=false(default)/true

With this option you can define, that the login procedure for Powerusers will check the submitted password only against the appropriate AD object (no local user accounts).

12.2 Dynamic Distribution

Especially in urgent situations, but also in the Problem and Incident Management, it can become necessary to inform a group of users, which can not be composed of a classic combination of users (e.g. usernames, AD groups), but has to be setup by using common (homogeneous) properties. A group of clients, which is setup by common properties, can also be called dynamic group, respectively common event based group.

The dynamic distribution of information is based on the ability of the Infoclients, to perform an examination of system-properties on the client PC at a certain point of time and to form the members of a dynamic group in dependency of these result.

There are two types of mechanisms:

- Dynamic InfoClientValues: Perform an examination on the client PC upon start of the Infoclient and communicate the results to the Infoserver upon registering. Based on these InfoClientValues it is then possible to create a group by using a scriptfilter.

- Dynamic Channels: Perform an examination on the client PC at the begin of (and during) the active-time of an Info and initiate the display of the message depending on the result of the examination. The function of the examination is placed via scriptfilter directly in the channel. Dynamic Channels can not be subscribed to by the Infoclients!

Fields of application:

- Disturbances and system failures in general - Incident Management - proactive information of users at upcoming or current disturbances - Problem Management - information of users on the progress of current fault repairs - Continuity Management This tool enables you to targetedly address a clearly defined user-environment within seconds, without searching tediously for affected users in existing groups. This metod saves you a lot of precious time!

Notice: Dynamic "groups" are no stationary Infoserver-usergroups, but virtual property- groups, which are composed at the moment of the client examination. For this reason, the number of group members is variable at any time.

Example:

Alle users which are currently using the programm "Outlook" on August 8th 2007 at 15:00 form a dynamic group at that certain moment.

Properties of a dynamic group can be:

> Alle user currently running MS Excel > All computers, on which MS Excel is installed > All users connected to a certain application server etc.

An exact listing of all possible properties can be found in chapter Types of Clientproperties.

Notice: With dynamic groups, you are mastering a very powerful tool which allows you to inform effectively only those users affected by a disturbance.

The foundation of the dynamic distribution of information is the principle of Infoclientvalues.

The queried properties are being deployed as dynamic Infoclientvalues through an Inifile- export.

Notice: The examination of the client-properties is performed by the Infoclient itself, not the Infoserver. Therefore, no increased network traffic is generated.

12.2.1 Dynamic InfoClientValues

12.2.1.1 Types of Clientproperties

The following types of client properties can be selected:

- Applications (installed) - Processes (running currently) - Connections - Files (existing) - Registry Keys - Properties of files - Inifiles - WMI Commands

Dynamic Infoclientvalues

The Scan of the client properties occurs with so called "dynamic Infoclientvalues", which are a special form of Inifile entries. There are 17 types of dynamic Infoclientvalues, to scan different types of properties. According to the results of the scan, there can be sent automatical or manual messages.

Overview of the dynamic Infoclientvalues

type/value function example syntax

diFileExists Scans, if a file exists. According to the result, a Path message can be shown. e.g.: c:\programs\cordaware\ mailtonews.exe diFileSize Scans the size of a file. E.g, if a database has Path achieved a critical size, an automatically message can be sent to an admin, or to the user. e.g.: j:\database\backup

diFileAge Scans the age of file. Message can be sent Path according to the age of a file. e.g.: c:\programs\cordaware\ mailtonews.exe

diFileVersion Scans the version number of a file. Messages can Path be sent according to version number of a file. e.g.: c:\programs\cordaware\ mailtonews.exe

diDirExists scans, if a certain path exists. E.g. all users of open Path office etc. e.g.: c:\programs\cordaware diDiskSize Scans the size of a device. E.g, if a device has Dive Letter achieved a critical size, an automatically message e.g.: c can be sent to an admin, or to the user.

diDiskFree Scans the free space of a device Drive Letter e.g.: c diRegExists Scans if a certain Regkey exists Regkey e.g.: HKEY_LOCAL_MACHINE\ SOFTWARE\Cordaware\I nfoband\Path

diRegKey Returns the value of a certain Regkey Regkey e.g.: HKEY_LOCAL_MACHINE\ SOFTWARE\Cordaware\I nfoband\Path diPrinterExists Scans, if a particular printer exists in the Printer Name configuration e.g.: Hp deskjet 930c diProcessRuns Scans, if a process is running currently. If it is Name of the process running a message can be sent to all this users e.g.: infoclient.exe diProcessRan Scans, if a process ran while a session. Name of the process e.g.: infoclient.exe diConnectedTo Scans active connections,e.g. client-server Computername or IP connections. Address Wildcharts can be used. e.g.: server1 or 192.168.69.*

diListenTo Scans open ports Port e.g: 805 diNetdirConnect Scans wether a device is mounted to a server. If name of the server edTo the connection is interrupted, the client can be Wildcharts can be used informed. e.g.: *server* diInifileValue Reads out values from Inifiles path of the Inifile: c:\Programs\Cordaware\ Infoband \Infoclient.ini;General=A ddress' diWmiValue Reads out values bases on WMI WMI command: e.g.: Select ProcessID from Win32_Process where Caption = "Infoserver.exe"

Further information about the possibilities you can find in the chapter Examples.

12.2.1.2 Allocate Clientproperties

Clientvalues are special form of client identification. Clientvalues are entered in the Inifile of the client.

For the dynamic distribution of information, special clientvalues, the so called dynamic Clientvalues are used. These values contain the particular properties of the client. Compared to the normal "Clientvalues", the dynamic Clientvalues aren't subscribed from the client by the user, but are allocated to the client pc from the server.

The first step on the way to the dynamic distribution of information is the configuration of dynamic Clientvalues. For each client property will be defined a dynamic Clientvalue into the Inifile of the client.

Important notice: If you use the "ad hoc - scan" of the Dynamic Channels, you don't need to define a dynamic clientvalue in the Inifile Configuration. You can define them directly in the configuration of Dynamic Channels. For more information about this, read the chapter Dynamic Channels

Definition of dynamic Clientvalues by using the Inifile configuration

To add a dynamic Clientvalue to the Inifile of a client, proceed as follows:

1. Open the Inifile export under New info > Details > Inifile

2. Scroll down until the configuration of the dynamic Clientvalues

3. Now, enter a name for your Clientvalue, choose a type, and add a value, which specifies the type. You can find an overview over all different types in the chapter types of client properties

Example:

4. Click on Insert. Your dynamic Clientvalues now are written into the Infoeditor.

5. Click on Save. The values are now sent to clients.

In the connections overview, you can see an overview over the dynamic Clientvalues of each client.

Dynamic Clientvalues can be used in user groups, or with Dynamic Channels.

12.2.1.3 Application in Infoservergroups

By using a dynamic Clientvalue in a Usergroup, "common event based groups" can be designed.

Example:

All client PCs that have e.g. Photoshop installed, can be merged into the group "Photoshop users".

Now if a breakdown, or a disruption appears, you can exactly inform the concerning group, about state and duration of the recovery.

Important notice: Compared to Dynamic Channels, "common event based groups" are static. Only the client properties, that are existing at the moment of the connection between Infoserver and Infoclient, can be used.

To scan temporary properties, like e.g. running processes, it is recommended to use Dynamic Channels.

Example:

The path:, c:\programs\cordaware\infoband", or the file "c:\programs\cordaware\infoband\infoclient.exe", are existing at the moment of the connection. The process "winword.exe" is started and stopped temporarily during a session.

Designing event based groups

Notice: If you want to design a "common event based group", it is necessary, that dynamic InfoClientValues were setup before.(see chapter definition of Clientvalues)

To design an event based group, proceed as follows:

1. Select Groups > New groups in the menu.

2. Enter a name and the description of the group.

3. At the overview page, click on the link add.

4. Add your dynamic Clientvalues to the Scriptfilter

Examples:

Example 1

Groups with one common property.

You want to configure a group, which has one common property. For example, you have defined a dynamic Clientvalue for all clients with an office Installation. The name of the Clientvalue is "office_installed". The type is "diDirExists". The result is true or false (installed, or not installed)

Configuration of the Scriptfilter

1. Remove the comment from the "res" line (see image)

// Res := InfoClientValue('Name') = 'YourValue';

2. Enter the type and the name of your Clientvalue e.g.:

// Res := InfoClientValue('office_installed') = '1';

Example 2

Groups with several common properties

It is also possible to define groups with several common properties.

Use the operators and and or.

Configuration of the Scriptfilter:

1. Define your variables

For example: res1, res2, res3: Boolean;

2. Enter the types and values of your dynamic Clientvalues

For example:

res1 := InfoClientValue('direxists') = '1'; res2 := Infoclientvalue ('regexists') = '1'; res3 := Infoclientvalue ('filexists') = '1';

3. Set the Result (SetResult)

Example: If you want to design a group of all office users, which additionally access on database1, than set:

"SetResult (res1 and res3)".

12.2.2 Dynamic Channels

12.2.2.1 Configure Dynamic Channels

Introduction

Dynamic channels are the most sophisticated tools for dynamic realtime-messaging and an effective instrument of the continuity management.

Common event based groups are chracterized by properties, which are given at the time of the client-connection to the Infoserver.

Dynamic Channels go one step further and react to dynamic changes on the client- environment. Every type of dynamic Clientvalue can be used in a dynamic Channel. This way, flexible and immediate information channels are at your disposition. You can react instantly with highly targeted messages to current events.

Creating dynamic Channels

In general, there are two methods of creating a dynamic Channel.

1. Query existing Clientvalues

If you already have created dynamic Infoclientvalues (e.g. for dynamic groups), then you can use these in a dynamic Channel too. Simply use the name of the Infoclientvalue and the expected value in the scriptfilter.

Res := InfoClientValue('Name') = 'YourValue';