Wednesday 23 September 2015

synchronise configuration of WLS JAS node while down

Are you as frustrated as me with this.

You have made some JAS.INI file changes in SM that you want to synchronise with your installed JAS APP.

image

Cool, I get it – now I want to synchronise the config – so basically

copy from:

D:\jde_home\SCFHA\targets\JWB01P_PPCMSNZ_92\config

to

D:\oracle\Middleware\Oracle_Home\user_projects\domains\E1_Apps\servers\JWB01P_PPCMSNZ_92\stage\JWB01P_PPCMSNZ_92\app\webclient.war\WEB-INF\classes

But it STARTs the instance.  I do not want it started, I just want the parameters to be right for next time I start it.  It’s really frustrating.  I can see in the Server Manager logs, that it does the changes  to the file and then requests a restart:

FINER: Setting the attribute 'OracleAccessSSOSignOffURL' to value '' in INI file 'D:\jde_home\SCFHA\targets\JWB01P_PPCMSAU_91\config\jas.ini'.
23/09/2015 2:13:48 PM com.jdedwards.mgmt.targets.IniDynamicMBean setAttributeWithUserName
FINER: Setting the attribute 'frameBustingForE1Menu' to value 'differentDomain' in INI file 'D:\jde_home\SCFHA\targets\JWB01P_PPCMSAU_91\config\jas.ini'.
23/09/2015 2:14:06 PM com.jdedwards.mgmt.targets.owl.OWLJ2EEServer start
FINER: Recieved request to start server 'JWB01P_PPCMSAU_91'

So this is not cool, does anyone else have this?  I understand that if this is the FIRST time the application is started – it’s not actually been expanded to the stage directory by WLS, so this might explain why it cannot be sync’d until it’s at least started for the first time.


It’s also important to remember that it’s the nodemanager that does all of the stop and start commands that are executed through SM, therefore you need to ensure that this is up and running for the synchronisations to work.

23/09/2015 2:09:54 PM com.jdedwards.mgmt.targets.owl.OWLJ2EEServer updateApplicationFiles

INFO: Update succeeded for application 'JWB01P_PPCMSAU_91', from location 'webclient.war/WEB-INF/classes'

23/09/2015 2:09:54 PM com.jdedwards.mgmt.targets.owl.OWLJ2EEServer updateApplicationFiles

INFO: Update succeeded for application 'JWB01P_PPCMSAU_91', from location 'webclient.war/WEB-INF/classes'

23/09/2015 2:15:00 PM com.jdedwards.mgmt.targets.owl.OWLJ2EEServer updateApplicationFiles


You can see from the above that it’s got no problems updating the files.

3 comments:

Unknown said...

This is actually a reported bug that was corrected in tools 9.1.5.3

Issue reported in Bug 20463428 - JAS INSTANCE RESTARTS WHEN CHANGING LOG FILE CONFIGURATION IN SERVER MANAGER

Shannon Moir said...

I'm on 9.1.5.5 - strange! That is logging too, I'm actually not changing logging - I'm just synchronising config files. It's slightly different. Although I can imagine the panic of a CNC person enabling logging in 9.1.5.2 which restarts the web!!!

Unknown said...

Because of your tools release I would assume that it isn't the same issue reported. We had tool 9.1.4.4 and this was happening to us as well but when we moved to 9.1.5.4 the automatic restart of the JAS instance when clicking synchronize stopped.

It didn't just happen when you changed logging, it happened on any change you synchronized to the INI as well.

E1: SVM: WLS: HTML Server Instance Configured on WebLogic Server Restarts When Changing Log File Configuration and During Synchronization Operation from Server Manager Console Version 9.1.5 (Doc ID 1970186.1)

Extending JDE to generative AI