reference

• deleteObject
  Calling deleteObject on a particular server will remove it from the load balancer. This is the only way to remove a service from your load balancer. If you wish to remove a server, first call this function, then reload the virtualIpAddress object and edit the remaining services to reflect the other changes that you wish to make.
• getGraphImage
  Get the graph image for a load balancer service based on the supplied graph type and metric. The available graph types are: 'connections' and 'status', and the available metrics are: 'day', 'week' and 'month'. This method returns the raw binary image data.
• getObject
  getObject retrieves the SoftLayer_Network_LoadBalancer_Service object whose ID number corresponds to the ID number of the init parameter passed to the SoftLayer_Network_LoadBalancer_Service service. You can only retrieve services on load balancers assigned to your account, and it is recommended that you simply retrieve the entire load balancer, as an individual service has no explicit purpose without its 'siblings'.
• getStatus
  Returns an array of SoftLayer_Container_Network_LoadBalancer_StatusEntry objects. A SoftLayer_Container_Network_LoadBalancer_StatusEntry object has two variables, 'Label' and 'Value' Calling this function executes a command on the physical load balancer itself, and therefore should be called infrequently. For a general idea of the load balancer service, use the 'peakConnections' variable on the Type Possible values for 'Label' are: * IP Address * Port * Server Status * Load Status * Current Connections * Total Hits Not all labels are guaranteed to be returned.
• getVip
  The load balancer that this service belongs to.
• resetPeakConnections
  Calling resetPeakConnections will set the peakConnections variable to zero on this particular object. Peak connections will continue to increase normally after this method call, it will only temporarily reset the statistic to zero, until the next time it is polled.
• SoftLayer_Network_LoadBalancer_Service
  The SoftLayer_Network_LoadBalancer_Service data type contains all the information relating to a specific service (destination) on a particular load balancer. Information retained on the object itself is the the source and destination of the service, routing type, weight, and whether or not the service is currently enabled.
• SoftLayer_Network_LoadBalancer_Service
  Load balancer services represent the 'routes' that the load balancer will have available to route requests. Each service has a source port (located on the load balancer itself), and a destination IP address and port. Any services that share a source port will be used as potential routes for traffic coming into the load balancer on that port. For instance, if there are two services that both have a source port of 80, both of those services will be used as balanced servers for traffic coming into your virtual IP on port 80. For a more complete example, consider the following scenario: :Virtual IP Address: 123.123.123.123 :Servers on your account: :12.34.56.78 :23.45.67.89 :You want to set up both HTTP(port 80) and HTTPS (port 443) on each of those servers. :You will need four services: {| |- ! SourcePort ! DestinationIpAddress ! DestinationPort |- | 80 | 12.34.56.78 | 80 |- | 80 | 23.45.67.89 | 80 |- | 443 | 12.34.56.78 | 443 |- | 443 | 23.45.67.89 | 443 |} The services also have a routing type, these ALSO need to be the same for services that share the same port. For this example, the services with a source port of 80 should have HTTP as their type. The other two services should have TCP as their type. The affect of other variables are listed in their individual documentation.