Download Installation Reference Card

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Tandem Computers wikipedia , lookup

PL/SQL wikipedia , lookup

Microsoft Access wikipedia , lookup

Serializability wikipedia , lookup

Database wikipedia , lookup

Database model wikipedia , lookup

Expense and cost recovery system (ECRS) wikipedia , lookup

Concurrency control wikipedia , lookup

Versant Object Database wikipedia , lookup

Clusterpoint wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

Transcript
CPM Installation Reference Card
MPS Frame
Contact MPS
Required Merchant Setup Information
Before a CyberSource Payment Manager (CPM) can begin payment processing, the merchant
must set up an account with Midwest Payment Systems (MPS). Please contact MPS to initiate
this process and obtain the required merchant setup information. Also, if you support
American Express (AmEx) please contact American Express to obtain their required merchant
setup information.
Required Information
Record Information
Merchant ID
Store Number
Acquirer BIN
Destination Country Code
Originating ID
Midwest
Payment Systems
800.278.6888
Category Code
FTP Username
FTP Password
American Express
Merchant Services
800.528.5200
FTP File Name
American Express Establishment
Number
Authorization IP Address
Authorization Port Number
Settlement IP Address
Settlement Port Number
American Express Merchant Name
American Express Service City
American Express Charge
Descriptors
Minimum CPM
requirements
CPM (Windows)
Administration and Server Hardware
•
•
•
•
•
•
Form Number: 1169.1
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
Date Printed: September 2001
Administration and Server Software
•
•
•
•
Microsoft Windows NT Server or NT Workstation Software 4.0 operating system with
Service Pack 6a,
Windows 2000 Server, Service Pack 1, or
Windows 2000 Advanced Server, Service Pack 1
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
Administration Software
•
•
•
•
Microsoft Windows NT Server or NT Workstation Software 4.0 operating system with
Service Pack 6a,
Windows 2000 Server, Service Pack 1, or
Windows 2000 Advanced Server, Service Pack 1
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
©2001 by CyberSource Corporation. All rights reserved.
Server Software
•
Sun Solaris 8 operating system with Solaris 8 recommended patch cluster
Database Requirements
•
•
Oracle 8.1.x or Sybase 11.x
OpenLink ODBC Drivers
Technical requirements
CPM Installation
Unix
NT
Unix server
administrator
Windows NT
server administrator
Database
administrator
Network
administrator
Hardware
technician
Set up the server for the CPM environment (A)
•
•
•
•
CPM Server
$
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 MPS (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)
•
•
MPS
If you’re upgrading from a previous version of CPM, update the CPM database tables.
Set up the general and specific MPS settings (A)
•
•
•
•
•
•
Form Number: 1169.1
Use the CPM Database Utility and create CPM tables in your ODBC database.
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 MPS.
Set up CPM Security and enable the Secure Socket Layer (SSL) feature for transaction
security between the CPM transaction APIs and the CPM Server.
Date Printed: September 2001
Test the CPM Server (A)
•
•
•
Run local trial transactions on the CPM Server in Test mode to ensure proper connectivity
of the network, database, and any auxiliary software.
Call MPS 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 MPS with the CPM Server in Production mode.
Once testing is complete, ask MPS to place the connection hardware in the appropriate
Production mode.
CyberSource
Customer Support
314.692.0929 Phone
314.692.0805 Fax
©2001 by CyberSource Corporation. All rights reserved.