BLAManagement command group for the AdminTask object using wsadmin scripting

-assetID

Specifies the configuration ID of the asset to delete. The command accepts incomplete IDs for the assetID parameter, as long as the system can match the string to a unique asset. (String, required)

-force

Specifies whether to force the system to delete the asset, even if other assets depend on this asset. (Boolean, optional)

WebSphere:assetname=asset2.zip

-assetID

Specifies the configuration ID of the asset to edit. This parameter accepts an incomplete configuration ID, as long as the system can match the string to a unique asset ID. (String, required)

-AssetOptions

Use the AssetOptions step and the following arguments to set additional properties for the asset.

inputAsset (read-only)

Specifies the source package of the asset.

name (read-only)

Specifies the name of the asset. The default value for this argument is the file name of the source package.

defaultBindingProps (read-only)

Specifies the default binding properties for the asset. This argument only applies to enterprise assets. For assets which are not enterprise assets, specify the asterisk character (*) for pattern matching. For enterprise assets, specify the .* value to set the argument as a non-empty value.

description

Specifies a description for the asset.

destinationUrl

Specifies the URL of the asset binaries to deploy.

typeAspect

Specifies the asset type aspect.

relationship

Specifies the asset relationship. Use the plus sign character (+) to add additional assets to the existing relationship. Use the number sign character (#) to delete an existing asset from the relationship. To replace the existing relationships, specify the same syntax as in the importAsset command. If the asset specified in the relationship does not exist for add or update, the command returns an exception.

filePermission

Specifies the file permission configuration.

validate

Specifies whether to validate the asset. The default value is false. The product does not save the value specified for validate. Thus, if you select to validate the asset (true) now and later edit the asset, when you edit the asset you must enable this setting again for the product to validate the updated files.

-UpdateAppContentVersions

For an EBA asset, use this step and the following arguments to select bundle versions for the asset.

For transitioning users: In the WebSphere® Application Server Version 7 Feature Pack for OSGi Applications and Java™ Persistence API 2.0, bundle changes to the asset are applied by restarting the business-level application. In Version 8.x, these changes are applied by updating the composition unit. The new approach in Version 8.x means that many bundle changes can be applied in place, without restarting the running business-level application. To enable this new approach, the UpdateAppContentVersionsStep parameter has been replaced with the UpdateAppContentVersions parameter, and instead of restarting the business-level application you run the editCompUnit command with the CompUnitStatusStep parameter.

bundle_name

Specifies the name of the bundle.

current_version

Specifies either a bundle version number, for example 1.0.0, or NOT_DEPLOYED for shared bundles (that is, use bundles) that are declared in the application manifest but not deployed by the runtime environment. This argument describes the current configuration of the bundle, and is not used to change the configuration.

update_preference

Specifies the new bundle version preference. This is either a bundle version number, for example 1.0.0, or NOT_DEPLOYED for shared bundles, or NO_PREF if you want the system to choose a bundle version for you. If you do not want to update the version for a given bundle, set this attribute to the same value that you are using for the current_version attribute.

Include an entry (that is, the bundle_name current_version and update_preference) for each bundle that is listed in the application manifest between the application content header and the use bundle header. Include every bundle, whether or not you are updating the bundle version.

Specify the syntax as follows:

AdminTask.editAsset('[
  -assetID asset_name 
  -UpdateAppContentVersions [
    [bundle_1_name current_version update_preference]
    [bundle_2_name current_version update_preference]
    [bundle_3_name current_version update_preference]
    [bundle_4_name current_version update_preference]
    [bundle_5_name current_version update_preference]
  ]]')

• Using Jython string:

  AdminTask.editAsset('-assetID asset3.zip -AssetOptions [[.* asset3.zip * "asset for testing"
     c:/installedAssets/asset3.zip/BASE/asset3.zip "" assetname=a.jar "" false]]')

• Using Jython list:

  AdminTask.editAsset(['-assetID', 'asset3.zip', '-AssetOptions', '[[.* asset3.zip * "asset for testing"
     c:/installedAssets/asset3.zip/BASE/asset3.zip "" assetname=a.jar "" false]]'])

