Re: Witango-Talk: Verisign Bean and others

Wed, 10 May 2006 09:29:39 -0700

Yes, I was trying to find that too. I was looking for the server to send the xml too, and how the http request needed to be formatted, and I couldn't find it.

Here is my witango code to use the bean, its a simple method, that should work with any payflow pro account:

<@! first instantiate or check that the bean is instantiated in a custom scope, so it is global >

<@if "<@var bighead$pfprobean type=text> contains 'Object'">
<@else>
<@assign bighead$pfprobean '<@CREATEOBJECT OBJECTID="PFProJava" TYPE="JavaBean">'>
</@if>

<@! then the method >
<@assign local$parmList "YOUR PARM LIST GOES HERE">
<@comment>
The authorize method takes 4 String parameters. ints and booleans cause witango to crash.
parmList as string, istest as string (0=live, 1=test), certpath as string (should be absolute path, network path UNC works), and timeout as string
</@comment>
<@assign local$res <@callmethod bighead$pfprobean method="authorize('<@var local$parmList>','1','c:\pathtocertsfolder','30')">>

If istest param, is 0, then the request goes to: payflow.verisign.com else, if 1, it goes to: test-payflow.verisign.com

Your parmList has your login and all in it, and you can specify timeout.

I didn't specify port 443, cuz it should always be that, but i could in future. Also, you MUST specify the path to the folder that contains the "f73e89fd.0" file.

The method returns the standard urlencoded form list, but I added 3 values on end:

return rc+"&HOST="+HostAddress+"&ISTEST="+istest+"&TIMEOUT="+timeout;

This just allows you to verify that the parameters you passed in, were received and parsed correctly.

Thats it. I have a bunch of stuff going on this morning, and a couple meetings, but I will post the bean and the test taf, by the end of the day, with source. I didn't incorporate proxy support in the bean, but it would be simple to fix and recompile.

-- 

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040

On May 10, 2006, at 8:50 AM, Robert Shubert wrote:

Well, your question prompted me to look over the documentation and see what’s what. It turns out that even if you prepare an XML transaction, payflow still expects you to use one of their SDKs to submit it too them. This means that I can’t seem to find a way to do a straight http post to them outside of their software. That said, I’ll have to turn my attention back to one of the other methods. If COM doesn’t work, and external EXE is a little iffy, I guess that taking a look at your bean would be next. Can I assume that the bean would just take an already constructed parameter string, pass it to payflow and then make the result available? Thanks for your efforts on this. Robert

 

From: Robert Garcia [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 10, 2006 11:25 AM
To: [email protected]
Subject: Re: Witango-Talk: Verisign Bean and others

 

Have you tested <@URL with the xml spec yet? I have found it is not flexible enough for special types of posts, like this one maybe. You may have to set headers, etc.

 

I am sure I can find some java code that I can use as a framework. Let me know if your test works.

 

I will posting the verisign bean, and the magick bean, in the next day or two.

 

It went into production today, once you resolve what doesn't work, and don't use in the studio, the beans just work, and don't fail.

 

I even tested the beans against the witango dll sample, and made a simple dll. The bean was just as fast, if it was already instantiated in memory as an object.

 

--

 

Robert Garcia

President - BigHead Technology

VP Application Development - eventpix.com

13653 West Park Dr

Magalia, Ca 95954

ph: 530.645.4040 x222 fax: 530.645.4040

 

On May 9, 2006, at 12:45 PM, Robert Shubert wrote:



I have not yet started construction on my new method, but I am anticipating
to use the XML structure along with Witango's built-in @URL to do the
communication. If that should fail me, I'll probably fall back to that built
in object (winhttp 5.1 I think?).

 

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf



________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to