Ipocc Watchdog En

Deploying IP Office Contact Center Watchdog

Release 9.0.2Issue 1.0

February 2014

© 2013 Avaya Inc. All Rights Reserved.

Notice

While reasonable efforts have been made to ensurethat the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organizationof such changes.

Documentation disclaimer

"Documentation" means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya generally makes available to users of its products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions,or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants, and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User.

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work allthe time and has no control over the availability of the linked pages.

Warranty

Avaya provides a limited warranty on itshardware and Software ("Product(s)" ). Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language, as well as information regarding supportfor this Product while under warranty is available to Avaya customers and other parties through the Avaya Support website:

http://support.avaya.com

Please note that if you acquired the Product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to you by said Avaya Channel Partner and not by Avaya. "Software" means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products or pre-installed on hardware products, and any upgrades, updates, bug fixes, or modified versions.

Licenses

THE SOFTWARE LICENSE TERMS AVAILABLEON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING ORSELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END USER", AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE "AVAYA".

Avaya grants you a license within the scope of the license types described below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to you. “Designated Processor” means a single stand-alone computing device. “Server” means a Designated Processor that hosts a software application to be accessed by multiple users.

License type(s)

Designated System(s) License (DS). End User may install and use each copy of the Software only on a number of Designated Processors up to the number indicated in the order. Avaya may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose.

Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A “Unit” means the unit on which Avaya, at its sole discretion, bases the

pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server.

Copyright

Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or hardware provided by Avaya. All content on this site, the documentation and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law.

Virtualization

Each vAppliance will have its own ordering code.Note that each instance of a vAppliance must be separately ordered.If the end user customer or Business Partner would like to install2 of the same type of vAppliances, then 2 vAppliances of that typemust be ordered.

Each Product has its own ordering code. Note that each instance of a Product must be separately licensed and ordered. "Instance" means one unique copy of the Software. For example, if the end user customer or Business Partner would like to install 2 instances of the same type of Products, then 2 Products of that type must be ordered.

hird-party components

