WAS v8.5 > Administer applications and their environment

Use the administrative clients

Subtopics

• Use the dmgr console
  We can install, start, and access the dmgr console. We can also specify console preferences and access help.
• Get started with wsadmin scripting
  Scripting is a non-graphical alternative used to manage WebSphere Application Server.
• Use administrative programs (JMX)
  This topic describes how to use Java APIs to administer WAS and to manage the applications.
• Use command-line tools
  WAS v8.5 provides many tools that we can call from a command line.
• manageprofiles command
  Use manageprofiles.sh to create, delete, augment, back up, and restore profiles, which define runtime environments. Using profiles instead of multiple product installations saves disk space and simplifies updating the product because a single set of core product files is maintained.
• 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.
• serverStatus command
  Use the serverStatus command to obtain the status of one or all of the servers configured on a node.
• cleanupNode command
  The cleanupNode command cleans up a node configuration from the cell repository.
• registerNode command
  Use the registerNode command to register a stand-alone node with an administrative agent so the administrative agent can manage the node.
• deregisterNode command
  Use the deregisterNode command to unregister a node from an administrative agent so that we can use the node stand-alone or register the node with another administrative agent.
• 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 backupConfig.
• 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 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 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.
• Example: Security and the command line tools
  To enable WAS security, provide the command line tools with authentication information.

+

Search Tips   |   Advanced Search