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 displays at
the top the page.
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.
If an application
server on which the application is deployed synchronizes configuration with the
deployment manager during server startup, then the application
might not start and a DeploymentDescriptorLoadException error might
be written to the server SystemErr.log file. Stop and restart the
server, and then try starting the application again.
If the application contains Service Component
Architecture (SCA) composites and does not start, check for the following
problems:
- If SCA composite assets do not start, ensure that each asset is
mapped to a deployment target that is enabled for the Feature Pack
for SCA.
- If an asset composition unit uses an Enterprise JavaBean (EJB)
binding and does not start because it has a non-WebSphere
target of "null", delete the asset composition unit and add
it again to the business-level application. Specify a target enabled
for the Feature Pack for SCA when you add the asset to the business-level
application. You cannot change the target after deployment.
- If the META-INF/sca-deployables directory
has multiple SCA composite files and the application does not start
because the product cannot obtain the CompUnitInfoLoader value,
place only the file that contains the composite in the META-INF/sca-deployables directory.
You can place the other composite files anywhere else within the archive.
In multiple-node
environments, synchronize the nodes after you save changes to the
target before starting the business-level application.
What to do next
To restart a running application, select the application
you want to restart, click Stop and then click Start.