Displaying and executing MBean operations

The Management Console allows you to perform operations on MBeans. These are specific actions that are performed in the resource adapter, e.g. resetting statistics counters or checking availability.

Every MBean possesses an Operations node. Clicking this node or choosing Show MBean Operations from the context menu outputs a table which lists all the operations for the corresponding MBean.

Figure 57: MBean operations

When you click an operation, the detailed information is displayed in the window at the bottom.

Operations that you can perform using the Management Console are identified accordingly in the column Invocable. In a similar way to when modifying attribute values, the Management Console can only execute operations which have no or only simple parameter types. Proceed as follows to execute this type of operation:

• In the operation's context menu, choose the command Invoke MBean Operation.... Alternatively, you can select the operation and click the Invoke button below the table.

• Enter the call (invocation) parameters in the subsequent dialog (if necessary). The dialog may consist of several sheets. The operation is not performed until you confirm with OK.

The Management Console outputs a message after execution. This contains either the result of the operation or an error message if it was not possible to perform the operation.

Switching a resource adapter in the cluster to another proxy

You can use the MBean operation selectProxyApplication to stop a proxy while the cluster is running and simultaneously switch the resource adapter(s) to a different proxy ("soft" switchover). This has the advantage of minimizing negative impacts on operation. In contrast, if you stop a running proxy in a proxy cluster directly via the context menu then the connections administered by this proxy are immediately cleared, with the result, for example, that open transactions are interrupted and may have to be rolled back.

You can avoid this by performing a "soft" switchover. Proceed as follows:

• Shut down the proxy using the UTM tool kdcshut and specify a wait time.

  To do this, open a shell or DOS command window and enter the following command (with "\" in Windows systems):

  <openUTM-Server_home>/ex/kdcshut <Proxy_home> time

  Here, <openUTM-Server_home> is the openUTM installation directory, <Proxy_home> is the fully qualified path name of the proxy and time is the wait time in minutes (recommended value: at least 10 minutes). On the one hand, this call prevents any new connections from being established and, on the other, it stops the proxy from being shut down immediately.

• Immediately after this in the Management Console, call the resource adapter MBean in a resource adapter instance that is operating with the proxy that you want to shut down. In this MBean, call the operation selectProxyApplication in order to assign a different proxy to the resource adapter instance. BeanConnect selects the new proxy automatically using internal algorithms.

  If the application server is configured as a cluster, you must perform this operation for every resource adapter instance in the application server cluster that is assigned to the proxy that you want to shut down. The resource adapter MBean's CurrentProxyUrl attribute indicates the proxy to which a resource adapter instance is assigned.

• Once you have switched the resource adapter to the new proxy, you can shut down the earlier proxy by calling kdcshut again and specifying a short wait time (e.g. 5 minutes):

  <openUTM-Server_home>/ex/kdcshut <Proxy_home> 5 G

  The parameters 5and Gcause the proxy to be shut down once all the connections have been cleared but at the latest at the end of the 5 minute wait time.