Using the administrative clients

  • Using the administrative console

    You can install, start, and access the administrative console. You can also specify console preferences and access help.

  • Getting started with wsadmin scripting

    Scripting is a non-graphical alternative that you can use to configure and manage WebSphere® Application Server.

  • Using administrative programs (JMX)

    This topic describes how to use Java application programming interfaces (APIs) to administer WebSphere Application Server and to manage your applications.

  • Using command-line tools

    The product provides many tools that you can call from a command line.

  • startServer command

    The startServer command reads the configuration file for the specified server process and starts that server process.

  • stopServer command

    The stopServer command reads the configuration file for the specified server process. This command sends a Java management extensions (JMX) command to the server telling it to shut down.

  • startManager command

    Use the startManager command to manipulate a deployment manager with scripting.

  • stopManager command

    The stopManager command reads the configuration file for the WebSphere Application Server, Network Deployment manager process.

  • startNode command

    The startNode command reads the configuration file for the node agent process and constructs a launch command.

  • stopNode command

    The stopNode command reads the configuration file for the node agent process and sends a Java Management Extensions (JMX) command telling the node agent to shut down.

  • serverStatus command

    Use the serverStatus command to obtain the status of one or all of the servers configured on a node.

  • addNode command

    The addNode command incorporates an application server installation into a cell.

  • removeNode command

    The removeNode command returns a node from a WebSphere Application Server, Network Deployment distributed administration cell to a stand-alone application server installation.

  • cleanupNode command

    The cleanupNode command cleans up a node configuration from the cell repository.

  • syncNode command

    The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

  • renameNode command

    A short name is assigned to a node during installation and customization. Use the renameNode command to modify the node name of a federated server.

  • registerNode command

    Use the registerNode command to register a stand-alone node with an administrative agent so that the administrative agent can manage the node.

  • deregisterNode command

    Use the deregisterNode command to unregister a node from an administrative agent so that you can use the node stand-alone, register the node with another administrative agent, or federate the node with the deployment manager.

  • backupConfig command

    The backupConfig command is a simple utility to back up the configuration of your node to a file.

  • restoreConfig command

    Use the restoreConfig command to restore the configuration of your node after backing up the configuration using the backupConfig command.

  • versionInfo command

    The versionInfo command generates a report that includes a list of installed fix packs and interim fixes.

  • genVersionReport command

    The genVersionReport command uses the versionInfo command to generate the versionReport.html report file in the current working directory, which is usually the bin directory. The report includes a list of installed fix packs and interim fixes.

  • historyInfo command

    The historyInfo command generates a report that includes a history of installed or uninstalled fix packs and interim fixes.

  • genHistoryReport command

    The genHistoryReport command generates the historyReport.html report file in the current working directory, which is usually the bin directory. The report includes a list of installed or uninstalled fix packs and interim fixes. The genHistoryReport script invokes the historyInfo script specifying the correct parameters to place the information generated into an HTML file in the current directory.

  • managesdk command

    The managesdk command provides the names of software development kits that are used by the product.

  • GenPluginCfg command

    The GenPluginCfg command is used to regenerate the WebSphere web server plug-in configuration file, plugin-cfg.xml.

  • EARExpander command

    Use the EARExpander command to expand an enterprise archive (EAR) file into a directory to run the application in that EAR file.

  • revokeCertificate command

    The revokeCertificate command uses an implementation class that is passed to communicate with a certificate authority (CA) server to revoke a certificate. Processing this command sends a revocation request to the CA server to mark this certificate as revoked.

  • requestCertificate command

    The requestCertificate command uses an implementation class that is passed in to communicate with a certificate authority (CA) server to request a CA signed certificate. The command then adds the certificate to a supplied keystore.

  • createCertRequest command

    The createCertRequest command creates a PKCS10 certificate request and stores it in a client keystore so that it can be used to send to a certificate authority (CA) server using the requestCertificate command line utility.

  • queryCertificate command

    The queryCertificate command uses an implementation class that is passed to communicate with a certificate authority (CA) server and query a certificate.

  • restoreJobManager command

    The restoreJobManager command restores the job manager database from a previous backup.

  • Example: Security and the command line tools

    If you want to enable WebSphere Application Server security, you need to provide the command line tools with authentication information.

  • Using MVS console commands

    This topics discusses the MVS console commands that you can use to start, stop, and modify the product nodes and servers.

  • START command

    The START command reads the configuration file for the specified server process and starts the server, deployment manger, node agent, administrative agent, or job manager.

  • STOP command

    The STOP command reads the configuration file for the specified server process and stops the server, deployment manger, node agent, administrative agent, or job manager.

  • Modify command

    You can issue the modify command from the MVS console to dynamically modify product operations.

  • Display command with examples

    The display command is useful for obtaining data on a variety of processes.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 3:08:41 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=container_using_admin_clients
File name: container_using_admin_clients.html