Last updated on MAY 08, 2017
Applies to:Oracle Payments - Version 220.127.116.11 to 18.104.22.168 [Release 11.5]
Information in this document applies to any platform.
Checked for relevance on 29-Jun-2014.
Configuring Oracle iPayment with processor based models such as Paymentech, FDC or Citibank requires establishment of socket connection over leased-line to backend payment system servers. Leased line connection is required for both IP based online authorization and FTP based batch settlement process. This leased line socket connection to a specific IP and port on backend payment system server is established when the apache is started and continuously held by iPayment until explicitly terminated by either apache bounce or some other process such as firewall idol time limit.
Most backend payment systems impose a limitation of one single active connection over a combination of online IP and port due to security reasons. Due to this and the fact that iPayment online connection to this IP and port combination is never released, it is recommended that the backend payment system servlet be configured in a dedicated JVM environment.
Goal of this note is to document steps required for configuring backend payment system servlet for Oracle iPayment on a dedicated host running a single JVM process. Process used and steps outlined here assumes that users have dedicated host for iPayment backend payment system servlet and has installed iAS and verified that apache is operational on this host.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms