Difference between 11i/R12.1.3

1)By default form server is running socket mode in oracle application 11i and in R12 forms are running in Servlet mode.

Socket
+++++
Dedicated connection between client and server.
less secure
more network traffic.
High load on the server.

Servlet
++++++++
more secure
less network traffic
less load on the server

2)in Oracle Apps 11i we use to apply patches on 806/817 home using patch.sh script where as in R12 we use to apply using opatch.
3)INST TOP is introduce in Oracle Application 12.1.3 where all the configuration files,dbc file and port files are kept.
4)When form server is running in socket mode we can grep the process using ps -ef|grep -i frmweb and when it is running in servlet mode we can grep process using
ps -ef|grep -i http.

5)Report server is obsolete in Oracle Application 12.1.3 and running via concurrent manager.
6)After changing apps password through FNDCPASS it doesnot require to run AUTOCOFNIG or change some property or configuration file in R12 where as in oracle application
we do perform this task.
7)In ad_bugs table language column has been added to identified NLS patches has been applied to system.
8)We will compile forms in oracle application 11i using f60gen and where as in R12 we do compile using frmcmp_batch.


Jserver
++++
Jserver was build on c and c++ language and it is not compitable to run fusion middleware type of applications thus oracle removed this application server in R12.


OC4J
+++
OC4J was a product of a company a called orion flare.
Oracle bought and renamed to OC4J (Oracle Container for Java) which is compitable to run Fusion
Middleware types of application.


Hope , you enjoyed reading the difference between oracle application 11i and R12.

Thanks for visting my blog.

Difference between Web server/Application Server

Web Server
+++++++++
1)It is used to display static pages/html pages in web browser.It can't host EJBs.
2)Web server will accept http and https requests or support two protocols.
3)It does not support transactions itself or database connection pooling.
4)It has only one containter that is web contianer.
5)It acts as a proxy server or forward the request to application server.


Application server

+++++++++++++++++++
Application server execute business logic by interact with different client.
1)It is used to display the dynamic pages or content.
2)Application server will accept different proctocols http/SNMP/T3/LDAP/RMI/RPC  etc.
3)support tx
4)It has two or more container.

web,EJB,WS and JMS.

App Server have components and features to support Application level services such as Connection Pooling, Object Pooling, Transaction Support, Messaging services etc.

ERROR: Edit session is enabled in the patch file system.

issues
+++++


adop phase=prepare got failed with below error message .


=======================================
validateEditLockEnabled ...
=======================================

ERROR: Edit session is enabled in the patch file system.
Corrective Action:Release the edit lock and  retry the adop operation.

==========================================
validateJDBCDescriptor ...
==========================================

Solution
++++++++
Adop Prepare Phase Failed On TxkADOPValidation ERROR: Domain is not in edit mode. Validating /config/edit.lok file in patch file system (Doc ID 1920804.1)

Do this in patch file system.

/u01/apps/TEST/fs2/FMW_Home/user_projects/domains/EBS_domain_TEST
[apptest@ebscrp EBS_domain_TEST]$ mv edit.lok edit.lok_old
[apptest@ebscrp EBS_domain_TEST]$


2. Source the patch file system environment.

3. Execute:

cd $ADMIN_SCRIPTS_HOME
./adadminsrvctl.sh stop forcepatchfs

4. Re-run prepare:
 
  adop phase=prepare

Closing socket as no data read from it on 10.xx.xx.xx:14,525 during the configured idle timeout of 5 secs+OTM 637

Issue
+++
INFO | 2016/04/09 23:18:31 | <Apr 9, 2016 11:18:31 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.xx.xx.xx:14,525 during the configured idle timeout of 5 secs>
INFO | 2016/04/09 23:18:31 | <Apr 9, 2016 11:18:31 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.xx.xx.xx:14,524 during the configured idle timeout of 5 secs>
INFO | 2016/04/09 23:18:31 | <Apr 9, 2016 11:18:31 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.xx.xx.xx:61,991 during the configured idle timeout of 5 secs>
INFO | 2016/04/09 23:18:31 | <Apr 9, 2016 11:18:31 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.xx.xx.xx:61,990 during the configured idle timeout of 5 secs>

Solution
++++++++
As per the update received from the development team, those are just connections from the Weblogic to another server timing out because there was no activity.

[weblogic.transaction.TxTimer: '1'] but has failed to stop it.This is very likely to create a memory

When we stop otm application services , we have seen above error mesage in otm console log file of web server .


Solution
++++++
The process is stopping, so this error message can just be ignored.
The errors are from the Weblogic threads that are started up in the background to communicate with the Weblogic server.