Download Installation Reference Card

CPM Installation Reference Card
FDMS Nashville Frame
Contact
FDMS Nashville
Required Merchant Setup Information
Before CyberSource Payment Manager (CPM) can begin payment processing, the merchant must open
an account with First Data Merchant Services (FDMS). Contact FDMS Nashville to initiate this process
and obtain the required merchant setup information.
Gateway Settings
Required Information
Record Information
Host IP Address
First Data Merchant
Services
(Nashville Platform)
301.745.7371
Host IP Port
Source ID
Enable Authorization Decline
Codes
Enable Third Party Provider
TPP ID2
CyberSource
Customer Support
software-support@
cybersource.com
Visa BID2
Visa AUAR2
Merchant Agreement Settings
Required Information
FDMS Merchant ID
Terminal ID
Enable Partial Authorization
Record Information
CPM (Windows)
Administration and Server Hardware
•
•
•
•
•
•
Intel Pentium II Processor (minimum 400 MHz recommended)
Minimum 128 Mbytes RAM suggested. Additional RAM may be required depending on
transaction volume.
Hard disk space with at least 9 Gbytes of available, uncompressed space
Dual-speed CD-ROM drive or higher
SVGA monitor
10Base-T or faster network interface card (NIC) installed and connected to the network
Administration and Server Software
•
•
•
•
Microsoft Windows 2000 Server, Service Pack 1, or
Windows 2000 Advanced Server, Service Pack 1, or
Windows 2003 Server
TCP/IP protocol stack
ODBC-compliant and Y2K-compliant database installed on its own computer. The database is
required for logging all transactions and CPM Server information. CPM supports Microsoft SQL
Server, Sybase, and Oracle database applications.
ODBC driver software for your brand of database installed for the CPM Server.
Database Requirements
•
ODBC compliant and Y2K compliant, relational database management system (RDBM) installed
on its own computer. The database is required for logging transaction and CPM Server information.
CPM supports Microsoft SQL Server and Oracle database applications.
Note CyberSource recommends that SQL Server users who expect to have databases containing
150,000 or more transactions use Microsoft SQL Server 7.0 or greater.
•
The latest ODBC driver software for the database application you will use with the CPM Server.
CPM (Unix)
Administration Hardware
•
•
•
•
•
•
Intel Pentium II Processor (minimum 400 MHz recommended)
Minimum 128 Mbytes RAM suggested. Additional RAM may be required depending on
transaction volume.
Hard disk space with at least 1 Gbyte of available, uncompressed space
Dual-speed CD-ROM drive or higher
SVGA monitor
10Base-T or faster network interface card (NIC) installed and connected to the network
Server Hardware
•
•
•
•
•
Sun Sparc (minimum of one 256 MHz processor)
Minimum 128 Mbytes RAM suggested. Additional RAM may be required depending on
transaction volume
Hard disk drive with at least 1 Gbyte of available, uncompressed space on /opt file system
Dual-speed or higher CD-ROM
Network interface card (NIC) installed and connected to the network
©2011 by CyberSource Corporation. All rights reserved.
Minimum CPM
requirements
Administration Software
•
•
•
•
Microsoft Windows 2000 Server, Service Pack 1, or
Windows 2000 Advanced Server, Service Pack 1, or
Windows 2003 Server
TCP/IP protocol stack
ODBC-compliant and Y2K-compliant database installed on its own computer. The database is
required for logging all transactions and CPM Server information. CPM supports Microsoft SQL
Server, Sybase, and Oracle database applications.
ODBC driver software for your brand of database installed for the CPM Server
Server Software
•
Sun Solaris 8 with recommended patch cluster, or Solaris 9
Database Requirements
•
•
Oracle 9.1, Sybase 12.5, or DB2
OpenLink ODBC Drivers
Technical requirements
Unix
Unix server
administrator
Windows
Windows server
administrator
Database
administrator
Network
administrator
Hardware
technician
Set up the server for the CPM environment (A)
•
•
•
•
CPM Installation
Locate the server in a secure area that has access to network and communication connections
behind a firewall.
Connect the server to the network.
Configure the TCP/IP protocol stack.
Test the network connection.
Set up the communication connection for FDMS Nashville (B)
•
•
Install the required leased line.
Connect the leased line to the preconfigured frame relay access device.
Install and configure any required auxiliary software (C)
Set up the ODBC-compliant database (D)
Install the CPM Server software (A)
•
•
Install the CPM Server software, connect the server to the database, select the payment option, and
configure the setup.
If installed, configure the CPM Client.
Prepare the CPM Server database (D)
•
•
•
•
D
C
If you’re upgrading from a previous version of CPM, update the CPM database tables.
B
Connect the CPM Administration Client to the CPM Server.
Choose the established Data Source Name (DSN) for the database and establish login settings.
Set up the CPM Server information.
Set up the storage parameters for the established database.
Set up a merchant for FDMS Nashville.
Set up CPM Security and enable the Secure Socket Layer (SSL) feature for transaction security
between the CPM transaction APIs and the CPM Server. (Optional)
Test the CPM Server (A)
•
A
Use the CPM Database Utility and create CPM tables in your ODBC database.
Set up the general and specific FDMS Nashville settings (A)
•
•
•
•
•
•
CPM Server
Run local trial transactions on the CPM Server in Test mode to ensure proper connectivity of the
network, database, and any auxiliary software.
Call FDMS Nashville and inform them that you would like to run trial transactions to confirm data
transmission. Using the CPM Client or your proprietary client program, run the trial transactions
for FDMS Nashville with the CPM Server in Production mode.
Once testing is complete, ask FDMS Nashville to place the connection hardware in the appropriate
Production mode.
©2011 by CyberSource Corporation. All rights reserved.
FDMS Nashville