EBizCharge for Oracle E-Business Suite
Pre-Installation Guide

Table of Contents

EBizCharge for Oracle E-Business Suite (EBS)
Compatibility
EBizCharge works with Oracle EBS 12.1.3, 12.2.4, 12.2.6, 12.2.8
Required Installation Time

Approximately 30 business days comprising of the following steps:
Day 1: Create credentials, set up the environment, and begin installation.
Day 1- 4: Complete installation process.
Day 5 -15: Testing by the EBizCharge team.
Day 16 - 25: UAT by client in test environment.
Day 26 – 28: Production Migration without conversions (with conversions it could be more than a week depending on the data size).
Day 29 - 30: Client can go live once all deployment checks are confirmed.

Overview

EBizCharge for Oracle E-Business Suite (EBS) works in harmony with the Oracle EBS ERP to save time by managing payments in one place, for merchants and their customers. EBizCharge integrates with Oracle EBS to process credit and debit payments.

EBizCharge automatically applies payments back to invoices and updates the balance due, cuts down on user errors, and eliminates double data entry.  

Important

This pre-installation guide is a stand-alone document prepared exclusively for the EBizCharge for Oracle E-Business Suite integration. It provides necessary information on the pre-requisites to be provided to merchants prior to the installation. Content included in this guide may change when updates and enhancements are made. For further information on the EBizCharge integration, please contact your EBizCharge Relationship Manager, or our in-house 24/7 Support team.

Purpose

The purpose of this guide is to provide streamlined installation instructions for merchants and their customers/end-users.

This guide is not to be used for widespread publication unless, prior written consent is obtained from CBS designated personnel. It is not intended to be used for detailed specifications, maintenance, or trouble shooting of EBizCharge for Oracle.

Additional documentation for the EBizCharge for Oracle EBS integration can be requested, please contact Technical Publications.

Connectivity Requirements

EBizCharge requires high-speed internet connectivity to work on desired terminals and devices. EBizCharge works with both MAC and Windows operating systems.

Ancillary Documentation

In addition to this handbook, Technical Publications offers the following documents to support the EBizCharge for Oracle EBS integration:

  1. Installation Guide
  2. User Guide
  3. Functionality Overview

Requirements

The following are required prior to the installation process:

  1. Java version of their Unix.
  2. Unix box access.
  3. DB access.
  4. Application access – sysadmin responsible for the merchant’s development instance.

Prerequisites

The following prerequisites must be in place prior to the installation of EBizCharge:

  1. Create ebizch directory in $JAVA_TOP and give all permissions to the designated user for this directory.
  2. Merchant’s must provide their development application username and password for accessing the environment.
  3. Merchant’s Oracle DBA (database administrator) must change the following file.Edit the file $INST_TOP/ora/10.1.3/j2ee/oacore/config/oc4j.properties just comment out those parameters, adding a ‘#’ at the beginning of the line:

http.proxyHost

http.proxyPort

http.nonProxyHosts

  1. Create ebizch schema and allow to create and grant permissions on tables to apps user.
  2. R12: IBY: Setting up payment wallets for funds disbursement (Doc ID 1430916.1).
  3. Install wallet certificate using the following link: https://soap.ebizcharge.net/eBizService.svc
  4. Create ebizch user in oracle applications.

Deployment Considerations

These provisions must be in place prior to installing EBizCharge:

  • The client must have a sandbox login to Oracle EBS. EBizCharge Support Team will provide merchants with their sandbox login and password.
  • XML files should be sent to the client to reside on their workstation prior to installation.
  • The client’s primary user must have full Admin rights.
  • The client’s Security ID must be provided to the installer prior to installation.

Glossary

Glossary for all the integration are available in one place. 

See Glossary for more details on the terms listed.