R12.2 Configuration Management - Scenario on adRegisterWLSListeners
Some Oracle E-Business Suite Release 12.2 configurations are managed via AutoConfig, and some are managed natively via Fusion Middleware Control or Oracle WebLogic Server Administration Console.
The adRegisterWLSListeners tool has been introduced to perform synchronization of context variables with the associated Oracle WebLogic Server configuration parameters.
Note: This tool does not listen for changes to the Oracle HTTP Server configuration parameters.
Execute the following command to start adRegisterWLSListeners.pl:
$ perl/bin/adRegisterWLSListeners.pl contextfile=
Once started, adRegisterWLSListeners keeps running, listening for changes to the WebLogic Server configuration and synchronizing the context files stored in the database.
Important: The adRegisterWLSListeners tool automatically stops when WebLogic Administration Server is shut down. On UNIX instances, the tool is started automatically started whenever WebLogic Administration Server is started. On Windows instances, you must start the tool explicitly every time WebLogic Administration Server is started.
For this demo I have started the tool manually to see if the changes I make is getting recorded
SQL>
SQL>
Some Oracle E-Business Suite Release 12.2 configurations are managed via AutoConfig, and some are managed natively via Fusion Middleware Control or Oracle WebLogic Server Administration Console.
The adRegisterWLSListeners tool has been introduced to perform synchronization of context variables with the associated Oracle WebLogic Server configuration parameters.
Note: This tool does not listen for changes to the Oracle HTTP Server configuration parameters.
Execute the following command to start adRegisterWLSListeners.pl:
$ perl
Once started, adRegisterWLSListeners keeps running, listening for changes to the WebLogic Server configuration and synchronizing the context files stored in the database.
Important: The adRegisterWLSListeners tool automatically stops when WebLogic Administration Server is shut down. On UNIX instances, the tool is started automatically started whenever WebLogic Administration Server is started. On Windows instances, you must start the tool explicitly every time WebLogic Administration Server is started.
For this demo I have started the tool manually to see if the changes I make is getting recorded
SQL> select * from AD_NODES_CONFIG_STATUS;
NODENAME W O C
---------------------------------------- - - -
TESTSERVER01 N N N
You can see from the above back end SQL that Weblogc , OHS and Context File are showing value N since they are not changed.
Now let us make a change in the Weblogic.
SQL> select * from AD_NODES_CONFIG_STATUS;
NODENAME W O C
---------------------------------------- - - -
TESTSERVER01 Y N N
adRegisterWLSListeners.pl has updated the database table AD_NODES_CONFIG_STATUS with status Y for WebLogic Column.
This is how weblogic changes are keep in track and synced using adRegisterWLSListeners.pl
