Post-deployment Verification

07/09/2026

Graphwise for Adobe Experience Manager 1.0

Ensure the following checks are completed after every deployment to a new environment. These checks are the same on both 6.5 LTS and Adobe Experience Manager as a Cloud service, where you run them is not.

#	Check	6.5 LTS	AEMaaCS	Pass condition
1	Bundle active	`/system/console/bundles`	Developer Console > Statues > Bundles	`ai.graphwise.aemconnector.core` is Active
2	Connection config satisfied	`/system/console/configMgr`	Developer Console > Status > Configurations	Graphwise Connection is bound and shows the expected URL. Secrets are masked.
3	Service user exists	`useradmin` or `/security/users.html`	`/security/users/html` on author	`graphwise-aem-connector` exists under `system/cq:services/graphwise`
4	Repoinit content present	CRXDE Lite	Repository browser on any environment; CRXDE Lite on dev	`/conf/graphwise/poolparty/endpoints` has 14 child nodes; `/var/graphwise/poolparty` has `sync-runs` and both claim roots.
5	Queues registered	`/system/console/slingevent`	Developer Console > Statues> Sling Jobs.	All four Graphwise queues listed, type `ORDERED` (which is what makes them serial)
6	Consoles reachable	Tools > Graphwise Connector on author	same	Five entries: Configuration, Auto-Tagging, Dashboard, Audit, Maintenance
7	Connection works	Configuration console > Test connection	same	Success. A 403 here means a Graph Modeling role problem, not a connector problem.
8	Indexes resolve	Groovy Console `explain`	Developer Console > Queries	Refer to Verifying the Indexes.

Note

Checks 6 and 7 behave consistently across all supported environments because they use the connector's author-side user interface rather than platform-specific tooling.

The connector relies on two Lucene indexes for performance. Without these indexes, incremental sync takes significantly longer to complete.

Ensure all five properties are covered by Lucene indexes:

uri on cq:Tag
configID on sync runs
startedAt on sync runs
graphwiseSyncDirty (drift marker)
graphwiseSyncStructureDirty (drift marker)

Follow the information for your AEM deployment model:

AEM 6.5 LTS:
Run the Groovy script below in Groovy console (/apps/groovyconsole.html.
Note
Do not use the CRXDE Lite Query tool, as it does not provide useful output for EXPLAIN queries.
AEM as a Cloud Service: Run the same queries in Developer Console > Queries. Omit the EXPLAIN prefix because the tool adds it automatically.

Use the following Groovy script to verify that the required properties are indexed correctly:

def qm = session.workspace.queryManagerdef explain = { label, stmt ->  println "--- ${label} ---"  qm.createQuery("explain " + stmt, "JCR-SQL2").execute().rows.each { println it.getValue("plan").string }}explain("tag uri lookup",  "select * from [cq:Tag] where isdescendantnode('/content/cq:tags') and [uri] = 'http://example.org/x'")explain("dirty marker lookup",  "select * from [cq:Tag] where isdescendantnode('/content/cq:tags') and [graphwiseSyncDirty] = true")explain("sync-run configId lookup", "select * from [nt:unstructured] where isdescendantnode('/var/graphwise/poolparty/sync-runs') and [configId] = 'x'")

Important

Ensure to verify that the query plan references a gw.* or graphwise.* index and include the queried property. If the property does not appear in the query plan, it is not indexed.

In this section: