Administer unique portal farm installations
In a farm of uniquely installed IBM WebSphere Portal instances, each instance has its own release database while every other database domain is shared, including the JCR. Each unique installation also has its own unique IBM WAS configuration profile and its own WAS admin console. Therefore, application, server configuration, and service updates must be made on each server. IBM recommends that such updates be automated through configuration scripts that call the appropriate command line tools for making the changes (for example XMLAccess, wsadmin, etc), such that the exact same change can be repeated on each server without the possibility of injecting human error.
Update a single server
How we remove and restore a server from production traffic depends on the load balancing mechanism used. If we are using the WAS plugin for the HTTP Server, for example, it is a matter of temporarily removing that Server entry from the ServerCluster definition and either restarting the HTTP Server or waiting for the HTTP Server to reload the configuration (if automatic reload is enabled).
- Remove the server from the production traffic.
- Apply the update.
- Restart the server.
- Verify the change as appropriate.
- Restore the server back to the production traffic.
Parent: Administer a portal farm