Portal Admin Server, Cacao, Portal Monitoring: Relationship FAQ
By ajitsabnis on Dec 06, 2006
Ajit Sabnis wrote:
Michel Bouyges wrote:Hello ,
I restarted Cacao and have the same error , I join below the trace of shell commands, web server log and cacao log .
I would be very happy to find anwers to question below :
-what is Cacao ?
Cacao stands for Common Agent Container, i.e. a Container for deploying OSNode agents that help managing the OSNode. For example in our case Portal Admin Server (PAS) is deployed in Cacao environment. You can view it as collection of MBeans available to manage something on this OSNode.
-what are the relation between cacao , the portal MBeans, and the MBean server .
PAS MBeans get registered in an MBeanServer. The MBeanServer and remote connection to it is managed by Cacao.
Lets call Cacao JVM as JVM-Cacao.
Now, there are PS Monitoring MBeans that get registered in an MBeanServer in portal web-app. This happens in portal web-app JVM, say JVM-Portal.
- how works psadmin, is it a JMX client ? does this command speaks to the cacao server ?
Then, psadmin is a JMX client running in say the third JVM, say JVM-psadmin. psadmin (JVM-psadmin) does its administrative functions invoking PAS MBeans (from JVM-Cacao).
In case of Monitoring subcommands of psadmin, JVM-psadmin talks to JVM-Cacao that in turn talks to JVM-portal to fetch requested monitoring information.
- why is there two cacao command in the filesystem : /usr/sbin/cacaoadm et /opt/SUNWcacao/bin/cacaoadm ?
/usr/sbin/cacaoadm is for Cacao 2.0 that is part of JES5/PS7.1
/opt/SUNWcacao/bin/cacaoadm is for Cacao 1.x that was part of earlier release.
Both can co-habit on one OSNode.
- what is the data/event flow between Cacao, Directory Server, Portal Server / Access Manager, admin CLI
I think PAS needs Directory Server to be up when it (JVM-Cacao) comes up. PAS stores its configuration information in Directory, and needs it when running.
PS needs AM up, AM needs DS up.
psadmin needs PAS/Cacao up.
Does this help?
- I do not see any MBean registered when connecting the jconsole on the web server process id ( when adding appropriate JVM defines ), where are registered these Mbean ?
By default portal (JVM-Portal) doesn't use Java 5 Platform MBeanServer (for we support WebContainers that still run on J2SE 1.4). Probably that's why you don't see JVM-Portal MBeans in WebServer using JConsole.
- what does mean this message from psadmin :Could not connect to server instance. Please check if server is up.which server must be up ? Cacao server ? , MBean server ? web server ?
Portal Server being up.
For WebContainer differences (WS, AS, BEA, IBM) Monitoring gets initialized in a lazy fashion. On first request to portal, Monitoring gets initialized, and PSConsole/psadmin can fetch monitoring information. Until that time, portal is said to be not up. (The status of web-app can be found on WebContainer monitoring support, if available.)
So, "Portal Server is up" indicates that at least one request is served by portal.
- The /var/opt/SUNWportal/logs/admin/\*.cli.log file keep now a zero size and do not register any message. I don't know why, but it is difficult to understand what happen without log .
This is probably fine for this log file belongs to psadmin (or JVM-psadmin writes to that file).
logs/admin/portal.0.0.log is written by PAS (JVM-Cacao).
/var/opt/SUNWportal/portals/portal1/logs/<instance>/ logs are written by JVM-Portal.