Third Party Shopping Cart - ELF2 Logs - Urchin Integration(repost)

We currently use [[login to view URL]][1] (SNS) shopping cart solution to handle our shopping cart needs for our [[login to view URL]][2] website. Our website pages are hosted on a GoDaddy dedicated Redhat server along with Urchin 5.7.03. We have been using Urchin successfully for almost two years, but we have never setup the ELF2 log processing and integration with our shopping cart. Unfortunately, SNS doesn't have a ELF2 log export that we can setup the Urchin software to access. They do, however, have the ability to post several variables, including all of the order transaction data for each order, to a CGI that can receive the variables and build a local ELF2 log file which Urchin can access locally. The CGI is 98% complete already and is written in PERL. The 2% that is incomplete is only related to arranging the data in the ELF2 log file to match the very specific layout and arrangement that Urchin requires. Additionally, we would like to setup the UTM sensor on all of the shopping cart pages, which are hosted on SNS and are on https pages. We will purchase a security certificate if necessary, but it would need to be setup on our server for us. The reason we believe we need a security certificate is so that when a visitor is on the SNS https shopping cart pages and the [login to view URL] image is accessed across https, we don't want to see the security warning. SNS does allows custom HTML to be entered on each individual shopping cart page. Most importantly, we would like for a visitor's previous visits to be associated with a purchase if they decidie to finally purchase one of our products. I understand that the UTM sensor, which is already installed on all of our regular web pages, and the ELF2 log processing, this can call be accomplished. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Redhat Linux/Unix