Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Key

Summary

Issue Type

Release Notes

AR-37

AR_We need a link to on-line help file on 'Installation Welcome' and 'Replicator Manager' screens

Change Request

On the Welcome page of Adonis Replicator, there is a link to the instructions on how to install configure and upgrade Replicator:

AR-73

Possibility to set max file size

Change Request

The maximum size of a CAB/RPL file can be set on the page of Replicator Settings Wizard. To do it, enter the maximum size value to the Maximum size of an export file field:

This setting sets max file size for both high and low priority files.

The size setting value must be more or equal to 100000 bytes or 0.

AR-85

Export failure when exporting data from PWLOG_PAYROLL_EXEC table

Change Request

Fixed the issue occurred while trying to export the PWLOG_PAYROLL_EXEC table to Replicator.

AR-86

An explicit value for the identity column

Bug

Launching replication for a vessel resulted in the error "An explicit value for the identity column in table '#_PWTRN_COURSE_SCHEDULES_OLEDOCS' can only be specified when a column list is used and IDENTITY_INSERT is ON". The error has been fixed via creating a temporary table that has no IDENTITY column.

AR-105

Error log to track errors and activity of Replicator Plugins

Change Request

AR-129

Replication Monitoring: impossible to add a client in the android application

Bug

The Android application did not allow adding clients. The issue has been fixed.

AR-130

Replication Monitoring: to show login form in android app in the case when android user was removed from ReplMonervice

Bug

The Android application checks errors on each request. In case an error occurs because a user is deleted, the application closes while logging out all the users.

AR-131

Replication Monitoring: Exit action for Clients screen in android application

Change Request

The Android application can be closed by clicking the Back button twice.

AR-134

Reliability improvements

Change Request

Applied a set of changes:

  • The maximum size of a CAB/RPL file can be set on the page of Replicator Settings Wizard.

  • Fixed the issue occurred while trying to export the PWLOG_PAYROLL_EXEC table to Replicator.

  • The error "An explicit value for the identity column in table '#_PWTRN_COURSE_SCHEDULES_OLEDOCS' can only be specified when a column list is used and IDENTITY_INSERT is ON" has been fixed via creating a temporary table that has no IDENTITY column.

AR-137

Update the database connector class and the procedure that tests a database connection

Change Request

The settings wizard's page for database connection settings has been changed:

  1. ADO connection string was replaced with OLE DB Provider, SQL Server Name and Database Name parameters since the settings wizard does not use or save other connection string parameters any more.

  2. The controls for current site number are moved to the DB settings page from Export/Import page of the settings wizard.
    This is because the current site number has become a part of the db connection settings. Replicator uses the current site number to retreive the password for REPL user from PWSECURITY_USERS table.

AR-168

Update formatting of "TablePKS = ?" parameter for the import query

Change Request

Replicator forms a value to pass to “TablePKS = ?” placeholder on import in the same way as the delete triggers do for repl_Deleted.TablePKS column (see ad_CreateTriggerForDeleteSQL function in the Adonis database).

AR-169

Switch to repl_Deleted table instead of repl_Deleted_log

Change Request

The following enhancements are implemented:

  • Updated the SQL script that replicator uses to delete a row from repl_UpdateParameters table. The system generates the DELETE action for table repl_UpdateParameters and inserts the DELETE action into repl_Deleted and repl_Deleted_Log tables. The record is populated in the columns TableName, TablePKS, GMTDeletedDate in the both tables.

  • Updated the delete trigger that replicator creates for repl_Programs table. Replicator Manager deletes trigger called TDv2_repl_Programs.

AR-172

Possibility to setup replication for new site separately from the general one

Change Request

Added the possibility to choose a site and export data to it separately from the general replication. As a result, the replicator can replicate data for sites without waiting until a time-consuming export to a new vessel completes.

  1. Click the Independent Export node in the connection tree. Replicator Manager opens the Independent Export workspace:

  1. On the workspace, click the drop down list to select a site for which

Replicator will export data separately from the general replication.

Once done, the site number selected in the drop down list is shown in the Independent Export node:

