Sentry has been eliminated. Its functionality has been incorporated into Administrator through the use of views, events and the DBMS.

Transcription

1 1 Performance: The overall default system performance is better than in v3.02 when the data is accessed via TCP. When the data is accessed using the new optional direct access method, the performance is much better than in v3.02 (as much as 12 times faster). Encryption: In v3.02 all communications via TCP were encrypted with a weak algorithm. By default in v3.10, no communications are encrypted. By installing an optional certificate on each node that is part of the system, all TCP communications are encrypted with a very strong 128 bit data encryption algorithm. The new optional direct data access method is performed by the operating system and network drivers and access to the data using this method is not encrypted even if a certificate is installed. Sentry: Sentry has been eliminated. Its functionality has been incorporated into Administrator through the use of views, events and the DBMS. The DBMS does much of the system monitoring that was previously done by Sentry. Events: Sentry Events have been replaced with GECS System Events. New GECS Events make it easy for users to choose which Events they care about and what actions or notifications they would like generated when the particular Event occurs. Ability to send SNMP Trap numbers and messages when a particular Event occurs. Jobs can depend on the occurance of Events. User can create and define your own Events. Ability to activate jobs based on specified Events occurring. Ability to customize notifications, using Event Definitions you can customize the messages sent when specific events occur. Ability to play specified WAV files when specified Events occur.

2 2 Job Views: Sentry lists have been replaced with new customizable views. New Job Views to allow customized filtering of jobs displayed in lists. Users can add and share an unlimited number of separate job views. Ability to display jobs within specified windows of time. Ability to sort job lists by job number, date/time or job status. Ability to display job's schedule time, start time or finish time in views. More responsive list population. New Batch Summary views allow jobs to be displayed at the batch or job level. Customizable background and foreground color in Job views. Event Views: New Event views to allow customized filtering of Events displayed in lists. Users can add and share an unlimited number of separate Event views. Users can be alerted to special Events. User event indicator button at the bottom right corner of the administrator program. Customizable background and foreground color in Event views. Job Changes: Job record now contains the new Minimum Good Return Code field. Job record now contains the new Never Late field. Job record now contains the new Job Notes field contains an ASCII text file that can be edited and used for notes, comments or documentation relative to the job. Job record now contains the new Generate Event on success and on failure fields. Job status of Waiting Approval has been renamed to On Hold

3 3 Controller Error File: No more controller error logs (CONTROL.ERR). it has been replaced by Events. Log File: Mo more log file. Log information now maintained with jobs and by events. No more log records. Jobs run only once, repeating jobs create a new instance for each time scheduled to run. New Job statistics information in the job record that contains log info. SNMP: The DBMS can now generate SNMP traps for Events that occur. The new GECSMIB.DLL can be used with Microsoft's SNMP service to monitor GECS from network management software programs.

4 4 Other: Ability to send Internet Mail attachment(s). DBMS data backup option adds the ability click a button to quickly backup GECS data or run a command line utility to backup GECS data. New Command Line Utilities GECSEVNT, GECSBKUP and GECSCERT. Enhanced Web Client programs. SDK Updates. New Substitution Variables for batch name, and MANY MORE... Allowing the use of formatting strings in substitution variables such as (%m). You can no longer simulate a job. This has been replaced with the ability to change the job's return code or skip and reschedule the job. The DBMS handles loading WRK files not the Controller. The DBMS now sends and receives all . The DBMS now handles most system maintenance tasks such as purging old jobs. Job detail now has the new This Jobs History toolbar button. Job detail now has the new This Jobs Events toolbar button. Ability to ping Agents, Controller, or DBMS from the Administrator program. All lists can display a record count by right clicking on the column header.

5 Caveats when upgrading from Version ECS 5.x: TCP-IP is required. If you are running a network without IP, (e.g. Novell with only IPX/SPX) you will need to contact your network administrator. If you install all the GECS components (DBMS, Controller and Agent) on one computer, you still need TCP-IP. Environmental variables, file dependencies (trigger files) and minimum disk space requirements are relative to the agent computer. Remember, your job server is now split into two pieces which may or may not be on one computer. DOS, OS/2 and Windows 3.x are not supported. DOS, OS/2 and Windows 3.x are still a valid command line types. But, the jobs must run on an NT/2000 agent. There is limited support for Windows 95/98. It can still be a valid command line type but, the jobs must run on an NT/2000 agent. The GECS Administrator program can be installed on computers running Windows 95/98. Job Notes are no longer supported. "Smart Pulse" is no longer supported in GECS Sentry. Controller.err (formerly SERVER.ERR) file can no longer be viewed from the Controller Edit screen. Btrieve(r) client/server issues are gone. Btrieve(r) is not used by Global ECS v3.0, other than to convert your ECS 5.1 data. If you have applications which use Btrieve(r) (or other products from Pervasive Software), there are no longer any special setup configurations required. Existing applications compiled with earlier versions of the SDK (including Direct ECS) will need to be re-built with Version 3.00 of the Global ECS SDK.