Forms Servlet mode to Socket mode Release 12 Apps   Leave a comment

Forms Servlet mode to Socket mode conversion on Release 12 Apps

 

How to convert Forms server to Socket mode from Servlet mode in Oracle Apps R12

Run the following command to enable Forms Socket Mode on Forms/web nodes (Place correct context file name and port value)

$FND_TOP/bin/txkrun.pl -script=ChangeFormsMode -contextfile=$CONTEXT_FILE -mode=socket -port=9030 -runautoconfig=No

Where port = forms port and contextfile=your environment contextfile

To Start/Stop/check Status of forms servers use following scripts

cd $ADMIN_SCRIPTS_HOME
./adformsrvctl.sh status/stop/start

How to find forms mode of connection in R12

[applmgr@r12 ~]$ grep frmConnectMode $CONTEXT_FILE

<forms_connect oa_var=”s_frmConnectMode”>servlet</forms_connect>

Let’s convert Servlet to Socket.

Step1: Shutdown the application Tier Services.

[applmgr@r12 scripts]$ sh adstpall.sh apps/apps

[applmgr@r12 scripts]$ $FND_TOP/bin/txkrun.pl -script=ChangeFormsMode -contextfile=$CONTEXT_FILE -mode=socket -port=9030 -runautoconfig=No

*** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS

*** Log File = /d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/rgf/TXK/txkChangeFormsMode_Wed_May_15_10_56_04_2013.log

Program : /d01/oracle/PROD/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkChangeFormsMode.pl started @ Wed May 15 10:56:04 2013

*** Log File = /d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/rgf/TXK/txkChangeFormsMode_Wed_May_15_10_56_04_2013.log

Arguments passed: -contextfile=/d01/oracle/PROD/inst/apps/PROD_r12/appl/admin/PROD_r12.xml -mode=socket -port=9030 -runautoconfig=No

———–

Values used

———–

Context File   : /d01/oracle/PROD/inst/apps/PROD_r12/appl/admin/PROD_r12.xml

Mode           : socket

Port           : 9030

Run AutoConfig : No

Execute SYSTEM command : netstat –a

[applmgr@r12 scripts]$ $FND_TOP/bin/txkrun.pl -script=ChangeFormsMode -contextfile=$CONTEXT_FILE -mode=socket -port=9030 -runautoconfig=No

*** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS

*** Log File = /d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/rgf/TXK/txkChangeFormsMode_Wed_May_15_10_56_04_2013.log

Program : /d01/oracle/PROD/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkChangeFormsMode.pl started @ Wed May 15 10:56:04 2013

*** Log File = /d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/rgf/TXK/txkChangeFormsMode_Wed_May_15_10_56_04_2013.log

Arguments passed: -contextfile=/d01/oracle/PROD/inst/apps/PROD_r12/appl/admin/PROD_r12.xml -mode=socket -port=9030 -runautoconfig=No

———–

Values used

———–

Context File   : /d01/oracle/PROD/inst/apps/PROD_r12/appl/admin/PROD_r12.xml

Mode           : socket

Port           : 9030

Run AutoConfig : No

Execute SYSTEM command : netstat –a

********************************

Backing up context file….

********************************

Context file backed up at: /d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/rgf/TXK/Wed_May_15_10_56_04_2013/PROD_r12.xml

********************************

Changing to Socket Mode…….

********************************

Updating context Variable s_forms_servlet_serverurl….

Updated context Variable s_forms_servlet_serverurl to

Updating context Variable s_frmConnectMode….

Updated context Variable s_frmConnectMode to socket

Updating context Variable s_formsstatus….

Updated context Variable s_formsstatus to disabled

Updating context Variable s_formsserver_status….

Updated context Variable s_formsserver_status to enabled

Updating context Variable s_other_service_group_status….

Updated context Variable s_other_service_group_status to enabled

Updating context Variable s_formsport….

Updated context Variable s_formsport to 9030

Updating context Variable s_formslauncher_path….

Updated context Variable s_formslauncher_path to OA_HTML/frmservlet

********************************************************************************

You should run Autoconfig to update the runtime configurations to new Forms Mode.

********************************************************************************

 

Log file to change the Forms Mode :

/d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/rgf/TXK/txkChangeFormsMode_Wed_May_15_10_56_04_2013.log

Program : /d01/oracle/PROD/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkChangeFormsMode.pl completed @ Wed May 15 10:56:39 2013

End of /d01/oracle/PROD/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkChangeFormsMode.pl : No Errors encountered

[applmgr@r12 scripts]$ sh adopmnctl.sh startall

