Projects:Store Server Module Validation Updating

Contents 1 Introduction 2 Validate synced tables and dataset as part of build validation 3 Validating synced and dataset tables from the UI 3.1 Dataset validation 3.2 Synced Table validation 3.3 Global Validation Process 4 Tracking Issue

Introduction

This project is to encapsulate 2 different topics related to the store server documentation:

• provide a wiki page outlining the approach to take when installing bug fixes and new features in a multi-server environment
• provide a wiki page which gives guidelines to developers when developing for a store server environment. See here for the first version.
• combine the validation of synched tables and store server creation datasets into one process which can be called from the UI. See separate section below.

The documentation will be added to the main Store Server landing page.

Validate synced tables and dataset as part of build validation

• The proposal is to include synced table/dataset validation as a module validation in the build step.
• The main obstacle is that the current validation logic uses the DAL. This needs to be reworked to not use the DAL in any place. The changes are in 2 files:
  • SynchronizationDataSetValidation.java
  • SynchronizationTableValidation.java
• The next step is to add:
  • a module validation to the replication module which checks the synced table definition
  • a module validation the store server synchronization module which checks the store server dataset

Validating synced and dataset tables from the UI

The proposal is to create a process which can be called from the Synchronized Table and from the DataSet tab.

Dataset validation

• A button with the label validate should be added to the dataset window-root tab.
• This button should only be visible for the Store Server Dataset (you can use the UUID of the store server dataset as display logic).
• When clicked the system should do the same as the validate.storeserver.dataset task in the storeserver.synchronization/build.xml file. See the java code which can be copied here.
• The result of the task should be shown in a popup window.
• If there are no errors/warnings then the system should show a green message in the popup.
• If there are errors/warning then the system should show these in the popup message. Possibly change the way the validation code now prints errors to capture them and display them in the popup.

Synced Table validation

• Add a new button to the synchronized table window.
• When clicked the system should do the same as the validate.sync.tables task in the replication.symmetricds/build.xml file. See the java code which can be copied [1].
• The result of the task should be shown in a popup window.
• If there are no errors/warnings then the system should show a green message in the popup.
• If there are errors/warning then the system should show these in the popup message. Possibly change the way the validation code now prints errors to capture them and display them in the popup.

Global Validation Process

• A global validation process should be implemented and reachable through the menu for the system admin.
• This global validation process should combine the 2 validation tasks above and show the total result in the popup window.

Tracking Issue

For the store server table validation task:

• https://issues.openbravo.com/view.php?id=33237