EDI Integration - Revision history

Simon Clive at 04:50, 24 August 2012

2012-08-24T04:50:12Z

Simon Clive at 06:24, 20 August 2012

2012-08-20T06:24:44Z

Simon Clive at 06:23, 20 August 2012

2012-08-20T06:23:23Z

Simon Clive at 06:22, 20 August 2012

2012-08-20T06:22:52Z

Simon Clive at 06:22, 20 August 2012

2012-08-20T06:22:04Z

Simon Clive at 05:30, 20 August 2012

2012-08-20T05:30:44Z

Simon Clive at 05:29, 20 August 2012

2012-08-20T05:29:29Z

Simon Clive at 05:28, 20 August 2012

2012-08-20T05:28:26Z

Simon Clive at 05:19, 20 August 2012

2012-08-20T05:19:10Z

Dene at 02:01, 5 January 2012

2012-01-05T02:01:31Z

← Older revision		Revision as of 04:50, 24 August 2012
Line 51:		Line 51:

	'''URL''' – URL of your Destination server eg https://localhost:446<br>'''Database''' – ERP Database name that changes will be written to 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		'''URL''' – URL of your Destination server eg https://localhost:446<br>'''Database''' – ERP Database name that changes will be written to 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>
		+
		+	'''Suggested web sites for more information on Ports and Forwarding: '''<br>
		+
		+	http://serverfault.com/questions/26564/how-to-check-if-a-port-is-blocked-on-windows
		+
		+	http://www.t1shopper.com/tools/port-scan/
		+
		+	http://www.yougetsignal.com/tools/open-ports/<br>

	<u><br></u>		<u><br></u>

@@ Line 44: / Line 44: @@
 *Select the '''Add '''button to set up a new'''Integration Site Configuration'''
-&nbsp;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
+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
 <br>

@@ Line 35: / Line 35: @@
 *From the Main Menu Select '''Utilities – Preferences'''
-*Select'''EDI and Integration''' and Scroll down to the '''Site Integration''' header
+*Select&nbsp; '''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
@@ Line 42: / Line 42: @@
 '''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'''
 &nbsp;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

@@ 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
-*For this to work all remote IP&nbsp;Addresses'''Must be Fixed IP&nbsp;Addresses''', however the Main Server can be Dynamic.
+*For this to work all remote IP&nbsp;Addresses '''Must be Fixed IP&nbsp;Addresses''', however the Main Server can be Dynamic.
 *'''All EDI'''&nbsp;set up is done on the '''Main Server''', nothing has to be done at a Remote Location
 <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
@@ Line 29: / Line 29: @@
 <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 '''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'''
 *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
 <br>
 '''Site Integration Config'''
 *Select the'''Add '''button to set up a new'''Integration Site Configuration'''
-&nbsp;Fill out the
+&nbsp;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
-−
 Fill out the '''Destination''' field with the following

@@ 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
-'''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
+<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.
-'''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)'''
-<br>'''Site Integration '''
+'''Site Integration '''
-From the Main Menu Select '''Utilities – Preferences '''<br>Select'''EDI and Integration''' and Scroll down to the '''Site Integration''' header<br>'''Tick''' the '''Site Integration Enabled''' check box and the select the desired Logging Level
+*From the Main Menu Select '''Utilities – Preferences'''
 <br>
 '''Site Integration Config'''
-'''<br>Select the Add button to set up a new '''Integration Site Configuration <br>Select the '''Setup''' button which loads an information screen with the following set up recommendations
+*Select the'''Add '''button to set up a new'''Integration Site Configuration'''
-. Turn off '''Two Way Synch'''<br>2. From Head Office select '''POS''' and set time to '''5 mins'''<br>3. From the Remote Site select '''Product''' and set time to '''8 hours'''
+&nbsp;Fill out the
 Fill out the '''Destination''' field with the following
-'''<br>URL''' – URL of your Destination server eg https://localhost:446<br>'''Database''' – ERP Database name that changes will be written to 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
+'''URL''' – URL of your Destination server eg https://localhost:446<br>'''Database''' – ERP Database name that changes will be written to 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
 <u><br></u>

@@ Line 14: / Line 14: @@
 == Overview  ==
-'''Creating a connection using EDI''
+''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
+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
-<br>
+<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.
+'''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 the 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 the only the required data is '''Pulled''' back eg POS / Sales Transactions
-Source vs Destination
+'''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 <br>From the Main Menu Select Utilities – Preferences <br>Select EDI and Integration and Scroll down to the Site Integration header<br>Tick the Site Integration Enabled check box and the select the desired Logging Level
+<br>'''Site Integration '''
-Site Integration Config<br>Select the Add button to set up a new Integration Site Configuration <br>Select the Setup button which loads an information screen with the following set up recommendations
+From the Main Menu Select '''Utilities – Preferences '''<br>Select'''EDI and Integration''' and Scroll down to the '''Site Integration''' header<br>'''Tick''' the '''Site Integration Enabled''' check box and the select the desired Logging Level
-Fill out the Destination field with the following<br>URL – URL of your Destination server eg https://localhost:446<br>Database – ERP Database name that changes will be written to 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
+'''Site Integration Config'''
-<br>
+'''<br>Select the Add button to set up a new '''Integration Site Configuration <br>Select the '''Setup''' button which loads an information screen with the following set up recommendations
-<br>
+. Turn off '''Two Way Synch'''<br>2. From Head Office select '''POS''' and set time to '''5 mins'''<br>3. From the Remote Site select '''Product''' and set time to '''8 hours'''
 <br>

← Older revision		Revision as of 05:19, 20 August 2012
Line 16:		Line 16:
	'''Creating a connection using EDI''		'''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	+	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
		+
		+	<br>
		+
		+	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 the 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)
		+
		+	<br>Site Integration <br>From the Main Menu Select Utilities – Preferences <br>Select EDI and Integration and Scroll down to the Site Integration header<br>Tick the Site Integration Enabled check box and the select the desired Logging Level
		+
		+	Site Integration Config<br>Select the Add button to set up a new Integration Site Configuration <br>Select the Setup button which loads an information screen with the following set up recommendations
		+
		+	1. Turn off Two Way Synch<br>2. From Head Office select POS and set time to 5 mins<br>3. From the remote site select Product and set time to 8 hours
		+
		+	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
		+
		+	Fill out the Destination field with the following<br>URL – URL of your Destination server eg https://localhost:446<br>Database – ERP Database name that changes will be written to 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>
		+
		+	<br>
		+
		+	<br>

@@ Line 1: / Line 1: @@
-<menu align="center" name="myMenu">
+<menu name="myMenu" align="center">
 More Detail=
 [[Audit Trail List]]
@@ Line 16: / Line 16: @@
 '''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 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