Description Syntax Example startApplication

WLST Command and Variable Reference 3-27

3.5.6.3 Example

The following example redeploys myApp application using the plan.xml file located in the c:myapps directory. wls:mydomainserverConfig progress=redeploymyApp c:myappsplan.xml Redeploying application myApp ... Redeployment of myApp is successful wls:mydomainserverConfig The previous example stores the WLSTProgress object returned in a user-defined variable, in this case, progress. You can then use the progress variable to access the state of the redeploy command. For example: wls:mydomainserverConfigServers progress.getState completed wls:mydomainserverConfigServers For more information about the WLSTProgress object, see WLSTProgress Object in Oracle WebLogic Scripting Tool.

3.5.7 startApplication

Command Category: Deployment Commands Use with WLST: Online

3.5.7.1 Description

Starts an application, making it available to users. The application must be fully configured and available in the WebLogic domain. The startApplication command returns a WLSTProgress object that you can access to check the status of the command. For more information about the WLSTProgress object, see WLSTProgress Object in Oracle WebLogic Scripting Tool. In the event of an error, the command returns a WLSTException.

3.5.7.2 Syntax

startApplicationappName, [options] planPath Optional. Name of the deployment plan file. The filename can be absolute or relative to the application directory. This argument defaults to the planplan.xml file in the application directory, if one exists. options Optional. Comma-separated list of deployment options, specified as name-value pairs. For a list of valid deployment options, see options argument description in Section 3.5.1, deploy . In addition, the following deployment option can be specified for the redeploy command: ■ appPath —Name of the archive file or root of the exploded archive directory to be redeployed. ■ deploymentPrincipalName —String value specifying the principal for redeploying the file or archive during server starts. You can use this option to overwrite the current deployment-principal-name in the config.xml file. Argument Definition 3-28 Oracle Fusion Middleware WebLogic Scripting Tool Command Reference

3.5.7.3 Example

The following example starts the BigApp application with the specified deployment options. wls:mydomainserverConfigServers progress=startApplicationBigApp, stageMode=NOSTAGE, testMode=false Starting the application... Successfully started the application. The previous example stores the WLSTProgress object returned in a user-defined variable, in this case, progress. You can then use the progress variable to access the state of the startApplication command. For example: wls:mydomainserverConfigServers progress.getState completed wls:mydomainserverConfigServers For more information about the WLSTProgress object, see WLSTProgress Object in Oracle WebLogic Scripting Tool.

3.5.8 stopApplication