Orax SDI Cloud Reference

 
  1. Introduction
  2. Self-Management tools
  3. Communication and Content management
  4. Sales and Customer Relationship Management
  5. Services & Service level management
  6. Billing and customer statements
  7. Inventory & Asset management
  8. Production management
  9. Human Resources and Payroll
  10. Procurement and Supply chain
  11. Ledgers & Accounting
  12. Reporting and Analytics
  13. Administration & configuration
  14. Business Improvement
  15. Development and Process management
    Up    Previous    Next

Integration Development

Orax SDI is a cloud platform able to interface with other systems like eternal computers and sensors. Often the need will arise to compile reports or logic based on external data, or a hybrid of internal and external data. To address this need you need to load the external data into a record in the Orax SDI system. A custom record can be created in the Development module. Workflows, reports and modules can be build that makes use of custom and standard data in the Orax SDI system.

The primary interface used for integration is the Automation module. The Automation module is meant to receive and send data in the form of metrics or other custom datasets. Integration with other systems is therefore a good match for the integration module.

The standard way of integrating one-way data from external systems is to deploy an Automation agent (program) on the remote database system. An integration script can then be used to pull changes off the external system and send them to Orax SDI for processing. The following outline explains the working and components of such an integration setup.

1. Create an Automation System in Orax SDI and deploy the corresponding agent on the external system.
This allows the remote agent to be managed from inside Orax SDI and receive uploads.

2. Create an Integration metric in the System on Orax SDI.
An Integration metric is a script that is executed on the remote system on an interval. The script connects to the external database, compiles a change dataset (new records, updated records and deleted records) and uploads it to Orax SDI. An example of such a script is available for Windows.

3. Integration processing is performed once the dataset is received and saved in a custom record.
Data changes are uploaded to Orax SDI in a CSV semi-colon separated file. Each line in the file starts with XTP:. It then requires a N (new record), U (update) or D (delete). This is the first field of the CSV record. After that a unique identifier for the data is required (Unique ID field). Orax SDI will use this unique ID to update and delete data and ensure that new data is not duplicated. Following these 2 fields, the rest of the data has to be listed and match the custom record fields exactly. Below is an example of the CSV file.


XTP:N;UniqueID;Data1;Data2;...
XTP:U;UniqueID;Data1;Data2;...
XTP:D;UniqueID;Data1;Data2;...



A sample / template integration script is available for Windows SQL Server systems. It uses VBScript to connect to a database and create a local set of change tables. Using these change tables, the system calculates records that need to be sent to Orax SDI. The CSV files is populated and sent to the Orax system.

For more information about integration and especially custom integration please contact Orax support. Orax SDI has an API that can be used to build many kinds of custom applications and integration.

 

    Up    Previous    Next