How to integrate Silktide with AEM
Supported versions
The Silktide AEM integration is currently available for:
- AEM 6.4
- AEM 6.5 (SP2+)
Download the Silktide AEM integration plugin here.
Installing the Silktide package
- Obtain the relevant AEM package from Silktide, for your AEM version
- Login to your AEM author instance
- Make sure that your AEM account has permission to upload and install packages
- Navigate to CRX Package Manager by clicking on Tools (the hammer icon on the far-left) > Deployment > Packages
- Click on Upload Package and select the AEM package provided earlier
- Click OK
- Click on Install to open the installation modal
- Click on the Install button
- Check the log shows the installation was successful
Connect AEM to Silktide
- Log into Silktide as an account administrator
- Click on the user menu (top-right) and select Settings
- Click on Integrations
- Click New CMS
- Select Adobe Experience Manager from the list provided and press Add
- Make a note of the API key and Endpoint URL provided on the next screen. You will need to copy these into AEM
- Login to AEM author instance with admin user account
- Click on the Silktide icon from the Start page:
- Enter your Endpoint URL and API key provided by Silktide:
- Click Save
- Silktide can now be used for all pages by default (you can override this below)
URL mappings
Two optional Silktide features depend on an additional piece of configuration:
- Deep link from Silktide directly into AEM to edit a specific page with an issue
- Automatic re-testing of AEM pages when they are published
For these, Silktide needs to know how to translate between the private and the public URLs used by AEM.
For example, this editor URL:
http://localhost:4502/editor.html/content/we-retail.htmlMaps to this public URL:
http://localhost:4502/content/we-retail.htmlIn this case, the transformation is very simple – we simply remove (or add) /editor.html from the path of the URL.
To configure this, give your Silktide Customer Success Manager an example of the same page being edited, and being viewed on the public site. We plan to add an editor that will allow you to configure rules to make these transformations yourself in the near future.
Advanced configuration
Enable/Disable Silktide for specific pages
The Silktide integration is enabled for all pages by default. You can change this as follows.
- To disable Silktide for a page / hierarchy of pages:
- Login to the AEM author instance
- Under Sites, find the page you want to modify
- Select the page you want (click the thumbnail) and select Properties from the top navigation bar
- Click the Silktide Integration tab
- Select Disable from the dropdown option and leave the Override Parent Page Configuration unchecked
- Click on the Save button
- Silktide is now disabled for the current page and its child pages
- To enable Silktide for a child page when it is disabled on its parent page
- Login to the AEM author instance
- Under Sites, find the page you want to modify
- Select the page you want (click the thumbnail) and select Properties from the top navigation bar
- Click the Silktide Integration tab
- Select Enable from the dropdown option and select Override Parent Page Configuration
- Click Save
- Now, Silktide is enabled for the child page
If you’re ever unsure of the status of the Silktide integration, hovering over the Silktide icon whilst editing any page will show whether it is enabled or disabled.
Configure permissions
Silktide adds some configuration options to AEM. You can configure who has access to these.
Permitted users can perform the following actions:
- Set the API key (i.e. see the Silktide icon on the Start page)
- Configure what pages the plugin applies to
In most cases, you can leave this alone, as AEM administrators will already have access.
- Login to AEM author instance with an admin user account
- Navigate to Tools > Security > Groups
- Search for the silktide-admin group
- Select silktide-admin group from the results
- Add any necessary users to this group
