Oracle Developer 6i patchset 19 (6.0.8.28.x) or later (Note 125767.

1)

1. 2. 3. 4. 5.

[COMMON_TOP]/admin/scripts/adfroctl.sh Change all lines containing mode=http to mode=socket or mode=https This file should always be kept in sync with the version at $FND_TOP/resource/appsweb.cfg Stop the Forms and Reports server processes. Install the Developer 6i Patch

Forms & Reports 6i Patch 19 for Linux Note: You should be logged in as the oracle user with write privileges to the ORACLE_HOME.(ie. You have write permission to all the files under $ORACLE_HOME) Installation Instructions Set your ORACLE_HOME. If you are going to apply this patch on top of an iAS install: Set ORACLE_HOME to <iAS_HOME>/6iserver o Prepend <iAS_HOME>/6iserver/bin to the *beginning* of PATH o Prepend <iAS_HOME>/6iserver/lib to the *beginning* of LD_LIBRARY_PATH Copy the files in this patch to your $ORACLE_HOME. Unzip the patch using either WinZip on NT or unzip on Unix. Run the install script contained in the patch: o cd $ORACLE_HOME/developer6i_patch19 o ./patch_install.sh 2>&1 | tee patch_install_p19.log (ksh) o ./patch_install.sh |& tee patch_install_p19.log (csh) o Check patch_install_p19.log for errors. Relink Procedure Builder, Forms, Graphics and Reports: o cd $ORACLE_HOME/procbuilder60/lib; make -f ins_procbuilder.mk install o cd $ORACLE_HOME/forms60/lib; make -f ins_forms60w.mk install o cd $ORACLE_HOME/graphics60/lib; make -f ins_graphics60w.mk install Reports has both link-time and run-time dependency with libjava.so so you need to append $ORACLE_HOME/network/jre11/lib/linux/native_threads in $LD_LIBRARY_PATH before linking Reports. The same $LD_LIBRARY_PATH should be used at run-time. o cd $ORACLE_HOME/reports60/lib; make -f ins_reports60w.mk install De-Installation Instructions o Set your ORACLE_HOME. o If you originally applied this patch on top of an iAS install:

o o o o o o o o o o o o o Linux Users 7.

Set ORACLE_HOME to <iAS_HOME>/6iserver Prepend <iAS_HOME>/6iserver/bin to the *beginning* of PATH Prepend <iAS_HOME>/6iserver/lib to the *beginning* of LD_LIBRARY_PATH Run the de-install script contained in the patch: cd $ORACLE_HOME/developer6i_patch19 ./patch_deinstall.sh 2>&1 | tee patch_deinstall_p19.log (ksh) ./patch_deinstall.sh |& tee patch_deinstall_p19.log (csh) Check patch_deinstall_p19.log for errors. Relink Procedure Builder, Forms, Graphics and Reports: cd $ORACLE_HOME/procbuilder60/lib; make -f ins_procbuilder.mk install cd $ORACLE_HOME/forms60/lib; make -f ins_forms60w.mk install cd $ORACLE_HOME/graphics60/lib; make -f ins_graphics60w.mk install cd $ORACLE_HOME/reports60/lib; make -f ins_reports60w.mk install

Relink Applications Executable on UNIX Platforms

The executables are f60webmx, ar60run , ar60runb, ar60rund, and are all owned by FND. You can relink these executables by running adadmin When the Main Menu appears select 'Maintain Applications Files Menu' and then select 'Relink Applications Program' Answer the questions below as follows, in order to select the individual executables for relinking. Enter list of products to link ('all' for all products)[all] : fnd Generate specific executables for each selected product [No] ? y Relink with debug information [No] ? n (You will then be offered a list of executables that are available for relinking) Enter executables to relink, or enter 'all' [all] : f60webmx ar60run ar60runb ar60rund * * In a multi-node configuration, not all these executables exist on each node. The list of executables will show those that do exist on the node you are currently running on, and only those should be entered to avoid errors.

8.

Apply the Oracle Applications 11i Interoperability Patch Linux users must also apply the Linux interoperability Patch 3830807.

#------------------------------------------------------------------------# Patch for Bug 3830807 #-------------------------------------------------------------------------

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

