Removing configuration objects with the wsadmin tool

Use this task to delete a configuration object from the configuration repository. This action only affects the configuration.

About this task

If a running instance of a configuration object exists when you remove the configuration, the change has no effect on the running instance.

Procedure

  1. Start the wsadmin scripting tool.
  2. Assign the ID string that identifies the server that you want to remove:

    Using Jacl:

    set s1 [$AdminConfig getid /Node:mynode/Server:myserver/]

    Using Jython:

    s1 = AdminConfig.getid('/Node:mynode/Server:myserver/')
    Table 1. AdminConfig getid command description . The following table describes the AdminConfig getid command.
    Element Description
    set is a Jacl command
    s1 is a variable name
    $ is a Jacl operator for substituting a variable name with its value
    AdminConfig is an object that represents the WebSphere® Application Server configuration
    getid is an AdminConfig command
    Node is an object type
    mynode is the host name of the node from which the server is removed
    Server is an object type
    myserver is the name of the server to remove
  3. Remove the configuration object. For example:
    • Using Jacl:

      $AdminConfig remove $s1
    • Using Jython:
      AdminConfig.remove(s1)
    Table 2. AdminConfig remove command description . The following table describes the AdminConfig remove command.
    Element Description
    $ is a Jacl operator for substituting a variable name with its value
    AdminConfig is an object that represents the WebSphere Application Server configuration
    remove is an AdminConfig command
    s1 evaluates the ID of the server that is specified in step number 2
  4. Save the configuration changes.
    Use the following command example to save your configuration changes:
    AdminConfig.save()
  5. In a network deployment environment only, synchronize the node.
    Use the syncActiveNode or syncNode scripts in the AdminNodeManagement script library to propagate the configuration changes to node or nodes.
    • Use the syncActiveNodes script to propagate the changes to each node in the cell, as the following example demonstrates:
      AdminNodeManagement.syncActiveNodes()
    • Use the syncNode script to propagate the changes to a specific node, as the following example demonstrates:
      AdminNodeManagement.syncNode("myNode")

Results

The application server configuration no longer contains a specific server object. Running servers are not affected.