Skip Headers

Oracle Payments Implementation Guide
Release 12.1
Part Number E13416-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Profile Options

Profile Options

This appendix lists the profile options that affect the operation of Oracle Payments. This appendix includes a brief description of each profile option that you or your system administrator can set at the site, application, responsibility, or user levels.

During implementation, your system administrator sets a value for each user profile option to specify how Oracle Applications controls access to and processes data.

See Overview of Setting User Profiles, Oracle Applications System Administrator's Guide.

Profile Options Summary

This table indicates whether you can view or update profile options and at which System Administrator levels the profile options can be updated: at the user, responsibility, application, or site levels.

A Required profile option requires you to provide a value. An Optional profile option already provides a default value which you can change.

The key for this table is:

Oracle Payments Profile Options

You can use the System Administrator responsibility to set the Oracle Payments profile options.

IBY: ECAPP URL

This property contains the following URL:

http://machine:port/<jsp>/ecapp?

Replace the machine and port with the names of the actual machine and the actual port where the Oracle Payments ECServlet is installed. Also, make sure that ? is present at the end of the URL or append ? at the end.

This information is mandatory if your EC applications use Oracle Payments PL/SQL APIs or if your application is an Oracle 3i client.

IBY: HTTP Proxy

This property specifies the proxy-URL. For example, http://www-proxy.us.oracle.com.

To set up this property with an empty value, insert a string starting with <. For example, <none>.

IBY: No Proxy Domain

This property specifies the domain name for which no proxy is needed. For example, us.oracle.com.

To set up this property with an empty value, insert a string starting with <. For example, <none>.

IBY: XML Base

This property specifies the location of files required by Oracle Payment's XML framework, such as Oracle Payments DTD files. This property should give the location of the $IBY_TOP/xml directory, where $IBY_TOP is expanded to its fully qualified path name. For example, /usr/appl_top/iby/11.5.0/xml

IBY: JAVA XML Log File

This optional property gives the full-qualified pathname of the debug file where XML messages should be written. This file is similar in purpose to the Oracle Payments debug file, but has been separated from it since XML messages are much larger than single debug statements. If no value is specified for this property, then XML logging is disabled.

IBY: XML Temp Directory

Temporary XML work directory, which must be writable by Oracle Payment's application server. This parameter is optional, but will reduce Oracle Payment's memory usage if provided.

IBY: Outbound Payment Payer ID

Select from the list of values displayed, the payee in Oracle Payments issuing the payment order to the bank. You can set this only at the site level. You need to define this to send transactions from Oracle Payables to Oracle Payments.

IBY: Outbound Payment System Suffix

Enter the three-letter suffix of the payment system that will handle your outbound payment instructions.

IBY: Default Payee for BR Remittance

Select from the list of values displayed, the payee in Oracle Payments remitting the Bills Receivable. You can set this only at the site level. You need to define this to send BR remittance batch from Oracle Receivables to Oracle Payments.

IBY: UI Visibility Class

You can define the visibility class profile option at different levels. This value will determine what data a user can see in the Oracle Payments Operation UI and what mask is applied to the data before displaying it.

IBY: Wallet Location

Location of the Oracle Wallet.

IBY: Wallet Password

Password to open the Oracle Wallet.

IBY: Registered Instrument Encryption

Determines whether registered payment instruments must be stored in encrypted format; if set to Yes, the system security key must have been provided to the Oracle Payments engine in order to register/modify payment instruments; use encrypted registered payment instruments as part of a transaction. The default value is No.