Oracle Apps R12 Forms : Servlet or Socket

Default Forms connection mode in Oracle Applications R12 is “SERVLET” where as in Oracle Apps 11i default form connect mode is “SOCKET” So

What is difference between socket and servlet mode in Forms ?
What are advantages and disadvantages of each ?
Can we change default R12 forms mode from servlet to Socket ?

Oracle Form Servlet Overview in apps R12
——————————————

i) In this mode, Java servlet handles communication between forms client(java based) and Oracle Forms Service (10g).

ii) All connection is via HTTP Server so there is no need to start form server and no need to open form server port on firewall between client machine and application tier.

iii) More secure as compared to Forms Socket Mode.

iv) Network traffic is more as HTTP protocol is more chatty so little bit network bandwidth hungry when compared with SOCKET mode

v) No additional certificate requirement during SSL implementation for application tier, single certificate will handle both forms & web connection.

How to change from default Servlet mode (in apps R12) to Socket mode ?
———————————————————————

Refer to Oracle Metalink Note # 384241.1 Using Forms Socket Mode with Oracle E-Business Suite Release 12

Are there any network overheads of using Forms in Servlet Mode ?
—————————————————————-

Metalink Note # 311091.1 Understanding the Network Overhead Of Forms Servlet Listener Architecture Compared to Forms Server, covers some interesting points w.r.t. network traffic

Advantage & Disadvantages of Forms Servlet Mode

———————————————————-
– Simple SSL Configuration (as no separate ssl configuration is required for Forms as connections are via web/http server)

– No port need to open to access forms in firewall

– More secure method of deployment over Internet

– Result in more network traffic because of HTTP is more chatty than socket (dedicated) so not preferred in WAN implementation.

Difference between Oracle Apps 11i and R12

Database:
Database Version in 11i (11.5.9 & 11.5.10) was 9i Rel 2 where as in Release 12 its 10g R2 (10.2.0.2)

Application Tier:
Tech Stack in Application Tier consist of iAS(1.0.2.2.2) & Developer 6i (Forms & Reports 8.0.6) but in Applications R12 it is build on Fusion Middleware (10g Web Server and 10g Forms & Reports)

Sub component in Application Tier
A) HTTP Server or Web Server in R12 is Version 10.1.3 which is built on Apache version 1.3.34. In apps 11i it is Version 1.0.2.2.2 built on Apache Version 1.3.19
B) Jserv in apps 11i is replaced by OC4J (mod_jserv is replaced by mod_oc4j)
C) Forms Version 6i in Apps 11i is replaced by Forms 10.1.2.0.2 in R12
D) Reports Version 6i in Apps 11i is replaced by Reports 10.1.2.0.2 in R12
E) JDBC version is changed from version 9 in apps 11i to version 10.2.0 in Apps R12
F) modplsql or mod_pls is removed from Apps R12 (What will happen to my mod plsql applications- coming soon* )
G) Java processes use JDK/JRE version 1.5.0 in R12 against JDK version 1.3.1 or 1.4.2 in Apps 11i
H) For various environment variable changes check below picture

I) New top INSTANCE_TOP added in Release 12 for configuration and log files

Clone Apps 11i Instance

