Company: Link Technologies
Case No: L12317. Project: 12.51: LinkSOFT version 12.51
Logged By: Sanjay (Link Technologies) on 07 Jun 2021 10:10AM
Priority: High
Product: Framework
Group: New Feature
Time Taken: 15.00 (Weight: 24.00)
Version: 12.51.0813
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Rashna, Sanjay
Resolve By: Tuesday, 06 July 2021 11:59 PM [1263 days since logged date]
Status: Closed
Subject: LinkSOFT WEB API to handle data transmission between two LinkSOFT Databases instead of using "Linked Servers"
Summary:    

LinkSOFT API development to handle data transmission between two LinkSOFT Databases. This is required to eliminate the following issues:

  1. Replication uses Linked Servers. We have a lot better control via an API and can throttle and add size limits to handle bandwidth and traceability.
  2. Opening SQL server PORT 1433 on a LAN environment poses some risk. Some customers require replication over the internet and are opening SQL server port despite being advised to use a VPN.
  3. Some data for TNA needs to be sent from local installations to the cloud.

High-level design:

  1. Each transmission should be a closed-loop transmission. i.e. there should have a known origin and each batch must be tracked from Initiation, transmission to closure.
  2. Create a function that allocates a unique number to each transmission. The unique ID should be readable, suggest YYMMDD-HHMMSSS-{3 digit code}. Let's name this "Transmission ID", referenced as "TID", to denote a readable code user can use to track each transmission.
  3. This code should be referenced in the status of each transmission. e.g. In TNA, a file being transmitted should have Statuses: "Queued {TID}", "Transmitted {TID}" and at the receiving end, "Received {TID}", "Processed {TID}", "Closed {TID}"
Audit Notes:Edited by sanjay on 12/08/21 17:02. Edited by sanjay on 26/07/21 09:04. Edited by sanjay on 12/07/21 08:20. Edited by sanjay on 12/07/21 08:04. 
12 Jul 202108:04AM Comment 1 by Sanjay (Link Technologies) Case L12317 added to project 12.44
12 Jul 202108:11AM Comment 2 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 12-07-2021 12:10 PM
Proceed with Replication Testing using 12.44

12 Jul 202108:16AM Comment 3 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 12-07-2021 12:13 PM Time Taken: 3.00

Please perform the following tests on Compare Data

  1. Verify Masterfile
    1. Send/Receive Differences
    2. Verify again to confirm data has transmitted correctly
  2. Verify Transactions
    1. Send/Receive Differences
    2. Verify again to confirm data has transmitted correctly
  3. Review Error logs and API Queues
  4. Use Queue monitor to track packages

12 Jul 202108:18AM Comment 4 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 12-07-2021 12:16 PM

For Replication Testing, setup the environment as follows:

  1. One Standalone
  2. Two Branch
  3. HQ

Test data flow between all stations, monitor time taken and record results


12 Jul 202108:20AM Comment 5 by Sanjay (Link Technologies) ETC was changed from 06/07/2021 to 06/07/2021
26 Jul 202109:04AM Comment 6 by Sanjay (Link Technologies) Case L12317 added to project 12.50
11 Aug 202104:08PM Comment 7 by Rashna (Edge Business Solutions) Assigned To: Alvis (Link Technologies) Followup Date: 11-08-2021 01:47 PM Time Taken: 4.00
The following tests were performed:

Table 1 - Test Results
#Test Case DetailsPass/FailComments
 1
  1. Create replication setup with below connections
    1. Head Office
    2. Branch
    3. Standalone
Pass
 
 2
  1. Test replication of master files
 Pass
  1. Created a product in Branch and it replicated to the HQ and standalone DB under 1 under.
 3
  1. Test Inventory Transaction
 Pass
  1. Created a Purchase Order in Branch and it replicated to the HQ and standalone DB under 1 under.
 4
  1. Test sales transactions
 Pass
  1. Processed a sale in Branch and verified the sales report in HQ and Standalone. Data was replicated under 1 min.
5
  1. Test compare data
Pass

Environment Details

  1. OS version:
  2. Application version: 12.50.07023GA
  3. Setup on:
    1. Server:LinkQA4
    2. Database: LinkSOFT-HQ, LinkSOFT-B1, and LINK SOFT-Standalone
    3. LinkSOFT URL: HTTP://10.0.13/LinkWEB-HQ, HTTP://10.0.13/LinkWEB-B1, HTTP://10.0.13/LinkWEB-Standalone
  4. Login Details: Standard username and password for user "admin"

Next Step:

  1. As per the discussion with Alvis, expired token keys are not validated in version 12.50. This has been resolved in version 12.51.
  2. Documentation of replication setup using the "LinkSOFT API".

12 Aug 202105:02PM Comment 8 by Sanjay (Link Technologies) Case L12317 added to project 12.51
16 Aug 202102:22PM Comment 9 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 16-08-2021 06:18 PM Time Taken: 8.00
Documentation completed and published.

If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L12317 in the subject line of all emails regarding this issue.

Document size: 9.3 KB
For call complaints, please contact the Managing Director of the company using this form.