Setting Up Servlets on an Oracle Web Server

New instructions added, version 7.5.3, 8.1, 7.5.4 Patches, 8.4 Patches

 

Some servlet setup must be completed on the Oracle Web Server for the following functions in NDS Applications.

For application servers other than Oracle 9i AS, please consult the appropriate documentation or contact NDS support for further assistance.

 

 

NDS Mail Servlet

1. Create a directory within your NDS Home Directory called jserv. For example: C:\nds\jserv.

2. Extract all files in the jserv.zip into this directory.

3. Modify the .properties files to reflect the name of the directory, if needed.

4. Modify C:\Oracle\iSuites\Apache\Jserv\conf\jserv.conf.

5. Find the line: # Mount point for servlet zones.

6. Add the servlets that you need:

#ApJServMount /ndsmail /ndsmail

 

7. Modify C:\Oracle\iSuites\Apache\Jserv\conf\jserv.properties

8. Find the Zones section, and choose the servlets that you need. It should look something like this:

# Servlet Zones parameters
###########################

# List of servlet zones Apache JServ manages
# Syntax: zones=[servlet zone],[servlet zone]... (Comma separated list of String)
# Default: NONE
#zones=root,ndsmail
zones=root

# Configuration file for each servlet zone (one per servlet zone)
# Syntax: [servlet zone name as on the zones list].properties=[full path to configFile] (String)
# Default: NONE
# Note: if the file could not be opened, try using absolute paths.
root.properties=C:\ORACLE\iSuites\Apache\Jserv\servlets\zone.properties

 

9. At the end of the file, choose the servlets that you need. It should look something like this:

#NDS Servlet
wrapper.classpath=C:\ORACLE\806\forms60\java\f60srv.jar
wrapper.path=C:\ORACLE\iSuites\bin;C:\ORACLE\806\bin

#NDS mail
#ndsmail.properties=c:\nds\jserv\ndsmail.properties
#wrapper.classpath=c:\nds\jserv\activation.jar
#wrapper.classpath=c:\nds\jserv\mail.jar

#wrapper.classpath=c:\nds\jserv\crimson.jar
#These next files are the Oracle provided jdbc drivers
#for the database/jvm combination you are using. Ask us for the files.
#wrapper.classpath=c:\nds\jserv\classes12.zip
#wrapper.classpath=c:\nds\jserv\nls_charset12.zip
#wrapper.classpath=c:\nds\jserv\ocrs12.zip

 

10. Restart the Apache server.

11. Once the application server starts, the necessary servlet is available.

12 Set up the MURM, Initialization Parameter Maintenance, entries for Email and Fax setup

 

Payflow Pro Payment Processing

The NDS - Payflow Pro Gateway is supersedes the NDS - Verisign Gateway for credit card processing. As of September 1, 2009, all users of the NDS - Verisign Gateway desiring to continue to process credit cards using Payflow Pro should upgrade to the NDS - Payflow Pro Gateway.

The NDS - Payflow Pro Gateway is distributed as a single WAR file for deployment on a modern java based application server. It is not compatible with the application server provided with Xephr. We recommend using the Apache Tomcat 6 application server for deploying this product.

 

Windows Installation

1. Install Sun's Java 6 JDK from java.sun.com.

2. Add the path to the Java JDK's bin directory to your system path. To do this:

3. Obtain and Install the latest version of Tomcat 6 from http://tomcat.apache.org/download-60.cgi. Be sure to install the "Windows Service Installer" to ensure that Apache is installed as a service.

4. During installation of Tomcat, you will be asked for the location of your JRE, you MUST ensure that you have selected the appropriate directory supplied with the JDK (usually something like "C:\Program Files\Java\jdk1.6.0_15\jre").

5. Tomcat normally listens on port 8080. This can be changed during the installation.

6. When the installation is complete, you should ensure that "Run Tomcat" is checked.

7. Launch the browser of your choice and go to http://localhost:8080 and ensure that you see the Tomcat welcome page.

8. Copy the payflowpro.war file to the Tomcat "webapps" directory.

9. Once this is done, you should be able to go to http://localhost:8080/payflowpro and verify that the new code is installed and working.

10. Update the properties file to shift it to production mode. This will require Tomcat to be restarted.

11. The WAR file automatically creates a payflowpro.properties file when it is first requested.

12. Set up the MURM, Initialization Parameter Maintenance, entries for Payflow Pro Payment Processing in the Payflow Pro Variable Setup section.