tools (e.g. sqlplus, tnsnames.ora, etc.).

Refer to the proper Oracle documentation on setting up the OA

environment variables for further information.

Install the Oracle Client

The Oracle client
followed immediately by the SID should return OK.

Create $CUSTOM_TOP
It is recommended to create a CUSTOM_TOP for the AventX software. The following provides information on
how to create a custom top if these instructions are needed.

Oracle EBS < R12.2.x

This may be considered optional. However, most companies prefer to install the AventX software into a
CUSTOM_TOP. Consult KB Article 16326 for more information about how to create $CUSTOM_TOP.
Oracle EBS > R12.2.x

AventX must be installed in a Custom Top for an R12.2+ environment. This involves creation of a custom
application (custom top and schema) for the AventX software.
schema XXAVENTX with custom top XXAVENTX_TOP. In R12.2+ adsplice MUST be run to register the custom
application. Performing manual steps to create the custom application, as one would do prior to R12.2+, is
not sufficient.

To create a custom application in R12.2+ follow the Oracle Support Document ID 1577707.1. A summary of
the steps contained within this document can be found below: These steps should be performed by the
applmgr (or equivalent) user.

1.
2. Unzip the patch in an appropriate location.
3. Manually copy the three .txt files from the 3636980\izu\admin directory to a temporary location.
4. Rename izuprod.txt to <module>prod.txt where <module> is the custom application
abbreviation (example xxaventx).
5. Rename izuterr.txt to <module>terr.txt where <module> is the custom application
abbreviation (example xxaventx).
6. Edit newprods.txt
Change all references from "izu" to <module> IZU
<MODULE> as above (keep case sensitivity)

Modify other values as appropriate.

7. Edit <module>prod.txt.

Change all references from "izu" to <module> and all references from "IZU" to <MODULE>.
Installing the Software - Pre-installation Steps (All EBS Versions)
Page 26 of 937
Proprietary to STR Software
Change all references for prodid 278 to be your own unique product ID. Oracle recommends a number above
50,000. The following SQL may be used to ensure it is not in use:

SQL>select decode(count ,0, 'Selected number is Available', 'Selected number

already in use') Status, &&enter_custom_applID selected_number

from

select count(*) as count from

select 'x' from fnd_oracle_userid

where oracle_id=&& enter_custom_applID

union

select 'x' from fnd_application

where application_id=&& enter_custom_applID

);

8. Edit <module>terr.txt

Change all references from "izu" to <module> and all references from "IZU" to <MODULE>.

Change the text "Oracle_Support_Diagnostic_Tools" to be "AventX_for_Oracle_EBS"

9. Copy the three text files <module>prod.txt, <module>terr.txt, and newprods.txt to the
$APPL_TOP/admin directory.

10. Change directory $APPL_TOP/admin and run adsplice. The adsplice utility must be run from this
directory.

11. Follow the on screen prompts.

Installing the Software - Pre-installation Steps (All EBS Versions)

Page 27 of 937
Proprietary to STR Software
12. autoconfig will be run automatically by the adsplice tool. Depending on your architecture the
adsplice utility may need to be run multiple times.

If there are multiple application tiers and $APPL_TOP is not shared, adsplice must be run on each
application tier.

If there are multiple application tiers and a shared APPL_TOP, autoconfig must be run on each application
tier.

Recording ADSPLICE action for product: xxaventx

Do you wish to regenerate your environment file [Yes] ?

Checking if AutoConfig is enabled....

Running AutoConfig on : All products ...

The log file is located at:

/oraapps/d01/oracle/VIS/fs1/EBSapps/appl/admin/VIS/log/autoconfig_1.log

Please check the log file for more details about the run of AutoConfig.

If you added new products, use FNDCPASS to change their default passwords.

AD Splicer is complete.

13. Verify the creation of the Custom Application using the following queries; the <PRODUCT ID> is the
numeric ID created in previous steps.

SQL>select * from fnd_application where application_short_name = '<MODULE>';

SQL>select * from fnd_product_installations where APPLICATION_ID = <PRODUCT ID>;

SQL>select * from dba_users where username = '<MODULE>';

14. Log out and back in as the applmgr user and run the following:

$ env | grep <MODULE>

$ ls $<MODULE>_TOP

15. After adsplice is run, the password for xxaventx must be changed. This is required by Oracle EBS.

(Conditional) - Install and Configure the AventX UNIX Software

The AventX UNIX software is required to integrate fax and email delivery with the AventX Oracle Connector
software. This software is NOT required if deploying the AventX for Oracle EBS software for use with the
AventX Print Xpress and/or AventX Attachment Xpress for EAM modules. Download the AventX UNIX
software and follow the instructions for performing the base installation of the software if required.

Installing the Software - Pre-installation Steps (All EBS Versions)

Page 28 of 937
Proprietary to STR Software