The error message "Alfresco is running without Share Services" specifically indicates that the Alfresco Share user interface is unable to find and connect to essential services that it expects to be available from the repository. These services, which include functionalities for site management, user invitations, and other collaborative features, are packaged within the alfresco-share-services.amp (Alfresco Module Package). This AMP is a repository-side extension and must be applied to the alfresco.war file. Applying this module to the repository and restarting the service makes the required APIs available to Share, resolving the error.

A. The Share Services AMP is a repository extension; applying it to the Share web application (share.war) is incorrect and will not resolve the issue.

C. Re-deploying the share.war file will not fix the problem, as the issue lies with missing components in the repository, not the Share application itself.

D. While using matching versions is a prerequisite for a stable system, it does not automatically install the optional Share Services AMP, which is the specific cause of this error.

1. Alfresco Content Services 7.0 Documentation, Installing Share Services: "The Share Services AMP (alfresco-share-services.amp) is required for Alfresco Share to run correctly. It is applied to the Alfresco Repository WAR (alfresco.war)." This section explicitly states the purpose of the AMP and where it must be installed.

Source: Alfresco Documentation, https://docs.alfresco.com/content-services/latest/install/zip/amp#install-share-services-amp (This link points to the latest version, but the principle is consistent across ACS versions).

2. Alfresco Content Services 6.2 Documentation, Installing an Alfresco Module Package (AMP): This guide details the standard procedure for applying AMP files to Alfresco WAR files using the Module Management Tool (MMT). The process involves placing the AMP in the amps directory and running the applyamps script, which targets the alfresco.war by default. This confirms the technical procedure implied in the correct answer.

Source: Alfresco Documentation, https://docs.alfresco.com/content-services/6.2/install/zip/amp/ (Section: "Install an Alfresco Module Package").

The Smart Folders functionality is installed using an Alfresco Module Package (AMP). However, after the installation of the AMP, the feature is not active by default. To use Smart Folders, a system administrator must explicitly enable the function by setting the smart.folders.enabled property to true in the alfresco-global.properties file and then restarting the Alfresco server. A failed attempt to create or apply a Smart Folder is a direct symptom of this default-disabled state.

A. The site manager created a template first.

Creating a template is a prerequisite for applying a Smart Folder structure; it is a necessary step in the process, not a cause for failure.

B. Smart Folders can only be created by Site Administrators.

This is incorrect. Applying a Smart Folder template is governed by standard folder permissions; users with edit permissions on a folder (e.g., Site Manager, Collaborator) can apply the template.

C. The Smart Folder AMP has not been installed.

While a missing AMP would make the feature unavailable, the more specific and common cause of failure after installation is that the feature remains disabled by its default configuration.

1. Alfresco Content Services 7.0 Documentation, "Configuring Smart Folders": This official documentation explicitly states the default configuration.

Reference: "You can enable or disable the Smart Folders feature by setting the smart.folders.enabled property to true or false in the alfresco-global.properties file. You must restart the Alfresco server for the setting to take effect. By default, this property is set to false."

Source: Alfresco Content Services 7.0 Documentation, Administering Section.

2. Alfresco Content Services 7.0 Documentation, "Applying a Smart Folder Template": This page clarifies the permissions required, refuting option B.

Reference: Under the prerequisites for applying a template, the documentation states: "Ensure you have the correct permissions to edit the folder." This indicates standard permissions are used, not a role exclusive to Site Administrators.

Source: Alfresco Content Services 7.0 Documentation, Using Content Services Section.

The Aggregating Content Store is specifically designed to combine multiple content stores into a single virtual store. It designates one store as the primary, which handles all read and write operations for new content. The remaining stores are configured as secondary, read-only stores. This architecture is commonly used for content migration scenarios, allowing access to legacy content in read-only archives while all new content is directed to the primary store.

A. File content store: This is the default, single-store implementation. It does not have the built-in capability to aggregate multiple stores or define primary/secondary read-write/read-only roles.

B. Selector Content Store: This store routes new content to one of several underlying stores based on defined rules (e.g., content type or properties), but it doesn't create a primary/secondary read-only structure.

C. Caching content store: This store provides a local cache for a remote backing store to improve performance in distributed environments. It is not designed to aggregate multiple read-only secondary stores.

1. Alfresco Content Services 7.4 Documentation, "Types of content stores":

Aggregating content store: "The Aggregating content store is a content store that aggregates a set of stores. It is a primary store for read and write, and a set of secondary stores for read only."

