Initially we tried to use uConnector but our friends told it was not officially completed hence suggested to try alternate methods. Since the program we are building is going to exist on the server as a separate program like a windows service or console application, we are trying to use the database directly and take the values from the tables created for uCommerce.
Our umbraco version is 4.9.0 and uCommerce is 3.0.0.12320
We would like to know whether we are in the right direction or if there are any alternate suggestions from your side to make this solution better.
I cannot only give an answer on behalf of myself and my experiance :)
I've seen quite a few times where uCommerce were run in an console application because the customers wanted some jobs done on an daily schedule. One of these jobs could easy be some logic exporting Orders as XML. It is not a bad solution. Actually.
However it is not for uCommerce 3.0, but the basics are the same. Lifecycles on objects configured in the DI configs are removed, so it should actually be a little easier :)
AN ALTERNATIVE SOLUTION:
I've also done another similar solution. That was creating a view with relevant data for use directly in a pivot table in Excel which is very easy to setup. It would automatically give you a huge set of options for filtering. So that would be nice to take that into consideration also :)
Exporting Orders as XML on separate scheduled program
Initially we tried to use uConnector but our friends told it was not officially completed hence suggested to try alternate methods. Since the program we are building is going to exist on the server as a separate program like a windows service or console application, we are trying to use the database directly and take the values from the tables created for uCommerce.
Our umbraco version is 4.9.0 and uCommerce is 3.0.0.12320
We would like to know whether we are in the right direction or if there are any alternate suggestions from your side to make this solution better.
I cannot only give an answer on behalf of myself and my experiance :)
I've seen quite a few times where uCommerce were run in an console application because the customers wanted some jobs done on an daily schedule. One of these jobs could easy be some logic exporting Orders as XML. It is not a bad solution. Actually.
I don't think there's a better solution than what you suggested for doing so. Soren himself has a guide on how to do it; http://www.publicvoid.dk/EnableTheUCommerceEcommerceAPIOutsideTheWebContext.aspx
However it is not for uCommerce 3.0, but the basics are the same. Lifecycles on objects configured in the DI configs are removed, so it should actually be a little easier :)
AN ALTERNATIVE SOLUTION:
I've also done another similar solution. That was creating a view with relevant data for use directly in a pivot table in Excel which is very easy to setup. It would automatically give you a huge set of options for filtering. So that would be nice to take that into consideration also :)
Hope that was an usefull answer :)
is working on a reply...