[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Verisign PayFlowPro Installation on Raq 4i
- Subject: [cobalt-users] Verisign PayFlowPro Installation on Raq 4i
- From: "Troy Arnold" <cobalt@xxxxxxxxxxxxxx>
- Date: Tue Dec 17 03:43:01 2002
- Organization: websetters, inc.
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
We are nearly there with the Verisign PayFlowPro installation. The app is
testing out properly I am having a bit of trouble with the Perl example they
bundled and have questions pertaining to that below. But first I thought I
would submit the steps I took to get the payment service installed and
functioning properly. A small contribution (hopefully) back to the
community.
Verisign PayFlowPro Payment Service Installation on a slightly modified
Cobalt Raq4i
Introduction:
The aim of this document is to explain what was necessary for me to get
VeriSign/PayFlowPro set up as my payment gateway. At the time of this
writing, I was using our custom developed gateway interface and the Payflow
Pro SDK version 3.00
Getting / Installing Payflo Pro SDK
After getting your Payflo Pro account set up, log in to your account at
https://manager.verisign.com. Click the link towards the top of your screen
that says download.
Under the section labeled Payflow Pro Software Development Kit (SDK), will
be a link for your operating system. I used the Linux version. Once you have
downloaded the software, uncompress it. I uncompressed the file in
/usr/local directory. You should now have a new subdirectory named
verisign.
I changed directory to /usr/local/verisign/payflowpro/linux/lib. The file
libpfpro.so needs to be copied into one of your system library paths, or you
need to modify your LD_LIBRARY_CONF environment variable to include the
directory that you want to store this file.
I chose to copy libpfpro.so into /usr/local/lib/. In order to do this though
I had to become root. If you do not have root access to the machine, you
will need to use the LD_LIBRARY_CONF method of making this library visible
to the system.
To accomplish this I performed the following.
>cp /your/path/verisign/payflowpro/linux/lib/libpfpro.so /usr/local/lib
>pico /etc/ld.so.conf
Add the following line at the bottom:
/usr/local/lib
Once you have moved that file you will need to run ldconfig to make sure the
system can see the new library.
Save the files and reload the libs:
>/sbin/ldconfig
Okay so after I did this I realized you could simply cp the file to the
/usr/lib but this seemed safer. Comments?
Now we need to add the Verisign cert path to the environmental variables.
>pico /etc/profile
Insert the following at the end of the file...
PFPRO_CERT_PATH=/usr/local/verisign/payflowpro/linux/certs
export PFPRO_CERT_PATH
Upon restarting services the path was then listed by the ENV or PRINTENV
command which can be run to verify that the variable is now set correctly.
A good way to test that this is all properly set up is to change your
present directory to /your/path/verisign/payflowpro/linux/bin/ and run
./pfpro
If you get an error that says something like it couldn't load a .so file,
then you need to make sure that the payflow library is visible.
Next, edit the test.sh file located in the same bin directory so that it
contains your information for the USER,PARTNER,
PWD, and VENDOR variables. Once you have done that, run the program. The
output should resemble this:
you@localhost:~/verisign/payflowpro/linux/bin$ ./test.sh
----------------------------------------------------
***> Performing 'pfpro' binary test transaction.....
RESULT=0&PNREF=V28A02586876&RESPMSG=Approved&AUTHCODE=874PNI&AVSADDR=X&AVSZI
P=X
Done with 'pfpro' binary test transaction...
---------------------------------------------------
Now I moved to installing the Perl API's as we are unsure whether we will be
using xml, java or perl.
The Perl client has been designed to run on both Unix and NT platforms. You
must have set the environment variable PFPRO_CERT_PATH as listed above
before continuing.
Assuming your perl is setup correctly, and the Payflow Pro Client is
installed, do the following:
>perl Makefile.PL
>make
>make test
>make install
If you receive the following message, it means the Payflow Pro Client was
not able to be copied from the ../lib directory to a new lib subdirectory:
Warning: the following files are missing in your kit:
lib/libpfpro.a
lib/pfpro.h
Next I copied the /your/path/verisign/payflowpro/linux/perl/examples/cgidemo
folder to a web accessible directory and began changing parameters within
the signiodemo.cgi file. Made a few 755 permissions changes and we are
starting to test.
So that is where we are at. Everything is functional, simply working the
bugs on their example systems to integrate into our own custom app. The
problem I started this email off with follows:
Unfortunately when I ran their example perl forms I received an error:
Error 405 Method not allowed
The requested method POST is not allowed for the URL
/cgi-bin/cgidemo/billing.html
I think their demo is posting to the html and that I need to add ScriptAlias
or Alias to the srm.conf file. Anyone have any comments on this. Any input
on the proper code and location? is it the admsrv/conf/httpd.conf file that
I should edit?
Hope that most of this document helps someone out there and look forward to
the feedback on posting to html docs. The step-by-step methods listed above
are in no way guaranteed to function properly on your system. I am simply
forwarding the results of my experience. So if it screws you up I am
absolved of all responsibility.
Best regards,
Troy Arnold
websetters, inc.