• Balaswamy Kalla
• Jabej Nerella
• Ashok Rajagopal
Change History
OTL Calendar View is a new flexible Calendar view of OTL timecards. This document
addresses steps to set this application up and its various configurations. To understand
the background of the document, please go thru the following questions.
5. Is there any special skill required to get this functionality up and running?
Setting up the ADF based Calendar View of timecards requires some knowledge
about middleware administration and access to key functions in the Middle Tier.
Steps are outlined in this document with detailed instructions.
6. Is there any difference between the ADF pages and standard OAF pages?
ADF pages, unlike standard OAF pages cannot be used as soon as the patch
containing the functionality is applied. Once set up, they can be used exactly like
standard OAF pages by users.
There are no OTL Preferences attached to this functionality. However, a new profile
option OTL: Calendar View Colors is provided with the functionality to configure the
colors rendered in the Calendar View. Details are provided in the section Using the
Calendar View below.
The calendar view of timecards enables you to see all the time entries recorded in the time
store on the respective dates in terms of start time and stop time, or hours recorded for
each entry. Time entries are indicated by a band on the days covered by that timecard
period along with the total hours recorded in that timecard. This helps in easy
identification of timecards that have been entered. The calendar view also helps you to see
what timecard periods or days do not have time entered and also the gaps in time entries
on any specific day. The timecard and time entries are represented on the calendar using
different color coding. You can change this color coding using the new profile option OTL:
Calendar View Colors.
Calendar View provides the users with the following 4 views of time recorded.
Monthly View
In addition to flexible views of Time entered, the Calendar View enables the users to
navigate to Recent Timecards and Create Timecards page to Create, View or Update
timecards.
3) After Applying the patch Go to this folder in the server machine for OTLCalendar
application $HXC_TOP/patch/115/ear/OTLCalendar.zip file
and take a back up of the file (or)
4) Unzip the Downloaded Patch and go the below location.
22117777/hxc/patch/115/ear/OTLCalendar.zip
7) Unzip the war file and open WEB-INF/web.xml file in text editor.
a. <context-param><param-name>APPL_SERVER_ID</param-name>
12) Zip the folder and rename it to. ear file again.
Tip: If 7-Zip software is installed, you can directly edit web.xml file without
Unzipping and zipping the file. Steps – Open archive for ear file, again same for
war file, open WEB-INF and right click on web.xml and edit to change the
Oracle Time and Labor Development Page 12 of 40
parameter and save.
Server id is key point here, after deploying the OTL Calendar ear file
works only for the EBS instance whose server id is provided. If the Calendar application
require to work with another instance needs another deployment
With server id supplied as instructed in the prepare deployment section.
§ You can use WinSCP or any ftp application to move the. ear file to the WebLogic
server machine.
§ It is recommended to use different WLS server than the one that comes with EBS
in order to minimize the impact of online patching on the OTL Calendar feature.
You can download the weblogic server (10.3.6) from MOS.
the changes will not take effect until you deploy the ear file on the respective
/F
§ You can read the log data from nohup.out file as shown in the following screenshot
using the command tail –f nohup.out
§ Find the message ‘Server started in RUNNING mode’ to know that the server
started successfully.
§ Please refer to the My Oracle Support Note 974949.1 for details about the
AppsDataSource and on how to configure it in the chapter “Using Oracle E-Business
Suite DataSources”. The sections that are to be followed from the note for this
chapter are:
• 2.1.2. Register the External Node and Generate the Desktop DBC File
§ Once the server is in running mode, launch the Oracle WebLogic Administration
Console for your application server using URL like this one:
e.g.: http://rws3220111.us.oracle.com:7001/console
§ Login with Username and password given during creation of web logic server
§ Click on the New button for Data Sources and select Generic Data Source.
• Select "Oracle's Driver (Thin) for Instance connections; Versions:9.0.1 and later".
• The database administrator must decide the database driver to be used
depending on their database type.
Click Next.
• DB username-apps
Finish.
Note: If the password for apps user is not provided then enter a user who has Apps
Schema Connect role.
§ Navigate to Domain Structure -> Environments -> Deployments and click the
"Install" button.
Give location where the ear file which is extracted from the patch is ftped to
web logic server.
Note: This is the location where you stored the .ear file after the last step from
the step ‘Preparing the deployment file’.
Once ear is deployed and is active to be sure that there is no issue from WLS end.
https://<host>:<port>/
e.g. http://rws3220xyz.com:7010/
§ Set the profile Option at site level “OTL: Calendar View Colors” to
LAVENDAR|ORANGE|TEAL
Navigate to OTL Self Service Timecard Responsibility -> Time –> Calendar.
java.lang.NoClassDefFoundError: oracle/binding/DataControl
Bounce the Weblogic server of adf domain, our deployed application is not compiled
properly, so we need to bounce once to get all the class file are created.
at
oracle.jbo.server.DBTransactionImpl.lookupDataSource(DBTransactionImpl.java:1491)
This is because the PATH and CLASSPATH env variables contain paths leading to the
Oracle E-Business Suite installation are under the same user. Unset these env variables
and set them to default ones and restart the WebLogic server.
The Deployed ADF-Calendar application is https enabled, need to generate the new
certificates for proper hand shake and add the certificates keys in the deployments
configuration.
§ Performance issue, while more than one user using OTL calendar application the
page expires or timed out.
Go to Weblogic server console -> Domain Structure - > Services -> Data Sources - >
<Select the data source > - > Connection Pool - > Maximum Capacity: <big value>.
After the OTL calendar application deployed successfully, go to Self service responsibly ->
Time -> Calendar to launch the calendar. All the time entries recorded in OTL Time store
will be displayed on the ADF calendar in the respective dates in terms of start time & stop
time or Hours recorded for each entry. Existing timecards will be indicated by a band on
the days covered by that timecard period along with the total hours recorded in that
timecard. This helps in easy identification of timecards which have been entered and not
entered.
Timecard and the time entries are represented on the calendar using different color
coding. This color coding’s can be changed by customer using the new profile option OTL:
Calendar View Colors
To set the profile option, choose 3 colors from the above list.
E.g. LAVENDAR|ORANGE|BLUE
Here, the first color, i.e. LAVENDAR specifies the days in which Timecard exists, and the
second color i.e. ORANGE indicates individual Time Entries. The third color, BLUE indicates
presence of events as available in HXC_CALENDAR_EVENTS table.
Effective start date and Effective end date columns in the table tells the system that, this
event is repeated for all the years mentioned.
Points to note
§ The calendar's week start day is based on the user's timecard recurring period
preference.
§ ADF Calendar component is built using ADF development standards and guidelines.
It will use the same http session as of EBS session.
§ Authorized Delegate can see his own timecards only on the calendar, even if
Authorized Delegate has the OTL Self-Service Resource Time Menu attached