Difference between revisions of "EDI Integration"
From TrueERP wiki
Simon Clive (Talk | contribs) |
Simon Clive (Talk | contribs) |
||
| Line 18: | Line 18: | ||
These connections are created using the Web API, so please ensure that the "'''Web API Test'''" form is working correctly within the required TrueERP database, before attempting anything to do with the EDI integration | These connections are created using the Web API, so please ensure that the "'''Web API Test'''" form is working correctly within the required TrueERP database, before attempting anything to do with the EDI integration | ||
| − | *For this to work all remote IP Addresses'''Must be Fixed IP Addresses''', however the Main Server can be Dynamic. | + | *For this to work all remote IP Addresses '''Must be Fixed IP Addresses''', however the Main Server can be Dynamic. |
*'''All EDI''' set up is done on the '''Main Server''', nothing has to be done at a Remote Location | *'''All EDI''' set up is done on the '''Main Server''', nothing has to be done at a Remote Location | ||
| + | <br> | ||
| − | + | <u></u><u></u>'''Two Way Synchronisation''' works on a '''Push – Pull''' basis, meaning the Main Server '''Pushes All''' data out to a remote location and then '''Pulls All''' data back from this remote location. The disadvantage of this set up is that '''All''' of the data from both Databases needs to '''Synchronise''' which is extremely slow and in most cases not required. | |
| − | <u></u><u></u>'''Two Way Synchronisation''' works on a '''Push – Pull''' basis, meaning the Main Server '''Pushes All''' data out to a remote location and then '''Pulls All''' data back from this remote location. The disadvantage of this set up is that '''All''' of the data from both Databases needs to '''Synchronise''' which is extremely slow and in most cases not required. | + | |
'''One Way Synchronisation''' of only selected data is much faster as only relevant data is '''Pushed''' to a remote location eg Product/Inventory Data and then only the required data is '''Pulled''' back eg POS / Sales Transactions | '''One Way Synchronisation''' of only selected data is much faster as only relevant data is '''Pushed''' to a remote location eg Product/Inventory Data and then only the required data is '''Pulled''' back eg POS / Sales Transactions | ||
| Line 29: | Line 29: | ||
<br> '''Source vs Destination''' | <br> '''Source vs Destination''' | ||
| − | *When setting up Site Config for '''POS''' the '''Source''' is the Remote Location and the Destination is the Main Server '''(Pulling Data)''' | + | *When setting up Site Config for '''POS''' the '''Source''' is the Remote Location and the Destination is the Main Server '''(Pulling Data)''' |
*When setting up Site Config for '''Product''' it works in Reverse the '''Source''' is the Main Server and the Destination is the Remote Location '''(Pushing Data)''' | *When setting up Site Config for '''Product''' it works in Reverse the '''Source''' is the Main Server and the Destination is the Remote Location '''(Pushing Data)''' | ||
| + | <br> '''Site Integration ''' | ||
| − | + | *From the Main Menu Select '''Utilities – Preferences''' | |
| − | + | *Select'''EDI and Integration''' and Scroll down to the '''Site Integration''' header | |
| − | *From the Main Menu Select '''Utilities – Preferences''' | + | |
| − | *Select'''EDI and Integration''' and Scroll down to the '''Site Integration''' header | + | |
*'''Tick''' the '''Site Integration Enabled''' check box and the select the desired Logging Level | *'''Tick''' the '''Site Integration Enabled''' check box and the select the desired Logging Level | ||
<br> | <br> | ||
| − | '''Site Integration Config''' | + | '''Site Integration Config''' |
*Select the'''Add '''button to set up a new'''Integration Site Configuration''' | *Select the'''Add '''button to set up a new'''Integration Site Configuration''' | ||
| − | Fill out the | + | Fill out the '''Source''' field with the following <br> '''URL''' – URL of your Source server eg https://202.168.123.322:446<br>'''Database''' – ERP database name that changes will be read from eg sample_company <br>'''User''' – ERP user name to log into database with eg webuser<br>'''Password''' – ERP user password to log into database with eg webuser |
| − | '''Source''' | + | |
| − | field with the following | + | |
| − | <br> | + | |
| − | '''URL''' – URL of your Source server eg https://202.168.123.322:446<br>'''Database''' – ERP database name that changes will be read from eg sample_company <br>'''User''' – ERP user name to log into database with eg webuser<br>'''Password''' – ERP user password to log into database with eg webuser | + | |
| − | + | ||
| + | <br> | ||
Fill out the '''Destination''' field with the following | Fill out the '''Destination''' field with the following | ||
Revision as of 17:22, 20 August 2012
Overview
Creating a connection using EDI
These connections are created using the Web API, so please ensure that the "Web API Test" form is working correctly within the required TrueERP database, before attempting anything to do with the EDI integration
- For this to work all remote IP Addresses Must be Fixed IP Addresses, however the Main Server can be Dynamic.
- All EDI set up is done on the Main Server, nothing has to be done at a Remote Location
Two Way Synchronisation works on a Push – Pull basis, meaning the Main Server Pushes All data out to a remote location and then Pulls All data back from this remote location. The disadvantage of this set up is that All of the data from both Databases needs to Synchronise which is extremely slow and in most cases not required.
One Way Synchronisation of only selected data is much faster as only relevant data is Pushed to a remote location eg Product/Inventory Data and then only the required data is Pulled back eg POS / Sales Transactions
Source vs Destination
- When setting up Site Config for POS the Source is the Remote Location and the Destination is the Main Server (Pulling Data)
- When setting up Site Config for Product it works in Reverse the Source is the Main Server and the Destination is the Remote Location (Pushing Data)
Site Integration
- From the Main Menu Select Utilities – Preferences
- SelectEDI and Integration and Scroll down to the Site Integration header
- Tick the Site Integration Enabled check box and the select the desired Logging Level
Site Integration Config
- Select theAdd button to set up a newIntegration Site Configuration
Fill out the Source field with the following
URL – URL of your Source server eg https://202.168.123.322:446
Database – ERP database name that changes will be read from eg sample_company
User – ERP user name to log into database with eg webuser
Password – ERP user password to log into database with eg webuser
Fill out the Destination field with the following
URL – URL of your Destination server eg https://localhost:446
Database – ERP Database name that changes will be written to eg. sample_company
User – ERP user name to log into database with eg webuser
Password – ERP user password to log into database with eg webuser
