Deployment Process
03/09/2026
Graphwise for Adobe Experience Manager 1.0
The connector can be deployed on either AEM 6.5 LTS (Long Term Support) or AEM as a Cloud Service.
Adobe Experience Manager 6.5 LTS provides maximum flexibility and infrastructure control, while AEM as a Cloud Service provides a full managed, cloud-native platform with automatic scaling, continuous updates and reduced operational overhead.
AEM 6.5 LTS and AEM as a Cloud Service use different deployment and verification procedures. Choose the deployment method that matches your AEM platform, then expand the corresponding section to view the required steps.
The LTS package is installed directly through Package Manager.
Obtain the LTS package by doing either of the following:
Build the connector from the source (
mvn clean install) then take the package fromcontent-packages/complete/target/graphwise-aem-connector-<version>-lts.zipDownload the
ltsclassifier package from the Graphwise Nexus repository.
On the author instance, open
/crx/packmgr, uploadgraphwise-aem-connector-<version>-lts.zipand then install the package.Note
The first install takes noticeably longer than later ones while the OSGi bundles settle.
Verify that the following appears in Package Manager:
Note
If any of the following packages are present without the
-lts- suffix, the cloud variant is installed. Replace it with the corresponding-ltspackage.graphwise-aem-connector-ltsgraphwise-app-content-ltsgraphwise-config-content-lts
Choose where to store the connection configuration. You can use either of the following options:
In your own project:
As an OSGi configuration for the author run mode. This is the recommended approach as it makes the configuration reproducible and versioned.
In the Web Console:
Suitable for a quick validation on AEM 6.5 Restrict Web Console Access to administrator if the environment contains real credentials. Not available on AEM as a Cloud Service.
Verify and run the checklist in Post-deployment verification.
Note
The connector package is the same across all environments. Only the OSGi connection configuration differs. Synchronization mappings created in the UI are stored under
/conf/graphwiseand can be promoted between environments as content. The mappings do not contain secrets.
For AEM as a Cloud Service the connector is added as a Maven dependency to the customer application and deployed through the Cloud Manager pipeline. Cloud Manager builds the application from the customer Git repository, whereby the connector must be resolvable at build time and embedded in the application build.
Declare the repository in your project and configure credentials using Cloud Manager's private Maven repository mechanism. Graphwise will provide the required credentials.
Note
Access to the OSGi Web Console is blocked in all environments in AEM as a Cloud Service.
Configure Graphwise Nexus repository access:
Ensure the customer build can resolve the required connector artifacts, dependencies and parent POMs.
In Cloud Manager add the repository and provide the necessary credentials using the private repository configuration.
Add the connector dependency to the customer all-package:
Build the connector and embed it in the author-on installation folder:
/apps/<customer-app>/install.author.Use the default (unclassified) artifact for AEM as a Cloud Service deployments.
Embed the connector in an author only installation folder to ensure that the connector is installed only on author instances.
Note
The connector remains a separate bundle and package; since embedding does not merge its code into the customer's application bundles.
Provide the connection configuration as an author-run-mode OSGi configuration and reference secrets from Cloud Manager environment secrets.
Deploy through the customer's Cloud Manager pipeline.
Verify and run the checklist in Post-deployment Verification and then refer to Indexing for AEM as a Cloud Service.
Indexing is an Adobe Experience Manager capability that improves search and query performance by organizing content and metadata for efficient retrieval. While indexing is provided by AEM, this section explains the Graphwise connector's specific indexes, their purpose, and the expected deployment behavior. AEM as a Cloud Service includes two indexing mechanisms that support these operations.
Node under | Origin | Role |
|---|---|---|
| shipped in | Not an index definition. Cloud Manager reads it |
| generated by Cloud Manager | The real cloud indexes. Carry |
| shipped in both variants | Hand-written fallbacks. The only indexes on 6.5 LTS and on a local AEM SDK, neither of which performs the merge. |
On a local AEM SDK,
diff.indexremains inactive while the twographwise.*index definitions perform the indexing operations. This behavior is expected and does not indicate a deployment issue.On AEM as a Cloud Service, two Lucene indexes cover the same paths. This is expected and ensures that a functional index is available regardless of the merge result.
On AEM as a Cloud Service, two obsolete index definitions may remain after deployment because package filter root removals do not delete existing nodes.
As a result unused index definitions such as
graphwise.tags-1-custom-1andgraphwise.sync-runs-1-custom-1can persist and must be removed manually in each environment.Do not delete definitions that contain
mergeInfo. These defintions are managed by Cloud Manager and should be removed by deleting the correpsonding entry fromdiff.jsonrather than deleting the definition directly.The retirement of the
-custom-2fallback indexes is managed as an engineering activity and is outside the scope of this guide. Until they are retired, both indexes pairs should be considered expected and supported.