The simplest way is to address the backend host and port directly, skipping over any HTTP proxy tier.
If the cluster is behind some JSESSIONID-aware proxy server, you could test by mocking a JSESSIONID cookie whose second colon-separated field ends in the cloneID of the backend JVM you want to test. You can see the cloneID's in use in plugin-cfg.xml (if you use the WebSphere WebServer Plug-in) or by examining headers generated while accessing your application.
If you use the Intelligent Management for WebServer features of the WAS Plugin running in IHS or Apache, you could specify custom routing rules:
https://www.ibm.com/docs/en/was-zos/9.0.5?topic=rules-intelligent-management-web-servers-routing to send a specific client to a specific JVM.
Even if your end user traffic does not use this solution, you could setup a webserver w/ Intelligent Management features and point at it during testing.
------------------------------
Eric Covener
------------------------------
Original Message:
Sent: Sun February 27, 2022 03:20 AM
From: Essam Ali
Subject: WebSphere Application URL
Hi everyone,
I have a websphere application server with many nodes. There is an application installed on all nodes.
For testing and developing purposes I need to open the application on a specific node.
How can I run the application installed on one node of the WebSphere AS? Can I use a direct link or use the ssh command line?
Please help.
Thanks
------------------------------
Essam Ali
------------------------------