Googly
Member
My company's JDE servers are located in USA and most of the transactions are done from Mexico-Office. Does this have latency when doing the data transfers? Please clarify!
Zoltan_Gyimesi
Legendary Poster
Hi Venkat,
Your issue is cloudy and not clear at all.
Would you be so kind to clarify and provide us with enough info about your scenario, making possible for us to help you.
Waiting for clarification & Regards,
Zoltán
Your issue is cloudy and not clear at all.
Would you be so kind to clarify and provide us with enough info about your scenario, making possible for us to help you.
Waiting for clarification & Regards,
Zoltán
Chan Rana
Legendary Poster
Are you talking of disk latency?? We are not as good as you to understand what the issue is so you need to give more info as said by Zoltan.
Chan
Chan
DBohner-(db)
Legendary Poster
Yes and NO....
There is the latency of the network. If you are on web clients (8.11 and newer), all transactions will actually occur on the server (in the US, not in Mexico) - so you wouldn't have any true 'latency' issues (where someone else's transaction is committed between the time you start and complete yours).
Additionally, EnterpriseOne is an SQL based system. On legacy systems, each record and/or field could be read or written individually. On an SQL system - the entire transaction is, in most cases, committed as a whole. This protects data integrity where a partial transaction is written, interrupted, then completed.
If you can be more clear as to which latency you are concerned - we can better explain the concept and/or process. Additionally - if you include the system/configuration in your footer (part of your profile setup) - we can target individual system inadequacies.
(db)
There is the latency of the network. If you are on web clients (8.11 and newer), all transactions will actually occur on the server (in the US, not in Mexico) - so you wouldn't have any true 'latency' issues (where someone else's transaction is committed between the time you start and complete yours).
Additionally, EnterpriseOne is an SQL based system. On legacy systems, each record and/or field could be read or written individually. On an SQL system - the entire transaction is, in most cases, committed as a whole. This protects data integrity where a partial transaction is written, interrupted, then completed.
If you can be more clear as to which latency you are concerned - we can better explain the concept and/or process. Additionally - if you include the system/configuration in your footer (part of your profile setup) - we can target individual system inadequacies.
(db)
