Skip to main content

Understanding -msimode for managed servers and how it can be used with Oracle EBS r12.2

 Recently, I was asked implications of Admin server availability when connecting to Oracle EBS login Page.
When pondering further, Few scenarios that arise were -
1. What if running Admin server goes down for some reason, will this impact managed servers that are already running?
2. Can we start managed server (say oacore_server1) if admin server is down? How?

Let's start understanding relationship between admin server and managed server.

Admin server 

is the central entity for configuration of entire domain. You manage and 
configure all resources in the domain through admin server. Config.xml is loaded
by Admin server during its startup. This file is stored under -
$FMW_Home/user_projects/domains/EBS_domain/config

Managed server 

is responsible for hosting components and associated resources that comprise your application (ex. JSPs, EJBs,datasources,JMS Modules,etc).

During startup of managed server, it will reach out to admin server and get configuration and deployment settings. This pretty much the second question-- 

Can we start managed server (say oacore_server1) if admin server is down? How?

But there is a catch here, we have MSI mode for managed servers to skip this dependency. MSI stands to Managed Server Independence

During Startup -

Managed Server ---> configuration files ---> Admin server 

if Admin server is down ---> Managed server fails to start

If Managed server has MSI enabled(by default enabled) 

                                --> use -msimode option

                                    --> managed server starts by directly accessing configuration/security files


By default, MSI is enabled and below navigation can be used to check the same -

Environment 

          > Servers  

    > Select Managed server(say oacore_server1)

> Tuning>(scroll down)

       > Advanced

       >Checkbox for MSI





Using MSI mode with oacore_server1 managed server -

admanagedsrvctl.sh start oacore_server1 -msimode                        


Coming onto 1st question, 

What if running Admin server goes down for some reason, will this impact managed servers that are already running?

1. If servers(admin and managed) are on same host machine, typically the case in a single node ebs environment, then obviously all servers will have similar implications.

2. If only the admin server is down while managed servers are up and running, failure of an Administration Server itself does not interrupt the operation of Managed Servers in the domain

Ref- https://docs.oracle.com/cd/E13222_01/wls/docs90/domain_config/understand_domains.html


Note: When admin server is down, each Managed Server periodically attempts to reconnect to the Administration Server to synchronize its configuration state with that of the Administration Server.


Concluding Thoughts - 

It is important to understand dependency between admin server and managed server when starting up application services as there may be scenarios when managed servers would be waiting for admin server for EBSDomain to start and eventually result in overall availability of the system. -msimode may be used to independently start a managed server when admin server is not available and root cause of admin server can be fixed later.





Comments

Post a Comment

Popular posts from this blog

Logfile locations in EBS r12.1 and EBS r12.2

Startup/shutdown Apps tier services are started and stopped frequently and we must know logfiles when troubleshooting startup/shutdown issues. $INST_TOP/logs/appl/admin/log $INST_TOP/logs/appl/admin/log Apache OHS being part of opmn in r12.1 has continued in r12.2. Logfile locations for troubleshooting have been changed $INST_TOP/logs/ora/10.1.3/Apache/error_log[timestamp] $INST_TOP/logs/ora/10.1.3/opmn/HTTP_Server~1.log $IAS_ORACLE_HOME/instances/*/diagnostics/logs/OHS/*/*log*   OPMN Logfile locations for r12.1 and r12.2 have been changed $INST_TOP/logs/ora/10.1.3/opmn/opmn* $IAS_ORACLE_HOME/instances/*/diagnostics/logs/OPMN/opmn/* Oacore oacore in r12.1 is oc4j component and part of 10gAS. However, in r12.2, oacore is now a managed server for weblogic server $LOG_HOME/ora/10.1.3/j2ee/oacore/oacore*/ $LOG_HOME/ora/10.1.3/j2ee/oacore/oacore*/ $LOG_HOME/ora/10.1.3/opmn/oacore*/oacor...
1 comment
Read more

Query to Check AD and TXK code levels in your EBS environment

Below query can be very handy in finding out current AD and TXK code levels. col ABBREVIATION for a10 set lines 1000 col NAME for a50 col CODELEVEL for a20 SELECT ABBREVIATION,NAME,codelevel FROM AD_TRACKABLE_ENTITIES WHERE abbreviation in ('txk','ad'); ABBREVIATI NAME                                                CODELEVEL ---------- -------------------------------------------------- ------------ ad           Oracle Applications DBA                             C.11 txk         Oracle Applications Technology Stack    ...
1 comment
Read more

Compile all JSP files in Oracle ebs r12.2

Before you start compiling jsps and following below steps, I recommend understanding some key differences between 11i, r12.1 and r12.2 when it comes to compiling jsps. Please follow below link and then proceed further - One-stop shop to Compile JSPs in 11i, r12.1 and r12.2 1. Take a backup of _pages directory that will be modified due to jsp compilation - $ cd $EBS_APPS_DEPLOYMENT_DIR/oacore/html/WEB-INF/classes/ $ cp -R _pages _pages29dec2019 $ ls -ld _pages* drwxr-xr-x 5 applmgr oinstall 249856 Dec 29 16:36 _pages drwxr-xr-x 5 applmgr oinstall 249856 Dec 29 16:56 _pages29dec2019 2. Stop apache, oacore and oafm services - adapcctl.sh stop admanagedsrvctl.sh stop oacore_server1 admanagedsrvctl.sh stop oafm_server1 3. Compile the jsps manually using the below command - $ cd $FND_TOP/patch/115/bin/ $ perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile --flush -p              4. Check class file last mo...
Post a Comment
Read more