From version 990 onwards of EmployeeCenter, your Database Administrator will be asked to deploy the Applaud Solutions REST servlet. Once installed, you will enjoy faster load times and less network traffic across all devices and platforms.
This is a one-off installation task that is performed once per environment. At the end of patch installation, your Database Administrator will be given instructions on how to deploy the REST servlet. These instructions are only presented once per environment and subsequent patch installs will not prompt for these steps even if they were not performed. These steps are mandatory; EmployeeCenter will not function correctly without them.
This is a technical change that uses java servlet-based web services rather than JSP-based. It does not fundamentally change the functionality, security or architecture. The steps performed here are Oracle's recommended way of deploying servlets and these changes will be preserved when upgrading Oracle or running AutoConfig.
For reference, these are the steps provided to a Database Administrator post-install:
1. Deploy the REST servlet as described in $XXAS_TOP/txt/REST_post_install.txt.
Contents of $XXAS_TOP/txt/REST_post_install.txt:
These steps are required to deploy the Applaud Solutions
REST servlet. EmployeeCenter will not function correctly until
these steps have been completed.
1. As the APPLMGR user, login to the Application Tier (APPL_TOP) by
sourcing the environment file.
2. Navigate to the $FND_TOP/admin/template directory
3. Create a subdirectory called custom (if one does not already exist)
4. From $FND_TOP/admin/template copy the orion_web_xml_1013.tmp file
to the newly created custom directory. DO NOT override this
file if it already exists because you may remove existing
custom entries.
5. Create a new <servlet> and <servlet-mapping> section directly underneath any existing
<servlet> and <servlet-mapping> section that looks like this:
<servlet>
<servlet-name>ApplaudRestManager</servlet-name>
<servlet-class>xxas.oracle.apps.xxas.com.RestManager</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>ApplaudRestManager</servlet-name>
<url-pattern>/applaud/api/*</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>ApplaudRestSignIn</servlet-name>
<servlet-class>xxas.oracle.apps.xxas.com.SignIn</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>ApplaudRestSignIn</servlet-name>
<url-pattern>/applaud/auth/signin</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>ApplaudRestSignUp</servlet-name>
<servlet-class>xxas.oracle.apps.xxas.com.SignUp</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>ApplaudRestSignUp</servlet-name>
<url-pattern>/applaud/auth/signup</url-pattern>
</servlet-mapping>
6. For 12.2.2+ installations only: Complete steps 4, 5 and 6 for the file
$FND_TOP/admin/oacore_web_xml_FMW.tmp.
Note that some installations will have the file located at an alternate location:
$FND_TOP/admin/template/oacore_web_xml_FMW.tmp
in which case perform the steps against this file instead.
In order to to synchronize the changes (during the next prepare phase) between both the file systems fs1 and fs2, follow the steps below. Note that the custom synchronization driver file, located at <APPL_TOP_NE>/ad/custom/adop_sync.drv, should be used in these steps. This file has the required documentation on how to put an entry in for a file that needs to be synchronized between the two file systems.
#copy modified template files custom directory to other base
rsync -zr %s_current_base%/EBSapps/appl/fnd/12.0.0/admin/template/custom %s_other_base%/EBSapps/appl/fnd/12.0.0/admin/template
Also for 12.2 customers, please ensure the following Oracle patches are installed to fix Oracle bugs with custom servlets:
The patch level must be at 12.2.2 with the following additional patches installed: 17217965, 17217772, R12.AD.C.Delta.4 (17766337) R12.TXK.C.Delta.4 (17893964).
If you are on 12.2.4 or above, you are guaranteed to have the above patches in place.
7. Run AutoConfig on the Application Tier.