This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
I'm not having much luck with hits on this topic - maybe I'm using the wrong search terms.
Assume WebLogic is serving to addresses:
127.0.0.1:7001 (local machine)
10.2.2.2:7001 (external interface).
Here is what I'm trying to do:
1) Take WebLogic offline
2) Serve 10.2.2.2:7001 from a different application (might say something like 'server is down for maintenance')
3) Do maintenance (may require bringing up the server only on port 127.0.0.1:7001 and interacting with it)
4) Switch interface 10.2.2.2:7001 back to running on WebLogic without restarting
The part I'm missing is how to enable another interface in WebLogic pragmatically after the domain has started (Step 4, if it is even possible).
Is there a way to do this or is there a better approach?
I could bring WebLogic offline again and restart it on both interfaces, but some of our slower VMs take 10+ minutes to restart. During that time, browsers would see 'could not connect' errors.
What's your domain configuration? It's normal to have the admin server listening on one IP address, and then one or more management server that listen on different IP addresses. Typically the admin server tends to be configured on the management LAN and the managed servers on the production LAN network.
Having more than one management server allows you load balance between them, and also failover. I suspect that is what you require - to be able to shutdown one of the servers and have the system failover onto the the running managed server?