Professional Documents
Culture Documents
Please describe your specific skills and achievements under each heading.
Experience with Oracle Weblogic. Please specify number of Servers/Domains, your role, experience with
creating domains, creating weblogic users, deployment, servers clusters … )
Configured almost 15 servers and 60 domains
I have 9 years of deploying web based and web enabled Oracle Forms, Reports and ADF/Java applications on
WebLogic Server (11g, 12c), Oracle Application Server (9i, 10g) and OC4J.
Usually installed, configured, administered and supported 4 WebLogic servers at a time like development,
SIT, UAT and Production running on different Operating Systems (Windows, Unix, Linux or IBM AIX).
Created domains for different applications on development, SIT, UAT and Production WebLogic servers.
Configured LDAP and Oracle Internet Directory for WebLogic Users.
Experience with trouble shooting weblogic issues
I have resolved various issues. Some common issues are as under:-
i) Compatibility Issues:- Before installation, in order to ensure installing compatible JDK, WebLogic
Server and Forms versions, reviewed Oracle Fusion Middleware certification document for compability.
ii) Domain Creation and Configuration for Forms and Reports: After installation of WebLogic Server
and FMW Forms and Reports created domain and configured following main files:-
1. hosts
2. tnsnames.ora
This file is used for database connectivity.
3. formsweb.cfg
This file controls the settings for each Forms application. It has a default section, plus
optional sections for each application, to override the default settings.
4. default.env
This is where environment variables are specified in web enabled forms. The client/server
equivalent is to specify the environment variables in the Windows Registry on Windows
platforms, or on the command line on Unix.
iii) Use Oracle WebLogic Server 11g Administration Console and Oracle Enterprise Manager 11g Fusion
Middleware Control for troubleshooting.
iv) Perform File Operations on Client machine: File operations were performed on WebLogic Server
only. in order to perform file operations on client machines, WEBUTIL technique was used. WEBUTIL
is a pre-packaged set of components focused at solving the more common challenges faced by Forms
developers. Such as, uploading and downloading, files, pictures from client machines.
v) Toolbar button icons Issue: Icons were not shown in web enabled Forms. Icons jar file have been
created and configured in formsweb.cfg.
Experience with FMW 11g? Please specify version and products have been used.
Developed rich web applications using Oracle Application Development (ADF) and deployed on Oracle
WebLogic Server (11g, 12c).
Knowledge of SOA, OSB and Oracle Mobile Application Development Framework (MAF).
Experience with web version of Oracle Forms and Reports administration and support. Experience with trouble
shooting?
o Please specify what version of Oracle Forms and Reports did you use
I have used D2K, Oracle Forms and Reports 6/6i, 9i, 10g,11g and 12c versions
I have also achieved following Oracle Developer certifications:-
i) Oracle Application Developer Certifie0d Professional, Release 2 Effective on: April 16, 2001
ii) Oracle Application Developer Certified Professional, Release 6/6i Effective on: April 16, 2001
iii) Oracle PL/SQL Developer Certified Associate Effective on: November 7, 2000
o Have you already installed/configured web based version of Oracle Forms and Reports
I have 9 years of experience deploying web enabled Oracle Forms and Reports (11g, 12c) on Oracle
WebLogic Server 11g, 12c versions and deploying web enabled Oracle Forms and Reports (9i, 10g) on Oracle
Application Server 9i, 10g versions.
o Troubleshooting experience. What kind of issues did you resolve?
During upgrading client-server Forms and Reports to Web enabled Forms and Reports or
developing web enabled Forms and Reports, I have resolved various issues. Some common issues
are as under:-
1. Forms Controls
i. In Forms 6i, the canvas properties should (width) x (height) sizes were not set properly.The size
was larger, scroll bars came up on the screen. The complete screen was not visible, re-arranged
the items on the screen so that the complete screen wass visible at a time and a scrollbar was not
shown on the window. Canvas view size was not exceeded the window size.
ii. Minimum size of LOV was set ------- as width and --------as height. List of values were
appeared at the left top corner (1,70). Set property ‘LOV X Position ‘ & ‘LOV Y Position’.
Automatic position property of LOV was set to NO.
iii. While using HOST, TEXT_IO, READ_IMAGE_FILE, DDE, OLE etc I kept in mind that
FORMS (10g / 11g) is a three tier architecture, hence normal file operations were performed on
middle tier i.e Web Server (Oracle Application Server / WebLogic Server) and not the Client
PC. In case File operations were to be performed on client machines and not on Web Server
then WEBUTIL technique need to be used.
iv. Avoided using Timer events as they show the performance on web drastically.Some Oracle
Forms built-ins resulted in a roundtrip from the client to the server. So, they caused
performance issue. They have been deleted or modified.
1. Synchronize built-ins
2. Timers
v. All the PL/SQL Libraries and Menu modules were complied into higher versions before the
compilation of the Form modules.
vi. hide_menu built in was not supported any more. hide_menu was commented in form modules.
i. Whenever ‘CALL_FORM’ was used for calling form, then used ‘HIDE’.
ii. Check all forms for occurrence of CALL_FORM. The first parameter (form name specified in
the string) should be in capital letters. This is required when the form runs on UNIX
environment.
1. When-Timer-Expired
2. When-Mouse-Enter
3. When-Mouse-Up
4. When-Mouse-Down
5. When-Window-Deactivated
iv. ICONIC Files are not supported on Web. Instead Use Image File in GIF format.
v. HOST_COMMAND, ORA_FFI, USER_EXIT are supported but users cannot see visual Output
or Interact with them.
4. Invoking Reports from Forms
i. RUN_PRODUCT is no more supported for running reports from Forms. Instead
RUN_REPORT_OBJECT should be used. Reports can have HTML, PDF, TEXT formats etc.
ii. WEB.SHOW_DOCUMENT can be used to run reports.
5. Character Mode Reports
Character mode reports are not supported. Character mode reports are to be changes into GUI
reports.