1. Create a user named AXF.

   A system account user name and password is required to create the user. For assistance creating the user, contact your DBA.

2. Assign the configuration schema user the following access privileges:

   • Create table

   • Create sequence

   • Create type

   • Create public synonym

   • Create session

   • Create procedure

   • Unlimited tablespace

1. Locate the scripts in the following folders. Separate folders are provided for Oracle E-Business Suite Forms releases 11 and 12.

   • For Oracle E-Business Suite Forms:

     MW_HOME/wccontent/axf/adapters/ebs/R11/

     MW_HOME/wccontent/axf/adapters/ebs/R12/

   • For Oracle E-Business Suite OAF:

     MW_HOME/wccontent/axf/adapters/ebs/oaf/

2. Using SQL*PLUS, log in to the Oracle E-Business Suite database as the AXF Oracle E-Business Suite configuration schema user (AXF).

   This user was previously created, as described in Creating the AXF Oracle E-Business Suite Configuration Schema User (AXF).

3. As the AXF user, execute the AXF_CREATE_TABLES_SYNONYM script from the applicable Oracle E-Business Suite location.

   To execute the script, enter:

   @AXF_CREATE_TABLES_SYNONYM.sql

   Verify that the following tables were created: AXF_COMMAND_PARAMETERS, AXF_COMMANDS, AXF_CONFIGS, AXF_PROPERTIES, and AXF_FND_MAP.

4. As the AXF user, customize and execute the OAF_AXF_CREATE_TABLES_SYNONYM script from the applicable Oracle E-Business Suite location.

   Before executing the script, set the script's AXF_OAF_REDIRECT_PAGE_URL value so that it identifies the Oracle E-Business Suite system's hostname and port (typically 8000).

   To execute the script, enter:

   @OAF_AXF_CREATE_TABLES_SYNONYM.sql

   Verify that the following tables were created: OAF_AXF_CMD_PARAMS, OAF_AXF_COMMANDS, OAF_AXF_CONFIGS, and OAF_AXF_PROPERTIES.

   Note:

   The AXF_CREATE_TABLES_SYNONYM and OAF_AXF_CREATE_SYNONYM scripts insert rows into the AXF_PROPERTIES and OAF_AXF_PROPERTIES tables, respectively. By default, the AXF_SOAP_SECURITY security parameter is set to TRUE. For SOAP security to work, you must store the SOAP user's password in the FND_VAULT. See Securing Adapter Communications for Oracle E-Business Suite for information on storing the SOAP user name and password in the Oracle E-Business Suite FND_VAULT.

5. As the AXF user, execute the AXF_EBS_PROPERTIES_DATA script from the applicable Oracle E-Business Suite location.

   To execute the script, enter:

   @AXF_EBS_PROPERTIES_DATA.sql

6. Log in as the APPS user.
7. As the APPS user, execute the AXF_APPS_INIT script from the applicable Oracle E-Business Suite location.

   Execute the script by entering:

   @AXF_APPS_INIT.sql

8. As the APPS user, execute the AXF_ADD_EBS_ATTACHMENT_PROC_R12 or AXF_ADD_EBS_ATTACHMENT_PROC_R11 script from the applicable Oracle E-Business Suite location.

   Execute the script by entering the command appropriate for your version:

   @AXF_ADD_EBS_ATTACHMENT_PROC_R12.sql

   @AXF_ADD_EBS_ATTACHMENT_PROC_R11.sql

   Note:

   This compilation may result in warnings, which you can ignore.

9. As the APPS user, execute the AXF_MANAGED_ATTACH_AVAIL, AXF_MANAGED_ATTACH_VALUES, and AXF_MANAGED ATTACHMENT_DATA scripts from the applicable Oracle E-Business Suite location.

   Execute the scripts by entering:

   @AXF_MANAGED_ATTACH_AVAIL.sql

   @AXF_MANAGED_ATTACH_VALUES.sql

   @AXF_MANAGED_ATTACHMENT_DATA.sql

10. As the APPS user, execute the AXF_SOAP_CALL_PROC script from the applicable Oracle E-Business Suite location.

    Execute the script by entering:

    @AXF_SOAP_CALL_PROC.sql

    Note:

    This compilation may result in warnings, which you can ignore.

1. Copy the AXF_CUSTOM.pld file to a UNIX system and run the dos2unix command to convert the file to UNIX format.

   As an alternative, open the file in vi editor and manually remove the ^M characters from the file.

