RemoteWare Server Administrator'

RemoteWare
Server
A dm i n i st r a to r ’s
G u i d e
Version 4.1 Service Pack 1A
RemoteWare Server Administrator’s Guide
Version 4.1 Service Pack 1A
This document was prepared to assist licensed users of RemoteWare by XcelleNet, Inc.; its contents may not be used for any
other purpose without prior written permission. The material contained herein is supplied without representation or warranty
of any kind and is based on typical use. Any unusual use may produce unpredictable results. XCELLENET ASSUMES NO
RESPONSIBILITY AND SHALL HAVE NO LIABILITY OF ANY KIND ARISING FROM THE SUPPLY OR USE
OF THIS DOCUMENT OR THE MATERIAL CONTAINED HEREIN. Companies, names, information, and data used
in examples herein are fictitious unless otherwise noted. The information in this document is furnished for informational use
only and is subject to change without notice.
References in this manual to XcelleNet products, programs, or services do not imply that XcelleNet intends to make these
available in all countries in which XcelleNet operates.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR
52.227-19.
© 1997-2003 XcelleNet, Inc. All Rights Reserved.
All rights reserved, including the right to reproduce this document or any portion thereof in any form.
Printed in the United States of America.
RemoteWare is a trademark of XcelleNet, Inc.
Other product and company names mentioned herein may be the brand names, trade names, trademarks or registered trademarks of their respective orders.
Contents
U S IN G TH IS GU ID E
About this guide ................................................................................................................ xi
Use Adobe Acrobat to view guide online ......................................................................... xi
Using RemoteWare online Help ..................................................................................... xii
RemoteWare Support Services....................................................................................... xiii
What’s in this guide ......................................................................................................... xiv
Related publications........................................................................................................ xvi
CH AP TE R 1: S E TT IN G U P TH E S E R V E R
Starting and stopping the Server ..................................................................................... 20
Starting a local Server .................................................................................................. 20
Stopping a local Server ................................................................................................ 21
Starting a Clustered Server ......................................................................................... 22
Using the RemoteWare Menu......................................................................................... 24
Using Administrator to set security ................................................................................. 27
Enabling users or groups ............................................................................................. 28
Disabling users or groups ............................................................................................ 29
Granting rights ............................................................................................................. 29
Denying rights.............................................................................................................. 30
Changing system-wide settings........................................................................................ 31
Changing the System Name ........................................................................................ 32
Changing the local Server name ................................................................................. 33
Setting the date and time on a standalone Server ...................................................... 34
Changing the date and time on Clustered Servers..................................................... 35
Changing the time zone............................................................................................... 35
Changing the date and time format ............................................................................ 37
Controlling how the Server maintains connections.................................................... 38
Controlling work object execution .............................................................................. 39
Changing the way the Server communicates.............................................................. 40
Setting alarm thresholds .................................................................................................. 41
Setting logging options..................................................................................................... 42
Removing a Cluster or Workstation ................................................................................ 43
Setting up an Execution Server ....................................................................................... 44
iv
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
CH AP TE R 2: S E TT IN G U P CO MM UN ICA TI O N R E S OU R CE S
Using dial scripts .............................................................................................................. 46
Creating a new dial script ............................................................................................ 47
Editing dial scripts ........................................................................................................... 48
Saving a dial script ....................................................................................................... 49
Compiling a dial script................................................................................................. 49
Changing dial script font options ................................................................................ 50
Using long distance services ............................................................................................ 51
Adding a long distance service .................................................................................... 52
Enabling and disabling a long distance service .......................................................... 53
Copying a long distance service .................................................................................. 53
Deleting a long distance service .................................................................................. 54
Updating a long distance service ................................................................................. 54
Limiting outbound connections ...................................................................................... 55
Activating Server resources ............................................................................................. 56
Creating a Network Group.......................................................................................... 56
Displaying current resources....................................................................................... 58
Adding asynchronous resources .................................................................................. 59
Editing asynchronous resources.................................................................................. 62
Deleting an asynchronous resource ............................................................................ 63
Defining NetBIOS resources ...................................................................................... 63
Defining process only resources ................................................................................. 65
Defining SPX and TCP/IP resources.......................................................................... 66
Working with modem types ............................................................................................. 69
Editing modem definitions.......................................................................................... 70
Copying a modem type ................................................................................................ 72
Defining protocol services ............................................................................................... 74
Adding a protocol......................................................................................................... 75
Copying a protocol....................................................................................................... 76
Updating a protocol ..................................................................................................... 76
Deleting a protocol ...................................................................................................... 76
CH AP TE R 3: D E F IN IN G A ND UP DA TI NG CLI EN TS
Displaying the Client List ................................................................................................
Filtering the Client list ................................................................................................
Adding a Client definition ...............................................................................................
Changing the general Client settings ..........................................................................
78
79
82
83
Co nt ents
v
Specifying Client communication settings.................................................................. 85
Specifying Server communication settings for Clients............................................... 89
Assigning sessions to Clients............................................................................................ 90
Unassigning a selection from a Client......................................................................... 91
Viewing Client information.............................................................................................. 92
Supplying Client comments............................................................................................. 93
Updating Client definitions ............................................................................................. 94
Copying a Client definition.............................................................................................. 95
Deleting a Client definition ............................................................................................. 96
Resetting Security ............................................................................................................ 96
Defining Client groups .................................................................................................... 97
Assigning members to Client groups .......................................................................... 98
Assigning Client groups to parents.............................................................................. 99
Deleting a Client group ............................................................................................. 100
Editing a Client group ............................................................................................... 100
CH AP TE R 4: I NS TA LL IN G TH E CLIE N T
Making Client installation kits .......................................................................................
Installing ODBC and MAPI on RemoteWare Clients .............................................
Creating standard Client installation kits..................................................................
Upgrading Windows-based RemoteWare Clients ....................................................
Creating installation kits for OS/2 Clients ................................................................
Using template Clients...................................................................................................
Creating template installation kits.............................................................................
Creating Client installation kit to Run Client as a Service ...........................................
Setting template Client parameters ..........................................................................
Registering a template Client....................................................................................
ESD Auto Apply ........................................................................................................
102
102
103
106
110
111
111
115
118
120
124
CH AP TE R 5 : B U ILD IN G O B JE CTS
Using Work Object Editor .............................................................................................
Creating a work object ...................................................................................................
Setting general work object attributes ..........................................................................
Defining events for Worklist and ESD objects.............................................................
Add defining events for Multicast Work Object ...........................................................
Adding Byte Level Differencing to work object...........................................................
Inserting events..........................................................................................................
126
128
129
131
133
134
134
vi
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Copying, pasting, and deleting events.......................................................................
Searching for events...................................................................................................
Searching and replacing event text ...........................................................................
Disabling and enabling events...................................................................................
Exporting an event list...............................................................................................
Importing an event list...............................................................................................
Creating a Group object ................................................................................................
Specifying attributes for an Application object.............................................................
Choosing members for an Application or Application Group object ..........................
Defining events for Multicast work object....................................................................
Enabling and disabling work objects .............................................................................
Making work object assignments...................................................................................
Assigning sessions to objects .....................................................................................
Assigning Clients to objects.......................................................................................
Assigning users and user groups to applications.......................................................
Assigning objects to parents ......................................................................................
Filtering the Objects list ................................................................................................
Copying, deleting, and renaming objects......................................................................
Using Worklist Editor ....................................................................................................
Inserting events..........................................................................................................
Copying, pasting and deleting events........................................................................
Exporting an event list...............................................................................................
Importing an event list...............................................................................................
ESD Auto Apply ........................................................................................................
135
136
137
138
139
140
141
142
143
145
145
146
147
148
150
152
153
155
156
158
159
160
161
161
CH AP TE R 6: D E F IN IN G A ND S CHE D UL IN G S E S S IO NS
Creating sessions ............................................................................................................
Setting the session schedule ......................................................................................
Assigning objects to a session ....................................................................................
Assigning Clients to a session ....................................................................................
Setting up RemoteWare Multicast session ...............................................................
Assigning Multicast work object to the session ........................................................
Assigning Clients to Multicast session ......................................................................
Limiting session activity.............................................................................................
Enabling and disabling sessions.....................................................................................
Changing a session schedule..........................................................................................
Copying, renaming, and deleting sessions ....................................................................
164
165
167
169
170
170
171
172
173
173
174
vii
R e m o t e W a r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Viewing current and scheduled sessions .......................................................................
Changing the screen refresh interval ........................................................................
Viewing details of the session ....................................................................................
Filtering the list of sessions............................................................................................
Changing session execution times .................................................................................
Selecting the current server ......................................................................................
Turning the Scheduler on and off .............................................................................
175
176
176
178
178
179
179
CH AP TE R 7: CO N NE CT IN G IN TE R A CTI V E LY
Interactively connecting to a Client ..............................................................................
Using literals in pathnames .......................................................................................
Selecting a view..........................................................................................................
Customizing the Interactive Session window ...............................................................
Changing colors and fonts .........................................................................................
Storing contents of the output screen ...........................................................................
Using Remote Console ..................................................................................................
Using Remote Console with DOS Clients................................................................
Using Remote Console with OS/2 Clients................................................................
Troubleshooting Remote Console .................................................................................
Disconnecting from the Client..................................................................................
Understanding Remote Control ....................................................................................
Setting up Remote Control .......................................................................................
Assigning the Remote Control work object to Clients .............................................
Setting up Remote Control modems ........................................................................
Using Remote Control...............................................................................................
182
183
184
185
185
187
189
192
193
195
195
196
196
197
197
198
CH AP TE R 8: U S IN G S E S SI O N R E CO V E R Y
Using Session Recovery .................................................................................................
Using the Client/Session list box ...............................................................................
Using the Session Recovery status icons...................................................................
Customizing the Session Recovery window ..................................................................
Using Session Recovery’s filters.....................................................................................
Using filter combinations ..........................................................................................
Filtering by Status......................................................................................................
Filtering by All ...........................................................................................................
Filtering by Client......................................................................................................
Filtering by Session....................................................................................................
202
203
204
206
207
208
210
210
211
212
viii
R e m o t e W a r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Filtering by Time Range............................................................................................
Filtering by ECF........................................................................................................
Filtering by session status..........................................................................................
Removing filters.........................................................................................................
Importing and exporting filter settings .....................................................................
Viewing Client details ....................................................................................................
Updating session data ....................................................................................................
Using the Refresh Automatically function................................................................
Manually refreshing data ...........................................................................................
Restarting sessions .........................................................................................................
Identifying unsuccessful restarts ...............................................................................
Generating Session Recovery reports ...........................................................................
213
214
215
215
215
218
219
219
220
221
222
223
CH AP TE R 9: M O NIT O RI NG CUR R E NT SY S TE M AC TIV I TY
Viewing the system’s current status ...............................................................................
Viewing the status of different resources..................................................................
Viewing resource details ............................................................................................
Viewing active sessions information ..........................................................................
Viewing Client information .......................................................................................
Viewing Network status alarms .................................................................................
Starting and stopping the scheduler..........................................................................
Monitoring the Server status .........................................................................................
Viewing Server information.......................................................................................
Viewing licensing values ............................................................................................
Updating licensing values ..........................................................................................
Viewing the Licensing Log ........................................................................................
Viewing Server or Cluster activity.............................................................................
Using Report Manager...................................................................................................
Using the Report Editor ............................................................................................
Printing a report.........................................................................................................
Deleting a report........................................................................................................
Copying a report ........................................................................................................
Working with report definitions ................................................................................
Generating reports from sessions or command lines ...............................................
Using Report Manager to generate CSV files ..........................................................
Using the command line to generate CSV files........................................................
Generating a CSV file from within a session ............................................................
226
227
228
230
231
232
232
233
235
236
237
238
239
240
241
242
243
243
244
245
246
247
248
ix
R e m o t e W a r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
CH AP TE R 10 : V IE W ING RE M O TE WA R E LO GS
Using the Log Viewer ....................................................................................................
Setting View Properties..................................................................................................
Selecting fields within a view ....................................................................................
Quick Filters Views ........................................................................................................
Customizing an existing Quick Filter View...............................................................
Creating Quick Filter View .......................................................................................
Viewing Quick Filter Views .......................................................................................
Filtering fields within a view..........................................................................................
Setting field values .....................................................................................................
Customizing the Log Viewer .........................................................................................
Renaming and reorganizing folders and views .........................................................
Viewing log details..........................................................................................................
Viewing row details ....................................................................................................
Viewing session event details.....................................................................................
Displaying work object details...................................................................................
Displaying event details.............................................................................................
Exporting a log view.......................................................................................................
252
254
255
257
259
261
262
263
264
266
268
270
270
272
273
274
275
CH AP TE R 11 : U S ING R EM O TE WA R E ME S S A GIN G
Working with user definitions........................................................................................
Filtering the list of users............................................................................................
Adding a new local user .................................................................................................
Adding a new remote user .............................................................................................
Assigning groups to local or remote users.....................................................................
Assigning applications to local users..............................................................................
Assigning user attributes to local users..........................................................................
Copying and deleting existing users ..............................................................................
Working with user groups ..............................................................................................
Assigning users to user groups ..................................................................................
Assigning applications to a user group ......................................................................
Editing an existing user group...................................................................................
Copying a user group.................................................................................................
Deleting a user group ................................................................................................
Viewing database assignments .......................................................................................
Setting Messaging Log options......................................................................................
Synchronizing address books .........................................................................................
278
279
280
282
283
285
288
291
292
294
296
298
299
300
301
302
303
x
R e m o t e W a r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Updating address books immediately .......................................................................
Updating address books periodically.........................................................................
Setting non-delivery receipt options .............................................................................
Working with Gateways .................................................................................................
Accessing the RemoteWare Gateway properties pages ...........................................
Configuring the RemoteWare Gateway....................................................................
Activating Gateway synchronization .........................................................................
Maintaining Gateways....................................................................................................
Configuring and using MAPI services...........................................................................
Working with the Message Store Service .................................................................
Working with the Address Book Service...................................................................
304
304
307
309
310
311
313
314
316
316
317
A PPE N D IX A: D E LI VE RI NG RE M O TE WA R E SCR I PTS
Creating the RemoteWare Script ..................................................................................
Testing the script........................................................................................................
Placing scripts on the Server .....................................................................................
Creating the scripts ESD work object ......................................................................
320
320
320
321
A PPE N D IX B: TU NI NG A R E MO T E WA RE CL US TE R
Network topology considerations ..................................................................................
Transports and binding orders.......................................................................................
Registry settings .............................................................................................................
324
324
325
A PPE N D IX C: RE M O TE WA R E DA TA B AS E S CHE M A
RWLOG_Session History LOG VERSION: 4.00.0055.0000.4 ...................................
RWLOG_FileTransfers LOG VERSION: 4.00.0055.0000.2 .......................................
RWLOG_Messaging LOG VERSION: 4.00.0055.0000.2 ...........................................
RWLOG_MsgRecipients LOG VERSION: 4.00.0055.0000.1 ....................................
RWLOG_ServerMessages LOG VERSION: 4.00.0055.0000.3 ..................................
RWLOG_In+ventory LOG VERSION: 4.00.0055.0000.1 ..........................................
328
331
333
334
335
336
INDEX...................................................................................................................................... 361
Chapter X: Chapter Title <-- Apply “chapter hidden” style
Using This Guide
This guide introduces you to RemoteWare, a remote-systems management tool
specifically designed to distribute software to and perform inventory scans for remote
and fixed-site users. It contains fundamental information necessary to use the software.
About this guide
We recommend you print this guide so it is readily available as you perform your tasks.
If you prefer to use this guide online, you may find it helpful to zoom to 150% for
enhanced readability.
Printing this manual
From Acrobat Reader, you can print the entire guide or a range of pages.
To print the guide:
1
On the File menu, click Print.
2
Select the printer and number of copies, and click OK.
Use Adobe Acrobat to view guide online
Use Adobe Acrobat Reader’s hyperlinks and Find features to easily access information
in this guide.
Hyperlinks
Hyperlinks take you directly to a topic or page. Hyperlinks are included for the
following:
•
Table of Contents and Index
•
Topics at the beginning of each chapter
•
Cross references
To use hyperlinks:
1
Click the
Hand tool on the Acrobat Reader toolbar. The pointer changes to a
hand.
2
Place the hand symbol over the topic/page number you want to view and click.
Acrobat Reader takes you to the page you selected.
xii
R e m o t e W a r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Find feature
You can use Find to search for text in any document you have open.
To search for text:
1
On the toolbar, click
2
Enter the term(s) you want to find in the Find What field. Click Cancel to close.
3
To narrow your search:
4
Find.
•
Match Whole Word Only to search for the exact term only.
•
Match Case to do a case-sensitive search.
•
Find Backwards to move backwards instead of forwards through the
document.
Click Find to begin your search.
To continue to search for other instances of a term, select Edit and Find Again. In
the Find dialog box, the original term displays in the Find What field. Click Find
Again. Repeat this process until you have found the section you want to view.
Using RemoteWare online Help
RemoteWare online Help provides explanations of features and steps for how to
complete tasks.
To access RemoteWare online Help:
On the application’s Help menu, click Topics (or Help Topics), or press F1.
RemoteWare Support Services
XcelleNet offers a variety of support options to help you get the most out of
RemoteWare.
If you have a question about the product, first look in the documentation or consult the
online Help. If you can’t find the answer, contact Customer Support.
Usin g This Gu id e
xiii
Customers who are on a maintenance plan with XcelleNet may contact Technical
Support Monday through Friday from 8:30 A.M. to 8:30 P.M. EST for assistance. Call
the Technical Support staff at 1-800-669-1211 toll free, 678-585-7320 in the Atlanta,
Georgia area or +44 208 538 5888 for Europe, Middle East or Africa. You can find
detailed information on obtaining Technical Support on XcelleNet’s
www.XcelleNet.com web site.
xiv
R e m o t e W a r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
What’s in this guide
This guide includes the following:
Table 1. Chapters in this guide
Chapter
Title
Description
Chapter 1
Setting up the Server
Explains how to use Administrator and
Server Profile to set security, enable
users, and configure Server parameters.
Chapter 2
Setting up Communication
Resources
Explains how to use Server Profile to
define resources at the Server so the
Server can communicate with the
Client.
Chapter 3
Defining and Updating Clients
Explains how to use Client Profile to
define Clients and Client groups.
Chapter 4
Installing the Client
Explains how to use the Makekit Wizard
in Client Profile to create installation
kits for Clients and template Clients.
Chapter 5
Building Objects
Explains how to use Work Object Editor
and Worklist Editor to create different
types of work objects and assign them to
communications sessions and/or Clients.
Chapter 6
Defining and Scheduling
Sessions
Explains how to use Session Editor to
define and schedule sessions between
the Server and Clients.
Chapter 7
Connecting Interactively
Explains how to use Interactive Session
to remotely interact with Clients, either
using Interactive Session, Remote
Console, or Remote Control with
pcAnywhere.
Chapter 8
Using Session Recovery
Explains how to use Session Recovery to
track and troubleshoot sessions that are
failed or missing.
Chapter 9
Monitoring Current System
Activity
Explains how to use Network Status to
check the status of current sessions and
the state of the Server, and how to print
status reports using Report Manager.
Chapter 10
Viewing RemoteWare Logs
Explains how to use Log Viewer to view
RemoteWare Session History, Server
Messages and File Transfer Logs.
Usin g This Gu id e
Table 1. Chapters in this guide
Chapter 11
Using RemoteWare Messaging
Explains how to use Directory Manager
and Messaging Administrator to define,
add, and delete users to address books,
as well as synchronize address books.
Appendix A
Delivering RemoteWare Scripts
Explains how to deliver RemoteWare
scripts.
Appendix B
Tuning a RemoteWare Cluster
Explains how to tune a Cluster.
Appendix C
RemoteWare Database Schema
Displays the Field Name, Attribute, and
Description of the log and messaging
functions.
xv
xvi
R e m o t e W a r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Related publications
These guides are available in electronic format on the RemoteWare CD-ROM or from
the XcelleNet’s www.XcelleNet.com web site.
•
RemoteWare Server Installation Guide. Contains detailed information about
configuring your system so you can install the RemoteWare Server and its
components.
•
RemoteWare Server Reference Guide. Contains a detailed description of every
application, facility, window, menu, and control present in the RemoteWare Server.
Use this book when you want to know what something does, how it is used, or why it
behaves as it does.
Electronic documentation
In addition to the printed books, the following documents are available on the
RemoteWare CD. Unless otherwise specified, all documents reside in the \Documents
directory. All electronic documents require the Adobe Acrobat reader to view and print
PDF files. Install the reader from the RemoteWare CD using
the\Acroread\Acroread.exe file.
Administrator guides
•
RemoteWare Workshop for Windows Developer’s Guide. Explains how to use
RemoteWare Workshop to create and publish customized desktop-style Workshop
applications.
•
RemoteWare Subscriber Administrator’s Guide. Shows how to build and deploy lists
of files and applications to the Client. It also explains how to use the Subscriber
Lists at the RemoteWare Client.
•
RemoteWare AntiVirus Manager Administrator’s Guide. Explains how to deploy,
maintain, control, and report on McAfee VirusScan software in networks serviced
by RemoteWare.
•
RemoteWare Inventory Manager Administrator’s Guide. Explains how to use
Inventory Manager for centralized monitoring and reporting of hardware and
software resources on RemoteWare Clients. Instructions include how to create
Inventory Manager Profiles that control the operating and scheduling of Client
inventory scans, and how to assign those Profiles to Clients. The guide also
describes how to view and interpret the centrally stored resource information for
each Client.
•
RemoteWare Software Manager Administrator’s Guide. Explains how to use
Software Manager to efficiently and securely distribute, install, and manage
Using This Guide
xvii
software for enterprise system users. Includes how to create and define software
package contents and then assign that package to a RemoteWare Client.
•
RemoteWare Migration Guide. Explains how to plan and implement many aspects
of migration from RemoteWare for OS/2 to RemoteWare.
•
RemoteWare Multicast System Administrator’s Guide. Explains how to use
RemoteWare Multicast. Multicast allows administrators to distribute files to a large
number of RemoteWare Clients with a single communication session from the
Server. It contains fundamental information necessary to use the software,
including a conceptual overview and highly interactive walkthroughs.
•
RemoteWare ActiveX Controls Reference Manual. Presents the 32-bit ActiveX
controls that are included with the RemoteWare 32-bit Client software. These
controls add selected Client functionality to ActiveX or OLE container applications.
•
RemoteWare Developer’s API Manual. Describes the RemoteWare Application
Programming Interfaces (APIs) that allows you to control and configure the
RemoteWare Server and Clients using a third-party programming language such as
Microsoft Visual C++ 6.0 or Microsoft Visual Basic 6.0.
•
RemoteWare Workshop for Windows Programmer’s Guide. Describes optional
programmatic extensions that enhance Workshop environments.
•
Summit BasicScript Reference Manual and Summit BasicScript User’s Guide
provide information on the options and structure for RemoteWare scripting. These
documents are available in the \Document\Development Tool Administrator
Guides\Summit BasicScript Documentation directory on the RemoteWare CD.
•
User’s Guide/VirusScan for Windows 3.1®, 95/98, and NT. Helps the Windows Client
user understand the functionality in McAfee VirusScan for Windows 3.1, Windows
95/98, and Windows NT Workstation 4.0.
Client guides
•
RemoteWare 32-Bit Windows Client User’s Guide. Helps the 32-bit Windows Client
user install, set up, and understand the functionality in the RemoteWare Client.
•
RemoteWare Windows 3.x Client User’s Guide. Helps the 16-bit Client user install,
learn, and take advantage of all the features available in the RemoteWare Windows
3.x Client software.
•
RemoteWare DOS Client User’s Guide. Explains how to use the DOS Client for
communication with the RemoteWare Server.
•
RemoteWare OS/2 Client User’s Guide. Presents the features, setup procedures,
available options, and connection methods for the OS/2 Client software.
xviii
R e m o t e W a r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
•
RemoteWare 4690 Client User’s Guide. Explains how Clients in the IBM 4690
environment exchange data and files with the RemoteWare Server. Also presents
the user interface features and available options.
•
RemoteWare Text-Based Clients User’s Guide. Explains how to use the SCO, UNIX,
AIX, VMS and DOS Clients to communicate with the RemoteWare Server.
•
RemoteWare Software Manager Client User’s Guide. Describes how Client users
can subscribe to Software Manager packages and then communicate with a
RemoteWare Server to receive those packages.
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
1
1RemoteWare
Setting up the Server
Once you have installed the RemoteWare Server and started the service, you should set
up access rights, confirm a successful installation, and configure resources the Server
uses to communicate with remote users. To successfully complete the tasks in this
chapter, make sure the RemoteWare Server service is running and you have access to
the necessary RemoteWare Server programs.
This chapter includes:
• Start and stop a local or Clustered Server
• RemoteWare Menu used to access programs
• Administrator program used to set security
• Change system-wide settings
• Set alarm thresholds
• Set logging options
• Remove a Cluster or Workstation
• Set up an Execution Server
20
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Starting and stopping the Server
RemoteWare Servers use a Windows NT service process to manage and run the Server
programs and subsystems. Sometimes you may need to start or stop a Server service.
You can create icons to start and stop a local RemoteWare Server. To avoid accidentally
shutting down the Server, you should place these icons in a separate program group,
such as the RemoteWare Utilities group. You can also place shortcut icons on your
desktop.
Starting a local Server
Note: You can only start the local RemoteWare Server service from the local computer.
To start a local RemoteWare Server service from the Windows NT command line type
net start "RemoteWare", or use the steps below.
To start a local Server from the Services control panel:
1
On the Start menu, point to Settings and select Control Panel.
2
Double-click the
3
Scroll through the list of services and select the RemoteWare Server service.
4
Click Start. The RemoteWare Server service starts and appears as “Started” in the
Status column.
Services icon in the Control Panel window.
C HAPT ER 1 / Set ting up t he Ser ve r
5
21
Click Close after the service has started.
Stopping a local Server
To stop a local RemoteWare Server service from the Windows NT command line type
net stop “RemoteWare”, or use the steps below.
To stop a local Server from the Services control panel:
1
On the Start menu, point to Settings and select Control Panel.
2
Double-click the
3
Highlight the RemoteWare Server service.
4
Click Stop. The RemoteWare Server service stops and the Status column is empty.
5
Click Close after the service has stopped.
Services icon in the Control Panel window.
22
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Starting a Clustered Server
To start a Clustered Server from a remote computer:
1
2
In RemoteWare Menu, double-click the
Administrator icon.
On the File menu, select Server Control and Options.
The System Control property page lists available Servers.
3
Select the Server you want to start.
4
Click Start. The Administrator program closes automatically. To verify the Server
has started, reopen the Administrator.
Note: If RemoteWare Servers in a Cluster use a different username/password to log
on as a Windows NT service for the RemoteWare Server service, the Server
reports a “Down” state in the Administrator, Server Profile, and Network Status
programs. You must use the same user name and password for the RemoteWare
service on all computers.
C HAPT ER 1 / Set ting up t he Ser ve r
23
Using Administrator to start and stop the Server
Sometimes you may change the Server settings, and in order for those changes to take
effect, you will need to restart the Server. You can use the Administrator program to
stop and start the Server from within the RemoteWare program.
To start or stop a local or Clustered Server:
n
You cannot use
the Server Control
and Options feature
to start a local
RemoteWare Server.
This feature is only
applicable to remote
Servers and
Workstations in a
RemoteWare Cluster.
1
In the RemoteWare Menu, double-click the
Administrator icon.
2
On the File menu, select Server Control and Options.
The Start and Stop buttons are enabled when you select a Server.
n
If you have a
clustered system with
more than three
Servers, bringing
multiple Servers
down results in an
alarm being
registered in the
alarms section only
for the last Server
brought down.
3
On the System Control page, select a Server, then click Start or Stop.
4
Click OK to return to the Administrator window.
24
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Using the RemoteWare Menu
Use the RemoteWare Menu to access the applications available to you within the
RemoteWare program. When you start the service, the RemoteWare Menu appears.
The RemoteWare Menu program is an Explorer-style interface that lists groups of
RemoteWare programs in the left pane and the individual programs available to you in
the right pane. The programs you see in the RemoteWare Menu depend on two things:
•
The applications you installed on the RemoteWare Server machine.
•
The program access rights for the currently logged-in user. You assign rights from
the Administrator program. For more information, see “Granting rights” on
page 29.
To view the available programs: Highlight a program group in the left pane; the
available programs appears in the right pane.
To open a program: Double-click a program icon in the right pane.
C HAPT ER 1 / S ett ing up t he Ser ve r
25
Table 2, “RemoteWare programs,” briefly describes all of the programs available in
RemoteWare Server. Some of these programs are optional or may be installed as standalone programs; your RemoteWare Server may not include all of the programs listed
below. For a more detailed list and explanation of the RemoteWare Menu, see the
RemoteWare Server Reference Manual or the appropriate application Administrator’s
Guide.
Table 2. RemoteWare programs
Program
Icon
Program
Use this program to . . .
Administrator
Assign System Administrator rights to users.
Server Profile
View or configure Server system parameters.
Client Profile
Set Client parameters and view Client
information.
Work Object Editor
Define and organize tasks to execute.
Worklist Editor
Create or modify task lists.
Session Editor
Schedule and organize how and when work
objects will execute.
Schedule Manager
Monitor and deploy sessions.
Network Status
Monitor communications activity and Server
status.
Report Manager
View and generate Server information.
Interactive Session
Establish and interactive link with a Client.
Log Viewer
View SQL logs containing information about your
RemoteWare Server(s) and Clients.
Messaging Administration
Adjust the Message Transfer Agent’s (MTA)
operating parameters.
Directory Manager
Create and manage RemoteWare users.
26
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Table 2. RemoteWare programs
Program
Icon
Program
Use this program to . . .
Subscriber Editor
Compile and publish collections of files that are
available to Clients.
Workshop Editor
Develop and deploy custom operating
environments to Clients.
Software Manager
Distribute, install, and manage software for
Clients.
Inventory Manager
Inventory, retrieve, and report essential software
and hardware inventory information that resides
on Clients’ machines.
C HAPT ER 1 / Set ting up t he Ser ve r
n
27
Using Administrator to set security
Use the Administrator program to control access security for RemoteWare programs at
the Server. Any user who has been granted rights can use Administrator.
Administrator runs while the Server is active or down. Each RemoteWare program has a
set of rights. Using Administrator, you can grant or deny Windows NT users or groups
access to any RemoteWare program, allowing them to perform specific functions. For
example, you could allow the Monitors user group rights to start the Report Manager
program, but only to view reports.
Note: You cannot modify any access permissions on the currently logged in user.
You do not have to exit Administrator in order to save changes. The next time a user
starts RemoteWare, the changes will take effect.
To start the Administrator:
In RemoteWare Menu, double-click the
main window appears.
Administrator icon. The Administrator
You may experience a delay as Administrator searches for other RemoteWare Servers
visible to your computer or for other NT domains in your network.
Note: For efficient administration, you should assign rights to Local or Domain
Groups, not to Users.
28
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Enabling users or groups
When you enable a user or group, you allow them access to RemoteWare programs. The
user or group you enable appears in full color in left pane of the Administrator window.
To enable users or groups:
1
Expand the RemoteWare Server tree in the left pane by
clicking the plus sign to the left of the Server.
2
Highlight a dimmed user from the Local or Domain Users
folder, or a dimmed group from the Local or Domain
Groups folder. You cannot activate an already enabled
item.
3
Click
Grant on the toolbar. One of the following
results occurs:
4
5
•
If you have granted rights to programs to that user or
group in the past, then those programs and rights are
reactivated.
•
If you have not previously granted rights to a
selected user or group, then the Add Application
dialog box appears.
In the Add Application dialog box, choose one or
more of the programs in the list box.
•
To select adjacent items, press and hold [Shift]
(for contiguous items) while clicking the
programs you want to add.
•
To select non-adjacent items, press and hold
[Ctrl] while clicking the programs you want to
add.
When you are finished selecting applications, click
OK.
For information on assigning rights for the program(s), see “Granting rights” on
page 29.
C HAPT ER 1 / Set ting up t he Ser ve r
29
Disabling users or groups
By disabling users or groups, you prevent them from accessing RemoteWare programs.
The users or groups you disable appear dimmed in left pane of the Administrator
window.
To disable a user or group:
1
Select an enabled user from the Users or Domain Users folder, or select an enabled
group from the Local Groups or Domain Groups folder. You cannot disable Servers,
folders, or previously disabled entries.
2
Choose one of the following:
•
To disable a selection but keep any currently assigned rights, click
Deny on the toolbar. The selection and rights are disabled.
•
Deny
To disable a selection and delete any assigned rights, click the
and Clear on the toolbar. The selection is disabled and all rights for that user or
group are deleted.
Granting rights
When you grant rights for RemoteWare programs to any enabled user or local group,
you determine what actions each user or group can perform within the program.
To grant rights to a user or group:
1
Highlight the user or group whose program rights you want to modify. If your
selection is disabled, see “Enabling users or groups” on page 28.
2
Complete one of the following steps:
3
•
To assign programs to a user or group for the first time, or to add rights for
Add Application
programs not in the current list for a user or group, click
on the toolbar. The Add Application dialog box appears. Go to Step 3.
•
To re-enable rights to programs for users or groups, click the plus sign to
expand the tree in the left pane and view the user or group’s current rights for
each program. Click the check boxes to the left of each entry to turn rights on
and off.
In the Add Application dialog box, select one or more programs and click OK. By
default, the user or group gains complete access to the chosen programs.
30
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
4
Click the
plus sign to view the user or group’s rights for each program. If you do
not want the user or group to have complete access for a program, then click the
check box to the left of the function you want to disable.
Note: When you deny users or groups access to all functions in a program, they still
have read-only access to the program.
Denying rights
You may deny rights to users or groups in several ways:
By deselecting a specific check box in a program’s rights list. The rights you
disable are not available to the users or groups the next time they start the program.
1
Select a user or group. The program list appears in the right pane.
2
Expand the rights for a program by clicking the
program.
3
Clear the check boxes for specific functions you want to deny.
plus sign to the left of a
By removing the program from the user’s or group’s program list. When you
remove a program, the specified user or group will have no access to the program.
1
Select a user or group. The program list appears in the right pane.
2
Highlight the program you want to remove.
3
Click
Remove Application on the toolbar. The program and its rights no
longer appear in the list, and the user or group no longer has access to the program.
By disabling the user or group. When you disable the user or a group, the user or
group can no longer access any RemoteWare programs. For more information, see
“Disabling users or groups” on page 29.
C HAPT ER 1 / Set ting up t he Ser ve r
n
31
Changing system-wide settings
You control many Server, Workstation, or Cluster functions from the Settings and
Cluster pages in the Server Profile. To change other system-wide settings, you can use
Control Panel. Table 3, “Changing system settings,” explains briefly how to change
settings. The next sections describe in more detail how to display or change these
settings.
Table 3. Changing system settings
To
Do this
Change the System Name
On the Settings page, type a new name in the name field. The
new name appears when you reboot the computer containing the
data drive.
Change the local Server
name
From Windows’ Network control panel, select the Changes page
and enter the new computer name.
Change the date and time
For a Standalone Server, use the Date/Time button on the
Settings page in Server Profile. Note: You must suspend your
Scheduler before changing the values, or sessions may run at
wrong times or not at all.
For Clustered Servers, use the net time command line
function on a common time base.
Change the time zone
From Windows’ Date/Time control panel, change the time zone
on the computer that serves as the time base.
Change date and time format
From Windows’ Regional Settings control panel, set the ordering,
separators, and formatting for the date and time.
Note: RemoteWare Servers always use the 24-hour clock for
scheduling and setting times.
Control how the Server
maintains connections
On the Settings page, select how you want to maintain
connections. For more information, see “Controlling how the
Server maintains connections” on page 38.
Control how work objects
execute
On the Settings page, select the For all Clients, Enable check box
for ESD or Applications.
Enable compression
On the Settings page, select the For all Clients, Enable check box
for Compression, then enter specific file extensions.
Change Server’s
communication type
On the Cluster page, select either the Inbound or Inbound/
Outbound Command menu items.
Turn off a Clustered Server
On the Cluster page, select Disable on the Command menu. One
Server must be enabled and running at all times.
32
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Changing the System Name
The System Name identifies all Servers in a standalone or Clustered system. It is related
to the Serial Number and is different from the individual Server Name. A RemoteWare
Client refers to the System Name during a session.
To change the System Name:
1
In Server Profile, click the Settings tab. The Settings page appears.
2
Highlight any existing text in the Name field.
3
Enter up to 31 characters for the new System Name.
C HAPT ER 1 / Set ting up t he Ser ve r
33
Changing the local Server name
The local Server name appears on the Settings, Cluster, and Resources pages of the
Server Profile, as well as in other Server programs. The Server Profile Cluster page lists
all local Server names along with RemoteWare Workstations. This name always
corresponds to the Windows NT or Windows 2000 computer name and is updated each
time you restart the local RemoteWare Server.
Note: If RemoteWare Servers in a Cluster use a different username/password to log
on as a Windows NT service for the RemoteWare Server service, the Server will
report a “Down” state in the Administrator, Server Profile, and Network Status
programs. You must use the same user name and password for the RemoteWare
service on all computers.
To change the local Server name on a Server:
1
In the Windows Control Panel, double click the
2
On the Identification page, click Change.
3
Edit or type a new name in the Computer Name field.
4
Click OK.
5
Network icon.
Click OK to save the new Computer Name. The Local Server Name changes the
next time you start the RemoteWare Server. For more information on how to stop
the Server, see “Starting and stopping the Server” on page 20.
34
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Setting the date and time on a standalone Server
Note: Never modify the date or time on a Server with an active Scheduler. Doing so
may cause pending sessions to execute at the wrong time, or not at all. Suspend
the Scheduler from the Schedule Manager program.
Depending on how you have configured your computer network and its RemoteWare
Servers, you can set a Server’s date and time:
•
Manually from the Server Profile. Enter the time and date on the Settings page.
•
Manually from the Date/Time control panel. Use Windows Control Panel to
set the date and time.
•
Manually from another computer. Type net time [\\ComputerName |
/domain[:DomainName]] /set from a Windows command prompt to
synchronize the time with one time server or another computer. For example, to
synchronize the Server with a computer named CHRONOS, type net time
\\CHRONOS /set.
•
Automatically from the computer. Schedule a net time command to execute
at a certain time each day using the Windows at command.
•
Automatically from the Server. Create a Process Only session that contains an
EXECUTE event for the net time command.
C HAPT ER 1 / S ett ing up t he Ser ve r
35
Changing the date and time on Clustered Servers
Note: The system clocks on all Clustered Servers must be identical. Time drifts of even
a few seconds can cause serious load and schedule imbalances. The Server with
the earliest time tries to execute all of the sessions that become active, rather
than balancing the load across all Servers in the Cluster.
Do not set the system clocks on Clustered Servers from the Settings page. Use the net
time command to reference and set the date and time from a single source. To
manually or automatically synchronize clocks in a Cluster:
•
Manually using the net time command. Type the appropriate command from a
command prompt. For more information, see the Command Reference in
Windows Help. Use the same computer for the time reference. The time may be
incorrect by a few seconds as long as all the system clocks on the Server computers
are identical. For an example of the net time command, see “Setting the date
and time on a standalone Server” on page 34.
•
Automatically using the at command. Use the at command to schedule the
execution of a net time operation periodically during the day. See the Command
Reference in Windows Help for more information on the at command.
Changing the time zone
The time zone is a component of the date and time. The Server uses the time zone to
compute the time offset between itself and Clients during a communication session.
The correct time zone is especially important when the Server is instructed to adjust the
Client’s system clock using the SET TIME event in a work object. Depending on your
network and your RemoteWare configuration, use the appropriate method listed below:
•
For a standalone Server, use the Date/Time control panel. Change the time
zone at the Server, or on the computer you use for your time reference.
•
For a Cluster, change the Date/Time control panel on the computer that
serves as a time reference. All Servers adjust time zone after the next net
time command occurs.
Setting the Server’s time zone is especially important if you have Clients across several
time zones and you plan to use the Set Client Time work object to automatically set the
time on those Clients. If you have not set the time zone at the Server correctly, all your
Client times will be set incorrectly.
Note: If the Client changes time zones without updating the time zone setting in
Client Profile, the Client will receive a full system ESD.
36
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Maintain client’s date/time stamps on sent files
Add this registry key in Client Profile to maintain the date/time stamps of the files sent
by clients located in different time zones.
To maintain Client date/time stamp:
1
Under \\HKEY_LOCAL_MACHINE\Software\RemoteWare\Server, create a
New Key called TZIgnore. No data value is to be set for this key.
Note: After this TZIgnore key is set, the existing Win32 client types will get their client
files re-sent on the first connection.
Maintain Server date/time stamp
Add this registry key in Client Profile to maintain the Server date/time stamp, instead of
changing to the one reported by the Client.
To maintain the Server date/time:
1
Under \\HKEY_LOCAL_MACHINE\Software\RemoteWare\Server, create a
New Key called, Use Server TimeZone. No data value is to be set for this key.
If this new key is present, when you change the time zone on the client and
connect, the RemoteWare server retains its original time zone and won't be
changed to match the time zone on the RemoteWare client.
Time zones that do not allow daylight savings time
ESD may be delivered twice to Clients when the RemoteWare Server computer uses a
time zone that does not allow Daylight Savings Time (such as “GMT 04:00 Caracas, La
Paz”).
To verify whether the current time zone allows daylight savings changes:
1
From Control Panel, choose Date/Time. The Date/Time Properties dialog displays.
2
Click the Time Zone tab.
3
Verify whether the Automatically adjust clock for daylight savings changes
check box displays. Time zones that do not allow daylight savings do not display this
check box.
To avoid resending ESD:
1
On the Start menu, point to Settings and select Control Panel.
2
Double-click the System icon in the Control Panel window. The System Properties
dialog box appears.
3
NT: Click the Environments tab.
Windows 2000: Click the Advanced tab and choose Environment Variables.
C HAPT ER 1 / Set ting up t he Ser ve r
4
37
Add a System variable of TZ in the form:
TZ=xxxttt
where xxx is any three letters indicating the time zone code, and ttt is the time
difference between GMT and local time (available from the Date/Time control
panel).
For example, the setting for Indiana (East) would be TZ=EST-5.
Changing the date and time format
Regional Settings in the Windows Control Panel controls the date and time formats in
all RemoteWare programs. From Regional Settings, you can change the appearance of
the information to match a local or personal standard.
Although most RemoteWare programs display time in whatever format you choose, the
Server still uses and displays a 24-hour clock for all scheduling operations. You must
specify time in the correct format when scheduling sessions. For example, to schedule a
session at 4:23 PM, enter the time as 16:23. For more information, see “Setting the
session schedule” on page 165.
When you make changes to Regional Settings in the Windows Control Panel, they
appear on the RemoteWare Server when you restart the service.
38
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Controlling how the Server maintains connections
Use the Settings page in Server Profile to instruct the Server when to disconnect from a
Client in the event that another session is waiting to contact the same Client.
To determine how the Server maintains connections:
1
In RemoteWare Menu, double-click Server Profile.
2
Click the Settings tab. The Settings page appears.
3
In the Maintain Connection field, select one of the following options:
•
Select Always to maintain the connection if another session is ready to execute.
•
Select Never to break the connection in every situation.
•
Select For sessions with priority greater than or equal to n to set a
threshold for maintaining a connection.
C HAPT ER 1 / Set ting up t he Ser ve r
39
Controlling work object execution
On the Settings page in Server Profile, use the For all Clients, enable options to
determine work object and compression behavior for all Clients in a RemoteWare
system. These global settings overwrite any other options you set in the system. You can
also apply most of these options to individual Clients and events.
To enable or disable global settings:
1
Select or clear the ESD check box to prevent all System
and User ESD work objects from executing.
2
Select or clear the Applications check box. All
Application work objects defined in the Work Object
Editor are normally executed unless disabled at the Client
or other level. Disabling the Applications check box
prevents any Application work objects from executing,
including those which service Clients.
Compression by file extension
Use the Compression and Extensions not to Compress options to control
compression across the entire RemoteWare system for data sent to or received from the
Client.
To allow data compression:
1
Select the Compression check box.
Note: Selecting this option overrides compression settings at the event level.
2
If you know that files with specific extensions do not compress well, enter these file
extensions in the Extensions Not To Compress area (without the “.” separator).
For example, to avoid compressing files with names like myprog.exe, type “exe” in
the field (not “.exe”). Files that do not compress well include executables (EXE)
and already compressed files (ZIP).
40
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
3
Click Add. The file extensions appear in alphabetical order in the box on the right.
4
Repeat Steps 1 and 2 to add more file extensions.
To remove an extension from the Extensions Not To Compress list:
1
Highlight the extension you want to remove in the list on the right.
2
Click Delete.
3
Repeat Steps 1 and 2 for other extensions you want to delete.
Changing the way the Server communicates
Use the Server Profile Cluster page to specify the RemoteWare Server’s
communications type:
Inbound only. An inbound only Server is limited to receiving calls from Clients and
cannot schedule outbound sessions. However, it performs faster than the default
inbound/outbound Server.
Inbound/Outbound. The Server can both initiate calls to and receive calls from the
Client. This is the default setting for the Server.
Note: You should set up RemoteWare Clusters to have as few inbound/outbound
Servers as possible.
To change the communications type:
1
In Server Profile, click the Cluster tab.
2
Highlight the Server name on the Cluster page.
3
On the Command menu, select Inbound Only or Inbound/Outbound. A
message window instructs you to reboot.
4
Restart the RemoteWare Server service to complete the change.
C HAPT ER 1 / Set ting up t he Ser ve r
41
n Setting alarm thresholds
Use the Alarms page to specify when the system should notify you about specific
occurrences, such as when:
•
The Server’s data disk drive reaches a threshold percentage full.
•
The Client’s default disk reaches a percentage of its capacity.
•
A port receives a specified number of consecutive modem and/or no dial tone errors
and is subsequently disabled.
To display the Alarms page:
1
In RemoteWare Menu, double-click the
Profile window appears.
Server Profile icon. The Server
2
Click the Alarms tab. The Alarms page appears.
3
Use the spin buttons next to the threshold values to select the appropriate
notification level. When alarms occur, they appear in the Network Status program.
42
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Setting logging options
Use the Logging page to limit the amount of information recorded by the RemoteWare
Servers in your system. This option may increase performance, eliminate unnecessary
information, reduce the size of the logs, and reduce the amount of log rollover.
To display the System Logging Options page:
1
In the RemoteWare Menu, double-click the
Server Profile icon.
2
Click the Logging tab. The Logging page appears.
3
Click the check box that corresponds to the level of logging performed for the
entire Server network. For more information about the impact of the choices, see
“Logging page” in the RemoteWare Server Reference Manual.
C HAPT ER 1 / Set ting up t he Ser ve r
n
43
Removing a Cluster or Workstation
From the Cluster page in Server Profile, you can delete remote Servers or
Workstations. Delete a Server or Workstation if:
•
it no longer exists on that computer
•
it is being moved to another computer
•
it is being reinstalled or updated with new software.
Verify that the entry you are deleting is no longer processing sessions.
Note: Deleting a RemoteWare Workstation or Cluster does not remove the files or
data from the remote system. If necessary, run the uninstall utility on that
machine to remove files from the deleted system.
To delete a RemoteWare Workstation or Server:
1
In Server Profile, click the Cluster tab.
2
Highlight the Server or Workstation name in the Cluster list box.
3
On the Command menu, select Disable.
4
On the File menu, select Delete. A message window appears asking if you want to
delete the Server or Workstation.
5
Click Yes to delete the item. The deleted RemoteWare Server or Workstation will
no longer be visible to this RemoteWare Server.
44
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Setting up an Execution Server
By copying files from your RemoteWare directory onto another machine running
Windows NT/2000/XP on the same local area network, you can set up an Execution
Server that will off-load processes from an existing RemoteWare Server. By doing this,
you can dedicate your RemoteWare Server to communicating with Clients.
An Execution Server recognizes the EXEcute and NOTIFY events it receives from the
RemoteWare Server.
To install an Execution Server on an NT/2000/XP machine:
From the \system directory on your RemoteWare Server, copy the following files:
1
n
When running the
RemoteWare Server
Service Account set
to interact with
Desktop, the
exe_serv Execution
Server program
opens an MS-DOS
window when
executing a
background process.
•
exe_serv.exe
•
rwsnls.dll
•
queues.dll
•
OS2map.dll
2
Check the \Winnt\System32 directory on the machine that will run the Execution
Server to verify you have the file msvcrt40.dll. If this file does not appear on the
Execution Server machine, copy it from the RemoteWare Server machine and paste
it into the \Winnt\System32 directory on the Execution Server.
3
On the Execution Server machine, create a folder called System. Place the files you
copied from the RemoteWare Server into this directory.
From the command line, type start exe_serv.
4
By default, the maximum number of processes this machine can execute is set to 2. The
queue name appears as /queues/exe_serv.que, and the pipe name appears as
\\.\pipe\exe_serv.pip.
To change the default settings on your Execution Server, use the commands in Table 4,
“Execution Server commands”.
Table 4. Execution Server commands
Command
Option
Action
Example
-P
# of Processes
Sets the number
of processes you
can execute at
one time
-P4
-PN
Pipe Name
Changes the
pipe name
-PN\\<machinename>\pipe\<pipe name>
-QN
Queue Name
Changes the
queue name
-QN/queues/<name of queue>
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
2
2RemoteWare
Setting Up Communication Resources
Before you define your Clients and create your installation kits, you should set up your
communications resources at the Server.
This chapter includes:
• Create and edit dial scripts
• Add and update long distance services
• Define and modify asynchronous, NetBIOS, and TCP/IP resources
• Work with modem types
• Add and update protocol services
46
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Using dial scripts
Use Dial scripts, a set of dial and text instructions, to establish an asynchronous
connection with a communications system, such as a long distance service or network
provider. The Dial Scripts page in Server Profile lists all existing dial scripts.
To display the Dial Scripts page:
1
In RemoteWare Menu, double-click the
2
Click the Dial Scripts tab.
Server Profile icon.
You should assign each dial script to a long distance service. Then you can assign the
long distance service to a Server resource on the Resources page or a Client on the
Client Profile Client page.
C HAPT ER 2 / Se tt in g Up Com m un ic at ion Re sou rce s
47
Creating a new dial script
To create a new dial script:
1
In Server Profile, click the Dial Scripts tab.
2
Click
3
Enter a New Dial Script name (from 1 to 8 characters) for the dial script.
4
Click OK.
5
Enter dial script commands. For more information, see “Editing dial scripts” on
page 48.
New on the toolbar.
48
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Editing dial scripts
The Dial Script Editor works like an ordinary text editor. Use the Dial Script Editor to
enter and edit dial script commands.
Note: You can use any text editor to create dial scripts and save the scripts in the
\sysfiles\scripts directory. Dial scripts you create with a text editor must end with
the .ds file extension and must be compiled with the Dial Script Editor at a later
time.
To edit a dial script:
1
In Server Profile, click the Dial Scripts tab.
2
To open the Dial Script Editor, complete one of the following:
•
To create a new script, see “Creating a new dial script” on page 47.
•
To edit an existing script, double-click the script entry on the Dial Scripts page.
The Dial Script Editor appears.
3
Type the dial script commands. Use the “Dial Scripts page” section in the
RemoteWare Server Reference Manual for a list of valid commands. Click Undo to
reverse your last action, if needed.
4
When you have completed the script, either:
•
Click Save to keep your additions or changes without compiling the script. For
more information, see “Saving a dial script” on page 49.
•
Click Compile to verify the script and convert it into a form RemoteWare can
use. Use this option when you have completed the script. For more information,
see “Compiling a dial script” on page 49.
C HAPT ER 2 / Se tt in g Up Com m un ic at ion Re sou rce s
49
Saving a dial script
Saving a dial script writes the current dial script to a file name with a .ds file extension,
as in the example dialnow.ds. Dial scripts are saved in the \sysfiles\scripts directory but
you cannot use them in a Long Distance resource until you compile them.
Save your dial scripts to keep your current changes, when:
•
You do not have the time to finish the script.
•
You cannot debug an error at this time.
•
You do not want to use the script at this time.
To save a dial script:
1
Click Save in the Dial Script Editor.
Compiling a dial script
When you compile a Dial Script, it generates a valid version of the Dial Script that the
RemoteWare system can use. Compiled Dial Scripts are saved in the \sysfiles\scripts
directory with a .cds file extension. Dial Scripts you have not compiled have an asterisk
“*” in the Last Compiled column of the Dial Scripts list. Uncompiled scripts cannot be
used by a Server or Client.
To compile a dial script:
1
Click Compile in the Dial Script Editor. A message appears stating that compiling
will automatically save the script.
2
Select Yes to continue or No to cancel.
A message appears at the bottom of the Dial Script Editor window, indicating whether
the script was compiled successfully or resulted in an error. If a previously compiled
version of the script exists, then RemoteWare will keep the previous version until you
successfully recompile it.
50
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Changing dial script font options
You can customize the way your dial scripts appear.
To change the dial script font:
1
Click the Font button on the Dial Script Editor. The Font dialog box appears.
2
Choose the Font, Style, Size, Effects, and Color. As you make selections, a sample
of the selected font appears in the Sample area of the dialog box.
3
Select OK to return to the Dial Script Editor.
C HAPT ER 2 / Se tt in g Up C om m un ic ation Res our ce s
n
51
Using long distance services
Use the Long Distance page in Server Profile to access and define the services offered
by regional carriers, packet networks, and national long distance carriers. This page lists
and defines the access codes or procedures for up to 128 services.
To display the Long Distance page:
1
In RemoteWare Menu, double-click
Server Profile.
2
Click the Long Distance tab. The Long Distance property page appears.
The Long Distance page lists long distance services for the RemoteWare system. You
will see a sample service called “Normal,” which was defined during installation.
52
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Adding a long distance service
If the long distance service you use is not listed on the Long Distance page, you can add
it to the list.
To add a long distance service:
1
At the Long Distance page in the Server Profile, click
Long Distance Service Detail dialog box appears.
2
Enter a name for the service in the Name field.
3
Select the Enable this Service check box to make this service available as a Server
or Client resource when you finish defining it.
4
Select one of these options:
•
New on the toolbar. The
Dial String. Select this when the service adds a simple prefix or suffix to the
phone number. The <Phone # > variable is a placeholder for inserting the
Client phone number and is already in this field. Insert any special commands
(such as pauses) for dialing before or after this variable.
Note: Do not enter the actual phone number where <Phone # > is located. The Server
automatically inserts the Client’s phone number.
A complete dial string looks like this: 9, 5551234<phone#>,,780494944. If you
are not sure how to set up the dial string, make the call yourself and write down
exactly what you dial and how long you wait for signals or dial tones. Use this
information to develop the dial string.
C HAPT ER 2 / Se tt in g Up C om m un ic ation Res our ce s
•
5
53
Dial Script. Select this when the service requires more than one step, such as a
connection with a public network requiring a user name and password. Before
using this choice, verify that a dial script exists that meets your needs. For more
information, see “Using dial scripts” on page 46. After selecting the Dial
Script option button, highlight the dial script name in the field to the right of
the button. If “The selected dial script needs to be compiled” message appears,
click Edit and see “Compiling a dial script” on page 49.
Click OK when you are finished. The service appears on the Long Distance page.
Note: If you did not select the Enable this Service check box in the Long Distance
Service Detail dialog box, you must enable the service before assigning it to
ports or Clients.
Enabling and disabling a long distance service
Use the Enable and Disable options on the Command menu to change the availability
of a long distance service. You must enable a long distance service before you can assign
it to a port or Client. When you disable a long distance service, you prevent it from
being assigned to a port or Client. You should disable a service when you change its
definition.
n
Tip: You can also
highlight the item
and right-click select
Enable or Disable
from the shortcut
menu.
•
To enable a long distance service, highlight the item on the Long Distance page
list and click
Enable.
•
To disable a long distance service, highlight the item on the Long Distance page
list and click
Disable.
Copying a long distance service
Copy a long distance service if you know that more than one Client will use the same
service to connect to the Server. You can also edit the service by making a copy and then
replacing the original with the copy.
To copy a long distance service:
1
On Long Distance page in Server Profile, select a service and click
the toolbar. The Long Distance Service Detail dialog box appears.
Copy on
2
Enter a name for the new dial script in the Name field.
3
Edit the service type if necessary, then click OK to save changes and return to the
list of long distance services.
54
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Deleting a long distance service
When you delete a long distance service, you erase the definition, including the dial
string (but not a dial script). As an alternative, you can disable the service so that it
cannot be used by a port or Client.
Note: You cannot delete a long distance service that you have assigned to a Client. You
must first unassign the service from all Clients. Assign and unassign long
distance services to each Client on the Server page in Client Profile.
To delete a long distance service:
1
Verify the service is not assigned to a Client. Generate a Client Detail Report in the
Report Manager program and filter on Server Info. For more information, see
“Using Report Manager” on page 240.
2
On the Long Distance page in Server Profile, select the service you want to delete.
3
On the File menu, click Delete.
4
Click OK to confirm your choice. Server Profile deletes the service from the Long
Distance page.
Updating a long distance service
You can make changes to any long distance service.
To update a long distance service:
1
On the Long Distance page in Server Profile, select the service you want to change.
2
Click
3
On the File menu, click Update.
4
Enter the changes in the Long Distance Service Detail dialog box.
5
Click OK. All changes take effect after you close the Long Distance Service Detail
dialog box and enable the service.
6
Select the entry again and click
distance service.
Disable on the toolbar to disable the service before you make changes.
Enable on the toolbar to re-enable the long
C HAPTE R 2 / Se ttin g Up C om m unica tion Res our ce s
n
55
Limiting outbound connections
You can limit the number of outbound connections that occur within a certain period of
time. You can specify limits for one or more resource types. When you limit the number
of connections, the Server initiates only the number of sessions you specify; all other
sessions of the same type are blocked, even if resources are available.
Note: You cannot limit Process Only sessions.
To limit an outbound connection:
1
In Server Profile, click the Limit Outbound tab.
2
Select the Limit Outbound Connections check box.
3
Select the check box next to each resource type for which you want to limit
connections.
4
Use the Limit connections to n new sessions per session spin boxes to specify
the number of outbound sessions for each resource type.
Note: You must restart the Server in order for these changes to take effect.
56
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Activating Server resources
Use the Network Groups and Resources pages in Server Profile to define and activate
communication resources (such as a modem on port COM1) so the Server can complete
sessions with Clients. A resource is a specific process or physical connection the
RemoteWare Server uses to communicate with Clients.
Creating a Network Group
When you create a Network Group, you group selected Clients together in a single set.
Then you associate these Network Groups with Port Groups. Network Groups and Port
Groups work together to manage the number and priority of outbound connections
over individual IP ports.
When you create a Network Group, it is stored in a file called netgrps.dat in the Server’s
\sysfiles\<machinename> directory. It creates one file per Server, so if you have a
Clustered Server, each Cluster may have its own Network Groups. You can have a
maximum of 64 groups per Server.
To create a Network Group:
1
In Server Profile, click the Network Groups tab. The Network Groups property
page appears.
C HAPT ER 2 / Se tt in g Up C om m un ic ation Res our ce s
n
Tip: Right-click
any Network Group
to access the shortcut
menu commands.
57
2
Click
3
Enter the group’s name in the Name field.
4
The group’s status defaults to enabled. Click
Disable to disable the group. You
will have to enable the group again before you initiate a session.
Click OK. The group you created appears in the list box on the Network Groups
property page.
5
New on the toolbar. The Network Group Details dialog box appears.
To delete a Network Group:
1
On the Network Groups page in Server Profile, select the group you want to delete.
2
On the File menu, select Delete. The Group you selected is deleted from the
Network Groups list. The group number will be available for the next group you
create.
Note: You cannot delete the Default Network Group.
58
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Displaying current resources
Use the Server Profile Resources property page to add or change resource definitions.
To display the Resources page:
1
In RemoteWare menu, double-click
Server Profile.
2
Click the Resources tab. The Resources property page appears in Server Profile.
The Resources page lists five resources: NetBIOS, Process Only, TCP/IP, SPX, and
Async (COM ports) by default. See “Resources page” in the RemoteWare Server
Reference Manual for more details about this page.
C HAPT ER 2 / Se tt in g Up C om m un ic ation Res our ce s
59
Adding asynchronous resources
Use the Resources page to define the asynchronous resources that represent the serial
ports. Asynchronous (async) resources typically use serial ports and modems to
communicate with Clients. A RemoteWare Server using more than one asynchronous
resource also relies upon a multichannel communications device to manage the
multiple serial ports in an efficient manner.
To add a port definition:
1
On the Resources page in Server Profile, click
New on the toolbar.
The Port Number field displays the next unused port number.
2
To change the port number, select from the Port Number drop-down list box.
Only unused port numbers appear in the list.
Note: The port number is different from the communications serial port number and
the device number.
The Device field shows the next available hardware serial port (such as COM1 and
COM2). The configuration of your Windows hardware and multichannel
communications boards determines if these ports are available to the Server. An
error appears in the Server Log if you select a device that does not exist.
3
To change the device, select the device number from the Device drop-down list
box.
The Max Data Rate field shows a default value for the selected modem.
60
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
4
Select the maximum data rate for this modem from the Max Data Rate drop-down
list box.
Note: For a Direct Connect asynchronous connection, the Max Data Rate setting for
the Server’s asynchronous resource must match the Data Rate of the
asynchronous resource defined for the Client.
The Inbound Data Rate applies only to Server ports accepting inbound calls. The
majority of Clients should use this rate when they connect to the port. See the
RemoteWare Server Reference Manual for more information about inbound ports.
Note: If you are defining a direct connect Client, the Inbound Data Rate must match
the Max Data Rate set in Step 4.
5
Under Usage types, select the Inbound and/or Outbound check box(es) for this
resource.
6
Select a number from the Port Priority drop-down list box.
Zero (0) is the lowest priority and nine (9) is the highest. By selecting a priority
number, you reserve some ports for only high-priority sessions.
7
Click the Modem Type button to select a different modem type.
8
Select a modem definition. To define a direct connect Client (a Client connected
directly to the Server via a null modem cable), select Direct Connect as the modem
type.
9
Click OK.
If you selected Direct Connect as your modem type, the Select Clients dialog box
appears. If you did not select Direct Connect as your modem type, go to Step 11.
C HAPT ER 2 / Se tt in g Up Com m un ic at ion Re sou rce s
10
61
Select a Client name from the list.
Note: If you have not defined a Client, select the SAMPLE Client and click OK.
Return to this page after you have defined your Clients. For more information,
see “Adding a Client definition” on page 82.
11
In the Port Phone Number area, type the telephone number of the phone line
associated with this port.
A Client with inbound capabilities can use this number to call the RemoteWare
Server. If a Direct Connect Client is using this port, this field is disabled.
Note: The phone number entered appears as a choice on the Client page in Client
Profile.
12
In the Long Distance Service area, assign one or more long distance services to
the port. This field is disabled if the port is assigned to a Direct Connect Client.
The Defined list on the right lists active services from the Long Distance page.
Select the services to assign to this port and click Assign. These services appear in
the Assigned to Port list on the left. The list on the left displays the services
available at this port.
When you assign a long distance service to this resource, the port is available to
place an outbound call to a RemoteWare Client with the same resource assigned to
it.
13
Select the Enable Port check box to make the port available for communication.
14
Click OK to accept the resource definition.
The Resources page displays the new definition. Repeat these steps for each port
you define, or use the Copy command if port definitions share common attributes.
For more information, see “Copying an asynchronous resource” on page 62.
62
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Editing asynchronous resources
Before you modify a resource definition, disable the port. A disabled port prevents
anyone from using the resource until after you have made your changes.
To disable a port, make changes, and enable the port:
1
On the Resources page in the Server Profile, highlight the port you want to change
and click
Disable.
2
On the File menu, click Update. The Async Resource Detail dialog box appears.
3
Make desired changes to any fields in the Async Resource Detail dialog box, then
click OK.
4
While the port is highlighted, click
communications.
Enable to make the port available for
Copying an asynchronous resource
Copy an asynchronous resource when you want to change an existing resource or to save
time when you are defining similar asynchronous resources.
To copy an asynchronous resource:
1
On the Resources page in the Server Profile, select the port you want to copy.
2
Click
3
On the Async Resource Detail dialog box, make your changes, then click OK.
Copy. The Async Resource dialog box appears.
The new resource appears on the Resources page.
Disabling an asynchronous resource
Disable the port to make changes to the port definition, or to temporarily prevent it
from being used.
To disable a port definition:
n
Tip: You can also
highlight the port
name and right-click
to display its shortcut
menu, then select
Disable.
1
On the Resources page in Server Profile, select the port you want to disable.
2
Click
Disable.
C HAPT ER 2 / Se tt in g Up Com m un ic at ion Re sou rce s
63
Deleting an asynchronous resource
Delete an asynchronous resource to erase all information for that port. Rather than
deleting a definition, you may wish to disable it so it cannot be used. For information on
disabling a port, see “Disabling an asynchronous resource” on page 62.
To delete a port definition:
1
On the Resources page in the Server Profile, select the port you want to delete and
click
Delete.
2
At the “Are you sure?” prompt, click Yes to delete the port definition.
Defining NetBIOS resources
You can use NetBIOS as your main resource for a LAN transport for Ethernet, token
rings, or NT configurations.
To define a NetBIOS resource:
1
n
Due to
performance issues,
we recommend you
do not use the
NetBIOS resource
during Remote
Control sessions or
when connecting to
Windows 3.1
Clients.
2
3
In Server Profile, click the Resources tab.
Double-click NetBIOS in the list of resources.
Select the Enable resource check box to enable NetBIOS.
4
Use the Number of Resources spin box, to select the number of resources
allocated to NetBIOS.
5
Click Add Port Group to assign a Network Group to this resource.
64
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
6
Enter a port group name and click OK.
7
In the Usage field, select the Inbound and/or Outbound check box(es) to indicate
whether the Client and/or Server initiates the connection. This usage is from the
RemoteWare Server’s point of view and affects all resources of this type.
Note: Network/Port Grouping is not valid for Inbound only sessions.
8
Use the Number of Ports spin box to select the number of ports to use for this
resource.
9
Use the Port Priority spin box to set the priority level for this resource.
10
Click OK.
The number of resources you defined appears in parentheses next to NetBIOS on
the Resources page.
C HAPT ER 2 / Se tt in g Up C om m un ic ation Res our ce s
65
Defining process only resources
Use process only resources for sessions that run only at the Server.
To define a process only resource:
1
In Server Profile, click the Resources tab.
2
Double-click Process Only on the list of displayed resources.
3
Select the Enable resource check box to enable Process Only sessions.
4
Use the Number of Resources spin box to select the number of resources
dedicated to Process Only.
5
Click OK.
The number of resources defined appears in parentheses next to Process Only on
the Resources page.
66
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Defining SPX and TCP/IP resources
To define SPX or TCP/IP resources:
1
On the Server Profile Resources page, double-click SPX or TCP/IP on the list of
displayed resources. The SPX Detail or TCP/IP Detail dialog box appears.
2
Select the Enable resource check box to enable SPX or TCP/IP.
3
Use the Number of Resources spin box to select the number of allocated
resources that the Server has available to communicate with its Clients.
4
In the Server Address field, verify the address represents this Server.
Note: If you are using a Clustered Server, each Server can have a different address
available for Clients.
5
Click Add Port Group to assign a Network Group to the SPX or TCP/IP resource.
6
Enter a port group name and click OK.
C HAPT ER 2 / Se tt in g Up Com m un ic at ion Re sou rce s
7
67
Select the Inbound and/or Outbound check boxes to specify whether the Client
and/or Server can originate a connection. The direction is from the RemoteWare
Server’s point of view and affects all resources of this type.
Note: Network/Port Groups are not valid for Inbound only sessions.
8
Select a Network Group from the Available Network Groups list box.
9
Click
10
Use the Number of Ports spin box to select the number of ports to use for this
resource.
11
Use the Port Priority spin box to set the priority level for this Resource Group.
to add the Network Group to the Assigned Network Groups field.
Note: Port Priority ranges from 0 to 9.
12
Click OK to return to the TCP/IP or SPX Detail dialog box.
Click OK to return to the Resources page.
To copy an existing port group:
13
n
Tip: To access the
Copy, Delete,
Update, Enable, and
Disable commands,
select any resource
and right-click.
1
On the Resource page in Server Profile, select a TCP/IP group.
2
On the File menu, select Copy.
The Server assigns the next available number to the copy. All group definitions
remain the same.
68
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To update an existing port group:
1
Click the Resources tab, select the TCP/IP resource you want to update.
2
On the File menu, select Update.
3
Click Edit Port Group.
4
Make any changes to the group.
5
Click OK to return to the TCP/IP Detail dialog box.
To change Port Group Name:
1
Click the Resources tab.
2
Double-click the device you want to change.
3
Highlight a Group and click Edit Group button.
4
Enter a Group Name and click OK.
5
Click OK.
C HAPT ER 2 / Se tt in g Up Com m un ic at ion Re sou rce s
n
69
Working with modem types
The Modem Types page in Server Profile contains modem definitions used throughout
the RemoteWare system. Use this page to build custom modem definitions and modify
existing modem definitions.
Note: Use the Client system-defined modem option in the Client Profile program to
create a custom modem definition only after you have tried using one of the predefined modem selections or a definition provided by your RemoteWare
representative.
To create a new modem definition:
1
In RemoteWare Menu, double-click the
Server Profile icon.
2
Click the Modem Types tab. The Modem Types page appears.
3
At the Modem Types page in the Server Profile, click
Type dialog box appears.
New. The New Modem
70
n
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
RemoteWare 4.0
provides support for
European ISDN
through the RVS-COM
Modem definition.
This definition enables
RemoteWare to access
and drive CAPIcompliant ISDN cards.
4
Enter a new name for the modem type.
5
Click OK.
Editing modem definitions
You can edit existing modem types. .
Note: As a safety precaution, you should edit a copy of the existing modem definition.
For more information, see “Copying a modem type” on page 72.
To edit a modem definition:
1
On the Modem Types page, double-click the modem you want to edit. The Edit
Modem dialog box appears. For detailed information about each field on this page,
see the “Edit Modem dialog box” section in the RemoteWare Server Reference
Manual.
2
On the Command Strings property page, enter the appropriate information.
Note: To speed up the hardware disconnect process on the Server, leave the Modem
Escape and Modem Hangup fields blank to eliminate the few seconds required
to process the +++ and ATH! commands. This technique only works if dropping
DTR will hang up your modem. Do not assign this modem type to Clients. Use
this option only if you have a large number of short calls to place. Saving two or
three seconds on longer calls may not noticeably cut costs because telephone
billing methods often charge in larger increments.
C HAPT ER 2 / Se tt in g Up Com m un ic at ion Re sou rce s
3
71
Click the Result Codes tab.
For detailed information about each field on this page, see the “Edit Modem dialog
box” section in the RemoteWare Server Reference Manual.
4
Select a result code from the New Result Code spin box. The result code that
corresponds to each number appears in the Result Code/String list box.
5
Click the Settings tab.
For detailed information, see the “Edit Modem dialog box” section in the
RemoteWare Server Reference Manual.
72
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
6
From the Maximum Data Rate spin box, select a data rate.
7
From the Modem Delay spin box, select the number of milliseconds the Server
should wait before sending the modem a signal.
8
From the Modem Timeout spin box, select the number of seconds before the
Server time out of a connection.
9
Click OK to return to the Modem Types property page.
Copying a modem type
If you want to define a new modem type with parameters similar to an existing modem
type, copy the existing modem type, enter a new name, and change the parameters.
To copy an existing modem type:
1
On the Server Profile Modem Types page, select the modem type you want to copy.
2
Click
3
Enter a new name in the To Modem Type field.
4
Click OK to return to the Modem Types page.
Copy. The Copy Modem Type dialog box appears.
The new modem type appears in the modem type list. For information on editing
modem types, see “Editing modem definitions” on page 70.
To rename a modem type:
1
On the Server Profile Modem Types page, select the modem type you want to
rename
2
On the File menu, select Rename. The Rename Modem Type dialog box appears.
C HAPT ER 2 / Se tt in g Up Com m un ic at ion Re sou rce s
73
3
Enter a new name in the To Modem Type field.
4
Click OK to return to the Modem Types page. Server Profile renames the modem
type.
To delete a modem type:
Note: You cannot delete a modem type if you have not assigned it to a port or a Client.
1
On the Server Profile Modem Types page, select the modem type you want to
delete.
2
Click
Delete. An information message window appears asking if you are sure
about your choice.
3
Click Yes if you want to delete the modem type you selected. Server Profile
removes the entry and returns to the Modem Types page.
74
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Defining protocol services
Use the Protocol page in Server Profile to define the parameters for communicating
across transports by configuring packets and windows of data that will be transported
during a session. Use the default settings unless your resources require different
settings (such as different packet or window sizes). If you are sending large files, you
may need to adjust some of the parameters.
To display the Protocol Services page:
1
In RemoteWare Menu, double-click the
Server Profile icon.
2
Click the Protocol tab. The Protocol property page appears.
C HAPT ER 2 / Se tt in g Up C om m un ic ation Res our ce s
75
Adding a protocol
You may want to add or reconfigure a protocol to work better over poor quality phone
lines by decreasing packet and window sizes.
To add a protocol:
n
For ASYNC
resources, a packet
size of 1536 , a
window size of 8,
and compression
turned “Off” has
consistently provided
good throughput.
This should give a
throughput of about
77 kbps on a 56
kbps line.
1
At the Protocol page in the Server Profile, click
2
Enter a description for the protocol in the Description field.
3
Select a resource type from the Resource drop-down list box.
Select the Packet Size (in bytes) from the drop-down list box.
4
New.
The packet size determines how many bytes are included in one transmission
packet over any network. Check with your network vendor to determine if any
packet size requirements exist. The maximum value for the packet size depends on
the window size; multiplying the two values cannot exceed 16,384 (16K) bytes.
5
Select the Window Size from the drop-down list box. The window size may vary
depending on your network’s requirements and the condition of the lines. The
maximum value is partially determined by the packet size; see Step 4 for details.
6
Select a Retransmit Timeout (in seconds) from the drop-down list box. The
default is sufficient for most situations but depends on the network response. For
example, Clients linked by satellite may need this value increased, while very fast
networks may benefit from a smaller value.
7
Specify a Session Timeout from the drop-down list box. Change this value only if
there is a performance increase on fast networks, or when more time is needed for
slow networks to respond.
8
The Enable Compression option is selected by default. If you clear the check box,
the Server does not compress data when a file is transferred. If your modems have
built-in compression enabled, you may want to disable compression.
9
Click OK to save the settings.
76
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Copying a protocol
To copy a protocol:
1
From the Server Profile Protocol page, select the protocol you want to copy.
2
Click
3
Enter a description for the new protocol.
4
Change the settings for the new protocol definition. For more information, see
“Adding a Protocol” and “Protocol Service Detail” in the RemoteWare Server
Reference Manual.
Copy. The Protocol Service Detail dialog box appears.
Updating a protocol
To update a protocol:
1
On the Server Profile Protocol page, select the protocol you want to update.
2
On the File menu, select Update.
3
Make changes to the information fields.
4
Click OK to apply the changes.
Deleting a protocol
To delete a protocol:
1
On the Server Profile Protocol page, select the protocol you want to delete.
2
Click
Delete.
Note: You cannot delete a default protocol.
3
Click Yes to confirm your choice.
Server Profile deletes the protocol and returns to the Protocol Services page.
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
3
3RemoteWare
Defining and Updating Clients
Before the RemoteWare Server can communicate with remote or local Client
computers, you need to define each RemoteWare Client in the Client Profile program.
This chapter includes:
• Display list of defined Clients
• Add, change, and delete Client definitions
• Define Client group for Clients who use the same applications or have
similar requirements
78
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Displaying the Client List
Use the Client List property page to define and view Clients on the RemoteWare
Server.
To display the Client List page:
In RemoteWare Menu, double-click the
Client Profile icon.
If you are setting up Clients for the first time since you installed the Server, only a
Sample Client appears in the list.
C HAPTE R 3 / D e finin g a nd Up da tin g C lie n ts
79
Filtering the Client list
Use the Filter menu options to limit the number of Clients and Client groups to appear
on the Client List page. Once you apply a filter, the Filter menu indicates Filter-ON,
and the toolbar indicates which filter you have applied. You can apply more than one
filter at a time. You can save filters you have previously applied to a Client list. If you
have not applied any filters, the Filter menu indicates Filter-OFF.
The Client List filters are described below. For a detailed explanation of each filter, see
the RemoteWare Server Reference Manual.
Table 5. Client List filters
Filter
Toolbar
Button
Action
by Select Clients and Groups
Select Clients and Groups dialog Box
appears. Choose items from list and click
OK. The Client List page displays only
the filtered items.
by Members of Selected Groups
Select Client Groups dialog box appears.
Choose groups from list and click OK.
The Client List page displays only the
filtered groups.
by Enabled Clients
Filter applied immediately. The Client
List page displays only enabled Clients.
by Disabled Clients
Filter applied immediately. The Client
List page displays only disabled Clients.
by Registered Clients
Filter applied immediately. The Client
List page displays only registered
Clients.
by Unregistered Clients
Filter applied immediately. The Client
List page displays only unregistered
Clients.
by Clients Requiring Manual
Verification
Filter applied immediately. The Client
List page displays only Clients that
require manual verification.
80
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To apply one or more filters:
1
In Client Profile, click the Client List tab.
2
To apply the desired filter, click the appropriate filter button on the toolbar. The
Client List page displays the list of filtered items.
3
Repeat Step 2 for each filter you want to apply. The Client List page displays a list of
items with all filters you selected applied.
To remove one or more filters:
1
In Client Profile, click the Client List tab.
2
For each filter you want to remove, click the appropriate filter button on the
toolbar.
3
To remove all filters, click
Remove Filters. RemoteWare removes all filters
and all items appear in the list box.
To save a filter or combination of filters:
1
In Client Profile, click the Client List tab. You can only save an active filter or filter
combination. To verify the filter or filter combination is active, ensure the Filter
menu heading reads “Filter-ON.” To verify which filters are active, open the Filter
menu; a check mark appears next to any active filters.
2
On the Filter menu, select Write Filters. The Write Filter File dialog box appears.
3
Enter a file name and click Save.
C HAPTE R 3 / D e finin g a nd Up da tin g C lie n ts
81
To use a saved filter:
1
In Client Profile, click the Client List tab. You do not have to disable any current
active filters before you apply a saved filter.
2
On the Filter menu, select Read Filters. The Select Filter File dialog box appears.
3
Select the saved filter you want to apply to the list and click Open. The filter is
applied to the current Client List.
82
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Adding a Client definition
Each Client you add must contain this information:
•
A Client name
•
A Client password
•
A set of communications attributes (phone numbers or network addresses, and
other resource information).
If you need to add a number of similar Clients, create a standard Client definition, then
copy it and change only those fields that differ for each Client.
To add a client definition:
1
In Client Profile, click the Client List tab.
2
Click
3
Enter a Client name in the Name field.
New on the toolbar.
The Client name cannot be changed.
Note: Do not use “All” as a Client Group name, if you plan to use External
Configuration Files (ECFs) to build work objects, define scheduled sessions, or
configure Clients and Client groups.
4
Enter a description in the Description field.
5
Click OK.
C HAPTE R 3 / D e finin g a nd Up da tin g C lie n ts
83
Changing the general Client settings
After you create a new client, the Client Profile displays the General page. Use this page
to enter the general settings for the Client you created.
To enter general settings:
1
From the Type drop-down list box, select the Client’s operating system.
2
In the Description field, the information you entered at the Client List page
appears. You can change this information at any time.
3
In the Password field, enter a password.
Note: The Install Drive and Path field displays C:\ as the default drive letter. The Path
field displays the location where the Client directory resides. You cannot change
this value from the Server. It is defined by the Client during installation and is
sent back to the Server during the first communication session.
84
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
4
Click Timezone to configure the time zone offset setting for the Client. The Select
Client’s Universal Time Coordinate dialog box appears.
5
From the list box, select the Client’s location and time zone, then click OK. You
must specify this value to correctly set and retrieve a Client’s time.
6
To allow access for secondary Servers, enter the serial numbers in the Other
Server Serial Numbers fields. Up to seven RemoteWare Servers can access the
same Client (6 in addition to the Server that defines the Client).
7
The Enable Options box controls features for this Client. Select any of the following
check boxes that apply:
•
Application Work Objects. Select this to enable or disable Application work
objects.
•
Electronic Software Distribution. Select this to enable or disable ESD work
objects.
•
Inbound Work Object Selection. Select this to allow the Client
communications software user to choose which assigned work objects to
execute.
C HAPTE R 3 / D ef i ni n g an d Up da ti n g C li e nt s
85
Specifying Client communication settings
Use the Client property page to do the following:
•
Assign communication resources to the Client
•
Define the Server phone numbers or addresses
•
Enable an inbound communications schedule
•
Enable Multicast for TCP/IP Client (if licensed for Multicast)
To set communication settings:
1
In the Client Profile window, click the Client tab.
Sample Async Dialog Box:
Note: The Multicast Enable check box displays only if you are licensed for Multicast.
2
n
Due to
performance issues,
we recommend you
do not use the
NetBIOS resource for
RemoteWare
Windows 3.1
Clients.
3
From the Protocol drop-down list box, choose the protocol definition the Server
and Client use to communicate.
If you selected a network protocol, go to Step 5.
Or
If you selected an ASYNC protocol, the Modem Type field displays a default value.
To use a different modem at the Client, select another modem from the Modem
Type drop-down list box.
86
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Sample TAPI defined Async Dialog Box:
Note: The Multicast Enable check box displays only if you are licensed for Multicast.
To use a TAPI modem, select the Use Client system defined modem (TAPI)
check box, then select the Use country and area code check box, if needed.
When this box is checked, the dialing entry utilizes the country and area code
settings set on the Client (part of the OS settings). Select the Use System
Location check box to use the dialing rules (part of the OS settings) on the Client.
If defining a direct connect Client, select Direct Connect.
To create modem definitions, see “Working with modem types” on page 69.
4
n
For a Direct
Connect ASYNC
connection, the
Server's ASYNC
resource Data Rate
must match the Data
Rate of the Client's
ASYNC resource.
5
From the Modem Port drop-down list box, select the communications port for the
modem at the Client.
From the Data Rate drop-down list box, select the correct value.
6
If the Client needs to place inbound calls, click the Primary button to enter a
Server phone number or address.
7
Enter the Server Phone Number or network address the Client uses to contact
the Server.
Note: The Server Phone Number option is not available for NetBIOS settings.
C HAPTE R 3 / D e finin g a nd Up da tin g C lie n ts
87
You can also enter an indirect network address, which allows the Client to always
have the current Server phone or address. Type the name of the Server, for example
<SERVER1>.
8
To enter an alternate number or address for the Server, click the Secondary
button. Enter the secondary phone number or network address.
9
Select the Inbound Schedule check box if you want the Client to connect with the
Server at a set time each day.
10 Click the Time button to set the time the Client
contacts the Server.
•Use the Time spin buttons to set the time.
•Click OK.
11 Use the Retries spin buttons to change the number of
attempts made during a single connection.
To define another async connection, network connection, or scheduling
method to connect to the Server:
1
n
To configure
alternate settings,
see “Specifying
Client
communication
settings” on page
85.
2
On the Client page, select Undefined from the Client Configuration drop-down
list box.
Up to four alternate settings can be defined for each Client. All of these settings
appear in the Client’s dialing directory.
88
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To enable Multicast for TCP/IP Clients:
Sample TCP/IP defined Client Dialog Box:
Note: The Multicast Enable check box displays only if you are licensed for Multicast.
1
Select the Enable check box.
Important: When you check Enable in Client Profile, the Client is
automatically assigned to the RWS Multicast ESD work object.
For additional information on Multicast, refer to RemoteWare Multicast System
Administrator’s Guide.
When you Disable Multicast this removes the Client from the assignments.
C HAPTE R 3 / D e finin g a nd Up da tin g C lie n ts
89
Specifying Server communication settings for Clients
Use the Server property page in Client Profile to define the resources and methods the
Server uses to connect to the Client.
To select Server communication settings for Clients:
1
n
Due to
performance
considerations, we
recommend you do
not use the NetBIOS
resource with
RemoteWare
Windows 3.1
Clients.
2
Select the resource the Server uses to call the Client.
If you selected an asynchronous resource, choose the service the Server uses to call
the Client from the Long distance service drop-down list box.
Or
If you selected a NetBIOS, SPX, or TCP/IP
resource, choose the Network Group to which to
assign the Client from the drop-down list box.
3
In the Client Phone Number or Client Address
field, enter the number or address the Server uses
to contact the Client.
Note: NetBIOS Clients use the Client name as the Client Address. TCP/IP Clients can
use either the numerical address (as in 127.0.0.1) or the DNS name (as in
cr01.sample.com). The DNS name must be resolvable to the Server’s IP
address.
90
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
4
From the Matching Client Configuration drop-down list box, choose the
protocol the Server should expect when it calls the Client.
5
To define an alternate resource, long distance service, and Client phone number,
repeat Steps 1 through 4 in the Alternate box of the Server page. The Server will
use the alternate method to call the Client if it cannot reach the Client using the
primary method.
Assigning sessions to Clients
Use the Assignments page in Client Profile to specify which work objects and sessions
run when the Client and Server connect. The page also allows you to assign a Client to
Client groups.
Note: To assign users to Clients, use the Directory Manager program.
To display the Assignments page for a specific Client:
1
On the Client List page, highlight the Client name.
2
Click the Assignments tab.
3
On the Assignments property page, the list box displays the items (work objects,
sessions, users, or Client groups) associated with this Client. Use the View dropdown list box to select which items appear in the list box, or to select what type of
item to assign to the Client.
C HAPTE R 3 / D e finin g a nd Up da tin g C lie n ts
4
91
To assign a Client, verify the View area displays the type of item you are assigning.
Click Assign.
A window similar to the one above displays the items currently defined on this
Server system.
5
Choose one of the following:
•
To assign the Client to all the items listed, select the All ... button, where the
button name includes the item (such as the All Objects or All Client Groups
button).
•
To assign the Client to a specific item, highlight the item in the list box and click
OK to return to the Assignments page.
•
To assign more than one item, press the [Ctrl] key and click each of the items to
assign. Or, press the [Shift] key while clicking multiple adjacent items to assign.
Click OK once you have selected the items.
Unassigning a selection from a Client
1
From the Assignments page, select the item type you want to remove from the View
drop-down list box.
2
Choose one of the following:
•
To remove one or more items, highlight the item(s) on the Assignments page,
then click Unassign.
•
To remove all assignments of that type, click Unassign All.
92
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Viewing Client information
Use the Information page in Client Profile to view general information about the Client.
If the Drive and Memory values appear as Uninitialized, then the Client has either not
connected or you have not assigned the CHECK CLIENT DISK work object to the
Client. For more information on assigning work objects and sessions to Clients, see
“Assigning sessions to Clients” on page 90.
To display the Information page:
1
On the Client List page, select the Client.
2
Click the Information tab.
Note: This property page varies based on the components you have installed. If
Inventory Manager is installed on the RemoteWare Server, this property page
contains two tabs; Client Information and Configuration Files. These tabs
display information based on the Inventory scan completed on the Client's
computer. If you have not completed an Inventory scan on your Clients'
computers these tabs appears blank.
For more information about each field on this page, see the “Information page” in the
RemoteWare Server Reference Manual.
C HAPTE R 3 / D e finin g a nd Up da tin g C lie n ts
93
n Supplying Client comments
Use the Comments page in Client Profile to add optional notes, contact names, and
location information pertinent to the Client to help you resolve hardware problems or
other situations. The Client user does not see this information.
To display the Comments page for a specific Client:
1
On the Client List page, select a Client.
2
Click the Comments tab.
3
Enter the names, addresses, and phone numbers of people you can contact at the
Client location, as well as any details about this site.
94
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Updating Client definitions
To update a Client definition:
1
On the Client List page in Client Profile, highlight the Client you want to change.
2
Click
Disable on the toolbar to prevent the Client from communicating with
the Server until you finish your changes.
3
Click the appropriate tab to display the property page and make any necessary
changes for the selected Client.
4
When you are through making your changes, click the Client List tab.
5
Make sure the client is still selected then click
enable the Client.
Enable on the toolbar to re-
You can send changes in the Client definition to the Client using any of the following
methods:
•
Enable the RWS System ESD object for the Client.
•
Create a session that sends the updated Client file nodeinit.xdt to the Client. On the
Server, this file exists as nodeinit.dat in the \NODE\ClientName directory and
should be sent to the Client’s \nodesys directory as nodeinit.xdt.
•
Use an Interactive Session to send the new nodeinit.xdt file to the Client. See the
RemoteWare Server Reference Manual for more information on Interactive
Sessions.
C HAPTE R 3 / D ef i ni n g an d Up da ti n g C li e nt s
n
95
Copying a Client definition
When setting up a Client with similar settings as an existing Client, you can copy the
existing definition, then edit it to create the new Client definition.
To copy an existing Client definition:
1
On the Client List page in Client Profile, select the Client.
2
Click
3
Enter a Name and Description for the copy, then click OK.
4
A dialog box appears asking if you want the object, Client group, and session
assignments to be copied to the new Client. Select Yes if you want the assignments
to be copied or No if you do not.
Copy on the toolbar. The Copy Client dialog box appears.
Client Profile creates the new Client definition and displays the General Settings page.
You can now make changes to the Client definition.
96
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Deleting a Client definition
When you delete a Client from the Server’s Client list, RemoteWare also automatically
removes it from any associated Client groups, sessions, and work objects.
Note: You cannot delete a Client that you have assigned to a direct connect port, or a
Client with assigned users. You must unassign all users before you can delete the
Client.
To delete a Client definition:
1
On the Client List page in Client Profile, select the Client you want to delete.
2
Click
3
Select Yes when prompted. Client Profile deletes the Client and returns to the
Client List page.
Delete on the toolbar.
n Resetting Security
Clients use several pieces of information to authorize access to a Server. The Client and
the Server share an internal security token. This token may get damaged if the Client’s
files are corrupted or the connection drops during the token exchange.
If the Client continually receives a security error:
1
On the Client List page, select the Client for which you want to reset security.
2
On the Command menu, select Reset Security to disable security checking for the
next connection.
3
To disable security checks for all Clients, select Reset All Security on the
Command menu. Every Client will have security suspended on the next
connection.
C HAPTE R 3 / D e finin g a nd Up da tin g C lie n ts
n
97
Defining Client groups
A Client group is a collection of Clients that are running similar programs or have the
same session or work object requirements. Client groups simplify the management of
large numbers of Clients.
To define a Client group:
1
In Client Profile, click the Client List tab.
2
On the File menu, select New Client Group.
.
Note: Do not use “All” as a Client Group name, if you plan to use External
Configuration Files (ECFs) to build work objects, define scheduled sessions, or
configure Clients and Client groups.
3
Enter a name and description for the Client group, then click OK.
98
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Assigning members to Client groups
Use the Members page to add members to a Client group or to view the members of a
current Client group. Both Clients and Client groups can belong to a Client group.
To assign members to a Client group:
1
On the Members page in Client Profile, click Assign.
2
From the Clients and Client groups currently defined on the system, highlight the
desired Clients and Client groups, then click OK.
To assign all defined Clients and groups to the Client group, click All Clients &
Groups.
C HAPTE R 3 / D e finin g a nd Up da tin g C lie n ts
99
Assigning Client groups to parents
Use the Parents page to assign Client groups to a parent group or to view the parents of
a Client group. A “parent” is a group to which the current group belongs.
To assign a Client group to a Parent:
1
From the Client List page, select the Client group you want to assign to a parent
group.
2
Click the Parents tab.
3
Click Assign to display a list of defined Client groups.
4
To assign a parent to the selected Client group, select a group from the list and click
OK.
100
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Deleting a Client group
To delete a Client group:
1
At the Client List page in Client Profile, highlight the Client group you want to
delete.
2
Click
3
Click Yes in the confirmation message window.
Delete on the toolbar.
Editing a Client group
To edit a Client group, highlight the Client group on the Client List page in Client
Profile. Then select the tab for the property page where you need to make changes.
To change an existing Client group description:
1
On the Client List page, highlight the desired Client group name.
2
On the Command menu, select Change Client Group Description. The Change
Description for Group dialog box appears.
3
Enter the new description and click OK. The updated description appears on the
Client List page.
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
4
4RemoteWare
Installing the Client
Using RemoteWare’s Makekit Wizard, you can create a Client installation kit to install
the RemoteWare software at the Client. You can also use the Makekit Wizard to create
and register template Clients.
This chapter includes:
• Make Client installation kits for all Client types
• Create template Client makekits
• Create Client installation kit to Run Client as a Service
• Register and verify template Clients
102
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Making Client installation kits
After you have defined your Client, you can make the installation kit for the
RemoteWare Client software. This section includes instructions on how to create the
Client Installation Kits for the following Client types:
•
Windows 3.x/95/98/Me or NT/2000/XP
•
DOS
•
SCO UNIX
•
4690
•
OS/2 Clients
•
VMS Alpha Client
•
VMS VAX Client
•
HP-UX Client
•
AIX Client
•
Unixware
This section includes instructions to upgrade Windows 3.x Clients to Windows 95/98/
Me or NT/2000/XP, or to upgrade Windows 95/98/Me Clients to Windows NT/2000/XP.
Note: The RemoteWare Client software should be installed on a local drive. XcelleNet
does not support running the Client from a network drive.
Usually, when you create installation kits, you create them for specific Clients. However,
if you have a large number of Clients that are the same, consider creating a template
Client installation kit to save yourself some time. A template install kit allows you to
enter all of the general information when you create the kit at the Server, and the Client
fills in the specific information when he or she installs the software.
Installing ODBC and MAPI on RemoteWare Clients
The RemoteWare Client requires Messaging Application Programming Interface
(MAPI) and Open Database Connectivity (ODBC) support to run RemoteWare
Messaging. Clients which will use RemoteWare Messaging must install MAPI and
ODBC before running the RemoteWare Client Setup.
MAPI
MAPI is part of the Windows Messaging component, which is included with some
versions of the Windows system, Microsoft Outlook, and Microsoft Office. It is likely
that your Clients already have MAPI support. However, you should verify this by
viewing the operating system’s installed components. The steps to do this vary
depending on the Client’s operating system.
C HAPT ER 4 / I ns ta lli n g th e C li en t
103
ODBC
The RemoteWare Server CD contains ODBC installation programs you can deploy to
and install on Clients. The files you need can be found in the \MDAC folder.
Creating standard Client installation kits
Use the Makekit Wizard to create installation kits to send the RemoteWare Client
software to all Client types. To create a number of identically configured Clients, use
the Wizard to create template Client installation kits. For more information, see
“Creating template installation kits” on page 111.
Note: The Makekit Wizard options vary depending on the Client type for which you
are creating the installation kit.
To create a standard Client installation kit:
1
If you are placing the kit on a floppy disk, insert a blank disk into the drive.
2
On the Client List page, select the Client.
3
On the Command menu, select Make Installation Kit.
Note: Click Cancel at any time to exit the Makekit Wizard.
4
To create a standard Client installation kit, click Next.
104
n
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To convert a
Windows 3.x Client
into a 32-bit
Windows 95/98/
Me or Windows NT/
2000/XP Client, see
the section
“Upgrading 32-bit
Clients” later in this
chapter.
5
Enter the directory location where you want to place the installation files, or click
to search for a directory location.
6
7
Click Next to continue. The dialog box that appears depends on the type of Client
installation kit you are creating.
•
If you are creating a standard installation kit for a Windows 95/98/Me or NT/
2000/XP Client, the Control File dialog box appears. Go to Step 7.
•
If you are creating a standard installation kit for a Client type other than
Windows 95/98/Me or NT/2000/XP, the Client Options dialog box appears. Go
to Step 8.
For Windows 95/98/Me or NT/2000/XP Client installation kits, in the Control File
dialog box, select one of the following options:
•
If you want to add a control file such as silent.ini for a silent Client install, select
the Include Control File check box. Click
to locate the file you want to
include, then click Next to continue. The Client Options dialog box appears.
Note: For information on what to include in a silent.ini file, see the RemoteWare
Server Reference Manual.
•
If you do not want to add a control file, click Next to continue and go to Step 8.
The Client Options dialog box appears.
C HAPT ER 4 / In s ta lli n g th e C lie n t
8
105
On the Client Options dialog box, complete the following steps:
•
Select the Include User-Defined ESD Files check box to include any ESD
files assigned to the current Client.
•
If the Client operates in a language other than English, select a language from
the Installation Language drop-down list box.
Note: When you create a template kit for a Windows 95/98/Me or NT/2000/XP Client,
the Makekit Wizard installation language is based on the system settings at the
Client.
9
Click Next to continue.
10
On the Summary dialog box, select one of the following options:
11
•
To make changes to the installation kit, click Back.
•
To complete the installation kit, click Create.
When the status reaches 100%, click OK to return to Client Profile.
The software is now ready to install at the Client.
106
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Upgrading Windows-based RemoteWare Clients
You can use the Makekit Wizard to upgrade existing Windows 3.x RemoteWare Clients
to Windows 95/98/Me or NT/2000/XP RemoteWare Clients, or to upgrade existing
Windows 95/98/Me RemoteWare Clients to Windows NT/2000/XP RemoteWare
Clients. In order to complete the upgrade, you must already have installed the
RemoteWare Client software at the Client. If you are installing a 32-bit Client for the
first time, you must create a new installation kit. For more information, see see
“Creating standard Client installation kits” on page 103.
To upgrade a Windows-based Client:
1
On the Client List page, select a Client whose type corresponds to the type of
Client you want to result from the upgrade. For example, if you want to upgrade a
Windows 3.x Client to Windows 98, choose a Windows 98 Client.
If the Client type does not exists, create a new Client. Select New Client on the
File menu.
2
On the Command menu, select Make Installation Kit.
3
On the Welcome dialog box, select the Create 32-bit Upgrade check box and
click Next.
4
Click Create to create the necessary upgrade files. RemoteWare creates a work
object for you to send to Clients so they can upgrade their Client type.
C HAPT ER 4 / I ns ta lli n g th e C li en t
107
5
On the Client List page, select the Client you want to upgrade.
6
Click
7
Click the General tab.
8
Select Windows 95/98/Me or Windows NT/2000/XP from the Client Type dropdown list box.
9
Click the Client List tab.
10
If an Async resource is displayed, the Use Client system defined modem (TAPI)
option is selected by default. If you do not want to use TAPI, clear the check box,
then choose the appropriate modem type.
Disable on the toolbar to disable the Client.
Note: To use TAPI, you must ensure a TAPI modem is defined at the Client.
11
Click the Client List tab again, then select the Client you are upgrading.
12
Click Enable on the toolbar to re-enable the Client.
13
Click the Assignments tab, then click Assign.
14
Choose the RWS Upgrade Windows to 95/98 or NT Client work object then
click OK. The work object displays on the Assignments tab.
Note: To upgrade other Windows 3.x Clients to 32-bit Clients of the same type, assign
the work object to these Clients.
When the Client and Server connect, the upgrade work object copies the installation
files, installs the program, and then disconnects. During the next connection, the
clean-up work object deletes all Windows 3.x or 95/98/Me Client files from the Client.
Then you can unassign the RWS Upgrade Windows to 95/98 or NT Client work
object.
108
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Installing the 4690 Client software using a Client installation kit
Before you create an installation kit for a 4690 Client, ensure that each 4690 Client has
a Client type of IBM 4690 Client or IBM 4690 TCP/IP on the Client Profile General
property page. Then, create an installation kit. For more information, see “Creating
standard Client installation kits” on page 103. Since there is no installation
program for the 4690 Client, the Registration Key, Prompt for Server Serial Number,
Prompt for Client Name, and Template Makekit options are not valid. The Installation
Language and Prompt for User Information options do not apply.
When the Make Installation Kit function is complete, three program files are created:
•
XNODE.286 is the Communications Kernel program that controls all
communications between the 4690 Client computer and the RemoteWare Server.
•
XCOMM.286 is the Client Communications user interface program used to
initiate a connection to the Server, view and edit Client setup, and view the
Communications Log.
•
NODEINIT.DAT is the Client setup file that stores configuration information for
each client.
Note: The IBM 4690 operating system cannot read files copied from the Windows NT
operating system. The RemoteWare Server runs under Windows NT and is used
to create the Client installation disk. Therefore, the 4690 Client computer
cannot automatically read the files on the Client installation disk. To make the
Client installation disk readable by the 4690 operating system, you must run the
CHKDSK utility on the diskette at the 4690 computer. For more information,
see Chapter 2, “Installation,” of the RemoteWare 4690 Client User’s Guide.
C HAPT ER 4 / I ns ta lli n g th e C li en t
109
Installing the 4690 Client software using FTP (TCP/IP Clients only)
Using FTP (File Transfer Protocol), you can transfer the Client software directly from
the RemoteWare Server to each Client computer that uses a TCP/IP connection.
To transfer the Client files using FTP:
1
Create a Client installation disk using the instructions in the previous section and
choose a destination location on the local RemoteWare Server. For 4690, three files
are created (NODEINIT.DAT, XCOMM.286, and XNODE.286) in this location.
2
On each 4690 Client computer, create a Client userid and password in the
c:\adx_sdt1\adxhsiuf.dat file. To use FTP, you must have a userid and password
for each machine.
3
On the RemoteWare Server, go to a command prompt and type:
ftp <IPAddress>
where <IPAddress> is the IP address for the 4690 Client computer to which you
want to transfer files (for example, you might type ftp 172.16.34.27). You will see a
message indicating that there is a connection to the FTP server you specified.
4
Enter the userid you created for this 4690 Client, then enter the password. You will
see a message indicating that the user is logged on, and then you will see an FTP
prompt.
5
At the prompt, type binary to put FTP into binary mode.
6
Next, you must create the \NODESYS directory on the Client computer. At the
FTP prompt, type: mkdir c:\nodesys
7
Copy each of the 4690 Client program files to the \NODESYS directory using the
put command. For example, to copy the XNODE.286 file from the \makekit
directory on the RemoteWare Server’s d: drive, you would type:
put d:\makekit\xnode.286 c:\nodesys\xnode.286
The following message appears:
200 PORT command successful.
150 Opening BINARY mode data connection for H0:/nodesys/xnode.286
226 Transfer complete.
8
Repeat Step 7 for each of the remaining 4690 program files (XCOMM.286 and
NODEINIT.DAT) to copy them to the 4690 Client computer.
Once the installation using FTP is complete and the Client user configures the 4690
Client, communications can begin between that Client and the RemoteWare Server.
For configuration instructions, see the RemoteWare 4690 Client User’s Guide.
110
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Creating installation kits for OS/2 Clients
To create a Client installation kit for an OS/2 Client using the Make Installation Kit
command in Client Profile, see “Creating standard Client installation kits” on
page 103. When creating the Makekit to install the text-based OS/2 Client, the first
resource defined for the OS/2 Client will be the type of text-based Client that will be
included on the Makekit. For example, if the first resource defined for the OS/2 Client
is TCP/IP, then the text-based Client included will be the TCP/IP only Client.
Note: The OS/2 Client Makekit includes program files for both the text- and GUIbased OS/2 Client. The Client user installs the appropriate client type by
running either the OIINSTALL (for GUI interfaces) or the OTINSTALL (for
text-based clients) installation program.
C HAPT ER 4 / I ns ta lli n g th e C li en t
n
111
Using template Clients
Template Clients save time during the installation when you are creating a number of
identically configured Clients. You can duplicate one installation kit many times, so you
do not have to create many makekits.
Creating template installation kits
If you need an number of identically configured Clients, use the Makekit Wizard to
create template Client installation kits.
To create a template installation kit:
1
If you are placing the kit on a floppy disk, insert a blank disk into the drive.
2
On the Client List page, select the Client on which to base the template Client.
3
On the Command menu, select Make Installation Kit.
4
In the Makekit Options field, select the Template Installation Kit check box, then
click Next.
5
In the Makekit Directory area, enter the directory where you want to place the
installation files, or click
to search for a directory location and click Next.
112
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
6
•
If you are creating a template kit for a Windows 95/98/Me or NT/2000/XP
Client, the Control File dialog box appears. Go to Step 7.
•
If you are creating a template installation kit for another Client type, the Client
Options dialog box appears. Go to Step 8.
For Windows 95/98/Me or NT/2000/XP template clients, select one of the
following:
•
If you want to add a control file such as silent.ini for a silent Client installation,
select the Include Control File check box. Click
to locate the file, then
click Next.
•
If you do not want to add a control file, click Next to continue.
7
Select the Include User-Defined ESD Files check box to include any ESD files
assigned to the current Client.
8
If the Client operates in a language other than English, select a language from the
Installation Language drop-down list box.
Note: When you create a template kit for a Windows 95/98/Me or NT/2000/XP Client,
the Makekit Wizard installation language is based on the system settings at the
Client.
C HAPT ER 4 / I ns ta lli n g th e C li en t
9
Click Next.
10
Select one or both of the following options:
11
12
113
•
Select the Prompt for Serial Number check box if you want the user at the
Client to enter the serial number assigned to the Server in order for the Client
to register successfully.
•
Select the Prompt for Client Name check box if you want the user to enter a
Client name when registering.
Click Next.
•
If RemoteWare Messaging is installed, go to Step 12.
•
If you do not use Messaging, the Client Registration dialog box appears. Go to
Step 13.
To add a template user to the installation kit, select the Prompt for User
Information check box and click
to browse for users. Click Next.
Note: If you enabled registration when you defined the Client, the Client Registration
dialog box does not appear. Go to Step 15.
114
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
13
Select the Enable Client Registration check box to enable Clients to register at
the Server when they install the software.
14
Click Next.
15
Click Create to complete the installation kit, or click Back to make changes.
16
A dialog box shows the status of the makekit process. When the status reaches
100%, click OK to return to Client Profile.
C HAPT ER 4 / In s ta lli n g th e C lie n t
115
Client installation kit to Run Client as
n Creating
a Service
This feature allows you to install the RemoteWare Client as a service. When you install
the client as a service this provides all the rights and features that are part of running
applications as services under Microsoft Windows. You have the option to specify
service account logon credentials and startup options. This feature eliminates the need
to manually run the RemoteWare Client program..
Note: RemoteWare Clients can install and run as a service only if the user account is
assigned to the Administrators group. For information, see “Granting rights”
on page 29.
Note: If the RemoteWare Client is installed as a service under a non-local system
account, Logon as a Service must be granted to the user through the operating
system.
To create an installation kit to Run Client as a service:
1
On the Client List page, select the Client you want to run as a service.
2
On the Command menu, select Make Installation Kit.
3
Select the Run Client As Service check box and click Next.
116
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
4
Specify where the account service should be installed. By default the Use existing
service account information option is checked. This indicates the client service is
installed under the Local System account.
Or clear this option to enter the User Name and Password fields.
5
Click OK and then click Next.
6
Enter the directory location where you want to place the installation files, or click
to search for a directory location.
7
Click Next to continue.
8
Select the Include User-Defined ESD Files check box to include any ESD files
assigned to the current Client.
9
If the Client operates in a language other than English, select a language from the
Installation Language drop-down list box.
Note: When you create a template kit for a Windows 95/98/Me or NT/2000/XP Client,
the Makekit Wizard installation language is based on the system settings at the
Client.
10
Click Next to continue.
C HAPT ER 4 / I ns ta lli n g th e C li en t
11
Click Create to complete the installation kit, or click Back to make changes.
12
A dialog box shows the status of the makekit process. When the status reaches
100%, click OK to return to Client Profile
117
Important: The Run As Service option used during the Makekit installation
wizard only completes the configuration portion of the Client Service
installation. Next, the user must run the setup.exe to complete the service
installation process.
When the Client runs setup.exe the final dialog box defaults to the Install as
service option. After installation is complete the RemoteWare Client service
starts automatically.
Note: After the Client runs setup.exe, the RemoteWare kernel is hidden and does not
display in the system tray for non-local system accounts. The Run Client as
Service feature is designed to work in the background on the Client.
118
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Setting template Client parameters
n
To create systemnamed or usernamed Client during
registration, the
Allow Registration to
Create new Clients
option must be
selected.
You register and verify template Clients in several ways. This table lists some of the
methods and their advantages.
Table 6. Options for registering a Template Client
Option
Inbound to Server
Outbound to Client
From the Registration Options dialog:
Enable Client
Registration
Control when Clients can connect
and successfully register.
Turn off or on to control when an
administrator can schedule a
registration session.
Allow Registration
to Create new
Clients
Automatically add new Clients when
they first connect. Uses the name
chosen by the Client if the Prompt
for Client Name option is enabled;
otherwise the Server creates the
name from the Client Prefix and
Counter.
Disable this option to force Client
names to match preexisting
unregistered definitions in the Client
List.
Does not apply to outbound
registration.
Note: This option will not work if
you enabled the Prompt for User
Information option for the makekit.
Client Prefix/
Counter
Enable these two fields from the
Allow Registration to Create New
Clients option. Character and
number limits are based on your
current licensing. Control what
Clients are called.
Does not apply to outbound
registration.
Default template
user
Provides a model user as a basis for
user attributes, assigned applications,
and other settings.
Does not apply to outbound
registration.
Require
Administrator
Verification
Once new or predefined Clients have
registered, limit their capabilities to
just connecting until their identity is
confirmed.
Be able to complete the
registration process, but perhaps
require another administrator to
activate the Clients.
Require
registration key
Control Client registration to
individuals with the correct
password.
Does not apply to outbound
registration.
C HAPT ER 4 / I ns ta lli n g th e C li en t
119
Table 6. Options for registering a Template Client
Option
Inbound to Server
Outbound to Client
From the Makekit Wizard:
Prompt for Serial
Number
Requires Client user to provide
Server’s serial number for successful
registration.
Does not apply to outbound
registration.
Prompt for User
Information
Requires Client user to supply user
name, address, and other
information.
Creates user name and profile
using template user
characteristics.
Prompt for Client
Name
Allows Client user to determine
name. Also used when the Allow
Registration to Create New Clients
option is disabled to match a chosen
Client name with a predefined entry
in the Client list.
After Client user has installed
template Client, the Server’s name
choice overrides the name chosen
at the Client.
120
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Registering a template Client
After installing the Client software on the Client computer, you can register the
template Client several ways:
•
Inbound registration. The last page of the Client installation allows the user to
initiate a connection to the Server. A message appears after the connection to
indicate whether registration was successful.
•
Outbound registration. The individual installing the Client chooses No to the
offer to initiate a registration connection. The Client user then starts the Client
Communications program and lets the Client wait for a call from the RemoteWare
Server.
•
Verification. Verification is an extra option you can add to permit the Server
Administrator with an added level of security.
Note: On a Template Client, multiple registry entries are created. These entries
include the Makekit profile name and the unique Client name generated from
the Makekit.
Inbound registration
n
When you create
a DOS or
OS2TCOMM
template Makekit
based on an existing
(enabled) Client,
registration will fail
unless you reset
security for the Client
in the Client Profile
prior to the template
Client calling the
Server.
In order for inbound registration to be successful, both the Server and the Client must
correctly set or complete connection and registration information. Table 7, “Information
needed for inbound registration,” lists the information you need to complete for setting
up inbound registration.
Table 7. Information needed for inbound registration
Item
Description
At the Server:
Enable Client
Registration
If this option is disabled, then Clients connect but cannot complete
registration.
Allow Registration
to Create New
Clients
The Prompt for Client Name option in the Makekit must be enabled.
Otherwise registration is unsuccessful, since the Client cannot select a
name, and the Server does not provide one either. Disabling this option
allows Server to match chosen Client name with a predefined Client
definition. Clients create their own names, or the Server creates a name
based on the Prefix and Counter.
Completed Client
definition
A definition by the same name as the Client’s given name must exist if the
Allow Registration to Create New Clients option is disabled.
At the Client:
Connections
The connection protocol used to contact the Server must be correctly
configured.
C HAPT ER 4 / I ns ta lli n g th e C li en t
121
Table 7. Information needed for inbound registration
Item
Description
Client Name
If the Prompt for Client Name option is enabled, then you should instruct
the user on what names are allowed.
When the Allow Registration to Create New Clients option is disabled, the
name must correspond exactly with one that is already defined (but not
registered) on the Server.
If the Allow Registration to Create New Clients option is enabled, the name
can be any eight letters and numbers.
User Information
When enabled during Makekit generation, Clients may enter their user
names and other information.
Serial Number
If you enabled Prompt for Serial Number during Makekit generation, then
the correct Server Serial Number is required.
Registration key
If you enabled Require Registration Key, then the Client must enter this key
exactly as it appears in the Client Profile’s Client Registration Options
window.
After the proper settings exist at the Server, the inbound registration is controlled by the
Client software. If the Client user inputs the correct information supplied by the Server
Administrator, then the registration session may begin at the end of the installation
procedure.
The Client may also use the Client Registration program to start the inbound
registration after installation is complete.
Outbound registration
The Server may initiate and complete template Client registration after the Client
software is correctly installed and the Client is accessible. Table 8, “Outbound
registration prerequisites,” describes some of the prerequisites for a successful
outbound registration.
Table 8. Outbound registration prerequisites
Item
Description
Enable
Registration
Enable the Enable Client Registration option in the Client Registration
Options window.
Predefined Client
The Server must have a Client definition for the outbound Client
registration. You may want to use a copy of the template Client definition;
do not use the original template definition.
Connection
information
Verify that the Server page contains a valid Client Phone Number or Client
Address value for the Client.
122
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Table 8. Outbound registration prerequisites
Item
Description
Installation
Verify with the Client user that the software has been successfully installed.
Client active
The Client Communications program or the winxnode communications
engine must be active and currently monitoring the serial port or network
address that will be used by the Server.
Correct
information
If required, the Client user must have entered the correct information (such
as Serial Number or Registration Key).
To complete outbound registration:
1
Click the Client List tab.
2
On the Registration menu, select Schedule Registration Session. The Select
Clients for Registration Session dialog box appears.
3
Select the Clients in the list and click OK. Click All Clients to schedule a session to
all Clients.
4
On the Filter menu, select by Registered Clients to check the progress of the
registration. You may also want to look at the Session History view in Log Viewer for
information about registration or its reason for failure.
C HAPT ER 4 / I ns ta lli n g th e C li en t
123
Using manual verification
One of the options in the Client Registration Options window is Require Administrator
Verification. This option adds a level of control at the Server before the Client is able to
communicate as a fully registered Client. Clients do not have to call a second time to
complete verification. When enabled, verification is valid on all inbound and outbound
registration sessions.
Once a Client is registered, you can select by Clients Requiring Manual
Verification on the Filter menu to view which Clients are awaiting verification.
To verify a Client:
1
Click the Client List tab.
2
On the Registration menu, select Manual Verification. The Select Clients to
Verify dialog box appears.
3
Select one or more Clients from the list and click OK, or click All Clients to verify
every Client in this list.
The Clients operate as fully registered Clients the next time they connect. You do
not have to start a connection with the Client to verify it.
Unregistering a Client
You can unregister a lost or missing template Client in order to quickly recover without
having to delete it and recreate the template makekit. An unregistered Client can begin
the registration and verification process during the next communications session.
To unregister a Client:
1
Select the template client you want to recover.
2
On the Command menu, select Unregister Client.
3
Notify the user to re-run the registration and verification process during the next
communications session.
124
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
ESD Auto Apply
ESD (Electronic Software Distribution) is used by the RemoteWare system to keep
files and programs at the RemoteWare Client fully functional. If a Client has out-of-date
files or is missing a critical system file, the RemoteWare system ESD downloads and
replaces the affected file(s). This restores the client to a fully operational state. In most
cases, the ESD download must be to the Client system in order to complete the
process.
For complete information about ESD Auto Apply, refer to Chapter 3 - Preparing for
Communications in the RemoteWare 32-Bit Windows Client User’s Guide.
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
5
5RemoteWare
Building Objects
Work objects and worklists are the fundamental building blocks for all tasks on the
RemoteWare Server. Work objects are lists of tasks or events that execute during a
connection with a Client or as part of a session. Work objects perform tasks using
events, which are commands used to instruct RemoteWare to complete an operation.
This chapter includes:
• Create a work object
• Add Byte Level Differencing to work object
• Manage an object group
• Assign work objects to sessions or Clients
• Filter objects for viewing
• Use the Worklist Editor
126
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Using Work Object Editor
Use Work Object Editor to build, manage, and assign the objects needed to complete
tasks using RemoteWare, such as registering Clients, running reports, and checking
Client disks.
To open Work Object Editor:
In the RemoteWare Menu, double-click the
Work Object Editor icon. This icon
is located in the All Utilities and Server Setup groups. The Work Objects Editor
window appears.
The first time you open Work Object Editor, a list of pre-defined work objects appears.
You can also create your own work objects. For more information, see “Creating a
work object” on page 128.
C HAPT ER 5 / Bu ild ing Ob je ct s
127
Table 3 explains the different object types in Work Object Editor and in what situations
you would use each type. Not all of the types listed in Table 3 appear in the systemdefined objects list.
Table 3. Types of work objects
Use
For . . .
ESD
Files on the Server you want updated regularly at the Client. When an
ESD object executes, the Server checks all files specified in the event list
and builds a list of what needs to be updated. The files are then updated in
one efficient transfer.
Worklist
Tasks you want completed at the Client, the Server, or both. Worklist
objects can incorporate any of the events listed in Appendix A of the
RemoteWare Server Reference Manual. When the object executes, each
event is processed in order.
Group
Related ESD and Worklist objects you need to assign to multiple sessions
or many Clients. Group objects to save time when you make assignments.
When you group objects, the group (instead of the individual objects that
make up the group) is listed at the Client. If the user chooses to have the
group execute, all of the objects in the group execute.
Application
Keeping track of applications available to or in use by Clients or users, for
licensing purposes.
Application Group
Applications assigned to many users or user groups. Grouping objects saves
time when you make assignments. When application objects are grouped,
the individual objects that make up the group are listed at the Client, so the
user can select individual objects to execute. RemoteWare Applications
create an Application Group object for each application.
Multicast
Multicast work objects consist of a set of events executed through a
Multicast session. On the Server, these work objects can contain any before
events. The three types of events which can be run on the Client include:
•
•
•
Send
Execute
Delete
128
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Creating a work object
Before you create work objects, you must decide which type of object you want to use.
What you select depends on the function you want RemoteWare to perform. How you
create a work object depends on the type of object you want to create, since each type
has certain characteristics and attributes.
To create a new work object:
1
In Work Object Editor, click the Objects tab.
1
On the File menu, select New.
2
Choose the type of object you want to define. For additional information, see
“Types of work objects” on page 127.
3
Enter the Enter a Unique Object Name field to describe the object.
4
Click OK. The new object appears in the Objects list.
C HAPT ER 5 / Bu ild ing Ob je ct s
129
n Setting general work object attributes
Use the General Attributes property page in Work Object Editor to limit or restrict
work object execution for any object. See “General Attributes property page” in the
RemoteWare Server Reference Manual for detailed information.
To set general attributes for an object:
1
From the Work Object Editor Objects page, select the object.
2
Click General Attributes tab.
3
Select the Enabled check box to make the object available for execution to Clients
and sessions.
4
From the Execution drop-down list box, choose whether the Client user has the
ability to control execution of this object.
5
Select a number from the Priority spin box to determine the execution order of
objects in a session.
Note: The Priority option is not available for Group, Application, or Application Group
objects.
130
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
6
Select the Include on Client Installation Disks check box to transfer files to the
Makekit when they are associated with this object. Enabling this option potentially
increases the size of the makekit; disabling this option potentially increases the
connection time of the first session.
Note: The Include on Client Installation Disks option is not available for Worklist
objects.
7
If you want to restrict this object to specific operating systems used by the Client,
select the Enable check box in the Limit Object Execution to Client Type(s) field.
Note: The Limit Object Execution to Client Type(s) field is unavailable for some
objects.
8
In the Execution Window area, select the Enable check box to restrict execution to
a specific time range. Set the time range using the 24-hour clock.
9
Select the Activation/Deactivation check boxes to set a date and time range for
object execution. For example, the object executes during the first three months
next year. Leaving one control disabled leaves that date range open-ended.
Once you have set the work object’s general attributes, the steps vary based on the type
of work object. Go to one of the following sections to continue to build your work
object:
•
To build Worklist or ESD objects, see “Defining events for Worklist and ESD
objects” on page 131.
•
To build a Multicast Work Object, see “Defining events for Multicast work
object” on page 145.
•
To build Group objects, see “Creating a Group object” on page 141.
•
To build Application objects, see “Specifying attributes for an Application
object” on page 142. Also see “Choosing members for an Application or
Application Group object” on page 143.
•
To build Application Group objects, see “Choosing members for an
Application or Application Group object” on page 143.
C HAPT ER 5 / Bu ild ing Ob je ct s
n Defining events for Worklist and ESD objects
131
Worklist and ESD objects include the Events page to define lists of tasks or files. For a
complete description of events and available options, refer to Appendix A, “Events,” in
the RemoteWare Server Reference Manual.
To define a Worklist or ESD object:
1
From the Work Object Editor, highlight the Worklist or ESD object.
2
Click the Events tab.
132
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
3
Click Add Events menu, then select the event type and specific event from the
menu.
Note: The ESD Events list can only use the SEND FILE, CHECK and SEND,
MAKEDIRECTORY, CHECK FILE, and COMMENT events.
Note: Byte Level Differencing is available for the SEND and GET events. This
feature detects differences between file versions at the Server and the Client
and sends only the differences to the Client or Server, which reduces the time
required to update files and software.
4
To enable an option, select the check box or the button next to the option. For more
information on the Event Details dialog box, see the RemoteWare Server Reference
Manual.
Different paths, execution instructions, and options apply to each event you include
in the list. The valid options for an event are enabled; invalid options appear
dimmed.
5
After you define the event, click Done.
After you have defined and added all of your events to the work object, you can assign
them to sessions and Clients. For information on assigning work objects to sessions and
Clients, see “Making work object assignments” on page 146.
C HAPT ER 5 / Bu ild ing Ob je ct s
n
133
Add defining events for Multicast Work Object
Multicast work objects consist of a set of events executed through a Multicast session.
On the Server, these work objects can contain any before events. The three types of
events which can be run on the Client include:
•
Send
•
Execute
•
Delete
For additional information about events, refer to Appendix A, in the RemoteWare
Server Reference Manual.
To define a Multicast object:
1
Click the Objects tab.
2
Select the Multicast object.
3
Click the Events tab.
4
To create the event list, click the Add Events menu, then select the event type and
specific event from the submenu.
Note: All events assigned to a Multicast work object are before events. The events to
be run on the Clients can only include: SEND, DELETE, and EXECUTE.
5
To enable an option, select the appropriate check box or radio button. Different
paths, execution instructions, and options apply to each event you include in the list.
Note: Byte Level Differencing is unavailable for Multicast events.
Note: Recursive option is available for the SEND events.
6
Once you define the event, click Done to return to the event list to continue adding
events.
134
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Adding Byte Level Differencing to work object
Byte Level Differencing is available for the SEND and GET events. This feature
detects differences between file versions at the Server and the Client and sends only the
differences to the Client or Server, which reduces the time required to update files and
software. This feature can be added to an existing work object or to a new work object.
Note: This feature is available for Windows 32-Bit Clients only.
To add Byte Level Differencing to an existing object:
1
Click the Objects tab.
2
Select the work object to which you want to add Byte Level Differencing.
3
Click the Events tab and select a SEND or GET event.
4
In the Options area, select the Byte Level Differencing check box.
5
Click Done.
Inserting events
To insert an event in a work object:
1
From the Work Object Editor, highlight the worklist or ESD object to edit.
2
Click the Events tab.
3
Select one of the following:
4
•
To insert an event before the highlighted event: On the Add Events menu,
select Insert Before and then select the event type to add from the Add
Events menu.
•
To insert an event after the highlighted event: On the Add Events menu,
select Insert After and then select the event type to add from the Add Events
menu.
When you leave the Events page, a dialog box prompts you to save the changes.
Choose Yes to save the edited list, or No to retain the original list.
C HAPT ER 5 / Bu ild ing O b je cts
135
Copying, pasting, and deleting events
Once you have defined an event, you can copy and paste it into another list, so you do
not have to define the event more than once.
To copy one or more events that are already included in the list:
1
Highlight the event or events.
2
On the Edit menu, select Copy.
To paste an event before another event:
1
Highlight the event.
2
On the Add Events menu, select Insert Before.
3
On the Edit menu, select Paste. The Work Object Editor inserts the pasted events
before the highlighted event in the list.
To paste an event after another event:
1
Highlight the event.
2
On the Add Events menu, select Insert After.
3
On the Edit menu, select Paste. The Work Object Editor inserts the pasted events
after the highlighted event in the list.
The copied event(s) are stored in the clipboard until you copy (or cut) another event. To
store events without risk of losing them, use the Export command. For more
information, see “Exporting an event list” on page 139.
To remove events from the list, but keep a copy on the clipboard:
1
Highlight the event or events.
2
On the Edit menu, select Cut. The events are removed from the list but are saved
on the clipboard.
To permanently delete events from the list:.
1
Highlight the event or events.
2
Click
Delete.
136
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Searching for events
To search for an event:
1
Click the Objects tab.
2
Select a Worklist, ESD, or Multicast object.
3
Click the Events tab.
4
On the Edit menu, select Find.
5
Enter the search text. You can enter all or part of an event text.
6
Select Up or Down to move through the object events.
7
Click Search to find the item or Cancel to return to the list. The first item to
match the search criteria is highlighted, or a message displays if the item cannot be
found.
8
To continue the search for the same text, click Find Next from the Edit menu or
click F3.
C HAPT ER 5 / Bu ild ing Ob je ct s
137
Searching and replacing event text
To search and replace event text:
1
Click the Objects tab.
2
Select a Worklist, ESD, or Multicast object.
3
Click the Events tab.
4
On the Edit menu, select Replace.
5
Enter the search text. You can enter all or part of an event text.
6
Select Up or Down to move through the object events.
7
Click Find Next to find the item or Cancel to return to the list. The first item to
match the search criteria is highlighted, or a message displays the item cannot be
found.
Note: Use the Match Case check box, to further narrow your search.
8
If the item is correct, enter the replacement text in Replace with and select the
Replace or Replace All button to change the event text.
138
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Disabling and enabling events
The events you define are automatically enabled. If you may disable an event(s) in a
work object, if needed and later enable the event.
To disable or enable an event in a work object:
1
Click the Objects tab.
2
Select the work object to which you want to
enable or disable events.Click the Events tab.
3
Right-click an event, and from the Edit menu,
select Enable Event or Disable Event.
When an event is disabled the event text appears
gray in the Work Object Editor.
You may select multiple events to enable or
disable if needed
.
Note: In Report Manager, when you generate a Work Object Report the Disabled
events are preceded by a semicolon (;), similar to the ini files.
To search for events, see “Searching for events” on page 136.
C HAPT ER 5 / Bu ild ing Ob je ct s
139
Exporting an event list
You can save the list of events or any portion of the list as a file and export it so you can
edit or work with it in the Worklist Editor. You can use this event list with the insert
WORKLIST event and EXCEPTION worklist event in the Worklist Editor to import
the list into another event list or to edit the file.
To export an event list:
1
In the Work Object Editor, click the Events tab.
2
Highlight the events to include in the new event file. Use the [Ctrl] key and click
individual events to select portions of the list, or choose Select All on the Edit
menu.
3
On the File menu, choose Export (selected).
4
Select the directory where you want to place the event list file.
Note: The default directory for worklists is \worklist on the Server’s data drive.
5
Enter the File Name, or select a file name from the list box to overwrite an existing
file.
6
Click Save.
140
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Importing an event list
To import an event list:
1
In the Work Object Editor, click the Events tab.
2
Highlight the event in the current list, which comes either before or after the
imported events.
3
Select one of the following:
•
To import an event before the highlighted event, select Insert Before on
the Add Events menu.
•
To import an event after the highlighted event, select Insert After on the
Add Events menu.
•
To insert the worklist at the beginning of the event list, deselect all events
by choosing Unselect all on the Edit menu.
4
On the File menu, select Import.
5
Enter the File name, or select a file name from the list box.
6
Click Open to insert the worklist after the currently highlighted event.
Note: If you import a worklist into the ESD Files event list, any events other than
SEND FILE, CHECK and SEND, MAKE DIRECTORY, CHECK FILE, and
COMMENT are omitted as the list is imported.
C HAPT ER 5 / Bu ild ing Ob je ct s
n
141
Creating a Group object
Group objects include members, which are previously defined ESD and Worklist
objects.
To add members to a group object:
1
Once you have defined the attributes for the Group object, click the Members tab.
2
Click Assign.
3
Highlight one or more objects to include in this group, then click OK. To make
every item a member of this group, click All Objects.
142
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To remove an object from a group:
1
Highlight the Group object you want to remove on the Work Object Editor
Members page.
2
Click Unassign. The object is removed from the list of objects assigned to the
group.
3
To remove all assigned objects from the group, click Unassign All.
4
Confirm the command by choosing Yes to continue or No to cancel.
n Specifying attributes for an Application object
Specify the Application Attributes when you create an Application object.
To specify attributes for an application object:
1
From the Work Object Editor Objects page, highlight an application object.
2
Click the Application Attributes tab.
3
In the Executable File area, enter the path and file name for the application’s
program file. Click Browse to display a list of files, drives, and directories at the
Server.
Note: Only use the Executable file field for RemoteWare applications.
C HAPT ER 5 / Bu ild ing Ob je ct s
4
5
143
In the Working Dir/Path area, enter the directory or path for the executable file.
In the Command line area, enter the application’s startup command.
•
Use the %u variable to automatically insert the user name in the command
line.
•
Add the %p variable to include the password in the command line.
You define user names and passwords in the Directory Manager program.
n
Choosing members for an Application or
Application Group object
Application and Application Group objects include members, which are previously
defined ESD, Worklist, and Group objects. Application Groups can also include
Application objects as members.
To choose members for an application or an application group object:
1
After you have defined the General and Application Attributes for the object, click
the Members tab.
144
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
2
Click Assign. The Select Application Objects dialog box appears, showing the
Worklist, ESD, and Group objects that are currently defined.
3
Highlight the name of the object(s) that you want to assign to this application or
application group object, then click OK. To assign all of the objects to the group,
click All Objects.
To remove a member:
1
Highlight the object you want to remove.
2
Click Unassign. The object is removed from the list of objects assigned to the
application or application group.
To remove all members:
1
Click Unassign All.
2
Select Yes to continue or No to cancel the command.
C HAPT ER 5 / Bu ild ing O b je cts
n
145
Defining events for Multicast work object
After you have created the Multicast object, you add events to the work object. For
instructions on how to create an object, see “Creating a work object” on page 128.
To define events for a Multicast work object:
1
From the Work Object Editor, highlight the Multicast object.
2
Click the Events tab.
3
To create the event list, click the Add Events menu, then select the event type and
specific event from the submenu.
Note: All events assigned to a Multicast work object are before events. The events to
be run on the Clients can only include: SEND, DELETE, and EXECUTE.
n
4
To enable an option, select the appropriate check box or radio button. Different
paths, execution instructions, and options apply to each event you include in the list.
5
Once you define the event, click Done to return to the event list and continue to
add events.
Enabling and disabling work objects
After you create the objects for your network, you must enable them, so the Server can
process them.
To enable an object:
1
From the Objects list window, highlight the object you want to enable.
2
Click
3
Repeat these steps for each object you want to enable.
Enable.
To keep the Server from processing an object, select it and click
Disable.
146
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Making work object assignments
After you have defined and enabled work objects, you must assigned them to Clients,
sessions, or users in order for the work objects to execute. Assign sessions and/or Clients
to ESD, Worklist, and Group objects. Assign users to Application and Application
Group objects.
Keep these things in mind as you make assignments to work objects:
•
If you assign a Client to an object, the object executes each time the Server
connects outbound to that Client.
•
If you assign a session to an object, the object executes each time the session
runs.
•
If you assign a session and a Client to an object, the object executes only once
per session; however, it also executes when the Client connects but the session does
not run.
Certain conditions may cause objects not to execute. For example, an ESD or
Application object does not execute when you have enabled the No ESD or No
Applications option. Other reasons a work object may fail to execute include:
•
Limit execution to assigned session objects option is enabled
•
Work object is disabled
•
The session is run outside the execution window
•
Limit Object Execution to Client Type(s) option is enabled
•
The object has reached the deactivation time you enabled originally
C HAPT ER 5 / Bu ild ing Ob je ct s
n
You can also
assign sessions to
objects from the
Session Editor’s
Objects page.
147
Assigning sessions to objects
To assign a session to an object:
1
From the Objects page, highlight a worklist, ESD, or Group object.
2
Click the Sessions tab.
3
Click Assign. The Select Sessions dialog box appears, showing the currently
defined sessions.
4
Highlight the sessions to assign to this object and click OK. You can also click All
Sessions to assign all of the sessions to the object.
148
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To unassign a session from an object:
n
You can also
assign Clients from
the Client Profile’s
Objects page.
5
On the Sessions page, highlight the session(s) you want to remove.
6
Click Unassign. The session no longer appears in the list of sessions assigned to the
object.
7
To remove all assigned sessions from the object, click Unassign All. You are
prompted to confirm the command. Choose Yes to continue or No to cancel the
command.
Assigning Clients to objects
To assign a Client to an object:
1
From the Work Object Editor Objects page, highlight a Worklist, ESD, or Group
object.
2
Click the Clients tab.
C HAPT ER 5 / Bu ild ing Ob je ct s
149
3
Click Assign. The Select Clients and Client Groups dialog box appears, showing the
currently defined Clients and Client groups.
4
Choose one of the following:
•
Highlight the Clients or Client groups you want to assign to this object and click
OK.
•
Click All Clients & Groups to assign all of the Clients and/or Client groups
listed to the object.
150
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Assigning users and user groups to applications
To assign a user or user group to an application:
1
From the Work Object Editor Objects page, highlight an application or application
group.
2
Click the Users tab.
3
Click Assign. The list box shows the users and user groups currently defined.
C HAPT ER 5 / Bu ild ing O b je cts
4
151
Choose one of the following:
•
Highlight the users or user groups you want to assign to this object and click
OK.
•
Click All Users & Groups to assign all of the users and/or user groups listed to
the object.
152
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Assigning objects to parents
Use the Parents page to assign Worklist, ESD, and Application object to existing group
objects. The Parents page is used to define the object, assign it to a Group, an
Application, or an Application Group object.
To assign an object to an existing group object:
1
Highlight the name of a Worklist, ESD, or Application object.
2
Click the Parents tab.
3
Click Assign.
4
Highlight the object you want to assign as the parent, then click OK.
5
To unassign an object, highlight the group on the Parents page and click Unassign.
To unassign the object from all of the groups, click Unassign All.
C HAPT ER 5 / Bu ild ing O b je cts
n
153
Filtering the Objects list
Use the Filter menu options to limit the number of work objects to appear on the
Objects page. If you have not applied any filters, the Filter menu heading reads “FilterOFF.” Once you apply a filter, the Filter menu heading reads “Filter-ON,” and the
toolbar indicates which filter you have applied. You can apply more than one filter at a
time. You can save filters you have previously applied to the objects. For a more detailed
explanation of filters, see the RemoteWare Server Reference Manual.
Table 4. Work Object Editor filters
Filter
Toolbar
Button
Action
by Selected Objects
Select Objects dialog box appears. Choose items
from list and click OK. The Objects page displays
only the filtered items
by Object Owner
Select Object Owner Types dialog box appears.
Choose items from list and click OK. The Objects
page displays only the filtered items
by Enabled Objects
Displays only enabled Objects.
by Disabled Objects
Displays only disabled Objects.
by ESD Objects
Displays only ESD Objects.
by Worklist Objects
Displays only Worklist Objects.
by Application Objects
Displays only Application Objects.
by Application Group Objects
Displays only Application Group Objects.
by Group Objects
Displays only Group Objects.
by Multicast Objects
Displays only the Multicast Objects.
154
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To apply one or more filters:
1
In Work Object Editor, click the Objects tab.
2
For each filter you want to apply, click the corresponding toolbar button. The
Objects page displays the list of filtered items.
3
Repeat Step 2 for each filter you want to apply. The Objects page displays a list of
items with all filters applied.
To remove one or more filters:
1
In Work Object Editor, click the Objects tab.
2
For each filter you want to remove, click the corresponding toolbar button.
3
To remove all filters, click
Remove Filters. RemoteWare removes all filters
and all items appear in the list box.
To save a filter or combination of filters:
1
In Work Object Editor, click the Objects tab. A filter or filter combination must be
active in order for you to save it. To verify the filter or filter combination is active,
ensure the Filter menu heading reads “Filter-ON.” To verify which filters are active,
open the Filter menu; you will see a check mark next to any active filters.
2
On the Filter menu, select Write Filters.
3
Enter a file name and click Save.
To use a saved filter:
1
In Work Object Editor, click the Objects tab. You do not have to disable active
filters before you apply a saved filter.
2
On the Filter menu, select Read Filters. The Select Filter File dialog box appears.
3
Select the saved filter you want to apply to the list and click Open. The filter is
applied to the current objects list.
C HAPT ER 5 / Bu ild in g O bje cts
n
155
Copying, deleting, and renaming objects
Use the copy, delete and rename options to manage your objects list. To save time when
you are defining similar objects, copy an object and edit the copy. The copied object
retains the complete original object definition, including assignments.
To copy an object:
1
In the Objects list, highlight the object you want to copy.
2
Click
3
Enter a name for the copy, then click OK. The copied object appears in the Objects
list.
Copy. The Copy dialog box appears.
To delete an object:
1
Highlight the object you want to delete in the Objects list.
2
Click
3
Select Yes to delete the object or No to cancel the command.
Delete. You are prompted to confirm the command.
To rename an object:
1
In the Objects list, highlight the object you want to rename.
2
On the File menu, select Rename.
3
Enter a new Name for the object, then click OK. The object appears in the Objects
list with the new name.
156
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Using Worklist Editor
Use Worklist Editor to create and edit worklist files. A worklist is a sequence of events
that resides in an external file (generally with the .evf extension). The worklist file is a
versatile method to edit and access events. After you have created or edited your
worklist files, bring them into Work Object Editor by:
•
Using the Insert Worklist or Exception Worklist events
•
Importing a worklist into the Events page.
To create a worklist file:
1
In the RemoteWare Menu, double-click the
2
Click
New to begin a new worklist.
Work List Editor icon.
C HAPT ER 5 / Bu ild ing O b je cts
n
The dialog box
varies based on the
type of event
selected.
3
Click Add Events, select the event type and the specific event from the menu.
4
Enter the applicable information and select the options specific to the event.
157
Different paths, execution instructions, and options apply to each event. The valid
options for an event appear in dark type and invalid options are dimmed.
Note: Byte Level Differencing is available for the SEND and GET events. This
feature detects differences between file versions at the Server and the Client
and sends only the differences to the Client or Server, which reduces the time
required to update files and software.
n
For a complete
description of events
and available
options, refer to
Appendix A,
“Events,” of the
RemoteWare Server
Reference Manual.
5
After you defined the event, click Done. You may continue to add events.
158
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
6
On the File menu, select Save As to save the worklist.
7
Enter a file name for the worklist and select the directory in which to save it, then
click Save.
Inserting events
You can insert events into an existing worklist.
To insert an event:
1
From the Worklist Editor, highlight a worklist event.
2
Select one of the following:
3
•
To add an event before the highlighted event, select Insert Before on the
Add Events menu.
•
To add an event after the highlighted event, select Insert After on the
Add Events menu.
On the Add Events menu, choose the event type you want to add.
C HAPT ER 5 / Bu ild ing O b je cts
159
Copying, pasting and deleting events
•
To copy one or more events already included in the list, highlight the event or
events and click
Copy. After you copy the event, you can paste it into the list.
The copied event(s) are stored in the clipboard until you copy (or cut) another
event.
•
To paste events, highlight the event that will come before the copied event, then
select Paste on the Edit menu. The Worklist Editor inserts the pasted events after
the highlighted event.
You can delete events two ways:
•
Remove events from the list, but keep a copy in the clipboard. Highlight the
event or events and select Cut on the Edit menu. The events are removed from the
list, but are saved in the clipboard.
•
Permanently delete events from the list. Highlight the event or events, then
click
Delete.
160
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Exporting an event list
You can export a worklist to Work Object Editor, where you can assign it to Clients or
sessions, assign members or parents to it, or import it into another worklist event.
To export an event list:
1
On the Worklist Editor list of events, highlight the events to include in the new
worklist file. You can use the [Ctrl] key and click individual events to select portions
of the list or choose Select All on the Edit menu.
2
On the File menu, select Export (selected).
3
Enter a name in the File Name field, or highlight a file name in the left list box to
overwrite an existing file. Click OK.
The default directory for worklists is \worklist on the Server’s data drive.
C HAPT ER 5 / Bu ild ing Ob je ct s
161
Importing an event list
You can import event lists from Work Object Editor in order to edit them, or to add
events and create a new work object.
To import an event list:
1
In the Worklist Editor, highlight the event in the current list that will come before
the imported events. The imported event appears in the list after the highlighted
event. To insert the worklist at the beginning of the event list, select Unselect all
on the Edit menu before you import the list.
2
On the File menu, select Import.
3
Enter the event file name in the File name field, or highlight a file name in the list
box, then click Open to insert the worklist after the highlighted event.
ESD Auto Apply
ESD (Electronic Software Distribution) is used by the RemoteWare system to keep
files and programs at the RemoteWare Client fully functional. If a Client has out-of-date
files or is missing a critical system file, the RemoteWare system ESD downloads and
replaces the affected file(s). This restores the client to a fully operational state. In most
cases, the ESD download must be to the Client system in order to complete the
process.
For complete information about ESD Auto Apply, refer to Chapter 3 - Preparing for
Communications in the RemoteWare 32-Bit Windows Client User’s Guide.
162
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
6
6RemoteWare
Defining and Scheduling Sessions
Use Session Editor to schedule and organize work objects and connections with Clients.
You can create sessions to define when and how work objects execute at a specific time,
or for a Client connection.
This chapter includes:
• View and create a session
• Understand the different scheduling methods
• Assign Clients and work objects to the session
• Monitor sessions
• Filter sessions
164
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Creating sessions
Use Session Editor to create and edit sessions, as well as assign them to Clients and
control how they execute. To create a session, you begin at the Sessions page in Session
Editor. Once you create the session, you set the session schedule.
To create a session:
1
In RemoteWare menu, double-click the
Editor main window appears.
Session Editor icon. The Session
If you are setting up sessions on this RemoteWare system for the first time, the
Session Editor lists system-defined sessions such as the Sample Session and the
RWS Default Inbound sessions.
2
Click
New. The Create a new Session dialog box appears.
3
Enter a unique name for this session, then click OK. The Schedule page appears.
Go to the next section to set this session’s schedule.
C HAPTE R 6 / D ef inin g a nd Sc he du lin g Se ss ions
165
Setting the session schedule
Use the Schedule page to set the session and schedule types.
To set a session schedule:
1
On the Sessions page, highlight the session for which you want to set a schedule.
2
Click the Schedule tab.
The session and schedule types determine the options available on this property
page. In the Session Type area, select the session type: Inbound, Outbound, Both,
Process Only, or Multicast (if licensed for Multicast).
Note: You can change the Session Type only if the session is disabled and has no
Clients assigned to it.
3
In the Schedule Type area, select the schedule type describing how often the
session will occur. If you chose Inbound session in Step 1, this box is disabled.
4
Depending on the Schedule Type, select one of the following options:
•
Fixed session. Select the Repeat Session option that determines the time
interval between session executions. If you select Every n Weeks, you must
select at least one day of the week from the check boxes.
Add dates to the Except On list box to prevent the session from running on a
particular date.
•
Calendar session. Use the Add Date and Delete Date buttons to specify
exact execution dates and times.
166
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
•
Dependent session: Select the Depends on session button. The Depends on
Session dialog box appears.
Choose the session whose schedule this dependent session monitors. Click OK.
Select one or more of the four conditions the dependent session uses as criteria
to execute.
Note: Dependent sessions execute at least one hour apart because the minimum
session execution window is one hour. Dependent sessions scheduled less than
an hour apart will not execute at the expected time and/or frequency.
5
For Fixed sessions, specify a Start Session time and date. The Enter Date and Time
dialog box appears.
Enter a date and time, then click OK to return to the Schedule page.
6
Set the Session Priority value if you want this session to be scheduled first (when
other sessions are waiting for the same resource), or to take advantage of resources
that are marked for a specific priority.
7
To set a time limit for how long the Server tries to make a connection with a Client,
use the Stop trying outbound calls after n hour(s) field.
8
If you selected the Both session type in Step 3, the Do this session early if a
Client calls within n hour(s) before scheduled outbound start time option is
available. Set this field to allow the session to run if the Client calls the Server
within a specified time period. The number in this field signifies the hours before
the Start Session time.
C HAPT ER 6 / D e finin g a nd Sche d ulin g Se s sion s
9
167
Select the Enable Retries check box to allow the Server to call again in the event
of a failed session. You can also enable retries for Inbound sessions. Once you’ve
enabled retries:
•
In the Interval spin box, set the time interval for the retry.
•
In the Number of retries spin box, set the value to one greater than the
number of retries to prevent an alternate resource from being used on any
retries.
•
In the Alternate resource on retry # spin box, select on what retry an
alternate resource should be used.
Assigning objects to a session
After you have set the schedule for a session, assign work objects that will execute when
the session runs.
To assign an object to a session:
1
From the Session Editor Sessions page, highlight the session you want to execute.
2
Click the Objects tab. The Objects property page appears.
Note: This page only lists the objects assigned to the session. Additional objects,
assigned to the Client or the user at the Client, may execute when the session
runs. For information about how to keep the additional objects from executing,
see “Limiting session activity” on page 172. The Schedule Manager Detail
window lists all objects that will and will not be executed.
168
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
3
Click Assign.
4
Complete one of the following steps:
•
Highlight the name of the object(s) that you want to assign to this session and
click OK.
•
Click All Objects to assign all of the objects listed to the session.
To unassign an object from a session:
1
From the Session Editor Sessions page, highlight the session you wish to change.
2
Click the Objects tab.
3
Complete one of the following steps:
•
Highlight the object you want to unassign, then click Unassign. The object is
removed from the list of objects assigned to the session.
•
To remove all assigned objects from the session, click Unassign All. Choose Yes
when prompted to remove the assignment or No to cancel the command.
C HAPT ER 6 / D e finin g a nd Sche d ulin g Se s sion s
169
Assigning Clients to a session
1
On the Session Editor Sessions page, highlight the session to which you want to
assign a Client.
2
Click the Clients tab.
3
Click Assign. appears.
4
Complete one of the following steps:
•
Highlight the name of the Client(s) or Client group(s) that you want to assign to
this session, then click OK.
•
Click All Clients & Groups to assign all of the Clients and/or Client groups
listed to the session.
170
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Setting up RemoteWare Multicast session
A Multicast session is similar to a RemoteWare Process Only session. Files are
transferred to those Clients who are listening during the session, only one remote
connection is required. A Multicast session is scheduled and runs only once. This
information applies only if you are licensed for Multicast.
Clients who should receive files are assigned to the Multicast session through regular
assignments.
Note: A RemoteWare Server can execute only one Multicast session at a time and only
one Multicast session per cluster.
To create a new session:
1
From the RemoteWare Menu, double-click the Session Editor icon.
2
Click New.
3
Enter a unique name for this session, and click OK.
To set the session type and schedule:
1
Click Session Type Multicast.
2
Click OK.
3
Select a Schedule Type.
4
Select Schedule Options.
To enable the session:
1
Click the Sessions tab.
2
Right-click the new Multicast session and choose Enable.
Assigning Multicast work object to the session
Assign the Multicast work object so it executes during the session. This information
applies only if you are licensed for Multicast.
Note: Only Multicast work objects can be assigned to Multicast Clients.
To assign Multicast work object to the session:
1
In Session Editor, select the Multicast session.
2
Click the Objects tab.
3
Click Assign.
C HAPT ER 6 / D e finin g a nd Sche d ulin g Se s sion s
171
4
In the View drop down box, select Objects (MC) to view only the Multicast work
objects.
5
Select the Multicast work objects you want to execute during the session.
Note: If you assign work objects that are not Multicast work objects, only the "Before"
events execute.
6
Click OK. The Objects property page displays the assigned work object.
Assigning Clients to Multicast session
To indicate which Clients are to receive the multicast files, assign these Clients to the
Multicast session. This information applies only if you are licensed for Multicast.
To assign Clients to Multicast Session:
1
In Session Editor, select the Multicast session.
2
Click the Clients tab.
Note: If you assign a Client to receive Multicast files, who does not have Multicast
enabled then the transfers to that Client fail with no acknowledgements.
3
Click Assign.
4
Select Clients or Client groups you want to assign to this object.
Or
Click All Clients & Groups to assign all the Clients and/or Client groups to the
object.
5
Click OK. The Clients or Groups display in the Clients tab.
Important: Clients who need to receive files should be assigned to the
Multicast session as shown in these steps.
172
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Limiting session activity
Use the Options page to limit session activity by assigned session work objects, by
Application objects, or ESD objects.
To limit session activity:
1
On the Sessions page, highlight the session you want to limit.
2
Click the Options tab. The Options page appears.
3
Complete one of the following steps:
•
Select the Limit execution to assigned Session objects check box to allow
only this session to run during a communication session.
•
Select the No Applications during Session check box to prevent Application
work objects from executing during this session.
•
Select the NO ESD during Session check box to prevent ESD work objects
from executing during this session.
C HAPT ER 6 / D e finin g a nd Sche d ulin g Se s sion s
173
n Enabling and disabling sessions
After you create the sessions for your RemoteWare system, you must enable them so
that the Server will process them.
To enable a session:
1
From the Sessions page, highlight the session you want to enable.
2
Click
3
Repeat these steps for each session you want to enable.
Enable Session.
To remove a session from the session schedule:
1
Highlight the session you want to disable.
2
Click
3
Repeat these steps for each session you want to disable.
Disable Session.
n Changing a session schedule
To change the Schedule Type, you must first disable the session and remove any Client
assignments. The steps in this section change a session from a calendar to fixed
Schedule type or vice versa.
To change a session schedule:
1
On the Sessions page, highlight the session you want to change.
2
Click
3
Click the Clients tab.
4
Make note of the assigned Clients, then click Unassign All. Confirm the command
by selecting Yes.
5
Click the Schedule tab.
6
Change the Schedule Type and specify any parameters necessary for the new type.
For more information, see “Setting the session schedule” on page 165.
7
Click the Clients tab to reassign the session to the Clients. For more information,
see “Assigning Clients to a session” on page 169.
8
Return to the Sessions page, and click
Disable Session.
Enable Session.
174
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Copying, renaming, and deleting sessions
When you are defining similar sessions, you can copy a session and edit the copy to save
time. The copied session includes the schedule, objects, assignments, and options of the
original session. You can also rename sessions, or you can delete them when you no
longer need them.
To copy a session:
1
From the Sessions page, highlight the session you want to copy.
2
Click
3
Enter a name for the copied session, then click OK.
4
If you had assigned the original session to Clients, you are prompted to keep the
assignments for the copy. Choose Yes to preserve the original assignments in the
copy or No to delete the original assignments.
Copy. The Copy the selected Session dialog box appears.
The copied session appears on the Sessions page. The copy is Disabled by default.
To rename a session:
1
From the Sessions page, highlight the session you want to rename.
2
On the File menu, select Rename. The Rename the selected Session dialog box
appears.
3
Enter a new name for the session, then click OK. The session appears on the
Sessions page with its new name.
To delete a session:
1
From the Session Editor Sessions page, highlight the session you want to delete.
2
Click
3
Select Yes when prompted to delete the session, or No to cancel the command.
Delete.
C HAPTE R 6 / D ef inin g a nd Sc he du lin g Se ss ions
n
175
Viewing current and scheduled sessions
Use Schedule Manager to view the Server’s Scheduler, which is the program that
manages and starts sessions at scheduled times.
To display the Schedule Manager:
In RemoteWare Menu, double-click the
Manager main window appears.
Schedule Manager icon. The Schedule
This window lists each enabled Outbound or Inbound/Outbound Session scheduled to
an enabled Client. In addition, the window displays active sessions.
Use the Schedule Manager sparingly in situations that involve large numbers of
scheduled sessions (for example, more than 2,000) because it can affect the Server’s
performance. Minimize or close the Schedule Manager window when you are not using
it.
176
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Changing the screen refresh interval
The Schedule Manager window updates information every 20 seconds.
To change the refresh interval:
Select one of the following options on the View menu:
•
Set Refresh Time allows you to set the update interval.
•
Refresh Automatically is a menu option that in its disabled state will not update
the window until you enable it or use the Refresh option. Use this command when
you want to study the current window.
•
Refresh updates the window immediately, listing outstanding changes to scheduled
sessions.
The default refresh interval of 20 seconds is restored when you exit and re-enter the
Schedule Manager.
Viewing details of the session
Use the Session Detail to view additional information about a particular session in the
Schedule Manager window. For example, when a session shows remaining retries, you
can find out exactly how many times the session has been attempted and how many
retries remain.
To display Session Detail:
1
Double-click a session name.
C HAPT ER 6 / D e finin g a nd Sche d ulin g Se s sion s
177
The Session Detail window contains three or four property pages, depending on the
session type. See the RemoteWare Server Reference Manual for more information
on the Session Detail window.
2
Click OK to return to Schedule Manager.
178
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Filtering the list of sessions
In both Session Editor and Schedule Manager, you can use the Filter menu or toolbar
buttons to display only those sessions you want to view. You can also apply more than
one filter at a time. Filter-ON appears in the menu bar and the toolbar indicates which
filter is in use when a filter setting is active. The filter choices are listed in the “Session
Editor” and “Schedule Manager” chapters of the RemoteWare Server Reference
Manual.
You apply several types of filters:
•
Filters requiring a selection. After you select a filter, choose one or more item
types to use as the filter criteria. Click OK. The items matching the filter criteria
appear.
•
Filters that are immediately applied. When you apply a filter such as Enabled
Sessions, you do not have to set any other criteria. Once you select one of these
filters, it remains active until you turn it off.
•
Removing one or more filters. To remove a single filter in the active state, click
the filter’s toolbar button. To remove any other filter, click
Remove Filter.
To remove all filters, select Remove All Filters on the Filter menu.
n
•
Saving a filter or combination setting for later use. The Write Filters option is
available when a filter is active. On the Filter menu, select Write Filters, specify a
file name, and click OK.
•
Retrieving and using a saved filter. You can apply saved filters over the current
list, even if filters are active. The current filter set changes only if the same setting
exists in the retrieved filter. On the Filter menu, select Read Filters, select a filter
file from the list, and click OK.
Changing session execution times
Use Schedule Manager to change how one or more scheduled sessions execute. You
can also control the scheduled sessions by disabling a Client in the Client Profile or a
session in the Session Editor:
•
Disabling a Client removes the Client temporarily from any sessions assigned to
it. Use this option when the Client is not processing communications properly or
you are making some changes at the Client site that affect the sessions.
•
Disabling a session removes all instances of that session from the Schedule
Manager. Use this option to change a session or to remove one or more instances of
the session that are permanently in a Blocked state.
See the RemoteWare Server Reference Manual for a description of the Command menu
C HAPT ER 6 / D e finin g a nd Sche d ulin g Se s sion s
179
options.
Selecting the current server
If you are using Clustered Servers, you can select Select Current Server on the
Command menu to display the session status and activity on any Clustered Server in
your system. From this view, you can change the status of sessions on different Servers.
Turning the Scheduler on and off
You may need to stop the Scheduler. For example, you may need to update a few
sessions that are about to run, or start some maintenance on the Server. Use the
Scheduler-ON menu to stop and start the Scheduler.
When you turn the Scheduler off, currently active sessions will continue to process and
complete. However, no additional sessions will become active. Depending on the
complexity of your sessions, they may take a few moments to finish and for the queue of
active sessions to empty.
To stop the Scheduler:
On the Scheduler menu, select Suspend on Current Server. For Clustered Servers,
only the currently displayed Scheduler stops.
For Clustered Servers, you may want to select Suspend on All Servers to stop every
Scheduler in the system.
To restart the Scheduler:
On the Scheduler menu, select Resume on Current Server to allow the Scheduler on
the current Server to execute sessions.
For Clustered Servers, select Resume on All Servers to start all Schedulers at the
same time.
180
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
7
7RemoteWare
Connecting Interactively
Use Interactive Session to work with Client and Server file systems in real time, without
defining a set order of events in a work object. You can immediately contact any enabled
Client, enter any sequence of events, and view and manipulate the Client’s graphical
user environment.
This chapter includes:
• Start Interactive Session to connect to a Client
• Customizing Interactive Session window
• Use Session’s Remote Console feature
• Set up Session’s Remote Control feature
182
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Interactively connecting to a Client
When you open Interactive Session, it begins the set of procedures necessary to connect
to an enabled Client.
To start the Interactive Session program and connect to a Client:
1
In the RemoteWare Menu, double-click the
Interactive Session icon. This
icon is located in the All Utilities or Server Operations group. The Select Client
dialog box appears.
2
In the Select Client dialog box, select the Client you want to contact, then click OK.
If you click Cancel, you will not connect to a Client at this time, but you still can
type Server commands.
3
If Clients have alternate resources defined in their Client Profile, the Select
Resource to Use dialog box appears. Select a resource and click OK.
CHAPTER 7 / Connec ting Int eractively
4
183
Interactive Session initiates an outbound connection to the Client. You can
interrupt the connection by clicking
Disconnect on the toolbar.
Interactive Session prints a verification when it connects with the Client.
n
The CHKDSK
command reports the
operating system
version as OS/2
version 2.4 when the
Client is running on
OS/2 version 4.
5
Type a command in the Command Prompt field, or select a command on the
Client Commands or Server Commands menu. For more information on the
available commands, see Reference Manual.
6
Click Execute to run the command.
Using literals in pathnames
Within Interactive Session, you can pass a literal string for pathnames and filenames.
Literal strings are text that contain reserved characters, such as wildcards, spaces, and
punctuation. A Server encountering a literal string does not check to see if the string is
valid; it uses the string as is.
To specify a literal string, use double quotes (“ ”) to set off the pathname and filename.
The ending double quote is optional in the last parameter of the command line. The
double quote prevents the Server from adding the default drive or path and allows you
to use mixed case, other device names, long filenames, or filenames that include
reserved characters or spaces.
184
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Use the following guidelines when specifying literal strings within sessions:
•
You may use placeholders within a literal string. The placeholder will not be sent as
a literal string. For example:
GET FILE “\<ClientName>\TheFile
The system inserts the actual Client name. <ClientName> will not be passed as a
literal string.
•
The end quote is needed only when the command line is ambiguous due to long
filenames or spaces. For example:
COPY “This is file 1” “This is the copy”
Using long filenames
You can use filenames of up to 255 characters for any Server and Client computer
operating systems supporting the use of long filenames. Files can be renamed to shorter
or longer names during a file transfer, copy, or rename operation. For example, SEND
“MY LONG FILE NAME” MYFILE.DAT would copy the Server file MY LONG
FILE NAME and rename it to the short MYFILE.DAT name on the Client.
Selecting a view
By default, when you start an Interactive Session, the selected Client’s “view” or prompt
appears, so commands you enter at the command prompt affect the Client computer.
However, you can change to the Server view so that commands you enter at the prompt
affect the Server.
To change the view:
At the right of the command prompt area, select one of the following two options:
•
Client
•
Server
The view updates to reflect your choice. All new commands will take place on the
selected machine.
CHAPT E R 7 / Co nn ec ting Int er ac tive ly
185
n Customizing the Interactive Session window
Within Interactive Session, you can use several commands to customize the appearance
of the Interactive Session window. You can control the background color of the output
window, the color and font of the different types of commands and responses, and
whether the toolbar or status bar displays in the window. You can also switch between
the Server and connected Client views.
Changing colors and fonts
You can change the color of the output screen so that different types of commands and
responses appear in differently colored text. For example, you could specify that all
Server commands appear in blue text, while all Client commands appear in purple text.
You could also configure the colors so that all error messages automatically appear in
red text. This way, you can see at a glance the types of commands and responses
displayed on screen.
To change the colors of the output screen and the command text:
1
On the View menu, select Set Colors. The Set Colors dialog box appears.
The first five color fields correspond to the following text types:
2
•
Server commands
•
Server results
•
Client commands
•
Client results
•
Errors
To select a color for a command, click the down arrow to the right of the each field
and select a color. The text for each command appears in the appropriate color in
the text box on the left side of the dialog box, so you can see your changes before
you finalize them.
186
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
3
To select the background color, click the down arrow at the right of the Background
field and select the desired background color. The text box refreshes so that you can
preview your color choice.
4
Click OK to save your color choices and return to the main window.
Note: Color selections are valid only until you exit Interactive Session. When you
restart Interactive Session, the output window colors return to the default
colors.
To change the font used in the output window:
1
On the View menu, select Set Font.
2
Use this standard Windows dialog box to select the font, style, size, and script you
want to use in the output window.
3
Click OK to save your font choices and return to the main window.
Note: Font selections are valid only until you exit Interactive Session. When you
restart Interactive Session, the output screen font settings return to the defaults.
CHAPTER 7 / Connec ting Int eractively
n Storing contents of the output screen
187
Sometimes you may want to save the contents of the Interactive Session output screen
to use in the future.
To save the contents of the output screen:
1
Click
Capture on the toolbar.
The CAPTURE command is automatically inserted at the Command Prompt.
2
Following the CAPTURE command, enter the path and file name to save the
contents. For example, to save the contents in a file named session1.txt in the
Sessions directory, the command prompt should read:
CAPTURE C:\Sessions\session1.txt.
188
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
3
Click Execute or press [Enter]. The output screen records the results.
CHAPTER 7 / Connec ting Int eractively
n
189
Using Remote Console
Using the DOS and OS/2 Remote Console of Interactive Session, you can connect to a
DOS or OS/2 Client and remotely run text-based applications that are stored on the
Client. Any keystrokes entered at the Server and Client are shared.
For example, if you want to start a text-based spreadsheet application stored on a Client,
you would use Remote Console on the RemoteWare Server to execute the program.
Everything that appears on the Client’s screen also appears on the RemoteWare Server’s
screen.
Note: Remote Console supports all keystrokes on a U.S. English keyboard except for
Print Screen, Scroll Lock, and Break and the [ALT] key in combination with
number pad keys. Remote Console supports any text-based application that runs
on the same console as the RemoteWare Client Kernel. It does not support
video graphics, only text and text color attributes. Remote Console can only
capture screens in 25 line mode, not in 43 or 50 line mode.
Remote Console’s time-out feature automatically terminates the Remote Console
session after five minutes of inactivity. If no screen updates are sent to the Server for
more than five minutes, Remote Console stops and the Interactive Session view returns.
Once Remote Console ends, the time-out for Interactive Session is reset. Interactive
Session disconnects the Client after five minutes of inactivity.
Some DOS commands, for example DOS COPY CON, lock out other processes until
the DOS command completes. If the command takes a long time to end, the
communications session may be dropped, depending on the RemoteWare protocol
assigned to the Client.
190
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To start Remote Console:
1
Initiate an outbound connection to a DOS or OS/2 Client through Interactive
Session.
2
Once the Server has successfully connected to the Client, click
Console on the toolbar.
Start Remote
Note: For Remote Console to run, the Kernel must be running in a full screen DOS
or OS/2 Session. If the application running on the Client changes to graphics
mode while the Server Administrator is using Remote Console, Remote
Console ends automatically and returns to the Interactive Session view.
CHAPTER 7 / Connec ting Int eractively
191
Once Remote Console starts, the bottom portion of the Interactive Session main
window is replaced by a black text screen.
You will see the console screen for the currently running RemoteWare Client
Kernel. All Interactive Session menu commands and toolbar buttons except the
Stop Remote Console command are disabled when Remote Console is active.
3
To stop Remote Console, select Stop Remote Console on the Command menu.
192
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
The DOS window closes and the Interactive Session view returns. You can continue
to send commands to the Client as you normally do. You do not terminate the
Interactive Session when you stop Remote Console.
Using Remote Console with DOS Clients
Using Remote Console, you can connect to a DOS Client and remotely run text-based
applications that are stored on the Client.
To start a Remote Console session with a DOS Client:
1
Start Interactive Session and initiate an outbound session to a DOS Client. For
detailed instructions on using Interactive Session, see “Interactively connecting
to a Client” on page 182.
2
Click
Start Remote Console on the toolbar.
Note: If the Client is not in text mode, an error message stating that the Remote
Console session cannot run appears at the Server. If the application at the Client
changes to graphics mode while you are using Remote Console, Remote
Console will close automatically. In addition, Remote Console can only capture
screens in 25 line mode—not 43 or 50 line mode.
What appears on the Client’s screen now also appears on the Server’s screen.
Both the Server and Client user can enter commands or input data required to run
the program.
CHAPTER 7 / Connec ting Int eractively
193
Be careful when you enter DOS commands in Remote Console. DOS will “shut
out” other activities until the DOS command you enter completes. If the command
takes a long time to complete, the connection between the RemoteWare Server and
the Client may be dropped. Do not enter the DOS COPY CON command and do
not use [Ctrl][S] to pause a DIR or TYPE operation while using Remote Console.
3
To end a Remote Console session, select Stop Remote Console on the Command
menu. This does not end the Interactive Session. The Interactive Session view
returns and the Interactive Session continues.
Using Remote Console with OS/2 Clients
Remote Console supports full screen video input/output (VIO) for both OS/2 text-based
and graphical Clients. When the OS/2 Client software is installed at the Client, the
Startup.cmd file is automatically modified to include the START /FS OS2NODE
command and the START /FS OS2TNODE command.
If the OS/2 Client software is already installed, change the DETACH statement in the
Startup.cmd file to Start /FS. This command starts the Client in a full screen group.
Note: You cannot use Remote Console to monitor pop-up windows on OS/2 Clients.
To prevent error message pop-up windows (such as those that appear when you
are trying to access a disk drive that does not have a disk in it) from appearing at
the Client, add the AUTOFAIL=YES command line to the Client’s Config.sys
file.
194
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To start a Remote Console session with an OS/2 Client:
1
Start Interactive Session and initiate an outbound connection to an OS/2 Client.
2
Click
3
To monitor a specific program at the Client and have it start automatically, use the
–c<command> option in conjunction with the START /FS OS2NODE or START
/FS OS2TNODE command to start the program instead of the command
interpreter. For example, to start a program called “Local Server,” you would enter:
Start Remote Console on the toolbar.
START /FS OS2NODE –c “LOCAL SERVER”
Note: You must enter the correct path for the command line. The OS/2 Client must be
started from the same drive as the \Nodesys directory.
4
To end a Remote Console session, select Stop Remote Console on the Command
menu. This does not end the Interactive Session. The Interactive Session view
returns and the Interactive Session continues.
CHAPT E R 7 / Co nn ec ting Int er ac tive ly
n
195
Troubleshooting Remote Console
Use the information in Table 5, “Troubleshooting Remote Console,” to identify and
correct problems using Remote Console.
Table 5. Troubleshooting Remote Console
Error
Action to resolve the problem
Create Remote Console Thread failed.
This error message indicates that your system is
running low on resources (memory, threads, handles,
etc.) If this error occurs, close some open applications
and retry Remote Console. If this is unsuccessful,
reboot the RemoteWare Server.
The Client screen is not in a supported
text mode.
This error message indicates that the Client screen was
not ready. Retry Remote Console. If the error still
occurs, it may indicate the Client is running in another
unsupported non-text mode.
The Start Remote Console command
is disabled.
Verify that the Client is either a DOS or OS/2 Client
and that you have initiated an Interactive Session with
the Client.
Remote Console is not supported at this
Client.
Verify that the Client is either a DOS or OS/2 Client.
Disconnecting from the Client
In Interactive Session, you can disconnect with the Client by:
•
Typing DISC at the command prompt.
•
Selecting
•
Going to the Command menu and selecting Disconnect.
Disconnect tool from the toolbar.
Interactive Session verifies that you want to disconnect before performing the action.
196
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Understanding Remote Control
Use Remote Control to view and manipulate the Client’s environment from a graphical
interface, exactly as it appears at the Client. With Remote Control, you are not
restricted to using typed commands; you can use the keyboard and mouse to partially
take over the Client. A Client user may operate the Client computer, but only if you are
not currently intervening.
Remote Control can operate over any asynchronous or network protocol, but only with
the 32-bit Windows 95/98, Windows NT, and Windows 2000 Clients. Asynchronous
modem users should understand the setup instructions presented later in this section
for setting up a Remote Control modem.
Note: While the use of NetBIOS for Remote Control sessions is supported, Remote
Control connections using the NetBIOS protocol are noticeably slower than
those using other protocols.
Setting up Remote Control
Each time you start Interactive Session to connect to a Client, the program verifies it
has the ability to use Remote Control. To run Remote Control, the Client must have the
following:
•
32-bit Windows Client
•
Remote Control work object assigned and installed
When you assign and deliver the Remote Control work object to a Client, it
automatically installs the pcAnywhere software on the Client computer. pcAnywhere
allows the Server to communicate with the Client during a Remote Control session.
Note: When running the Client as a service, in order to properly utilize the Remote
Control feature, both the pcAnywhere host service and the client service must
be marked to interact with the desktop. This can be accomplished from the
control panel services applet. Failure to do so may cause loss of remote control
capabilities and, in some cases, the Server screen may appear blank although
there is a remote connection.
Note: Symantec does not support pcAnywhere 9.2 (Remote Control) on Microsoft’s
Terminal Server.
CHAPTER 7 / Connec ting Int eractively
197
Assigning the Remote Control work object to Clients
To assign the Remote Control work object to Clients:
1
From the RemoteWare Menu program, open the Work Object Editor program.
2
On the Objects tab, select either of the following work objects: RWS pcAnywhere
Client Delivery - Full or RWS pcAnywhere Client Delivery - Staged.
3
Click the Clients tab.
4
Click the Assign button.
5
Select the Client(s) that will use Remote Control. Click OK when done.
6
Click the Objects tab and select the RWS pcAnywhere Client Installation work
object.
7
Repeat steps 3-5 to assign the Client(s) on which to install pcAnywhere.
8
Close the Work Object Editor program. pcAnywhere is silently installed once the
Remote Control object has been assigned, the session executes, and the machine
reboots.
Important: The pcAnywhere installation process at the Client requires that the
Client reboot. Because this installation process is “silent” and does not require
any user intervention, the Client machine may reboot automatically.
Setting up Remote Control modems
•
If you use the RemoteWare Server computer to launch Remote Control, no
additional hardware is required. The RemoteWare Server uses its existing modem
to start both the Interactive Session and the Remote Control session with the
Client.
•
If you use a RemoteWare Workstation to control the RemoteWare Server, the
Workstation computer requires a TAPI modem for the Remote Control session.
The Workstation instructs the modem at the Server to launch the Interactive
Session with the Client, and the TAPI modem at the Workstation contacts the
Client to start the Remote Control session.
•
No hardware changes are required for the RemoteWare Client.
198
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Using Remote Control
Once you have established a connection with the Client, you are ready to use Remote
Control.
To start a Remote Control session:
n
While the use of
NetBIOS for Remote
Control sessions is
supported, Remote
Control connections
using the NetBIOS
protocol are
noticeably slower
than those using
other protocols.
1
On the Command menu, select the Remote Control. pcAnywhere™ attempts to
connect to the Client. You will see the following screen.
2
If you are using SPX as your connection resource to connect to the Client, the
pcAnywhere Waiting dialog box appears. From the list provided, select the
computer you want to remotely control. For more information on this screen, refer
to the pcAnywhere™ documentation.
3
When the connection is complete, your Server shows the contents of the Client’s
window. You can now complete your tasks at the Client.
The pcAnywhere™ program adds a toolbar to your screen. For more information on
each option, refer to your pcAnywhere documentation.
CHAPTER 7 / Connec ting Int eractively
199
To stop a Remote Control session:
1
On the Server, select the
End Remote Control Session button on the toolbar.
2
Click Yes to confirm that you want to disconnect from Remote Control.
When you end a Remote Control session, you return to Interactive Session. Interactive
Session will still be connected to the Client. For Workstation users, Interactive Session
will no longer be connected to the Client.
200
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
8
8RemoteWare
Using Session Recovery
You can use RemoteWare’s Session Recovery to quickly identify Clients for which
sessions were FAILED, FAILED FINAL, COMPLETED, SUCCESSFUL, or
MISSING. You can also restart failed or missing sessions from within Session Recovery.
This chapter includes:
• Session Recovery’s key features
• Session Recovery’s filters
• View Client details
• Update session data
• Restart and resubmit sessions
• Generate reports
202
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Using Session Recovery
Use Session Recovery to recover and resubmit sessions that failed to run. You can access
all entries logged in your Session History Log in Log Viewer from Session Recovery. By
applying different combinations of filters to these session entries, you can identify
sessions by status—Failed, Failed-Final, Completed, Successful, and Missing—and by
other criteria, such as by Client or Client Group, session name, and time range. Once
you have identified specific Failed-Final and Missing sessions, you can restart all of
them or just selected sessions with the click of a single button.
With Session Recovery, you can better monitor and manage your RemoteWare sessions.
Some typical situations in which you could use Session Recovery include:
•
Identifying missing sessions. If the RemoteWare Server experiences a hardware
failure during an outbound session or if a scheduled inbound session fails to occur,
you can filter the entries in Session Recovery to view only those sessions that did not
run, and then resubmit those sessions for processing.
•
Locating ECF sessions. When the RemoteWare Server experiences a hardware
failure while processing an ECF, you can use Session Recovery to view ECF files,
identify those that did not complete, and then resubmit them for processing.
•
Isolating Failed sessions. When you want to isolate Clients that failed to run a
particular session—a daily polling session, for example—you can use Session
Recovery to identify and quickly resubmit sessions that failed to complete
successfully.
•
Identifying and resubmitting Failed-Final sessions. When a session has been
designated as Failed-Final and you want to resubmit it for processing, you can
display only Failed-Final sessions and resubmit them with the click of a button.
CHAPT E R 8 / Usin g Ses s ion Re cove r y
203
To start Session Recovery:
In RemoteWare Menu, locate and double-click the
RemoteWare Session Recovery main window appears.
Session Recovery icon. The
Using the Client/Session list box
The Client/Session list box displays Client Name, Session Name, Server Name, Start
Time, Duration and Status based on the filters you select. When you first start Session
Recovery, this list box is empty; you must select at least one filter in order to populate
this box. You can apply a number of different filter combinations. For more detailed
information on applying filters, see “Using Session Recovery’s filters” on page 207.
204
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Searching the Client/Session list box
At times, you may need to search the Client/Session list box for a specific session. Use
the Search Client command on the View menu to quickly locate a specific Client in the
Client/Session list. You’ll find this command useful when the Client/Session list box
contains a large number of entries.
To search the Client/Session list box:
n
Tip: Pressing [F3]
on the keyboard also
advances to the next
matching entry.
1
On the View menu, select Search Client. The Search Client dialog box appears.
2
In the Enter Client to search field, enter the name of the Client you want to
locate. This field is not case sensitive; “NWREGION” is the same as “nwregion.”
3
Click OK to begin the search. The first entry that matches the search criteria you
entered is automatically highlighted.
4
If more than one entry matches the search criteria, select Find Next Client on the
View menu to automatically advance to the next matching entry.
Using the Session Recovery status icons
You can quickly determine the status of the sessions using the icons that appear to the
left of each entry in the Client/Session list box.
Table 6. Session Recovery status icons
Icon
Name
Description
Failed
Sessions that are flagged as Failed in the Session History Log in Log
Viewer. Failed sessions are those that failed to connect to the Client
but have retries remaining. This is a yellow icon.
Failed-Final
Sessions flagged as Failed-Final in the Session History Log in Log
Viewer. Failed-Final sessions are those that failed to connect during
the specified time frame and have exhausted all retries. This is a red
icon.
Completed
Sessions that started and ended within the expected time frame but
did not execute all of their events. This is a gray icon.
Successful
Sessions that started and ended within the expected time frame and
executed all events. This is a green icon.
CHAPT E R 8 / Using Ses s ion Re cove r y
Table 6. Session Recovery status icons
Icon
Name
Description
Missing
Indicates the sessions missing from the Session History Log in Log
Viewer. Missing sessions were scheduled but did not start during the
expected time frame, since the Client did not initiate an inbound
session when expected. This is a blue icon.
205
206
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Customizing the Session Recovery window
You can easily customize the Session Recovery main window. You can:
•
Display and hide the toolbar. To alternately display or hide the toolbar at the top
of the main window, select the Toolbar command on the View menu.
•
Display and hide the status bar. To alternately display or hide the status bar at
the bottom of the main window, select the Status bar command on the View menu.
•
Set the display font. To select the font used to
display information in the Client/Session list box,
select Set Font on the View menu. Using the
Windows Font dialog box, you can select the font,
font style, and size for the entries. For instructions
on using the Font dialog box, see your Windows
documentation.
CHAPT E R 8 / Usin g Ses s ion Re cove r y
207
n Using Session Recovery’s filters
To use the Session Recovery program effectively to monitor and maintain your system’s
sessions, you must understand the various Session Recovery filters and how they
operate. Each time you start Session Recovery, you must apply at least one filter; the
Client/Session list box remains empty until you do.
You can use any one of the different types of filters Session Recovery provides to display
only those sessions you want or to quickly determine how many sessions have a
particular status.
Table 7. Session Recovery Filters
Filter
Button
Description
by Status
Filters the Client/Session list by Status code, and displays the
results. The Status code indicates the reason the session failed.
For example, Busy, Client Security, ESD Failure, Invalid Disk
Drive, etc.
by All
Filters the Client/Session list by all sessions based on the
completion field (Successful, Complete, Failed, or Failed Final)
and displays the results.
by Client
Filters the Client/Session list so only sessions executed for
selected Clients or Client Groups appear.
by Session
Filters the Client/Session list so only selected sessions appear.
by Time Range
Filters the Client/Session list so only sessions executed during a
specified time range appear.
208
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Table 7. Session Recovery Filters (continued)
Filter
Button
Description
by ECF
Filters the Client/Session list so only selected Scheduler ECF
files with the extension .ece or .ecb appear.
by Failed
Sessions
Filters the Client/Session list so the only sessions that appear are
those that attempted to connect to a Client but failed and have
one or more retries remaining.
by Failed-Final
Sessions
Filters the Client/Session list so the only sessions to appear are
those attempted to connect to a Client but failed and have no
retries remaining. The Failed-Final filter is applied by default
when you apply the by Client, by Session, by Time Range, and by
ECF filters.
by Successful
Sessions
Filters the Client/Session list so only sessions initiated properly,
executed all defined events, and ended with defined expectations
appear.
by Completed
Sessions
Filters the Client/Session list so only sessions initiated properly,
ended within the defined time frame, but did not execute all of
their events appear.
by Missing
Sessions
Filters the Client/Session list so only sessions missing from the
Session History Log in Log Viewer appear. Missing sessions were
scheduled but did not start within the expected time frame.
Using filter combinations
You can use each of Session Recovery’s filters alone or in combination with other filters.
For example, to view all of the sessions for a particular Client, regardless of the session’s
status or time of execution, you would apply the
by Client filter.
However, if you wanted to see only those sessions that executed during a particular time
period for two specific Clients only, you would use the
by Client filter in
combination with the
by Time Range filter.
CHAPT E R 8 / Usin g Ses s ion Re cove r y
209
This graphic illustrates
how you can use three
different filters in
combination with each
other to narrow in on
the exact information
you need.
In this scenario, the
RemoteWare Server
Administrator first uses
the by Failed Sessions
filter to identify all
Failed Sessions (figure
1).
Then a second filter by
Time Range is applied
to narrow the list to
include only those
sessions which failed
during a specific period
of time (figure 2).
Next, the third filter by
Client is applied to
locate all sessions for a
specific Client that
failed during the
specified time range
(figure 3).
The Display segment in the last image represents the entries to appear in the Client/
Session list box.
210
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Filtering by Status
Use the
by Status option to filter the Client/Session list by the Status code, and
display the results. The Status code indicates the reason the session failed.
To filter by Status:
1
Click
menu.
Filter by Status on the toolbar or select by Status… on the Filter
2
Select the failure codes you want to query. To select multiple failure codes, hold
down the Ctrl or Shift key and select the codes.
The Client/Session list displays all sessions based on the reason the session failed.
Filtering by All
Use the
by All option to filters the Client/Session list so all the sessions based on
the completion field display. The by All option includes: Successful, Complete, Failed,
and Failed-Final sessions.
To filter by All:
1
Click
Filter by All on the toolbar or select by All… on the Filter menu.
The Client/Session list displays all sessions with a Successful, Complete, Failed, and
Failed-Final status.
CHAPT E R 8 / Usin g Ses s ion Re cove r y
211
Filtering by Client
Use the
by Client option to filter sessions associated with one or more Clients or
Client Groups. When you apply the by Client filter, the by Failed-Final filter is also
applied by default. You can remove the Failed-Final filter and apply any of the other
status filters.
To filter by Client:
1
Click
by Client on the toolbar. The Select Clients and Client Groups dialog box
lists all defined Clients and Client Groups.
2
Select the Clients or Client Groups whose session entries you want to display:
3
•
To view only Clients, only Client Groups, or both Client and Client Groups,
select the appropriate item in the View field.
•
To select adjacent entries, click the first entry, press [Shift], and select the last
entry.
•
To select multiple, non-adjacent entries, click the first entry, press [Ctrl], and
select the next entries.
•
To search for a specific entry, enter the search criteria in the Search/Select
box.
•
To display details about a selected entry, click Item Detail.
Click OK.
The Client/Session list displays only sessions for the selected Clients and Client
Groups.
212
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Filtering by Session
Use the
by Session option to filter for specific sessions only. When you apply the by
Session filter, the by Failed-Final filter is also applied by default. You can remove the
Failed-Final filter and apply any of the other filters
To filter by Session:
1
Click
by Session on the toolbar. The Select Sessions dialog box lists all sessions
currently defined in your RemoteWare system.
2
Select the sessions for which you want to view information.
3
•
To select adjacent entries, click the first entry, press [Shift], and select the last
entry.
•
To select multiple, non-adjacent entries, click the first entry, press [Ctrl], and
select the next entries.
•
To search for a specific entry, enter the search criteria in the Search/Select
box.
•
To display details about a selected entry, click Item Detail.
Click OK.
The Client/Session list displays only information for the selected sessions.
CHAPT E R 8 / Usin g Ses s ion Re cove r y
213
Filtering by Time Range
Use the
by Time Range option to filter sessions that executed during a specified
period of time. When you apply the by Time Range filter, the by Failed-Final filter is
also applied by default. You can remove the Failed-Final filter and apply any of the
other status filters.
To filter by Time Range:
1
Click
2
Select one of the following options:
3
by Time Range on the toolbar.
•
Before. Displays all entries for sessions which executed before a specified date
and time. Click the adjacent button to set the date and time.
•
Between. Displays all entries for sessions which executed between two
specified dates and times. Click each adjacent button to set the beginning and
ending date and time.
•
After. Displays all entries for sessions which executed after a specified date and
time. Click the adjacent button to set the date and time.
•
Last. Displays all entries for sessions which executed in the last n days and
hours. Click the adjacent button to select the desired number of days and hours.
Click OK.
The Client/Session list displays only entries for sessions that executed during the
specified period of time.
214
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Filtering by ECF
If you use ECFs (external configuration files) to schedule sessions to Clients and Client
Groups, you can use the
by ECF option to filter only those entries associated with a
selected ECF file. When you apply the by ECF filter, the by Failed-Final filter is also
applied by default. You can remove the Failed-Final filter and apply any of the other
status filters.
n
For more
information on
working with ECFs,
see Appendix B
of the RemoteWare
Server Reference
Manual.
To filter by ECF:
1
Click
by ECF on the toolbar.
2
In the Schedule ECF box, select the Schedule ECF for which you want to display
information.
3
The sessions contained in the selected Schedule ECF appear in the adjacent
Sessions box. Select one or more of the sessions.
4
Click OK.
The Client/Session list displays the selected entries.
CHAPT E R 8 / Using Ses s ion Re cove r y
215
Filtering by session status
n
Tip: To improve
system performance
while displaying
Missing sessions,
apply another filter,
such as by Time or
by Client first, then
apply the by Missing
filter.
Use the five status filters—by Failed, by Failed-Final, by Successful, by Completed, and
by Missing— to display entries only for those sessions with the selected status. For
example, to see a list of all Failed-Final sessions, click
by Failed-Final on the
toolbar. For detailed descriptions of each status filter, see “Session Recovery Filters”
on page 207.
Note: The by Missing filter does not locate missing sessions run previously and for
which a record still exists in the Session History Log in Log Viewer. To locate
these missing sessions, you must use the by Missing filter in combination with
the by Time Range filter. For example, if a Polling session ran on September 1
and September 2 but did not run as scheduled on September 3, the by Missing
filter used alone will not identify Polling as a missing session, because it will find
a record of it in the Session History Log. However, if you use the by Time Range
filter to locate all sessions run after September 2 and then apply the by Missing
filter, Session Recovery will locate the missing Polling session.
Removing filters
To remove all applied filters, click
Remove Filters. This removes all entries from
the Client/Session list box. To remove individual selected filters, click the enabled
toolbar button.
n
Tip: You can also
turn filters off and on
using the commands
on the Filter menu.
When all filters are removed, the Client/Session list
box is empty and “OFF” displays to the left of the
Filter menu on the menu bar.
Importing and exporting filter settings
The more you use Session Recovery, you may find that you frequently use the same
combinations of filters. For example, suppose several of your Clients in the same region
have been experiencing problems with their phone lines for several weeks. To be sure
the nightly polling sessions executed for these Clients, every morning you use the by
Missing, by Time Range, and by Client filters together to determine if the scheduled
sessions executed for these Clients as expected. Instead of entering the same criteria
and selecting the same Clients each day, you can save the filter settings to a file which
you can call on as needed and use repeatedly.
216
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Saving filters to a file
When you write (or export) filters to a file, you save the selected filter settings for
future use.
To save filter settings to a file:
1
Apply the desired filters and select settings as necessary.
2
Once you have applied the filters, select Write Filters on the Filter menu. The
Write Filter File dialog box appears.
3
By default, filters are saved to the \RWS\Sysfiles\filters directory. You can accept
this default location or enter a new location in the Save in field.
4
In the File name field, enter a name for the file. By default, the file will be saved
with the .flt extension.
5
Click Save to write the filter settings to the file.
CHAPT E R 8 / Usin g Ses s ion Re cove r y
217
Applying filters from a file
When you read filters from a file, you quickly apply filters you have previously saved to a
file.
To apply filters from a file:
1
On the Filter menu, select Read Filters. The Select Filter File dialog box appears.
2
By default, Session Recovery looks for all .flt files in the /RWS/Sysfiles/filters
directory. If you saved the filter files to a different location, use the Look in field to
navigate to the appropriate location.
3
Select the filter you want to apply and click Open. The Client/Session list box filters
accordingly.
218
n
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Tip: You can also
right-click a Client in
the Client/Session list
box and select the
Details shortcut
command to display
this dialog box.
Viewing Client details
You can view detailed information about a selected Client from within Session
Recovery.
To view Client details:
1
Select a Client in the Client/Session list box.
2
On the View menu, select Details.
The Client information displayed in this dialog box is pulled directly from the
RemoteWare Client Profile.
3
Click OK to return to the main window.
CHAPT E R 8 / Usin g Ses s ion Re cove r y
n
219
Updating session data
Session Recovery uses the data logged in your RemoteWare Session History Log to
populate the Client/Session list box. Because sessions may execute continuously on your
RemoteWare system, you must ensure Session Recovery has access to the most recent
session data.
You can specify how frequently data is automatically refreshed. You can also manually
refresh data whenever you choose or prevent data from refreshing at all.
Using the Refresh Automatically function
When you first start Session Recovery, the Refresh Automatically function is disabled.
Data is not updated until you either enable Refresh Automatically or until you manually
refresh data.
Enabling automatic refresh
To enable the Refresh Automatically function, select
the Refresh Automatically command on the View
menu. Once you have enabled this command, Session
Recovery automatically refreshes data every 20
seconds by default. However, you can change the
default refresh rate. For instructions, see “Setting
an automatic refresh time” on page 220.
Disabling automatic refresh
Sometimes you may not want data to refresh automatically. For example, if you are
trying to isolate problems in Session Recovery and there is a great deal of activity on
your RemoteWare system, you may find that frequent data updates complicate your
task. The frequent updates may also be distracting. In these situations, you may
temporarily disable the Refresh Automatically function. To disable the Refresh
Automatically option, clear the Refresh Automatically command on the View menu.
220
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Setting an automatic refresh time
When you set an automatic refresh time, you force Session Recovery to update data at
the specified interval. By default, the refresh time is set at 20 seconds, which means
every 20 seconds the session data is updated. However, you can specify a different
refresh rate.
When you set a different refresh rate, the rate remains in effect until you close Session
Recovery. Once you restart the program, the default refresh rate of 20 seconds goes
back into effect.
To set the automatic refresh time:
1
On the View menu, select Set Refresh Time.
2
Select the desired refresh time. You can select from 10 to 60 seconds. The default is
20 seconds.
3
Click OK to close the Set Refresh Time dialog box.
Note: Setting the refresh time does not enable the Refresh Automatically feature. You
must manually enable the Refresh Automatically command on the View menu
in order for automatic updates to occur.
Manually refreshing data
n
Tip: You can also
press [F5] to
automatically refresh
session data.
You can also manually refresh data quickly and easily whenever you want.
To manually refresh data:
1
Click the
Refresh toolbar button.
This command is unavailable if the Server History Log in Log Viewer has not been
updated with sessions that started or ended while Session Recovery was running.
CHAPT E R 8 / Usin g Ses s ion Re cove r y
n
221
Restarting sessions
You can restart sessions that are marked as
Failed-Final and resubmit sessions
marked as
Missing. Failed-Final sessions are those sessions that were attempted but
failed to complete and have no retries remaining. Missing sessions are sessions that
were never attempted, which may be the result of Clients not calling the RemoteWare
Server at the scheduled time, or of a system failure while sessions were in a blocked
state waiting for a resource.
To restart or resubmit a specific session:
1
In the Client/Session list box, select the session to restart.
2
Click the
3
Click Yes to restart the session or No to cancel.
4
Restart Session toolbar button.
Click OK. The list updates to reflect the restarted session.
222
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To restart or resubmit all displayed sessions:
1
Ensure only the sessions you want to restart appear in the Client/Session list box.
Note: The Restart All command is disabled if any session with a status other than
Failed-Final or Missing appears in the Client/Session list box or if one or more
sessions are highlighted in the list box.
2
Click the
Restart All Sessions toolbar button.
3
Click Yes to continue or No to cancel.
4
Click OK. The list updates to reflect the restarted sessions.
Identifying unsuccessful restarts
When you restart a session a message indicates the number of successful and
unsuccessful restarts. You may see an “unsuccessful restart” message for several reasons:
•
The system cannot create or write to the Session History Log view in Log Viewer.
•
The system cannot open the worklist file (*.wrk).
•
The system cannot retrieve the Client information or the session information for the
specific Client.
•
The scheduler cannot launch a session.
•
The session’s status is no longer “Failed-Final” or “Missing.” A session’s status may
change if another Server successfully resubmitted the session since the last time you
refreshed the session data in Session Recovery.
CHAPT E R 8 / Usin g Ses s ion Re cove r y
223
n Generating Session Recovery reports
The Session Recovery report is generated from the RemoteWare Report Manager. A
full Session Recovery report provides a list of all sessions for each Client organized by
session status. The report includes; each session’s start date/time, duration, status, and
resource port number. To customize the report use the filters and include only the
information you need.
To generate a Session Recovery report:
1
Start RemoteWare Report Manager and locate the Session Recovery report in the
list of available reports.
2
On the File menu, select Generate Report.
224
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
3
Select the filters to apply to the report.
Note: In Report Manager, the filter fields by All and by Status are not available.
4
To generate the report in the form of a CSV (comma separated value) file, select the
Generate CSV File check box.
5
Click OK to generate the report.
This may take a few moments depending upon the amount of data in your
RemoteWare system and the filters you have selected. The report appears:
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
9
9RemoteWare
Monitoring Current System Activity
A RemoteWare Server provides you several programs to monitor the current or past
activity of the RemoteWare system.
This chapter includes:
• View current Server activity using Network Status
• View and generate reports of the Server’s activity and configuration
using Report Manager
226
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Viewing the system’s current status
The Network Status program displays the current status of the entire RemoteWare
system, including detailed resource, session, object, and Client information. The
program features dynamic status displays that give you visual indicators of system
activity.
To open the Network Status window:
In the RemoteWare Menu, double-click the
Network Status icon. This icon
appears in the All Utilities and Server Operations groups.
The window is divided into two panes. The left pane displays available Servers and
resources. The right pane gives detailed information on the highlighted item in the left
pane.
CHAPT ER 9 / Mon it orin g C ur re nt S ys tem Activ it y
227
Viewing the status of different resources
You can change the type of information displayed on the pages of the Network Status
window by clicking an item in the left pane.
If you have a Clustered Server, you can view the resources for other Servers by clicking
the items arranged hierarchically below each Server in your system.
Depending on the level of detail you need, you can select one of three items under each
Server name that presents information about a resource:
•
Active Sessions gives a summary of the resources in use, sessions, and connected
Clients.
•
Resources gives a summary of the resources and how they are defined.
•
Individual resource names, such as ASYNC, NetBIOS, Process Only, SPX, and
TCP/IP provide detailed information on the resource, connected Client, and
current activity.
228
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Viewing resource details
For each item under the Resources category, a resource detail provides
communications definitions and transmission statistics for the current session. This
information is updated as the session executes.
To view resource details:
1
Click one of the Resource items (such as ASYNC, NetBIOS, Process Only, SPX, or
TCP/IP) in the left pane of the Network Status window. Information on defined
resources appears in the right pane.
CHAPT ER 9 / Mon it orin g C ur re nt S ys tem Activ it y
229
2
Double-click any resource item in the right pane. The Details dialog box for that
resource appears.
3
See the RemoteWare Server Reference Manual for more information on the Detail
property pages. To view another resource detail, repeat Steps 1 or 2. You can display
as many detail pages as you need, but displaying a large number of pages may affect
the performance of your Server.
4
To exit the Detail dialog box, click Close.
230
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Viewing active sessions information
As a session takes place with a Client, you can use Network Status to view the events as
they execute. You can view session activity two ways:
•
by active sessions
•
by Client.
To display active sessions:
Select
Active Sessions for the appropriate Server in the left pane of the Network
Status window.
CHAPT ER 9 / Mon it orin g C ur re nt S ys tem Activ it y
231
Viewing Client information
You can view Client information when a selected Client is connected to the Server. The
connected Client’s name appears in the Client column of the individual resource items.
To display Client Information:
1
In the left pane, select an individual resource item.
2
In the right pane, double-click the resource connected to the Client.
3
Click the Client tab.
4
Click Reset to zero out the cumulative statistics for this port, or click Close to
return to the Network Status window.
232
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Viewing Network status alarms
The Server name item and Alarms item in the left pane provide both status (such as
Server Reboot) and error (such as Scheduler Overrun) information.
The Server name item displays the total number of alarms.
Use the Alarms item to display a short list of the alarms.
To view details about or to remove an alarm:
1
Select
Alarms for the appropriate Server in the left pane of the Network Status
window.
2
Double-click an alarm entry in the right pane of the Network Status window. A
message explains the alarm and prompts you to clear it.
3
Choose Yes to clear the alarm.
Starting and stopping the scheduler
A situation you notice in the Network Status program may signal the need to stop the
Scheduler. Use the Network Status program instead of taking the time to open and use
the Schedule Manager program. This command only affects the current Server.
1
On the Command menu, select Suspend Scheduler.
2
Click Yes to confirm the command, or No to cancel.
3
On the Command menu, select Resume Scheduler to restart the Scheduler on
this Server.
CHAPT ER 9 / Mon it orin g C ur re nt S ys tem Activ it y
233
n Monitoring the Server status
After installing or upgrading your Server, the Server administrator should use the logs to
determine if changes were successful. This section concentrates on the Server Profile
Licensing and Cluster pages, and the Server Messages Log in the Log Viewer program.
Server status and information is available from several RemoteWare programs listed in
Table 8, “Server monitoring and log programs.”
Table 8. Server monitoring and log programs
To determine
Use this program
Licensing limits and current values
Server Profile’s Information and Licensing pages
Whether a Server is active or down
Administrator’s System Control page, Server Profile’s
Cluster page, or Network Status’s RemoteWare Servers
view
What modifications, messages, and
errors pertain to the Server
Server Messages Log in Log Viewer
Which files have been transferred
between the Server and Clients
File Transfer Log in Log Viewer
What sessions have executed and
their results
Session History Log in Log Viewer
Which sessions are currently active
Schedule Manager or Network Status’s Active Sessions
view
What resources are available or in
use
Network Status’s Resources view
Command line settings for other
RemoteWare programs
Administrator’s Command Options page
Log file sizes
Administrator’s Log Files page
Messaging activity
Messaging Log in Log Viewer
234
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Use the RemoteWare programs listed in Table 9, “Log entry types,” to view the
information contained in the RemoteWare log files.
Table 9. Log entry types
Program
Type of entries
Server Information
Part of the Server Profile program. Contains system version
and location information as well as numbers of licensed
sessions and Clients.
Licensing Log
Part of the Server Profile program. Contains current maximum
allowable resources and displays past changes to licensing
values.
Server Messages Log (Log
Viewer)
Server-related entries, such as configuration changes, resource
status, system alerts, errors, and program status messages.
Session History Log (Log
Viewer)
Each scheduled session and its status. For each session listed,
details present the objects and events executed, their outcome,
and, if applicable, the reasons an item did not complete
successfully.
File Transfer Log (Log Viewer)
Every file transferred by a GET, SEND, or CHECK SEND
event. The log lists the file name, Client name, time and date
sent, session name, and status.
Report Manager
Generates the text of all logs and other Server characteristics.
C HAPT ER 9 / Monit orin g C urr e nt Sy st em Activit y
235
Viewing Server information
View the Server Profile Information page when you need to know the location, version,
or current usage of sessions and Clients.
To view Server Profile information:
In RemoteWare Menu, double-click the
window appears.
Server Profile icon. The Server Profile
The Information page provides the following information:
•
Serial Number. The serial number corresponds to the license number of your
RemoteWare system.
•
System Data Path. The path name containing the data files and working area for
all Servers in a standalone, Workstation, or Clustered system. For a Cluster, the
path name must be shared so that the other machines in the Cluster can see the
data drive. This location must be the same for all Clustered Servers and
Workstations, otherwise they will not work as a Cluster and will not be visible to
each other through the Cluster page.
•
Version Number. This value defines the exact features and revision level of your
system. Provide this number to your RemoteWare representative when you need
product support.
•
Sessions. Although the Concurrent value appears on the Licensing page, this
section permits you to see how many sessions have been defined and enabled across
the entire RemoteWare system.
236
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
•
Clients. The Maximum value is the same as the licensed number, but this section
also lets you see how many defined and enabled Clients exist on the RemoteWare
system.
Viewing licensing values
Licensing values are provided from a Licensing disk or from update code when you
install or upgrade your Server. You can view or update your licensed and actual values
from the Server Profile Licensing page.
To view licensing values:
1
In RemoteWare Menu, double-click the
Server Profile icon. The Server
Profile window appears. The Information page displays your Server’s licensing
values for concurrent sessions and node counts.
2
Scroll to and click the Licensing tab.
The Licensing page displays the number of licensed and currently used Clients
(also called users or Applications), ports (Sessions/Server), Servers, and
Workstations.
If you have any questions about your licensing values, contact your RemoteWare
representative.
CHAPT ER 9 / Mon it orin g C ur re nt S ys tem Activ it y
237
Updating licensing values
When you update your RemoteWare Server’s licensing values, you increase the number
of licensed Clients for your system.
To update your licensing values:
1
From the RemoteWare Menu, double-click the
Server Profile window appears.
Server Profile icon. The
2
Scroll to and click the Licensing tab. The Licensing page appears.
3
On the Licensing page, double-click any item in the list box. The Update Licensing
window appears.
4
From the Update Licensing dialog box, select one of the following:
•
Select Read Update Code(s) From UPD File to update licensing from a
floppy disk or file. If the file is on a licensing disk, insert the licensing disk into
the floppy drive. If necessary, enter the correct disk drive and path name for the
floppy disk or file, or click Browse to search for the correct path. Click OK.
The update codes are read from the file and the new licensing values appear.
•
Select Enter Update Code to update licensing from the keyboard. Obtain a
licensing code from your RemoteWare representative. Enter the license code
(up to 18 characters) in the text field. Click OK. The new licensing values
appear.
238
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Viewing the Licensing Log
To view the Licensing Log:
1
In the RemoteWare Menu, double-click the
Profile window appears.
Server Profile icon. The Server
2
Scroll to and click the Licensing tab. The Licensing page appears.
3
On the Command menu, click View License Log. The License Log dialog box
appears.
The License Log displays every change you have made to the licensing on this
RemoteWare Server system.
4
Click Close when you are finished viewing the log.
CHAPT ER 9 / Mon it orin g C ur re nt S ys tem Activ it y
239
Viewing Server or Cluster activity
Use the Server Profile Cluster page to instantly assess the status of Servers or
Workstations on the network.
To view the Cluster page:
1
In RemoteWare Menu, double-click the
Profile Information page appears.
Server Profile icon. The Server
2
Click the Cluster tab. The Cluster page appears.
You should see all of the Servers and Workstations in your system. Normally
functioning Servers display an Enabled status and a state of Running.
240
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Using Report Manager
Use Report Manager to view the reports available for the Server. You can also generate,
view, and print these reports. The report files are text files that you can import into
other programs. You can also generate reports from a command line or from a session.
To open Report Manager:
In the RemoteWare Menu, double-click the
Report Manager icon. The Report
Manager main window appears. The icon appears in the All Utilities and Server Logs
groups.
Note: Additional reports that are available for other RemoteWare products installed
on the Server may also appear in this window.
To generate a report:
1
Highlight the name of the report you want to generate.
2
On the File menu, select Generate Report.
When you generate an Administration, Long Distance Services, Modems, Port
Communications, Ports, Protocols, or System report, you do not have to specify
additional information and the report is created immediately. When you generate
the other types of reports, you must specify additional information before the report
is created.
After you generate a report for the first time, it automatically appears in its own
window.
CHAPT ER 9 / Mon it orin g C ur re nt S ys tem Activ it y
241
Filtering report information
With several of the reports, you can use filters to restrict them to a certain level of detail.
Many reports, such as the Work Objects report, may be extremely large and take a while
to generate if you don’t apply filters. The filters are summarized in the “Report Filters”
section of the RemoteWare Server Reference Manual, and are described in detail in the
sections specific to each report.
For reports that use filters, the Write Filters and Read Filters buttons allow you to
save and reuse specific filter settings for that report.
Selecting the file format
The reports generated in the Report Manager are formatted for you to view in the
Report Manager; however, some column-oriented reports include the Generate CSV
File (Comma Separated Value) option. Enable this option to have each entry in the
report separated by a comma with no additional formatting. The CSV file format is
useful if you plan to import the report into another program that recognizes commas as
indicating a new field.
Using the Report Editor
When viewing a report, you can use the multi-line report editor to copy selected text to
the clipboard. Then you can paste the text into a text editor. You can also customize the
editor using commands you select on the View menu.
Copying and pasting text
1
Highlight the text you want to copy, or choose Select All from the Edit menu.
2
Click
3
Paste the copied text into a word processing program. The copied text remains in
the clipboard until you copy another section of text.
Copy.
242
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Searching for text
1
On the Edit menu, select Search for. The Search Administration dialog box
appears.
2
Enter the text you want to search for in the Search for area.
3
Enable the Case Sensitive check box if necessary, then click OK. The found text is
highlighted. If no text is found, a message box appears.
4
Click OK again to find additional instances of the specified text.
Printing a report
To print a report from Report Manager to your default network printer, you must install
and properly configure the printer. See your Windows documentation for more
information on installing and configuring your printer.
To print a generated report:
1
Highlight the name of the report you want to print.
2
On the File menu, select Print Report.
You may only want to print a set amount of lines in the report, or for longer reports, you
may want to print only a section of pages at a time. You can set the number of lines you
want to print on each page.
To set the number of lines to be printed per page:
1
On the Command menu, select Set page size. The Set Page Size for Printing
dialog box appears.
2
Enter the number of lines per page. The default is 66 lines per page.
3
Click OK to finish.
CHAPT ER 9 / Mon it orin g C ur re nt S ys tem Activ it y
243
Deleting a report
You may want to delete reports once you have exported them into a word processing
program, so you can free disk space on your server.
To delete a generated report:
1
Highlight the name of the report you want to delete.
2
On the File menu, select Delete Report.
3
Select Yes when prompted to confirm the command.
Copying a report
1
Highlight the name of the report you want to copy.
2
On the File menu, select Copy Report.
3
Enter a new name for the report, and click OK. The new report name is listed in
the Report Manager window.
244
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Working with report definitions
You can add custom report definitions that are based on existing report definitions to
the Report Manager window.
To add a new report definition:
1
On the Command menu, select Add Report Definition. The Report Definition
dialog box appears.
2
Enter a new Report Name. This name will appear in the Report Name column on
the main window.
3
Enter a valid name for the Output File and the Program Name of the executable
that you want to generate the report. See the “Report Manager” chapter in the
RemoteWare Server Reference Manual for a list of the report executable files.
4
Specify any Additional Options, such as a filter file or format.
5
Click OK. The new report appears on the main window.
Once you have defined a report definition, you can change or delete it if necessary.
Changing a report definition
If you change a report definition’s options, the new options become the default.
However, when you generate the report, the Report Definition dialog box appears so
you can make any other selections.
To change a report definition:
1
Highlight the name of the report whose definition you want to change.
2
On the Command menu, select Change Report Definition.
3
Make changes, then click OK.
C HAPT ER 9 / Monit orin g C urr e nt Sy st em Activit y
245
To delete a report definition:
1
Highlight the name of the report whose definition you want to delete.
2
On the Command menu, select Delete Report Definition.
3
When prompted to confirm the command, click Yes.
Generating reports from sessions or command lines
You can also generate reports from within a session or from the command line. To
generate a report from within a session, you can edit a copy of a worklist file called
reports.evf, located in the \worklist directory. This file contains three events for each
report type you can generate. For example, the three lines listed below perform the
following operations:
•
DELETE \SYSFILES\REPORTS\RPT_ADMIN.LST Delete an existing report
called rpt_admin.lst in the \reports directory.
•
EXECUTE START RPT_ADMIN.EXE -H Execute a command to generate the
rpt_admin report (Administration Report) with the Cancel dialog box hidden.
•
WAIT \SYSFILES\REPORTS\RPT_ADMIN.LST 5:00Wait for 5 minutes, or until
the report is generated. (The wait is necessary if you want to run another report
from the session. It prevents all reports from running simultaneously.)
Reports.evf is a sample file that shows how you can generate reports in a work object.
Import reports.evf into a worklist object using the Import command and edit it, or you
can build your own worklist object. Since the sample file is very large, edit it to contain
only the commands you want.
To generate reports from the command line, enter the command and any options. You
cannot use a worklist as you can when using an object. For example, to create a Server
Log report to the output file msg.lst using a filter file at the command line, you would
enter:
RPT_MSG -f MSGFLTR.FLT -o MSG.LST
All reports are stored in \sysfiles\reports unless you specify a full path.
See each report in the RemoteWare Server Reference Manual for a description of valid
command line options.
246
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Using Report Manager to generate CSV files
Using Report Manager, you can generate the CSV file format for the ten additional
reports. You can also generate these reports from a command line or within a Session.
Note: When you generate the Administration, Long Distance Services, or Modems
reports, the report is created immediately (in standard Report Manager format)
without your having to specify additional information.
The Report Manager program displays all of the available Server reports you can
generate, view, and print. Double-click the Report Manager icon in the RemoteWare
Menu. You’ll find the icon in the All Utilities and Server Logs groups.
To generate a CSV file using Report Manager:
1
In Report Manager, select the report that you want to generate.
2
On the File menu, select Generate Report. The respective Report dialog box
appears.
3
Select the Generate CSV File check box to format the column-oriented report,
and then click OK. The selected report generates and then appears.
In this example, the CSV file includes tags, which are positioned as the first entry on
each line. The second entry of the tag CLI_NAME indicates the beginning of a new
record. Note the same report generated in the standard Report Manager format.
View the field information in both reports.
CHAPT ER 9 / Mon it orin g C ur re nt S ys tem Activ it y
247
Using the command line to generate CSV files
Use either the Windows Start, Run command or the DOS Command Prompt to
generate CSV files at the command line.
To generate a CSV file from the command line:
1
At the command line, enter the command and any options.
Note: If you don’t know the options that are available for a specific report, enter a “?”
after the name of the report, for example, rpt_ndet.exe ? The respective
Report dialog box appears displaying the available command line options.
2
Press [Enter] or click OK. A Report dialog box appears that displays the report
generation progress.
Note: All generated reports are stored in the \Sysfiles\Reports directory unless you
specify a full path.
248
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Generating a CSV file from within a session
The Work Object Editor lets you edit a sample report file—Reports.evf—to generate
reports from within a work object. This sample report file contains three events for each
report type that you can create:
•
DELETE <ServerData>\SYSFILES\REPORTS\RPT_NDET.LST. Deletes an
existing report called rpt_ndet.lst in the \Reports directory.
•
EXECUTE START RPT_NDET.EXE -H. Executes a command to generate the
rpt_ndet report (Client Detail Report) with the Cancel dialog box hidden.
•
WAIT <ServerData>\SYSFILES\REPORTS\RPT_NDET.LST 5:00. Waits for 5
minutes, or until the report is generated. (The Wait event prevents multiple reports
from running simultaneously.)
To open Report Manager, double-click the Report Manager icon in the RemoteWare
Menu. You’ll find the icon in the All Utilities and Server Setup groups.
Note: You can find a copy of reports.evf in the RWS\Worklist directory.
To generate a CSV file within a Session:
1
On the Events property page in the Work Object Editor, select File then Import
from the menu bar. The Open dialog box appears.
2
Double-click the Worklist directory.
CHAPT ER 9 / Mon it orin g C ur re nt S ys tem Activ it y
3
249
Double-click Reports.evf. The Events property page displays all of the events in
the sample file.
Note: The sample file is very large, so you should edit the file to include only the
commands that you want.
4
Double-click a specific line to access the respective Event Details dialog box. Use it
to edit the event’s behavior.
5
Click Done when you’ve finished editing the specific event.
6
Exit the Work Object Editor when you’ve completed all edits.
250
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
10
10RemoteWar
e
Viewing RemoteWare Logs
You can view the contents of your RemoteWare logs using Log Viewer. You can also
customize the views of each log, specify filters and fields to appear within each view.
This chapter includes:
• View RemoteWare log data using the Log Viewer
• Quick Filter Views
• Apply filters to views
• Create custom log views
• Export log views
252
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Using the Log Viewer
The Log Viewer lists the occurrence of any action that affects the RemoteWare Server.
It allows you to view the information in this database by creating folders and views that
group and filter log entries by a number of different criteria.
You can rename the Log Viewer’s default folders and views or add new folders and views
in order to customize your Log Viewer. For more information, see “Customizing the
Log Viewer” on page 266.
To open the Log Viewer:
1
In the RemoteWare Menu, double-click the
Log Viewer icon.
Note: The Inventory Manager and Multicast folders displays only if you are licensed
for those components.
The Log Viewer groups log views into categories, each has its own folder:
•
File Transfers Logs. This folder contains log views that record every instance in
which the Server sends or receives a file. Using File Transfers’ views and fields, you
can quickly determine if a file was transferred, identify the number of file
exchanges, and view file level details.
•
Inventory Manager Logs. If licensed for Inventory Manager, this folder displays
the log views from the Client inventory scans, which includes hardware and
software scan results. Each log includes, the activity (scan description), activity ID,
client name, date and type (Info).
CH A PT ER 1 0 / Vi e wi ng R em o t eWar e L o gs
253
•
Messaging Logs. This folder contains log views that record every instance in which
messages are sent through the RemoteWare Messaging program, the originating
user, the date and time, and the size of the message.
•
Multicast Logs. If licensed for Multicast, this folder displays the log views from
the Multicast sessions that have been run. Each log includes, start time, session,
client name, status, message, and row ID.
•
Server Messages Logs. This folder contains log views that record information,
warning and error messages specific to the Server. For example, information about
when channels were created, modified, published, unpublished, and deleted
display. When the RemoteWare service was started and stopped, and when a
worklist or sendlist was modified also display.
•
Session History Details. This folder contains details about past sessions. The
information includes, row ID, session name, start time, status, event command,
parameter 1, preposition, parameter 2, and failure reason.
•
Session History Logs. This folder contains log views about past sessions, such as
the channel involved, the session end time and duration, the user and computer
information, and session event status.
•
Transaction Pipe Logs. This folder contains log views about transaction pipe APIs
which have occurred between the Client and server. The information includes bytes
received, bytes sent, Client name, compression rate, duration, start time, end time,
messages received, pipe name, port, resource, resource code, row ID, server name,
status, and status code. For additional information about transaction pipe APIs,
refer to the RemoteWare API Manual.
To open any log view:
1
In the left pane, click the
parent folder.
plus sign to expand the
2
Click on the view you wish to see.
The log view appears in the right pane of the Log Viewer
window.
254
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Setting View Properties
Whether you accept the default folders and log views in the Log Viewer or decide to
create your own, you can determine which fields you want to appear in each log view.
The View Properties window allows you to select and filter fields to display. For more
information on creating custom views, see “Customizing the Log Viewer” on page
266.
To open View Properties:
1
Select a view from the left pane of the Log Viewer window.
2
Click the
•
Parent Folder. Displays the path for the view selected.
•
View Name. Displays which view you currently have selected.
Properties icon.
Note: If you want to change the view you have selected, click Cancel, select the view
you want to modify, and re-open the View Properties window.
C H A PT ER 1 0 / Vi e wi ng R em o t eWar e L o gs
255
•
All Fields. Displays all the fields by category you can add to customize the log view
you have selected. Also use this window to select Fields to Filter.
•
Fields To Display. Displays the fields to appear for the log view you have selected.
Also use this window to remove and sort fields.
•
Fields With Filter. Displays any fields for which you have defined filters. Also use
this window to select filtered fields to remove or modify.
Selecting fields within a view
You can select certain fields to view from each of the log view categories. For example,
you may want some specific information about file transfers, such as the bytes sent, the
file name, the file size at the Server, the status of the transfer, and the end time of the
transfer. For a list of all categories, fields and their descriptions, see the RemoteWare
Server Reference Manual.
To select fields to display:
1
In the All Fields window, select the field you want to add.
2
Click Add To View. The field you have added appears in the Fields to Display.
3
Repeat steps one and two for each field you want to add.
4
When you are finished, click OK.
Note: If you add fields from more than one category to your view, the view will not
appear in the Log Viewer.
256
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To remove a field from a view:
1
Select the field you want to remove.
2
Click Remove From View.
To sort fields in a view:
1
Select the field you want to move.
2
Click Move Up or Move Down to place the item in the order you want.
CH A PT ER 1 0 / Vi e wi ng R em o t eWar e L o gs
n
257
Quick Filters Views
The Quick Filters Views streamlines the filter definition process. It reduces the time
and number of steps it takes to setup a filter view. Several predefined Quick Filter
Views are provided with Log Viewer. You select a filter and then select the values
specific to your company to be included in the Quick Filter View. You can also add or
remove Quick Filter fields and filters as desired. For instructions on how to select filter
values, see “Customizing an existing Quick Filter View” on page 259.
Note: The Inventory Manager Quick Filters and Multicast Quick Filters only display
if you are licensed for Inventory Manager and Multicast components.
The predefined Quick Filters Views include:
File Transfer Quick Filters
The File Transfer Quick Filters default view displays the Start time, Client Name,
Status (FAILED or SUCCESSFUL), Command (GET, SEND, or CHECK SEND),
and File Name fields This view has the following predefined filters:
•
Client
•
File
•
Time Range
Inventory Manager
The Inventory Manager Quick Filters default view displays the log views from the
Client inventory scans, which includes hardware and software scan results. Each log
includes, the activity (scan description), activity ID, client name, date and type (Info).
This view has the following predefined filters:
•
Activity
•
Client
•
Type
Messaging
The Messaging Quick Filters default view displays an entry for every message received
and processed by the Message Transfer Agent (MTA). Each log includes, the originating
user, Client Name, Date/Time received, message priority, and size in bytes. This view
has the following predefined filters:
•
Client
•
User
258
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Multicast Quick Filters
The Multicast Quick Filters default view displays the Start time, Session, Client Name,
Status (FAILED or SUCCESSFUL), Message, and Row ID. This view has the
following predefined filters:
•
Client
•
File
•
Session
•
Status
•
Time Range
Server Message Quick Filters
The Server Message Quick Filters default view displays the Date/Time, Server, Type
(message type), and Message fields. This view has the following predefined filters:
•
Server
•
Time Range
•
Type
Session History Detail Quick Filters
The Session History Detail Quick Filters default view displays the Session Name, Start
Time, Status (FAILED or SUCCESSFUL), Event Command, Parameter 1,
Preposition, Failure Reason, and Row ID fields. This view has the following predefined
filter:
•
Status
•
Session
Session History Quick Filters
The Session History Detail Quick Filters default view displays the displays the Session
Name, Client Name, Status (FAILED or SUCCESSFUL), Start Time, Duration,
NetMgr Name (Server Name) and Resource fields. This view has the following
predefined filters:
•
Client
•
Resource
•
Server
•
Session
CH A PT ER 1 0 / Vi e wi ng R em o t eWar e L o gs
•
259
Time Range
Transaction Pipe Quick Filters
The Transaction Pipe Quick Filters default view displays Bytes Recorded, Bytes Sent,
Client Name, Compression Rate, Duration, Start Time, End Time, Messages Received,
Messages Sent, Pipe Name, Port, Resource, Resource Code, Row ID, Server Name,
Status (FAILED or SUCCESSFUL), and Status Code.
This view has the following predefined filter:
•
Status
Customizing an existing Quick Filter View
Multiple Quick Filter fields can be assigned to a view. Whenever the view properties are
accessed, a dialog box is presented for each Quick Filter field, this enables the user to
modify one or more of the Quick Filter field values.
Note: When you initially start to use Quick Filters, you need to select the values
specific to your company. For example, to display File Transfer Quick Filter by
Client, select the your clients from the list.
To change an existing Quick Filter View:
1
In Log Viewer, from a Quick Filters folder, select a filter view and click
Filter.
Quick
260
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
2
Double-click the Value field or use the arrow keys to add the values as a filter. Or
use the second Value field to enter a new value, and then click Add New.
3
To add condition options to this value, click Advanced button.
Enter the necessary condition information.
4
Click OK.
Log Viewer displays the Quick Filter view filtered by the value(s) you selected.
CH A PT E R 1 0 / Vi e wi ng R e mo t eWar e L o g s
261
Creating Quick Filter View
To create a Quick Filter View:
1
From a Quick Filters folder, select a filter value and click
right-click a filter value and click Quick Filter.
Quick Filter. Or
2
In this example, set the time value and click Add to List.
3
To add condition options to this value, click Advanced button.
Enter the necessary condition information.
4
Click OK.
Note: To remove a field as a filter, remove the check mark in the Quick Filter Field
check box and click OK. The field is no longer a filter for the view, and a new
field can be selected as a filter. To display the Quick Filter Field check box, click
Advanced button.
262
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Viewing Quick Filter Views
The Quick Filter views are indicated in a Filters folder when the Quick Filter check box
is marked.
To review the Quick Filters Views:
1
2
Access the Log Viewer. Under a folder for each type of log, click a Quick Filters
folder.
Select a Quick Filter view, and then click
Quick Filter.
Or right-click the view and click Quick Filter….
Note: When you initially start using Quick Filters, you need to select the values
specific to your company.
3
Double-click a Value field to add the value as a filter.
Or use the arrow keys to select values.
4
After you completed your selections, click OK.
CH A PT E R 1 0 / Vi e wi ng R e mo t eWar e L o g s
n
263
Filtering fields within a view
You can use filters to “filter” the data displayed in a view. For example, the “Errors” view
in the Messages folder could contain a filter on the “Type” field that would only show
messages of type ERROR or FATAL ERROR. Filters can display log fields that share a
common characteristic or can be combined to display log fields that occurred under
specific conditions.
To open the Filter dialog box:
1
From the fields listed on the View Properties dialog box, select the field you want to
define.
2
Click Filter By Field. The Filter dialog box appears. For a list of all conditions that
you can set when you filter a field, see the RemoteWare Server Reference Manual.
Note: If you want to select another field to filter, close the Filter dialog box and choose
another field from the View Properties dialog.
264
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Setting field values
You can set field values two ways:
•
Manually. You can enter the specific information such as a date, a time, or a file
size. Enter values manually if you are filtering fields for a new log view or if you
need to filter the field by a specific value.
•
Select Value. You can click Select Value to choose a value from the Field Values
from Log dialog box. Use this option to select values that have already been logged.
To set a field value:
1
Select a Condition option.
2
In the values area, you can either:
3
•
Manually enter a value such as a date, a time, or a file size.
•
Click Select Value to select a field value from the existing log view. The Field
Values From Log dialog box appears. Select the value and click OK.
Click OK to return to the View Properties dialog box.
You can also set more than one value for a field. For example, if you want to find file
transfers that took place on a series of dates: August 3, August 4, and August 5 starting
at 8:30 A.M., you can enter these dates and add them to the list. The log view will show
file transfers that took place only on those dates.
When you select or manually enter a value, you can click Add To List to add the value
to a list of values for filtering.
Note: You can only add values to a list if you have chosen the = or != conditions.
CH A PT ER 1 0 / Vi e wi ng R em o t eWar e L o gs
265
The conditions and values you set for a field appear in the Fields With Filter area of the
View Properties dialog box.
From the Fields with Filter area of the View Properties dialog box, you can also remove
and modify filters.
To remove a filter:
1
Select the filter you want to remove.
2
Click Remove Filter.
3
Click OK.
To modify a filter:
1
Select the filter you want to modify.
2
Click Modify Filter. The Filter dialog box appears.
3
Make any changes to the filter. The new information appears in the Fields with
Filter area of the View Properties dialog box.
266
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Customizing the Log Viewer
With RemoteWare’s Log Viewer, you can customize your log views and organize them to
meet your needs. Folders, indicated by the
icon, can contain log views or other
folders. You can group a number of related log views into the same folder, or “nest”
folders within each other to create a hierarchical structure.
The Log Viewer provides several ways for you to organize views into folders. You can
create a new view directly in a folder or create new folders and move existing views into
these folders. You don’t need to recreate a view just because it is not in the right
location.
For example, if you have a mobile sales force, you may decide to create a folder called
“Sales Regions,” and within that folder create a folder for each region. Each folder may
contain several different log views. You may create a log view called “MW Report
Transfers,” which would log all report (or file) transfers for Client users in the Midwest
Region.
You can also create a view in the Midwest Region folder called “Sessions by Client” and
apply filters that allow you to view information from sessions one Midwest Region
Client at a time.
CH A PT E R 1 0 / Vi e wi ng R e mo t eWar e L o g s
267
To create a new folder:
1
Select the All Views parent folder.
2
Click the
New Folder button.
Note: The name of the parent folder appears in the first area.
3
Enter the name of the new folder.
4
Click OK.
The new folder appears under the parent folder.
To create a new view:
1
Select a folder where you want to place the new view.
2
Click the
New View icon. The View Properties dialog box appears. The name
of the folder in which you’ve chosen to place the new view appears in the first area.
You cannot choose another folder from this dialog box. You must close View
Properties and select another folder from the left pane of the Log Viewer window.
3
Enter a name in View Name.
4
Select the fields to include in this view. For more detailed instructions, see
“Selecting fields within a view” on page 255.
5
Set filters for any fields you want to include in the new view. For more detailed
instructions, see “Filtering fields within a view” on page 263.
The new view appears in the folder you selected to contain it.
268
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Renaming and reorganizing folders and views
You can rename and reorganize your folders and views as your
needs change. For instance, when you first organized the Log
Viewer, you had one parent folder for all Sales Regions, and
each region contained several views. Instead, you may decide
to restructure your Log Viewer so that each Sales Region has
its own set of subfolders that contain various log views.
When you create new folders and views, they appear by
default in alphabetical order in the Log Viewer’s tree
directory. However, you can organize folders and views into
any number of groups. Use functions such as renaming
folders and views, and copy, cut, paste and delete to
reorganize the Log Viewer.
Note: You cannot rename the All Views folder in the Log Viewer.
To rename a folder or a view:
1
Select the folder or view you want to rename.
2
On the File menu, select Rename. The Rename dialog box appears. The last name
you gave the folder or view appears in the Original Name area. You cannot choose
another folder or view from this dialog box. You must click Cancel and choose
another folder or view from the left pane of the Log Viewer window.
3
Enter the new name of the folder or view in New Name.
4
Click OK.
CH A PT E R 1 0 / Vi e wi ng R e mo t eWar e L o g s
269
Cutting, copying, and pasting folders
Use the Cut, Copy, and Paste commands to move folders and views quickly from one
location to another, and organize the views and folders to meet your needs.
To move or copy an existing view or folder to another location:
1
Select any folder or view you want to copy or move in the left pane of the Log
Viewer.
2
Choose one of these commands:
•
Cut. Use this command or the
toolbar button to move an item. Cut
removes the item from its present location and moves it to the Clipboard. The
item is not deleted until you paste it elsewhere.
•
Copy. Use this command or the
toolbar button to make a duplicate of the
item. If the duplicate name conflicts with another item in the destination folder,
RemoteWare adds a number to the end of the new name.
3
Right-click the folder where you want to place the item.
4
Select Paste from the shortcut menu.
The Log Viewer places the cut or copied item in the selected folder.
Deleting folders and views
You can delete any folder or view from the Log Viewer when you no longer need it. If
you are deleting a folder that contains several views or subfolders, the Log Viewer
delete all the views and subfolders.
To delete a view or folder:
1
Select a view or folder in the left pane of the Log Viewer.
2
Click the
3
Choose Yes to delete the view or folder.
Delete button.
270
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Viewing log details
Log Viewer allows you to view the details about a
particular message, session, file transfer, or other event.
When you select Row Details on the File menu, the
Log Viewer will either call the Row Detail dialog box or
the select detail type dialog box. From the Select Detail
Type dialog box, you can view two types of log details:
•Default. This shows the Row Detail dialog box, which
displays all information about each field in the selected
item.
•
Session Event Detail. This provides the details of each event in a session. This
session detail generates only for Session History log views.
Viewing row details
The Row Detail dialog box presents all fields in the Session History, Messaging, File
Transfers, or Server Messages category. You can view information about a specific item
when you select the Row Details.
To view row details for Messages:
1
Select an item in the right pane of the Log Viewer.
2
Select Row Details from the File menu.
3
To view details for another item in the log view, click Next or Previous.
4
If the item contains a message longer than 255 characters, a
Detail
button appears on the Row Detail dialog box. If you select the Message (Long) item
and click Detail, you can view the entire message.
CH A PT E R 1 0 / Vi e wi ng R e mo t eWar e L o g s
5
Click OK.
6
Click OK to return to the Log Viewer main window.
271
To view row details for File Transfers or Sessions:
1
Select an item in the right pane of the Log Viewer.
2
Select Row Detail from the File menu.
3
Select Default on the Select Detail Type dialog box and click OK. The Row Detail
dialog box appears.
4
Click Next or Previous to view details for another item.
5
Click OK.
272
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Viewing session event details
The Detailed History For Session window provides specific file transfer or session entry
information.
To display the Detailed History For Session window:
1
Select a Session History log view entry.
2
On the File menu, select Row Detail.
3
Select Session Event Detail from the Select Detail Type dialog box.
By default, the History For Session window opens at the object level. This highest level
of detail lists channel work objects and allows you to identify the objects executed and
determine where a problem may have started.
If not already at the object level of detail, click the Condense Objects button. (If the
objects are already listed, this button reads Expand Objects.)
CH A PT E R 1 0 / Vi e wi ng R e mo t eWar e L o g s
273
Displaying work object details
Display work object details to identify the events in a work object and the completion
status of each event.
To view event information:
1
Select a work object.
2
Click the Expand Objects button. (If event details are already displayed, this
button reads Condense Objects.)
The event listing contains these columns:
•
Flags. The event flag codes in the History For Session window indicate if and why
an event failed. For a list of event flag codes, see the RemoteWare Server Reference
Manual.
•
Event. Displays the evaluated event. The RemoteWare Server evaluates variables
and conditional statements during start time and substitutes the values in the event
history detail.
274
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Displaying event details
To display event details:
Click the Expand Events button in the History For Session window. (If the events
already appear in the window, the button reads Condense All Events.)
At this level of detail, the window displays channels, their events, and a description for
each event. The description includes any information the event returns when
successful, or the reason an event failed. For more information about the columns in the
event detail listing, see the RemoteWare Server Reference Manual.
CH A PT ER 1 0 / Vi e wi ng R em o t eWar e L o gs
n
275
Exporting a log view
You can export your log views and save them as text (*.txt) files in another location on
your network.
To export a log view:
1
Select a log view from the left pane of the Log Viewer main window.
2
On the File menu, select Export.
3
In the Save As area, enter the path where you want to save the log view or click
Browse to locate the folder where you want to save the log view.
4
Select one of the following:
5
•
All Rows. Saves all rows of the log view.
•
Row to Row. Allows you to enter a range of rows you want to save. If you select
only the rows you need, this saves disk space.
Click OK.
276
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Chapter X: Chapter Title <-- Apply “chapter hidden” style
C HA P T E R
11
11RemoteWar
e
Using RemoteWare Messaging
RemoteWare Messaging Services (also called Messaging) allow applications to exchange
messages and information within the RemoteWare network and beyond. RemoteWare
transports, stores, and processes the messages for messaging-aware application, as well
as RemoteWare applications such as RemoteWare Workshop and Subscriber.
This chapter includes:
• User definitions
• Assign user attributes to local users
• Work with user groups
• View database assignments for Messaging Transport Agent (MTA)
• Synchronize address books
• Work wth Gateways
• Configure and use MAPI services
278
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Working with user definitions
The Directory Manager program displays and maintains the addressing information for
all users of the RemoteWare network.
To open Directory Manager:
In the RemoteWare Menu, double-click the
Directory Manager icon. This icon is
located in the All Utilities and Messaging Operations groups.
Directory Manager displays user groups in the left pane and users in the right pane. The
listed users are members of the highlighted group.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
279
Filtering the list of users
If you have large user lists, you may want to use one or a combination of filters to limit
the list of displayed users. Use the Filter menu options to view a specific class of users.
You may apply more than one filter simultaneously. Filter-ON appears in the menu bar
and the toolbar indicates which filter is in use when a filter setting is active.
When you apply filters, you only affect your view of the list, not the actual availability of
users. Some of these methods are listed in Table 10, “Methods for filtering users.”
Table 10. Methods for filtering users
To
Use this
button
Or select this command on the
Filter menu
Show which user(s) belongs to a Client
by Client
See which user profiles have been
changed but not yet updated
by Changed User
View users that are up to date and have no
pending changes
by Unchanged Users
List users who receive address updates
and whose addresses are synchronized by
RemoteWare
by Synchronized Users
List unsynchronized users who do not
appear in address lists and who do not
receive address updates
by Unsynchronized Users
Stop filtering the user list
Remove All Filters
280
n
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Adding a new local user
For information
on configuring and
maintaining the
RemoteWare
Gateway which
enables remote users
to exchange
information with
local users, see
“Working with
Gateways” on
page 309.
Local users are based on the RemoteWare Server, can transfer RemoteWare data, and
can be assigned to a Client. Using a gateway, local users can also exchange information
with remote users.
Creating a new local user requires you to provide the following:
•
A last name (first name and middle initial are optional but recommended
•
A unique address (or Client logon name)
•
A Client name, if this is an active RemoteWare user
If you are creating a large number of similar users, you may save time by copying and
modifying a standard user definition. You can also use the USER ECF commands to
generate users from a text file.
To create a new user:
1
From Directory Manager, click
New User. The Profile dialog box appears.
2
Select the Local User option if it is not selected.
3
In the First Name field, enter the user’s first name. If the user name is a company,
leave this field blank and enter the company name in the Last Name field.
4
In the MI field, enter the user’s middle initial.
5
In the Last Name field, enter the user’s last name or the company name.
6
In the Address/Client Login field, enter the user’s logon name . Make the choice
easy to remember, since users must use this name each time they access Messaging.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
281
7
To place this user in the address book distributed to users on Clients, select the
Include User in Address Book check box.
8
Select the Enabled check box in the Client group box. The Select Client dialog box
appears.
9
Select the name of the Client to assign to the user and click OK to return to the
Profile dialog box. Messages will not be sent to the user unless you have assigned
the user to a Client.
10
Enter a default password in the Password field. Users use this password to access
Messaging or any RemoteWare application on the RemoteWare Client. The user
can change the password at the Client by using the Mail and Fax program in
Control Panel.
11
Complete one of the following steps:
•
Click Apply to save settings. Continue with the next sections to assign user
groups and attributes to this user.
•
Click OK to save settings and return to the groups and user list window in
Directory Manager.
282
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Adding a new remote user
Remote users are external to the RemoteWare network. Using a gateway, remote users
can exchange information with local users.
Note: If you have RemoteWare Gateway, you can automatically add remote users to
the Directory Manager database. For information on configuring and
maintaining the RemoteWare Gateway that enables remote users to exchange
information with local users, see “Working with Gateways” on page 309.
To create a new remote user, you must provide the following information:
•
A last name (first name and middle initial are optional)
•
A unique address
•
The correct address type
To add a new remote user:
1
From Directory Manager, click
New User. The Profile dialog box appears.
2
Select the Remote User option.
3
In the First Name field, enter the user’s first name. If the user name is a company,
leave this field blank and enter the company name in the Last Name field.
4
In the MI field, enter the user’s middle initial.
5
In the Last Name field, enter the user’s last name or the company name.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
n
283
6
In the Address/Client Login field, type the user’s logon name. This is the fully
qualified name that is compatible with the address type. For example, for Internet
users, enter example.acme.net.
7
To place this user in the address book distributed to users on Clients, select the
Include User in Address book check box.
8
In the Address Type field, click the down arrow to select the messaging system for
this user.
9
Complete one of the following steps:
•
Click Apply to save the setting. Continue with the next section to assign user
group to this user.
•
Click OK to save the settings and return to the Directory Manager program.
Assigning groups to local or remote users
From the Groups property page, you can assign local or remote users to user groups.
To assign groups to local or remote users:
n
To define a user
group, see
1
“Working with
user groups” on
page 292.
In Directory Manager, double-click the Client you want to assign to a group. The
Profile dialog box appears.
If the user is already assigned to one or more user groups, these groups appear in
the list box.
2
Click the Groups tab.
284
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
3
Click Assign to display a list of available user groups. The Select User Groups
dialog box appears.
4
Complete one of the following steps:
5
•
To assign the user to one or more groups, select the desired groups and click
OK.
•
To assign the user to all available groups, click All User Groups.
Click OK to save the settings and return to Directory Manager.
To remove a user group assignment:
1
In Directory Manager, double-click the Client for which you want to remove user
group assignments. The Profile dialog box appears.
The list box displays the names of all user groups to which this user is assigned.
2
Click the Groups tab.
C H A PTE R 1 1 / U s i ng R em o t eWar e M e ss a gi ng
3
4
n
285
Complete one of the following steps:
•
To remove one or more user groups, select the desired groups and click
Unassign.
•
To remove all user group assignments, click UnAssign All.
Click OK to save the settings and return to Directory Manager.
Assigning applications to local users
Use the Applications page to assign published Workshop applications and Subscriber
lists to a local user.
To add a application assignment:
1
From Directory Manager, double-click the user to which you want to assign local
users. The Profile dialog box appears.
2
Click the Applications tab.
If one or more applications are already assigned to the user, these applications
appear in the list box.
286
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
3
Click Assign to display a list of available user groups. The Select Application
Objects dialog box appears.
4
Complete one of the following steps:
5
•
To view information about a selected application object, click Item Detail.
•
To assign one or more applications to the user, select the desired applications
and click OK.
•
To assign all available applications, click All App Objects.
Click OK to save the settings and return to Directory Manager.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
287
To remove a application object assignment:
1
In Directory Manager, double-click the Client for which you want to remove
application object assignments. The Profile dialog box appears.
2
Click the Applications tab.
The list box displays the names of all application objects assigned to this user.
3
4
Complete one of the following steps:
•
To remove one or more application objects, select the desired object and click
Unassign.
•
To remove all application objects, click UnAssign All.
Click OK to save the settings and return to Directory Manager.
288
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Assigning user attributes to local users
Use the Attributes page to assign a set of labels and values to local users.
To assign user attributes to local users:
1
From Directory Manager, double-click the user to which you want to assign user
attributes. The Profile dialog box appears.
2
Click the Attributes tab.
If one or more attributes are already assigned to the user, these applications and
their corresponding values appear in the list box.
3
Click Add to add a new attribute. The Edit Attribute dialog box appears.
4
In the Edit Attribute dialog box, enter the attribute’s label in the Name field and
the corresponding value in the Value field.
5
Click OK to save the attribute definition and close the Edit Attribute dialog.
6
To assign another attribute to the user, repeat Steps 4 through 6.
7
Click OK to return to Directory Manager.
To edit an attribute definition:
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
1
In Directory Manager, double-click the Client for which you want to remove
application object assignments. The Profile dialog box appears.
2
Click the Attributes tab.
289
The list box displays the names of all attributes assigned to this user.
3
Select the attribute you want to edit and click Edit. The Edit Attribute dialog box
appears.
4
In the Edit Attribute dialog box, make the necessary changes to the attribute’s name
and value.
5
Click OK to save the changes and return to the Attributes property page.
6
To edit another attribute, click Apply and repeat Steps 3 through 5.
7
To save the changes and return to Directory Manager, click OK.
290
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
To remove an assigned attribute:
1
In Directory Manager, double-click the Client for which you want to remove
application object assignments. The Profile dialog box appears.
2
Click the Attributes tab.
The list box displays the names of all attributes assigned to this user.
3
To remove one or more attributes from the user, select the desired attribute and
click Remove.
4
To remove another attribute, click Apply and then repeat Step 3.
5
To save the settings and return to Directory Manager, click OK.
To edit a user definition:
1
In Directory Manager, double-click the user whose definition you want to modify.
2
You can modify the information on any of the property pages. Click Apply to save
your changes before moving to another property page.
3
When you have made all necessary changes, click OK to save the changes and
return to Directory Manager. To return to Directory Manager without saving
changes, click Cancel.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
n
291
Copying and deleting existing users
To copy a user:
1
From Directory Manager, locate and highlight the user or group you want to
duplicate.
2
On the File menu, select Copy. The Profile dialog box appears.
3
Change the necessary user information. You must set the Address/Client Login
field to be a unique value for the address type shown.
4
Click Apply to save any changes before moving to other property pages.
5
To preserve the settings on the Groups, Applications (local users only), and
Attributes (local users only) pages, click Yes. Click No to erase all settings on these
property pages.
The copied user appears in the user list. If this user is synchronized, all address
books are updated during the next directory synchronization.
To delete a user:
1
From Directory Manager, highlight the user you want to delete.
2
On the File menu, select Delete. A message box appears asking if you want to
delete the user.
292
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
3
Click Yes to permanently delete this user.
Note: Deleted records are not automatically removed from the Directory Manager
table. To remove deleted records and reuse the space they occupy, use the GEN
utility GENUSER to create a User ECF, drop the rows from the table, and then
process the User ECF to repopulate the table. You should then perform both a
Directory synchronization and a Gateway synchronization.
n
Working with user groups
User groups serve two functions in Directory Manager:
•
You can form specific units that share one or more traits in common. Then you may
assign the groups once to RemoteWare applications, instead of many times to
individual users. These groups are visible only at the Server; users never have direct
access to these groups.
•
You can turn a user group into a distribution list. The distribution list contains users
treated as a group and visible to other users. Using a group designated as a
distribution list sends the message to all users in that group.
To create a new user group:
1
From Directory Manager, click
New Group.
2
In the Group field, enter the name of the user group (up to 15 characters).
3
(Optional) Type a Description for this group. Although not required, the
description is helpful for users and Server Administrators.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
293
4
Select the Distribution List check box to allow users to use the user group as a
distribution list. Otherwise, the user group is only available to Server
Administrators.
5
Complete one of the following steps:
•
Click OK to save changes and close the Profile window. The group will have no
members if you stop at this point. You can add members to the group at any
time.
•
Click Apply to save changes, then click the Members tab to add users to this
group.
For instructions on adding users to user groups, see “Assigning users to user
groups” on page 294.
294
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Assigning users to user groups
To assign users to user groups:
1
From Directory Manager, highlight the group to which you want to add users.
2
On the File menu, select Edit. The Profile dialog box appears. The list box displays
all the users currently assigned to the group.
3
Click the Members tab.
4
To add one or more users to this user group, click Assign. The Select Users dialog
box appears.
C H A PTE R 1 1 / U s i ng R em o t eWar e M e ss a gi ng
5
6
295
Complete one or more of the following steps:
•
To view information about a selected user, click Item Detail.
•
To search for a user, enter the search criteria in the Search/Select box.
•
To assign one or more users, select the users and click OK.
•
To assign all users, select All Users and click OK.
On the Members page, click OK to save the assignments and return to Directory
Manager.
To unassign users from a group:
1
From Directory Manager, highlight the group from which you want to delete a user.
2
On the File menu, select Edit. The list box displays all the users currently assigned
to the group.
3
Click the Members tab.
4
Complete one of the following steps:
5
•
To unassign one or more users, select the users and click UnAssign.
•
To unassign all users, select UnAssign All.
Click OK to save the assignments and return to Directory Manager.
296
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Assigning applications to a user group
To assign an application to a user group:
1
From Directory Manager, highlight the group to which you want to assign
applications.
2
On the File menu, select Edit.
3
Select the Applications tab.
The Applications page lists all applications currently assigned to the user group.
4
To assign one or more applications, click Assign.
The Select Application Objects dialog box lists all application objects defined in
your RemoteWare system.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
5
6
297
Complete one or more of the following steps:
•
To search for an application, enter the search criteria in the Search/Select box.
•
To assign one or more applications, select the applications and click OK.
•
To assign all applications, click All App Objects and click OK.
On the Members page, click OK to save the assignments and return to Directory
Manager.
To unassign applications from a group:
1
From Directory Manager, highlight the group from which you want to delete an
application.
2
On the File menu, select Edit. The Profile dialog box appears.
3
Click the Members tab.
The list box displays all the application objects currently assigned to the group.
4
5
Complete one of the following steps:
•
To unassign one or more applications, select the users and click UnAssign.
•
To unassign all applications, select UnAssign All.
Click OK to save the assignments and return to Directory Manager.
298
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Editing an existing user group
To edit an existing user group:
1
From Directory Manager, highlight the group from which want to delete an
application.
2
On the File menu, select Edit. The Profile dialog box appears.
3
Make the necessary changes to settings on the Profile, Members, and Applications
pages. For specific instructions, see the previous sections.
4
When you have made all the necessary changes, click OK to save the changes and
return to Directory Manager.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
299
Copying a user group
To copy a user group:
1
From Directory Manager, locate and highlight the user group you want to copy.
2
On the File menu, select Copy. The Profile dialog box for the new group appears.
The information and settings in the Profile window match those of the user group
being copied.
3
In the Group field, enter a unique name for the new group.
4
Make additional changes to the Profile, Members, and Applications pages as
necessary.
5
When you have made all necessary changes, click OK to save the new user group
profile and return to Directory Manager.
300
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Deleting a user group
To delete a user group:
1
From Directory Manager, highlight the user group you want to delete.
2
On the File menu, select Delete. You are asked to confirm that you want to delete
this user group.
3
Click Yes to permanently delete the user group. User definitions that were
members of this group are not deleted. Click No to cancel.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
n
301
Viewing database assignments
Use the Messaging Administration program to view the current settings for the mail
transfer agent (MTA) on the RemoteWare Server.
To display the current database assignments:
Double-click the
Messaging Administration icon in the RemoteWare Menu.
This window displays each messaging subsystem and its corresponding database
information.
Note: You cannot change database assignments or values from the Database
Subsystems page. To modify database assignments, you must reinstall
Messaging Services from the RemoteWare CD. Do not modify the ODBC
Control Panel values.
302
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Setting Messaging Log options
Use Messaging Administration’s Messaging Log page to determine or view the current
values to maintain entries in the Messaging Log view in Log Viewer.
To set Messaging Log properties:
1
In RemoteWare Menu, double-click the
Messaging Administration icon.
The Messaging Administration window appears.
2
Click the Messaging Log tab.
3
In the History Log Size Option area, select a number from the Days to Maintain
History spin box. The value you select here determines the number of days for
which the log reports messages.
4
In the Logging Options area, select one of the following options for Message and
Recipients Per Message:
•
None. Displays no messages.
•
Errors Only. Displays only error messages.
•
Log All. Logs and displays all messages on your RemoteWare system.
The Messaging Statistics area of the Messaging Log property page displays the number
of total and failed messages currently stored in the Messaging Log. The values that
appear here are the values you select in the areas on the left side of the Messaging Log
page. For more information about the size and logging options and the impact of the
choices, see “Messaging Log page” in the RemoteWare Server Reference Manual.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
n
303
n Synchronizing address books
Directory
synchronization is
not the same function
as Gateway
synchronization.
Directory sync
reconciles differences
between
RemoteWare user
directories, while
Gateway sync
reconciles differences
between two different
messaging systems
on either side of a
gateway. For more
information, see
User additions and changes to the information contained in the Directory Manager
program immediately update the user directory database on the Server. However, the
Server must periodically instruct the user directory to produce a list of changes to
update the rest of the RemoteWare network. The Server then sends the changes to
Clients in order to synchronize the Server’s and user’s address book.
The settings on the Directory Synchronization property page in the Messaging
Administration program control when the updates occur. You can also use this page to
manually synchronize address books.
To access the Directory Synchronization page:
1
Open the Messaging Administration program.
2
Click the Directory Synchronization tab.
“Working with
Gateways” on
page 309..
You can synchronize the Server’s user directory and users’ address book in two ways:
Immediately and Periodically. Each of these methods is discussed in greater detail in
the following sections.
304
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Updating address books immediately
You can manually initiate an address book synchronization from either the Directory
Synchronization page or the Directory Manager program.
•
From Directory Synchronization page. Click the Check Now button. The
Messaging Administration program indicates when the procedure begins and
records the status in the Server Messages Log.
•
From Directory Manager program. On the File menu, select Initiate
Synchronization. The right portion of the Directory Manager status bar indicates
the procedure has begun. Directory Manager also places status messages in the
Server Messages Log. When synchronization is complete, highlighted user entries
revert to normal to indicate a successful synchronization.
Updating address books periodically
You can set the Messaging Administration program to periodically update address books
at a specified date and time or at specified intervals.
To specify the interval between updates:
1
In the Messaging Administration window, click the Directory Synchronization
tab.
2
In the Check Every n Days field, select an interval from 1 to 30 days. A manual
synchronization (using the Check Now button) will not affect or reset the specified
interval.
To specify the data and time for the next update:
1
In the Messaging Administration window, click the Directory Synchronization
tab.
2
Click Next Synchronization Date and Time.
3
In the Enter Date and Time dialog box, select the date and time you want the
address books to be updated.
When you select a time, pick a time when synchronization will have the least impact
on Clients. For example, if you typically communicate with Clients in the evening,
you may want to initiate synchronization after the calling or polling cycle is over.
Starting synchronization before connecting with Clients is risky; the operation may
not complete before the Clients begin to connect.
C H A PTE R 1 1 / U s i ng R em o t eWar e M e ss a gi ng
305
Preventing synchronization for specific users
By default, users in the Directory Manager program are synchronized after they are
assigned to a Client, meaning they receive addressing updates when changes occur to
the user profiles.
You may not want to enable synchronization for a user:
•
When the user has not been assigned to a Client
•
If the user is not part of the RemoteWare network (for example, a mail gateway or
Internet user definition).
•
If disabling synchronization avoids the accumulation of update records and
prevents users from sending messages to inactive recipients.
To disable synchronization for an existing user:
1
In the RemoteWare menu, double-click the
Directory Manager icon.
306
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
2
Double-click the user’s name for which you want to disable synchronization. The
Profile dialog box appears.
3
Clear the Include User in Address Book check box. This user will no longer
appear in address lists and will not receive address book updates after a directory
synchronization.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
307
n Setting non-delivery receipt options
The Message Transfer Agent (MTA) generates non-delivery receipts (NDRs) in two
situations:
•
When it encounters a message whose recipient’s address it cannot find
•
When it encounters a message that it cannot successfully deliver to the recipient
within the time frame specified on the Non-Delivery Receipt property page.
Use the Non-Delivery Receipt property page to specify the criteria for generating the
second type of NDR.
To access the Non-Delivery Receipt property page:
1
In the RemoteWare menu, double-click the
2
Click the Non-Delivery Receipt tab.
Messaging Administration icon.
308
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Table 11, “Managing non-delivery receipts,” lists some common tasks you may need to
perform when managing non-delivery receipts.
Table 11. Managing non-delivery receipts
To
Do this
Change the number of days the MTA attempts
to deliver a message before generating an NDR
In the Produce Non-Delivery Receipt if
message has not been delivered to the
Client in n Days field to specify a period of
time from 1 to 60 days.
Specify how often to check the message store
for messages that have not been delivered
successfully by the specified number of days
Change the Check Every n Days field to set
the desired polling interval for messages in the
Server’s message store.
Check for non-deliverable messages
Click the Check Now button. The Server
generates NDRs and sends them to the
originator’s mailbox.
Specify at what time to check for NDRs
Click the Next Non-Delivery Receipt clean
Starting Time button to set the date (mm/dd/
yy) and time (hh:mm:ss) to check for NDRs.
The date and time specified controls when the
Check every n days field is executed.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
n
309
Working with Gateways
The RemoteWare Gateway consists of software at the Exchange Server that exchanges
messages between the messaging subsystems of the Exchange Server and the
RemoteWare Server.
You install the software on an Exchange Server, where it creates the RemoteWare
Gateway service and references the RemoteWare Server. It also registers itself on the
RemoteWare Server and accesses the ...\sysfiles\gateways shared directory. For more
information about installation, see the RemoteWare Installation Guide.
Before you can use the RemoteWare Gateway to exchange messages between these two
subsystems, you must first configure RemoteWare Gateway using the Microsoft
Exchange Administrator at the Exchange Server computer. You should configure
RemoteWare Gateway immediately after you install it.
310
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Accessing the RemoteWare Gateway properties pages
To start the Microsoft Exchange Administrator program:
1
Select Microsoft Exchange Administrator from the Programs group on the Start
menu.
2
In the left pane of the Microsoft Exchange Administrator main window, select the
Connections item.
3
From the list of connections in the right pane, double-click RemoteWare
Gateway to display the RemoteWare Gateway Properties pages.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
311
Configuring the RemoteWare Gateway
1
From the RemoteWare Gateway Properties window, click the Configuration tab.
2
Verify that the Display Name and Email Address fields in the System Administrator
section contain a valid account for users who need to contact the System
Administrator by mail.
3
Click the field next to the RemoteWare Gateways Directory button and type the
UNC path name to the RemoteWare Server’s ...\sysfiles\gateways directory. This
corresponds to the install directory specified during installation.
Note: Do not use the RemoteWare Gateways Directory button. Instead, type the path
in the adjacent field.
You should have set up a share to this directory with full access rights for both the
RemoteWare Gateway and the RemoteWare Server service accounts.
312
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
4
Click the Select SQL Connection to RemoteWare Directory button. The
RemoteWare Directory Database dialog box appears.
5
Click Configure ODBC Connection to select the database on the SQL Server
that corresponds to the Directory subsystem for the RemoteWare Server. To verify
this value, go to the RemoteWare Server Messaging Administration program and
display the Database Subsystems page. The correct database is listed in the
Assigned Database column for the Directory Subsystem entry. For more
information, see “Viewing database assignments” on page 301.
6
Click OK to return to the RemoteWare Gateway Properties window when you are
finished.
7
After you have configured the RemoteWare Gateway service, stop and restart the
RemoteWare/Exchange Synchronization service on the Control Panel of the
Exchange server.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
n
Gateway
synchronization is
not the same function
as Directory
synchronization.
Gateway sync
reconciles differences
between two different
messaging
subsystems on either
side of a gateway,
while Directory sync
reconciles differences
between
RemoteWare user
directories.
For more
information, see
313
Activating Gateway synchronization
The Directory Synchronization property page enables you to populate the Microsoft
Exchange Server with the RemoteWare addresses and vice versa.
To activate synchronization:
1
From the RemoteWare Gateway Properties window, click the Directory
Synchronization tab.
2
Choose one or more of the following:
“Synchronizing
address books”
on page 303.
3
•
Select the Synchronize Exchange Server Users with RemoteWare
Directory check box to populate the Exchange Server with RemoteWare
addresses.
•
Select the Synchronize RemoteWare Server Users with Exchange
Directory check box to update the RemoteWare user directory with Exchange
users.
If necessary, click Initiate Synchronization to reconcile user directories for the
selected option.
314
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Maintaining Gateways
Use the Gateway Manager page in the Messaging Administration program to view the
current settings for the RemoteWare Gateway and allows you to set the available
address types.
To view the current values:
1
In the RemoteWare Menu, double-click the
icon.
2
Click the Gateway Manager tab.
Messaging Administration
This window displays the gateway name, its location, capabilities, and status.
Note: To modify the Gateway name or location, you must use the RemoteWare CD
and reinstall RemoteWare Gateway on the Exchange Server computer.
C H A PTE R 1 1 / U s i ng R em o t eWar e M e ss a gi ng
315
To define valid address types for the gateway:
1
On the Gateway Manager page, double-click the gateway item. The RemoteWare
Gateway dialog box appears.
2
Select the address types from the Type List and click Add. The types in the
Selected Types list box are available when defining remote users in the Directory
Manager program.
316
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Configuring and using MAPI services
Two menu items in the Messaging Administration program allow you to maintain the
attributes MAPI’s Message Store (also known as Personal Folders) and the Address
Book for the configuration of the MTA profile. You can also access these windows from
the Mail and Fax program in Windows Control Panel.
Working with the Message Store Service
To access the MAPI Message Store:
Click the MAPI MS tool.
Table 12, “Managing MAPI personal folders,” describes some of the common tasks you
may need to perform from this window.
Table 12. Managing MAPI personal folders
To
Do this
Change the name of the personal folder
Highlight the old name in the Name field and
enter the new name.
Modify the personal folder file path
The path value cannot be changed directly. To
change the existing personal folder file, copy it
to another location, then use the Mail and Fax
program in Windows Control Panel to create a
new personal folder and specify a new location.
Change the password on the personal folder file
Click Change Password. Type the old and
new password, then verify the new password.
Optimize your personal folder file to make the
resulting file smaller
Click Compact Now.
C H A PT ER 1 1 / Us i ng R em o t eWar e M e s sa gi n g
317
Working with the Address Book Service
You can access to RemoteWare’s Personal Address book from the Messaging
Administration program.
To view the window:
Click the MAPI AB tool.
n
Tip: To view the
address book, you
can also select MAPI
Message Store
Service on the
Command menu.
Table 13, “Managing the Personal Address Book,” explains how to perform some of the
most common tasks related to managing the Personal Address Book.
Table 13. Managing the Personal Address Book
To
Do this
Change the name of the address book
Highlight the current contents of the Name
field and type a new name for this address book.
Specify a new location for the address file (or
change to another address file)
Click the Browse button or type the new path
and file name in the Path field.
Create a new address file
You cannot create a new address file from this
window. Run the RemoteWare installation
program to generate this file.
Change the naming order
Click the appropriate option button in the Show
Names by section.
318
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
A P P E N D I X
A
AREMOTEW
ARE
Delivering RemoteWare Scripts
This appendix describes how to deliver a script to RemoteWare Clients using ESD work
objects. It does not cover details of writing and enhancing scripts. For more information
on creating and using RemoteWare scripts please refer to the RemoteWare 32-Bit
Windows Client User’s Guide and Summit Software’s BasicScript Programmer’s Guide.
The procedures described in this appendix assume the reader is familiar with Windows
95/98/Me, Windows NT/2000/XP, and the RemoteWare Server. In addition, the script
writer must know the names of any dial-up networking entries on the Client if the writer
plans to use them.
The appendix provides instructions for the following tasks:
• Creating a RemoteWare script
• Testing the script
• Placing scripts on the Server
• Creating the scripts ESD work object
320
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n Creating the RemoteWare Script
All RemoteWare scripts must be created on a RemoteWare Client using the Script
wizard.
To start the script wizard and define the script:
1
Start the Client application and go to the Scripts view.
2
Double-click the Make New Script icon.
The script wizard opens. Follow the wizard’s instructions to create the desired
script. For more information on using the script wizard please refer to the
RemoteWare 32-Bit Windows Client User’s Guide.
3
After the wizard has completed your script, it will be stored as
x:\ClientInstall\nodesys\script\Scriptname.rws, where x: is the drive on which the
RemoteWare Client software was installed and ClientInstall is the directory where
you installed the software.
Note: Scripts that contain Client-specific information, such as Dial-up Networking
(RAS) connections, may need a separate script per Client.
Testing the script
You can test scripts by starting the RWSED.EXE program located in the
x:\ClientInstall\nodesys directory (where x: is the drive and ClientInstall is the directory
where you installed the RemoteWare Client application). After starting RWSED you
can load any script, then debug and edit it. Do not compile or bind the script.
Placing scripts on the Server
Copy verified scripts to a drive and directory accessible by the RemoteWare Server, for
example c:\CRS\scripts. This is the directory where the ESD work object created later
in this section will look for the scripts to deliver to other Clients. Updated scripts placed
in this directory will be automatically sent to the Clients during the next connection.
To transfer the script from the Client to the Server, complete one of the following
actions:
•
copy the .RWS file from the Client
•
use Interactive Session to get the file from a remote Client
•
set up a work object to get all new .RWS files from a specific directory and place
them in the c:\CRS\scripts directory on the Server.
A P P E N D I X A / D e l i v e r i n g R e m o t e Wa r e S c r i p t s
321
Creating the scripts ESD work object
Create a RemoteWare ESD work object to deliver and keep the scripts up to date:
1
Start the RemoteWare Server Work Object Editor program.
2
On the File menu, select New, then ESD Object.
3
Enter a unique name to identify the work object, for example “Deliver Client
Scripts.”
4
Set any general attributes you may require for this work object. For more
information, see the RemoteWare Server Reference Manual.
5
Click the Events tab.
6
On the Add Events menu, select File transfer, then SEND file(s) to Client.
7
Type the drive letter and path name where you placed the script files in the “Place
scripts on the Server” section in the Server Filename or Wildcard field. Using the
example from that section, you would type c:\CRS\scripts\*.RWS.
8
Type <ClientInstall>\nodesys\scripts\*.RWS for the Client Filename or Wild Card
or Directory field and click Done.
9
Assign the ESD work object to an appropriate session and the desired Clients.
The next time the Client and Server communicate and run the session selected above
the latest versions of the Scripts will be delivered to the Client.
322
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
A P P E N D I X
B
BREMOTEW
ARE
Tuning a RemoteWare Cluster
Network-based RemoteWare Servers require an extremely high performance
networking environment to rapidly exchange information and to robustly handle
network disturbances.
This appendix presents advanced information for the experienced Server Administrator.
It describes the configuration for a file server connection used when implementing a
RemoteWare Cluster, or a single Server with a remote data drive.
The procedures and information are intended to tune the Windows NT networking
environment, to ride out network disturbances, and to configure the network to be as
clean a network environment as possible. The final goal is to optimize the RemoteWare
Server’s network file I/O connection to the remote data drive that contains the shared
Cluster data files.
324
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
n
Network topology considerations
•
•
•
•
n
Check the physical configuration of the network connecting the RemoteWare Servers, Workstations and remote data drive. The Servers, Workstations and the data
drive should be located on a separate segment of the network. They should be connected to each other with an Ethernet switch to insure maximum bandwidth. Additional or excessive links between the Server and its data drive are a potential source
of network errors.
Check drivers and network interface card (NIC) configurations. There have been
issues reported in some drivers distributed with the Windows NT 4.0 CD-ROM,
particularly the AMD PCNET PCI Ethernet Adapter used in many HP Vectra XU
desktop computers. Make sure you have the latest driver and any patches or service
packs. Sources for NIC drivers are the computer manufacturer’s web site, network
card manufacturer’s web site, and the web site for the manufacturer of the driver
circuit used on the NIC.
Configure the network transport used for the RemoteWare Server. The RemoteWare Server and the data drive file server network protocols and bindings determine
the type and path of network connection(s) used to support network file I/O for the
RemoteWare Servers. RemoteWare has been tested using the tuning parameters
described in this appendix for the TCP/IP transport.
A timeout value for the network connection should be set to 20 to 40 seconds for
initial values. Network errors which cannot be corrected within this time interval are
very serious.
Transports and binding orders
1
On the file server that contains the RemoteWare ‘data drive’, open the Network
control panel applet and click the Protocols tab. Verify that the TCP/IP transport is
installed.
2
On all RemoteWare Servers and RemoteWare Workstations:
•
Open the Network control panel applet and click the Protocols tab. Verify that
the TCP/IP transport is installed.
•
In the Network control panel applet, choose the Bindings tab, and choose all
services in the Show Bindings for field.
•
Open the tree control for the Workstation service.
•
Verify that the WINS Client (TCP/IP) protocol is listed first in the Workstation
service subtree (the possible choices are WINS Client (TCP/IP), NetBEUI
Protocol or NWLink NetBIOS (SPX/ IPX)). If WINS Client (TCP/IP) is not at
A P P E N D I X B / Tu n i n g a R e m o t e W a r e C l u s t e r
325
the top of the list, highlight it and click the Move Up button to move it up in
the binding order.
•
n
Again under the Workstation service, open the subtree of the TCP/IP protocol.
If you see more than one network adapter listed (you might see RAS even if you
only have one network card in your system), highlight and move to the top of
the list the network adapter for the primary connection between the file server
and RemoteWare Server. Your choice should be the first network card installed
in the system designated by the (1) after the network card icon.
Registry settings
Use the Registry Editor to set the following network tuning parameters. If the
parameters are not present, the default value is in effect.
On all RemoteWare Servers, all RemoteWare Workstations and the file server
that contains the RemoteWare data drive, add or modify the following value:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\
Services\Tcpip\Parameters\TcpMaxDataRetransmissions
REG_DWORD
Default = 5 (attempts)
On all RemoteWare Servers and all RemoteWare Workstations, add or modify the
following value:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\
LanmanWorkstation\Parameters\SessTimeout
REG_DWORD
Default: 45 (seconds)
The following registry value settings have been empirically determined for different
timeout settings. Note that a LAN session timeout will occur when the minimum of the
SessTimeout and transport timeout values as specified below expires.
Table 1. TCP values
Tolerance goal
TcpMaxDataRetransmissions
SessTimeout
12 seconds
(default)
(default)
25 seconds
6
51
326
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Table 1. TCP values
Tolerance goal
TcpMaxDataRetransmissions
SessTimeout
50 seconds
7
103
102 seconds (1 min, 42 sec)
8
205
204 seconds (3 min, 24 sec)
9
410
409 seconds (6 min, 49 sec)
10
819
A P P E N D I X
C
CREMOTEW
ARE
RemoteWare Database Schema
Below are fields and descriptions of fields for the following logs and messaging
functions in RemoteWare:
• RWLOG_SessionHistory LOG VERSION: 4.00.0055.0000.4
• RWLOG_FileTransfers LOG VERSION: 4.00.0055.0000.2
• RWLOG_Messaging LOG VERSION: 4.00.0055.0000.2
• RWLOG_MsgRecipients LOG VERSION: 4.00.0055.0000.1
• RWLOG_ServerMessages LOG VERSION: 4.00.0055.0000.3
• RWLOG_Inventory LOG VERSION: 4.00.0055.0000.1
328
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
History LOG VERSION:
n RWLOG_Session
4.00.0055.0000.4
Field Name
ROW_ID
event_file
Attributes
int
int
status
failure_reason
varchar (50)
int
Field Description
Table index (internal)
Identifies log file that contains detail information
(internal)
Text description of the session status
Description of the reason for failure (see options
below)
failure_reason Defines
start_time
end_time
datetime
(8) bytes
datetime
(8) bytes
0
Undefined error
1
Unable to connect
2
Failed due to critical event
3
Timeout waiting for client
4
Failed due to lost link
5
Client modem did not answer
6
Got a busy signal
7
No Dial Tone on host line
8
Error trying to dial modem
9
Unable to get resources
10 Invalid client password
11 Invalid system serial number
12 System was rebooted
13 Invalid Default Disk Drive
14 Send ESD Failed
15 Out of range session
16 Wrong Client Name
17 Session was unscheduled
18 User Aborted Session
19 Client Security Failed
20 Registration disabled
Start time and date of session
End time and date of session
APPE NDI X C /
duration
baud_rate
client_id
netmgr_id
total_events
current_event
int
int
int
int
int
int
ok_events
int
events_logged
int
resource
client_type
varchar (50)
int
329
Duration of the session
Connection baud rate (Async)
Client identification number (internal)
Server identification number (internal)
Total number of events in details
Number of the event being processed when the
session was interrupted. If the session completed or
never started, current event is zero.
Number of events that were successful in the session
Internal flag that indicates events were logged for
the session
Resource name e.g., TCP/IP, NetBIOS, Async, SPX
Client type (see options below)
client_type Options
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
DOS Asnyc Client
OS/2 Client
VMS Alpha Client
VMS Vax Client
Linux 6.X Client
SCO Unix Client
IBM 4680 Client
NetBios Dos Client
SCO Unix TCP/IP
HP UNIX - TCPIP
HP UNIX - Async
Windows 3.x Client
AIX RISC TCP/IP
AIX RISC Async Client
UnixWare Async Client
UnixWare TCPIP Client
VMS Alpha TCPIP Client
IBM 4690 Client
Windows 95 (Chicago) Client
Windows NT Client
330
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
20
resource_type
int
was Windows NT for Alpha Client now
NCR RAS UNIX
21 was Windows CE Client now NCR RAS
TCP
22 Sun Solaris Asynch
23 Sun Solaris TCPIP
Resource identification number that represents the
text string in the Resource field (see options below)
resource type int Options
comm_flags
int
retrys_left
total_trys
netmgr_name
client_name
ld_class
session_name
status_code
int
int
varchar (16)
varchar (9)
int
varchar (42)
int
0
ASYNC
1
X25
2
NETBIOS
3
PROCESS_ONLY
4
UNUSED
5
TCPIP
6
SPX
Internal set of flags that define the communication
state
Remaining number of retries for the session
The number of tries it took to complete the session
Server name
Client name
Long distance class index (internal)
Session name from session editor
Codes that define the status of the session (see
options below)
Status Bit Mask Defines
session_slot
session_rec
int
int
0x00 Session Entry is uninitialized
0x01 Session was successful
0x02 Session Failed
0x04 Failed Session Recovered
0x08 Final Session Log Entry
Index into an internal status table (internal)
Index into an internal session file (internal)
APPE NDI X C /
331
LOG VERSION:
n RWLOG_FileTransfers
4.00.0055.0000.2
Field Name
ROW_ID
status
status_raw
Attributes
int
varchar (50)
int
Field Description
Table index (internal)
Text representation of the file transfer status
Numeric representation of the file transfer status
(see options below)
status_raw int Options
eventcmd
eventcmd_raw
varchar (50)
int
0x0000 Command not executed
0x0004 Completed Successfully
0x0008 Command Failed
Event command
Numeric representation of the event command (see
options below)
eventcmd_raw int Options
eventid
cmprs_rate
start_time
end_time
file_size
datetime
failure_code
failure_reason
client_id
session_id
netmgr_id
valid_mask
int
int
datetime
(8) bytes
datetime
(8) bytes
Int
datetime
(8) bytes
int
varchar (150)
int
int
int
int
1
Send File to Client
2
Get File from Client
3
Send Server Directory
4
Get Client Directory
50
Check and Send File
Identifies the event: 1 for SendFile, 2 for GetFile
Compression rate for transfer
Start time and date of transfer
End time and date of transfer
File size in bytes
Date and time file was created or changed
NT failure code
Text description of the failure code
Client id index of client in system data (internal)
Session id index of session in system data (internal)
Server id index of server in system data (internal)
Flags indicating which information is valid. (see
options below)
Valid Field Masks for wValidMask
332
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
filename
client_name
hostpath
clientpath
varchar (261)
varchar (9)
varchar (261)
varchar (261)
0x0001 File Size & Date is Valid
0x0002 Compression Rate is Valid
0x0004 Valid Dos Error Code
0x0008 Valid No Execute Error
0x0010 Extended attributes included
0x0020 Extended attributes processed
Name of file being transferred
Client name
Path name of the file on the server
Path name of the file on the client
APPE NDI X C /
LOG VERSION:
n RWLOG_Messaging
4.00.0055.0000.2
Attributes
ROW_ID
int
pr_msg_id
int
pr_orig_user_name
varchar 100)
pr_orig_user_addr
varchar (255)
pr_orig_user_addr_type varchar (10)
Field Name
pr_orig_client_name
pr_priority
pr_size
pr_date_time
pr_status
pr_subject
pr_msg_type
pr_sent_date_time
varchar (10)
int
int
datetime
(8) bytes
int
varchar (100)
varchar (100)
datetime
(8) bytes
Field Description
Table index (internal)
Unique message identifier
Originator of the message
Originator's address
Address type (the type of mail system
used by originator)
RemoteWare Client name
Priority of the message
Size of the message
Process date and time
Status of the message
Subject of the message
Text version of the type of message
Date and time sent
333
334
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
LOG VERSION:
n RWLOG_MsgRecipients
4.00.0055.0000.1
Field Name
ROW_ID
pr_msg_id
Attributes
int
int
pr_recip_user_addr
pr_recip_client_name
varchar (255)
varchar (10)
pr_status
pr_recip_user_name
pr_recip_type
int
varchar (100)
int
Field Description
Table index (internal)
Message identifier (matches originating
message identifier)
Address of the recipient
RemoteWare Client name when type is
RW
Status of the message for recipient
Recipient of the message
Recipient type
APPEN DI X C /
335
LOG VERSION:
n RWLOG_ServerMessages
4.00.0055.0000.3
Field Name
ROW_ID
time
pid
netmgr
netuser
message_type
message_type
_raw
Attributes
int
datetime
(8) bytes
int
varchar (20)
varchar (20)
varchar (20)
int
Field Description
Table index (internal)
Date and time the message was processed
Identification number of the process that originated
the message
Network manager
Network user
Description of the message type
Numeric representation of the message type (see
options below)
message_type_raw int Options
message_flags
message_ text
explanation
actions
int
varchar (500)
varchar (500)
varchar (500)
sys_error_cod
e
sys_error_text
int
0x00 Fatal error message
0x01 Error message
0x02 Informational message
0x03 Debug message
0x04 User message
Internal flags that define the message (internal)
Message description in text
Text that further defines the message
Text that describes actions the user might take in
response to the message (optional)
System error code
varchar (500)
Text description of the system error code
336
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
LOG VERSION:
n RWLOG_In+ventory
4.00.0055.0000.1
Field Name
ROW_ID
ClientName
Type
XTimeStamp
Activity
ActivityID
XInt1
Attributes
int
varchar (255)
varchar (255)
datetime
(8) bytes
varchar (255)
varchar (255)
int
Field Description
Table index (internal)
Client name
Type of record
Process date and time
Text description of the activity
Specific activity identifier
Internal identifier
Glossary
This Glossary defines the terms and acronyms used in the RemoteWare documentation.
A
Abort
A command to stop an operation in progress. In
RemoteWare, used to stop a session on the
Server (in the Interactive Session or Schedule
Manager programs) or a connection at the
Client.
Accounts (Windows NT, RemoteWare
Server)
A user name, password, access rights, and other
characteristics that identify a user to the Server
and the operating system.
Activation
A definable date and time when a work object is
permitted to start executing. The activation and
deactivation define a timespan when the object
may execute.
Address
1 Client address is the set of characters that
defines how to reach a Client through a network.
You can define this value from the Client Profile
Server page. Also, the Client Profile Information
page can include a contact address, but this value
is for information only; it is not used by
RemoteWare.
2 Network address is a specially formatted
sequence of letters and numbers used by a
network to define this computer or to access
another network device.
3 An indirect address is any addressing
information placed in a file and referenced by
some method in a RemoteWare program.
Another application or process can then modify
the address without having to access or
manipulate the RemoteWare system.
4 User addresses are relevant to RemoteWare
Messaging Services and the applications which
use messaging. Addresses are unique identifiers
assigned to local and remote users for the
purpose of exchanging message-based
information. Addresses are stored in the User
Directory subsystem, are managed in the
Directory Manager program, and are the
originating point for all messaging activity.
5 Server address is the IP address (such as
127.0.0.1) or DNS name (such as
rw01.xcellenet.com) that a RemoteWare Client
uses to access the RemoteWare Server over the
SPX or TCP/IP transport.eaddress is the IP
address (such as 127.0.0.1) or DNS name (such
as rw01.xcellenet.com) that a RemoteWare
Client uses to access the RemoteWare Server
over the SPX or TCP/IP transport.
Address book
Stores electronic mail addresses and other
personal messaging information such as names,
phones, fax numbers, and mail addresses from
multiple service providers. The address book is
accessible from any system that uses MAPI.
338
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Address type
In messaging systems, specifies the transfer
format for transferring messages. Some examples
are SMTP for Internet mail and X400.
Administrator
A Server program that controls and changes
account access rights to other RemoteWare
programs, and can perform maintenance
functions for Server processes, log files, and
Clustered Servers.
After event
On the Work Object Editor Events page or in
the Worklist Editor, an after event is a task that
executes after a Client connection has ended.
This type of event is commonly used for
administrative and cleanup duties that do not
require a Client connection. See also Before
event.
Alarm
Notification of a significant issue at the Server or
Client. Clients display Alert icons, while the
Server records a message in the Server Log and
displays alarms in the Network Status window.
See also Alert icon.
Alarm thresholds
A numeric value the Server uses to determine
when to issue an alarm. Alarm thresholds are set
from the Server Profile Alarms page.
Alert icon
On the Client, a series of icons at the lower right
of the Client Communications window that
appear when a significant issue relevant to the
Client occurs. Alert icons include notification of
a resource error, ESD arrival, auto answer off,
and ESD off.
Alerts folder
On the Client, a folder in the Client
Communications window. Alerts are added to
the folder with a significant issue relevant to the
Client occurs. Alerts include notification of a
resource error, user-disabled features, and ESD
arrival.
Alternate resource
In the Client Profile on the Server or the Auto
Communications at the Client, defines the
transport medium and hardware to use when an
attempt to use the Primary Resource is
unsuccessful. Set this value on the Server at the
Client Profile Server and Client cards, or from
the Client at the Auto Communications
(winauto.exe) program.
Answer on ring
On the Server Profile Modems page, the Edit
Modem window defines the command that is
sent to the modem to answer a ringing line. This
command is only sent if the option is enabled
and allows the Server to control when calls are
accepted. This option prevents the modem from
accepting a call when the Server or Scheduler is
down or disabled.
Answer Response File
In Software Manager, the file that guides the
installation program at the Client. These files are
usually prepared by the software manufacturer
or produced to meet specific needs by a
configuration program and are used in automatic
installation so that no user intervention is
required.
Application
1 Any software that performs a task.
2 In the Work Object Editor, a type of object
that associates (assigns) one or more files and
defines a set of common tools for distribution to
Clients.
3 RemoteWare Applications are a set of
enabling technologies that allow Client users to
perform functions in addition to Client
communications. An example is RemoteWare
Messaging Services.
Application group
A type of work object that can be used to
organize application work objects into a single
unit.
Application Listbox
In Workshop, an Application Listbox displays
only those applications specifically assigned, at
the RemoteWare Server, to the Client user who
is logged in at runtime. Therefore, an application
list varies depending upon who is logged onto
the system.
Application Work object
See Work object.
Glossar y
339
Assignments
Autosubscribe
To identify an object, Client, user, or session as
belonging to a different item in the same list.
When referenced, assigned items function as a
group.
In Software Manager, an option which enables
administrators to force the Client to subscribe to
a package. When this option is enabled, the
package’s contents are pushed to the Client
when a connection to the RemoteWare Server
occurs. Client users are unable to unsubscribe
from an autosubscribe package.
Async
An abbreviated term for the asynchronous
transport. See also Asynchronous.
Asynchronous
A transport protocol for exchanging information
between the Client and Server. This protocol
commonly uses modems, phone lines, public
networks, and serial ports for hardware.
AT commands
Instructions sent to a modem to perform
configuration, dialing, and disconnection
operations. These commands usually begin with
the characters AT and make part of a quasistandard set of commands used to operate
modems.
AT style modem
An asynchronous device that understands and
uses AT commands to transmit information over
a serial port and a phone line. See also AT
commands.
Attributes
In Directory Manager, a set of tags and their
values that can be assigned to a user and applied
at his or her Client.
Auto answer
On a modem, refers to the command or the state
where the modem answers any ringing line,
regardless of whether the computer or Server is
ready to accept the call.
Auto Logout
In Workshop, when the Logout function is
enabled, the Client user is automatically logged
off a Workshop application. The Client user signs
back into the Workshop application using the
Workshop Login dialog box.
Auto Communications
A Client program that can automatically
schedule an inbound connection from the
command line or when launching the program.
The program name is WinAuto.exe.
B
BasicScript
In Workshop, this is the script language used to
write procedures in response to user and system
events. BasicScript is very similar to the Visual
Basic programming language. Like Visual Basic,
BasicScript allows usage of OLE automation
techniques to manipulate Workshop controls,
and third-party OCX or ActiveX controls you add
to Workshop applications.
Before event
In the Work Object Editor and Worklist Editor, a
task defined to execute before a connection takes
place with the Client. Before events may be used
to prepare for a connection without incurring
connection costs, and must be used exclusively
for Process Only sessions. See also After event.
Bits per second
The total number of indivisible information units
transferred between two locations in a second.
The bps measurement is used instead of baud
rate because there is less room for
misinterpreting the transfer rate.
Build Application
In Workshop, after an application is designed the
Build Application function is used to create the
Workshop application file. This file is in a
complied format and contains the basic
information about an application plus all of the
associated forms.
Byte Level Differencing
This feature detects differences between file
versions at the Server and the Client and sends
only the differences to the Client or Server,
which reduces the time required to update files
and software.
340
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Byte Level Differencing is available for the
SEND and GET events in the Work Object
Editor and Worklist Editor.
C
Calendar session
In the Session Editor, a type of session that
executes on set days and times. See also
Dependent session; Fixed session.
Calling
A connection state in which a computer is
attempting to contact another computer. If
successful, the next state is connecting.
of cleanup: full and normal. See also Full
cleanup; Non-Setup based installation.
Client
A computer that uses RemoteWare to access
centralized resources provided by another
computer (called the RemoteWare Server). See
also 16-bit Client; 32-bit Client; Template
Client.
Client Profile
The RemoteWare Server program used to define
RemoteWare Clients and create Client
installation kits. This program is called the Node
Profile in RemoteWare for OS/2.
Carriage return
Client type
1 In general, a nonprintable character that
represents the end of a command, instruction,
modem, or character string.
2 On RemoteWare, the exclamation mark ( ! )
or <cr> represents the carriage return character,
and is used to instruct a modem to start
executing any pending commands.
The operating environment that determines
which software is provided for the Client. The
Client type determines the features and
functionality available at the remote computer.
Case sensitive
An option that causes the computer to
distinguish between uppercase and lowercase
alphabetic characters. Therefore, “ECF” and
“Ecf” are interpreted differently if case
sensitivity is enabled.
Check if newer
During a file transfer event, this option only
sends the file if the source has a more recent
time and date stamp than the destination.
Check updates only
For file transfer events, transfers a file only if the
time, size, or date differs. This event option can
shorten the connect time since files are not
unconditionally transferred.
Checkpoint restart
The RemoteWare feature that enables failed or
interrupted communication sessions to restart at
the point of interruption rather than from the
beginning.
Cleanup
In Software Manager, the process of clearing all
installation files associated with a software
package. Software Manager provides two types
Client View
In Inventory Manager, the display of inventory
scanning results on a per-Client basis. See also
Client View; Custom Field; Inventory View.
Cluster (also Clustered Servers)
A collection of two to five Servers that share a
system name, serial number, and one data
directory. Clusters can not only collectively
handle more concurrent sessions, but they also
provide fault tolerance against a down Server
and load balancing across all Clustered Servers.
Comma Separated Value (CSV) file
In Report Manager, a report format that
separates each report entry with a comma and
removes other formatting. CSV files can be
imported into spreadsheet applications for
further analysis and manipulation. There are two
types of CSV files: standard and enhanced.
Standard CSV files eliminate report descriptions,
headings, and additional formatting. Enhanced
CSV files include a set of tags that are used to
identify the information on each line of the
report.
Command line
1 The point of interaction in a characterbased user interface. Commands, such as those
issued from the DOS command prompt, are
typed at the command line.
Glossar y
2 In the Work Object Editor, a field on the
Application Attributes page which allows you to
enter a command for the command line.
Command prompt
1 In a command line environment (such as
DOS), the location where commands are
displayed and executed when typed.
2 In the Interactive Session program, a field
that accepts typed commands for execution at
the program, at the Server, or at the Client.
Commands
An action or instruction that makes a computer
perform a specific task.
Comment
In the Work Object Editor and Worklist Editor,
an event that contains descriptive information
but is not processed by the Server. In the Dial
Script Editor, a line that is not used to connect
but provides additional information supplied by
the dial script’s creator.
Common-ISDN-API (CAPI)
An application programming interface standard
used to access ISDN (qv) equipment connected
to basic rate interfaces (BRI) and primary rate
interfaces (PRI). By adhering to the standard,
applications can make use of well-defined
mechanisms for communications over ISDN
lines, without being forced to adjust to the
idiosyncrasies of hardware vendor
implementations.
Compiled
A set of instructions that have been analyzed for
correctness and streamlined for execution. In
RemoteWare, dial scripts must be compiled to
validate the commands and make them available
to the Server or Client.
Completed
A session or work object status that indicates one
or more events were unsuccessful. The Session
History Log detail contains information on which
event failed or was not executed.
COM Port
Refers to an asynchronous serial port on a
computer or on a multichannel communications
board. Serial ports are also called COM ports
because the hardware and software refers to
341
specific ports as COM1, COM2, and so on.
RemoteWare recognizes up to 36 COM ports for
Servers and 4 COM ports for 16-bit Windows
Clients.
Compression
The process of analyzing and transforming data
so that it occupies less storage, less memory, and
takes less time to transfer. As an option,
compression may be performed by the Server
(by file extension, event, and globally) or by the
modem.
Concurrent
An action that occurs at the same time as
another. On RemoteWare, a Server can process
up to 64 concurrent sessions.
Conditional
The capability in a worklist to execute or skip one
or more events based on the status or outcome of
another event. Conditional events and the
Conditional option for an event allow events to
be skipped in a worklist.
Conditional event
1 An event in a worklist for which the
Conditional option is enabled. This event is
either skipped or executed based on the status of
the most recently executed event.
2 One of several events that can be used to
execute or skip one or more events based on the
status of a specified situation.
Connected
A connection state in which the Client and
Server have successfully completed security
procedures and are ready to execute a session.
Connecting
The connection state in which the Client and the
Server’s modem have completed a connection,
but the Client still has yet to complete the
security procedure.
Control panel
A Windows program that contains applets for
configuring the Windows operating
environment. On the Server, the Services and
System applets in Control Panel are frequently
used for RemoteWare settings.
342
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Criteria checking
In Software Manager, the feature which enables
administrators to set certain criteria, including
hard disk space, file delivery, and registry keys,
for a package. If a Client does not meet the
specified criteria for a package, Software
Manager will not deliver or install the package.
RemoteWare uses bits per second (bps) to
measure the data rate.
Deactivation
In the Work Object Editor, a date and time that
is optionally set and determines when the object
should no longer execute. See also Activation.
Critical
Default execution
A session status indicating that an unsuccessful
event terminated the session. An event must
have its Critical option enabled for this status to
occur.
In the Work Object Editor, an option on the
General Attributes page that causes the object to
execute unless the Client has explicitly disabled
this object from the Tasks page.
CSV file
Default inbound
See Comma Separated Value (CSV) file.
A system defined session the Server uses when a
Client placing an inbound connection has no
assigned inbound session. See also Inbound.
Custom Field
In Inventory Manager, a customized field of data
created by the administrator and associated with
one or more Clients’ retrieved inventory data in
the SQL database. See also Custom View,
Inventory View, Client View.
Custom View
In Inventory Manager, a display of inventory
scanning results designed by the administrator to
meet specific needs. By applying search
parameters to the data maintained in the
inventory database, administrators customize the
display of inventory information. See also
Client View; Custom Field; Inventory View.
Dependent session
In Session Editor, one of three session types.
Dependent sessions execute based on the
outcome of a monitored session, and are not
scheduled. See also Calendar session; Fixed
session; Monitored session.
Detail
In general, an information display that lists the
item and its particulars. Most RemoteWare log
programs and many other items use details to
display general and specialized information.
Detail window
D
DAT file
See Virus signature file.
Data drive
The drive letter or network volume containing
the active \sysfiles directory. Standalone Servers
can use local, NT, or Novell volumes, but
Clustered Servers must use and share the same
network based volume. See also Server.
Data rate
1 In data transfer, the amount of information
moved from one point to another over a span of
time.
2 Modems and other asynchronous devices
use the data rate to specify the maximum amount
of information that can be reliably transferred.
In RemoteWare, the box that appears when an
item has more information available. The detail
window may appear after double-clicking the
item or selecting a button or menu item.
Device (network or asynchronous)
Any hardware, such as a modem or network
interface card, that allows access to a general
network.
Dial script
One or more instructions used by the Client or
Server to access and connect through a modem
or network.
Dial Script Editor
A Server and Client program used to construct
and compile dial scripts.
Glossar y
343
Dial string
Disable
A sequence of characters from the Client or
Server to the modem requesting that the modem
place a call. This is often called Modem Dial.
See also AT commands.
A state in which the item cannot be used in an
active system. An item or feature may be
disabled by design, by operator choice, or
because the item is not properly configured.
Direct assignment
Distribution list
The condition or operation of associating a
Client, session, object, or group to another item
in this list by using the Assign command. See
also Indirect assignment.
In RemoteWare Messaging Services, refers to an
option available for user groups. A distribution
list consists of a user group that is available to
RemoteWare Extended Client users. Users may
select one or more distribution lists to simplify
message sending. See also User group.
Direct Connect (cable)
1 The situation in which a Client is attached
to a Server using a null modem serial cable.
2 A null modem serial connector that attaches
to the serial ports of the Client and the Server.
See also Null modem.
3 In RemoteWare, a special modem type
available at the Server Profile Resources page
and the Client Profile Client page. Unlike other
modem definitions, the Server does not dial or
connect when this option is selected.
Directory
1 Part of the structure for organizing files on a
disk. A directory can contain files or other
directories (called subdirectories).
2 The list of local and remote users accessible
from the Directory Manager program. This is
also called the Directory subsystem or the User
Directory.
Directory scan
Domain groups
Two or more Windows NT computers that share
a common domain database and security policy.
Down (Server)
A Server state indicating that a portion of the
Server is not functioning. This may result from a
Server that is still starting up or one that is
experiencing problems. Network Status,
Administrator, and Server Profile display the
status of all Servers on the network. Use the
Server Message Log in Log Viewer to determine
the cause of the downed Server.
During event
A task that is set up to execute only when the
Server is connected to the Client. Many events
can be set up as during events, but file transfer
events and messaging events require a
connection and therefore must be defined as
during. See also After event.
In Inventory Manager, a type of scan that collects
information on the directory and file structure of
all local hard drives of any 32-bit Windows
Client.
E
Directory Manager
See also External Configuration File (ECF).
A RemoteWare Server program that appears
when RemoteWare Messaging Services has been
installed. Creates, manages, and assigns
RemoteWare users to user groups and Clients.
Editor
Directory synchronization
The procedure used to reconcile differences
between two or more lists of users. RemoteWare
can perform automatic synchronization between
a RemoteWare user directory and a Microsoft
Exchange user directory.
ECF
Any program that allows you to manipulate data
in a file. Some examples in RemoteWare are the
Dial Script Editor, Subscriber Editor, and the
Workshop Editor.
ECF Server
A process that runs on the Server and processes
ECF data files placed in a watched directory. By
default, the watched directory is \ecf on the data
drive.
344
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Electronic Software Distribution
Commonly called ESD. The ability to check and
conditionally update Client files using a master
copy at the Server. System and User ESD objects
automatically update files if the existence, date,
time, or size differ from the Server’s file.
Enable
An option, resource, or item that is functioning,
implemented, or ready for use.
Encryption
A method for disguising information so that only
authorized recipients can use the information.
Passwords and messages are encrypted to
prevent their use by unauthorized parties.
Environment variable
A symbol defined in the System Environment
Variables section of the System control panel.
The variable may be used in a RemoteWare
event by referencing it as <$variable name>.
Environment variables cannot be set from
RemoteWare and retain the same value across all
events and objects.
scheduled session is independent of any other
session appearing with the same name and does
not affect the scheduling or rescheduling of
other sessions.
Execution drive
The drive letter or network volume containing
active files of the \system directory. Servers
generally possess their own separate execution
drives, which is usually the local hard drive.
Execution Server
A program at the Server that processes the
NOTIFY and EXECUTE events that can be in a
Work Object Editor work object, Worklist Editor
worklist, or command from the Interactive
Session program.
Execution type
See Electronic Software Distribution.
A work object attribute that determines if the
object executes based on choices from the
Client. The object can be set to always execute
(see Forced execution), execute only if the
Client enables the object (see Requestable
execution), or execute unless the Client disables
the object (see Default execution).
Events
Execution window
ESD
In the Work Object Editor or Worklist Editor,
the smallest unit of work in a work object or
worklist. Events perform file transfer, system
commands, conditional execution flow, and other
functions.
Exception worklist
A collection of events in an external file that is
referenced by an EXCEPTION worklist event in
a work object. This worklist executes only after a
Failed-Final session and can be used to run
recovery or salvage tasks.
Execute
1 Begin an operation or instruct a program to
start processing data, events, or commands.
2 In the Work Object Editor or Worklist
Editor, an event that can be used to start a Server
or Client program.
Execute now
In the Schedule Manager, a menu command that
begins a session immediately. This type of
From the Session Editor Schedule page, a
timespan formed by the combination of the Start
Session time, Stop trying outbound calls after n
hour(s) value, and Do this session early if a
Client calls within n hour(s) before scheduled
outbound start time. A session that does not
execute in its execution window generates an
OUT OF RANGE message in the Session Log.
Export
Copy data to an external file. The file may be a
text file or data that can be referenced or
imported by another program. Work Object
Editor, Worklist Editor, Workshop, and
Subscriber Editor provide an export option.
External Configuration File (ECF)
A text file containing specially formatted
instructions. The ECF is used to create, modify,
and delete settings, resources, and other items
on the Server. See also ECF Server.
Glossar y
F
345
Forced item
The status of a scheduled session indicating that
the session has failed in the past but still has
unused retries available. This session cannot be
restarted until it exhausts all its retries and
becomes a Failed-Final session.
In Subscriber, an item type. When a forced item
is included in a Subscriber List and that list is
distributed, the RemoteWare Server sends the
Subscriber List and the forced item to the
Clients. During any subsequent connections, if
the item has been altered or does not exist at the
Client, the Server sends it again.
Failed - Final
Full cleanup
A scheduled session where all attempts
(including retries) failed to contact the Client.
In Log Viewer, a log that records every file
exchange between the Server and the Client.
In Software Manager, one of two types of
cleanup processes that remove unwanted or
unneeded installation files that come from localbased installations from the Client’s system. A
full cleanup removes all the files associated with
a package from the Client’s system. A full
cleanup is typically performed when a user has
received a package and no longer wants it or
when attempts to install the package were
unsuccessful. See also Cleanup; Non-Setup
based installation.
Filter
Fully qualified name
A feature or operation that displays a subset of
items based on a common attribute. Filters are
available in Session Recovery, Log Viewer, and
Inventory Manager (Custom Views).
The drive letter, path name, and file name for a
file. An example would be
D:\DIR00\SUBDIR\FILE.TXT. See also Path
name; Universal Naming Convention (UNC).
Failed - All
Fault tolerance
A feature of Clustered Servers that automatically
detects a downed Server, recovers interrupted
sessions, and reschedules those sessions.
File Transfer Log
Fixed session
In the Session Editor, an option that causes a
session to execute at a specific interval.
Administrators define the fixed timespan in time
(minutes and hours), days, or every number of
weeks on indicated days. See also Calendar
session; Dependent session.
G
Gateway
In messaging, a component that allows
information from one messaging system to be
automatically transferred to and delivered within
another messaging system.
Flow control
Gateway Manager
A modem protocol that starts or stops
information transfer based on the destination’s
ability to receive the information. Flow control is
set from the Edit Modem dialog box.
A function of the Messaging Administration
program on the RemoteWare Server. Provides
the transfer of messages between RemoteWare
Messaging Services and a Microsoft Exchange
network.
Force delivery
In Software Manager, a method of installation
that installs a software package at the Client
silently with no input from the Client user. See
also Autosubscribe.
Gateway user
Forced execution
A set of Server programs that execute from the
command line and create text (ECF) files
containing instructions for recreating portions of
the Server’s configuration.
In the Work Object Editor, an object that always
executes when it is assigned to a Client. Forced
objects cannot be disabled by the Client user.
A local or remote user that has been allowed to
use the messaging gateway.
GEN utilities
346
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Group
Indirect address
A collection of similar items (such as Clients,
applications, or work objects) that can be
assigned, manipulated, or changed as a unit.
1 In RemoteWare, a variable used to
represent a location or value that may change
frequently, such as a network address.
2 A variable name substituted for an actual
network address.
Group Name
In Server Profile, this is the name you assign to
the Port Group.
Guidance file
In Software Manager, a text file included in a
software package that contains information to
assist the Client user with the installation
process. The Client user can view a notes file
before or during the installation. Notes files are
only available for Setup based packages. Also
called a Notes file.
H
High priority
In RemoteWare Messaging, a ranking given to a
message which determines how it will be
processed and how it is displayed at the Client.
See also Low priority; Normal priority; Real
time priority.
I
Inbound
In RemoteWare, indicates the initiation and
direction of establishing a connection, beginning
at the Client and attempting to contact the
Server.
Inbound only
1 A Server that only accepts connections from
Clients, but cannot initiate any outbound
connections.
2 A session that executes only when assigned
Clients connect with the Server. One inbound
session can be assigned to a Client.
Incoming queue
RemoteWare Messaging Services uses the
incoming queue to store messages arriving from
the remote computer. On the Client, these
messages are processed and passed to the MAPI
message store. On the Server, the messages are
processed by the Message Transfer Agent (MTA)
and placed in each recipient’s outgoing queue.
Indirect assignment
An association with an item (such as a Client,
object, or session) which incidentally occurs
because it belongs to a directly assigned item.
Indirect file
A file that contains a fully qualified file name and
is referenced by a RemoteWare application. This
option may be used to dynamically change or
choose different files based on a session
condition or a program that modifies the
contents of the indirect file.
InstallShield
The program a RemoteWare Server installation
uses to create a RemoteWare system.
Integrated Services Digital Network
(ISDN)
Internationally developed telecommunications
system for sending signals in digital format along
optical fibers and coaxial cable. The system
converts the link between the user’s telephone
(or private branch exchange) and the digital
telephone exchange from an analog to a digital
system, increasing the amount of information
that can be carried.
Interactive Session
A Server program that allows the administrator
to access Clients through a menu and character
based user interface.
Inventory Manager
The RemoteWare application that automatically
scans and retrieves detailed inventory data—
such as processor type, amount of memory,
operating system installed, and commercial
software package usage—on remote systems.
Inventory Profile
In Inventory Manager, the execution schedule
and set of options that control the distribution
and execution of inventory scanning software.
Administrators assign Clients or Client Groups
to one or more Inventory Profiles when he or she
Glossar y
347
wants to gather inventory information from
them.
based or Server-linked Editors, all Published
Lists.
Inventory View
Listen
In Inventory Manager, the display of inventory
scanning results based on a number of
predefined resource categories. See also Client
View; Custom Field; Custom View.
For a communication resource, the state in
which no connection exists and the Server or
Client software is ready to accept a connection.
On the Server, Network Status displays LISTEN
for available resources.
ISDN
See Integrated Services Digital Network
(ISDN).
Item detail
An option that provides more information about
a selected item. Item detail is available in most
RemoteWare logs.
K
kB
See Kilobyte (kB).
Kilobyte (kB)
A unit of computer storage and memory
measurement that equals 1024 bytes. One byte is
typically the smallest accessible unit in a file or
data transfer.
L
License log
In the Server Profile program, a window
available from the Licensing page that displays
every change to the number of permitted
resources.
Licensing
1 A property page in the Server Profile
program that displays current maximum values
of resources, and provides access to the License
Log.
2 The act of modifying the number of allowed
ports, Clients, Servers, Workstations, and so on.
This can be performed from a licensing file or an
update code created specifically for this Server.
List Library
The tree control in the left pane of the
Subscriber Editor window. The List Library
provides access to Working Lists and, for Server-
Literal string
One or more characters that are specifically
marked so that they remain unchanged by the
software or operating system. In RemoteWare,
literal strings may either be enclosed in double
quotes “ ” as with nonstandard file names, or
preceded with a backslash “\” in dial scripts.
Load balancing
A feature on Clustered Servers that evenly
distributes active scheduled sessions across all
available Servers. Imbalances may occur if a
resource problem develops on a Server, or if one
or more Server clocks drift out of
synchronization. Use the net time NT command
to align system clocks.
Local Area Network
Computers connected in a geographically close
network, such as in the same building or campus.
Local Server Name
The computer name for a single RemoteWare
Server. This value is set from the Networks
Control Panel and is updated each time the
Server is restarted.
Local user
A user that is based on the RemoteWare Server,
can be assigned to an Extended Client, and
transfer RemoteWare data. With a gateway, local
users can also exchange information with remote
users. See also User.
Log
Any program or file that records the occurrence
of a change with another program or system. On
the Server, the License Log, File Transfer Log,
Server Message Log, Session History Log,
Inventory Manager Log, and Messaging Log
may be available; the Client has a
Communications Log.
348
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Log Viewer
MAPI spooler
A RemoteWare program used to monitor current
or past system activity. Provides one interface for
viewing multiple Server, messaging, and
Inventory Manager logs that are stored in an
external SQL database.
A program or process that accepts messaging
information and delegates it to a service provider
that is capable of delivering the message.
Long distance
For phone or asynchronous communication
resources, a term that infers the addition of an
area code, country code, or call accounting
information to the base phone number.
Long Distance Services
From the Server Profile, the ability to define and
use a prefix, suffix, or dial script in addition to
the Client’s phone number or network address.
This facility is available from the Server Profile’s
Long Distance page.
Low priority
RemoteWare Messaging Services assigns
rankings to messages to determine when to
process the message and how to place it in the
Client’s message list. Low priority messages
usually appear last in the message list, and may
be processed after Normal, High, and Real Time
priority messages.
M
Maintain Dial Connection
From the Server Profile’s Settings page, a
system-wide setting that prevents a connection
from being terminated if another session is
waiting to connect with that Client.
Makekit
The set of files produced in the Client Profile
program when you perform a Make Installation
Kit operation. A Makekit is used to create and
install a Client.
Make-Kit Wizard
In Client Profile, a series of windows that assist
with the creation of a Client makekit. Appears
when you select Make Installation Kit from the
Command menu.
MAPI
See Messaging Application Programming
Interface (MAPI).
Master worklist
A constantly changing RemoteWare internal file
residing in memory that contains the current set
of events in an active session. The master
worklist changes during an active session when
conditional events occur, user variables are
resolved, and events return a status value that
causes a change in execution.
Matching resource
One or more communication resources from the
Server Profile Resources page that can be used
by a scheduled session to connect with a Client.
In Schedule Manager, the General page of the
Details for Session window lists available
matching resources. The session remains
blocked until a matching resource is available or
created.
MB
See Megabyte (MB).
Megabyte (MB)
A unit of computer memory and storage that
equals 1,048,576 bytes.
Members
1 A property page in the Client Profile and
Work Object Editor programs. In general, the
pages list which items belong to the group. In
Client Profile, the page occurs for Client groups
and lists member Clients and groups. In the
Work Object Editor, the page lists the objects
that are part of an application or application
group work object.
2 In RemoteWare Messaging Services,
indicates which users are included in a user
group or distribution list.
Memory
In computers, a circuit that can rapidly store and
recall information for processing. Large amounts
of memory are often required for normal
operation of advanced operating environments
like RemoteWare; more memory tends to result
in faster and larger computational capacity.
Glossar y
Message
A structure or set of parameters used for
communicating information or a request.
Messages are passed by RemoteWare Messaging
Services from a user to the Server (for a request),
or to other users (to pass information).
Message queue
A storage location for messages in transit.
RemoteWare Messaging Services uses an
incoming and outgoing queue for messages and
attachments.
Message store
In RemoteWare Messaging Services and MAPI,
a staging area used by MAPI to hold and deliver
messages to one or more recipients.
Message Transfer Agent (MTA)
A RemoteWare Server program that receives,
processes, and delivers messages to each user’s
outgoing queue. This program is not directly
accessible to an administrator, but can be
controlled from the Messaging Administration
program.
Messaging (Services)
RemoteWare provides a complete set of
RemoteWare Server and Client programs, APIs,
and ECFs for the configuration and
administration of messages between users and
the Server.
Messaging Administration
A RemoteWare Server program used to control
the Message Transfer Agent and MAPI settings
and to schedule processing of non-delivery
reports and directory synchronization for users.
Messaging-aware
A process, program, or application that has the
capability to recognize (and presumably use)
messaging services, allowing the user to
exchange information between two or more
computers.
Messaging Log
In Log Viewer, a log that records the passage of
each message processed by the Message Transfer
Agent. Use the Messaging Log to determine
which messages are not being delivered, identify
trends in processing performance, and view the
volume of messages during a time period.
349
Messaging Application Programming
Interface (MAPI)
An open application programming interface
implemented by Microsoft that provides
resources used by developers to access
messaging services, resulting in compatibility
between messaging-enabled applications and
messaging systems. RemoteWare conforms to
MAPI 1.0 standards.
Monitored session
A session referenced by a dependent session to
determine when the dependent session should
execute.
MTA
See Message Transfer Agent (MTA).
Multicast
RemoteWare Multicast extends traditional pointto-point transmission by transferring outbound
data simultaneously to multiple sites.
RemoteWare Multicast enables one-to-many
data transfer, sending one copy of each packet to
an entire group of remote locations. The network
then forwards the packets to only the
destinations identified to receive them, reducing
network congestion and strains on server
resources.
N
Named pipe
An interprocess mechanism on the Server that
allows an application to communicate small
amounts of data with another local or remote
process.
NDR
See Non-delivery report (NDR).
NetBIOS
Network Basic Input Output System - a
communications resource available to network
based Servers and Clients. NetBIOS
communications hide the networking details and
addressing from the applications or users.
NetUser
The short RemoteWare label for a user. This
term is from 1 to 8 characters in length. Clients
350
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
usually see the user’s full name and not the
NetUser label when referencing another user.
Network Group
In Server Profile and Client Profile, a collection
of Clients that can be associated with Port
Groups to manage port use by various types of
resources. You create Network Groups on the
Network Groups page in Server Profile. You
assign individual Clients to Network Groups on
the Client Profile Server page.
Network Status
A Server program that monitors Server
resources, Server conditions, and current Server
activity.
No execute
The status of a work object or event that
indicates the item was not processed. Several
issues cause this status, including an upstream
item that caused execution to terminate, a
deactivated work object, and a conditional
statement or block that was not executed.
unneeded installation files that come from localbased installations from the Client’s system.
When a Client user receives a local-based
package from the Server, its contents are placed
in a temporary staging area until it is installed. A
normal cleanup removed temporary files from
the staging area. See also Cleanup; Full
cleanup.
Normal priority
A ranking assigned to a message that determines
how it is processed and how it appears in a
message list. Messages are assigned a normal
priority by default. See also High priority;
Low priority; Real time priority.
Not executed
See No execute.
Null modem cable
A serial asynchronous connector constructed to
reverse the transmit and receive wires and allow
two computers to connect asynchronously
without modems or a phone line. This cable is
Node
The name for a Client in RemoteWare for OS/2.
See also Client.
Node Profile
The name for the Client Profile Server program
in RemoteWare for OS/2. See also Client
Profile.
Non-delivery report (NDR)
A message generated by RemoteWare
Messaging Services (specifically, the Message
Transfer Agent) and sent to the message
originator. Indicates that the message did not
arrive at one or more of its recipients. NDR
processing is controlled from the Messaging
Administration program on the Server.
Non-Setup based installation
In Software Manager, a type of installation used
for applications that have no installation program
and are distributed as a custom application or a
collection of files. See also Setup based
installation.
Normal cleanup
In Software Manager, one of two types of
cleanup processes that remove unwanted or
used when communicating with a direct connect
Client.
O
Object
The abbreviated term for “work object.” An item
containing specific tasks to be performed by a
RemoteWare Server. The Work Object Editor
program manages five (5) types of objects
depending on the tasks to be performed.
Object Linking and Embedding (OLE)
A set of object-based programming standards,
developed by Microsoft and incorporated into
Windows. OLE enables development of reusable
and shared software components, so that objects
can communicate with each other. RemoteWare
conforms to version 2.0 standards of Object
Linking and Embedding.
ODBC
See Open Database Connectivity (ODBC).
OLE
See Object Linking and Embedding (OLE).
351
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Open Database Connectivity (ODBC)
Packet size
An interface and set of programming standards
that allows different systems to access database
data. ODBC provides a vendor-neutral way of
accessing data from any ODBC-compliant
database. RemoteWare uses ODBC to access
messaging-related data on the Client and the
Server.
The number of bytes in a packet. RemoteWare
supports sizes from 128 to 16,384 bytes. The line
conditions, equipment, and other factors
determine the maximum effective packet size.
Originating (Client, user, address)
In RemoteWare Messaging Services, the source
for messaging-based information. The terms
above progress from most general to most
specific; that is, an address is unique for a given
messaging system, a user may have several
addresses, and a Client may have several users
(and several addresses).
Outbound
In RemoteWare, indicates that the Server
initiated and established a connection with a
Client. The Server is always used as the starting
point when determining whether a session is
inbound or outbound.
Outgoing queue
RemoteWare Messaging Services uses the
outgoing queue to store messages destined for
the remote computer. On the Client, these
messages are sent to the Server during a
communication session. On the Server, the
Message Transfer Agent processes messages and
places them in the outbound queue for each
recipient.
P
Package
In Software Manager, a set of files that install
software on a Client computer. The information
contained in the package’s files defines how,
when, and where the software is to be installed at
the Client.
Parents
In the Client Profile and Work Object Editor
programs, a property page that lists the groups
that include the current item as a member.
Partial success
In RemoteWare Messaging Services, and
specifically in the Messaging Log, a partial
success indicates that a message was delivered
successfully to at least one recipient, but at least
one recipient did not receive the message. The
Server Administrator can use the Messaging Log
detail to determine which recipient did not
receive the message, and the Client user receives
a non-delivery report (NDR) for the recipients
not contacted.
Password
A set of characters that must be provided to an
application before access is permitted. Server
administrators must provide a user account and
password; Client software provides a password as
part of the connection procedure.
Path name
Specifies the location of a file within the
directory tree. For example, the path of the
README.WRI file in the SYSFILES directory
on the E drive would be
E:\SYSFILES\README.WRI. See also Fully
qualified name; Universal Naming
Convention (UNC).
Pause
A command available in the Dial String Editor
and dial strings at the Server and Client. Pause
waits the specified number of seconds before
continuing to the next command.
PBX
See Private Branch Exchange (PBX).
Packet
Pending
A unit of information transmitted as a whole
from one device to another on a network.
RemoteWare transmits packets that can be
configured from 120 to 16,384 bytes.
In Schedule Manager, a scheduled session state
that indicates a future execution time. The Start
Time value displays when the session moves out
of the pending state.
352
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
PID
Primary resource
See Process identification (PID).
See Named pipe.
The connection method first used to establish a
connection. If the connection fails, a Server has
the option to switch to an alternate resource on a
specific retry attempt.
Port
Primary Server
Pipe
1 A connection or socket for attaching a
device, such as a modem, to the computer.
Information is sent from the computer to the
device through a cable.
2 In RemoteWare, the access method for
asynchronous communication resources.
Port Group
In Server Profile, a collection of NetBIOS, SPX,
or TCP/IP resources used in conjunction with
Network Groups to manage port usage by
certain resource types. A Port Group specifies
the number and priority of ports for outbound
communications sessions.
Port number
The label a computer or software uses for a port.
Serial port numbers are typically represented as
COMn, where the n is a number from 1 to 36 on
the Server, and 1 to 4 on Windows 3.x Clients.
Post-ESD event
For an ESD work object, a task that executes
immediately after the ESD list has finished
processing. These events are located on the
Work Object Editor Events page when the PostESD events radio button is active.
Predefined variables
A set of placeholders provided with the
RemoteWare software, such as <time> and
<ServerData>. The placeholders are resolved
with actual values when the session or work
object executes. Predefined variables are always
available in work objects.
Pre-ESD event
For an ESD work object, a task that executes
prior to ESD list processing. These events are
located on the Work Object Editor Events page
when the Pre-ESD events radio button is active.
Pre-ESD is often used to set up directory
structure or to examine a Client’s current state.
Refers to the RemoteWare Server that created
the Client’s Makekit. The Primary Server grants
rights for secondary Servers to access this Client
from Other Server Serial Numbers field on the
Client Profile General page. Primary Servers
maintain the secondary Server list and are
responsible for maintaining the Client’s system
ESD.
Priority
1 The ability for a session or object to be
processed first in time when other items are
competing for the same resources.
2 For a resource, the ability to specify a
minimum session priority reserved for an
asynchronous resource. This is set from the
Server Profile Resources page.
3 In RemoteWare Messaging Services, a
ranking assigned by the user to a message that
determines its method of processing, its order in
a message list, and, in some instances, its
eligibility for transfer (for example, when a user
requests high priority messages only). The
choices are low, normal, high, and real time
priority.
Private Branch Exchange (PBX)
Phone equipment that manages the phone
system for an office or group, independent of the
public phone network. Some PBXs interfere
with asynchronous data communications or may
require a prefix to reach an outside line.
Process identification (PID)
A unique number assigned to processes on a
Windows NT system. These numbers change
when the system reboots. Server Message Log
records PIDs.
Process Only
In Session Editor, a session type that does not
use a communication resource and runs only on
the Server. Process Only sessions contain events
that are all marked as Before and On Server
events. These session are used to complete tasks
353
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
on the Server without waiting for or occupying a
communication resource.
deletes all of the archived version of any files in
the list.
Protocol
Pull Application
1 A set of rules and conventions by which two
or more computers pass messages across a
network.
2 A Server Profile property page that contains
defined settings for connection resources.
Settings can vary by compression, window size,
packet size, session timeout, and retransmit
timeout.
In Workshop, to cease distribution of a particular
Workshop application, use the Pull Application
function. Pulling removes the Workshop
application file and any related files from the
CRS\Workshop\Publish directory and deletes all
of the associated work objects on the
RemoteWare Server.
Publish
In Session Editor, the ability to remove dates
(from calendar-based and fixed session
schedules) that have already passed.
In Subscriber, to make a Working List or a
working version of a Published List available to
the RemoteWare Server. Published Lists can
then be hosted by an application, such as a form
in an application created by RemoteWare
Workshop.
Publish Application
In Workshop, to make an application available to
the RemoteWare Server for distribution to
Client users. Publishing an application copies an
application file and the related files to the
CRS\Workshop\Publish directory. It also creates
the RemoteWare work objects associated with
the published Workshop application.
Published List
In Subscriber, a Working List that has been
published and resides in the Published Lists
folder. A working version of the Published List
also exists in the Working Lists folder,
represented by a list icon with red lines.
Purge dates
Q
Queue
In RemoteWare, a communications mechanism
used by the NOTIFY and EXECUTE events to
pass information to another process on the same
computer. See also Named pipe.
Quota
The maximum length of time and/or number of
bytes allotted to a set of file transfer events in a
session. Two events create a quota block: begin
QUOTA block and END QUOTA. Once the
quota has been exceeded, RemoteWare stops
processing the file transfer events in the block
and begins processing the next session event
after the block.
R
Published Lists folder
RAM (Random access memory)
In Subscriber, a folder within the List Library
that contains all Published Lists. On a Standalone Editor, the Published Lists folder will
always be empty.
See Memory.
Published package
In Software Manager, a package that has been
made available to Clients. See also
Unpublished package.
Pull
In Subscriber, to make a Published List
unavailable to the RemoteWare Server, usually
because the list is obsolete. Pulling a list also
Real time priority
In RemoteWare Messaging Services, indicates
the highest ranking for a message. These
messages are immediately transferred during the
next connection. Messaging based applications
such as RemoteWare Subscriber use real time
priority to transmit a request and receive a
prompt reply.
REG file
In Software Manager, a registry file containing
the registry key additions or modifications
354
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
necessary to fully install and register an
application at the Client. When a .REG file is
included in a software package, the information
is imported by default to the Client computer’s
registry.
Registration
RemoteWare Messaging Services
A technology that allows RemoteWare to transfer
messages and information between RemoteWare
users, programs (such as Subscriber and
Microsoft Exchange), and other networks (such
as the Internet).
In Client Profile, the process used to validate
new Clients.
RemoteWare Server
Registry
RemoteWare Subscriber
In Windows 95/98/Me, and Window NT/ 2000/
XP a database repository for information about a
computer’s configuration. RemoteWare uses the
Registry to identify the RemoteWare Server
Service and provide other identification.
See Subscriber.
Release date
A Server program that generates and displays
reports on all Server activities and
configurations.
The date the RemoteWare Server software was
created by the manufacturer. Different release
dates can indicate the level of revisions in the
system.
Release notes
A document that provides additional information
about the RemoteWare programs.
Remote Control
A feature in RemoteWare that allows the Server
administrator to display and manipulate a
Windows user environment on a 32-bit
Windows-based RemoteWare Client. Remote
Control is available from the Interactive Session
program.
Remote Console
A feature in RemoteWare that allows the Server
administrator to remotely control RemoteWare
OS/2 and DOS Clients. Remote Console is
available from the Interactive Session program if
the Remote Console Feature Pack has been
installed.
See Server.
RemoteWare Workshop
See Workshop.
Report Manager
Requestable execution
In the Work Object Editor, an execution type on
the General Attributes page that executes the
object only if the Client requests it explicitly. By
default, requestable objects are not executed and
never execute for outbound sessions.
Reserved characters
Many of the non-alphabetic and non-numeric
characters which have special meaning for the
operating system or RemoteWare. Examples are
“< >” for variables or “ ! ” for the carriage return
in dial strings and modem strings.
Reset security
In Client Profile, the act of suspending security
for one or more Clients during the next
connection. Once connected, the Client and
Server reestablish the security tokens.
Resource
In RemoteWare Messaging Services, a user
name and address that represents a destination
external to the RemoteWare network.
A general term for any part of a computer that
can be allotted to a program or process while it is
running. In RemoteWare, resources typically
refer to the asynchronous and other
communications resources available for sessions
and connections.
RemoteWare Developer’s Kit
Restart session
A RemoteWare product that includes
RemoteWare Workshop and RemoteWare
Subscriber.
The ability in the Session Recovery program to
reschedule a session with a status of Missing or
Failed-Final.
Remote user
355
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Result code
Scheduler
Information returned from a modem that is used
by RemoteWare to decide on the next action.
A process of the Schedule Manager that
manages the pending, blocked, suspended, and
active sessions on a RemoteWare system.
Resume
In Schedule Manager, the ability to restart a
suspended scheduler.
Retention count
In Subscriber, the number of files archived at the
Client or Subscriber Editor. For the Server and
Client Retention Count fields, refers to the
maximum number of archived versions for this
particular file.
Retries
An attribute in a session that allows a failed
connection to try to connect again up to a set
number of attempts. The Server may also
attempt to use an alternate resource after a
defined number of retries.
Return code
Information returned from the operating system
and placed in the appropriate log.
Rights
In Administrator, refers to the access privileges
granted to a user for each RemoteWare program
and task for that application.
Running
A Server state that indicates normal functioning.
RWS code
A standardized numeric code that is issued for
most informational, alert, and error messages.
These codes appear in the logs.
S
S7 register
For a modem, sets the number of seconds the
modem waits for a carrier.
S8 register
Sets the duration, in seconds, of the pause “,”
dial command option.
Schedule Manager
A RemoteWare Server program that lists
pending scheduled sessions and sessions in
progress, and enables the Server administrator to
start and stop scheduled sessions.
Script Editor
In Workshop, this is used to create and edit
script subroutines for forms or controls. Each
script is tied to a specific event for a particular
control or form object.
Search/Select field
A window control that appears when list boxes
may contain large amounts of items. Typing the
first few characters of the item and pressing
[Enter] displays the first occurrence matching
the input. Using wildcards can select matching
items, and using the exclamation mark “ ! ” as the
first character deselects matching items.
Secondary Server
A Server that is permitted to communicate with
a Client owned by another (Primary) Server.
Secondary Servers can perform any task except
System ESD on the Client.
Security
A method used to protect a system from
unauthorized use. The Server uses accounts and
passwords, and a Client uses a multistage
security protocol to connect with a Server. The
Administrator program is used to define Server
rights, while the Client Profile program is used
to specify Client passwords.
Security token
One portion of the security protocol between a
Client and the Server. The token cannot be
displayed or changed, but it can be reset from
the Server using the Reset Security option in
Client Profile.
Segmented delivery
The breaking of large files (such as software
packages) into smaller pieces called segments.
The segments are sent to the Client over the
course of several communications sessions. Once
all segments have been transferred to the Client,
RemoteWare reassembles them. Segmented
delivery can be used to control the length of
communications sessions.
356
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Serial number
A numeric label assigned to all Servers or
Clustered Servers in a system. This number is
part of the security protocol for Clients, and is
used for licensing.
Serialize
For the ECF Server, an option that guarantees
processes will not try to simultaneously access
the same application or data, which would result
in an error.
Server
1 When capitalized, refers to the
RemoteWare Server. The RemoteWare Server
provides centralized data administration and
powerful communications capabilities to vast
numbers of remote computers.
2 When not capitalized, refers to a computer
that provides specialized resources or services to
other network computers.
Server Message Log
In Log Viewer, a log that lists all changes, issues,
or errors relating to the RemoteWare Server
system. Server Profile
Server-based Editor
Subscriber Editor installed on the RemoteWare
Server. Server-based Editors have Publish, Pull,
and Archive capabilities.
Server-linked Editor
Subscriber Editor installed on a computer other
than the RemoteWare Server, but linked (via a
network) to the RemoteWare Server. Serverlinked Editors have Publish, Pull, and Archive
capabilities.
Service
1 In RemoteWare, the Windows NT/2000/XP
Service that enables the Server to operate
without a system administrator having to log and
start the program on the Server.
2 In Windows NT/2000/XP, a process that
performs a specific system function and provides
an Application Programming Interface (API) for
other processes to call.
Session
A collection of work objects and a schedule
destined to some Clients. Sessions are managed
in the Session Editor, and scheduled sessions
appear in the Schedule Manager.
Session Editor
A Server program that creates sessions for
scheduling. Session Editor allows sessions to use
work objects, provide a schedule for execution,
and define assigned Clients.
Session History Log
In Log Viewer, a log that records all connection
activity from the Schedule Manager, Interactive
Session, and inbound Client connections.
Session Recovery
A RemoteWare program used to identify,
recover, and resubmit sessions that failed to run.
Setup based installation
In Software Manager, a type of installation used
for applications that provide their own
installation program to perform file copy and
system update operation (for example, Setup.exe
or Install.exe). A Setup program is usually
provided with commercial software. See also
Non-Setup based installation.
Signature file
See Virus signature file.
16-bit Client
The RemoteWare software that allows any
Windows 3.x computer to communicate with a
RemoteWare Server. 16-bit Clients can also be
installed on Windows NT or Windows 95
computers, but the 32-bit Client is optimized for
these systems. See also Client; 32-bit Client.
Skip
In the Schedule Manager, a command that
makes a pending session skip the current start
time and reschedule for the next start time.
Software Catalog
In Inventory Manager, the list of software
referenced by Inventory Manager during
software scans of RemoteWare Clients.
Inventory Manager can detect and report
software that is defined in this catalog.
Administrators can customize the Software
Catalog to track or ignore specific applications,
such as internally developed software or
common programs.
357
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Software Catalog Editor
Subscription Only
The Inventory Manager component used to
modify and update the Software Catalog.
In Subscriber, an item type. When a subscription
only item is included in the Subscriber List, and
that list is published and distributed, the
RemoteWare Server sends only the list. The
Client user must subscribe to the item and
connect with the RemoteWare Server to receive
it.
Software Manager
The RemoteWare application that enables
administrators to distribute, install, and manage
software for remote and mobile users.
SPX
Sequenced Packet Exchange - Novell NetWare’s
native communication service, used to provide
reliable communications to Clients and Servers.
SQL Server
A Microsoft retail product that provides
relational database management. RemoteWare
accesses SQL Server through ODBC to store
messaging-related information and some logging
data at the Server.
Standalone Editor
Successful
A session, work object, or event status that
indicates that the item performed its tasks as
expected.
Suspended
A scheduled session is suspended by the Server
administrator in the Schedule Manager before it
is active. The session cannot become active and
remains as is until someone resumes the session.
Synchronization
In Subscriber, a Subscriber Editor installed on a
computer that is not linked to the RemoteWare
Server. Standalone Editors do not have Publish,
Pull, and Archive capabilities. Working Lists
must be exported to the Server or a Serverlinked Editor to use any publish capabilities.
In RemoteWare Messaging Services, the process
of reconciling the contents of the Server and
Client address books. The synchronization
interval may be controlled from the Messaging
Administration program on the Server.
Subscriber
System ESD
A RemoteWare product that allows central
administration and organization of large lists of
files and documents. These files are delivered to
a Client user when requested. Only
RemoteWare Extended Clients can use
RemoteWare Subscriber.
In the Work Object Editor, an ESD work object
that is not a USER owner type. This type of ESD
occurs for RemoteWare Applications and
programs needed by RemoteWare to keep the
Client updated.
Subscriber Editor
The RemoteWare Subscriber component used to
create, change, publish, archive files in, and
otherwise maintain Subscriber Lists.
Subscriber List control
The OLE control supplied by RemoteWare
Subscriber that provides limited Client
functionality to applications created using OLE
control containers.
Subscriber Viewer
The RemoteWare Subscriber component used to
view DigitalPaper (DP) files created by
Common Ground TM, version 1.0 and later.
System name
In RemoteWare, the label given to every Server
in a Cluster. This name comes from the Settings
page in the Server Profile.
T
Target
1 In Work Object Editor, the file or directory
to which a source file is to be transferred,
appended, copied, or renamed during execution
of a work object’s events.
2 In Software Manager, the primary location
on the Client where package files are installed.
358
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
TCP/IP
Uncompiled
Transmission Control Protocol/Internet Protocol
- The primary wide area network protocol used
by Windows NT and UNIX networks.
In the Dial Script Editor and for dial scripts, a
dial script that has not been validated by the Dial
Script Editor. Uncompiled dial scripts have an
asterisk “ * ” to the right of the Last Compiled
date.
Template Client
In RemoteWare, a Client type defined in the
Client Profile during the Make Installation Kit
process that permits large numbers of Clients
with the same configuration to be created and
installed. The Makekit disk(s) from a template
Client can be mass produced and distributed to
potential Client computers for installation.
Filenames or other resource names that begin
with double backslash “\\”, indicating whether
they exist on a remote computer. An example
would be \\THING2\C drive\directory\file
name.txt.
Test Application
Universal Time Coordinate (UTC)
In Workshop, this function builds the application
and runs it on your system.
32-bit Client
The RemoteWare software allows any Windows
95/98/Me and Windows NT/2000/XP computer
to communicate with the RemoteWare Server.
See also Client.
Universal Naming Convention (UNC)
The list of geographical time divisions and
example countries used by RemoteWare to set
the time zone for Clients. The Server’s time zone
is set from the Date/Time Control Panel or the
net time command (preferred for Clusters).
Unpublished package
A numeric value or cutoff point where exceeding
this value triggers an action. The Server Profile
Alarms page contains thresholds that issue a
Server Message Log entry or deactivate a port.
In Software Manager, a package that is not
available to Clients. Administrators must
unpublish a package or make a working copy of
the package in order to edit its contents. See
also Package; Published package; Working
copy.
Throughput
Update code
The average bits per second transmitted over the
communications resource over the duration of
the connection, or during any specified event.
A series of characters that can be typed into the
Update Licensing window of the Server Profile
Licensing page. The Update code is used in lieu
of a licensing disk or LICENSE.UPD file and is
keyed for the current Server configuration.
Thresholds
Timeout
The ability to stop a task in progress if the
program does not receive an expected response
after a set or reasonable amount of time. Some
examples of timeouts are for connection
resources during establishment and active
sessions that do not receive a timely
acknowledgment.
User
Transport
On RemoteWare, consists of an individual’s or
entity’s name and other information required to
communicate or exchange data with other users.
More than one user can exist at a Client. Users
are available when RemoteWare Messaging
Services are installed at the Server.
A general term for a communications resource.
User defined variables
U
UNC
See Universal Naming Convention (UNC).
A placeholder defined and used in a work object
in the form <%variable-name>. Once defined,
the variable may be used anywhere in the
session, even across work objects. See also
Predefined variables; Environment variable.
359
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
User directory
Virus signature file
In RemoteWare Messaging Services, the list of
RemoteWare users, addresses, and other userrelated information stored in a database. This
information is used to build a Client’s address
book and process messages at the Server. The
user directory is accessible from the Directory
Manager program.
In Inventory Manager, a file created and
distributed by Network Associates, Inc. that is
used to detect a specific virus on Client
computers. Virus signature files should be
updated on a regular basis to ensure that new
viruses can be detected.
User ESD
In the Work Object Editor, any ESD work object
with a USER owner type. User ESD is used by
Server administrators to maintain files related to
the business. See also System ESD.
User group
A collection of RemoteWare users from the user
directory database. A user group may be used to
organize users by functional teams, required
applications, or other related traits. In addition,
user groups may be designated as distribution
lists, allowing RemoteWare Extended Client
users to use the groups to send messages.
User interface
Any method which allows a person to interact
with another system to perform a task. On
Windows computers, RemoteWare uses both the
character-based command line user interface
and the graphical user interface.
W
Wildcard
A character that represents one or more
characters. The question mark “ ? ” can be used
to represent any single character, and the asterisk
“ * ” represents any character or group of
characters that might match that position in
other filenames.
Work object
A collection of events and settings that perform
an action when executed on the Server. Work
objects reside in the Work Object Editor.
Work Object Editor
A Server program used to build and manage
work objects, which contain specific tasks that
are ultimately executed by the Server.
Working copy
V
In Software Manager, a duplicate or an original
package. A working copy of a published package
is used when the administrator wants to modify a
package but the original package cannot be
unpublished for editing or testing. A working
copy icon and a (w) at the end of a package name
indicates that a package is a working copy.
Variable
Worklist
A label or placeholder used in a work object. The
variable is evaluated when the event runs and
passes the result to the event. See also
Environment variable; Predefined variables;
User defined variables.
A sequence of events that reside in an external
file (generally with the .evf extension). The
Worklist Editor program manipulates these files,
and the Work Object Editor can export worklists
or import them to the Events page.
Version number
Worklist Editor
The numerical designation given to a specific
software release. RemoteWare’s version number
is available from any About box, or from the
Server Profile Information page.
A Server program that can create and
manipulate worklist files independently of the
Work Object Editor program or its files.
Convenient for preparing worklists that are
imported by the Work Object Editor, or for
worklists referenced by the Insert Worklist and
Exception Worklist events.
UTC
See Universal Time Coordinate (UTC).
Viewer
See Subscriber Viewer.
360
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Workshop
Workshop consists of two components:
Workshop Editor on the RemoteWare server,
and Workshop Client, which runs on
RemoteWare basic Client. The Workshop Editor
(referred to as “Workshop”) allows you to design
and manage desktop user interface programs,
called Workshop applications, for your
RemoteWare Client users.
Workstation
A Server feature that gives a non-Server
computer the ability to perform most functions
available on the Server. Some functions, such as
shutting down the Server, are not available from
a Workstation.
Index
NUMERICS
32-bit Clients
upgrade 106
4690 Clients
installation FTP 109
installation kit 108
remove members 144
Application objects 127
assign members 143
assign users 150
remove members 144
specify attributes 142
applications
assign 296
A
assign local users 285
active sessions
view 230
apply
filters 217
apply filters
add
Clients 82
local users 280
Work Object Editor 154
assign 146
members Group objects 141
applications 296
Port Groups 66
applications local users 285
protocol services 75
Client group parents 99
remote users 282
Clients 148
resources
Clients sessions 169
asynchronous 59
groups 283
Add Application dialog box 28
members Client groups 98
address books
sessions 147
synchronize 303
user attributes 288
update 304
users 294
Administrator
deny rights groups 30
users applications 150
work objects sessions 167
deny rights users 30
assign work objects 148
disable users 29
assigning
grant rights 29
Remote Control work object to Clients 197
main window 27
Async Resource Detail dialog box 59
set security 27
asynchronous resources
start 27
alarms
add 59
copy 62
Network Status 232
delete 63
set thresholds 41
disable 62
Alarms page 41
Application Attributes page 142
Application Group objects 127
edit 62
attributes
assign 288
assign members 143
edit 288
assign user groups 150
edit users 288
assign users 150
remove 290
362
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
B
Client groups
by Application Group Objects 153
by Application Objects 153
by Disabled Objects 153
by Enabled Objects 153
by ESD Objects 153
by Group Objects 153
by Multicast Objects
filter 153
by Object Owner 153
by Selected Objects 153
by Worklist Objects 153
Byte Level Differencing 132
assign members 98
assign parents 99
define 97
delete 100
edit 100
Client Information dialog box 218
Client list
filter 79
Client List page 78
Client page 85
Client Profile
apply filters 80
Client List page 78
C
Client page 85
Capture command 187
display Clients 78
change
General page 83
Comments page 93
Client settings 83
Information page 92
communications types 40
Make Installation Kit option 103
date and time Clustered Server 35
Members page 97
date and time format 37
Parents page 99
font
remove filters 80
dial scripts 50
fonts 185
refresh interval 176
report definitions 244
Server date and time 34
Server name 33
session execution times 178
save filters 80
Server page 89
Client view
select 187
Client/Session list box 203
search 204
Clients 148
session schedules 173
add 82
system name 32
assign work objects 146
system settings 31
assigning the Remote Control Work object to 197
time zone 35
change general settings 83
Change Description for Group dialog box 100
comments 93
Client
communicate 89
communication settings 85
assign sessions 146
Client definitions 82
copy definitions 95
create installation kits 102
copy 95
define 82
delete 96
delete definitions 96
update 94
disconnect Interactive Session 195
Client details
Session Recovery 218
display list 78
filter 79
Index
install 102
Makekit Wizard 103
remotely control 196
Control Panel
Regional Settings 37
copy
reset security 96
asynchronous resources 62
update definitions 94
Client definitions 95
upgrade 32-bit 106
events 135, 159
view information 92, 231
Log Viewer folders 269
clients
assign sessions 169
Clients page
Session Editor 169
Cluster page
Server Profile 40
Clustered Server
change date and time 35
long distance service 53
modem types 72
protocol services 76
report text 241
sessions 174
user groups 299
users 291
work objects
work objects
change system name 32
copy 155
Starting 22
time zone 35
Copy Modem Type dialog box 72
view activity 239
Copy Report File dialog box 243
Clustered Servers
communications types 40
remove 43
Schedule Manager 179
color
change 185
commands
Copy the selected Session dialog box 174
copying
reports 243
create
folders Log Viewer 267
Group objects 141
Network Groups 56
Client or local machine 187
new views Log Viewer 267
set color 185
sessions 164
Comments page 93
template installation kits 111
communications
user groups 292
inbound 40
compile
dial scripts 49
compression
files 39
conditions
set values 264
configure
MAPI services 316
work objects 128
Create a new Session dialog box 164
Create Folder dialog box 267
Create New Client dialog box 82
Create New Client Group dialog box 97
CSV files 246
generate command line 247
generate sessions 248
customize
Remote Control 196
Interactive Session main window 185
RemoteWare Gateway 311
Log Viewer 266
connections
limit outbound 55
maintain 38
Session Recovery main window 206
cut
Log Viewer folders 269
363
364
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
D
edit dial scripts 48
database assignments
view 301
date and time
change Clustered Server 35
change standalone Server 34
format 37
define
Client groups 97
clients 82
modem types 69
NetBIOS resources 63
Process only resources 65
protocol services 74
SPX resources 66
TCP/IP resources 66
define reports 244, 317
delete
asynchronous resources 63
Client definitions 96
Client groups 100
events 135, 159
Log Viewer folders 269
Log Viewer views 269
long distance services 54
modem types 73
Network Groups 57
protocol services 76
sessions 174
user groups 300
users 291
work objects 155
deleting
reports 243
Detail For Field ’Message (Long)’ dialog box 270
Detailed History For Session window 270
Event Detail fields 274
event flags 273
Expand All Events option 274
Expand Objects option 273
Detailed History For Sessions window 272
view event information 273
Dial Script Editor
create dial scripts 47
dial scripts 46
and long distance services 53
change fonts 50
compile 49
create 47
edit 48
save 49
Dial Scripts page 46
dial strings 52
Directory Manager
add local users 280
add remote users 282
assign applications 296
assign applications users 285
assign groups 283
assign user attributes 288
copy user groups 299
copy users 291
create user groups 292
delete user groups 300
delete users 291
edit user attributes 288
edit user groups 297, 298
filter users 279
main window 278
open 278
remove user attributes 290
remove users 284, 295
update address books 304
Directory Synchronization page 303
disable
asynchronous resources 62
event 138
groups 29
long distance services 53
sessions 173
users 29
work objects 145
Documentation
related publications
electronic xvi
PDF xvi
DOS Clients 192
Index
E
Multicast 127
paste 135, 159
ECFs
locate sessions 202
edit
asynchronous resources 62
dial scripts 48
modem definitions 70
Port Groups 68
user groups 297, 298
search 136
Events page 131
Exchange Administrator
open 310
Execution Server
set up 44
export
event list 139
Edit Attribute dialog box 288
edit Client groups 100
Edit Modem dialog box 70
Command Strings page 70
Result Codes page 71
Settings page 71
enable
event list Worklist Editor 160
export log views 275
Export View dialog box 275
F
Failed sessions 202
event 138
Failed-Final sessions 202
groups 28
Field Values From Log dialog box 264
long distance services 53
fields
sessions 173
filter 263
users 28
remove 256
work objects 145
select 255
Enter Schedule Time dialog box 87
sort 256
Enter Server Phone Number dialog box 86
file format 241
error messages 185
file names
ESD Auto Apply 124, 161
ESD objects 127, 131
event
use long 184
File Transfers
view row details 271
disable 138
File Transfers Log 252
enable 138
files
Event Details dialog box 132, 157
event list
export 139, 160
event lists
import 140, 161
event text
replace 137
search 137
events
copy 135, 159
compress 39
filter 153
by Multicast Objects 153
Objects list 153
sessions Schedule Manager 178
users 279
Filter dialog box 263
Add To List option 264
Select Value option 264
filters
delete 135, 159
apply immediately 178
export list 139
by Client 211
insert 158
by ECF 214
insert work objects 134
by Session 212
365
366
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
by Time Range 213
Client Profile 80
Session Recovery reports 223
Group objects 127
modify 265
add members 141
remove 154, 178, 215
create 141
remove Client Profile 80
remove fields 265
remove objects 142
groups
require selection 178
disable 29
save 154, 178, 216
enable 28
save Client Profile 80
saved Client Profile 81
grant rights 29
Guide
session by Completed 215
session by Failed 215
session by Failed-Final 215
session by Successful 215
Session Recovery 207, 208, 217
session status by Missing 215
set fields 263
set values 264
use saved 154, 178
Work Object Editor 153, 154
folders
copy 269
create Log Viewer 267
cut 269
paste 269
rename 268
rename Log Viewer 268
reorganize Log Viewer 268
Font dialog box 50, 206
fonts
change 185, 186
change dial scripts 50
format
reports 241
summary of chapters in xiv
I
icons
session status 204
Identification Changes dialog box 33
import
event lists 140, 161
inbound registration 120
Information page 92
insert
events 158
install
4690 Clients 108
4690 Clients FTP 109
OS/2 Clients 110
template Clients 111
install Clients 102
installation kits 102
template Clients 111
Interactive Session
change fonts and colors 185
customize main window 185
disconnect Client 195
G
Remote Control 196
Gateway Manager page 314
start Remote Control 198
gateways 309
stop Remote Control 199
select view 184
General Attributes page 129
General property page 83
generate
CSV files 246, 248
CSV files command line 247
reports 240
store output screen 187
Interactive session
use Remote Console 189
Index
L
File Transfers 252
license values
update 237
view 236
Licensing Log 238
Licensing page 236
Limit Outbound page 55
local view, select 187
log
set options Server Profile 42
log details
default 270
view 270
Log Viewer
categories
File Transfers 252
Messages 252
Sessions 252
open 253
Server Messages 253
Session History 253
set view properties 254
long distance
add service 52
and dial scripts 53
copy service 53
delete service 54
dial strings 52
disable 53
enable service 53
update services 54
Long Distance page 51
Long Distance Service Detail dialog box 52
long file names 184
create folders 267
M
create new views 267
Make Installation Kit option 103
customize 266
Makekit Wizard 103
display 252
Client Options dialog box 112
export log 275
Client Registration dialog box 113
fields
Control File dialog box 104, 112
remove 256
Directory dialog box 103, 111
remove filters 265
Template Options dialog box 113, 116
select 255
Template User Options dialog box 113
filter fields 263
filters, set values 264
folders
delete 269
Welcome dialog box 103, 111
manual verification
register Clients 123
MAPI AB tool 317
main window 252
MAPI services 316
modify filters fields 265
members
move folders 269
add Group objects 141
open log views 253
assign Application Group objects 143
rename folders 268
assign Application objects 143
rename views 268
assign Client groups 98
select fields
fields Log viewer 255
set view properties 254
sort fields 256
view row details 270
Logging page 42
logs
remove 144
Members page 97
in Work Object Editor 143
Work Object Editor 141
Menu
RemoteWare 24
Message Store Service 316
367
368
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Messages
view row details 270
Messaging Administration
Address Book Service 317
Gateway Manager page 314
gateways 309
Message Store Service 316
non-delivery receipts 307
open 301
synchronize address books 303
New Modem Type dialog box 69
Non-Delivery Receipt page 307
non-delivery receipts 307
O
Objects list
filter 153
Objects page 167
open
Directory Manager 278
Messaging Administration main window 301
Exchange Administrator 310
modem types
Messaging Administration 301
copy 72
Network Status 226
create definition 69
Report Manager 240
delete 73
Schedule Manager 175
edit 70
rename 72
set Remote Control 197
Modem Types page 69
Multicast
enable 88
events 127
Work Object Editor 126
organize
Log Viewer folders 268
OS/2 Clients 193
installation kit 110
outbound
registration 121
output screen 187
N
change colors 185
NetBIOS Detail dialog box 63
change fonts 185
NetBIOS resources
store contents 187
define 63
Network Group Details dialog box 57
Network Groups
create 56
delete 57
Network Groups page 56
Network Status
main window 226
open 226
start Scheduler 232
stop Scheduler 232
view
Client information 231
resource details 228
session information 230
view alarms 232
view system information 226
New Dial Script dialog box 47
P
parents
assign
objects 152
assign Client group 99
Parents page 99
Work Object Editor 152
paste
events 135, 159
Log Viewer folders 269
report text 241
Port Group Detail dialog box 66
Port Group Name
add 63, 66
change 68
Port Groups
Index
add 66
stop 199
edit 68
RemoteWare
update 68
print
reports 242
Menu 24
RemoteWare Gateway 309
configure 311
Process Only Detail dialog box 65
define addresses 315
Process only resources
maintain 314
define 65
Profile dialog box (groups) 292
Profile dialog box (user) 280
open pages 310
synchronize 313
remove
Profile dialog box (users) 282
application assignments 287
Protocol Service Detail dialog box 75
filters Schedule Manager 178
protocol services
filters Work Object Editor 154
add 75
copy 76
define 74
delete 76
update 76
Protocol Services page 74
users 284, 295
remove fields
Log Viewer 256
rename
modem types 72
sessions 174
work objects 155
R
Rename dialog box 268
refresh
automatically 220
manually 220
Refresh Automatically option 219
refresh interval
Schedule Manager 176
refresh option
Session Recovery 219
register
template Clients 120, 121
inbound 120
template Clients manual 123
Remote Console 189
DOS Clients 192
OS/2 Clients 193
start 190
troubleshooting 193, 195
Remote Control 196
assigning work object to Clients 197
run session 198
set modem 197
set up 196
start 198
Rename the selected Session dialog box 174
replace
event text 137
Report Editor 241
Report Manager
command line 245
copy text 241
copying reports 243
define reports 244, 317
deleting reports 243
filter information 241
generate
Session Recovery reports 223
generate CSV files 246
generate reports 240
main window 240
open 240
paste text 241
print reports 242
Report Editor 241
search text 242
select file formats 241
use 240
369
370
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
reports
change definitions 244
copy text 241
copying 243
definitions 244, 317
deleting 243
filter information 241
generate 240
Session Recovery 223
generate command line 245
paste text 241
print 242
search 242
select file formats 241
reset
security 96
resource details
view 228
Resource Details dialog box 229
resources
asynchronous 59
Details dialog box 229
display 58
NetBIOS 63
Process only 65
SPX 66
TCP/IP 66
view details 228
Resources page 56, 58
restart sessions 221
rights
deny groups 30
deny users 30
grant groups 29
grant users 29
Row Detail dialog box 270
Category 270
Field 270
Value 270
row details
File Transfers 271
Messages view 270
Sessions 271
S
save
contents output screen 187
dial scripts 49
filters 216
filters Client Profile 80
filters Schedule Manager 178
filters Work Object Editor 154
saved filters 81
use Schedule Manager 178
Work Object Editor 154
Schedule Manager
change refresh interval 176
filter sessions 178
open 175
remove filters 178
save filters 178
select Clustered Servers 179
set execution times 178
stop and start Scheduler 179
use saved filters 178
view current sessions 175
view scheduled sessions 175
Schedule Manager main window 175
Schedule page 165
Scheduler
start Network Status 232
stop and start 179
stop Network Status 232
schedules
session 173
screen
store contents 187
search
Client/Session list box 204
event text 137
events 136
reports 242
Search Client dialog box 204
security
reset Clients 96
set 27
select
fields Log viewer 255
Index
Interactive Session views 184
views 187
Select Application Objects dialog box 144, 286, 296
view Server information 235
session
unassign work object 147
Select Client dialog box 281
Session Detail dialog box 176
Select Clients and Client Groups dialog box 98, 149,
Session Editor
169
assign Clients 169
Select Objects dialog box 141, 152, 168
assign objects 167
Select Sessions dialog box 147
change sessions schedules 173
Select User Groups dialog box 284
Clients page 169
Select Users dialog box 294
copy sessions 174
Select Values dialog box 264
create sessions 164
Server
delete sessions 174
activate resources 56
disable sessions 173
change local name 33
enable sessions 173
change settings 31
limit session activity 172
connections 38
Objects page 167
monitor 233
rename sessions 174
set date and time 34
Schedule page 165
start 20
Sessions page 167
start Administrator 23
set schedules 165
stop 21
unassign work objects 168
stop Administrator 23
Session Editor main window 164
time zone 35
Session Event Detail
view activity Server Profile 239
view information 235
select 270
view 270
Server Messages Log 253
Session Event Details, view 272
Server page
Session History Log 253
Client Profile 89
Server Profile
Session Recovery 201
apply filters 217
Alarms page 41
automatic refresh 220
Cluster page 40, 239
Client details 218
Dial Scripts page 46
Client/Session list box 203
Licensing Log 238
customize window 206
Licensing page 236
ECF sessions 202
Limit Outbound page 55
Failed sessions 202
Logging page 42
Failed-Final sessions 202
Long Distance page 51
filter by Client 211
Modem Types page 69
filter by ECF 214
Network Groups 56
filter by Session 212
Protocol Services page 74
filter by Time Range 213
Resources page 56, 58
filters 207, 208
Server activity 239
generate reports 223
Settings page 39
main window 203
update license values 237
manual refresh 220
371
372
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
miss sessions 202
unassign work objects 168
refresh data 219
unsuccessful restarts 222
remove filters 215
update 219
restart sessions 221
view active 230
save filters 216
view current 175
start 203
view details 176
status 203
view scheduled 175
status icons 204
Sessions page 167
unsuccessful restarts 222
Set
Session Recovery report 223
Session Recovery Report dialog box 223
session status
by Completed 215
Server date and time 34
set
filter field values 264
Long Distance services 51
by Failed 215
Set colors dialog box 185
by Failed-Final 215
Set Font dialog box 186
by Missing 215
Set Refresh Time dialog box 220
by Successful 215
setting
Sessions
view row details 271
sessions
assign 147
properties Log Viewer 254
Settings page
Server Profile 39
set file compression 39
assign Clients 169
silent.ini file 112
assign objects 167
sort fields
both 40
Log Viewer 256
change execution times 178
SPX Detail dialog box 66
change schedules 173
SPX resources
copy 174
create 164
delete 174
define 66
Port Groups 66
start
disable 173
Administrator 27
ECF 202
Remote Console 190
enable 173
Remote Control 198
Failed 202
Scheduler 179
Failed-Final 202
Scheduler Network Status 232
filter Schedule Manager 178
Server 20
inbound 40
limit activity 172
miss 202
outbound
limit 55
rename 174
restart 221
Session Recovery 203
Starting
Clustered Server 22
status
Server 233
view 227
stop
set schedules 165
Remote Control 199
status icons 204
Scheduler 179
Index
Scheduler Network Status 232
long distance services 54
Server 21
Port Groups 68
store contents
protocol services 76
output screen 187
synchronization
sessions 219
upgrade
prevent 305
synchronize
32-bit Clients 106
user groups
address books 303
assign applications 296
RemoteWare Gateway 313
copy 299
system
create 292
change settings 31
delete 300
view status 226
system name
edit 297, 298
users
change 32
add local 280
system status
add remote 282
view 226
assign applications 285
assign attribute 288
T
assign groups 283
copy 291
TAPI modem 86
delete 291
TCP/IP Detail dialog box 66
disable 29
TCP/IP resources
edit attributes 288
define 66
enable 28
Port Groups 66
filter 279
template Clients
grant rights 29
install 111
remove attributes 290
register 120
set parameters 118
template installation kits 111
remove groups 284
users groups
assign users 294
time zone
remove users 295
change 35
Transaction Pipe logs 253
troubleshooting
Remote Console 193, 195
V
view
active sessions 230
U
alarms 232
unassign
work objects 147
work objects sessions 168
unsuccessful restarts 222
update
address books 304
Client definitions 94
license values 237
Client details 218
Client information 231
Cluster activity 239
current sessions 175
database assignments 301
license values 236
Licensing Log 238
Log Viewer row details 270
long messages 270
373
374
R e m o t e Wa r e S e r v e r A d m i n i s t r a t o r ’s G u i d e
Messages row details 270
Group objects 127
resource details 228
import events 140
row details File Transfers 271
Members page 141, 143
scheduled sessions 175
object types 127
select 184
open 126
Server activity 239
Parents page 152
Server information 235
Remote Control work object 197
session details 176
remove filters 154
Session Event Details 272
save filters 154
status 227
set attributes 129
View Properties
Log Viewer 254
open 254
View Properties dialog box
use saved filters 154
Worklist objects 127, 131
work objects 146, 153
Application 127
Add To View option 255
Application Group objects 127
fields 254
assign parents 152
Filter By Field option 263
assign sessions 147
Modify Filter option 265
control execution 39
open 254
copy events 135
Remove Filter option 265
create 128
Remove From View option 256
delete 155
view row details Sessions 271
delete events 135
views
disable 145
select 187
W
work object
Remote Control 197
Work Object Editor
Application Attributes page 142
Application Group objects 127
Application objects 127
apply filters 154
copy objects 155
create work objects 128
delete objects 155
disable work objects 145
enable objects 145
ESD Objects 131
ESD objects 127
Events page 131
export events 139
filter objects 153
General Attributes page 129
enable 145
ESD 127
Group 127
insert events 134
paste events 135
rename 155
search events 136
set attributes 129
unassign sessions 147
Worklist 127
Worklist Editor
copy events 159
create worklist files 156
delete events 159
import event lists 161
insert events 158
paste events 159
worklist Editor
export events 160
Worklist objects 127, 131
Workstations
Index
remove 43
Write Filter File dialog box 216
375
Download PDF
Similar pages