• Using Jython string:

  AdminTask.editAsset('-assetID defaultapp.ear -AssetOptions 
    [[.* defaultapp.ear .* "asset for testing" "" "" "" "" false]]')

• Using Jython list:

  AdminTask.editAsset(['-assetID', 'defaultapp.ear', '-AssetOptions', 
     '[[.* defaultapp.ear .* "asset for testing" "" "" "" "" false]]'])

-assetID

Specifies the configuration ID of the asset to export. This parameter accepts an incomplete configuration ID as long as the ID matches a unique asset. (String, required)

-filename

Specifies the file name to which the system exports the asset configuration. (DownloadFile, required)

-source

Specifies the name of the source file to import. (UploadFile, required)

-storageType

Specifies the way the system saves the asset in the asset repository. The default asset repository stores full binaries, metadata of binaries, or no binaries. Specify FULL to store full binaries. Specify METADATA to store the metadata portion of the binaries. Specify NONE to store no binaries in the asset repository. The default value is FULL. (String, optional)

-AssetOptions

Use the AssetOptions step and the following arguments to set additional properties for the asset.

inputAsset (read-only)

Specifies the source package of the asset.

name

Specifies the name of the asset. The extension file name of the asset must match the extension file name of the source package. The default value for this argument is the file name of the source package.

defaultBindingProps (read-only)

Specifies the default binding properties for the asset. This argument only applies to enterprise assets. For assets which are not enterprise assets, specify the asterisk character (*) for pattern matching. For enterprise assets, specify the .* value to set the argument as a non-empty value.

description

Specifies a description for the asset.

destinationUrl

Specifies the URL of the asset binaries to deploy.

typeAspect

Specifies the asset type aspect. Specify the typeAspect option in object name format, as the following syntax demonstrates: spec=xxx

relationship

Specifies the asset relationship. Use the plus sign character (+) to specify multiple asset relationships. The command returns an exception if you specify assets in the relationship that do not exist.

filePermission

Specifies the file permission configuration.

OSGi applications do not use a filePermission value.

validate

Specifies whether to validate the asset. The default value is false. The product does not save the value specified for validate. Thus, if you select to validate the asset (true) now and later edit the asset, when you edit the asset you must enable this setting again for the product to validate the updated files.

OSGi applications do not use a validate value.

WebSphere:assetname=asset2.zip

• Using Jython string:

  AdminTask.importAsset('-source c:\ears\asset1.zip -storageType NONE')

• Using Jython list:

  AdminTask.importAsset(['-source', 'c:\ears\asset1.zip', '-storageType', 'NONE'])

• Using Jython string:

  AdminTask.importAsset('-source c:\ears\asset1.zip -storageType METADATA -AssetOptions 
    [[.* asset2.zip .* "asset for testing" c:/installedAssets/asset2.zip/BASE/asset2.zip "" "" "" "" false]]')

• Using Jython list:

  AdminTask.importAsset(['-source', 'c:\ears\asset1.zip', '-storageType', 'METADATA', '-AssetOptions',
     '[[.* asset2.zip .* "asset for testing" c:/installedAssets/asset2.zip/BASE/asset2.zip "" "" "" "" false]]')

• Using Jython string:

  AdminTask.importAsset('[-source c:\ears\asset3.zip -storageType FULL -AssetOptions
     [[.* asset3.zip .* "asset for testing" "" spec=zip assetname=a.jar+assetname=b.jar "" false]]]')

• Using Jython list:

  AdminTask.importAsset(['-source', 'c:\ears\asset3.zip', '-storageType', 'FULL', '-AssetOptions', 
    '[[.* asset3.zip .* "asset for testing" "" spec=zip assetname=a.jar+assetname=b.jar "" false]]'])

• Using Jython string:

  AdminTask.importAsset('-source c:\ears\defaultapplication.ear -storageType FULL -AssetOptions
     [[.* defaultapp.ear .* "desc" "" "" "" false]]')

• Using Jython list:

  AdminTask.importAsset(['-source', 'c:\ears\defaultapplication.ear', '-storageType', 
    'FULL', '-AssetOptions', '[[.* defaultapp.ear .* "desc" "" "" "" false]]'])

-assetID

Specifies the configuration ID of the asset of interest. This parameter accepts an incomplete configuration ID as long as the ID matches a unique asset. (String, optional)

-includeDescription

Specifies whether to include the a description of each asset that the command returns. Specify true to display the asset descriptions. (String, optional)

-includeDeplUnit

Specifies whether to display the deployable units for each asset that the command returns. Specify true to display the deployable units. (String, optional)

WebSphere:assetname=asset1.zip
"asset for testing"

WebSphere:assetname=asset2.zip
"second asset for testing"
a.jar

WebSphere:aasetname=asset3.zip
"third asset for testing"
a1.jar+a2.jar

WebSphere:assetname=a.jar0
"a.jar for sharedlib"

WebSphere:assetname=b.jar
"b.jar for sharedlib"

WebSphere:assetname=defaultapp.ear
"default app"

• Using Jython:

  AdminTask.listAssets()

• Using Jython string:

  AdminTask.listAssets('-assetID asset1.zip')

• Using Jython list:

  AdminTask.listAssets(['-assetID asset1.zip'])

• Using Jython string:

  AdminTask.listAssets('-includeDescription true -includeDeplUnit true')

• Using Jython list:

  AdminTask.listAssets(['-includeDescription', 'true', '-includeDeplUnit', 'true')

-assetID

Specifies the configuration ID of the asset to update. This parameter accepts an incomplete configuration ID as long as the ID matches a unique asset. (String, required)

-operation

Specifies the operation to invoke on the asset of interest. (String, required)

The following table displays each operation that you can invoke on an asset:

Table 1. updateAsset supported operations . Specify one of the operations.

Operation	Description
replace	The replace operation replaces the contents of the asset of interest.
merge	The merge operation updates multiple files for the asset, but does not update all files.
add	The add operation adds a new file or module file.
addupdate	The addupdate operation adds or updates one file or module file. If the file does not exist, the system adds the contents. If the file exists, the system updates the file.
update	The update operation updates one file or module file.
delete	The delete operation deletes a file or module file.

-contents

Specifies the file that contains the content to add or update. This parameter is not required for the delete operation. (UploadFile, optional)

-contenturi

Specifies the Uniform Resource Identifier (URI) of the file to add, update, or remove from the asset. This parameter is not required for the merge or replace operations. (String, optional)

-AssetOptions

Use the AssetOptions step and the following arguments to set additional properties for the asset.

name (read-only)

Specifies the name of the asset. The default value for this argument is the file name of the source package.

defaultBindingProps (read-only)

Specifies the default binding properties for the asset. This argument only applies to enterprise assets. For assets which are not enterprise assets, specify the asterisk character (*) for pattern matching. For enterprise assets, specify the .* value to set the argument as a non-empty value.

description

Specifies a description for the asset.

destinationUrl

Specifies the URL of the asset binaries to deploy.

typeAspect

Specifies the asset type aspect.

relationship

Specifies the asset relationship. Use the plus sign character (+) to add additional assets to the existing relationship. Use the number sign character (#) to delete an existing asset from the relationship. To replace the existing relationships, specify the same syntax as in the importAsset command. If the asset specified in the relationship does not exist for add or update, the command returns an exception.

filePermission

Specifies the file permission configuration.

validate

Specifies whether to validate the asset. The default value is false. The product does not save the value specified for validate. Thus, if you select to validate the asset (true) now and later edit the asset, when you edit the asset you must enable this setting again for the product to validate the updated files.

updateAssociatedCUs

Specifies whether to update the composition units that are associated with an enterprise (Java EE) asset. This argument applies to enterprise assets only. The default value is none. Specify all to update all of the composition units that are associated with the enterprise asset.

For the replace operation, specify values for the AssetOptions name, defaultBindingProps, description, destinationUrl, typeAspect, relationship, filePermission, validate, and updateAssociatedCUs arguments. For operations other than replace, specify values for the AssetOptions name and updateAssociatedCUs arguments.

• Using Jython string:

  AdminTask.updateAsset('-assetID asset1.zip -operation replace -contents c:/temp/a.zip')

• Using Jython list:

  AdminTask.updateAsset(['-assetID', 'asset1.zip', '-operation', 'replace', '-contents', 'c:/temp/a.zip'])

• Using Jython string:

  AdminTask.updateAsset('-assetID asset1.zip -operation merge -contents c:/temp/p.zip')

• Using Jython list:

  AdminTask.updateAsset(['-assetID', 'asset1.zip', '-operation', 'merge', '-contents', 'c:/temp/p.zip'])

• Using Jython string:

  AdminTask.updateAsset('-assetID defaultapp.ear -operation add -contents 
    c:/temp/filename.jar -contenturi filename.jar')

• Using Jython list:

  AdminTask.updateAsset(['-assetID', 'defaultapp.ear', '-operation', 'add', '-contents', 
    'c:/temp/filename.jar', '-contenturi', 'filename.jar'])

• Using Jython string:

  AdminTask.updateAsset('-assetID defaultapp.ear -operation replace -contents 
    c:/temp/newapp.ear -AssetOptions [[defaultapp.ear .* newdesc "" "" "" "" false all]]')

• Using Jython list:

  AdminTask.updateAsset(['-assetID', 'defaultapp.ear', '-operation', 'replace', '-contents',
    'c:/temp/newapp.ear', '-AssetOptions [[defaultapp.ear .* newdesc "" "" "" "" false all]]'])

• Using Jython string:

  AdminTask.updateAsset('-assetID defaultapp.ear -operation merge -contents 
    c:/temp/newapp.ear -AssetOptions [[defaultapp.ear all]]')

• Using Jython list:

  AdminTask.updateAsset(['-assetID', 'defaultapp.ear', '-operation', 'merge', '-contents',
    'c:/temp/newapp.ear', '-AssetOptions [[defaultapp.ear all]]'])

-assetID

Specifies the configuration ID of the asset of interest. This parameter accepts an incomplete configuration ID as long as the ID matches a unique asset. (String, required)

Specify Asset options (AssetOptions)

Specify options for Asset.

*Asset Name (name): [defaultapp.ear]
Default Binding Properties (defaultBindingProps): 
 [defaultbinding.ejbjndi.prefix#defaultbinding.datasource.jndi#defaultbinding.datasource.username
#defaultbinding.datasource.password#defaultbinding.cf.jndi
#defaultbinding.cf.resauth#defaultbinding.virtual.host#defaultbinding.force]
Asset Description (description): []
Asset Binaries Destination Url (destination): [${USER_INSTALL_ROOT}/installedAssets/defaultapp.ear/BASE/defaultapp.ear]
Asset Type Aspects (typeAspect): [WebSphere:spec=j2ee_ear]
Asset Relationships (relationship): []File Permission (filePermission): [.*\\.dll=755#.*\\.so=755#.*\\.a=755#.*\\.sl=755]
Validate asset (validate): [false]

-blaID

Specifies the configuration ID of the business-level application of interest. (String, required)

-cuSourceID

Specifies the source configuration ID for the composition unit to add. You can specify an asset ID or a business-level application ID. (String, required)

-deplUnits

Specifies the deployable units to deploy for the asset. You can specify a subset of deployable units, all deployable units, or use the default as a shared library. If you do not specify this parameter, the system deploys each deployable unit. (String, optional)

For Java EE assets, the system ignores this -deplUnits parameter and, regardless of the value specified, can add Java EE assets as part of this command.

-cuConfigStrategyFile

Specifies the fully qualified file path for custom default binding properties. This parameter only applies to enterprise assets. (String, optional)

-defaultBindingOptions

Specifies optional Java Naming and Directory Interface (JNDI) binding properties for an enterprise asset. The binding properties available depend upon the type of enterprise asset. Use the format property=value to specify a default binding property. To specify more than one property, separate each property=value statement by the delimiter #.

You can specify binding properties now, when creating the asset, or later, when adding the asset as a composition unit to a business-level application. If you specify binding properties later, when adding the asset to a business-level application, then you can use a strategy file to specify the binding properties. (String, optional)

Use the following options with the defaultBindingOptions parameter:

Table 2. addCompUnit -defaultBindingOptions supported binding properties . Specify a binding property that is supported for the asset type.

enterprise asset type	Supported binding properties
Enterprise bean (EJB)	defaultbinding.ejbjndi.prefix defaultbinding.force
Data source	defaultbinding.datasource.jndi defaultbinding.datasource.username defaultbinding.datasource.password defaultbinding.force
Connection factory	defaultbinding.cf.jndi defaultbinding.cf.resauth defaultbinding.force
Virtual host	defaultbinding.virtual.host defaultbinding.force

-JeeImplementation

Associates Service Component Architecture (SCA) components in an SCA composite with enterprise archive (EAR) assets. An SCA composite definition can define Java EE applications as component implementations. You can define an EAR asset on an archive attribute of an implementation.jee tag for an SCA component and use the application deployed from the asset as its implementation. Use the -JeeImplementation parameter to associate SCA components in the business-level application to the EAR files named in the composite definition. This parameter is not required if there is only one deployed EAR composition unit in the business-level application and that deployed EAR composition unit matches the EAR file named in the composite definition.

componentName

Specifies the name of an SCA component in the SCA composite that you are deploying. The component uses an EAR file.

archiveName

Specifies the name of the EAR asset that the SCA component uses. The EAR file must be an asset of the business-level application. The EAR asset name must match the archive attribute on the implementation.jee tag in the SCA composite definition.

applicationName

Specifies the composition unit name of the EAR asset. To associate an SCA component with an EAR file, the EAR file must be a composition unit of your SCA business-level application.

-CUOptions

Specifies additional properties for the composition unit. Specify the following options with the CUOptions step:

parentBLA (read-only)

Specifies the parent business-level application for the new composition unit.

backingID (read-only)

Specifies the composition unit source ID.

name

Specifies the name of the composition unit.

description

Specifies a description of the composition unit.

startingWeight

Specifies the starting weight of the composition unit. Supported values are from 1 to 2147483647, the maximum Integer value.

startedOnDistributed

Specifies whether to start the composition unit after distributing changes to the target nodes. The default value is false.

restartBehaviorOnUpdate

Specifies the nodes to restart after editing the composition unit. Specify ALL to restart each target node. Specify DEFAULT to restart the nodes controlled by the sync plug-ins. Specify NONE to prevent the system from restarting nodes.

For example, specify the syntax of this step as -CUOptions [[.* .* cu4 "cu4 desc" 0 false DEFAULT]]

-MapTargets

Specifies additional properties for the composition unit target mapping. Specify the following options with the MapTargets step:

deplUnit (read-only)

Specifies the deployable unit Uniform Resource Identifier (URI).

For an enterprise bundle archive (EBA) asset, this URI is ebaDeploymentUnit.

server

Specifies the target or targets to deploy the composition units. The default value is the server1 server. Use the plus sign character ( + ) to specify multiple targets. Use the plus sign character ( + ) as a prefix to add an additional target. Specify the complete object name format for each server that is not aWebSphere Application Server server.

For example, specify the syntax of this step as -MapTargets [[a1.jar cluster1+cluster2] [a2.jar +server2]]

-ActivationPlanOptions

Specifies additional properties for the composition unit activation plan. Specify the following options with the ActivationPlanOptions step:

deplUnit (read-only)

Specifies the deployable unit Uniform Resource Identifier (URI).

activationPlan

Specifies a list of runtime components as the activation plan. Specify each activation plan in the format specName=xxx,specVersion=yyy, where specName represents the name of the specification and is required. Use the plus sign character ( + ) to specify multiple activation plans.

For example, specify the syntax of this step as -ActivationPlanOptions [[a1.jar specname=actplan0+specname=actplan1] [a2.jar specname=actplan1+specname=actplan2]]

For an EBA asset, use the following default values: -ActivationPlanOptions [[default ""]]

-CreateAuxCUOptions

Specifies additional properties for an auxiliary composition unit. Use this step if the composition unit source is an asset that corresponds to an asset that does not have a matching composition unit in the business-level application. Specify the following options with the CreateAuxCUOptions step:

deplUnit (read-only)

Specifies the deployable unit Uniform Resource Identifier (URI).

inputAsset (read-only)

Specifies composition unit source ID.

cuID

Specifies the composition unit ID that the system creates for the asset. If you do not want to create a new composition unit, do not specify this argument.

matchTarget

Specifies whether to match the targets of the dependency auxiliary composition unit with the targets of the new composition unit. The default value is true.

The product does not save the value specified for matchTarget. Thus if you select to not match the target (false) now and later edit the composition unit, when you edit the composition unit you must disable this setting again for the product to not match the targets.

For example, specify the syntax of this step as -CreateAuxCUOptions [[a1.jar a.jar auxCU true] [a2.jar a.jar defaultCU false]]

-RelationshipOptions

Specifies additional properties for relationships between assets, composition units, and business-level applications. Use this step if the source ID of the composition unit is an asset that has a matching composition unit in the business-level application. Specify the following options with the RelationshipOptions step:

deplUnit (read-only)

Specifies the deployable unit Uniform Resource Identifier (URI).

relationship

Defines the composition unit relationships. Specify the composition unit object name in the format: cuName=xxx. Use the plus sign character (+) to specify multiple composition unit object names in the relationship. If the composition unit specified in the relationship does not exist under the same business-level application, the system returns an error.

matchTarget

Specifies whether to match the targets of the composition unit relationship with the targets of the new composition unit. The default value is true.

The product does not save the value specified for matchTarget. Thus if you select to not match the target (false) now and later edit the composition unit, when you edit the composition unit you must disable this setting again for the product to not match the targets.

For example, specify the syntax of this step as -RelationshipOptions [[a1.jar a.jar auxCU true] [a2.jar a.jar defaultCU false]]

-ContextRootStep

For an EBA asset, context roots determine where the web pages of a particular web application bundle (WAB) are found at run time.

The context root that you specify here is combined with the defined server mapping to compose the full URL that you enter to access the pages of the WAB. For example, if the application server default host is www.example.com:8080 and the context root of the WAB is /sample, the web pages are available at www.example.com:8080/sample.

You should list the context roots for all the WAB modules that are contained in the OSGi application.

Specify the syntax of this step as follows:

  -ContextRootStep [
    [bundle_symbolic_name_1 bundle_version_1 context_root_1]
    [bundle_symbolic_name_2 bundle_version_2 context_root_2]]

For example, for an EBA file containing two WABs (com.ibm.ws.eba.helloWorldService.web at version 1.0.0, which is to be mapped to /hello/web, and com.ibm.ws.eba.helloWorldService.withContextRoot at version 0.9.0, which is to be mapped to /hello/service), this aspect of the command is as follows:

  -ContextRootStep [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 "/hello/web"] 
    [com.ibm.ws.eba.helloWorldService.withContextRoot 0.9.0 "/hello/service"]]

-VirtualHostMappingStep

For an EBA asset, you use a virtual host to associate a unique port with a module or application. The aliases of a virtual host identify the port numbers defined for that virtual host. A port number specified in a virtual host alias is used in the URL that is used to access artifacts such as servlets and JavaServer Page (JSP) files in a web module. For example, the alias myhost:8080 is the host_name:port_number portion of the URL http://myhost:8080/sample.

Each WAB that is contained in a deployed asset must be mapped to a virtual host. WABs can be installed on the same virtual host, or dispersed among several virtual hosts.

If you specify an existing virtual host in the ibm-web-bnd.xml or .xmi file for a given WAB, the specified virtual host is set by default. Otherwise, the default virtual host setting is default_host, which provides several port numbers through its aliases:

80

An internal, insecure port used when no port number is specified

9080

An internal port

9443

An external, secure port

Unless you want to isolate your WAB from other WABs or resources on the same node (physical machine), default_host is a suitable virtual host. In addition to default_host, WebSphere Application Server provides admin_host, which is the virtual host for the administrative console system application. admin_host is on port 9060. Its secure port is 9043. Do not select admin_host unless the WAB relates to system administration.

Specify the syntax of this step as follows:

-VirtualHostMappingStep [
    [bundle_symbolic_name_1 bundle_version_1 
    web_module_name_1 virtual_host_1]
    [bundle_symbolic_name_2 bundle_version_2 
     web_module_name_2 virtual_host_2]]

For example, for an EBA file containing two WABs (com.ibm.ws.eba.helloWorldService.web at version 1.0.0, which is to be mapped to default_host, and com.ibm.ws.eba.helloWorldService.withContextRoot at version 0.9.0, which is to be mapped to test_host), this aspect of the command is as follows:

-VirtualHostMappingStep [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 "HelloWorld service" default_host]
    [com.ibm.ws.eba.helloWorldService.withContextRoot 0.9.0 "HelloWorld second service" test_host]]

-MapRolesToUsersStep

For an EBA asset, use this step to map security roles to users or groups.

Specify the syntax of this step as follows:

-MapRolesToUsersStep [
    [role_name everyone? 
    all_authenticated_in_realm? 
    usernames groups all_authenticated_in_trusted_realms?]]

Key:

• role_name is a role name defined in the application.
• everyone? is set to Yes or No, to specify whether or not everyone is in the role.
• all_authenticated_in_realm? is set to Yes or No, to specify whether or not all authenticated users can access the application realm.
• usernames is a list of WebSphere Application Server user names, separated by the vertical line (|) character.
• groups is a list of WebSphere Application Server groups, separated by the | character.
• all_authenticated_in_trusted_realms? optionally set to Yes or No, to specify whether all users authenticated in a trusted realm can access the resource.

Note: For usernames, and groups, the empty string "" means to use the default or existing value. The default value is usually that no users or groups are bound to the role. However, when an application contains an ibm-application-bnd.xmi file, the default value for usernames is obtained from this file. If you are deploying an application that contains an ibm-application-bnd.xmi file, and you want to remove the bound users, specify just the | character (which is the separator for multiple user names). This explicitly specifies no users, and therefore guarantees that no users are bound to the role.

For example:

-MapRolesToUsersStep [
    [ROLE1 No Yes "" ""] 
    [ROLE2 No No WABTestUser1 ""] 
    [ROLE3 No No "" WABTestGroup1] 
    [ROLE4 Yes No "" ""]]

-BlueprintResourceRefBindingStep

For an EBA asset, Blueprint components can access WebSphere Application Server resource references. Each reference is declared in a Blueprint XML file, and can be secured using a Java Platform, Enterprise Edition (Java EE) Connector Architecture (JCA) authentication alias. Each bundle in an OSGi application can contain any number of resource reference declarations in its various Blueprint XML files.

When you secure resource references, those resource references can be bound only to JCA authentication aliases that exist on every server or cluster that the OSGi application is deployed to. An OSGi application can be deployed to multiple servers and clusters that are in the same security domain. Therefore, each JCA authentication alias must exist in either the security domain of the target servers and clusters, or the global security domain.

Specify the syntax of this step as follows:

-BlueprintResourceRefBindingStep [
    [
    bundle_symbolic_name 
    bundle_version 
    blueprint_resource_reference_id 
    interface_name 
    jndi_name 
    authentication_type 
    sharing_setting 
    authentication_alias_name
    ]]

Note: The value for jndi_name must match the jndi name that you declare in the filter attribute of the resource reference element in the Blueprint XML file.

For example, for an EBA file that contains a bundle com.ibm.ws.eba.helloWorldService.properties.bundle.jar at Version 1.0.0, which is to be bound to authentication alias alias1, the command is as follows:

-BlueprintResourceRefBindingStep[
    [com.ibm.ws.eba.helloWorldService.properties.bundle 1.0.0 resourceRef 
    javax.sql.DataSource jdbc/Account Container Shareable alias1]]

-WebModuleMsgDestRefs

For an EBA asset, binding a resource reference maps a resource dependency of the web application to an actual resource available in the server runtime environment. At a minimum, this can be achieved by using a mapping that specifies the JNDI name under which the resource is known in the runtime environment. By default, the JNDI name is the resource ID that you specified in the web.xml file during development of the web application bundle (WAB). Use this option to bind resources of type message-destination-ref (message destination reference) or resource-env-ref (resource environment reference), as defined in the Java specification JSR-250: Common Annotations for the Java Platform.

Specify the syntax of this step as follows:

-WebModuleMsgDestRefs [
    [
    bundle_symbolic_name
    bundle_version
    resource_reference_id
    resource_type
    target_jndi_name
	   ]]

For example:

-WebModuleMsgDestRefs [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 
    jms/myQ javax.jms.Queue jms/workQ] 
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 
    jms/myT javax.jms.Topic jms/notificationTopic]]

-WebModuleResourceRefs

For an EBA asset, binding a resource reference maps a resource dependency of the web application to an actual resource available in the server runtime environment. At a minimum, this can be achieved by using a mapping that specifies the JNDI name under which the resource is known in the runtime environment. By default, the JNDI name is the resource ID that you specified in the web.xml file during development of the web application bundle (WAB). Use this option to bind resources of type resource-ref (resource reference), as defined in the Java specification JSR-250: Common Annotations for the Java Platform.

Specify the syntax of this step as follows:

-WebModuleResourceRefs [
    [
    bundle_symbolic_name
    bundle_version
    resource_reference_id
    resource_type
    target_jndi_name
    login_configuration
    login_properties
    extended_properties
	   ]]

For example:

-WebModuleResourceRefs [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 jdbc/jtaDs javax.sql.DataSource 
    jdbc/helloDs "" "" ""] 
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 jdbc/nonJtaDs javax.sql.DataSource 
    jdbc/helloDsNonJta "" "" "extprop1=extval1"]]

Note: If you use multiple extended properties, the Jython syntax is extprop1=extval1,extprop2=extval2.

WebSphere:cuname=cu4
WebSphere:cuname=cua
WebSphere:cuname=cud

• Using Jython string:

  AdminTask.addCompUnit('-blaID myBLA -cuSourceID assetname=asset1.zip -CUOptions 
    [[.* .* cu1 "cu1 desc1" 0 false DEFAULT]] -MapTargets [[.* server1]] -ActivationPlanOptions 
    [.* specname=actplan0+specname=actplan1]')

• Using Jython list:

  AdminTask.addCompUnit(['-blaID', 'myBLA', '-cuSourceID', 'assetname=asset1.zip', '-CUOptions', 
    '[[.* .* cu1 "cu1 desc1" 0 false DEFAULT]]', '-MapTargets', '[[.* server1]]', '-ActivationPlanOptions',
     '[.* specname=actplan0+specname=actplan1]'])

• Using Jython string:

  AdminTask.addCompUnit('-blaID myBLA -cuSourceID yourBLA -CUOptions [[.* .* cu3 "cu3 desc3" 0 false DEFAULT]]')

• Using Jython list:

  AdminTask.addCompUnit(['-blaID', 'myBLA', '-cuSourceID', 'yourBLA', '-CUOptions', 
    '[[.* .* cu3 "cu3 desc3" 0 false DEFAULT]]'])

• Using Jython string:

  AdminTask.addCompUnit('-blaID myBLA -cuSourceID yourBLA -JeeImplementation
   [[mySCAcomponent myEARfile myEARassetName]]')

• Using Jython list:

  AdminTask.addCompUnit(['-blaID', 'myBLA', '-cuSourceID', 'yourBLA', 'JeeImplementation', 
    '[[mySCAcomponent myEARfile myEARassetName]]'])

AdminTask.addCompUnit('[
  -blaID WebSphere:blaname=helloWorldService 
  -cuSourceID WebSphere:assetname=com.ibm.ws.eba.helloWorldService.eba
  -CUOptions [
    [WebSphere:blaname=helloWorldService.eba 
    WebSphere:assetname=com.ibm.ws.eba.helloWorldService.eba 
    com.ibm.ws.eba.helloWorldService_0001.eba "" 1 false DEFAULT]] 
  -MapTargets [[ebaDeploymentUnit WebSphere:node=node01,server=server1]] 
  -ActivationPlanOptions [[default ""]]  
  -ContextRootStep [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 "/hello/web"] 
    [com.ibm.ws.eba.helloWorldService.withContextRoot 0.9.0 "/hello/service"]]
  -VirtualHostMappingStep [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 
    "HelloWorld service" default_host]
    [com.ibm.ws.eba.helloWorldService.withContextRoot 0.9.0 
    "HelloWorld second service" test_host]]
  -MapRolesToUsersStep [
    [ROLE1 No Yes "" ""] 
    [ROLE2 No No WABTestUser1 ""] 
    [ROLE3 No No "" WABTestGroup1] 
    [ROLE4 Yes No "" ""]]
  -BlueprintResourceRefBindingStep[
    [com.ibm.ws.eba.helloWorldService.properties.bundle 1.0.0 resourceRef 
    javax.sql.DataSource jdbc/Account Container Shareable alias1]]
  -WebModuleMsgDestRefs [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 
    jms/myQ javax.jms.Queue jms/workQ] 
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 
    jms/myT javax.jms.Topic jms/notificationTopic]]
  -WebModuleResourceRefs [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 jdbc/jtaDs javax.sql.DataSource 
    jdbc/helloDs "" "" ""] 
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 jdbc/nonJtaDs javax.sql.DataSource 
    jdbc/helloDsNonJta "" "" "extprop1=extval1"]]
]')

• Using Jython string:

  AdminTask.addCompUnit('-blaID theirBLA -cuSourceID asset2.zip -CUOptions 
    [[.* .* cu2 "cu2 desc" 0 false DEFAULT]] -MapTargets [[.* server1+server2]]')

• Using Jython list:

  AdminTask.addCompUnit(['-blaID', 'theirBLA', '-cuSourceID', 'asset2.zip', '-CUOptions', 
    '[[.* .* cu2 "cu2 desc" 0 false DEFAULT]]', '-MapTargets', '[[.* server1+server2]]'])

• Using Jython string:

  AdminTask.addCompUnit('-blaID yourBLA -cuSourceID asset2.zip -deplUnits a.jar -CUOptions 
    [[.* .* cu3 "cu3 desc" 0 false DEFAULT]] -MapTargets [[a.jar server1]] -ActivationPlanOptions 
    [[a.jar specname=actplan1]]')

• Using Jython list:

  AdminTask.addCompUnit(['-blaID', 'yourBLA', '-cuSourceID', 'asset2.zip', '-deplUnits', 'a.jar', '-CUOptions', 
    '[[.* .* cu3 "cu3 desc" 0 false DEFAULT]]', '-MapTargets', '[[a.jar server1]]', '-ActivationPlanOptions',
     '[[a.jar specname=actplan1]]'])

• Using Jython string:

  AdminTask.addCompUnit('-blaID ourBLA -cuSourceID b.jar -deplUnits default -CUOptions 
    [[.* .* cub "cub desc" 0 false DEFAULT]] -MapTargets [[default server1]]')

• Using Jython list:

  AdminTask.addCompUnit(['-blaID', 'ourBLA', '-cuSourceID', 'b.jar', '-deplUnits', 'default', '-CUOptions', 
    '[[.* .* cub "cub desc" 0 false DEFAULT]]', '-MapTargets', '[[default server1]]'])

• Using Jython string:

  AdminTask.addCompUnit('-blaID ourBLA -cuSourceID asset3.zip -deplUnits a1.jar -CUOptions 
    [[.* .* cu4 "cu4 desc" 0 false DEFAULT]] -MapTargets [[a1.jar cluster1+cluster2]] -CreateAuxCUOptions 
    [[a1.jar a.jar cua true]] -RelationshipOptions [[a1.jar cuname=cub true]]')

• Using Jython list:

  AdminTask.addCompUnit(['-blaID', 'ourBLA', '-cuSourceID', 'asset3.zip', '-deplUnits', 'a1.jar', '-CUOptions',
   '[[.* .* cu4 "cu4 desc" 0 false DEFAULT]]', '-MapTargets', '[[a1.jar cluster1+cluster2]]', '-CreateAuxCUOptions', 
    '[[a1.jar a.jar cua true]]', '-RelationshipOptions', '[[a1.jar cuname=cub true]]'])

• Using Jython string:

  AdminTask.addCompUnit('[-blaID yourBLA -cuSourceID defaultapp.ear -defaultBindingOptions
    defaultbinding.ejbjndi.prefix=ejb# defaultbinding.virtual.host=default_host#
    defaultbinding.force=yes -AppDeploymentOptions [-appname defaultapp -installed.ear.destination
    application_root/myCell/defaultapp.ear] -MapModulesToServers 
    [[defaultapp.war .* WebSphere:cell=cellName,node=nodeName,server=server1]
    [Increment.jar .* Websphere:cell=cellName,node=nodeName,server=server2]] -CtxRootForWebMod
    [[defaultapp.war .* myctx/]]]')

• Using Jython list:

  AdminTask.addCompUnit(['-blaID', 'yourBLA', '-cuSourceID', 'defaultapp.ear', '-defaultBindingOptions',
     'defaultbinding.ejbjndi.prefix=ejb# defaultbinding.virtual.host=default_host# defaultbinding.force=yes', 
     '-AppDeploymentOptions', '[-appname defaultapp -installed.ear.destination application_root/myCell/defaultapp.ear]',
     '-MapModulesToServers', '[[defaultapp.war .* WebSphere:cell=cellName,node=nodeName,server=server1]
     [Increment.jar .* Websphere:cell=cellName,node=nodeName,server=server2]]', '-CtxRootForWebMod', 
     '[[defaultapp.war .* myctx/]]'])

-blaID

Specifies the configuration ID of the business-level application of interest. (String, required)

-cuID

Specifies the configuration ID of the composition unit to delete. (String, required)

-force

Specifies whether to force the system to delete the composition unit, even if other composition units depend on this composition unit. (Boolean, optional)

WebSphere:cuname=cu1

-blaID

Specifies the configuration ID of the business-level application of interest. (String, required)

-cuID

Specifies the configuration ID of the composition unit to edit. (String, required)

-CUOptions

Specifies additional properties for the composition unit. Specify the following options with the CUOptions step:

parentBLA (read-only)

Specifies the parent business-level application for the composition unit.

backingID (read-only)

Specifies the composition unit source ID.

name (read-only)

Specifies the name of the composition unit.

description

Specifies a description of the composition unit.

startingWeight

Specifies the starting weight of the composition unit. Supported values are from 1 to 2147483647, the maximum Integer value.

startedOnDistributed

Specifies whether to start the composition unit after distributing changes to the target nodes. The default value is false.

restartBehaviorOnUpdate

Specifies the nodes to restart after editing the composition unit. Specify ALL to restart each target node. Specify DEFAULT to restart the nodes controlled by the sync plug-ins. Specify NONE to prevent the system from restarting nodes.

For example, specify the syntax for this step as -CUOptions [[.* .* cu4 "cu4 description" 0 false DEFAULT]]

-MapTargets

Specifies additional properties for the composition unit target mapping. Specify the following options with the MapTargets step:

deplUnit (read-only)

Specifies the deployable unit Uniform Resource Identifier (URI).

For an enterprise bundle archive (EBA) asset, this URI is ebaDeploymentUnit.

server

Specifies the target or targets to deploy the composition units. The default value is the server1 server. Use the plus sign character ( + ) to specify multiple targets. Use the plus sign character ( + ) as a prefix to add an additional target. Specify the complete object name format for each server that is not a WebSphere Application Server server.

For example, specify the syntax of this step as -MapTargets [[a1.jar cluster1+cluster2] [a2.jar server1+server2]]

-ActivationPlanOptions

Specifies additional properties for the composition unit activation plan. Specify the following options with the ActivationPlanOptions step:

deplUnit (read-only)

Specifies the deployable unit Uniform Resource Identifier (URI).

activationPlan

Specifies a list of runtime components as the activation plan. Specify each activation plan in the format specName=xxx,specVersion=yyy, where specName represents the name of the specification and is required. Use the plus sign character ( + ) to specify multiple activation plans.

For example, specify the syntax of this step as -ActivationPlanOptions [[a1.jar specname=actplan0+actplan1] [a2.jar specname=actplan1+specname=actplan2]]

For an EBA asset, do not modify the activation plan. Keep the following default values that were set when the composition unit was added: -ActivationPlanOptions [[default ""]]

-RelationshipOptions

Specifies additional properties for relationships between assets, composition units, and business-level applications. Use this step if the source ID of the composition unit is an asset that has a matching composition unit in the business-level application. Specify the following options with the RelationshipOptions step:

deplUnit (read-only)

Specifies the deployable unit Uniform Resource Identifier (URI).

relationship

Defines the composition unit relationships. Specify the composition unit object name in the format: cuName=xxx. Use the plus sign character (+) to specify multiple composition unit object names in the relationship. If the composition unit specified in the relationship does not exist under the same business-level application, the system returns an error.

matchTarget

Specifies whether to match the targets of the composition unit relationship with the targets of the new composition unit. The default value is true.

The product does not save the value specified for matchTarget. Thus if you select to not match the target (false) now and later edit the composition unit, when you edit the composition unit you must disable this setting again for the product to not match the targets.

For example, specify the syntax of this step as -RelationshipOptions [[a1.jar a.jar auxCU true] [a2.jar a.jar defaultCU false]]

-ReferenceJMSBindingResources

Specifies JNDI settings for the resource reference element of a Java Message Service (JMS) binding for a Service Component Architecture (SCA) composite of the business-level application. To run the editCompUnit command, specify the required parameters and this optional step. You can edit the destination JNDI name or connection factory JNDI name. The command updates the resource that is defined in the JMS binding. The JMS resource must exist. The product does not dynamically create JMS resources when you edit a composition unit.

-ServiceJMSBindingResources

Specifies editable JNDI settings for the resource service element of a Java Message Service (JMS) binding for a Service Component Architecture (SCA) composite of the business-level application. To run the editCompUnit command, specify the required parameters and this optional step. You can edit the destination JNDI name or activation specification JNDI name. The command updates the resource that is defined in the JMS binding. The JMS resource must exist. The product does not dynamically create JMS resources when you edit a composition unit.

-ReferenceJMSBindingResponseResources

Specifies editable JNDI settings for the response resource reference element of a Java Message Service (JMS) binding for a Service Component Architecture (SCA) composite of the business-level application. To run the editCompUnit command, specify the required parameters and this optional step. You can edit the response destination JNDI name or response connection factory JNDI name. The command updates the response resource that is defined in the JMS binding. The JMS resource must exist. The product does not dynamically create JMS resources when you edit a composition unit.

-ServiceJMSBindingResponseResources

Specifies JNDI settings for the response resource service element of a Java Message Service (JMS) binding for a Service Component Architecture (SCA) composite of the business-level application. To run the editCompUnit command, specify the required parameters and this optional step. You can edit the response destination JNDI name or response connection factory JNDI name. The command updates the response resource that is defined in the JMS binding. The JMS resource must exist. The product does not dynamically create JMS resources when you edit a composition unit.

-ContextRootStep

For an EBA asset, context roots determine where the web pages of a particular web application bundle (WAB) are found at run time.

The context root that you specify here is combined with the defined server mapping to compose the full URL that you enter to access the pages of the WAB. For example, if the application server default host is www.example.com:8080 and the context root of the WAB is /sample, the web pages are available at www.example.com:8080/sample.

You should list the context roots for all the WAB modules that are contained in the OSGi application.

Specify the syntax of this step as follows:

  -ContextRootStep [
    [bundle_symbolic_name_1 bundle_version_1 context_root_1]
    [bundle_symbolic_name_2 bundle_version_2 context_root_2]]

For example, for an EBA file containing two WABs (com.ibm.ws.eba.helloWorldService.web at version 1.0.0, which is to be mapped to /hello/web, and com.ibm.ws.eba.helloWorldService.withContextRoot at version 0.9.0, which is to be mapped to /hello/service), this aspect of the command is as follows:

  -ContextRootStep [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 "/hello/web"] 
    [com.ibm.ws.eba.helloWorldService.withContextRoot 0.9.0 "/hello/service"]]

-VirtualHostMappingStep

For an EBA asset, you use a virtual host to associate a unique port with a module or application. The aliases of a virtual host identify the port numbers defined for that virtual host. A port number specified in a virtual host alias is used in the URL that is used to access artifacts such as servlets and JavaServer Page (JSP) files in a web module. For example, the alias myhost:8080 is the host_name:port_number portion of the URL http://myhost:8080/sample.

Each WAB that is contained in a deployed asset must be mapped to a virtual host. WABs can be installed on the same virtual host, or dispersed among several virtual hosts.

If you specify an existing virtual host in the ibm-web-bnd.xml or .xmi file for a given WAB, the specified virtual host is set by default. Otherwise, the default virtual host setting is default_host, which provides several port numbers through its aliases:

80

An internal, insecure port used when no port number is specified

9080

An internal port

9443

An external, secure port

Unless you want to isolate your WAB from other WABs or resources on the same node (physical machine), default_host is a suitable virtual host. In addition to default_host, WebSphere Application Server provides admin_host, which is the virtual host for the administrative console system application. admin_host is on port 9060. Its secure port is 9043. Do not select admin_host unless the WAB relates to system administration.

Specify the syntax of this step as follows:

-VirtualHostMappingStep [
    [bundle_symbolic_name_1 bundle_version_1 
    web_module_name_1 virtual_host_1]
    [bundle_symbolic_name_2 bundle_version_2 
     web_module_name_2 virtual_host_2]]

For example, for an EBA file containing two WABs (com.ibm.ws.eba.helloWorldService.web at version 1.0.0, which is to be mapped to default_host, and com.ibm.ws.eba.helloWorldService.withContextRoot at version 0.9.0, which is to be mapped to test_host), this aspect of the command is as follows:

-VirtualHostMappingStep [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 "HelloWorld service" default_host]
    [com.ibm.ws.eba.helloWorldService.withContextRoot 0.9.0 "HelloWorld second service" test_host]]

-MapRolesToUsersStep

For an EBA asset, use this step to map security roles to users or groups.

Specify the syntax of this step as follows:

-MapRolesToUsersStep [
    [role_name everyone? 
    all_authenticated_in_realm? 
    usernames groups]]

Key:

• role_name is a role name defined in the application.
• everyone? is set to Yes or No, to specify whether or not everyone is in the role.
• all_authenticated_in_realm? is set to Yes or No, to specify whether or not all authenticated users can access the application realm.
• usernames is a list of WebSphere Application Server user names, separated by the | character.
• groups is a list of WebSphere Application Server groups, separated by the | character.

Note: For usernames, and groups, the empty string "" means to use the default or existing value. The default value is usually that no users or groups are bound to the role. However, when an application contains an ibm-application-bnd.xmi file, the default value for usernames is obtained from this file. If you are deploying an application that contains an ibm-application-bnd.xmi file, and you want to remove the bound users, specify just the | character (which is the separator for multiple user names). This explicitly specifies no users, and therefore guarantees that no users are bound to the role.

For example:

-MapRolesToUsersStep [
    [ROLE1 No Yes "" ""] 
    [ROLE2 No No WABTestUser1 ""] 
    [ROLE3 No No "" WABTestGroup1] 
    [ROLE4 Yes No "" ""]]

-BlueprintResourceRefPostDeployStep

For an EBA asset, Blueprint components can access WebSphere Application Server resource references. Each reference is declared in a Blueprint XML file, and can be secured using a Java Platform, Enterprise Edition (Java EE) Connector Architecture (JCA) authentication alias. Each bundle in an OSGi application can contain any number of resource reference declarations in its various Blueprint XML files.

When you secure resource references, those resource references can be bound only to JCA authentication aliases that exist on every server or cluster that the OSGi application is deployed to. An OSGi application can be deployed to multiple servers and clusters that are in the same security domain. Therefore, each JCA authentication alias must exist in either the security domain of the target servers and clusters, or the global security domain. See information about modifying the configuration of an EBA composition unit using the editCompUnit command.

Specify the syntax of this step as follows:

-BlueprintResourceRefPostDeployStep [
    [
    bundle_symbolic_name 
    bundle_version 
    blueprint_resource_reference_id 
    interface_name 
    jndi_name 
    authentication_type 
    sharing_setting 
    authentication_alias_name
    ]]

Note: The value for jndi_name must match the jndi name that you declare in the filter attribute of the resource reference element in the Blueprint XML file.

For example, for an EBA file that contains a bundle com.ibm.ws.eba.helloWorldService.properties.bundle.jar at Version 1.0.0, which is to be bound to authentication alias alias1, the command is as follows:

-BlueprintResourceRefPostDeployStep[
    [com.ibm.ws.eba.helloWorldService.properties.bundle 1.0.0 resourceRef 
    javax.sql.DataSource jdbc/Account Container Shareable alias1]]

-WebModuleResourceRefs

For an EBA asset, binding a resource reference maps a resource dependency of the web module to an actual resource available in the server runtime environment. At a minimum, this can be achieved by using a mapping that specifies the JNDI name under which the resource is known in the runtime environment. By default, the JNDI name is the resource ID that you specified in the web.xml file during development of the web application bundle (WAB).

Specify the syntax of this step as follows:

-WebModuleResourceRefs [
    [
    bundle_symbolic_name
    bundle_version
    resource_reference_id
    resource_type
    target_jndi_name
    login_configuration
    login_properties
    extended_properties
	   ]]

For example:

-WebModuleResourceRefs [
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 jdbc/jtaDs javax.sql.DataSource 
    jdbc/helloDs "" "" ""] 
    [com.ibm.ws.eba.helloWorldService.web 1.0.0 jdbc/nonJtaDs javax.sql.DataSource 
    jdbc/helloDsNonJta "" "" "extprop1=extval1"]]

If you use multiple extended properties, the Jython syntax is "extprop1=extval1,extprop2=extval2".

• Using Jython string:

  AdminTask.editCompUnit('-blaID myBLA -cuID cu1 -CUOptions [[.* .* cu1 cudesc 1 false DEFAULT]] -MapTargets 
    [[.* server2]] -ActivationPlanOptions [.* #specname=actplan0+specname=actplan2]')

• Using Jython list:

  AdminTask.editCompUnit(['-blaID', 'myBLA', '-cuID', 'cu1', '-CUOptions', 
    '[[.* .* cu1 cudesc 1 false DEFAULT]]', '-MapTargets', '
    [[.* server2]]', '-ActivationPlanOptions', '[.* #specname=actplan0+specname=actplan2]'])

• Using Jython string:

  AdminTask.editCompUnit('-blaID ourBLA -cuID cu4 -CUOptions [[.* .* cu4 "new cu desc" 1 false DEFAULT]]
     -MapTargets [[a1.jar server1+server2]] -RelationshipOptions [[a1.jar cuname=cub true]]')

• Using Jython list:

  AdminTask.editCompUnit(['-blaID', 'ourBLA', '-cuID', 'cu4', '-CUOptions', '
    [[.* .* cu4 "new cu desc" 1 false DEFAULT]]', '-MapTargets', '[[a1.jar server1+server2]]', '-RelationshipOptions', 
    '[[a1.jar cuname=cub true]]'])

• Using Jython string:

  AdminTask.editCompUnit('[-blaID ourBLA -cuID cu4 -CUOptions [[.* .* cu4 "new cu desc" 1 false DEFAULT]]
     -MapTargets [[a1.jar server1+server2]] -RelationshipOptions [[a1.jar +cuname=cuc true]] -ActivationPlanOptions 
    [a1.jar +specname=actplan2#specname=actplan1]]')

• Using Jython list:

  AdminTask.editCompUnit(['-blaID', 'ourBLA', '-cuID', 'cu4', '-CUOptions', '
    [[.* .* cu4 "new cu desc" 1 false DEFAULT]]', '-MapTargets', '[[a1.jar server1+server2]]', '-RelationshipOptions',
     '[[a1.jar +cuname=cuc true]]', '-ActivationPlanOptions', '[a1.jar +specname=actplan2#specname=actplan1]'])

• Using Jython string:

  AdminTask.editCompUnit('-blaID yourBLA -cuID defaultapp -MapModulesToServers 
    [[defaultapp.war .* WebSphere:cluster=cluster1][Increment.jar .* Websphere:cluster=cluster2]]
     -CtxRootForWebMod [[defaultapp.war .* /]] -MapWebModToVH [[defaultapp.war .* vh1]]')

• Using Jython list:

  AdminTask.editCompUnit(['-blaID', 'yourBLA', '-cuID', 'defaultapp', '-MapModulesToServers', 
   '[[defaultapp.war .* WebSphere:cluster=cluster1][Increment.jar .* Websphere:cluster=cluster2]]', '-CtxRootForWebMod', 
   '[[defaultapp.war .* /]]', '-MapWebModToVH', '[[defaultapp.war .* vh1]]'])

-blaID

Specifies the configuration ID of the business-level application of interest. (String, required)

-includeDescription

Specifies whether to include a description of each asset that the command returns. (String, optional)

-includeType

Specifies whether to include the type for each asset that the command returns. (String, optional)

Websphere:cuname=cu1
asset
"description for cu1"
Websphere:cuname=cu4
bla
"description for cu4"
WebSphere:cuname=defaultapp
Java EE
"description for defaultapp"

-blaID

Specifies the configuration ID of the business-level application of interest. The command accepts an incomplete configuration ID if the system matches it to a unique business-level application ID. (String, required)

-cuID

Specifies the composition unit of interest. The command accepts an incomplete configuration ID if the system matches it to a unique composition unit ID. (String, required)

-targetID

Specifies the name of the target of interest. For example, specify the server name to set the target to a specific server. (String, required)

-enable

Specifies whether to automatically start the composition unit of interest when the specified target starts. Specify true to start the composition unit automatically. If you do not specify true, the system will not start the composition unit when the target starts. The default value is true. (String, required)

-blaID

Specifies the configuration ID of the business-level application of interest. This parameter accepts an incomplete configuration ID if the system matches it to a unique business-level application ID. (String, required)

-cuID

Specifies the configuration ID of the composition unit of interest. This parameter accepts an incomplete configuration ID if the system matches it to a unique composition unit ID. (String, required)

Specify Composition Unit options (CUOptions)

Specify name, description options for Composition Unit.

Parent BLA (parentBLA): [WebSphere:blaname=myBLA]
Backing Id (backingId): [WebSphere:assetname=asset1.zip]
Name (name): [cu1]
Description (description): [cuDesc]
Starting Weight (startingWeight): [0]
Started on distributed (startedOnDistributed): [false]
Restart behavior on update (restartBehaviorOnUpdate): [DEFAULT]

Specify servers (MapTargets)

Specify targets such as application servers or clusters of application servers where you want 
to deploy the cu contained in the application.

Deployable Unit (deplUnit): [default]
*Servers (server): [WebSphere:node=myNode,server=server1]

Specify Composition Unit activation plan options (ActivationPlanOptions)

Specify CU activation plan optionsDeployableUnit Name (deplUnit): [default]
Activation Plan (activationPlan): [WebSphere:specname=actplan0+WebSphere:specname=actplan1] 

• Using latest OSGi application deployment.
• New OSGi application deployment not yet available because it requires bundles that are still downloading.
• New OSGi application deployment available.
• New OSGi application deployment cannot be applied because bundle downloads have failed.

• Using Jython string:

  AdminTask.viewCompUnit('-blaID myBLA -cuID myCompUnit')

• Using Jython list:

  AdminTask.viewCompUnit(['-blaID', 'myBLA', '-cuID', 'myCompUnit'])

• Using Jython string:

  AdminTask.viewCompUnit('-blaID myBLA -cuID defaultApplication')

• Using Jython list:

  AdminTask.viewCompUnit(['-blaID', 'myBLA', '-cuID', 'defaultApplication'])

-name

Specifies a unique name for the new business-level application. (String, required)

-description

Specifies a description of the new business-level application. (String, optional)

WebSphere:blaname=myBLA

-blaID

Specifies the configuration ID of the business-level application of interest. The command accepts an incomplete ID for the blaID parameter, as long as the system can match the string to a unique identifier. For example, you can specify the myBLA partial ID to identify the WebSphere:blaname=myBLA configuration ID. (String, required)

WebSphere:blaname=myBLA

-blaID

Specifies the configuration ID of the business-level application of interest. (String, required)

-BLAOptions

Use the BLAOptions step to specify a new description for the business-level application of interest.

name (read-only)

Specifies the name of the business-level application.

description

Specifies a description of the business-level application.

-blaID

Specifies the configuration ID of the business-level application of interest. Use the listBLAs command to display a list of business-level application configuration IDs. (String, required)

-cuID

Specifies the configuration ID of the composition unit of interest. Use the listCompUnits command to display a list of composition unit configuration IDs. (String, optional)

-blaID

Specifies the configuration ID of the business-level application of interest. (String, optional)

-includeDescription

Specifies whether to include a description of each business-level application that the command returns. Specify true to display the business-level application descriptions. (String, optional)

WebSphere:blaname=myBLA
WebSphere:blaname=yourBLA

• Using Jython:

  AdminTask.listBLAs()

• Using Jython string:

  AdminTask.listBLAs('-blaID myBLA')

• Using Jython list:

  AdminTask.listBLAs(['-blaID', 'myBLA'])

• Using Jython string:

  AdminTask.listBLAs('-includeDescription true')

• Using Jython list:

  AdminTask.listBLAs(['-includeDescription', 'true'])

-blaID

Specifies the configuration ID of the business-level application of interest. (String, required)

-cuID

Specifies the composition unit of interest. (String, optional)

-opName

Specifies the operation name of interest. (String, optional)

-long

Specifies whether to include additional configuration information in the command output. (String, optional)

"Operation: start"
   "Description: Start operation"
   "Operation handler ID: com.mycompany.myasset.ControlOpHandler" 
   "Operation handler data URI: None"
"Operation: stop"
   "Description: Stop operation"
   "Operation handler ID: com.mycompany.myasset.ControlOpHandler"
   "Operation handler data URI: None"
"Operation: clearCache"
   "Description: Clears specified cache or all caches"
   "Operation handler ID: com.mycompany.myasset.ControlOpHandler"
   "Operation handler data URI: None"
   "Parameter: cacheName"
      "Description: Name of cache to clear.  If not specified, all caches are cleared."

-blaID

Specifies the configuration ID of the business-level application to start. The command accepts an incomplete configuration ID if the system matches the string to a unique ID in your configuration. (String, required)

CWWMH0196I: Business-level application "WebSphere:blaname=DefaultApplication" was started successfully. 

-blaID

Specifies the configuration ID of the business-level application to stop. The command accepts an incomplete configuration ID if the system matches the string to a unique ID in your configuration. (String, required)

CWWMH0199I: Business-level application "WebSphere:blaname=myBLA" was stopped successfully. 

-blaID

Specifies the configuration ID of the business-level application of interest. The command accepts an incomplete configuration ID if the system matches the string to a unique business-level application. (String, required)

Specify BLA options (BLAOptions)

Specify options for BLA

*BLA Name (name): [DefaultApplication]
BLA Description (description): []