Prerequisites
- Check the Installation checklist.
- Launch the installation
- Steps for application tiers with multiple file systems (conditional)
- Perform post-requisites
- 12.2+ specific instructions (R12.2+ users only)
- Enable network connectivity to Applaud Cloud
- Enable Database Result Cache
- Configure Single sign-on (Optional)
- Set the XXAS: Google Maps API Key profile option
- Schedule License Management concurrent program
- Run Gather Schema Statistics concurrent program
All products will be deactivated after a 30-day grace period following installation. After 30 days the product will no longer work until it is licensed and activated. Once you have purchased an Applaud product you are able to activate it. Products need to be activated on all databases into which they are installed.
To activate a product please refer to Product activation.
Upgrading Release 12.1 to 12.2
If you have already been using the Applaud app on 12.1 and you are later upgrading to 12.2, you have additional steps that need to be run in addition to your standard Oracle upgrade.
Please only run these steps if you already have the Applaud app installed and you are upgrading. If you are installing Applaud for the first time on 12.2, please follow the above Installation steps.
The below steps are prepared whilst assuming that the old 12.1 file system is still mounted on the newly upgraded instance. If the existing 12.1 is a different server and you have upgraded to 12.2 with new servers, please mount the 12.1 file system to the new servers or update the below steps that suit your method of copying.
Copy XXAS_TOP
- Source the RUN file system environment:
$ . <INSTALL_BASE>/EBSapps.env run - The XXAS schema gets created as part of the upgrade process using adsplice, which will create the APPL_TOP/xxas directory on the new 12.2 run file system. Take a backup of the newly created APPL_TOP/xxas directory:
mv $APPL_TOP/xxas/12.0.0 $APPL_TOP/xxas/12.0.0_seed - Copy the $APPL_TOP/xxas schema from the 12.1 instance:
cp -rp <12.1 $APPL_TOP>/xxas/1.0.1 $APPL_TOP/xxas/. - Create the soft link to 12.0.0:
cd $APPL_TOP/xxasln -s 1.0.1 12.0.0
- Copy the existing data from 12.0.0_seed 12.0.0
rsync -zr 12.0.0_seed/* 12.0.0/.
Restore custom java classes
- Source the RUN file system environment:
$ . <INSTALL_BASE>/EBSapps.env run - Take a backup of the existing $JAVA_TOP:
cp -rp $JAVA_TOP/../classes $JAVA_TOP/../classes_applaud - Copy $JAVA_TOP/xxas from the 12.1 instance to the 12.2 $JAVA_TOP:
cp -rp <12.1 $JAVA_TOP>/xxas $JAVA_TOP/. - Run adcgnjar to re-generate customall.jar with the copied Applaud custom class files
Copy JSP’s and compile them
Source the RUN file system environment:
- Source the RUN file system environment:
$ . <INSTALL_BASE>/EBSapps.env run - Copy custom JSP's and HTML files from the 12.1 $OA_HTML to 12.2:
cp -rp <12.1 $OA_HTML>/xxas $OA_HTML/.
cp -rp <12.1 $OA_HTML>/a $OA_HTML/. - Compile custom JSPs:
perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s XxasBIPublisherSrv.jsp
perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s XxasBlobGetSrv.jsp
perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s XxasBlobPostSrv.jsp
perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s XxasEmp.jsp
perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s XxasOpenOfficeSrv.jsp
perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s XxasVacancies.jsp
perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s XxasXmlSrv.jsp
Re-deploy REST servlets
Follow the REST deployment steps to enable Applaud custom REST servlets, see our knowledge base article, Help & Troubleshooting - Can you tell me more about the REST servlet we need to deploy?
Temporarily disable workflow subscription
To avoid multiple workflow notification errors, disable the custom workflow subscription for the below event:
oracle.apps.wf.notification.send with the custom function xxas_user_devices_pkg.push_notif_messages
You should re-enable this after the upgrade is completed.
12.2+ Specific instructions
Follow the 12.2+ specific instructions (R12.2+ users only) specific steps from this installation article.
Follow-up task
- Next steps