2. Enter the following command line to convert AXF_CUSTOM.pld to AXF_CUSTOM.pll:

   $APPL_TOP/au/12.0.0/resource>frmcmp_batch.sh module=AXF_CUSTOM.pld  userid=apps/apps output_file=AXF_CUSTOM.pll module_type=library parse=yes
   

3. Enter the following command line to convert AXF_CUSTOM.pll to AXF_CUSTOM.plx:

   $APPL_TOP/au/12.0.0/resource>frmcmp_batch.sh module=AXF_CUSTOM.pll userid=apps/apps output_file=AXF_CUSTOM.plx module_type=library compile_all=special
   

4. Convert the CUSTOM.pll file to CUSTOM.pld file. Modify the CUSTOM.pld file by following the steps 9 and 10 in Compiling Oracle E-Business Suite Forms. Then compile CUSTOM.pld file using frmcmp_batch.sh with the commands provided in steps 2 and 3.

1. Verify that you are using the correct JDeveloper version for your Oracle E-Business Suite release. At http://support.oracle.com, search for the following articles to verify that your JDeveloper version includes the needed OAF patch. If you do not have the correct version, download and unzip the appropriate JDeveloper OAF patch file.

   • Doc ID 416708.1, How to find the correct version of JDeveloper to use with Oracle E-Business Suite 11i or Release 12.x

   • Doc ID 357218.1, Troubleshooting JDeveloper setup for Oracle Applications

2. Start JDeveloper, and create an application. Within the new application, create a project.
3. In the following location, locate the java files GenericUcmButtonCO.java and RedirectToAxfCO.java and add them to the project:

   $MiddlewareHome/OracleHome/axf/adapters/ebs/oaf/src/oracle/apps/ak/ucm/axf/webui

   Choose Add Project Content, then click the Add button and select the folder containing the Java files.

4. In the project properties, add the following OAF libraries:

   • BC4J Client

   • BC4J Runtime (Note: Do NOT add BC4J EJB Runtime)

   • Cabo

   • FND Libraries

5. Compile the Java files in the project (right-click the project and choose Rebuild).
6. Copy the class files (find Output Directory, which has the generated classes, via project properties) to the specified Oracle E-Business Suite mid tier $JAVA_TOP directory, creating the required directory structure.

   • Class files to copy: GenericUcmButtonCO.class and RedirectToAxfCO.class

   • Oracle E-Business Suite Server directory to copy class files to:

     $JAVA_TOP/oracle/apps/ak/ucm/axf/webui

7. Import the XML file for the Generic Flex Layout Region into the MDS Repository.

   • XML file to import: ManagedAttachmentButtonRN.xml

   • Directory from which to execute the command (might be $JDEV_USER_HOME, then up two levels to jdevbin):

     $JdevHome/jdevbin/oaext/bin

   • ManagedAttachmentButtonRN import command to execute (from the command prompt, replacing italicized parameters):

     ./import Full path to ManagedAttachmentButtonRN.xml -username appsUsername -password appsPassword -dbconnection "(description = (address_list = (address = (community = tcp.world)(protocol = tcp)(host = DB Hostname)(port = DB Port)))(connect_data = (sid = DB SID)))" -rootdir path to directory where ManagedAttachmentButtonRN.xml is located -rootPackage /oracle/apps/ak/ucm/axf/webui
     

   • Example ManagedAttachmentButtonRN import command (where the XML file is in the $JAVA_TOP directory):

     ./import /$JAVA_TOP/ManagedAttachmentButtonRN.xml -username apps -password password -dbconnection "(description = (address_list = (address = (community = tcp.world)(protocol = tcp)(host = DB Hostname)(port = DB Port)))(connect_data = (sid = DB SID)))" -rootdir /$JAVA_TOP -rootPackage /oracle/apps/ak/ucm/axf/webui
     

     Note:

     If the import fails and returns an error that a jar file is missing, add the full path for the oamdsdt.jar file to the CLASSPATH entry in the import script (import file on Linux, import.bat on Windows). The full path for oamdsdt.jar is:

     $JdevHome/jdevbin/oaext/lib/oamdsdt.jar

     For example, the import file typically contains a CLASSPATH entry of the form:

     set CLASSPATH=$JRAD_ROOT/jdev/appslibrt/uix2.jar

     Change it to add the required jar, like this:

     set CLASSPATH=$JRAD_ROOT/jdev/appslibrt/uix2.jar:/oracle/r12/JDeveloper/jdevbin/oaext/lib/oamdsdt.jar

