Monday, April 10, 2017

Alfresco Troubleshooting: JMX Settings

The file is a central place for Alfresco configuration and extension.  This properties file is created automatically during the Alfresco wizard installation.

While the use of a single central file for configurations simplifies management of Alfresco, any changes to settings made to the file require that the server be restarted before the changes become effective.  In most cases, the global properties file is changed infrequently, so having to do a restart is not that much of a problem.

But if changes to the file need to be made frequently, especially in a critical production system, it isn't desirable to have to restart the server whenever a configuration change is needed.

To enable configuration updates while the server is still running, Alfresco provides JMX as an alternative method for being able to change configuration settings on a system that is running.  Using a JMX client like JConsole, you can edit any configuration setting, and those changes then are persisted into the database and override any setting in the file.

Note that JMX settings stored in the database take precedent over the settings found in the file and that the file does not get updated after a parameter is changed by JMX. 

What this means is that JMX is the ultimate source of the current settings and any other settings found in Note that configuration files may not be accurate because they have been overridden or outdated by JMX.  This is why very often when a troubleshooting case is submitted to Alfresco Support the first request from the Alfresco support team is to see a dump of your JMX system settings.

Instructions for how to download the JMX settings dump differ depending on which version of Alfresco you are running:
In earlier versions of Alfresco, JConsole was automatically included as part of a complete Alfresco stack install.  It was located in the java/bin directory of the Alfresco home area.  In Alfresco 5.2.x, you will need to download JConsole or other JMX tool.

Detailed instructions for how to access Alfresco via JMX can be found here, and a useful blog post about how to troubleshoot JMX setup issues can be found here.

The standard URL for accessing JMX on Alfresco is:


Default credentials to access Alfresco JMX are:

userid: controlRole
password: change_asap

One project for troubleshooting Alfresco is the GitHub project called Alfresco Support Tools. This project includes a number of useful tools for troubleshooting Alfresco systems.  The tools are available from the Enterprise Alfresco Admin Console.  After installing the AMP from this project, the following options become available, as shown below.

One feature of the Alfresco Support Tools project called JMX Settings.  This option shows a list of the parameters that have been overridden with JMX settings.
An example screenshot is shown below.

Monday, April 3, 2017

How can I reset the Batch Instance Identifier (ID) value in Ephesoft?

Sometimes, for an Ephesoft deployment, it is advantageous to reset the Batch Instance Identifier (ID) or BI#. This might also be required because there is a "feature", some would say a bug, in MariaDB where the sequence value will reset to '1' when there are no batches in the queue and the DB is bounced.

First, we should determine the current BI# using the following command:

            select ID from BATCH_INSTANCE;

NOTE: It will be the highest value returned.

Remember the Batch Instance Identifier is displayed in Hexadecimal format when viewed in the Ephesoft interface. However, we will use an integer when updating the BI# at the DB level and Ephesoft will convert it to a Hexa Decimal value.  In this first example, we will set the BI# to '40001'. Ephesoft will display this as 'BI9C41'.

           alter table BATCH_INSTANCE auto_increment = 40001;

You can check the value using the previous select statement after you submit your next batch.

If you want to start with a specific Hexadecimal value, say A100, you will need to first convert it to a decimal. In this case, the decimal value '41216' would be used.

            alter table BATCH_INSTANCE auto_increment = 41216;

NOTE: To verify that the change has occurred you will need to process a new Ephesoft batch.

Thursday, March 2, 2017

Auditing Document Transactions in Alfresco Share

A frequent need for many of our customers is the ability to audit activity on a document in the Alfresco repository.  An easy way to do this is via a subscription to the Formtek Auditing Extension for Alfresco.

The Auditing Extension is one of several extensions to Alfresco that Formtek offers to enhance your Alfresco implementation.

The Auditing Extension is Integrated with Alfresco Share

For every object accessible via Alfresco Share, the Auditing Extension records the action performed, the date and time the action occurred, the user who performed the action, and optional details on the action. Each document and folder maintains its own auditing information, and any user who can access the document or folder can also view its audit log.

The Auditing Extension records standard Alfresco transactions such as Create, Edit Properties, Update Properties, Checkout, Download, Upload New Version, Move to, Copy to, Manage Permissions, Manage Aspects, Delete Document, and more.  It will also record actions initiated by other installed Formtek extensions (i.e. File Linking, Peer Association, Version Browser, and the Engineering Data Management Module).

So, what does it look like?  Here’s a screenshot of an audit of a single document.

Audit History for a Single Object

Selecting “More” provides additional information about the action performed.

Additional Capabilities for Administrators
If you are an administrator, you may access the admin console and use the Audit History Search Panel to search for audit records for different types of content stored in the repository. Audit records include the following information:

  • Timestamp – When the action occurred
  • Action – The action performed
  • User – The user who performed the action
  • Type – The type of item on which the action was performed
  • Name – The name of the item on which the action was performed.

Here’s a screenshot.

Audit History Search Panel with Results

The admin console also provides an effective means for an administrator to search for active and/or completed workflows. Workflow records include the following information:

  • Description – The workflow message
  • Initiator – The user who started the workflow
  • Start Date – The workflow start date
  • Due Date – The workflow due date
  • End Date – The date the workflow completed
  • Priority – The workflow priority (1=High, 2=Medium, and 3=Low)
  • Status – The workflow status, either Active or Completed
  • Details – A link to the details of the workflow in a new window.

Workflow History Results List

Need more information?  You can watch this short demo video.