Fwd: payflowpro broken on WebDNA 5.1?

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 54430
interpreted = N
texte = Hi all, I'm finally trying to upgrade our main ecommerce server to 5.1 on our new Dual 2Ghz G5 running OSX 10.3.1, but I'm having problems getting the Verisign Payflow Pro module to function properly. I fixed several configuration errors in the default install that entirely prevent Payflow from having a remote chance of functioning at all (I'll detail these in a separate email). After several hours of tweaking prefs, soft links, and templates, I'm confident that everything is now configured identically to our fully functioning 4.5.1 installation. When running the ProcessOrders.tpl template, the LastPayflorProHit.txt file is updated to contain: OHS:

Error:Java not initialized.

I isolated the OBJECT tag from this template on a test page with all the parameters hard-coded, and I still receive the same error message - Java not initialized. I'm able to run the command line javatest.pl script successfully (i.e. I get a valid reply from the Verisign test server), so I know that there's nothing wrong with the new java vm (1.4.1) talking to Verisign's java app or the verisign website via ssl. The hack we're using to get around this problem is a modified version of javatest.pl called with [SHELL] from the ProcessOrders.tpl page, but it's far from ideal. As another test I copied my WC451 directories and config from our production server onto this box and was able to process a test order through ProcessOrders.tpl without any problems. This points more toward a problem with Webcat 5.1 than with OSX 10.3 (in my mind, at least). I haven't tried WC5.1e and PayflowPro on a 10.2 machine yet. My desktop and home machines are already running 10.3 and I'm not going back! :) Questions: Is anyone using Verisign Payflow and Webcat 5? If so, are you also using Panther (10.3)? If you're still running 10.2, do you have the Java 1.4 update installed? My conclusion is that there appears to be a bug in the [OBJECT] tag in 5.1 (5.1c & e) that fails to initialize Java on OSX 10.3.1. If anyone else has evidence to the contrary, please let me know. Thanks, Dale ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Fwd: payflowpro broken on WebDNA 5.1? ( Dale LaFountain 2003)
Hi all, I'm finally trying to upgrade our main ecommerce server to 5.1 on our new Dual 2Ghz G5 running OSX 10.3.1, but I'm having problems getting the Verisign Payflow Pro module to function properly. I fixed several configuration errors in the default install that entirely prevent Payflow from having a remote chance of functioning at all (I'll detail these in a separate email). After several hours of tweaking prefs, soft links, and templates, I'm confident that everything is now configured identically to our fully functioning 4.5.1 installation. When running the ProcessOrders.tpl template, the LastPayflorProHit.txt file is updated to contain: OHS:

Error:Java not initialized.

I isolated the OBJECT tag from this template on a test page with all the parameters hard-coded, and I still receive the same error message - Java not initialized. I'm able to run the command line javatest.pl script successfully (i.e. I get a valid reply from the Verisign test server), so I know that there's nothing wrong with the new java vm (1.4.1) talking to Verisign's java app or the verisign website via ssl. The hack we're using to get around this problem is a modified version of javatest.pl called with [shell] from the ProcessOrders.tpl page, but it's far from ideal. As another test I copied my WC451 directories and config from our production server onto this box and was able to process a test order through ProcessOrders.tpl without any problems. This points more toward a problem with Webcat 5.1 than with OSX 10.3 (in my mind, at least). I haven't tried WC5.1e and PayflowPro on a 10.2 machine yet. My desktop and home machines are already running 10.3 and I'm not going back! :) Questions: Is anyone using Verisign Payflow and Webcat 5? If so, are you also using Panther (10.3)? If you're still running 10.2, do you have the Java 1.4 update installed? My conclusion is that there appears to be a bug in the [object] tag in 5.1 (5.1c & e) that fails to initialize Java on OSX 10.3.1. If anyone else has evidence to the contrary, please let me know. Thanks, Dale ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Dale LaFountain

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Forms Search Questions (1997) two unique banners on one page (1997) Comments in db? (1997) Active Server Code... (1998) splitting numbers in webDNA? (1997) Integration? (1999) Using [random] (1999) 4.0.x find (2000) [WebDNA] Random Numbers no repeat within a range (2014) PCS Emailer's role ? (1997) Encrypted items in DB (2001) Recursion & WebDNA (1999) Sku numbers (1997) Country & Ship-to address & other fields ? (1997) Web Logs (1998) Random sort is not random at all..... (2000) Can't Update records (1997) Protect vs Authenicate (1997) Large databases in WebCat (1997) hiding return characters (2000)