You are running adopmnctl.sh version 120.6

adopmnctl.sh: exiting with status 0

adopmnctl.sh: check the logfile /d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/admin/log/adopmnctl.txt for more information …

********************************

Backing up context file….

********************************

Context file backed up at: /d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/rgf/TXK/Wed_May_15_10_56_04_2013/PROD_r12.xml

********************************

Changing to Socket Mode…….

********************************

Updating context Variable s_forms_servlet_serverurl….

Updated context Variable s_forms_servlet_serverurl to

Updating context Variable s_frmConnectMode….

Updated context Variable s_frmConnectMode to socket

Updating context Variable s_formsstatus….

Updated context Variable s_formsstatus to disabled

Updating context Variable s_formsserver_status….

Updated context Variable s_formsserver_status to enabled

Updating context Variable s_other_service_group_status….

Updated context Variable s_other_service_group_status to enabled

Updating context Variable s_formsport….

Updated context Variable s_formsport to 9030

Updating context Variable s_formslauncher_path….

Updated context Variable s_formslauncher_path to OA_HTML/frmservlet

********************************************************************************

You should run Autoconfig to update the runtime configurations to new Forms Mode.

********************************************************************************

 

Log file to change the Forms Mode :

/d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/rgf/TXK/txkChangeFormsMode_Wed_May_15_10_56_04_2013.log

 

Program : /d01/oracle/PROD/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkChangeFormsMode.pl completed @ Wed May 15 10:56:39 2013

 

End of /d01/oracle/PROD/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkChangeFormsMode.pl : No Errors encountered

[applmgr@r12 scripts]$ sh adopmnctl.sh startall

 

You are running adopmnctl.sh version 120.6

 

adopmnctl.sh: exiting with status 0

adopmnctl.sh: check the logfile /d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/admin/log/adopmnctl.txt for more information …

[applmgr@r12 scripts]$ sh adautocfg.sh

Enter the APPS user password:

 

The log file for this session is located at: /d01/oracle/PROD/inst/apps/PROD_r12/admin/log/05151113/adconfig.log

 

AutoConfig is configuring the Applications environment…

AutoConfig will consider the custom templates if present.

Using CONFIG_HOME location     : /d01/oracle/PROD/inst/apps/PROD_r12

Classpath                   : /d01/oracle/PROD/apps/apps_st/comn/java/lib/appsborg2.zip:/d01/oracle/PROD/apps/apps_st/comn/java/classes

Using Context file          : /d01/oracle/PROD/inst/apps/PROD_r12/appl/admin/PROD_r12.xml

 

Context Value Management will now update the Context file

Updating Context file…COMPLETED

Attempting upload of Context file and templates to database…COMPLETED

Configuring templates from all of the product tops…

Configuring AD_TOP……..COMPLETED

Configuring FND_TOP…….COMPLETED

Configuring ICX_TOP…….COMPLETED

Configuring MSC_TOP…….COMPLETED

Configuring IEO_TOP…….COMPLETED

Configuring BIS_TOP…….COMPLETED

Configuring AMS_TOP…….COMPLETED

Configuring CCT_TOP…….COMPLETED

Configuring WSH_TOP…….COMPLETED

Configuring CLN_TOP…….COMPLETED

Configuring OKE_TOP…….COMPLETED

Configuring OKL_TOP…….COMPLETED

Configuring OKS_TOP…….COMPLETED

Configuring CSF_TOP…….COMPLETED

Configuring IGS_TOP…….COMPLETED

Configuring IBY_TOP…….COMPLETED

Configuring JTF_TOP…….COMPLETED

Configuring MWA_TOP…….COMPLETED

Configuring CN_TOP……..COMPLETED

Configuring CSI_TOP…….COMPLETED

Configuring WIP_TOP…….COMPLETED

Configuring CSE_TOP…….COMPLETED

Configuring EAM_TOP…….COMPLETED

Configuring FTE_TOP…….COMPLETED

Configuring ONT_TOP…….COMPLETED

Configuring AR_TOP……..COMPLETED

Configuring AHL_TOP…….COMPLETED

Configuring OZF_TOP…….COMPLETED

Configuring IES_TOP…….COMPLETED

Configuring CSD_TOP…….COMPLETED

Configuring IGC_TOP…….COMPLETED

AutoConfig completed successfully.

 

 

 

 

[applmgr@r12 scripts]$ sh adopmnctl.sh startall

 

You are running adopmnctl.sh version 120.6

adopmnctl.sh: exiting with status 0

 

adopmnctl.sh: check the logfile /d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/admin/log/adopmnctl.txt for more information …

 