DATE: September 20, 2004, Readme Updated June 2007 ----------------------------------------------------Platform Patch for : LINUX Intel RDBMS Version: : 8.0.6.3 Bugs Fixed by this patch: ------------------------3293983: 8.0.6.3 APPLICATIONS INTEROPERABILITY PATCH 3212373: PLEOS:PLEASE CREATE A PATCH FOR 806 NETWORK MAKE FILES TO INCLUDE STUBS 3212401: PLEOS:PLEASE CREATE A PATCH FOR D2K MAKEFILES TO INCLUDE STUBS IN LDFLAG 3830807: PATCH 3293983 NEEDS TO INCLUDE ALL THE MAKEFILES UNDER THE 8.0.6 ORACLE_HOME Patch Installation Instructions: -------------------------------You must login to your Linux machine as the Oracle software owner before applying this patch. Your setting for ORACLE_HOME must be the value for the Forms 6i 8.0.6 based ORACLE_HOME and you must have write previlages to this area. [1] To apply the patch, unzip the PSE container file: % unzip p3830807_8063_LINUX.zip [2] Set your current directory to the directory where the patch is located, eg: % cd 3830807 [3] Add execute permission to the script supplied in this patch % chmod u+x patch.sh [4] Check the value of LD_LIBRARY_PATH. This patch will relink reports60 binaries. Reports has both link-time and run-time dependency with libjava.so so you need to include $ORACLE_HOME/network/jre11/lib/linux/native_threads OR

# $ORACLE_HOME/network/jre11/lib/i686/native_threads # in $LD_LIBRARY_PATH before running patch.sh # # Please check your files under $ORACLE_HOME/network/jre11/lib to see # which one of the above is appropriate on your system. The same # $LD_LIBRARY_PATH should be used at run-time. # # [5] Run the script supplied by this patch # # % ./patch.sh # # [6] Relink all Applications executables. In AD Administration, choose # "Relink Applications programs" from the "Generate Applications Files" # menu. # # The installation of the patch is now complete.

9.

Configure Applications to use Sun JRE Native Plug-in

Step 1. Download Required Patches

o Step 1.1. Download the JRE Plug-in Oracle E-Business Suite

interoperability patch
Download the JRE plug-in Oracle E-Business Suite interoperability patch 6863618.

Step 2. Rename the JRE Plug-in and Place it on Webserver

o Step 2.1. Rename the JRE 6 Native Plug-in

Rename the downloaded JRE Native plug-in file from jre-6_uX-windowsi586-p.exe to j2se160X.exe Where X = the version number. (For single digit version numbers, please prefix the version number with a zero). Using jre-6u7 as an example X would be 07, so the file would be renamed j2se16007.exe). o Step 2.1.1. Place the JRE 6 Plug-in on the Web Application Tier

Move the j2se160X.exe file to the web application tier and place it in $[COMMON_TOP]/util/jinitiator.

[COMMON_TOP] refers to the top level directory where the common utilities are installed. By default, this is the parent directory of $JAVA_TOP. See the 'Installing Oracle Applications' manual for more details on the Oracle E-Business Suite file system.

Step 3. Apply Prerequisite Patches (Conditional)

o Developer 6i Patchset 19 Users

Developer 6i Patchset 19 (6.0.8.28.x) users must apply the forms focus fix patch 9863561. Please ensure you have also applied the Developer 6i Patchset 19 (6.0.8.28.x) interop patch 9935935 or later. (See note 125767.1 titled, 'Upgrading Developer 6i with Oracle EBusiness Suite 11i'.) Failure to apply this patch can result in the following error: Exception in thread "thread applet-oracle.forms.engine.Main-1" java.lang.NoClassDefFoundError: oracle/forms/ui/FLWTextArea at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at oracle.forms.handler.TextAreaItem.class$(Unknown Source) at oracle.forms.handler.TextAreaItem.getDefaultClass(Unknown Source) at oracle.forms.handler.UICommon.instantiate(Unknown Source) at oracle.forms.handler.UICommon.onCreate(Unknown Source) at oracle.forms.handler.TextAreaItem.onCreate(Unknown Source)

Step 4. Apply the Interoperability Patch

Apply the JRE plug-in Interoperability patch 6863618 by following the steps below. o Step 4.1. Enable Maintenance Mode

If you are using Oracle Applications Release 11.5.10 or Minipack 11i.AD.I or higher, you must enable 'Maintenance Mode' before applying the patch driver from the JRE Interoperability Patch, as follows; o Step 4.1.1. Shutdown Apache