“Third Party Components” mean certain software programs or portions thereof included in the Software that may contain software (including open source software) distributed under third party agreements (“Third Party Components”), which contain terms regarding the rights to use certain portions of the Software (“Third Party Terms”). Information regarding distributed Linux OS source code (for those Products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the Documentation or on Avaya’s website at: http://support.avaya.com/Copyright. You agree to the Third Party Terms for any such Third Party Components.

Note to Service Provider

The Product may use Third Party Components that have Third Party Terms that do not allow hosting and may need to be independently licensed for such purpose.

Preventing Toll Fraud

“Toll Fraud” is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services.

Avaya Toll Fraud intervention

If you suspect that you are being victimized by Toll Fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: http://support.avaya.com.Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: [email protected].

The trademarks, logos and service marks (“Marks”) displayed in this site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation and Product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party.

Avaya is a registered trademark of Avaya Inc.

All non-Avaya trademarks are the property of their respective owners, and “Linux” is a registered trademark of Linus Torvalds in the U.S. and other countries.

Downloading documents

For the most current versions of documentation, see the Avaya Support website:


Contact Avaya Support

See the Avaya Support website: http://support.avaya.com for product notices and articles, or to report a problem with your Avaya product.

For a list of support telephone numbers and contact addresses, go to the Avaya Support website: http://support.avaya.com, scroll to the bottom of the page, and select Contact Avaya Support.


http://support.avaya.com/licenseinfo

http://support.avaya.com/Copyright

http://support.avaya.com/Copyright






Deploying IP Office Contact Center Watchdog 1

ContentsAbout this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Application and commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5What is Watchdog? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5WDConfig tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Memory dump (Core dump) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Basic conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Environment variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Installed files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Installation as a service (no setup) . . . . . . . . . . . . . . . . . . . . . . . . . 10Uninstalling (no setup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Working with the Watchdog application . . . . . . . . . . . . . . . . . . . . . . . . 11Starting Watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Working on the configuration file. . . . . . . . . . . . . . . . . . . . . . . . . . 11

WDConfig application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Application and structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Menus and commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configuring settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Displaying settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Displaying scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17What is a scenario? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Run level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Changing the order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Changing the host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25


Creating user-defined symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Configuring macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Displaying macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27What is a macro? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Precondition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Inserting a symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Example of an import file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Explanation of keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Keywords (tags) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Distributing the configuration file . . . . . . . . . . . . . . . . . . . . . . . . . 39

Tips and tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Pinging the Watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40OmniORB naming service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Options for Watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Multiple core dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

About this manual


About this manual

This manual contains information about installing and configuring a system with Watchdog.

Target audience

This manual is intended for people installing and configuring a system with Watchdog. It makes no difference whether you are using this document in printed or online form.

Use this manual, as you see fit, for reference purposes or to learn how to install and configure a system with Watchdog.

4 Deploying IP Office Contact Center Watchdog

Application and commissioning



What is Watchdog?

Tasks

Programs can be started, stopped and monitored with the Watchdog application. The Watchdog can be configured. It is available as operating system service.

The three actions "starting", "stopping" and "monitoring" can be executed via one or several PCs. The term distribution is used to describe this. Dependencies between programs and the sequence of programs as well as network or PC failures can be taken into account.

The Watchdog application performs the following tasks.

• Starting programs in a defined sequence

• Monitoring the existences of processes and hosts

• Establishing the defined status and restarting programs when a process is lost

• Switching to an alternative scenario or at least restarting the system to the extent possible when a host is lost

• For distributed systems, recording the runtime of a ping to perform a simple performance analysis

• Executing macros

Communication

The Watchdog application communicates using TCP/IP.

Logging

Outputs from the Watchdog application are logged in the TTrace application. Additional outputs during installation or removing are provided via the standard terminal output.

WDConfig tool

You have to set all necessary parameters with a configuration file. To facilitate this task and avoid errors, you create and modify the configuration file with the WDConfig tool.


Configuration file

The configuration file contains all of the settings for the Watchdog application. This file is provided in XML format.

Note

Only use the WDConfig application to edit the configuration file. Do not edit the file manually.

Memory dump (Core dump)

When a process crashes, a core dump is written. To view the core dump settings, enter drwtsn32.exe under Start - Run. In the settings, you will also find the core dump folder. The core dump is usually designated as wd001.dmp.

With the TTraceConsole application, you can send a command to the Watchdog application, to protect existing core dumps from being overwritten in the event of certain errors.

For further information refer to: “Multiple core dumps” on page 41



Basic conditions

Limitation

The Watchdog application does not monitor the outputs of servers or programs. The Watchdog application does not communicate with the processes. It only checks whether the started components exist as a process in the operating system.

The TTrace application can filter outputs and communicate with the Watchdog application.

Prerequisites

The following conditions must be met to ensure error-free operation of the Watchdog.

Components not monitored

Components that depend on other non-monitored sub-components can be monitored. These sub-components must run without errors to ensure that the component works correctly. Examples for such dependencies are:

• Correctly installed and configured CORBA

• Correctly installed and running database system

• Correctly installed and running replication system

These sub-components are not supervised by the Watchdog application. Error-free operation of these sub-components must be ensured before starting the Watchdog application.


Example

The database is running when Watchdog application starts. However, the database is in a state which does not yet permit database queries. The Watchdog application now tries to stop and restart components. This process can repeat itself again and again. The system is not working.

Same configuration

The Watchdog application must be installed and correctly configured on every computer. The configuration file of the Watchdog application must be identical for all computers. You can ensure this is the case by using the Distribute function of the WDConfig application.

A certain distribution of programs on one or several computers is called a scenario. There is one scenario for one computer. For a distribution on several computers several scenarios have to be configured, e.g., if one computer or network connection should fail.

There are already three scenarios in the case of two computers. Either both computers are working or else one or the other fails. Depending on the number of computers involved, the number of scenarios to be described rises accordingly. If a scenario is missing, the DEFAULT scenario attempts to start.

Rights

Watchdog must have all necessary rights to affect all supervised processes.

Network environment

TheTCP/IP network environment must be installed correctly.

Environment variable

If environment variables are required to operate the processes under the control of the Watchdog application, the following must be taken into account.

The Watchdog application is started as an administrator user [Account]. This means that only the system environment variables are available to the Watchdog application and all processes started by the Watchdog application.

The user-specific variables are not available.



Installation

The Watchdog application is used to restart the software after a full or partial system failure as soon as the necessary components are available again.

Installation

As a rule, you use the Watchdog application with an Avaya product. Proceed as follows to install the Watchdog application.

1. You need a data carrier with the installation files for Watchdog.

2. Double-click the Watchdog.msi file.

3. Click Install. The Welcome dialog opens.

4. Click Next. The End User License dialog opens.

5. Select I accept the terms in the license agreement.

6. Click Next. The Choose Setup Type dialog opens.

7. Click Complete. The General Settings dialog opens.

8. Enter the host name of the TTrace server.

9. Click Next. The Ready to install dialog opens.

10. Click Install. The files are installed.

11. Click Finish to complete the installation.

Installed files

During the installation, the Watchdog and WDConfig applications are installed in the respective folder.

The default folder is Programs\Avaya\IP Office Contact Center\Watchdog.

File Explanation

watchdog.exe Watchdog application.

wdconfig.exe WDConfig application for configuration and settings.

WatchdogXML-C4T.ZIP Examples for Com4Tel

WatchdogXML.ZIP Examples for (One Server Standard Solutions, Two Server Standard Solu-tions)


Installation as a service (no setup)

Proceed as follows to install Watchdog as a service.

1. Open a command prompt (DOS box).

2. Go to the Watchdog application folder, generally Programs\Avaya\IP Office Contact Center\Watchdog.

3. Enter watchdog -install. Press RETURN. You can enter additional options for the Watchdog application in quotation marks. Example: watchdog -install “-tt my_tt_srv”

Uninstalling (no setup)

Proceed as follows to uninstall the Watchdog application.


2. Go to the Watchdog application folder, generally Programs\Avaya\IP Office Contact Center\Watchdog.

3. Enter watchdog -deinstall. Press RETURN. The service is closed and the Watchdog application is uninstalled.



Working with the Watchdog application

Starting Watchdog

The Watchdog application can be started without a configuration file. In this case, the Watchdog application runs in a standby mode and waits until a configuration file is distributed.

Working on the configuration file

You edit the configuration file with the WDConfig application. Always work with an inactive configuration file.

Note

Make sure you do not edit the copy of the configuration file that is currently being used by the Watchdog application. If you distribute this configuration file, then the Watchdog application function is no longer guaranteed.


WDConfig application

Application and structure

Application

The WDConfig is used to configure settings and scenarios for the Watchdog application.

Icon

You will see the following icon in Windows Explorer and in the title bar of the WDConfig application.

Menus and commands

The figure below shows the menu bar.

Commands of the File menu

The following table shows the commands and functions of the File menu.

Command Explanation

New Opens a new configuration file.

Open Opens an existing configuration file. You must select a configuration file.

Save Saves the current configuration file.

Save as Saves the current configuration file as a specified name.

import Imports parts of a configuration file.

Distribute Distributes the current configuration file.

Exit Exits the application.



Commands of the Edit menu

The commands of the Edit menu have no function.

Commands of the View menu

The following table shows the commands and functions of the View menu.

Commands of the Help menu

The following table shows the command and function of the Help menu.

Tool bar

The following schematic illustration shows the tool bar.

The following table shows the tool bar icons and their corresponding functions.

Command Explanation

Tool bar Shows or hides the tool bar.

Status bar Shows or hides the status bar.

Command Explanation

About WDConfig Shows the version of the WDConfig application and the copyright.

Icon Explanation Corresponds to menu and command

Opens a new configuration file. File - New

Opens an existing configuration file. You must select a configuration file.

File - Open

Saves the current configuration file. File - Save

Saves the current configuration file as a specified name. File - Save as


Shows the general settings for the Watchdog application. -

Opens the scenarios. You can edit, add, rename, or delete scenarios.

-

Opens the macro definitions. You can edit, add, rename, or delete a macro.

-

Icon Explanation Corresponds to menu and command



Configuring settings

Displaying settings

1. To configure the settings, click .

Settings

You can configure the following settings.

Setting Default Explanation

Port 10001 Specifies the IP port of the operating system used by a Watchdog to communicate with other Watchdogs in a distribution. You must specify the port number in decimal format. The WDConfig application also uses this port.

AliveInterval 5 sec. AliveInterval specifies the interval in seconds that Watchdogs use to check if they are still connected to the other Watchdogs. So-called alive-messages are exchanged at the end of each AliveInterval. The reason for this procedure is that it usually takes TCP/IP timeouts 5 minutes to determine that a connection has been interrupted. If, for example, the network connection between two computers is interrupted, it would take too long to react to this.

AliveTimeout 20 sec. AliveTimeout is closely connected to AliveInterval. The AliveTimeout specifies the interval after which the connection between two Watchdog applications is considered interrupted. AliveTimeout must be a multiple of AliveInterval. The factor 4 is recommended.

BootTimeout 60 sec. BootTimeout specifies the interval in seconds that the Watchdog applications in a distribution have to get in contact with each other. If this time is exceeded, the system switches to another scenario (another distribution of processes) for the missing Watchdogs. If a Watchdog application is added later, it is integrated in the processes and added to the system. Select a suitable value if the computers are located far away from each other and for the system startup phase.

WatchInterval 15 sec. WatchInterval specifies the interval in seconds that the Watchdog application uses to check if all programs started by application are still running.


DefaultDelay 15 sec. DefaultDelay specifies the interval in seconds that has to elapse after a successful program start, before the next program may be started. This is necessary since some interdependent programs need time to initialize before they can provide dependent programs with the necessary services. This value can depend considerably on computer performance and is to be selected accordingly.

SwitchDelay 30 sec. SwitchDelay gives the time interval in seconds that should elapse before the alternative scenario becomes active.

Server localhost All Watchdogs communicating with each other must be listed under Server. One computer name per consecutive line must be entered. Please note that if several network adapters are installed, the computer names associated with the faster network connections are used. For your own PC you always have to use the name provided by the host name program. Another computer name restriction is that short computer names without appended domain information must be used, i.e., ccserver instead of ccserver.somedomain.de.

The computer name is case-sensitive.

With a stand-alone system, you can use localhost.

This setting is updated automatically when a scenario is maintained.

Setting Default Explanation



Configuring scenarios

Displaying scenarios

1. Click to display the scenarios.

What is a scenario?

A scenario describes a distributed system. Each scenario must have an unambiguous name. The default scenario describes the distribution of components or processes including all computers entered under Server.

Multiple scenarios are possible for each configuration, however, each scenario must have its own host combination (no duplicate combinations). Each scenario must have a name. Each scenario consists of one or more run levels with consecutive ascending numbers. Each run level has one or more start commands (Run). The processes of a run level can be declared independent of each other (Dependencies=0). In this case, only the processes of the higher-level run level are terminated and restarted in the event of a crash, whereas with dependent processes (Dependencies=1 [default]), this run level is terminated, as well. This behavior is deactivated with the use of a special termination.

The scenario called DEFAULT has a special function. Only this scenario is used with a single host system.

With a multi-host system in which only this scenario is specified, this scenario is started even in the event of an incomplete boot. An incomplete boot means that not all configured hosts answer during the boot time. If additional scenarios are defined, but none of these has the host combination that is currently active, the boot operation continues.

You have the option of specifying that under normal circumstances during a process crash, the active scenario is terminated down to the run level in which the failed process is started. For Dependencies=1 (default) this includes the individual run level, and for Dependencies=0, this excludes the individual run level.

If special termination dependencies are specified for a scenario, only these dependencies apply. Processes are first terminated by means of a so-called "soft kill." If the application does not respond to the CloseRequest within the Stop timeout (default setting 30 seconds), then the application is terminated as usual with a hard kill, i.e., without a chance to respond.

When a connection to another Watchdog is lost, the system checks to determine whether it can switch to an alternative scenario. The alternative scenario must contain all hosts that are now still connected to the Watchdog. If an alternative scenario cannot be found, the system is terminated down to the lowest run level at which the failed host is running and waiting for the computer to be reactivated. This situation is comparable to starting the DEFAULT scenario after an incomplete boot.


Scenario

A register card is displayed for each scenario. The register card tab shows the name of the scenario. A scroll bar is added if necessary.

Buttons

You can add, copy, rename, or delete a scenario.

Setting

You can configure the following setting for a scenario.

Button Explanation

Adds a new scenario.

Copies the selected scenario.

You can rename the selected scenario.

Deletes the selected scenario. You are prompted to confirm your selection. You cannot delete the DEFAULT scenario.

You can replace the host names of the runs with a new host name.

Setting Explanation

Name Specifies the name of the scenario. The register card shows the name.

New

Copy

Rename

Delete

Ren.Host



Example

The following illustration shows an example of a scenario.


Run level

A run level specifies the value of one or more programs to be started.

The lowest allowed run level of the Watchdog application is 1. The run level 0 is not allowed.

A run level of X means that programs with this run level are started by the Watchdog application before programs with run level X+1 are started. This means that programs on run level X+1 are dependent on run level X. If this is not the case, then these programs can be assigned the same run level.

Dependency on a lower run level also means that once a program of the lower run level is stopped, the Watchdog application also stops all programs of the higher run level.

Note that all programs of the same run level must be also stopped if programs on the same run level (for example, kernel, vu, and vectors) communicate via shared memory.

Several computers are usually listed in one scenario. This is known as a distribution. One special distribution feature is a distributed run level. This means that several Watchdog applications start programs on the same run level. The starting order is kept even if several Watchdog applications participate.

A run level is marked in the WDConfig application with a red border.

Buttons

You can add, edit, or remove a run level.

Button Explanation

Adds a new run level.

Opens the settings of the selected run level.

Removes the selected run level. You are prompted to confirm your selection.

Add

Edit

Remove



Settings

You can configure the following settings for a run level.

Setting Explanation

As level Indicates the level. The level is automatically preset by the WDConfig application. To change the level, click Up or Down.

Name Indicates the name of the run level. Use of the optional name facilitates the configuration of terminations.

Containing runs depends on each other

Indicates that the runs within the run level are dependent on each other. This is the default setting.

If the runs within the run level are not dependent on each other, you can clear this option. This means that if one of the processes on a run level is ended, the other process continues, but the subsequent run levels are ended.

OptionalIndicates that the run level can be skipped if the application does not start.

Termination Indicates which run levels are terminated. You can select one or more run levels. Multiple run levels are separated by commas.


Run

A run stands for a process or application that must be started.

A selected run is marked in the WDConfig application with a gray border.

Buttons

You can add, edit, or remove a run.

Settings

You can configure the following settings for a run.

Button Explanation

Adds a new run.

Opens the settings of the selected run.

Removes the selected run. You are prompted to confirm your selection.

Setting Explanation

Symbolic name of run Indicates the symbolic name of the run.

Run installed service Indicates that the application is running as a service (Start service).

You can edit only the Start service, Start on host, and Delay until next start settings.

Indicates that the application is running as a common executable program (Start executable).

Start executable

or

Start service

Indicates the executable program.

Indicates the service. Note that you must enter the service name. You are not allowed to use the display name.

Located at directory Indicates the directory containing the program.

Program arguments Indicates the startup parameters for the program. You can use variables.

Add

Edit

Remove



Working directory Indicates a working directory.

Start on host Indicates the host name.

Delay until next start Indicates the delay in seconds until the start of the next process.

If you do not specify this setting, the DefaultDelay setting is used.

Stop timeout Indicates the time in seconds after which as program is ended. A default setting of 30 seconds is used.

Process priority Shows the priority of the process. You can choose from the following priorities: Low, BelowNormal, Normal, AboveNormal, High and Realtime. You can see the priority of a process in the Task Manager.

Window size Shows the format of the window. You can choose from the following settings: None (no window), Norm (normal window size), Min (minimized), Max (maximized).

Text color Specifies the text color. You can choose from Black, White, Red, Green, Blue, Magenta, BlueGreen, and Yellow.

Background color Specifies the background color. You can choose from Black, White, Red, Green, Blue, Magenta, BlueGreen, and Yellow.

No TTrace Display The process appears in the list of the TTrace Display application.

The process does not appear in the list of the TTrace Display application. This setting is useful for auxiliary tools, for example.

Setting Explanation


Changing the order

Use the following buttons to change the order within the run level or runs.

Button Explanation

Raises the selected run or run level. The run or run level is moved up in the list.

Lowers the selected run or run level. The run or run level is moved down in the list.

Up

Down



Changing the host name

You can change the host name in all settings. You can select the following options:

1. Click Ren.Host. The Rename Hosts in Runs dialog opens.

2. In the With field, enter the new host name. Select options.

3. Click OK. All host names are replaced by the new host name.

Creating user-defined symbols

User-defined symbols are used in start parameters for runs. User-defined symbols are only valid for one scenario. You must create the appropriate user-defined symbols for each scenario.

Settings

Enter the following settings for a user-defined symbol.

Example

For example, you can create the switch -ush hostname-x with $ORB$, thus making it easier to change.

Option Explanation

Program arguments inclusive When this option is selected, the host names in the parameters (program arguments) are replaced, as well.

User symbols inclusive When this option is selected, the host names are replaced in the user-defined symbols, as well.

Setting Explanation

Name Specifies the name of the user-defined symbol. A user-defined symbol is identified with "$Name$".

Value Specifies the value of the user-defined symbol.


Creating a user-defined symbol

Proceed as follows to create a user-defined symbol.

1. Click Symbols. The User Defined Symbols dialog opens.

2. To create a new user-defined symbol, click Add. To edit a selected symbol, click Edit. To remove a selected symbol, click Remove.

3. Enter the name and the value.

4. Click OK. The user-defined symbol is created.

5. Click Close. The user-defined symbol is displayed in the scenario register.



Configuring macros

Displaying macros

1. Click to display the macros.

What is a macro?

With a macro, you can perform the following steps. You can use a macro, for example, to end various processes in a specific order to achieve a controlled PC shut-down.

You can test a macro in collaboration with the TTrace application.

Macro

A register card is displayed for each macro. The register card tab shows the name of the macro. A scroll bar is added if necessary.

Buttons

You can add, copy, rename, or delete a macro.

Button Explanation

Adds a new macro.

Copies the selected macro.

You can rename the selected macro.

Deletes the selected macro. You are prompted to confirm your selection.

New

Copy

Rename

Delete


Settings

You can configure the following settings for a macro.

Precondition

For a macro, you can configure a precondition that must be fulfilled in order for the macro to be executed.

The Run command is used to determine whether the Watchdog application performing the check is executing or monitoring the specified run.

Settings

You can use the following settings for a precondition. You can select an option.

Setting Explanation

Name Specifies the name of the macro. The register card shows the name.

Temporarily disabled Indicates that the macro can be used. This is the default setting.

Indicates that the macro cannot be used.

Version You cannot change the setting 100.

Comment You can enter a comment.

Precondition Specifies a precondition. This precondition must be fulfilled in order for the macro to run.

Steps Shows the steps that are performed with the macro. You can add, edit, copy, and delete steps.

Setting Explanation

Runs(%PARAM%) Specifies a run. The name of the run is indicated with user-specific symbols.

Runs(<Name>) Specifies a run. You must enter a name.

Runs(<Level>, <Run>) Specifies a run. You must enter Level and Run.



Steps

You can add, copy, edit, and delete steps in the macro. You can specify the order of step in the macro using Up and Down.

PauseWatching

The PauseWatching step pauses the functions of the Watchdog application for a defined period of time. The functions resume after this time period. Use the ContinueWatching step to activate the functions earlier.

ContinueWatching

The ContinueWatching step deactivates a pause of the PauseWatching step. No settings are required.

SetRegistryString

The SetRegistryString step writes a specified string to a specific key in the Windows registry. This value can contain a number of placeholders.

Setting Explanation

Duration Specifies the duration of the time period.

Setting Explanation

Key Displays the registry key. You can select a registry key.

Subkey

Displays the subkey. You can select a symbol with .

Valuename

Displays the key name. You can select a symbol with .

Value

Displays the value. You can select a symbol with .


StoreRegistryString

The StoreRegistryString copies a specified string from the Windows registry to the internal storage of the macro. Each macro has its own storage. If a macro is called by another macro, this macro can also access the storage of the calling macro. You can use this function to move information from one macro to another macro. You can enter the following settings for the StoreRegistryString step.

Execute

The Execute step executes a specified command on the local PC. You can enter the following settings for the Execute step.

Setting Explanation

Key Displays the registry key. You can select a registry key.

Subkey

Displays the subkey. You can select a symbol with .

Valuename

Displays the key name. You can select a symbol with .

Value

Displays the value. You can select a symbol with .

Setting Explanation

CmdLine Displays a command that is being executed on the local PC.

You can select a symbol with .



CallMacro

The CallMacro step calls another macro. You can use this step to create subroutines. Note that the local storage of the macro is also used by the subroutine (macro).

To test the macro, you can use the TTrace application to send a command with the name of the macro to the Watchdog application. The placeholder %PARAM% displays the parameters.

You can enter the following settings for the CallMacro step.

AddToStorage

The AddToStorage step saves the value in the storage. This storage is also used by subroutines.

You can enter the following settings for the CallMacro step.

Setting Explanation

Name of the macro

Specifies the name of the macro. You can select a symbol with .

Parameter

Specifies the parameters of the macro. You can select a symbol with . Multiple parameters are separated by a comma (",").

Setting Explanation

Storage Indicates the storage location.

Value

Displays a value. You can select a symbol with .


Inserting a symbol

You can insert symbols in the steps.

A run can be named explicitly with a two-digit index or symbolic name.

The following settings are possible.

Setting Explanation

%PARAM% Displays the value from the parameter field of the command from TTrace.

%DIR(<Level>, <Run>)% Displays the contents of the Located at directory field from the configuration dialog of a run. You must specify Level and Run.

%DIR(<Name>)% Displays the contents of the Located at directory field from the configuration dialog of a run. You must specify the name.

%PID(<Level>, <Run>)% Displays the current process ID of the operating system for the run. You must specify Level and Run.

%PID(<Name>)% Displays the current process ID of the operating system for the run. You must specify the name.

%STORAGE(<Name>)% Specifies the contents of the storage. You must specify the name.



import

You can use the Import function to insert new components in an existing configuration. For components, an import file is created and integrated in an existing configuration with the configuration tool.

Example of an import file

The following example shows an import file.

<?xml version='1.0' ?><WDImport> <Scenario> <Runlevel No="1" Dependencies="0" > <Insert> <Before>"<Name of run level>"</Before> <Into>"<Name of run level>"</Into> <After>"<Name of run level>"</After> </Insert><Run No="1" > <Insert> <After>"Name of run"</After> <Before>"Name of run>"</Before> </Insert><Exe>"xyz1.exe"</Exe> <Dir>"e:\Business Call Center\cc\bin"</Dir> <Host>"localhost"</Host> <Delay>5</Delay> </Run> <Run No="2" > <Exe>"xyz2.exe"</Exe> <Dir>"e:\Business Call Center\cc\bin"</Dir> <Args>""</Args> <Host>"localhost"</Host> <Delay>0</Delay> </Run> </Runlevel> </Scenario><Macro Name="AddTest1" > <Execute> <CmdLine>"dir"</CmdLine> </Execute> </Macro></WDImport>


Explanation of keywords

You must use the following keywords in the import file.

Index Key Multi Explanation

- WDImport 1 Comprises the import specification.

1 Scenario N Describes the integration steps in existing scenarios.

1.1 Run level N Describes which run levels should be inserted in existing scenarios. The numbering always starts with 1 within the import file.

1.1.1 Insert 1 Describes how this run level is inserted in the scenarios. One of three options is specified. If an Insert is not specified, the run level is appended to the end of the existing configuration.

1.1.1.1 Before 1 Names the run level before which this level is inserted.

1.1.1.2 Into 1 Names the run level into which this level is inserted. For Into only, you must specify how the individual runs are positioned with respect to existing runs.

1.1.1.3 After 1 Names the run level after which this level is inserted.

1.2.1 Run N Description of a run. The content corresponds to the configuration file.

1.2.1.1 Insert 1 Describes how this run level is inserted in the scenarios. One of three options is specified.

1.2.1.1.1 Before 1 Names the run before which this run is inserted.

1.2.1.1.1 After 1 Names the run after which this run is inserted.

2 Macro N Defines macros to be inserted. The structure corresponds to the configuration file.



Configuration file

The configuration file contains the settings that you have configured in the WDConfig application. The configuration file is automatically created in XML format.

Structure

XML is block-oriented, i.e., each configuration element is surrounded by an opening keyword <tag> and a closing </tag>. Abbreviations are also possible. An extreme example is <Group key1=“value1“ key2=”value2” />. Blocks can be nested in any order.

If a quotation mark is necessary within a value, it must be written as \".

Keywords (tags)

The following tags are used in the configuration file.

Tags Reference/Explanation

<WDConfig> Start of settings

<Port> See “Settings” on page 15.

<AliveInterval> See “Settings” on page 15.

<AliveTimeout> See “Settings” on page 15.

<BootTimeout> See “Settings” on page 15.

<WatchInterval> See “Settings” on page 15.

<DefaultDelay> See “Settings” on page 15.

<SwitchDelay> See “Settings” on page 15.

<Optional> See “Settings” on page 15

<Server> See “Settings” on page 15.

<Scenario Name="DEFAULT" > See “What is a scenario?” on page 17.

<Symbol Name="$n$" Value="v" /> See “Creating user-defined symbols” on page 25.

<Runlevel No="1" > See “Run level” on page 20.

<Runlevel No="2" Dependencies="0" See “Run level” on page 20.


<Name> See “Run level” on page 20.

<Run No="1" > See “Run” on page 22.

<Name> See “Run” on page 22.

<Exe> See “Run” on page 22.

<Dir> See “Run” on page 22.

<Args> See “Run” on page 22.

<WDir> See “Run” on page 22.

<Host> See “Run” on page 22.

<StopTimeout> See “Run” on page 22.

<ProcessPrio> See “Run” on page 22.

<Size> See “Run” on page 22.

<TextColor> See “Run” on page 22.

<BackColor> See “Run” on page 22.

<NoDisplay> See “Run” on page 22.

<OnTermination> See “Run level” on page 20.

<Macro Name="name"> See “Macro” on page 27.

<Disabled>1</Disabled> See “Macro” on page 27.

<Comment> See “Macro” on page 27.

<PauseWatching> See “Steps” on page 29.

<Minutes> See “Steps” on page 29.

<ContinueWatching> See “Steps” on page 29.

<SetRegistryString> See “Steps” on page 29.

<RegKey> See “Steps” on page 29.

<RegSubKey> See “Steps” on page 29.

<RegValueName> See “Steps” on page 29.

<RegDate> See “Steps” on page 29.




Example

The following example shows a configuration file. This example is used for a Com4Tel C System Version 2.0.

<?xml version="1.0" ?> - <WDConfig>- <Scenario Name="STANDARD">- <Runlevel No="1" Dependencies="0"> <Name>"omniORB Naming Service"</Name> - <Run No="1"> <Name>"omniORB Naming Service"</Name> <Exe>"omniNames.exe"</Exe> <Dir>"C:\Program Files (x86)\Avaya\IP Office Contact Center\OmniORB"</Dir> <Args>"-logdir "C:\Documents and Settings\\All Users\Application Data\omniORB\.""</Args> <WDir>"C:\PProgram Files (x86)\Avaya\IP Office Contact Center\OmniORB"</WDir> <Host>"localhost"</Host> <Size>"None"</Size> </Run> </Runlevel>- <Runlevel No="2"> <Name>"ADB-Server"</Name> - <Run No="1"> <Name>"adb_srv"</Name> <Exe>"adb_srv.bat"</Exe> <Dir>"C:\Program Files (x86)\Avaya\IP Office Contact Center\Address Book Server"</Dir> <WDir>"C:\Program Files (x86)\Avaya\IP Office Contact Center\Address Book Server"</WDir> <Host>"localhost"</Host> </Run>

<Execute> See “Steps” on page 29.

<CmdLine> See “Steps” on page 29.

<CallMacro> See “Steps” on page 29.

<Name> See “Steps” on page 29.

<Parameter> See “Steps” on page 29.

<AddToStorage> See “Steps” on page 29.

<Name> See “Steps” on page 29.

<Value> See “Steps” on page 29.



</Runlevel>- <Runlevel No="3"> <Name>"Database"</Name> - <Run No="1"> <Name>"Database Server"</Name> <Exe>"db_srv.exe"</Exe> <Dir>"C:\Program Files (x86)\Avaya\IP Office Contact Center\Database"</Dir> <WDir>"C:\Program Files (x86)\Avaya\IP Office Contact Center\Database"</WDir> <Host>"localhost"</Host> <Size>"None"</Size> </Run>- <Run No="2"> <Name>"LockNotifyAccess Server"</Name> <Exe>"lna_srv.exe"</Exe> <Dir>"C:\Program Files (x86)\Avaya\IP Office Contact Center\Database"</Dir> <WDir>"C:\Program Files (x86)\Avaya\IP Office Contact Center\Database"</WDir> <Host>"localhost"</Host> <Size>"None"</Size> </Run> </Runlevel>- <Runlevel No="4" Dependencies="0"> <Name>"conneCTIon"</Name> - <Run No="1"> <Name>"CTI-Server"</Name> <Exe>"eai40.exe"</Exe> <Dir>"C:\Programs\Avaya\CTI"</Dir> <Args>"-e 5005 -p ncacn_ip_tcp"</Args> <WDir>"C:\Programs\Avaya\CTI"</WDir> <Host>"localhost"</Host> <Delay>30</Delay> <Size>"None"</Size> </Run>- <Run No="2"> <Name>"Config CTI-Server"</Name> <Exe>"cticonfig.exe"</Exe> <Dir>"C:\Programs\Avaya\CTI"</Dir> <WDir>"C:\Programs\Avaya\CTI"</WDir> <Host>"localhost"</Host> <Size>"None"</Size> </Run> </Runlevel>- <Runlevel No="5"> <Name>"RIS-Server"</Name> - <Run No="1"> <Name>"RIS"</Name> <Exe>"ris_v1000.bat"</Exe> <Dir>"C:\Programs\Avaya\ris\bin"</Dir> <WDir>"C:\Programs\Avaya\ris\bin"</WDir> <Host>"localhost"</Host> </Run> </Runlevel>



- <Runlevel No="6"> <Name>"Com4Tel C"</Name> - <Run No="1"> <Name>"Tom Server"</Name> <Exe>"tomsrv.exe"</Exe> <Dir>"C:\Programs\Common Files\Tenovis\Tom"</Dir> <WDir>"C:\Programs\Common Files\Tenovis\Tom"</WDir> <Host>"localhost"</Host> <Size>"None"</Size> </Run>- <Run No="2"> <Name>"c4tsrvman"</Name> <Exe>"c4tsrvman.exe"</Exe> <Dir>"C:\Programs\Avaya\Com4TelC\bin"</Dir> <WDir>"C:\Programs\Avaya\Com4TelC\bin"</WDir> <Host>"localhost"</Host> </Run>- <Run No="3"> <Name>"C4T-Server (Partner)"</Name> <Exe>"c4tsrv.exe"</Exe> <Dir>"C:\Programs\Avaya\Com4TelC\bin"</Dir> <WDir>"C:\Programs\Avaya\Com4TelC\bin"</WDir> <Host>"localhost"</Host> <Size>"None"</Size> </Run> </Runlevel> </Scenario> </WDConfig>

Distributing the configuration file

The Watchdog application must run on every PC where a component to be monitored is started. All Watchdog applications must access identical copies of the configuration file.

You use the Distribute function of the WDConfig application to distribute the configuration file. Proceed as follows:

1. Configure the settings and scenarios with the WDConfig application. Keep in mind that you must configure all relevant scenarios in a distributed system.

2. Save the configuration by clicking or selecting Save under File.

3. Select File then Distribute. The configuration file is distributed to all servers contained within it.


Tips and tricks

Pinging the Watchdog

The configuration file contains the following entry.

<Server>"H1,H2,H3,H4"</Server> +--> +-----> +--------> +--> +-----> +-->

This creates the following files in TTrace.

2006_07_14_tt_[Watchdog@<H1>].log_ping_to_<H2>_and_back2006_07_14_tt_[Watchdog@<H1>].log_ping_to_<H3>_and_back2006_07_14_tt_[Watchdog@<H1>].log_ping_to_<H4>_and_back2006_07_14_tt_[Watchdog@<H2>].log_ping_to_<H3>_and_back2006_07_14_tt_[Watchdog@<H2>].log_ping_to_<H4>_and_back2006_07_14_tt_[Watchdog@<H3>].log_ping_to_<H4>_and_back

OmniORB naming service

With OmniORB naming service, you must make sure that the path containing the log files for OmniORB naming service is enclosed in additional quotation marks.

Example

<Runlevel No=1><Run Dir="F:\programs\omniORB" Exe="omniNames.exe" Args="-logdir \"F:\programs\omniORB\"" Host="localhost" Delay=10</Runlevel>



Options for Watchdog

Proceed as follows to display the available options for the Watchdog application.


2. Go to the Watchdog application folder, generally Program Files (x86)\Avaya\IP Office Contact Center\Watchdog.

3. Enter watchdog -? or watchdog -h. Press RETURN. The available options are displayed.

Multiple core dumps

By the time the Watchdog notices the loss of a process it is monitoring, this process may already have generated a core dump. While the Watchdog is terminating dependent processes, these processes, in turn, can generate core dumps. To prevent the core dump of the process that caused the error from being overwritten, the Watchdog can rename the existing file before the dependent processes are terminated.

Default

The default setting specifies that only one memory dump is generated.

Prerequisite

You can only use this function with the TTraceConsole application.

Setting multiple core dumps

We recommend setting no more than ten core dumps, as each core dump requires corresponding memory. Proceed as follows to configure ten core dumps, for example:

1. In the process output of the TTraceConsole command, enter the command RenameCoreDump in the Command field.

2. In the Parameter field, enter the number of core dumps (10 in this example).

3. Click Send. In this example, ten consecutive core dumps will be written. After this, the Watchdog application will revert back to the default setting. Now, only one core dump will again be generated.



Glossary

CORBA CORBA stands for Common Object Request Broker Architecture. Common Object Request Broker Architecture or CORBA is an object-oriented middleware providing platform-independent protocols and services that was developed by the Object Management Group (OMG). CORBA makes it easier to create distributed applications in heterogeneous environments.

IP IP stands for Internet Protocol. It is used to address and fragment data and transmit this data to the recipient.

RPC RPC stands for Remote Procedure Call. RPC is a facility for transferring messages. A distributed application in a network can call up services on various computers by using RPC. RPC is used when remotely administering computers.

Socket Socket is a mechanism which makes possible a virtual connection between two processes. It is activated using a socket address. The socket address consists of a port number and a host address.

TCP TCP stands for Transmission Control Protocol. IP stands for Internet Protocol. TCP/IP meets the two most important requirements to be fulfilled in a network. First, it ensures secure transmission. Second, TCP/IP offers an address scheme so that each computer can be assigned an unambiguous address. Computers are numbered by the IP protocol.

XML eXtensible Markup Language (XML) is a general format for presenting structured information.

XML



Index

Index

AAbout WDConfig . . . . . . . . . . . . . . . . . . 13Account . . . . . . . . . . . . . . . . . . . . . . . 8AddToStorage . . . . . . . . . . . . . . . . . .31, 37AliveInterval . . . . . . . . . . . . . . . . . . .15, 35AliveTimeout . . . . . . . . . . . . . . . . . .15, 35Args . . . . . . . . . . . . . . . . . . . . . . . 36As level . . . . . . . . . . . . . . . . . . . . . . 21

BBackColor . . . . . . . . . . . . . . . . . . . . . 36Background color . . . . . . . . . . . . . . . . . 23Before. . . . . . . . . . . . . . . . . . . . . . . 34BootTimeout. . . . . . . . . . . . . . . . . . .15, 35

CCallMacro . . . . . . . . . . . . . . . . . . . .31, 37CloseRequest . . . . . . . . . . . . . . . . . . . 17CmdLine . . . . . . . . . . . . . . . . . . . .30, 37Command . . . . . . . . . . . . . . . . . . . . . 41Commands . . . . . . . . . . . . . . . . . . . . 12Comment . . . . . . . . . . . . . . . . . . . .28, 36Complete . . . . . . . . . . . . . . . . . . . . . . 9Configuration . . . . . . . . . . . . . . . . . . . 3, 8Configuration file. . . . . . . . . . . . . 11, 12, 35, 37Containing runs depends on each other . . . . . . . 21ContinueWatching . . . . . . . . . . . . . . . .29, 36Copyright . . . . . . . . . . . . . . . . . . . . . 13CORBA . . . . . . . . . . . . . . . . . . . . . . . 7Core Dump . . . . . . . . . . . . . . . . . . . . . 6Core dump . . . . . . . . . . . . . . . . . . . . 41

DDatabase . . . . . . . . . . . . . . . . . . . . . . 8Database system . . . . . . . . . . . . . . . . . . 7DEFAULT . . . . . . . . . . . . . . . . . . . .17, 35DefaultDelay. . . . . . . . . . . . . . . . . 16, 23, 35Delay until next start . . . . . . . . . . . . . . . . 23Dependencies . . . . . . . . . . . . . . . . . .17, 35Dir . . . . . . . . . . . . . . . . . . . . . . . . 36Directory . . . . . . . . . . . . . . . . . . . . . 22Disabled . . . . . . . . . . . . . . . . . . . . . 36Display name . . . . . . . . . . . . . . . . . . . 22

Distribute . . . . . . . . . . . . . . . . . 11, 12, 39Distributing. . . . . . . . . . . . . . . . . . . . . 39DOS box . . . . . . . . . . . . . . . . . . . . . . 10drwtsn32.exe. . . . . . . . . . . . . . . . . . . . . 6

EEdit . . . . . . . . . . . . . . . . . . . . . . . . 13Environment variable . . . . . . . . . . . . . . . . . 8Example

Configuration file . . . . . . . . . . . . . . . . 37Import file . . . . . . . . . . . . . . . . . . . . 33Run . . . . . . . . . . . . . . . . . . . . . . 24Run level . . . . . . . . . . . . . . . . . . . . 21Scenario . . . . . . . . . . . . . . . . . . . . 19

Examples . . . . . . . . . . . . . . . . . . . . . . 9Exe . . . . . . . . . . . . . . . . . . . . . . . . 36Execute . . . . . . . . . . . . . . . . . . . . 30, 37Exit . . . . . . . . . . . . . . . . . . . . . . . . 12

FFile . . . . . . . . . . . . . . . . . . . . . . . . 12Folder . . . . . . . . . . . . . . . . . . . . . . . . 9

GGlossary . . . . . . . . . . . . . . . . . . . . . . 43

HHelp . . . . . . . . . . . . . . . . . . . . . . . . 13Host . . . . . . . . . . . . . . . . . . . . . . . . 36Host name . . . . . . . . . . . . . . . . . . . 23, 25Hosts . . . . . . . . . . . . . . . . . . . . . . . . 5

IIcon . . . . . . . . . . . . . . . . . . . . . . . . 12Import . . . . . . . . . . . . . . . . . . . . . . . 33import . . . . . . . . . . . . . . . . . . . . . . . 12Import file . . . . . . . . . . . . . . . . . . . . . 34Input prompt . . . . . . . . . . . . . . . . . . 10, 41Insert . . . . . . . . . . . . . . . . . . . . . . . 34Into . . . . . . . . . . . . . . . . . . . . . . . . 34IP . . . . . . . . . . . . . . . . . . . . . . . . 8, 43IP port . . . . . . . . . . . . . . . . . . . . . . . 15


Index

KKey . . . . . . . . . . . . . . . . . . . . . . . . 29Keyword . . . . . . . . . . . . . . . . . . . . . 35Keywords . . . . . . . . . . . . . . . . . . . .34, 35

Llocalhost . . . . . . . . . . . . . . . . . . . . . 16Located at directory . . . . . . . . . . . . . . .22, 32

MMacro . . . . . . . . . . . . . . . . . . . . . . . 36Maximized. . . . . . . . . . . . . . . . . . . . . 23Memory dump . . . . . . . . . . . . . . . . . . . . 6Menu bar . . . . . . . . . . . . . . . . . . . . . 12Minimized . . . . . . . . . . . . . . . . . . . . . 23Minutes . . . . . . . . . . . . . . . . . . . . . . 36Multi-host system . . . . . . . . . . . . . . . . . 17

NName . . . . . . . . . . . . . . . . 18, 21, 25, 28, 37Network connection . . . . . . . . . . . . . . .15, 16Network environment. . . . . . . . . . . . . . . . . 8New. . . . . . . . . . . . . . . . . . . . . . .12, 13No TTrace Display . . . . . . . . . . . . . . . . . 23NoDisplay . . . . . . . . . . . . . . . . . . . . . 36

OOmniORB naming service . . . . . . . . . . . . . 40One Server Standard Solutions . . . . . . . . . . . . 9OnTermination. . . . . . . . . . . . . . . . . . . 36Open . . . . . . . . . . . . . . . . . . . . . .12, 13Optional . . . . . . . . . . . . . . . . . . . . .21, 35Options . . . . . . . . . . . . . . . . . . . . . . 41Order . . . . . . . . . . . . . . . . . . . . . . . 24

PParameter . . . . . . . . . . . . . . . . . . . .37, 41Parameter field . . . . . . . . . . . . . . . . . . 32PauseWatching . . . . . . . . . . . . . . . . .29, 36Ping. . . . . . . . . . . . . . . . . . . . . . . 5, 40Port . . . . . . . . . . . . . . . . . . . . . . .15, 35Precondition . . . . . . . . . . . . . . . . . . . . 28Priority . . . . . . . . . . . . . . . . . . . . . . 23Process . . . . . . . . . . . . . . . . . . . . . . . 7Process ID . . . . . . . . . . . . . . . . . . . . 32Process priority . . . . . . . . . . . . . . . . . . 23Processes . . . . . . . . . . . . . . . . . . . 5, 8, 15

ProcessPrio . . . . . . . . . . . . . . . . . . . . 36Program arguments . . . . . . . . . . . . . . . . 22Program arguments inclusive . . . . . . . . . . . . 25

QQuotation mark . . . . . . . . . . . . . . . . . . . 35

RRealtime . . . . . . . . . . . . . . . . . . . . . . 23RegDate . . . . . . . . . . . . . . . . . . . . . . 36RegKey . . . . . . . . . . . . . . . . . . . . . . 36RegSubKey . . . . . . . . . . . . . . . . . . . . 36RegValueName . . . . . . . . . . . . . . . . . . 36Ren.Host. . . . . . . . . . . . . . . . . . . . . . 25Rename Hosts . . . . . . . . . . . . . . . . . . . 25Replication system . . . . . . . . . . . . . . . . . . 7Rights . . . . . . . . . . . . . . . . . . . . . . . . 8RPC . . . . . . . . . . . . . . . . . . . . . . . . 43Run . . . . . . . . . . . . . . . . . . 22, 24, 28, 36Run installed service . . . . . . . . . . . . . . . . 22Run level. . . . . . . . . . . . . . . . 20, 24, 34, 35

SSave. . . . . . . . . . . . . . . . . . . . 12, 13, 39Save as . . . . . . . . . . . . . . . . . . . . 12, 13Scenario . . . . . . . . . . . . . . . . . . 17, 34, 35Send . . . . . . . . . . . . . . . . . . . . . . . 41Server . . . . . . . . . . . . . . . . . . . . . 16, 35Service . . . . . . . . . . . . . . . . . . . . 10, 22Service names . . . . . . . . . . . . . . . . . . . 22SetRegistryString. . . . . . . . . . . . . . . . 29, 36Settings . . . . . . . . . . . . . . . . . . . . . . 15

Macro . . . . . . . . . . . . . . . . . . . . . 28Precondition . . . . . . . . . . . . . . . . . . 28Run . . . . . . . . . . . . . . . . . . . . . . 22Run level . . . . . . . . . . . . . . . . . . . . 21Symbols . . . . . . . . . . . . . . . . . . . . 32

Size . . . . . . . . . . . . . . . . . . . . . . . . 36Socket . . . . . . . . . . . . . . . . . . . . . . . 43Stand-alone system . . . . . . . . . . . . . . . . 16Standby . . . . . . . . . . . . . . . . . . . . . . 11Start executable . . . . . . . . . . . . . . . . . . 22Start on host . . . . . . . . . . . . . . . . . . . . 23Start service . . . . . . . . . . . . . . . . . . . . 22Startup parameters . . . . . . . . . . . . . . . . . 22Status bar . . . . . . . . . . . . . . . . . . . . . 13Steps . . . . . . . . . . . . . . . . . . . . . 28, 32Stop timeout . . . . . . . . . . . . . . . . . . . . 23StopTimeout . . . . . . . . . . . . . . . . . . . . 36Storage . . . . . . . . . . . . . . . . . . . . 31, 32StoreRegistryString . . . . . . . . . . . . . . . . . 30


Index

Subkey . . . . . . . . . . . . . . . . . . . . . . 29SwitchDelay . . . . . . . . . . . . . . . . . . .16, 35Symbolic name of run . . . . . . . . . . . . . . . 22

TTags . . . . . . . . . . . . . . . . . . . . . . . 35TCP. . . . . . . . . . . . . . . . . . . . . . . . . 8TCP/IP . . . . . . . . . . . . . . . . . . . . . 5, 15Temporarily disabled . . . . . . . . . . . . . . . . 28Termination . . . . . . . . . . . . . . . . . . . . 21Text color . . . . . . . . . . . . . . . . . . . . . 23TextColor . . . . . . . . . . . . . . . . . . . . . 36Time interval. . . . . . . . . . . . . . . . . . . . 15Timeout . . . . . . . . . . . . . . . . . . . . . . 15Tool bar . . . . . . . . . . . . . . . . . . . . . . 13TTrace . . . . . . . . . . . . . . 5, 9, 23, 27, 32, 40TTraceConsole . . . . . . . . . . . . . . . . . 6, 41Two Server Standard Solutions . . . . . . . . . . . . 9

Uuninstalling . . . . . . . . . . . . . . . . . . . . 10User symbols inclusive . . . . . . . . . . . . . . . 25User-defined symbols . . . . . . . . . . . . . .25, 26

VValue . . . . . . . . . . . . . . . . . . 25, 29, 35, 37Valuename . . . . . . . . . . . . . . . . . . . . 29Version . . . . . . . . . . . . . . . . . . . . .13, 28View . . . . . . . . . . . . . . . . . . . . . . . 13

WWatchdog . . . . . . . . . . . . . . 5, 7, 8, 9, 15, 20WatchInterval . . . . . . . . . . . . . . . . . .15, 35WDConfig . . . . . . . . . . . . . . . . . . . . 5, 12WDImport . . . . . . . . . . . . . . . . . . . . . 34WDir . . . . . . . . . . . . . . . . . . . . . . . 36Window size . . . . . . . . . . . . . . . . . . . . 23Working directory . . . . . . . . . . . . . . . . . 23

XXML . . . . . . . . . . . . . . . . . . . . 6, 35, 43


Index