Forum Discussion
Migrating WAS6 to WAS8.5
We are currently migrating from WAS 6.0 (IBM-WebSphere Application Server ND) to WAS 8.5.
We take this migration to remove the IHS server with WAS plugin to transfer this functionality to the BigIP.
We followed this procedure: http://www.f5.com/pdf/deployment-guides/ibm-websphere-8-dg.pdf.
However, when the BigIP used as proxy, the WAS application server return the application port in the URL instead of 80.
For example:
URL
Response
http://m19.p.f5.com:19082/ATL_W/gui/css/atlas.css
http://m19.p.f5.com/ATL_W/gui/css/atlas.css
Is it missing something up?
3 Replies
- Kevin_Stewart
Employee
I didn't see anything in the guide that addresses this "reverse proxy issue", and I can't speak for the WAS8.5 configuration, but at the very least I believe you can integrate a stream iRule to replace values in the response payload. Take a look at the STREAM::expression wiki page for some great examples of how to do this. - nicolasjc
Nimbostratus
Hi,
The IHS insert a couple of feild in the http header that the WAS understand. It tell the WAS that the service has been proxyed.
When you do a tcpdump on the IHS you will find the Header $WSSP with the value "80" ( in your case).
You need to create a HTTP profile and insert that feild in it.
look like this in tmsh:
list ltm profile http http_was
ltm profile http http_was {
.
.
.
header-insert "\\$WSSP: 80"
.
.
.
}
let me know if it solve your problem... - Jean-Sebastien1
Nimbostratus
It's work. Thank you nicolasjc. Maybe F5 can add this on documentation
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com