Hello all,
Here is my situation. We have an IBM AS400 system which contains mainly COBOL applications from years back. Many of our essential systems run on the AS400 and we are destined to be using it for the foreseeable future.
We recently purchased Great Plains (7.5) and I've been doing a lot of integrations from AS400 to GP through Integration Manager. The main problem I have with Integration Manager is that is pretty much is a one-way street: Into Great Plains. As it stands now my company is going to be pushing both ways. In short, I need a way to sync our data both ways and I'd like avoid it being a manual process. I was looking at eConnect because it appears that this is what it does, but I've gotten a little confused on the details.
Questions:
1). Does eConnect run both ways?
a) Some documentation on it claims:
eConnect supports integration BETWEEN data from other applications and your Microsoft Great Plains application, enabling high volume and high speed in back-office transactions. Data can be pushed INTO Microsoft Great Plains from diverse application types such as Web storefronts, Web services, LEGACY APPLICATIONS, customer relationship management applications, and point-of-sale applications.
b) From the document it appears to only run one-way (no better than Integration Manager).
2). Is this (in general) how the application works?
a) You have Table.A on AS400 legacy system and Table.B on Great Plains.
b) It monitors each database it is instructed to for changes. When something changes in Table.A it writes a record of that in XML and then, using specifications, makes changes in Table.B
3). BizTalk is almost always mentioned in the same sentence as eConnect in most of the documentation I've read.
a) Is BizTalk an add-on to eConnect?
b) Do I need BizTalk to have eConnect 'talk back' to the As400?
As you can see I'm not exactly an expert on SQL or Great Plains, but I'm hoping that I'll be able to use eConnect to 'link' tables in Great Plains to my As400 system (which, of course stores information in wildly different formats from Great Plains). Thank you in advance for your input.
Ivan
Here is my situation. We have an IBM AS400 system which contains mainly COBOL applications from years back. Many of our essential systems run on the AS400 and we are destined to be using it for the foreseeable future.
We recently purchased Great Plains (7.5) and I've been doing a lot of integrations from AS400 to GP through Integration Manager. The main problem I have with Integration Manager is that is pretty much is a one-way street: Into Great Plains. As it stands now my company is going to be pushing both ways. In short, I need a way to sync our data both ways and I'd like avoid it being a manual process. I was looking at eConnect because it appears that this is what it does, but I've gotten a little confused on the details.
Questions:
1). Does eConnect run both ways?
a) Some documentation on it claims:
eConnect supports integration BETWEEN data from other applications and your Microsoft Great Plains application, enabling high volume and high speed in back-office transactions. Data can be pushed INTO Microsoft Great Plains from diverse application types such as Web storefronts, Web services, LEGACY APPLICATIONS, customer relationship management applications, and point-of-sale applications.
b) From the document it appears to only run one-way (no better than Integration Manager).
2). Is this (in general) how the application works?
a) You have Table.A on AS400 legacy system and Table.B on Great Plains.
b) It monitors each database it is instructed to for changes. When something changes in Table.A it writes a record of that in XML and then, using specifications, makes changes in Table.B
3). BizTalk is almost always mentioned in the same sentence as eConnect in most of the documentation I've read.
a) Is BizTalk an add-on to eConnect?
b) Do I need BizTalk to have eConnect 'talk back' to the As400?
As you can see I'm not exactly an expert on SQL or Great Plains, but I'm hoping that I'll be able to use eConnect to 'link' tables in Great Plains to my As400 system (which, of course stores information in wildly different formats from Great Plains). Thank you in advance for your input.
Ivan