事情起源与在应用层发现一个进程:
[apptest@vs022 bin]$ ps -fu apptest|grep opmn
apptest 19100 1 0 May01 ? 00:00:00 /u01/test/apps/fs2/FMW_Home/webtier/opmn/bin/opmn -d
apptest 19101 19100 0 May01 ? 00:01:54 /u01/test/apps/fs2/FMW_Home/webtier/opmn/bin/opmn -d
apptest 20347 20274 1 May01 ? 01:01:03 /u01/test/apps/fs2/FMW_Home/jrockit32/jre/bin/java -classpath /u01/test/apps/fs2/FMW_Home/webtier/opmn/lib/wlfullclient.jar:/u01/test/apps/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/u01/test/apps/fs2/EBSapps/comn/java/classes
-mx256m oracle.apps.ad.tools.configuration.RegisterWLSListeners -appsuser APPS -appshost vs022 -appsjdbcconnectdesc jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=vs022.hand-china.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=VIS)))
-adtop /u01/test/apps/fs2/EBSapps/appl/ad/12.0.0 -wlshost vs022 -wlsuser weblogic -wlsport 7002 -dbsid VIS -dbhost vs022 -dbdomain hand-china.com -dbport 1521 -outdir /u01/test/apps/fs2/inst/apps/VIS_vs022/appltmp/Thu_May_1_09_57_18_2014 -log /u01/test/apps/fs2/inst/apps/VIS_vs022/logs/appl/rgf/Thu_May_1_09_57_18_2014/adRegisterWLSListeners.log
-promptmsg hide -contextfile /u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml
apptest 28525 27833 0 23:38 pts/2 00:00:00 grep opmn
根据进程20274查找到了父进程:
[apptest@vs022 bin]$ ps -fu apptest|grep 20274
apptest 20274 1 0 May01 ? 00:00:00 perl /u01/test/apps/fs2/EBSapps/appl/ad/12.0.0/bin/adRegisterWLSListeners.pl contextfile=/u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml
apptest 20347 20274 1 May01 ? 01:01:05 /u01/test/apps/fs2/FMW_Home/jrockit32/jre/bin/java -classpath /u01/test/apps/fs2/FMW_Home/webtier/opmn/lib/wlfullclient.jar:/u01/test/apps/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/u01/test/apps/fs2/EBSapps/comn/java/classes
-mx256m oracle.apps.ad.tools.configuration.RegisterWLSListeners -appsuser APPS -appshost vs022 -appsjdbcconnectdesc jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=vs022.hand-china.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=VIS)))
-adtop /u01/test/apps/fs2/EBSapps/appl/ad/12.0.0 -wlshost vs022 -wlsuser weblogic -wlsport 7002 -dbsid VIS -dbhost vs022 -dbdomain hand-china.com -dbport 1521 -outdir /u01/test/apps/fs2/inst/apps/VIS_vs022/appltmp/Thu_May_1_09_57_18_2014 -log /u01/test/apps/fs2/inst/apps/VIS_vs022/logs/appl/rgf/Thu_May_1_09_57_18_2014/adRegisterWLSListeners.log
-promptmsg hide -contextfile /u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml
apptest 28629 27833 0 23:40 pts/2 00:00:00 grep 20274
查看了此脚本产生的日志如下:
[apptest@vs022 bin]$ cat /u01/test/apps/fs2/inst/apps/VIS_vs022/logs/appl/rgf/Thu_May_1_09_57_18_2014/adRegisterWLSListeners.log
Established connection with the WebLogic AdminServer.
Trying to establish connection using the AppsJDBCConnector
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=vs022.hand-china.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=VIS)))
Established the database connection...
Going to download the context file /u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml to /u01/test/apps/fs2/inst/apps/VIS_vs022/appltmp/Thu_May_1_09_57_18_2014/VIS_vs022.xml
Downloaded the context file VIS_vs022.xml from the database to /u01/test/apps/fs2/inst/apps/VIS_vs022/appltmp/Thu_May_1_09_57_18_2014
instantiate file:
source : /u01/test/apps/fs2/EBSapps/appl/ad/12.0.0/admin/template/adWlsAcMappings_xml.tmp
dest : /u01/test/apps/fs2/inst/apps/VIS_vs022/appltmp/Thu_May_1_09_57_18_2014/adWlsAcMappings.xml
WARNING: Unable to load the OHS ObjectNames
Registered notification listener for com.bea:Name=forms-c4ws_server1,Type=Server for the context file /u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml
Registered notification listener for com.bea:Name=forms_server1,Type=Server for the context file /u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml
Registered notification listener for com.bea:Name=oacore_server1,Type=Server for the context file /u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml
Registered notification listener for JMImplementation:type=MBeanServerDelegate for the context file /u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml
Registered notification listener for com.bea:Name=vs022,Type=NodeManager,Machine=vs022 for the context file /u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml
Registered notification listener for com.bea:Name=oafm_server1,Type=Server for the context file /u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml
Registered notification listener for com.bea:Name=ConfigurationManager,Type=weblogic.management.mbeanservers.edit.ConfigurationManagerMBean for the context file /u01/test/apps/fs2/inst/apps/VIS_vs022/appl/admin/VIS_vs022.xml
经过从网上查询,确定了这是一个监听weblogic参数配置变化的进程,这个进程会跟随weblogic 中的Admin server一同启动和关闭:
Run adRegisterWLSListeners Tool on the Application Tier
- The adRegisterWLSListeners tool has been introduced to perform synchronization of context variables with the associated Oracle WebLogic Server configuration parameters.
- This tool does not listen for changes to the Oracle HTTP Server configuration parameters.
- Once started, adRegisterWLSListeners keeps running, listening for changes to the WebLogic Server configuration and synchronizing the context files stored in the database.
- This tools starts/stops along with the WebLogic Admin Server.
Scenario on adRegisterWLSListeners
Run SyncContext on the Application Tier
- The adSyncContext.pl script reads the WLS configuration parameter values and synchronizes them with the context variables.
- This is used to synchronize the OHS configuration parameters with the respective context variables.
- This mechanism is called the 'feedback loop‘
- The SyncContext tool is one of the tools used for explicit synchronization of the context variables with the WLS configuration parameters.
- In Oracle E-Business Suite Release 12.2 some important configuration files like httpd.conf and ssl.conf are no longer maintained by AutoConfig. Oracle Enterprise Manager 11g Fusion Middleware Control should
be used to maintain these configuration files as well as making additional changes to Context File variables.
Scenario on SyncContext