LEARN. PRACTICE. GROW.Concept and mechanism
A request can cross a load balancer, IHS, plugin, and application server. Success on a direct backend call does not establish that the entire path works. The plugin uses configuration containing targets and mappings; generating plugin-cfg.xml differs from propagating it to the path consumed by IHS. Establish the effective file, its freshness, and application and virtual-host mappings. A manual edit can be lost during the next generation, so the fix should be reproducible from approved configuration. If only a new URI fails at the frontend, compare that mapping before attributing failure to the database or restarting every JVM.
Guided application
Another failure class appears when a release includes libraries conflicting with existing ones. Identify class version, origin, and class loader; globally switching to parent-last can introduce other conflicts. Session affinity also does not guarantee recovery: it routes requests to a member but does not itself replicate state. ND supports configured database persistence or memory replication mechanisms with their own requirements. During a rolling update, evaluate remaining member capacity and session, application, and data-schema compatibility. In a fictional portal, check authentication and session continuity after removing a member, alongside the health check. Document rollback and observed limits without promising zero downtime merely because a cluster exists.
New export works directly but returns 404 on IHS: compare URI, virtual host, and effective plugin copy.
Common pitfalls
Generation as propagation; parent-last as a universal fix; affinity as replication.
Related topics: ND topology and effective configuration · JDBC, pools, and transaction outcomes · JVM, logs, and time-based diagnosis
Validate the complete path, loaded libraries, and state continuity.
Reference: Plug-in configuration and propagation · DR WebSphere traditional ND 9.0.5; maintenance baseline 9.0.5.29 (2026-09-08); documentation reviewed 2026-09-30