From this moment the chosen site can be exported separately and it will be excluded from the export phase of the general replication: data export for that site will not be shown in Replication Status page and will not be logged to ReplService.log. Instead, data export for that site will be shown on the Independent Export workspace and will be logged in IndepRepl.log.

The independent export cannot be run on schedule but you can run it any time manually, no matter whether the general replication is running or not.

You can return the independently exported site back to the export phase of the general replication. To do it, select None in the drop down list of the Independent Export workspace.

AR-203

Status and real situation with uploading upgrade pack could be different

Bug

Added more information in the status column, reflecting the real status of each vessel upgrade

AR-204

No option to publish the same update package

Bug

Minor issue with regards to deleting records from repl_program.

AR-206

Update the delete trigger of repl_Programs and the program deletion procedure

Change Request

Minor issue with regards to deleting records from repl_program.

AR-207

Run parameters of the replicator service

Change Request

Added two command line switches to produce a more extended log to trace more replicator details and trace memory usage of the replicator service.

  1. -logschedule - enables logging of various actions related to replication and plug-in schedules to ReplFeatures.log

  2. -logmemory - enables logging of virtual memory information (size, number of blocks and others) to ReplService.log each time a replication starts or completes.

How to add the command line switches

  1. Start the Replicator manager

  2. On the welcome page, double-click on the Replicator instance name you want to add one or both of the switches.

  1. In the opened dialogue box, specify the required run parameters (e.g. “-logmemory -logschedule“) using space as a delimiter and click OK.

  1. Start the service for which you have entered the run parameter:

To disable the debug logging of a switch, stop the replicator service, open the Edit Run Parameters dialogue, delete the switch from the parameters line and start the service again.

AR-208

Add HTTPS Support to Replicator Monitoring Service

Change Request

Added HTTPS Support to Replicator Monitoring Service. To establish HTTPS connection, follow the steps below:

  1. In Adonis Replicator wizard, select the WebSocket protocol option and specify Server URI, its username and passord:

  1. In

Adonis Monitoring Service wizard, make sure the Use a separate port for Replicator services option is not selected and specify the SSL certificate location and private key:

AR-209

Replicator can not update APP with psexec utility

Bug

Replicator failed to update Adonis Personnel Portal. The issue has been fixed.

AR-213

Replicator unable to transfer files via SFTP

Bug

Fixed the issue that appeared while transferring files via SFTP.

AR-216

Replicator is using plain FTP even if "Use SSL" checkbox has a checkmark

Bug

If the Use SSL checkbox is selected in Replicator wizard, Replicator communicated FTP. The error has been fixed.

In addition, an attempt to connect to the Adonis FTP server with the preselected Use SSL option results in the message: SSL isn’t available for this server.

AR-219

Issue with the replicator's auto-upgrade

Bug

The interface buttons are aligned:

AR-243

Onboard replication frequently "hangs" at SFTP sending or receiving stage and service becomes unresponsive

Bug

When the secure connection breaks, the system entered a deadloop. The issue is now fixed.

AR-255

Monitoring Service doesn't respond after Logout action from android application

Bug

AR-256

Checking login and password during "test connection" action for Monitoring Service

Change Request

Added connection verifications:

  • While installing/updating the Replicator Service, it is possible to verify whether the connection to the Monitoring Service is successful:

  • In the Settings wizard of Replicator Service, it is possible to verify whether the login and password are valid:

AR-258

Replication Monitoring Service: not possible to create an android user if no one client exists in database

Bug

On logging in as administrator to the Monitoring Service and trying to add a new android user, an error occurred in the New Android Login dialog. The issue has been fixed.

AR-260

Replication Monitoring Service: issues with displaying actual data in Android application

Bug

The Android application did not show any details after replication. The issue has been fixed.

AR-264

Define set of monitoring service events for the Windows Event Viewer

Change Request

The monitoring service events are available in the Event viewer:

AR-272

Add check for server protocol version and some more minor changes

Change Request

Enhanced the Replicator functionality with the following:

  • Added check for the monitoring server protocol version to the replicator service to forbid communication between incompatible server and replicator.

  • Updated the transport protocol constants, conversion functions and correspondent UI controls for clarity in the source code and UI. Set possible transport protocols to TCP and WebSocket.

  • Fixed double exception in TWebSocketConnection methods in case of an exception in a TScWebSocketClient object to increase the replicator stability.

