WAS v8.5 > Deploy applications > Deploy business-level applicationsStart business-level applications
We can start a business-level application not running (has a status of Stopped). The application must contain code that can run on a server to start.
Before beginning
The application must be installed on a server. By default, the application starts automatically when the server starts. We can start and stop business-level applications manually using the dmgr console or wsadmin commands.
This topic describes how to use the dmgr console to start a business-level application.
- Go to the Business-level applications page.
Click Applications > Application Types > Business-level applications in the console navigation tree.
- Select the check box for the application you want started.
- Click Start. WAS v8.5 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 the application started displays at the top the page.
If the business-level application does not start, ensure the deployment target to which the application maps is running and try starting the application again.
IBM recommends using the HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.
If the application contains 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 v8 deployment target or to a v7 deployment target that supports SCA composites.
- If an asset composition unit uses an 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 that supports SCA composites when we add the asset to the business-level application. We 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 containing the composite in the META-INF/sca-deployables directory. We can place the other composite files anywhere else within the archive.
What to do next
To restart a running application, select the application to restart, click Stop and then click Start.
Related
Create business-level applications
Deploy business-level applications
Start a business-level application using programming
Stopping a business-level application using programming
Start business-level applications using scripting
Stopping business-level applications using scripting
Troubleshoot applications with HPEL