LEARN. PRACTICE. GROW.Concept and mechanism
In WebSphere traditional Network Deployment, the deployment manager coordinates cell configuration and maintains the master repository. The node agent participates in node management and synchronization; applications run in separate server processes. If the agent stops communicating, an application can continue responding while management is degraded. Do not use one indicator to conclude both are healthy. An edit made directly in a local copy can disappear when central configuration is synchronized. Save the change through the approved administrative mechanism, identify targets, and establish what was actually applied. With autosave disabled, AdminConfig.save persists changes but does not establish synchronization of every node or adoption by the runtime.
Guided application
In a fictional incident, two profiles use the name server1. Before collecting logs, record host, cell, node, profile, PID, time, and time zone. Compare saved configuration, synchronization state, and observed behavior. Successful saving at the manager followed by old behavior on one member supports investigating propagation before restarting the cluster. Maintain an inventory of traditional, Java, IHS, and plugin. This lesson targets traditional ND 9.0.5, with maintenance baseline 9.0.5.29 released on 2026-09-08. Liberty has a different version and configuration line; 26.0.0.9 is not the next traditional fix pack. The change plan should explicitly identify the product, owners, and acceptance criteria.
A timeout changes on three members but stays unchanged on a fourth: inspect that node agent and synchronization.
Common pitfalls
Confusing an active service with healthy management; editing local copies; mixing traditional and Liberty.
Related topics: Deployment, routing, and state · JDBC, pools, and transaction outcomes · JVM, logs, and time-based diagnosis
Establish the chain from central configuration through node to process.
Reference: Node agent and master repository · DR WebSphere traditional ND 9.0.5; maintenance baseline 9.0.5.29 (2026-09-08); documentation reviewed 2026-09-30