Shutdown Apache (on normal mode) by running; adapcctl.sh stop or adstpall.sh apps_user/apps_pwd

Step 4.1.2. Enable 'Maintenance Mode'

Enable 'Maintenance Mode' by running adadmin, and selecting the following options; Select menu option 5, 'Change Maintenance Mode' Select menu option 1, 'Enable Maintenance Mode' (For further information on Maintenance Mode please review note 291901.1 titled, 'Maintenance Mode - A New Feature in 11.5.10')

Step 4.2. Apply the JRE Interoperability Patch (UNIX Users only)

If your application-tier server nodes are running Microsoft Windows, skip this step and proceed to Step 4.3. Applying the JRE Interoperability Patch for the first time is a two stage process: o Step 4.2.1. Apply the Patch Driver

If you are upgrading to the JRE native plug-in for the first time, please apply the interop patch using AutoPatch. Note:If you wish to alter the JRE version you are currently running and have previously applied the interop patch on your environment, there is no need to apply it again. Please skip this step and continue to step Step 4.2.2 below. o Step 4.2.2. Run the txkSetPlugin.sh Script

Run the txkSetPlugin.sh script from the patch_top/interop_patch_number/fnd/bin/ directory, against the web node of your middle tier, where patch_top is the directory in which you unzipped this patch. The txkSetPlugin.sh script will update the new JRE version information into your AutoConfig context file, update the version used by Workflow and run AutoConfig to incorporate the new values throughout your application. This script must be run using the following command: txkSetPlugin.sh jversion Where: jversion represents the JRE version you wish to install, without decimal points or underscores. (e.g. 16026) This value is listed in the 'jversion Parameter' column of appendix JRE Parameter Settings. For example; the command to install JRE 1.6.0_26 is: txkSetPlugin.sh 16026 The script will prompt you for the following values, if it does not find them automatically:

Location of APPSORA.env file, if not present in the default location $APPL_TOP. Location of the AutoConfig Context File. Password for the APPS user in the database (If the correct value is returned by the script you may press the return key at the prompt). o Step 4.2.3. Multiple Application-Tier Web Server Nodes

If you have multiple web application tier server nodes, repeat the steps above to apply the patch driver in the JRE Interoperability Patch against all other web application tier server nodes. Step 4.4. Disable Maintenance Mode

Disable Maintenance Mode by following these steps: o Step 4.4.1. Disable 'Maintenance Mode'

Disable 'Maintenance Mode' by running adadmin, and selecting the following options; Select menu option 5, 'Change Maintenance Mode' Select menu option 2, 'Disable Maintenance Mode' o Step 4.4.2. Restart Apache

Restart Apache (on normal mode) by running; adapcctl.sh start or adstrtal.sh apps_user/apps_pwd

Section 4: Post-Installation Steps

Step 5. Verify your upgrade

Once the JRE plug-in has been installed on your client, follow these steps to verify that you have successfully upgraded JRE. o Step 5.1. Enable Java Console

Enable the Java Console on your PC through the 'Java Control Panel' by clicking on the 'Java' icon within your desktop clients 'Control Panel'. Select the 'Advanced' Tab and expand the 'Java Console' field. Make sure the 'Show Console' option is selected. o Step 5.2. Close Browser Windows

Close all browser windows. Wait a minute or so after the windows are closed until the processes have finished saving their data to disk.

Step 5.3. Sign into Oracle E-Business Suite Sign into Oracle E-Business Suite, and choose a Forms-based (Professional user interface) responsibility. For information on requirements and possible issues when trying to connect to a new or freshly upgraded Oracle E-Business Suite environment, please see Accessing Oracle E-Business Suite from a Desktop Client in the Appendices section. Step 5.4. Check the Console Window A window titled Java Console will appear, and should display lines describing the version. For example: Java(TM) Plug-in: Version 1.6.0_26 Using JRE version 1.6.0_26 Java HotSpot(TM) Client VM If a higher version of JRE from the one you installed is shown, it may be because a Non-Static versioning model is being used, please check Appendix A: Static vs Non-Static Versioning and Set Up Options. If this is not the issue, please verify that you have correctly followed all the steps above.

Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6)(patch 5903765) or later