Use this information to install and configure an AMP for linking Content Services to Alfresco Process Services (APS).
When Content Services and Process Services are linked, a folder rule action can be configured that starts a Process Services process when a document is added into the folder. This is called an APS action.
Prerequisites
To configure an APS action there are several prerequisites that must be met:
- Content Services installed.
- Process Services installed.
- Content Services and Process Services using a common LDAP database to sync users from.
Note: If Content Services and Process Services do not sync their uses against a single LDAP database then an APS action will never work. See configure LDAP for Content Services and configure LDAP for Process Services for information on configuring LDAP.
Install the AMP
To install the APS action AMP:
-
Visit Hyland Community and download the APS action zip bundle.
-
Unzip the bundle and place the
aps-action-share-6.2.1.amp
to the Content Servicesamps_share
directory. -
Run the
apply_amps.bat
file from thebin
directory to install the AMP. -
Check the output from the
.bat
file to ensure the installation was successful. -
Restart the Content Services server.
Configure the repository in Process Services
To configure the repository in Process Services:
-
Sign into Process Services as an administrator.
-
Open up the Identity Management section and select Tenants > Alfresco Repositories.
-
Create a repository connection:
Field Description Name Required. A name for the repository connection. Alfresco tenant Optional. The tenant to use for the connection. The default value is -default-
.Repository base URL Required. The base URL of Content Services, for example http://127.0.0.1:8080/alfresco/
.Share base URL Required. The base URL of Share, for example http://127.0.0.1:8080/share/
.Alfresco version Required. The version of Content Services used. This must initially be configured as 5.2
, even if using a later version of Content Services.Authentication Required. The authentication method to use. Select Enable Share Connector
checkbox.Secret Required. The common secret used for communication between Content Services and Process Services. The default value us activiti-share-connector-secret
. This must match the propertyactiviti.secret
set in Content Services. -
Save the connection.
-
Inspect the connection in the list. If the
ID
is1
and the default values do not need to be updated then this step is complete. If theID
is not set to1
then stop Content Services and Process Services and update the following two files with theID
showing in the repository list:- In
tomcat/shared/classes/alfresco-global.properties
in Content Services add a line foractiviti.alfrescoRepositoryName=alfresco-<ID>
where<ID>
was the ID displayed in Process Services, for examplealfresco-1002
. - In
tomcat/lib/activiti-app.properties
in Process Services update the propertyintegration.login.alfresco-1.secret
where1
is replaced with the ID displayed in Process Services, for exampleintegration.login.alfresco-1002.secret
.
- In
Enable review process app
To enable the bundled Review Processes app in Process Services, add the following into the <InstallLocation\>/lib/activiti-app.properties
and restart Process ServicesL
app.review-workflows.enabled=true
Configure Content Services properties
Content Services needs properties set in the tomcat/shared/classes/alfresco-global.properties
file that point to the Process Services installation and enable the use of APS actions:
Property | Description |
---|---|
activiti.domain | The domain that Process Services is running on, for example example-aps.com . |
activiti.baseUrl | The base URL of the Process Services installation. |
activiti.secret | The common secret Content Services and Process Services use for communication. The default value is activiti-share-connector-secret . This value must match the Secret value set in Process Services when configuring a repository connection. |
activitiRepoConnector.enabled | Set this to true to enable the use of APS actions. |