8. Import the XML file for the Custom OAF page used for redirection into the MDS Repository.

   • XML file to import: RedirectToAxfPG.xml

   • Directory from which to execute the command:

     $JdevHome/jdevbin/oaext/bin

   • RedirectToAxfPG import command to execute (from the command prompt, replacing italicized parameters):

     ./import Full path to RedirectToAxfPG.xml -username appsUsername -password appsPassword -dbconnection "(description = (address_list = (address = (community = tcp.world)(protocol = tcp)(host = DB Hostname)(port = DB Port)))(connect_data = (sid = DB SID)))" -rootdir Path to directory where RedirectToAxfPG.xml is located -rootPackage /oracle/apps/ak/ucm/axf/webui

     Example RedirectToAxfPG import command (where the XML file is in the $JAVA_TOP directory):

     ./import /$JAVA_TOP/RedirectToAxfPG.xml -username apps -password password -dbconnection "(description = (address_list = (address = (community = tcp.world)(protocol = tcp)(host = DB Hostname)(port = DB Port)))(connect_data = (sid = DB SID)))" -rootdir /$JAVA_TOP -rootPackage /oracle/apps/ak/ucm/axf/webui

     Note:

     If the import fails and returns an error that a jar file is missing, see the note in step Compiling Java Files, Copying Class Files, and Importing XML Files.

9. Verify that the import was successful, by running the following commands via SQL prompt as the Oracle E-Business Suite APPS user:

   SET SERVEROUTPUT ON
   BEGIN
   JDR_UTILS.PRINTDOCUMENT('/oracle/apps/ak/ucm/axf/webui/RedirectToAxfPG');
   JDR_UTILS.PRINTDOCUMENT('/oracle/apps/ak/ucm/axf/webui/ManagedAttachmentButtonRN');
   END;
   /

10. Load the oaf_axf_messages.ldt message bundle using FNDLOAD. This file contains the translatable messages used by the controller classes.

    • Verify that the LD_LIBRARY_PATH variable is set to $ORACLE_HOME/lib

    • As the Oracle E-Business Suite APPS user, execute the following command from $FND_TOP/bin:

      FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afmdmsg.lct Full path to oaf_axf_messages.ldt
      

    • When prompted, enter the APPS user password.

11. Restart the Oracle E-Business Suite instance.

1. Complete all steps except step 7 in Compiling Java Files Copying Class Files and Importing XML Files. (Step 7, which imports the ManagedAttachmentButtonRN.xml file, is not needed.)
2. Customize the sample XML file provided (SampleAXFButtonRN.xml), modifying the following button ID and button prompt (title) values.

   <oa:button id="AXFButton" prompt="Sample AXF Button"/>

   For example, you might change the button ID to IPM_BUTTON and button prompt (title) to Supplier Maintenance.

3. Import the XML file into the MDS Repository.

   • XML file to import: SampleAXFButtonRN.xml (or modified version)

   • Directory from which to execute the command:

     $JdevHome/jdevbin/oaext/bin

   • Import command to execute (from the command prompt, replacing italicized parameters):

     ./import  Full path to XML file -username apps -password appsPassword -dbconnection "(description = (address_list = (address = (community = tcp.world)(protocol = tcp)(host = DB Hostname)(port = DB Port)))(connect_data = (sid = DB SID)))" -rootdir path to directory where XML file is located -rootPackage /oracle/apps/ak/ucm/axf/webui
     

   • Example import command (where the XML file is in the $JAVA_TOP directory):

     ./import /$JAVA_TOP/SampleAXFButtonRN.xml  -username appsUsername -password appsPassword -dbconnection "(description = (address_list = (address = (cUommunity = tcp.world)(protocol = tcp)(host = DB Hostname)(port = DB Port)))(connect_data = (sid = DB SID)))" -rootdir /$JAVA_TOP -rootPackage /oracle/apps/ak/ucm/axf/webui
     

4. Use this button ID for the command in the OAF_AXF_COMMANDS Table (Oracle E-Business Suite OAF). The new button ID will correspond to AXF_EVENT_ID. An example is shown in OAF_AXF_COMMANDS Table (Oracle E-Business Suite OAF).
5. In the OAF_AXF_CMD_PARAMS table, add required command parameters, if any, for the AXF_EVENT_ID.
6. Follow the steps in Personalizing OAF Pages to Add Managed Attachments to add the button imported above via personalization. In step Personalizing OAF Pages to Add Managed Attachments of Personalizing OAF Pages to Add Managed Attachments, be sure to enter the name of the package you imported into the MDS repository in step Configuring Other Services on OAF Pages (Optional) of this section. In the example provided, this name is /oracle/apps/ak/ucm/axf/webui/SampleAXFButtonRN.

