WebSphere Virtual Enterprise, Version 6.1.1
             Operating Systems: Linux, Solaris, Windows


Configuring VMware Infrastructure 3 platforms and WebSphere Virtual Enterprise

To configure WebSphere® Virtual Enterprise to work with VMware Infrastructure 3 platforms, you must configure security so that the servers can communicate with each other and configure custom properties on your deployment manager to define the vCenter or ESX servers.

Before you begin

About this task

When you have multiple nodes running on a physical computer with VMware Infrastructure 3 platforms, WebSphere Virtual Enterprise can contact VMware through Web services. You can configure this communication in the administrative console by creating cell-wide custom properties. These custom properties define the URL, user ID, and password for thevCenter or ESX servers. You also must configure your key stores to retrieve signers from the vCenter or ESX servers.

How you configure your VMware environment to work with WebSphere Virtual Enterprise is dependent on your VMware configuration. You must create the custom properties for enough of the servers in your environment to make WebSphere Virtual Enterprise aware of all of the virtual machines and physical computers.
  • If you are using only ESX servers, you must configure the enough of the individual servers to make WebSphere Virtual Enterprise aware of the physical servers and virtual machines in the environment.
  • If you are using a vCenter server to manage your environment, you can connect to the vCenter server, which establishes communication with all of the virtual machines and servers that the vCenter server manages. You do not need to connect to each ESX server. If a vCenter is available, the best practice is to connect to the vCenter server instead of each ESX server.
  • If you are running multiple vCenter servers with a Microsoft Cluster Server (MSCS) to provide high availability, you can configure the key stores and custom properties for each vCenter server.

If you do not configure WebSphere Virtual Enterprise to work with VMware Infrastructure 3 platforms, the WebSphere Virtual Enterprise environment does not understand that the nodes are on virtual machines, and as a result, the machine processor or memory might be overloaded.

Procedure

Results

By configuring WebSphere Virtual Enterprise to work with vCenter or ESX, better service differentiation management results than using vCenter or ESX alone. With WebSphere Virtual Enterprise, you can add application-level goals and characteristics so that the autonomic managers can perform the necessary flow control in your virtualized environment.

What to do next

If timeout errors are occurring, you can increase the com.ibm.websphere.webservices.http.connectionTimeout and com.ibm.websphere.webservices.http.SocketTimeout custom property values from the default of 300 seconds to 600 seconds. Consider making this change when you have a virtualized environment with a large number of physical and virtual machines. For example, if your environment has 400 physical machines, when requests are sent from WebSphere Virtual Enterprise to the hypervisor for configuration information, the hypervisor contacts each of the 400 physical machines. If each request takes 1 second to complete, the default timeout of 300 seconds is not long enough to process all of the requests, and a read timeout results. See HTTP transport custom properties for Web services applications for more information about the custom properties.

Configure middleware servers on your WebSphere nodes.




Subtopics
VMware Infrastructure 3 platforms and WebSphere Virtual Enterprise
Related tasks
Related reference
Related information
VMware custom properties
Task topic    

Terms of Use | Feedback

Last updated: Oct 30, 2009 1:32:42 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1m1/index.jsp?topic=/com.ibm.websphere.ops.doc/info/odoe_task/tvmware.html