InfoCenter Home > 8.4.1.3: Workload Management/Cloning/Remote Administration ProblemsUnlike WebSphere Application Server Advanced Edition, the Standard Edition does not support the Workload Management function. WebSphere Application Server Standard Edition is limited to a single physical server. However, Standard Edition provides multiple JVMs that can be mapped to multiple virtual hosts on a single HTTP Server. Therefore multiple Web sites can still be hosted using one Standard Edition Application Server. Description of the Workload Management function and cloningLike the Standard Edition, WebSphere Application Server Advanced Edition provides multiple JVMs, but it also supports distributed system management for networks and clusters of Advanced Edition Application Servers. Distributed system management is an outcome of the the Workload Management function. This function enables cloning, or creating instances of a model. Clones can be created on a single machine or across multiple machines in a cluster. Modifying a model automatically propagates the changes to all of its clones. By administering a model, you can simultaneously administer several copies of a server (the clones). Scalability in a workload management environment occurs in two forms:
With Workload Management, requests can be routed to any server on any node with the same results. Workload Management provides for Failover where requests are routed to other nodes (servers) when one node fails. Failover occurs without affecting throughput or reliability. Workload Management and Cloning problem descriptionsThe following resources can be cloned. Select a specific type of resource to view typical problem scenarios. Application Server issuesThere may be some performance impacts using cloning:
EJB Containers and Enterprise BeansHomes of session beans have special information to indicate that these "homes" are workload management (WLM) enabled; that is, deployed on one or more servers. When a client accesses the home of a session bean, the client is referred to the homeOfHomes on the Admin Server. The client then creates proxies for each clone using a specific workload management policy as for example, round robin.
Servlet Engines, Web applications and ServletsIf requests are going to one server, verify that your model has more than one clone. Also verify that each clone has xBean deployed. This particularly applies to a Thin Servlet Redirector configuration since the ThinRedirector is an EJB client to the RemoteSRP bean. Also verify that the first server in the model is running. The first server must be running for the lookup phase to work correctly. Remote AdministrationYou can remotely administer WebSphere Application Server using: Remote admin consoleUse can run admin console remotely using the adminclient.bat file on Windows NT, or adminclient.sh file on UNIX. See article Administrative models for more information on implementing a remote admin client. Typical remote admin console problems are:
X Windows clients on UNIX machinesX windows client software can run on any platform but requires a UNIX X Windows Server. (Currently the X Windows Server is only available on AIX and Solaris platforms.) Typical X window client problems are:
Web based WebSphere admin consoleSee article Web administrative console overview for information on configuring and implementing a Web based admin console. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|