Unregistering servers

Edit online

You can discontinue the monitoring of a server. Unregistering a server does not affect its operation.

About this task

You must have a user profile with the Manage WebSphere inventory permission. For more information, see Configuring roles and permissions.
Note: Unregistering a server results in the deletion of data about the server, its vulnerabilities, its fix history, and its health investigations from the WebSphere Automation database. Any audit reports that are generated after a server is unregistered do not include these data.

Procedure

  1. Log in to WebSphere Automation; in the menu, click Operate > Application runtimes.
    For more information, see Accessing the WebSphere Automation UI.
  2. Open the Server management page, as shown in the following image.
    Figure 1. Viewing Server management page with an inventory of managed application servers
    Example Server management page showing inventory of managed application servers in a table. Column headings include Server, Hostname, Operating system, WebSphere version, Java SDK version, Topology, and action controls.
    If you do not see the menu option Operate > Application Runtimes, or if you see a message that you are not authorized, then you do not have permission to access the page. For more information about permissions, see Roles and permissions. If you do not see a listing of servers, then you need to register your servers with WebSphere Automation. For instructions on registering servers with WebSphere Automation, see Registering a server.
  3. Locate the server that you want to unregister in the list, click its action menu (the three-dot icon) and select Remove server.
    The server is unregistered from WebSphere Automation and is no longer monitored. To prevent the server from being registered again inadvertently, you must disable the usage metering feature on the removed server. Follow the instructions in the following note.
    Note: To prevent the server from being added again to the list of registered servers:
    1. WebSphere Application Server: Delete the was-usage-metering.properties file on the removed server.
    2. WebSphere Application Server Liberty: Edit the server.xml file on the removed server and remove the usageMetering-1.0 feature and the usageMetering configuration: 
      <featureManager>
   <feature>usageMetering-1.0</feature>
</featureManager>

<usageMetering url="your_usage_metering_URL"
apiKey="your_API_key"
sslRef="your_metering_sslRef"/>