This document provides information about version 2.6 of Event Replicator Administration.
Event Replicator Administration (as a subproduct of Adabas Manager) is a web-based graphical user interface (GUI) you can use to perform administrative tasks for Event Replicator for Adabas.
A complete description of the operating environment required by Event Replicator Administration is provided in Platform Coverage and Prerequisites.
The following updates have been made in this release:
Support for the new Event Replicator for Adabas global initialization parameter LOGINPUTTRANSACTION has been added. This new parameter has been introduced to reduce the possibility of replication pool overflows . It allows you to specify that the Event Replicator should use its SLOG system file as a temporary storage location for incoming compressed replication transactions, before they are queued to the assignment processing phase. This means that during the input phase, the compressed transactions are stored first in the Event Replicator Server replication pool, but then written to the SLOG system file, freeing up the space in the Adabas nucleus and Event Replicator Server replication pools. Such compressed input replication transactions written to the SLOG system file are called database-related input transactions. For more information on this parameter, read Setting Global Values.
Support for the new Event Replicator for Adabas global initialization parameter SUBTASKWAIT has been added . This new parameter allows you to override the default time in which the Event Replicator Server waits for an input or output subtask to initialize . The default wait time is 10 seconds, but you might have need to increase this time for your operating environment. When the Event Replicator Server starts an input or output subtask, it will now wait the number of seconds specified by the SUBTASKWAIT parameter (or 10 seconds if no SUBTASKWAIT parameter is specified) for the subtask to initialize. For more information on this parameter, read Setting Global Values.
Support for the new Event Replicator for Adabas global initialization parameter GOPEN has been added . In addition, support for the new DOPEN parameter has been added with all destination definitions in Event Replicator Administration . In prior releases, every destination was opened at startup. The DOPEN and GOPEN parameters allow you to control this functionality . DOPEN is a parameter you use in any individual destination definition to indicate whether or not that destination should be opened at startup or whether the decision to open the destination should be determined by the setting of the GOPEN parameter. GOPEN is a global parameter you use to specify the global policy on opening destinations at Event Replicator Server startup. For more information on the GOPEN parameter, read Setting Global Values. For more information on the DOPEN parameter, read about creating individual types of destination definitions in Maintaining Destination Definitions .
Support for the new Event Replicator for Adabas destination definition parameter DEVENTLOG has been added . This parameters allows you to log significant Event Replicator Server events to any destination (except Adabas destinations) you choose.
Event Replicator Server events are logged in URBS elements. In prior releases, these URBS elements were sent to destinations related to the event itself. With this enhancement, the URBS elements are also sent to any other destinations you have defined with DEVENTLOG=YES. If a related destination also is defined with DEVENTLOG=YES, it will only receive one instance of the URBS element.
To access the log of Event Replicator Server events in a destination queue, you must supply your own application that reads the event URBS elements in the destination queue. If such an application does not exist, the logged events simply sit in the queue.
For more information about this parameter, read about creating individual types of destination definitions in Maintaining Destination Definitions .
Support for the OPTIONS keyword of the DCLASSPARM parameter no longer supports a setting of 1 . If OPTIONS=1 is specified, it will be ignored.
However, this version introduces a new setting of the OPTIONS keyword: 32. If OPTIONS=32 is specified, the full before image (if available) and after image of all fields are sent for an update, even if the field values were not changed or are null. For more information about the DCLASSPARM options, read about creating individual types of destination definitions in Maintaining Destination Definitions .
Support for the new transaction filter definition parameters FSBEGIN, FSLENGTH, FTBEGIN, and FTLENGTH have been added . These parameters allow you to create a transaction filter for part of an alphanumeric or binary field (this functionality is not provided for fields in float format). Include and exclude processing function in the same way for partial fields as for complete fields in your transaction filters.
These new parameters specify the starting byte and length of the source field for which the comparison will take place (FSBEGIN and FSLENGTH parameters) and the starting byte and length of the target field (if one is specified) to which the source field should be compared (FTBEGIN and FTLENGTH parameters). .
Note:
The format of the complete field is used for partial field
comparisons. If the formats of a source field or partial source field and a
target field or partial target field do not match, the comparisons may always
result in an unequal condition. For example, comparing an alphanumeric field to
a packed field will always result in an unequal condition.
For complete information on these new parameters, read Maintaining Transaction Filter Definitions.
Support for the new "Update" value of the subscription file definition parameter SFREPLICATEDELETE has been added. The specification allows you to indicate how replicated physical deletes should be handled on your target database. If SFREPLICATEDELETE=Update is specified and an input record for the DBID/file is for a delete, the before and after images of the input record are passed to your subscription user exit. Your subscription user exit can then control the processing of replicated physical delete transactions on your target database. Your subscription user exit can have them:
physically deleted from your target database
converted to an update
ignored and not sent at all.
For complete information on the SFREPLICATEDELETE parameter, read Maintaining SFILE Definitions.
Support for the new subscription file definition parameter SFSECURITYFILE has been added. This parameter indicates that the subscription file is a security file of a source database and should be replicated. Security definitions then can be replicated when they have been added or updated on an Adabas database.
Note:
Adabas Security Facilities, including the Adabas security utility
(ADASCR) can be obtained only by special request. If you are interested in
Adabas Security Facilities, please contact your Software AG sales
representative.
The parameter specifications of SFILE definitions that are set to replicate security definitions are very specific and vary from those SFILE definitions for other Adabas files. In addition, a file defined in an SFILE definition with SFSECURITYFILE=YES cannot be used in initial-state definitions. For complete information on the SFSECURITYFILE parameter, read Maintaining SFILE Definitions.
Updates have been made to the Data Mapping Tool in this release. For a complete description of these enhancements, read Data Mapping Tool Release Notes.
For information on how long a product is supported by Software AG, access Software AG's Empower web site at https://empower.softwareag.com. Log into Empower . Once you have logged in, you can expand in the left menu of the web page and select to access the Product Version Roadmaps application. This application allows you to request support information for specific products and releases.
Support for 32-bit Linux operating systems will be dropped in a future version.
The documentation for this product is new with this release. If you have an Empower account, current, updated, and past versions of the documentation can be reviewed and downloaded by linking to the Software AG documentation, found on Software AG's Empower web site. If you do not have an Empower user ID and password yet, you will find instructions for registering on this site (free for customers with maintenance contracts).
The Event Replicator Administration documentation includes:
online HTML topics describing all aspects of the product;
Adobe Acrobat Reader Portable Document Format (PDF) files created from the HTML topics;
Adobe Acrobat Reader Portable Document Format (PDF) files for a series of manuals created from the HTML topics.
No hard-copy documentation is provided, but you can print the PDF and HTML files on your local printer.
With Service Pack 2 (SP2) for Windows XP and Service Pack 1 (SP1) for Server 2003, Microsoft introduced a range of powerful new security features that restrict active content that runs locally on your computer. Active content includes ActiveX controls, Java applets, and JavaScript. Software AG's documentation web pages contain some JavaScript, and the SEARCH, INDEX and CONTENTS capabilities are implemented as Java applets. As a result, when viewing documentation web pages that reside on your PC using Internet Explorer and Mozilla Firefox under Windows XP SP2, note that active content is blocked. You must explicitly and repeatedly allow active content if you want to make use of the documentation's full navigation features. Note that this behavior is only observed when reading web pages installed locally on your PC, including those on CD in the PCs CD-ROM drive.
The active content for which Software AG is responsible, that is, the JavaScript code in our HTML documentation pages, will not harm your computers. The risk in using the navigation applets is negligible: Software AG has received no reports from users concerning any harm caused to a computer by the applets. We therefore suggest that when reading Software AG documentation in a local context, you should allow active content via the Security settings in the browser (with Internet Explorer, usually found under Tools > Internet Options > Advanced).
Full details of alternatives can be found on the home page of the suppliers of the navigation applets: http://www.phdcc.com/xpsp2.htm.
