You can start a business-level application that is not running (has a status of
Stopped). The application must contain code that can run on a server to
start.
Before you begin
The application must be installed on a server. By default, the application starts automatically
when the server starts.
About this task
You can start and stop business-level applications manually using the administrative console or
wsadmin commands.
This topic describes how to use the administrative console to start a business-level
application.
Procedure
-
Go to the Business-level applications page.
Click in the console navigation tree.
-
Select the check box for the application you want started.
-
Click Start.
The product runs the application and changes the state of the application to
Started. The status is changed to partially started if not all
servers on which the application is deployed are running.
Results
A message stating that the application started is displayed.
If the business-level application does not start, ensure that the deployment target to which the
application maps is running and try starting the application again.
Note: This topic references one or more of the application server log files. As a
recommended alternative, you can configure the server to use the High Performance Extensible Logging
(HPEL) log and trace infrastructure instead of using SystemOut.log ,
SystemErr.log, trace.log, and
activity.log files on distributed and IBM®
i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace
information using the LogViewer command-line tool from your server profile bin directory. See the
information about using HPEL to troubleshoot applications for more information on using HPEL.
What to do next
To restart a running application, select the application you want to restart, click
Stop and then click Start.