You are here

Working with Alfresco Enterprise

By default the Alfresco SDK will use Alfresco Community artifacts, however, it can be configured to use Enterprise artifacts. This requires access credentials for the Alfresco Private Repository, and the modification of several Maven configuration files.
Attention: To obtain access to the Alfresco Enterprise repository, please refer to this knowledge base article. If you do not have access to this portal then please contact your Alfresco technical liaison representative within your company, or Alfresco directly.

The examples you have so far looked at have downloaded and used Community versions of the Alfresco artifacts. However, it is possible to use the Alfresco SDK with Enterprise artifacts. These artifacts are stored in a private repository, and only Enterprise customers have access to this repository.

There are four main considerations if you want to use Enterprise artifacts:

  1. You must ensure that you have access credentials for the Alfresco Private Repository.
  2. You must configure Maven to include support for the Alfresco Private Repository server, typically through editing the settings.xml file in the .m2 directory in your home directory.
  3. In your project you must edit the pom.xml file to ensure that the values for the properties alfresco.groupId and alfresco.version are set correctly according to the information that follows.
  4. You must also edit your pom.xml file to reference the Alfresco Private Repository that you created credentials for in (typically) the settings.xml file in your .m2 directory.

Accessing the Alfresco Private Repository

The first matter to consider is to ensure that you have credentials for the Alfresco Private Repository, where the Enterprise artifacts are stored. In fact the private repository also includes all public artifacts too. Once you have suitable credentials you need to add support for Alfresco private repository to your configuration. This would typically be done by adding your access credentials to the settings.xml contained in your ~/.m2 directory (for Linux and OS X). On Windows 7 and Vista this resolves to <root>\Users\<username> and on XP it is <root>\Documents and Settings\<username>\.m2.

This procedure is explained in detail in the tutorial Configuring access to the Alfresco Private Repository.

Setting alfresco.groupId and alfresco.version values to select edition

There is a convention that you need to be aware of that determines which edition of the Alfresco artifacts is used, Community or Enterprise. However this convention is different depending on whether you are referring to Alfresco versions prior to 4.2, or 4.2 and above.

For Alfresco versions prior to 4.2 the edition of the artifact used is determined by the value of the alfresco.groupId property. For Community the alfresco.groupId property value used is org.alfresco, and for Enterprise the alfresco.groupId property value used is org.alfresco.enterprise.

This is summarized in the following table:

Edition alfresco.groupId Example
Community org.alfresco org.alfresco:artifact-id:4.1.2
Enterprise org.alfresco.enterprise org.alfresco.enterprise:artifact-id:4.1.2

For 4.2 and above, the version numbering alone indicates whether the Enterprise or Community artifacts will be used. Version numbers that use an alpha character in the third position indicate Community, for example, 5.0.a. Version numbers that consist of a numeric character in the third position indicate Enterprise, for example 4.2.0. The value for property alfresco.groupId is org.alfresco in both cases.

This is summarized in the following table:

Edition alfresco.groupId alfresco.version Example
Community org.alfresco 5.0.a org.alfresco:artifact-id:5.0.a
Enterprise org.alfresco 5.0.0 org.alfresco:artifact-id:5.5.0

It is important that the POM (pom.xml) is edited correctly to reflect the edition of Alfresco artifacts required. This procedure is covered in more detail in the tutorial Configuring your project to support Enterprise artifacts.

Sending feedback to the Alfresco documentation team

You don't appear to have JavaScript enabled in your browser. With JavaScript enabled, you can provide feedback to us using our simple form. Here are some instructions on how to enable JavaScript in your web browser.