installing CFX_PayFlowPro on JRun4/cfmx

[ssidelko]

i've been trying to install the cfx_PayFlowPro on a linux box running Jrun4
that has CFMX 6.1 with no luck so far.

since the instructions for the cfx tag say to go into the cf admin and modify
the JVM path to include where the Verisign.jar file is located, and made sure
the path to that dir also exists.

the folder i have them in is
/opt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib

the string from jvm.config is

# JVM classpath

java.class.path={application.home}/servers/lib,{application.home}/servers/cfusio
n/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/cfusion.jar,{application.home}/ser
vers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib,{application.home}/lib/
jrun.jar,{application.home}/lib,{application.home}/servers/cfusion/cfusion-ear/c
fusion-war/WEB-INF/cfusion/lib/Verisign.jar

the cfx is registered as

tag name: CFX_PAYFLOWPRO
class name: CFXPayFlowPro
desc: CFXPayFlowPro

the box has been restarted a few times, and no luck thus far.

i just got the JMC password, so i'm going to see if i can find that to see if
there is any settings in there that might help. besides that i'm running out
of ideas because i've searched the web pretty heavily and haven't found anyone
else with this problem trying to install a cfx tag in a jrun4 environment.

Thanks in advance

Sean

[websaws]

We had the same problem on a Windows 2000 box. Here's how we solved it:

Turns out the VeriSign documentation is dead-wrong about what needs to be in
the classpath. (I figured this out by systematically removing each classpath
entry from jvm.config and restarting the cfusion service each time to see if it
worked.)

The key is to NOT have Verisign.jar specified in the classpath; only the path
to the correct FOLDER should be specified, WITHOUT the file name:

Incorrect:
{application.home}/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/V
erisign.jar

Correct:
{application.home}/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib

(Why cfusion.jar and jrun.jar work with their file names in the classpath is
beyond me. But trust me on this one.)

I also learned that any other Java cfx tag .jar files need to be in the same
folder as Verisign.jar or else there may be conflicts. It doesn't matter where
you put them, as long as they're all in the same place, and in a folder
specified in the classpath.

Another important tip: DO NOT use the JRun JMC to change the classpaths. There
seems to be a bug in the JMC that corrupts the jvm.config file. (Adds extra
carriage returns maybe?) Better to edit the file in Notepad.

Also remember that the same jvm.config is used by all your cf server
instances. So make sure any changes you make will work across all server
instances on that box.

Hope that helps!

[rave]

RE: Another important tip: DO NOT use the JRun JMC to change the classpaths.
There seems to be a bug in the JMC that corrupts the jvm.config file

This is bug 53429 as detailed in
[url]http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_19094[/url]

Regards,

David.