Nimbostratus
Nimbostratus
Here is an example of our current Production Irule. When users connecting they get the weblogic login page first, however after successfully logging into the portal and clicking on the apps link (i.e. /APP..), they get redirected to the APACHE pool since those contents are hosted on the apache server and not the weblogic or if they enter https://www.my-weblogic-server.com/APP01 "with the /APP.." in the URI, they will get prompted to login first before they are served up the contents off of the APACHE servers.
when HTTP_REQUEST {
switch -glob [string tolower [HTTP::uri]] {
"/APP01*" -
"/APP02" -
"/APP03" -
"/APP04" -
"/APP05*"
{
use pool APACHE-POOL
}
default {
use pool WEBLOGIC-POOL
}
}
}
What we want to accomplish is.
1. Allow only our QA dept to access the portal (it is not down during maintenance) to test. Their source IP is defined in the Data group.
2. send all users with IP address not defined in the datat group/class to the maintenace page so they do not login by mistake.
3. When the QA team login, they should be able to have the same ability to the portal as the i-rule defined above (they are able to get forwarded to the apche pool based on the /app... link they select.
Thank you for your help.
-AH