(iSeries)
Starting WAS on IBM i
After installing, start the WebSphere Application Server environment to begin using it.
This article assumes that we have configured your WAS for IBM i installation. See Configure the product after installation on IBM i if you have not yet configured the product.
Use this procedure to start the WAS environment.
Tasks
- Start the default application server profile.
Start the default standalone application server, as described in Starting default standalone application server profiles on IBM i.
Choose this task if we intend to run a standalone, unfederated application server.
Start and configure the default deployment manager profile, as described in Starting and configuring default deployment manager profiles on IBM i
Choose this task if we installed WAS Network Deployment and plan to run a deployment manager profile with one or more federated application server nodes.
- Configure the virtual host, as described in Configure virtual hosts on IBM i.
If our external HTTP server configuration uses ports other than the default ports, we must update the Host Aliases table for the virtual host to reflect the correct HTTP port number.
- Start the HTTP server instance, as described in Starting HTTP server instances on IBM i.
Start the HTTP server so that your application server profile can receive and respond to client requests.
- Start the default application server node, as described in Starting default application server nodes on IBM i.
If we installed WAS Network Deployment and are running a deployment manager profile with one or more federated application server nodes, perform this step to start the default application server node.
What to do next
Go to Starting default standalone application server profiles on IBM i to continue the installation.
(Dist) Or go to Starting default application server nodes on IBM i to continue the installation.
Subtopics
- (iSeries) Starting default standalone application server profiles on IBM i
WAS provides a default application server profile that contains several example applications. The default standalone profile is ready to run after we install, configure, and start WAS. Start the default standalone application server profile to use it.- (iSeries) Starting and configuring default deployment manager profiles on IBM i
WAS Network Deployment provides a configurable default deployment manager profile that you create using the manageprofiles command after installation.- (iSeries) Configure virtual hosts on IBM i
A virtual host is a configuration entity that allows WAS to treat multiple host machines or port numbers as a single logical host (virtual host) for configuration purposes. Each virtual host can be associated with multiple aliases. Each alias is a particular host name and port number. Configure the virtual host to make resources available for client requests.- (iSeries) Starting HTTP server instances on IBM i
IBM HTTP Server for IBM i runs in the QHTTPSVR subsystem, and each HTTP Server instance starts multiple jobs. The WAS code that plugs into IBM HTTP Server for IBM i runs in the HTTP Server job that communicates with one or more application servers. Start the HTTP Server instance to enable communication with the application server.- (iSeries) Starting default application server nodes on IBM i
Start the default application server node from the deployment manager administrative console.
Starting default standalone application server profiles on IBM i Starting and configuring default deployment manager profiles on IBM i Configure virtual hosts on IBM i Starting HTTP server instances on IBM i Starting default application server nodes on IBM i