After the creation of the managed servers, we often need to customize their 'Server Start' properties in the Admin Console in order to start them properly with the Admin Console. Below is a screenshot of my configuration here:
Except the 'Class Path' and 'Arguments' properties, other properties are straight-forward and easy to fill in.
For the two properties, my experience was to first start the managed server with the script startManagedWebLogic.sh, then do a 'ps -ef|grep java' to find the managed server process. You will find the 'Class Path' with -Djava.class.path=, then you can copy and paste into the 'Class Path' property in the Admin Console; You will also find some java arguments from the process that you can copy and paste into the 'Arguments' property.
You often need to adjust the arguments to increase the Java heap size, as with the defaults you are likely to get out of memory errors. Also you can add your own arguments there. For example, we added '-Ddenv=dev1' to for the applications to identify which nodes they are running in a cluster environment.
Saved the configuration. The managed servers then will be started with the customized properties, with the startManagedWebLogic.sh cript, Admin Console or Node Manager.
great post
ReplyDeleteMuy buena información entregada en esta discusión, muy clara y concisa, me gustó tu blog , muy interesante el tema del cual hay mucho por aprender
ReplyDeleteQuiero dejar esta página en la cual puedes ver productos de los retail de todo Chile,
y comparar los precios de avon campaña 18 con las otras tiendas