How to refresh configuration changes
Can some tell me, when you make a change to TCP protocol (in my case IDLE TIMEOUT and Keep Alive Interval) when those new values take affect after I click the update button? Is it dynamic and any new connection would then connect with the new rules, or do i need to take the resource out of the pool and then put it back in for the new setting to take affect? I'm trying to adjust settings so long lived connections do not timeout, but I don't seem to see a difference if I increase the idle timeout to one minute longer than the default. This tells me my changes are not taking affect. Currently the defaults are in place (300/1800). I have a client that times out at 5 minutes, which makes sense with the 300 Idle timeout default. But if I change it to 360 it should timeout at 6 minutes. But it stays at 5 minute time out? My F5 Admin, doesn't seem to know the answer to this?!
F5 ASM: Can it be used to analyze MQ messages?
Hi there, I'm currently looking for an application-layer content inspection solution for IBM MQ traffic. I'm aware from experience with F5 LTM that it can act as an inline proxy and encrypt/decrypt messages with ease, but I can't find any information that indicates that ASM would support this functionality for this particular application. Is it possible to add this functionality through the use of custom rules/scripts/filters, or is this something that ASM supports "out of the box"?