On Enterprise you have the ability to go to the Enteprise admin console, even though none of the functional administrators are capable of following it.
The second thing on Enterprise is that through JMX a lot can be changed/maintained. This means mostly the following steps to do a simple thing:
- Login on the server via SSH or RDP
- Enable X11 forwarding on Linux
- Open JConsole
- Go to the JMX Wiki of Alfresco and fill in the url, username & password
- Click on the MBeans tab (with X11 forwarding it can be damn slow for instance)
- Go through the tree and find you subsystems or your log4j logging class
- Set the appropriate settings
- This whole project will take you at least 5-15 minutes, not counting minutes on systems where you need Citrix or additional tokes to connect to.
Features at the moment:
Force a FULL LDAP synchronization. In some cases the incremental sync gets stuck and a full sync is needed. On the other hand, some instances are only synced nightly and this is nice to be triggered any time.
LDAP Status Refresh
See the status of the last/current sync. The LDAP sync runs in the background, so you have to keep polling/checking if it's finished.
Set any class to any selected Level (Debug/Info/Warn/Error) with just one button.
Work In Progress:
Restart an Alfresco Subsystem
Get a list of the current available subsystems and perform a restart. Very handy when for example ImageMagick or LibreOffice gets stuck.
Read & Set Properties for a Subsystem
It's nice to see which properties are available for a subsystem & the feature to set them without going through JMX/JConsole
Read alfresco-global.properties & all other system properties
- Do something with the Cronjobs in Alfresco
- Show the alfresco.log & share.log without going to the file system
- Do something with Solr/Lucene