anthill
New Member
Hello,
I am completely new to the technical aspects of Progress/OE and I think first steps is to have someone help me understand the overview of what I'm dealing with.
Here are the specifics... I have been tasked with figuring out how to manage the first 2 parts of a 3-part system. Each part is a separate server: Web shopping cart (PHP) -> Order API (PHP) -> Progress DB (11.3).
A few years ago we rebuilt the shopping cart for the client (in PHP). The shopping cart submits orders to an API (also PHP), the API submits orders to Progress (11.3 on RHEL 5.10 (no, that's not a typo)). The products are digital and are delivered automatically by Progress.
When we rebuilt the shopping cart we had a copy of the previous cart and it included the PHP scripts to submit orders to the API. At the time we had no insight into how the API worked, we simply integrated the existing code into the new cart. The cart has been working fine since we launched it a couple of years ago.
The client now wants to retire the API server and has asked us to integrate the API functionality into the cart (there is no need for a separate API at this time). We now have access to the API server so we understand the workings, but what we don't have are the ODBC drivers to connect directly to Progress (these are compiled on the existing API server so we can't simply copy them).
My specific goal (first priority) is to get some assistance to install the correct drivers on a development server so that we can test the proof of concept that we can submit orders directly to Progress (we have the POC ready, but can't connect to Progress). But, in the interests of understanding the "big picture" of what we're dealing with, I'd like a better understanding of the Progress backend... i.e. We find the names "Progress" and "OpenEdge" confusing (it seems the Progress platform name was changed to OpenEdge in 2014?), when looking for drivers we were unsure if we should be looking for Progress or OE, and what are the consequences for a client still running 11.3?
I'm happy to take any recommended reading links to answer the "big picture" questions, and I'll do my homework. But considering the very general nature of my initial questions, this might be better done as a phone call discussion, and I'm more than willing to consider this a paid consulting gig and happy to pay for a couple of hours to get some of these concepts through my thick skull.
And, as far as I'm aware, the client could be flying blind on their Progress platform... which means, as soon as the API functionality is integrated into the shopping cart the client may want the Progress server updated, maintained, etc. This would be a good opportunity to get prepared for (facilitate?) that possibility... we'd need a Progress expert(s) to manage that.
Thank you for your consideration.
Daniel.
I am completely new to the technical aspects of Progress/OE and I think first steps is to have someone help me understand the overview of what I'm dealing with.
Here are the specifics... I have been tasked with figuring out how to manage the first 2 parts of a 3-part system. Each part is a separate server: Web shopping cart (PHP) -> Order API (PHP) -> Progress DB (11.3).
A few years ago we rebuilt the shopping cart for the client (in PHP). The shopping cart submits orders to an API (also PHP), the API submits orders to Progress (11.3 on RHEL 5.10 (no, that's not a typo)). The products are digital and are delivered automatically by Progress.
When we rebuilt the shopping cart we had a copy of the previous cart and it included the PHP scripts to submit orders to the API. At the time we had no insight into how the API worked, we simply integrated the existing code into the new cart. The cart has been working fine since we launched it a couple of years ago.
The client now wants to retire the API server and has asked us to integrate the API functionality into the cart (there is no need for a separate API at this time). We now have access to the API server so we understand the workings, but what we don't have are the ODBC drivers to connect directly to Progress (these are compiled on the existing API server so we can't simply copy them).
My specific goal (first priority) is to get some assistance to install the correct drivers on a development server so that we can test the proof of concept that we can submit orders directly to Progress (we have the POC ready, but can't connect to Progress). But, in the interests of understanding the "big picture" of what we're dealing with, I'd like a better understanding of the Progress backend... i.e. We find the names "Progress" and "OpenEdge" confusing (it seems the Progress platform name was changed to OpenEdge in 2014?), when looking for drivers we were unsure if we should be looking for Progress or OE, and what are the consequences for a client still running 11.3?
I'm happy to take any recommended reading links to answer the "big picture" questions, and I'll do my homework. But considering the very general nature of my initial questions, this might be better done as a phone call discussion, and I'm more than willing to consider this a paid consulting gig and happy to pay for a couple of hours to get some of these concepts through my thick skull.
And, as far as I'm aware, the client could be flying blind on their Progress platform... which means, as soon as the API functionality is integrated into the shopping cart the client may want the Progress server updated, maintained, etc. This would be a good opportunity to get prepared for (facilitate?) that possibility... we'd need a Progress expert(s) to manage that.
Thank you for your consideration.
Daniel.