AR-280

Create a user-friendly dialog box for setting replicator service start parameters

Change Request

In Adonis Replicator, added two command line switches to get a more extended log with replicator details and memory usage of the replicator service:

  • -logschedule enables logging of various actions related to replication and plug-in schedules to ReplFeatures.log

  • -logmemory enables logging of virtual memory information (size, number of blocks and others) to ReplService.log each time the replication starts or ends

The command line switches are organized as checkboxes for a user to avoid mistakes while typing them manually:

Key

Summary

Issue Type

Release Notes

AR-90

Change to new Modified Icons

Change Request

Updated icons for application and installation set

AR-94

Replicator throws sql Security Error

Bug

To support TLS 1.2 and above we have implemented the possibility to support multiple database providers.   In the connection properties, you can select the OLE DB Provider.

If you receive the following error message, see below, you select MSOLEDBSQL

Connection failed:
SQLState: '08001'
[Microsoft] Microsoft OLE DB Provider for SQL Server [Message] [DBNETLIB][ConnectionOpen (SECDoClientHandshakeO).]SSL Security error.

Image Removed

AR-95

When processing repl_delete the system should continue when deleting from a non existing table

Bug

The replicator continues with the remaining scheduled tasks after it failed to delete information from a non-existing table.

AR-98

"Connection closed gracefully" during connection to SFTP

Bug

To transfer replication files via SFTP protocol, select SFTP as the mail system on the first page of the replicator settings wizard. The settings page for setting up a connection to an SFTP server is almost the same as the FTP settings page.

The SFTP protocol is a subsystem of the SSH protocol and it protects the communications between client and server with strong encryption. This is why there is one important difference between setting up an FTP connection and an SFTP connection. Before the replicator can connect to an SFTP server automatically (and transfer files to and from it), a person who sets up an SFTP connection must verify the server's host key. This can be done with the Test connection button on the SFTP settings page. In the middle of the SFTP connection test, you can see a dialogue box that shows the host key fingerprint. The dialogue enables you to verify or reject the server's host key.

Image Removed

A dialogue looking like this will be shown each time when you hit the Test connection button on the SFTP settings page. Due to his, you can always know the server's key fingerprint. You can also cancel the key verification if you do not trust the server anymore and then the replicator will not be able to connect to the server automatically.

Before setting up a connection to an SFTP server, we recommend reading short descriptions below that explain how to authenticate a server by its SSH host key. Links:
Verifying the host key
Host key fingerprint is an integral part of session information
Safely obtaining host key

AR-111

Allow dropping repl_Distrib_PW001OLEDOCS table

Bug

We changed distrib update query, and now it updates only those records where the state is actually changed.

This optimization will reduce the amount of data the query writes to the transaction log

AR-113

Not possible to use CTE (WITH Statement) in the select statement used as the restriction query

Bug

Common Table Expressions (CTE) as restriction queries are now supported.

AR-124

Not possible to use CTE (WITH Statement) in the select statement used as a purge rule

Change request

Implemented support for common table expression in the purge query

AR-140

P0P, P1R, and P05, P08 updates not picked by Replicator for no reason

Bug

Fixed the initialization problem when setting up a partial replication. In certain situations when the first time replication of the restriction query did not result in any pin, persons, to export. The system treated the next exports as if the destination site was a full replicated database that is transferred into partial replication site.

AR-100

New loading screen

Change request

Updated Icons for login and loading screens

AR-116

Incorrect purge of distribution tables

Bug

Modified purge database query to only delete records related to the current destination site

AR-42

Add a setting for update timeout

Change request

If due to some reasons the upgrade process is performing longer than value PROG_UPDATE_TIMEOUT_MIN from Replicator.ini then the upgrade won't be finished and the corresponding error message will appear in the Last Update Log.

AR-125

Change type of PKS parameter to match db field type

Change request

Various performance-related improvements.

Database Modifications


...

Other Versions 

Page Properties Report
cqllabel = "ar-rn"