Configure VMware Infrastructure 3 platforms and Intelligent Management

To configure Intelligent Management to work with VMware Infrastructure 3 platforms, configure security so that the servers can communicate with each other and configure custom properties on the deployment manager to define the vCenter or ESX servers.

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

The Intelligent Management configuration depends on the VMware configuration. Create the custom properties for the servers in the environment so that Intelligent Management can monitor all of the virtual machines and physical computers. To set the custom properties on the cell level, click System administration > Cell > Custom properties.

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


Results

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


What to do next

If timeout errors occur, we 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 Intelligent Management 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. For more information about the custom properties, read about HTTP transport custom properties for Web services applications.

Configure middleware servers on the WebSphere nodes.


Subtopics


Related tasks

  • Retrieve signers from a remote SSL port
  • Add middleware servers to configurations

  • HTTP transport custom properties for Web services applications
    VMware Infrastructure SDK


    Related information:

  • Intelligent Management: VMware custom properties