You can install, start, and access the administrative console. You can also specify console preferences and access help.
Scripting is a non-graphical alternative that you can use to configure and manage WebSphere® Application Server.
This topic describes how to use Java application programming interfaces (APIs) to administer WebSphere Application Server and to manage your applications.
The product provides many tools that you can call from a command line.
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.
The startServer command reads the configuration file for the specified server process and starts that server process.
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.
Use the serverStatus command to obtain the status of one or all of the servers configured on a node.
The cleanupNode command cleans up a node configuration from the cell repository.
Use the registerNode command to register a stand-alone node with an administrative agent so that the administrative agent can manage the node.
Use the deregisterNode command to unregister a node from an administrative agent so that you can use the node stand-alone or register the node with another administrative agent.
The backupConfig command is a simple utility to back up the configuration of your node to a file.
Use the restoreConfig command to restore the configuration of your node after backing up the configuration using the backupConfig command.
The versionInfo command generates a report that includes a list of installed fix packs and interim fixes.
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.
The historyInfo command generates a report that includes a history of installed or uninstalled fix packs and interim fixes.
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.
The managesdk command provides the names of software development kits that are used by the product.
The GenPluginCfg command is used to regenerate the WebSphere web server plug-in configuration file, plugin-cfg.xml.
Use the EARExpander command to expand an enterprise archive (EAR) file into a directory to run the application in that EAR file.
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.
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.
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.
The queryCertificate command uses an implementation class that is passed to communicate with a certificate authority (CA) server and query a certificate.
If you want to enable WebSphere Application Server security, you need to provide the command line tools with authentication information.