Cloning is process of creating replica of your source apps 11i Instance ( lets say you have one apps Instance with name VISIONTST and you want to create similar instance ( including same patches & user data) like VISIONPRD then you will use adclone utility (Also called as Rapid Clone these days). In this case source Instance will be VISIONTST and target Instance will be VISIONPRD. There are lot for scenario in which you wish to clone your E-Business Suite 11i Instance , like you want to Test if everything is OK in Test & then after testing want to create Production instance or you want to move your Instance from one machine to other machine or if you are highly experienced Apps DAB you can use clone as staged environment during Upgrade to reduce downtime ( this concept is called as staged appl_top or staged patching/upgrade , p.s. this is different from shared APPL_TOP)

So here I am putting broad level steps you will use to clone apps instance .

Step1 . Prerequisites Steps you do before start cloning using rapid clone
1.1 Verify source and target nodes software versions
1.2 Apply the latest AutoConfig Template patch
1.3 Apply the latest Rapid Clone patches

Step2 . Clone Source to Target
2.1 Run preclone on DB tier
2.2 Run preclone on Apps or middle tier
2.3 Copy source file system to target file system
2.4 Configure db tier
2.5 Configure apps/middle tier

Step 3 Finishing Task
3.1 Update profile options
3.2 Update printer settings (If printers are not configured or you don’t want to use printer you can skip this step)
3.3 Update workflow configuration settings (Important)

ADPATH Options

adpatch option=[option1,option2, ….optionN]

Below is option value with explanation
options=noautoconfig If you are applying number of patches out of which 4-5 patches run autoconfig then use this option & run autoconfig in last patch or manually (This will save your patching timing , first patch performance tip )
compiledb(def) or nocompiledb Use no compiledb if you have multiple patch then compile database objects in last patch
compilejsp(def) or nocompilejsp Use no compilejsp if you have multiple patch then compile jsp in last patch
copyportion Tells adpatch whether to run commands normally found in a copy driver.
databaseporion Tells adpatch whether to run commands normally found in a database driver.
generateportion Tells adpatch whether to run commands normally found in a generate driver
hotpatch Tells AutoPatch to apply a patch regardless of whether the Oracle Applications system is in maintenance mode.
integrity Tells adpatch whether to perform patch integrity checking, which verifies that the version of each file referenced in a copy action matches the version present in the patch (There are overheads with this)
maintainmrc Tells adpatch whether to automatically maintain the MRC schema after running actions normally found in the database driver. The MRC schema is only maintained if the MRC feature is enabled
prereq Tells adpatch whether to perform prerequisite patch checking prior to running patch driver files that contain actions normally found in the copy driver. (With lateset AD patch , default behaviour is changed from prereq to noprereq)
forcecopy The forcecopy command copies the files in a patch to the Applications file system without comparing the version number of the patch files with existing files

Oracle Apps Patch Basics

Standalone/Oneoff patches : This is used to define patch created to fix single/particular problem.
Mini Pack : This is group of oneoff patches for a particular product like INV, GL, AP and named like 11i.GL.E ( means this group of patches contain fix for 11i GL product (General Ledger till time E is released ) This is cummutative which means it will include 11i.GL.A, 11i.GL.B ….11iGL.D till 11i.GL.E earlier in 10.7 it used to called as patchset.
Family Pack : Group of mini packs in one family buldeled together is called as family pack. they are usually named as 11i_PF. Few example of falilies are SCM ( 11i.SCM_PF.G ), ATG ( 11i.ATG_PF.H ) _PF indicate Product Family Pack
Maintenance Pack : Group of family pack together is called as maintenance pack. So if you say your Verison is 11.5.10 then its maintenance pack 10 ( 3rd digit is maintenance pack ) so

To wind up things you can say

few one off patch make mini pack , few mini pack related to same family bundeled together as family pack & all family pack fixed till that time are bundeled in Maintenance pack .

NLS Patch ( When you have more than one language , like english & arabic or french .. ) then apart from normal patch you have to apply patch for specific language Installed in your system called as NLS patch.

Oracle Workflow Notification Mailer

Oracle Workflow in itself is a Product which is tough to cover in this blog but I am going to cover few important & frequently used components from Oracle Apps DBA point of view which is Workflow Notification Mailer .

Currently with OWF.H (Oracle Work Flow Minipack H) or 11.5.10 Oracle Applications Uses Java Mailer & before that it used to be C Mailer. Some of you who are on 11.5.8 or lower version might still be using wfmail.cfg under FND_TOP . Configuration is quite simple via OAM (Oracle Application Manager) provided you or your unix team setup inbound & outbound mails set up correctly. Notification Mailer will inturn use Operating System command/mail for inbound(for receiving mail) & outbound(for sending mails). At end of this post you can find few metalink notes which cover all things you require to configure Workflow Notification Mailer.
In 11.5.10 Java Notification Mailer is available out of the box , you simply need to configure via Oracle Application Manager .
Below metalink Notes should be enough to configure Workflow Notification Mailer & troubleshooting Mailer ..

Related Links

Metalink Note #

268085.1 Configuring the Oracle Workflow 2.6/11i.OWF.H Java-based Notification Mailer with Oracle Applications 11i

164871.1 Configuring the Workflow Notification Mailer in Oracle Applications Manager 11i

172174.1 WF 2.6: Oracle Workflow Notification Mailer Architecture in Release 11i

Is Oracle Fusion really ConFUSION ?

If you ask question “What is Oracle Fusion ?” to yourself I suppose every one will have different opinion. I would like to hear from you all in your words ( via comments on this post ) about what you think is Oracle Fusion .

Common confusion over Oracle Fusion
Most Common confusion over Fusion among most of guys I discuss/meet & also mentioned by Steven Chan in his post is thinking Oracle Fusion Middleware & Oracle Fusion Applications are same. In actual Oracle Fusion Middleware will be used in providing/building Oracle Fusion Applications using Existing Oracle Applications (Oracle E-Business Suite, Siebel, Peoplesoft, JD Eward).

Oracle Fusion Middleware is collection of Oracle Middleware products i.e.
–Oracle Application Server (Portal, Wireless, Forms, Reports, discoverer, Webcache, OC4J)
– Oracle Identity management (OID, SSO, Web Access Manager, CA, Identity Federation)
–Oracle SOA Suite (Service Oriented Suite)
–Oracle Collaboration Suite (RTC, Mail Server, Discussion, Content, Calendar)
–Oracle DW & BI (BI Beans, OWB, OLAP, Express Server, OSA, OFA, Datamart )
–Oracle development Tools (Designer, developer, SCM, forms, reports)
– Oracle Data hubs

and
Oracle Fusion Applications will be collection of Oracle Applications i.e.
–Oracle E-Business Suite / CRM
–Oracle Peoplesoft enterprise
–Oracle Siebel CRM
–Oracle JD Edward Enterprise

These fusion applications will use Fusion Middleware mentioned above

Few links which talk about Oracle Fusion Middleware & Fusion Applications are

http://blogs.oracle.com/schan/newsItems/departments/fusionApps

http://oracle.anilpassi.com/oracle-fusion-development-tools.html (Good one for developers & techno functional)

http://blog.oraclecontractors.com/?cat=4

http://www.oracle.com/applications/fusion.html (Good one for Oracle Fusion Applications Road Map)

More on Service Oriented Architecture (SOA Suite) and Oracle Fusion coming soon…