Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

Friday, May 14, 2021

Socket & Servlet Mode:

 When forms run SOCKET Mode these are dedicated connection between Client Machine & Form Server (Started by adfrmctl.sh).

Socket mode allows desktop clients to access the Forms Server directly.

When Forms run in servlet mode the forms requests are fulfilled by Jserv in Apache . There will be additional JVM for Forms Request in that case and you won’t start form via adfrmctl.sh.

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

servlet is  more secure as compared to Forms Socket Mode.

In Servlet mode no additional certificate is required during SSL implementation for application tier, single certificate will handle both forms & web connection.

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

By default in R12 forms mode is servlet and 11i is Socket.

To check  form service is in servlet or socket mode :

$ ./adformsctl.sh status

We can check it from front end also as follows.

Log in to Oracle Applications and launch a Forms-based application.

Open the Sun Java Console (from Tools Menu in Internet Explorer).

Check whether the "mode" directive displayed in Sun Java Console when

launching forms-based applications, is set to HTTP.

Direct Forms Servlet Launch is:

web_protocol>://.:/forms/frmservlet 


To check if it is socket from front end do as follows

Log in to Oracle Applications and launch a Forms-based application.

Open the Sun Java Console (from Tools Menu in Internet Explorer).

Check whether the "mode" directive displayed in Sun Java Console when

launching forms-based applications is set to socket.

The direct launch URL for Forms Socket Mode is:

://.:/OA_HTML/frmservlet 


Manually Starting/stoping/status of Forms Server in socket mode:

$INST_TOP/admin/scripts/adformsrvctl.sh start

$INST_TOP/admin/scripts/adformsrvctl.sh stop

$INST_TOP/admin/scripts/adformsrvctl.sh status 


Convert from Servlet mode to Socket mode:

Stop all the application tier services:

Run the following command to enable Forms Socket Mode:

$FND_TOP/bin/txkrun.pl -script=ChangeFormsMode \

[-contextfile=] \

-mode=socket \

[-port=] \

-runautoconfig= \

-appspass= 


$INST_TOP/appl/admin/.xml

-mode servlet - to enable Forms Servlet mode. This is the default value.

-socket - to enable Forms Socket mode

-port : Port number used to run Forms in socket mode. The default port number

is 9095.

A port number is not needed if servlet mode is used.

-runautoconfig : Specify whether AutoConfig should be run after changing the

forms mode. Possible values are as follows:

No : Do not run AutoConfig after enabling Forms servlet/socket mode. This is the

recommended value.

Yes : Run AutoConfig after enabling Forms servlet/socket mode.

-appspass :Password for the applications.

Thursday, October 22, 2020

OAM, OID and OIM:

 OAM: Oracle Access Manager:

OAM is the access manager, where we have abilities such as Single Sign On (SSO),Authentication

Authorization, Real time session management, Auditing and Policy Administration.

3 consoles in OAM i.e. Weblogic Console(/console), Enterprise Manager Console(/em), OAM Console (/oamconsole) in Oracle Access Manager.

Three main Consoles in OAM mainly

a) OAM Console : To register and manage system configurations, security elements, and policies.

b) WebLogic Console : Used by Administrators to Manage & Configure WebLogic Server (J2EE Server) on which OAM is deployed

c) FMW EM Console : Used by Administrators to Manage & Configure OAM Application


OID: Oracle Internet Directory:

OID is a LDAP implementation like Active Directory/AD. This is where users are stored for OAM.

Learn how to Install, Configure, Start/Stop OID, and how to Create a User/Group in OID. How to install Oracle WebLogic Server, how to install & configure IDM for OID server and how to verify WebLogic console and ODSM console.

OIM: Oracle Identity Manager:

OIM does life cycle management of a user or any similar entity. We may use OIM to provision the users. So basically it serves user management and reconciliation activities. If We have OIM, we can provision accounts to EBS or reconcile users from EBS to OIM.

when an employee is joined to your organization, you just create his user in  OIM and then reflect the necessary user/account definitions to the EBS .. FND_USER account, PERSON definitions etc.

When will OIM come into picture? Is this required for EBS?

Why does EBS require OID with OAM?

Reconciliation is for updating the Oracle Identity Manager. Provisioning is to put data from Oracle Identity Manager to another system.

Oracle Internet Directory (OID) : An LDAP directory server that stores its data in an Oracle database.

Oracle Identity Manager (OIM) : User Provisioning product acquired from Thor. It includes also reconciliation and administration tools. Reconciliation is the process by which operations, such as user creation, modification, or deletion, started on the target system are communicated to Oracle Identity Manager. The reconciliation process compares the entries in Oracle Identity Manager repository and the target system repository, determines the difference between the two repositories, and applies the latest changes to Oracle Identity Manager repository. In terms of data flow, provisioning provides the outward flow from the provisioning system (Oracle Identity Manager) by using a push model, in which the provisioning system indicates the changes to be made to the target system. Reconciliation is for updating the Oracle Identity Manager. Provisioning is to put data from Oracle Identity Manager to another system.

https://www.learn-it-with-examples.com/middleware/oracle-iam/oiam-architecture/oracle-identity-management-architecture-overview.html



Friday, October 16, 2020

TNS-01201: Listener cannot find executable :

 TNS-01201: Listener cannot find executable :

when starting listener getting error:

lsnrctl start LISTENER

TNS-01201: Listener cannot find executable

commented the entry in listener file:

diff listener.ora_10152020 listener.ora

43,52c34,43

< SID_LIST_LISTENER =

<    (SID_LIST =

<       (SID_DESC =

<         (GLOBAL_DBNAME = SID)

<           (ORACLE_HOME = /mnt/app/oracle/product/12.2.0/dbhome_1)

<            (SID_NAME = SID)

<       )

<      )

---

> ##SID_LIST_LISTENER =

> ###   (SID_LIST =

> ###      (SID_DESC =

> ###        (GLOBAL_DBNAME = SID)

> ##          (ORACLE_HOME = /mnt/app/oracle/product/12.2.0/dbhome_1)

> ###           (SID_NAME = SID)

> ###      )

> ###     )