Use the administrative clients

Subtopics

• Use the administrative console
  We can install, start, and access the administrative console. We can also specify console preferences and access help.

• Get started with wsadmin scripting
  Scripting is a non-graphical alternative that we can use to configure and manage WebSphere Application Server.

• Use administrative programs (JMX)
  This topic describes how to use Java APIs to administer WebSphere Application Server and to manage the applications.

• Use command-line tools
  The product provides many tools that we can call from a command line.

• manageprofiles command
  Use the manageprofiles command 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.

• startManager command
  Use the startManager command to manipulate a deployment manager .

• stopManager command
  The stopManager command reads the configuration file for the WAS Network dmgr 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 JMX (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 WAS 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 we 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 the node to a file.

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

• (iseries) checkprereqs command
  The checkprereqs command runs the prerequisite validator tool.

• (iseries) prerequisite validator tool
  The prerequisite validator tool verifies the WAS installation, ensures that we have the appropriate prerequisite software and PTFs installed, and verifies certain configuration settings required by the product.

• 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.

• (iseries) ivt command
  The install verification (ivt) script verifies that the application server for an instance is functioning correctly.

• (iseries) port validator tool
  The port validator tool verifies the WAS configuration to ensure that we do not have port conflicts between WebSphere Application Server profiles and products.

• 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.

• (iseries) Configure Qshell to run WebSphere scripts
  We can configure Qshell to run product scripts for IBM i.

• (iseries) Qshell environment variables
  WebSphere Application Server provides these Qshell environment variables that affect the WAS scripts.

• (iseries) Granting authority to a profile using the IBM i command line
  To grant authority to objects and directories in a profile, run the grtwasaut command from the Qshell command line.

• (iseries) Revoking authority to a profile using the IBM i command line
  To revoke authority to objects and directories in a profile, run the rvkwasaut script from the Qshell command line.

• (iseries) enbprfwas command
  The enbprfwas command enables a profile to allow an application server to run under it and optionally changes the group profile to QEJBSVR.

• (iseries) configureOs400WebServerDefinition command
  The configureOs400WebServerDefinition command creates a web server definition in a WAS or dmgr profile.

• (iseries) removeOs400WebServerDefinition command
  The removeOs400WebServerDefinition command deletes a web server definition from the configuration repository of a Standalone or dmgr profile.

• (iseries) chgwassvr command
  The chgwassvr command allows us to change the ports for an application server within a profile.

• (iseries) dspwasinst command
  The dspwasinst command displays information about a profile and the application servers it contains.

• (iseries) enablejvm command (deprecated)
  The enablejvm command enables you to configure the application server or a specific profile to use the IBM Technology for Java Virtual Machine, by choosing either option 11 or option 12 of the IBM Developer Kit for Java.

• (iseries) heapMonitor command
  The heapMonitor command manages the iSeries WebSphere Custom Service Heap Monitor, which sends messages to QSYSOPR when the WebSphere Java heap is close to exceeding or exceeds the storage pool size.

• (iseries) rvkwasaut command
  The rvkwasaut command revokes user authority to a profile and the objects associated with it.

• (iseries) servicetools command
  The servicetools command includes serviceability tools that we can use to troubleshoot WebSphere Application Server.

• (iseries) updwashost command
  The updwashost script updates a profile if the host name of the server is changed.

• (iseries) grtwasaut command
  The grtwasaut command grants a user authority to a profile and the objects associated with it.

• 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.

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

• Example: Security and the tools
  To enable WAS security, provide the tools with authentication information.

• (zos) Use MVS console commands
  This topics discusses the MVS console commands that we can use to start, stop, and modify the product nodes and servers.

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

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

• (zos) Modify command
  We can issue the modify command from the MVS™ console to dynamically modify product operations.

• (zos) Display command with examples
  The display command is useful for obtaining data on a variety of processes.