SAP Commerce: keep the server warm
Separate Java reload, platform generation, type-system updates and runtime configuration in the SAP development loop.
Attach through platform-owned launch configuration
Use Java 17+ and a matching agent. Put a stable agent path in hybris/config/local.properties through tomcat.javaoptions, preserving any existing JVM options.
tomcat.javaoptions=-javaagent:/absolute/tools/reclazz-agent-X.Y.Z.jarDo not self-reference tomcat.generaloptions. Do not rely on directly editing generated tomcat/conf/wrapper.conf: ant server regenerates it. The IDE integration can manage the same platform property for you.
Start once with the configured agent, then compile edited Java with the platform build. Enabling a plugin cannot instrument a server process that was already launched externally.
Generated model and DTO changes
Saving *-items.xml or *-beans.xml can run platform generation/build and reload the generated bytecode. That saves a restart for the supported Java change; it does not by itself create a database column or complete every platform type-system action.
For a new persistent attribute, perform the required Update Running System in HAC. Original-class reflective dispatch to added members still follows the stock/enhanced JVM limits. ModelService/Groovy reflective paths on a stock JVM may need enhanced redefinition or restart.
Properties, localization and Backoffice
Changed SAP configuration keys are applied through the platform Config path. Successfully applied keys are acknowledged independently; failed keys stay pending for retry. A startup-only consumer still needs its reported restart. This differs from the Boot candidate-binding path.
Platform log levels use log4j2.logger.<key>.name and .level pairs. Only touched loggers are updated, preserving unrelated HAC changes. Type/enum locale resources refresh localization caches; Backoffice label resources refresh the relevant label caches. Reopen the affected view to check the result.
Supported Spring XML bean changes follow the XML safety rules. Recognizing an XML file does not imply arbitrary MVC/security/filter-chain reconstruction.
ImpEx changes write real data
autoImpex=true is off by default. If enabled, recognized changed ImpEx files import into the running database. There is no automatic undo of application or import side effects.
Literal and macro-expanded REMOVE headers are refused unless impexAllowRemove=true. Unresolved/recursive header macros are also refused. This bounded scan is not a full ImpEx parser or an executable-script sandbox. Use HAC when the scan cannot establish the header’s safety.
Know the platform boundary
A new extension changes the startup extension list: build and restart. New dependency JARs change the JVM classpath: restart. Database/data migration, tenant initialization and cluster-wide consistency are separate responsibilities.
Interceptor refresh captures mappings before bean refresh and updates the actual SAP registry afterward. Missing/failed registration is a diagnostic, not success. SDK contract evidence must be distinguished from a live model-save/tenant acceptance test.
OCC field sets, request mappings/overrides and populator/list-merge directives have dedicated support paths. Read their detailed scope before changing registry topology or assuming an arbitrary custom composition is covered.
Backoffice configuration and process definitions
A recognized *-backoffice-config.xml save resets supported cockpit configuration caches through the native Resettable.reset() contract. It does not call resetToDefaults() or erase user customizations. If the running module reads a packaged copy, rebuild that copy before expecting the new configuration on view open. The implementation path is distinct from live tenant acceptance.
Widget action rules require an agent-prepared class. Standard module admission is described below. Existing prepared widget action bodies use ordinary class reload. Generic reflection already lets newly composed default MVC components bind added public non-static @SocketEvent handlers with at most one parameter; open components retain their bindings. Native SDK dispatch was measured for one-parameter handlers on JDK17/21 with actual cockpitng listeners and detached ZK components. A local Chrome acceptance on 2211-jdk21.8/JDK21 verified a self-connected synthetic widget: a newly composed second-tab view bound the added handler, the open view kept its binding, body edits applied, and removal stopped stale dispatch. Arbitrary socket/connection routing, MVVM and other reopen workflows remain unverified. Invalid native signatures keep a pending finding; static companion reload is unverified and also keeps a finding. Removing an added method now stops held listeners from running its stale body; restoring the signature restores its dispatch. Label/config cache refresh does not install actions, and no whole-helper replay or user configuration reset is performed.
Start with Reclazz before SAP first loads process definitions. A valid edit to an observed, registered local process XML can update its active in-memory definition through the native factory. Newly started processes use the edited graph; already started processes keep their stored definition version in that JVM.
Renamed processes, duplicate resource names, active DynamicProcessDefinition rows, custom factory/cache/reader implementations and files whose initial load was not observed are refused with a restart explanation. Created and deleted resources still require restart. A save before the native lazy cache first loads is left for that native load to read.
This does not migrate, replay or restart a process. Backoffice process restart, cache eviction, server restart and cluster propagation are outside the version-retention guarantee. Native parser/cache checks and a synthetic watcher fixture are separate from live tenant acceptance; see the evidence record for the current verification state.
Process XML verification scope
Stored Solr documents after a provider edit
Provider code already reloads for subsequent indexing calls. With autoSolrReindex=true, the SAP module can also queue a native update of existing local search documents. The default stays off.
The update selects only types and properties whose provider metadata matches the changed class, uses the stored PKs from the active physical index and refuses more than 10,000 stored documents per type. Property providers use a partial update; type-level resolvers use a whole-document UPDATE. No FULL operation, schema change, core reload or index switch is requested.
Only the stock local standalone provider and indexer strategy are supported. Unknown metadata, remote or distributed targets, missing cores and incomplete reads are refused. Discovery uses persisted provider identifiers and bean type metadata without loading native configurations or creating providers. Once targets are known, native preparation runs in a fresh tenant session; configuration loading, including physical-ownership checks, can construct providers. Persisted/native mapping mismatches are refused. Normal platform listeners and operation bookkeeping still run, including project callbacks and native database writes. Native indexing recalculates current values. Live type-level evidence uses a provider implementing both modern and legacy interfaces, with the legacy native callback selected; modern-only native acceptance remains unverified. The class reload receipt remains separate from indexing: verify the served search field after the operation.
Java Backoffice modules
Extensions with explicit backoffice-module=true metadata can compile saved backoffice/src sources or reload IDE builds in backoffice/classes. Core outputs and required Backoffice module classpaths stay separate.
Start with the agent before the widget class loads. The standard WidgetClassLoader qualifies only with one selected owning output file and identical initial bytes. A stale JAR/output mismatch, duplicate owner or another loader is refused. Subsequent saves target the prepared loader only; deployed JARs are not rewritten. Restart with matching startup artifacts if preparation was missed.
Synthetic watcher tests and both native SDK loader checks cover the Java reload path. Independent live Chrome acceptance on local 2211-jdk21.8/JDK21 verified startup preparation, source compilation, new-view versus open-view binding, handler body edits and removal without stale dispatch. The accepted flow is a self-connected synthetic widget with the default MVC binder; broader widget routing, static handlers and other live platform/JDK combinations remain unverified.
Sources & version scope
Documentation source 1.5.0 · evidence baseline 75535bd · reviewed 19 October 2026. Check your installed artifact; source features may postdate a release.