1. Ensure that SOAP security is enabled, by verifying that it is set to TRUE for the AXF_SOAP_SECURITY property in the AXF_PROPERTIES Table (Oracle E-Business Suite) and the OAF_AXF_PROPERTIES Table (Oracle E-Business Suite OAF).

   Note:

   Ensure that you restart Oracle E-Business Suite after changing AXF_SOAP_SECURITY from FALSE to TRUE.
2. Set the AXF_SOAP_POLICY property to USER_NAME_TOKEN.
3. Set the AXF_SOAP_USER value (for example, to weblogic). By default, this setting might be AXF and should be changed. The AXF_SOAP_USER refers to a valid Oracle WebLogic Server administrator.
4. Store the SOAP password in the database vault by executing the following command as APPS schema:

   execute fnd_vault.put('AXF','AXF_SOAP_USER','SOAP_PASSWORD');

   Where AXF_SOAP_USER is the SOAP user ID used in the SOAP header for authentication, and SOAP_PASSWORD is the SOAP password. (The first item, 'AXF', is an identifier that needs to be included as is.)

   For example:

   execute fnd_vault.put('AXF','weblogic','examplepassword');

5. Verify the previous command with this statement:

   select fnd_vault.get ('AXF','AXF_SOAP_USER') from dual;

   For example:

   select fnd_vault.get ('AXF','weblogic') from dual;

Perform the following procedures to specify Oracle E-Business Suite system settings for SSL configuration for AXF.

• Configuring the Oracle Wallet

• Configuring the Integration for SSL

1. Assign the AXF configuration schema user the following privileges:

   • Drop table

   • Drop sequence

   • Drop public synonym

2. As the AXF user, execute the AXF_DROP_TABLES_SYNONYM script for your Oracle E-Business Suite version, from the applicable location listed below. This script drops all tables, synonyms, and sequences created by the AXF_CREATE_TABLES_SYNONYM script run during installation.

   Oracle E-Business Suite 12: MW_HOME/wccontent/axf/adapters/ebs/R12/AXF_DROP_TABLES_SYNONYM.sql

   Oracle E-Business Suite 11: MW_HOME/wccontent/axf/adapters/ebs/R11/AXF_DROP_TABLES_SYNONYM.sql

   Execute the script by entering:

   @AXF_DROP_TABLES_SYNONYM.sql

3. Remove the AXF database schema user.
4. Remove AXF_CUSTOM.* (AXF_CUSTOM.pll, AXF_CUSTOM.pld, and AXF_CUSTOM.plx) from FORMS_PATH (or FORMS60_PATH on Oracle E-Business Suite 11 systems).
5. Restore the CUSTOM.pll file you backed up in step Compiling Oracle E-Business Suite Forms in Compiling Oracle E-Business Suite Forms.
6. Open Oracle Forms Builder and connect to the Oracle E-Business Suite database as the APPS user. Forms Builder is typically located in the /bin/ subdirectory of your database's Oracle home.
7. Open the restored CUSTOM.pll by selecting File, then Open and selecting PL/SQL Libraries (*.pll) in the Files of Type field.
8. With CUSTOM.pll open, select Program, then Compile pl/sql, then All (Oracle E-Business Suite 12) or Program, then Compile, then All (Oracle E-Business Suite 11).
9. Compile CUSTOM into a module (.plx) by selecting Program, then Compile Module (Oracle E-Business Suite 12) or File, then Administration, then Compile File (Oracle E-Business Suite 11).
10. Save all before exiting Forms Builder.

1. Assign the AXF configuration schema user the following privileges:

   • Drop table

   • Drop sequence

   • Drop public synonym

2. As the AXF user, execute the OAF_AXF_DROP_TABLES_SYNONYM script from the location listed below. This script drops all tables, synonyms, and sequences created by the OAF_AXF_CREATE_TABLES_SYNONYM script run during installation.

   MW_HOME/wccontent/axf/adapters/ebs/oaf/OAF_AXF_DROP_TABLES_SYNONYM.sql

   Execute the script by entering:

   @OAF_AXF_DROP_TABLES_SYNONYM.sql

3. Remove the AXF database schema user.