Manually refreshing WebSphere Application Server configuration with the proxy shared service

You can refresh an IBM® WebSphere® Application Server configuration.

About this task

If an IBM WebSphere Application Server instance fails to register with the elastic load balancer a deployment or update of a virtual application instance, you can manually refresh the configuration. If the Secure Sockets Layer (SSL) certificate for the WebSphere Application Server instance is updated, the elastic load balancer also updates the certificate in the storehouse.

Procedure

  1. Click Pattern > Virtual Application Instances (or Patterns > Manage > Virtual Application Instances in 2.3.3.3 or later).
  2. Select the virtual application instance.
  3. On the details pane, check the status of WebSphere Application Server in the Middleware perspective section. If WebSphere Application Server is in a failed state, you can restart the instance.
  4. Click Manage on the menu.
  5. Click the Operation tab.
  6. To recover a failed WebSphere Application Server instance, select it in the list. Under Fundamental settings, expand Start or restart the server and click Submit.
  7. Select the ELBClient instance.
  8. Expand Refresh Configuration with Proxy Shared Service.
  9. Click Submit.
    The elastic load balancer attempts to register WebSphere Application Server instances in the virtual application instance.
    • If a WebSphere Application Server instance registers successfully to the elastic load balancer, and the SSL certificate file is not updated, a message is displayed to inform you that a certificate update will not be done.
    • If a WebSphere Application Server instance registers successfully to the elastic load balancer, and the certificate file is updated, the certificate file is updated in the storehouse.
    • If WebSphere Application Server fails register to the elastic load balancer, the WebSphere Application Server registration configuration is refreshed. Before refreshing, the WebSphere Application Server role was in a Failed state. After successfully refreshing, the role is in Running state.

Results

WebSphere Application Server instances in the virtual application instance are registered and any updated certificates are stored in the storehouse.