[applmgr@r12 scripts]$ sh adformsrvctl.sh status

 

You are running adformsrvctl.sh  version 120.15.12010000.2

 

Checking status of FORMS Server (Socket Mode) …

 

Forms Server (Socket) is not running

adformsrvctl.sh: exiting with status 0

 

adformsrvctl.sh: check the logfile /d01/oracle/PROD/inst/apps/PROD_r12/logs/ora/10.1.2/forms/socket.log for more information …

 

[applmgr@r12 scripts]$ sh adformsrvctl.sh start

 

You are running adformsrvctl.sh  version 120.15.12010000.2

 

Starting FORMS Server in Socket Mode…

adformsrvctl.sh: exiting with status 0

 

adformsrvctl.sh: check the logfile /d01/oracle/PROD/inst/apps/PROD_r12/logs/ora/10.1.2/forms/socket.log for more information …

 

[applmgr@r12 scripts]$ sh adopmnctl.sh status

 

You are running adopmnctl.sh version 120.6

 

Checking status of OPMN managed processes…

 

Processes in Instance: PROD_r12.r12.ora.com

———————————+——————–+———+———

ias-component                    | process-type       |     pid | status

———————————+——————–+———+———

OC4JGroup:default_group          | OC4J:oafm          |   17341 | Alive

OC4JGroup:default_group          | OC4J:oacore        |   17340 | Alive

HTTP_Server                      | HTTP_Server        |   17339 | Alive

 

adopmnctl.sh: exiting with status 0

 

adopmnctl.sh: check the logfile /d01/oracle/PROD/inst/apps/PROD_r12/logs/appl/admin/log/adopmnctl.txt for more information …

 

[applmgr@r12 scripts]$

1

 

2

 

 

What is Forms Servlet Mode?

The Forms Listener Servlet is a Java servlet that delivers the ability to run Oracle Forms applications over HTTP and HTTPS connections. It manages the creation of a Forms Server Runtime process for each client, as well as network communications between the client and its associated Forms Server Runtime process.

The desktop client sends HTTP requests and receives HTTP responses from the web server. The HTTP Listener on the web server acts as the network endpoint for the client, keeping other servers and ports from being exposed at the firewall.

3

What is Forms Socket Mode?

Initial releases of the Oracle Forms Server product used a simple method for connecting the client to the server. The connection from the desktop client to the Forms Listener process was accomplished using a direct socket connection. The direct socket connection mode was suitable for companies providing thin client access to Forms applications within their corporate local area networks. For the direct socket connection mode, the client had to be able to see the server and had to have permission to establish a direct network connection.

Although the direct socket connection mode is perfectly suited for deployments within a company’s internal network, it’s not the best choice for application deployment via unsecured network paths via the Internet. A company connected to the Internet typically employs a strict policy defining the types of network connections that can be made by Internet clients to secure corporate networks. Permitting a direct socket connection from an external client exposes the company to potential risk because the true identity of the client can be hard to determine.

Servlet Mode Advantages

  1. HTTP and HTTPS traffic is easily recognizable by routers, while socket mode communications is generally considered suspect and treated on an exception basis.
  2. Existing networking hardware can be used to support basic functions such as load-balancing and packet encryption for network transit.
  3. More resilient to network and firewall reconfigurations.
  4. More robust: servlet connections can be re-established if network connections drop unexpectedly for Forms, Framework, and JSP-based pages.
  5. Is the only supported method for generic Oracle Forms customers, and therefore is more thoroughly tested by the Forms and E-Business Suite product groups.
  6. Performance traffic can be monitored via tools like Oracle Real User Experience Insight (RUEI).
  7. Socket mode is not supported on Windows-based server platforms.

Socket Mode Advantages

  1. Uses up to 40% less bandwidth than Forms servlet mode. This may be perceived by Wide Area Network (WAN) users as causing slower responsiveness, depending upon network latency.
  2. Uses fewer application-tier JVM resources than servlet mode, due to fewer TCP turns and lack of overhead associated with HTTP POST handling.

Switching Apps Deployments between Modes

Due to its numerous advantages, Forms servlet mode is the preferred and recommended deployment model for Forms on the web.

There may be circumstances where you need to switch between the default Forms modes. You might wish to switch your Oracle E-Business Suite Release 12 environment to socket mode to improve performance or reduce network load. You might wish to switch your Apps 11i environment to servlet mode as part of your rollout to external web-based end-users outside of your organization.

 

 

 

Advertisements

Posted October 29, 2013 by balaoracledba.com in OracleAppsR12

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: