Commands for AdminApp


 

+

Search Tips   |   Advanced Search

 

Use AdminApp to install, modify, and administer applications.

To start the scripting client when no server is running, to use only local operations, use the option...

-conntype NONE

Running AdminApp in local mode against a running server is not recommended, as config changes will not be reflected in the running server config. You could corrupt the config.

In a dmgr environment, config updates are available only if a scripting client is connected to a dmgr.

When connected to a node agent or a managed appserver, you will not be able to update the config because the config for these server processes are copies of the master config which resides in the dmgr.

The following commands are available for AdminApp:

 

deleteUserAndGroupEntries

Delete users or groups for all roles. Delete user IDs and passwords for all of the RunAs roles defined in the application.

Target object None.

Required parameters

application name

Application of interest.

Optional parameters: None.

Examples...

 

edit

Edit an application or module in batch mode. No options are required.

Target object: None.

Required parameters

application name

Application of interest.

options

Options to apply to the application or module config.

Optional parameters: None.

Examples...

 

editInteractive

Edit an application or module in interactive mode. The editInteractive command changes the application deployment. Specify these changes in the options parameter. No options are required for the editInteractive command.

Target object: None.

Required parameters

application name

Application of interest.

options

Options to apply to the application or module config.

Optional parameters: None.

Examples...

 

export

Export an application.

Target object: None.

Required parameters

application name

Application of interest.

file name

File name to export app to.

Optional parameters

exportToLocal

Specifies that the system should export the application of interest to the file name specified on the local client machine.

Examples...

 

exportDDL

Extract the DDL from an application.

Target object: None.

Required parameters

application name

Application of interest.

directory name

Name of the directory to export app to.

Optional parameters

options

Options to pass to app specified.

Examples...

 

exportFile

Export the contents of a single file specified by the URI from the application of interest.

Target object: None.

Required parameters

application name

Application of interest.

URI

Single file to export. Specify the URI within the context of an application. For example...

META-INF/application.xml

To specify files within a module, the URI begins with a module URI. For example:

foo.war/WEB-INF/web.xml

filename

Fully qualified path and file name of the file to export to.

Optional parameters: None.

Examples...

 

getDeployStatus

Display the deployment status of the application. After installing or updating a large application, use this command to display detailed status information for application binary file expansion. We cannot start the application until the system extracts the application binaries.

Target object: None.

Required parameters

application name

Name of the application of interest.

Optional parameters: None.

Examples...

 

help

Display general help information about AdminApp.

Target object: None.

Required parameters: None.

Optional parameters

operation name

Specify this option to display help for an AdminApp command or installation option.

 

install

Install an application in non-interactive mode, given a fully qualified file name and a string of installation options. The options parameter is optional.

Target object: None.

Required parameters

ear file

Path of the .ear file to install.

Optional parameters

options

Specify the installation options for the command.

Examples...

Many options are available for this command. We can obtain a list of valid options for an EAR file with the following command:

Jacl...

$AdminApp options myApp.ear

Jython...

print AdminApp.options('myApp.ear')

We can also obtain help for each object with the following command:

Jacl...

$AdminApp help MapModulesToServers

Jython...

print AdminApp.help('MapModulesToServers')

 

installInteractive

Install an application in interactive mode, given a fully qualified file name and a string of installation options. The options parameter is optional.

Target object: None.

Required parameters

ear file

Path of the .ear file to install.

Optional parameters

options

Specify the installation options for the command.

Examples...

 

isAppReady

Determine if the specified application has been distributed and is ready to be run. Returns a value of true if the application is ready, or a value of false if the application is not ready.

This command is not supported when wsadmin is not connected to a server.

Target object: None.

Required parameters

application name

Specify the name of the application of interest.

Optional parameters

ignoreUnknownState

Tests to see if the specified application has been distributed and is ready to be run.

Valid values are true and false.

If true, nodes and servers with an unknown state will not be included in the final ready return.

The command returns a value of true if the application is ready or a value of false if the application is not ready.

This command is not supported when wsadmin is not connected to a server.

Sample output...

wsadmin>$AdminApp isAppReady PlantsByWebSphere
ADMA5071I: Distribution status check started for application PlantsByWebSphere.
WebSphere:cell=Michael-DellCell01,node=Michael-DellNode01,distribution=true,expansion=notprocessing
ADMA5011I: The cleanup of the temp directory for application PlantsByWebSphere is complete.
ADMA5072I: Distribution status check completed for application PlantsByWebSphere.
true

With ignoreUnknownState parameters:

ADMA5071I: Distribution status check started for application TEST.
WebSphere:cell=myCell,node=myNode,distribution=unknown
ADMA5011I: The cleanup of the temp directory for application TEST is complete.
ADMA5072I: Distribution status check completed for application TEST.
false

Jacl...

$AdminApp isAppReady DefaultApplication
$AdminApp isAppReady TEST true

Jython...

print AdminApp.isAppReady('DefaultApplication')
print AdminApp.isAppReady('TEST', 'true')

 

list

List the applications that are installed in the config.

Target object: None.

Required parameters: None.

Optional parameters

target

Lists the applications that are installed on a given target scope in the config.

Sample output

adminconsole
DefaultApplication
PlantsByWebSphere

Examples...

 

listModules

List the modules in an application.

Target object: None.

Required parameters

application name

Application of interest.

Optional parameters

options

List of appservers on which the modules are installed. The options parameter is optional. The valid option is -server.

Example:

wsadmin>$AdminApp listModules PlantsByWebSphere
PlantsByWebSphere#PlantsByWebSphere.war+WEB-INF/web.xml
PlantsByWebSphere#PlantsGallery.war+WEB-INF/web.xml
PlantsByWebSphere#PlantsByWebSphereEJB.jar+META-INF/ejb-jar.xml

We can pass this string to edit and editInteractive...

PlantsByWebSphere#ivtEJB.jar+META-INF/ejb-jar.xml PlantsByWebSphere#ivt_app.war+WEB-INF/web.xml

 

options

Display a list of options for installing an EAR file.

Target object: None.

Required parameters: None.

Optional parameters

EAR file

Specifies the EAR file of interest.

application name

Application for which to display a list of options for editing an existing application.

application module name

Module name for which to display a list of options for editing a module in an existing application. This parameter requires the same module name format as the output that is returned by the listModules command.

file, operations

Displays a list of options for installing or updating an application or application module file. Specify one of the following valid values:

  • installapp - Use this option to install the file specified.

  • updateapp - Use this option to update an existing application with the file specified.

  • addmodule - Use this option to add the module file specified to an existing application.

  • updatemodule - Use this option to update an existing module in an application with the module file specified.

Sample output...

WASX7112I:

The following options are valid for "PlantsByWebSphere"
MapRolesToUsers
BindJndiForEJBNonMessageBinding
MapEJBRefToEJB
MapWebModToVH
MapModulesToServers
distributeApp
nodistributeApp
useMetaDataFromBinary
nouseMetaDataFromBinary
createMBeansForResources
nocreateMBeansForResources
reloadEnabled
noreloadEnabled
verbose
installed.ear.destination
reloadInterval

Return the valid options for an EAR file:

Jacl...

$AdminApp options /WAS/AppServer/installableApps/PlantsByWebSphere.ear

Jython...

print AdminApp.options('/WAS/AppServer/installableApps/PlantsByWebSphere.ear')

Return the valid options for an application:

Return valid options for an application module:

Return the valid options for the operation that is requested with the input file:

 

publishWSDL

Publish WSDL files for an application.

Target object: None.

Required parameters

file name

File of interest.

application name

Application of interest

Optional parameters

SOAP address prefixes

SOAP address prefixes to use.

The publishWSDL command does not return output.

Specify app and file names:

Jacl...

$AdminApp publishWSDL JAXRPCHandlerServer /tmpa.zip

Jython...

print AdminApp.publishWSDL('JAXRPCHandlerServer', '/tmpa.zip')

Specify app, file name, and SOAP address prefixes parameter values:

Jacl...

$AdminApp publishWSDL JAXRPCHandlersServer /tmpa.zip {{JAXRPCHandlersServerApp.war {{http http://localhost:9082}}}}

Jython...

print AdminApp.publishWSDL('JAXRPCHandlersServer', '/tmpa.zip', '[[JAXRPCHandlersServerApp.war [[http http://localhost:9082]]]]')

 

searchJNDIReferences

List applications that refer to the JNDI name on a specific node.

Target object: None.

Required parameters

Node configuration ID

Configuration ID for the node of interest.

Optional parameters

options

Options to use.

Sample output...

WASX7410W: This operation may take a while depending on the number of applications installed in the system.
MyApp
MapResRefToEJB :ejb-jar-ic.jar : [eis/J2CCF1]

The following example assumes that an installed application named MyApp has a JNDI name of eis/J2CCF1:

 

taskinfo

Provide information about a particular task option for an application file. Many task names have changed between V5.x and V6.x for a similar or the exact same operation. We might need to update existing scripts if we are migrating from V5.x to V6.x.

Target object: None.

Required parameters

EAR file

Specifies the EAR file of interest.

task name

Task for which to request the information.

Optional parameters: None.

Sample output...

MapWebModToVH: Selecting virtual hosts for Web modules
Specify the virtual host where you want to install the Web modules that are contained in
the application. Web modules can be installed on the same virtual host or dispersed among several hosts.
Each element of the MapWebModToVH task consists of the following three fields: "webModule," "uri," "virtualHost."
Of these fields, the following fields might be assigned new values: "virtualHost"and the following are
required: "virtualHost"

The current contents of the task after running default bindings are:
webModule: Java Mail Sample WebApp
uri: mtcomps.war,WEB-INF/web.xml
virtualHost: default_host

Examples...

 

uninstall

Uninstall an existing application.

Target object: None.

Required parameters

application name

Name of the application to uninstall.

Optional parameters: None.

Sample output...

ADMA5017I: Uninstallation of myapp started.
ADMA5104I: Server index entry for myCellManager was updated successfully.
ADMA5102I: Deletion of config data for myapp from config
repository completed successfully.
ADMA5011I: Cleanup of temp dir for app myapp done.
ADMA5106I: Application myapp uninstalled successfully.

Examples...

 

update

Update an application in non-interactive mode. This command supports the addition, removal, and update of application subcomponents or the entire application. Provide app, content type, and update options.

Target object: None.

Required parameters

application name

Name of the application to update.

content type

Indicate to update part of the application or the entire application.

The following list includes the valid content type values for the update command:

  • app - Indicates to update the entire application.

    This option is the same as indicating the update option with the install command. With the app value as the content type, specify the operation option with update as the value. Provide the new enterprise archive file (EAR) file using the contents option. We can also specify binding information and application options. By default, binding information for installed modules is merged with the binding information for updated modules. To change this default behavior, specify the update.ignore.old or the update.ignore.new options.

  • file - Indicates to update a single file.

    We can add, remove, or update individual files at any scope within the deployed application. With the file value as the content type, perform operations on the file using the operation option. Depending on the type of operation, additional options are required. For file additions and updates, provide file content and the file URI relative to the root of the EAR file using the contents and contenturi options. For file deletion, provide the file URI relative to the root of the EAR file using contenturi option which is the only required input. Any other options that you provide are ignored.

  • modulefile - Indicates to update a module.

    We can add, remove, or update an individual application module. If specify the modulefile value as the content type, indicate the operation to perform on the module using the operation option. Depending on the type of operation, further options are required. For installing new modules or updating existing modules in an application, indicate the file content and the file URI relative to the root of the EAR file using the contents and contenturi options. We can also specify binding information and application options that pertain to the new or updated modules. For module updates, the binding information for the installed module is merged with the binding information for the input module by default. To change the default behavior, specify the update.ignore.old or the update.ignore.new options. To delete a module, indicate the file URI relative to the root of the EAR file.

  • partialapp - Indicates to update a partial application.

    Using a subset of application components provided in a zip file format we can update, add, and delete files and modules.

    The zip file is not a valid Java 2 platform, Enterprise Edition (J2EE) archive. Instead, it contains application artifacts in the same hierarchical structure as they display in an EAR file.

    See on how to construct the partial application zip file, see the Java API section. If we indicate the partialapp value as the content type, use the contents option to specify the location of the zip file.

    When a partial application is provided as an update input, binding information and application options cannot be specified and are ignored, if provided.

Optional parameters

options

There are many options available for the update command. For a list of each valid option for the update command, see Options for AdminApp install, installInteractive, edit, editInteractive, update, and updateInteractive commands.

Sample output...

Update of singleFile has started.
ADMA5009I: Application archive extracted at /DOCUME~1/lavena/LOCALS~1/Temp/app_fb5a1960f0/ext
Added files from partial ear: []
performFileOperation:
source=/DOCUME~1/lavena/LOCALS~1/Temp/app_fb5a1960f0/ext,
dest=/DOCUME~1/lavena/LOCALS~1/Temp/app_fb5a1960f0/mrg, uri= META-INF/web.xml, op= add
Copying file from /DOCUME~1/lavena/LOCALS~1/Temp/app_fb5a1960f0/ext/META-INF/web.xml to
/DOCUME~1/lavena/LOCALS~1/Temp/app_fb5a1960f0/mrg/META-INF/web.xml
Collapse list is: []
FileMergeTask completed successfully
ADMA5005I: Application singleFile configured in WebSphere repository
delFiles: []
delM: null
addM: null
Pattern for remove loose and mod:
Loose add pattern: META-INF/[^/]*|WEB-INF/[^/]*|.*wsdl
root file to be copied: META-INF/web.xml to
/WAS/AppServer/wstemp/Scriptfb5a191b4e/workspace/cells/BAMBIE/applications/
singleFile.ear/deployments/singleFile/META-INF/web.xml
ADMA5005I: Application singleFile configured in WebSphere repository xmlDoc: [#document: null]
root element: [app-delta: null]
delta file name: /WAS/AppServer/wstemp/Scriptfb5a191b4e/workspace/cells/BAMBIE/applications/
singleFile.ear/deltas/delta-1079548405564
ADMA5005I: Application singleFile configured in WebSphere repository
ADMA6011I: Deleting directory tree /DOCUME~1/lavena/LOCALS~1/Temp/app_fb5a1960f0
ADMA5011I: Cleanup of temp dir for app singleFile done.
Update of singleFile has ended.

Examples...

 

updateAccessIDs

Update the access ID information for users and groups that are assigned to various roles defined in the application. The system reads the access IDs from the user registry and saves the IDs in the application bindings. This operation improves runtime performance of the application. Use this command after installing an application or after editing security role-specific information for an installed application. This method cannot be invoked when the -conntype option for wsadmin is set to NONE. You must be connected to a server to invoke this command.

Target object: None.

Required parameters

application name

Name of the application of interest.

bALL

The bALL boolean parameter retrieves and saves all access IDs for users and groups in the application bindings. Specify false to retrieve access IDs for users or groups that do not have an access ID in the application bindings.

Sample output...

ADMA5017I: Uninstallation of myapp started.
ADMA5104I: Server index entry for myCellManager was updated successfully.
ADMA5102I: Deletion of config data for myapp from config repository completed successfully.
ADMA5011I: Cleanup of temp dir for app myapp done.
ADMA5106I: Application myapp uninstalled successfully.

Using Jacl or true:

$AdminApp updateAccessIDs myapp true

Using Jacl for false:

$AdminApp updateAccessIDs myapp false

Jython for true:

print AdminApp.updateAccessIDs('myapp', 1)

Jython for false:

print AdminApp.updateAccessIDs('myapp', 0)

 

updateInteractive

Add, remove, and update application subcomponents or an entire application. When you update an application module or an entire application using interactive mode, the steps that you use to configure binding information are similar to those that apply to the installInteractive command.

If we update a file or a partial application, the steps that you use to configure the binding information are not available. In this case, the steps are the same as the ones you use with the update command.

Target object: None.

Required parameters

application name

Name of the application to update.

content type

Indicate to update part of the application or the entire application.

The following list includes the valid content type values for the updateInteractive command:

  • app - Indicates to update the entire application.

    This option is the same as indicating the update option with the install command.

    With the app value as the content type, specify the operation option with update as the value. Provide the new enterprise archive file (EAR) file using the contents option. We can also specify binding information and application options. By default, binding information for installed modules is merged with the binding information for updated modules. To change this default behavior, specify the update.ignore.old or the update.ignore.new options.

  • file - Indicates to update a single file.

    We can add, remove, or update individual files at any scope within the deployed application. With the file value as the content type, perform operations on the file using the operation option.

    Depending on the type of operation, additional options are required.

    For file additions and updates, provide file content and the file URI relative to the root of the EAR file using the contents and contenturi options. For file deletion, provide the file URI relative to the root of the EAR file using contenturi option which is the only required input. Any other options that you provide are ignored.

  • modulefile - Indicates to update a module. We can add, remove, or update an individual application module. If specify the modulefile value as the content type, indicate the operation to perform on the module using the operation option. Depending on the type of operation, further options are required. For installing new modules or updating existing modules in an application, indicate the file content and the file URI relative to the root of the EAR file using the contents and contenturi options. We can also specify binding information and application options that pertain to the new or updated modules. For module updates, the binding information for the installed module is merged with the binding information for the input module by default. To change the default behavior, specify the update.ignore.old or the update.ignore.new options. To delete a module, indicate the file URI relative to the root of the EAR file.

  • partialapp - Indicates to update a partial application. Using a subset of application components provided in a zip file format we can update, add, and delete files and modules.

    The zip file is not a valid Java 2 platform, Enterprise Edition (J2EE) archive. Instead, it contains application artifacts in the same hierarchical structure as they display in an EAR file.

    See on how to construct the partial application zip file, see the Java API section. If we indicate the partialapp value as the content type, use the contents option to specify the location of the zip file.

    When a partial application is provided as an update input, binding information and application options cannot be specified and are ignored, if provided.

Optional parameters

options

There are many options available for the updateInteractive command. For a list of each valid option for the updateInteractive command, see Options for AdminApp install, installInteractive, edit, editInteractive, update, and updateInteractive commands.

Sample output...

Getting tasks for: myApp WASX7266I: A was.policy file exists for this application; would you like to display it? [No]

Task[4]: Binding enterprise beans to JNDI names
Each non message driven enterprise bean in the application or module must be bound to a JNDI name.
EJB Module: Increment EJB module
EJB: Increment
URI: Increment.jar,META-INF/ejb-jar.xml
JNDI Name: [Inc]:

Task[10]: Specifying the default data source for
EJB 2.x modules
Specify the default data source for
the EJB 2.x Module containing 2.x CMP beans.

WASX7349I: Possible value for resource authorization is container or per connection factory
EJB Module: Increment EJB module
URI: Increment.jar,META-INF/ejb-jar.xml
JNDI Name: [DefaultDatasource]:
Resource Authorization: [Per connection factory]:

Task[12]: Specifying data sources for individual 2.x CMP beans
Specify an optional data source for each 2.x CMP bean. Mapping a specific data source to a CMP bean overrides
the default data source for the module containing the enterprise bean.

WASX7349I: Possible value for resource authorization is container or per connection factory
EJB Module: Increment EJB module
EJB: Increment
URI: Increment.jar,META-INF/ejb-jar.xml
JNDI Name: [DefaultDatasource]:
Resource Authorization: [Per connection factory]:container
Setting "Resource Authorization" to "cmpBinding.container"

Task[14]: Selecting Application Servers
Specify the appserver where you want to install modules that are contained in the application.
Modules can be installed on the same server or dispersed among several servers.
Module: Increment EJB module
URI: Increment.jar,META-INF/ejb-jar.xml
Server: [WebSphere:cell=myCell,node=myNode,server=server1]:

Task[16]: Selecting method protections for unprotected methods for 2.x EJB
Whether you want to assign security role to the unprotected method, add the method to the exclude list, or mark
the method as unchecked.
EJB Module: Increment EJB module
URI: Increment.jar,META-INF/ejb-jar.xml
Protection Type: [methodProtection.uncheck]:
Task[18]: Selecting backend ID
Specify the selection for the BackendID
EJB Module: Increment EJB module
URI: Increment.jar,META-INF/ejb-jar.xml
BackendId list: CLOUDSCAPE_V50_1
CurrentBackendId: [CLOUDSCAPE_V50_1]:

Task[21]: Specifying application options
Specify the various options available to prepare and install the application.
Pre-compile JSP: [No]:
Deploy EJBs: [No]:
Deploy WebServices: [No]:

Task[22]: Specifying EJB deploy options
Specify the options to deploy EJB.
....EJB Deploy option is not enabled.

Task[24]: Copy WSDL files
Copy WSDL files
....This task does not require any user input

Task[25]: Specify options to deploy Web services
Specify options to deploy Web services
....Web Services deploy option is not enabled.
Update of myApp has started.

ADMA5009I: Application archive extracted at /DOCUME~1/lavena/LOCALS~1/Temp/app_fb5a48e969/ext/Increment.jar
FileMergeTask completed successfully
ADMA5005I: Application myApp configured in WebSphere repository
delFiles: []
delM: null
addM: [Increment.jar, ]
Pattern for remove loose and mod:
Loose add pattern: META-INF/[^/]*|WEB-INF/[^/]*|.*wsdl
root file to be copied:
META-INF/application.xml to /WAS/AppServer/wstemp/Scriptfb5a487089/workspace/cells/BAMBIE/
applications/testSM.ear/deployments/testSM/META-INF/application.xml
del files for full module add/update: []
ADMA6017I: Saved document /WAS/AppServer/wstemp/Scriptfb5a487089/workspace/cells/BAMBIE/
applications/testSM.ear/deployments/testSM/Increment.jar/META-INF/ejb-jar.xml
ADMA6016I: Add to workspace Increment.jar/META-INF/ejb-jar.xml
ADMA6017I: Saved document /WAS/AppServer/wstemp/Scriptfb5a487089/workspace/cells/BAMBIE/
applications/testSM.ear/deployments/testSM/Increment.jar/META-INF/MANIFEST.MF
ADMA6016I: Add to workspace Increment.jar/META-INF/MANIFEST.MF
ADMA6017I: Saved document /WAS/AppServer/wstemp/Scriptfb5a487089/workspace/cells/BAMBIE/
applications/testSM.ear/deployments/testSM/Increment.jar/META-INF/ibm-ejb-jar-bnd.xmi
ADMA6016I: Add to workspace Increment.jar/META-INF/ibm-ejb-jar-bnd.xmi
ADMA6017I: Saved document /WAS/AppServer/wstemp/Scriptfb5a487089/workspace/cells/BAMBIE/
applications/testSM.ear/deployments/testSM/Increment.jar/META-INF/Table.ddl
ADMA6016I: Add to workspace Increment.jar/META-INF/Table.ddl
ADMA6017I: Saved document /WAS/AppServer/wstemp/Scriptfb5a487089/workspace/cells/BAMBIE/
applications/testSM.ear/deployments/testSM/Increment.jar/META-INF/ibm-ejb-jar-ext.xmi
ADMA6016I: Add to workspace Increment.jar/META-INF/ibm-ejb-jar-ext.xmi
add files for full module add/update: [Increment.jar/META-INF/ejb-jar.xml, Increment.jar/META-INF/MANIFEST.MF,
Increment.jar/META-INF/ibm-ejb-jar-bnd.xmi,
Increment.jar/META-INF/Table.ddl, Increment.jar/META-INF/ibm-ejb-jar-ext.xmi]
ADMA5005I: Application myApp configured in WebSphere repository
xmlDoc: [#document: null]
root element: [app-delta: null]
****** delta file name: /WAS/AppServer/wstemp/Scriptfb5a487089/workspace/cells/BAMBIE/
applications/testSM.ear/deltas/delta-1079551520393
ADMA5005I: Application myApp configured in WebSphere repository
ADMA6011I: Deleting directory tree /DOCUME~1/lavena/LOCALS~1/Temp/app_fb5a48e969
ADMA5011I: Cleanup of temp dir for app myApp done.
Update of myApp has ended.

Examples...

 

view

View the task specified by the task name parameter for an application or module.

Use -tasknames as the option to get a list of valid task names for the application. Otherwise, specify one or more task names as the option.

Target object: None.

Required parameters

name

Name of the application or module to view.

Optional parameters

bALL

The bALL boolean parameter retrieves and saves all access IDs for users and groups in the application bindings. Specify false to retrieve access IDs for users or groups that do not have an access ID in the application bindings.

-buildVersion

Specifies whether to display the build version of the application of interest.

The command returns the following information if specify the taskoptions value for the task name parameter:

MapModulesToServers
MapWebModToVH
MapRolesToUsers

The command returns the following information if specify the mapModulesToServers task for the task name parameter:

MapModulesToServers: Selecting Application Servers

Specify the appserver where you want to install the modules that are contained in the
application. Modules can be installed on the same server or dispersed among several servers:

Module: adminconsole
URI: adminconsole.war,WEB-INF/web.xml
Server: WebSphere:cell=juniartiNetwork, node=juniartiManager,server=dmgr

The following view command example lists each available task name:

The following view command example returns information for the mapModulesToServer task:

The following view command example returns information for the AppDeploymentOptions task:

The following view command example returns the build version for the DefaultApplication application:




Subtopics

Options for AdminApp install, installInteractive, edit, editInteractive, update, and updateInteractive commands
Example: Obtaining option information for AdminApp object commands

 

Related tasks

Pattern matching with wsadmin
Use AdminApp for scripted administration