WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

System A
1. Copy the file targetTree.xml to the /staticRoutes directory.
Note: The static routing information is not updated automatically.
Whenever there is a change (for example when an application is installed
or removed) the routing information needs to be manually refreshed. The
DMZ secure proxy servers needs to be restarted after each refresh of the
routing information to activate the change. If this is not feasible you need to
switch the dynamic routing to use a lower security level.
2. Go to the /bin directory and start wsadmin -lang jython
-conntype NONE.
3. Import the profile changes from /DMZProxy.car by running the
wsadmin command shown in Example 5-3.
Example 5-3 Sample code to import proxy profile
AdminTask.importProxyProfile('-archive /DMZProxy.car
-deleteExistingServers true')
AdminConfig.save()
4. Start the DMZ secure proxy server.
5.3.5 Topology with redundancy of multiple components
To remove single points of failure in a topology, redundant components are
added. Most components in a WebSphere Application Server topology provide
the options to implement redundancy. For example, Load Balancer hot standby
server with the primary Load Balancer server, clustered Web servers, clustered
application servers, and so forth. The topology shown in Figure 5-8 on page 161
illustrates the minimum WebSphere components used in an installation with the
usual high availability requirements (whereby the number of application servers
might vary).
160 WebSphere Application Server V7.0: Concepts, Planning, and Design