Selector content store: "The Selector content store provides a mechanism to select a content store to use from a set of stores, based on a content model property."

File content store: "The File content store is the default content store implementation."

Reference Location: Alfresco Documentation > Alfresco Content Services 7.4 > Administering > Repositories > Content stores > Types of content stores.

2. Alfresco Content Services 7.4 Documentation, "Configuring the Aggregating content store":

"The Aggregating content store is a content store that aggregates a set of stores. The first store in the list is the primary store. The primary store is the store that all new content is written to. The other stores are secondary stores and are read-only."

Reference Location: Alfresco Documentation > Alfresco Content Services 7.4 > Administering > Repositories > Content stores > Configuring content stores > Configuring the Aggregating content store.

Java Management Extensions (JMX) in Alfresco provide a standard interface for managing and monitoring the application server. It allows administrators to perform operations such as managing subsystems, enabling or disabling server components like FTP and CIFS, and controlling system-wide settings like single-user mode. However, JMX is not designed for application-level code debugging. Alfresco provides a dedicated JavaScript Debugger tool, accessible via a specific URL, for inspecting and debugging server-side JavaScript extensions. This tool offers features like stepping through code and inspecting variables, which are outside the scope of JMX's management and monitoring capabilities.

A. Alfresco subsystems (e.g., Authentication, Synchronization) are designed to be managed (started, stopped, and configured) directly via JMX MBeans, which is a primary administrative function.

C. The FTP and CIFS servers are implemented as Alfresco subsystems. Therefore, like other subsystems, they can be enabled or disabled at runtime using JMX operations.

D. Alfresco exposes an MBean (Alfresco:Type=Configuration,name=sysAdmin) that includes an operation to enable or disable single-user mode for maintenance tasks.

---

1. Alfresco Content Services 7.4 Documentation, "Using the JMX client": This section details the various administrative tasks that can be performed using a JMX client like JConsole. It explicitly mentions managing subsystems. The File Servers (CIFS/FTP) are listed as manageable subsystems.

Reference: Alfresco Content Services 7.4 Documentation > Administering > Monitoring Alfresco > Using the JMX client.

2. Alfresco Content Services 7.4 Documentation, "JMX bean categories reference": This page lists the MBeans available for management. The Alfresco:Type=Configuration,name=sysAdmin MBean is documented with its attributes and operations, including setSingleUserMode(boolean enabled).

Reference: Alfresco Content Services 7.4 Documentation > Administering > Monitoring Alfresco > JMX bean categories reference > sysAdmin.

3. Alfresco Content Services 7.4 Documentation, "The JavaScript Debugger": This document describes the dedicated tool for debugging server-side JavaScript. It details how to access the debugger via its web script URL (/alfresco/s/api/javascript/debugger) and use its features, confirming it is a separate mechanism from JMX.

Reference: Alfresco Content Services 7.4 Documentation > Developing > Customizing Share > The JavaScript Debugger.

For security reasons, Alfresco Content Services disables the remote JMX RMI connector by default. To connect remotely using a tool like JConsole, an administrator must explicitly enable this functionality. This is achieved by setting the alfresco.jmx.connector.enabled property to true in the alfresco-global.properties file and ensuring the related host and port properties are correctly configured. The problem described, where a connection attempt fails, directly points to this default disabled state.

A. The property alfresco.jmx.connector.enabled being set to true would enable the JMX connector, which is the opposite of the problem described.

C. JConsole is the standard Java monitoring tool included with the JDK and fully supports JMX Remoting (JSR-160) for connecting to remote MBean servers.

D. JConsole is a standard and officially documented tool for managing and monitoring Alfresco via JMX.

1. Alfresco Content Services 7.4 Documentation, Administering > Monitoring Alfresco > JMX settings. The documentation explicitly states: "The JMX RMI connector is disabled by default. To enable the JMX RMI connector, you must override the default settings..." It then lists the property alfresco.jmx.connector.enabled=false as the default.

2. Alfresco Content Services 6.2 Documentation, Administering > Monitoring Alfresco > Using the JMX command-line client. This section provides instructions for connecting with JConsole, confirming it is a supported tool. It also notes the requirement to enable the JMX connector first.

3. Oracle Java SE Documentation, Monitoring and Management Using JMX Technology > JConsole. This official source details the capabilities of JConsole, including its ability to connect to remote JMX agents, which is based on JSR-160.