Installing
Web Credit Card BofA 2.0
Contents
Introduction
Web Credit Card BofA is an application
that allows students to pay for tuition and fees with their credit card
number over the Web. Credit card transactions are processed through a service
provided by the Bank of America (BofA). Web Credit Card BofA will display
and accept payment for outstanding charges for a student by quarter or in
total. This document describes how to install Web Credit Card BofA, release
2.0.
Top
of page
Special
Considerations
Web Credit Card BOA is dependent
on the following:
- The CIS Web Transaction
Server must be installed.
- A secure Web server is
required; get a certificate before implementation.
- Perl must be installed
on the Web server.
- A merchant account relationship
with Bank of America is required.
- Your
authorization portal must be set up using the Bank of America Administrative
functions.
Top
of page
Gather
Required Information
Before you begin this procedure,
you must gather some information about your Web server and have your Bank
of America merchant account number.
During the installation, you
may be asked to provide the following information:
Server Installation Type
The type of Web server that
you are installing Web Credit Card on.
Options include:
- An NT server located on
your campus
- A Unix server located
on your campus
- The CTC server located
at the CIS
College Code
Your three-digit college code
Domain Name Server
The domain name of your Web
server, for example, www.yourcollege.ctc.edu
Application URL
The URL for locating the Web
Credit Card HTML files by the Web address, for example, www.yourcollege.ctc.edu/wts/wccba
Index Page
The name of the HTML file
that is displayed when users select the Web Credit Card Return
To Main link. Typically, this can be a menu or the
Web Credit Card login page, for example, index.html
Return URL
The URL that is associated
with the Web Credit Card Return To Main
link, for example, www.yourcollege.ctc.edu/wts/student
HTML File directory
The directory path that is
used by the operating system to locate the Web Credit Card HTML files,
for example:
- For Unix systems,
/directory/wts/wccba/
OR
- For NT systems, d:\\directory\\wts\\wccba\\
Web Registration Return
URL
The URL that is associated
with the Web Registration Return To Main
link, for example, www.yourcollege.ctc.edu/wts/webreg
Ccserver Location
The URL and name of the Web
Credit Card CGI program. This program resides in the CGI directory on
your Web server, for example:
- For most Unix systems, www.yourcollege.ctc.edu/cgi-bin/ccserver
OR
- For most NT systems, www.yourcollege.ctc.edu/scripts/ccservnt.exe
OR
- For most multi-district
colleges and colleges using the CTC Web server (where nnn
is your college code), www.yourcollege.ctc.edu/cgi-bin/ccnnn
Rqserver Location
The URL and name of the Web
Transaction Server CGI program. This program resides in the CGI directory
on your Web server, for example,
- For most Unix systems,
www.yourcollege.ctc.edu/cgi-bin/rqserver
OR
For NT most systems, www.yourcollege.ctc.edu/scripts/rqservnt.exe
OR
- For most multi-district
colleges and colleges using the CTC Web server (where nnn
is your college code), www.yourcollege.ctc.edu/cgi-bin/rqnnn
Merchant Identification
(Store ID)
The merchant account identification
from your Bank of America administrative login. The merchant identification
is also known as your Store ID.
Top
of page
Files
Included with this Release
The files included with this release
are:
| File Name |
Description |
| blue_dot.gif |
Image |
| clock6.gif |
Image |
| cookie.js |
Cookie Information |
| index.html |
Default menu. A copy of
the Credit Card Payment Login, waci600.html |
| install.html |
These installation instructions |
| lookie.js |
Script to get post data |
| waci223.html |
Web Registration, Process
Selection List |
| waci600.html |
Credit Card Payment Login |
| waci601.html |
Pass through Transaction
Amount |
| waci601.pl |
CGI program for gathering
Credit Card Information |
| waci601a.plh |
Frame for Card Information
screen |
| waci601b.plh |
Frame for requesting authorization |
| waci602b.html |
Call BofA - Please Wait |
| waci603b.html |
BofA Approved - Post to
CA |
| waci604.html |
Transaction Completed |
| waci605b.html |
Bank of America Transaction
Denied |
| waci606.html |
Data Entry Error |
| waci607.html |
Internal Error |
| waci608.html |
No Balance Due |
| waci609.html |
Credit Balance Due |
| waci610.html |
Posting Error |
| waci611h.html |
Help Documentation |
| wccba.cfg |
Installation Configuration
Template |
Note:
All files in this release are new or have been changed.
Top
of page
Installing
Web Credit Card
To install Web Credit Card, you
must:
- Install the files on the
server.
- Configure the HP 3000 to
run Web Credit Card.
Installing
Files on the Server
This section walks you through
the process of installing Web Credit Card on your campus's Web server.
If you are using the Unix server
"CTC" (located at CIS) to host your Web applications, steps
7, 8, and 9 will need to be performed by CIS staff. For assistance with
these steps, or any other portion of this installation, please contact
CIS Customer Support.
| 1. |
On
the CIS Web Site, go to the Web-Enabled Applications page at http://www.cis.ctc.edu/wctc/webapps/index.htm |
| 2. |
Under
the Web Credit Card BofA heading, click the WebCreditCard.exe
link and save the file on your PC. |
| 3. |
On
your PC using Windows Explorer, locate and open the downloaded file
WebCreditCardBofA.exe. When the
pre-installation program starts, answer the questions about your college's
Web server and your Bank of America merchant identification number.
The pre-installation program expands the Web Credit Card HTML, PLH,
PL, JS, GIF, and CFG files and customizes them for your college. |
| 4. |
On
your Web server, build a new directory to store the Web Credit Card
files.
If you currently have
Web Registration installed, the best position for this directory
is at the same level as the directory containing that application.
The recommended directory name is /wccba/
Verify that the permissions
on the directory are correct. At a minimum, they should allow Read
and Execute access for all viewers of the Web Credit Card pages.
|
| 5. |
On
your PC, locate the Web Credit Card installation directory. The default
installation directory is C:/Program Files/CIS/Web
Credit Card BofA |
| 6. |
Copy
all of the files (except install.html,
uninst.isu, waci601.pl,
and wccba.cfg) from the Web Credit Card
installation directory on your PC to the /wccba/
directory on your Web server. You can use any software that allows
you to copy files (for example, Windows Explorer or FTP).
- Copy the HTML, PLH,
and JS files to the /wccba/ directory
as ASCII.
- Copy the GIF files
to the /wccba/ directory as Binary.
Verify that the permissions
on the files are correct. At a minimum, they should allow Read and
Execute access for all viewers of the Web Credit Card pages. |
| 7. |
Copy
the file waci601.pl from the Web Credit
Card installation directory on your PC to the to the CGI directory
on your Web server and rename it to wacinnn.pl
( where nnn is your college code). Typically,
the CGI directory is named either /cgi-bin/
OR /scripts/ You can use any software
that allows you to copy files (for example, Windows Explorer or FTP).
- Copy the file waci601.pl
as ASCII to the CGI directory.
- In the CGI directory,
rename the file waci601.pl to wacinnn.pl
(where nnn is your college code).
Note: If you are using
the Unix server "CTC" to host your CIS Web applications,
you will need to contact CIS Customer Support to perform this step
for you. |
| 8. |
Since
the job ZX0800J, which runs on the HP 3000, processes requests from
a unique port on the Web Transaction Server, you will need to create
a new process for Web Credit Card called ccserver
to communicate with that port. In the CGI directory on your Web server,
create the new ccserver process by making
a copy of the rqserver process and saving
it under a new name.
Depending on your college,
the two files that make up the rqserver
process may be found under different names. Typically these files
can be located and copied as any of the following:
- In the /cgi-bin/
directory, copy the files rqserver
and rqserver.cfg and rename
them as ccserver and ccserver.cfg
OR
- In the /scripts/
directory, copy the files rqservnt.exe
and rqservnt.cfg and rename them as
ccservnt.exe and ccservnt.cfg
OR
- In the /cgi-bin/
directory, copy the files rqnnn and
rqnnn.cfg (where nnn
is your college code) and rename them as ccnnn
and ccnnn.cfg (where nnn
is your college code).
Note: If you you are
using the Unix server "CTC" to host your CIS Web applications,
you will need to contact CIS Customer Support to perform this step
for you. |
| 9. |
In
the CGI directory on your Web server, modify the ccserver
configuration file to specify the port number on the Web
server that will be used to process credit card authorization requests.
This port number must be the same as the port number you will specify
in the ZX0800S file (referenced in the section Configuring
the HP 3000 below). You may use any text editor to modify this
file. Depending on your college, this file is typically named either
ccserver.cfg or ccservnt.cfg
or ccnnn.cfg (where nnn
is your college code).
To select the port number,
you can usually increase the number that is currently in the file
by 1000. This is usually satisfactory as long as the new port number
is not being used by any other process, including any of the Web
Transaction Server process. For example, if the port number is 7000,
change it to 8000.
- Modify the line ManPort
to specify which port number on your Web server, for
example, ManPort 8000
Note: If you you are
using the Unix server "CTC" to host your CIS Web applications,
you will need to contact CIS Customer Support to perform this step
for you. |
Top
of page
Configuring
the HP 3000
This section walks you through
the process of configuring the HP 3000 for use with Web Credit Card BofA.
| 1. |
Log on to
your HP 3000 using a login to the Pnnn
account (where nnn is your college code).
To log on, you can use any terminal emulator (for example, Minisoft
or Reflection). |
| 2. |
Modify
the Web Transaction Server Configuration file ZX0710S.DATA.
In the file
ZX0710S.DATA, add the following configuration settings
for Web Credit Card. You can use any text editor to modify this
file (for example, Edit/3000). To easily find these new settings
later, you may want to group them with similar configuration settings.
Add the following lines:
- EnableCreditCard
1
This parameter enables
Web Credit Card.
- CreditCardBaseURL
http://www.yourcollege.ctc.edu/wts/directory/wccba/
This parameter identifies
the URL for Web Credit Card.
Replace the sample URL
with the URL for your site.
|
| 3. |
Modify
the Web Credit Card configuration file ZX0800S.DATA.
In the file ZX0800S.DATA,
change the following configuration settings for Web Credit Card.
You can use any text editor to modify this file.
- Modify the line containing
CGIHostName ctc.ctc.edu to specify
the name of your Web server, for example, www.everett.ctc.edu
- Modify the line containing
the ManPort value to specify the port
number on the Web server that will be used for processing credit
card authorization requests. This port number must correspond
to the port number specified in the ccserver
configuration file (referenced in the section Installing
Files on the Server, step 9 above), for example, ManPort
8000
- Modify the line containing
the AGPortArray value to specify the
ports on the HP 3000 that will be used for communication with
the credit card payment agents. Typically, this will be a series
of ports incremented by one, for example, AGPortArray
8001;8002;8003;8004
|
| 4. |
On
your HP 3000, start the Web Transaction Server Job (ZX0700J). This
will put your changes to the configuration file ZX0710S.DATA
into effect.
- If the ZX0700J job
is currently running, first stop it by scheduling the Web Transaction
Server Halt (ZX0730J) job. Then schedule ZX0700J to start again.
You can schedule both of these jobs with an Execution Time of
I (immediate).
|
| 5. |
On
your HP 3000, start the Web Credit Card Transaction Job (ZX0800J).
This will put your changes to the configuration file ZX0800S.DATA
into effect.
- If the ZX0800J job
is currently running, first stop it by scheduling the Web Credit
Card Transaction Halt (ZX0830J) job. Then schedule ZX0800J to
start again. You can schedule both of these jobs with an Execution
Time of I (immediate).
|
Top
of page
Testing
the Installation
This section provides information
about testing the Web Credit Card BofA installation. You can test the
installation after completing the sections Installing
Files on the Server and Configuring the HP 3000.
| 1. |
Using a Web browser,
display the Web Web Credit Card Login page;
for example, go to the URL https://www.yourcollege.ctc.edu/wts/wccba/waci600.html
|
| 2. |
Check with your college's
Business Office to see if they have set up the necessary FMS Configuration
Parameters for Web Credit Card. The parameters setup by the Business
Office are:
|
Top
of page
Putting
Web Credit Card into Production
This section provides information
about putting Web Credit Card BofA into production by making it available
to your students.
| 1. |
On your Web
server, move the file waci223.html
from the Web Credit Card directory to the Web Registration directory.
This file is
part of the Web Registration application but it includes a link
to Web Credit Card. The file waci223.html
should not be moved until you are ready to make Web Credit Card
available to your students through Web Registration.
|
| 2. |
Add a link from
your college Web site to the Web Credit Card Login page waci600.html. |
Top
of page
Documentation
For information about credit card
authorization, use the administrative Web site for Bank of America.
For information about other
CIS Web-enabled applications, visit the CIS Web site Web-Enabled
Applications.
Top
of page
Contacting
the CIS for Assistance
If you have any questions or comments
about Web Credit Card, please contact CIS Customer Support
Top
of page
All material is
Copyright (c) 1998-2001 Center for Information Services
3101 Northup Way, Bellevue, WA 98004
Telephone (425) 803-9700
This page last modified:
January 8, 2002
Mail comments and questions to: ctcwebmgr@cis.ctc.edu
|