WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows


Application edition management administrative tasks

You can use the Jacl or Jython scripting languages to manage application editions.

The administrative tasks for the application edition manager include the following commands:

activateEdition

The activateEdition command activates an edition.

Target object

None.

Required parameters

-appName
Specifies the name of the application. (String, required)
-edition
Specifies the name of the application edition. (String, required)

Optional parameters

None.

Return value

The command returns:
  • true: success
  • false: failure

Batch mode example usage

Interactive mode example usage

deactivateEdition

The deactivateEdition command deactivates an edition.

Target object

None.

Required parameters

-appName
Specifies the name of the application. (String, required)
-edition
Specifies the name of the application edition. (String, required)

Optional parameters

None.

Return value

The command returns:
  • true: success
  • false: failure

Batch mode example usage

Interactive mode example usage

rolloutEdition

The rolloutEdition command rolls out an edition and specifies the group size.

Target object

None.

Required parameters

-appName
Specifies the name of the application. (String, required)

Optional parameters

-edition
Specifies the value of the custom property. (String, optional)
-params
Specifies configuration values for the rollout. (String, optional)

rollout strategy

  • group: Activates the specified application in place of the current edition of the same application across the cluster on which the application cluster deploys, N servers at a time, as specified by the groupSize keyword. The default group size is 1. During rollout, both editions of the application can serve requests. Always set the group number to be at least one less than the cluster size so that at least one cluster member serves the old edition while the rollout of the new edition starts.
  • atomic: Activates the specified application in place of the current edition of the same application across the cluster on which the application cluster deploys, one half of the cluster at a time, such that only one edition of the application serves requests at any given time.

reset strategy

Specifies how to start an application edition instance during the rollout operation.
  • hard: Stops or restarts the application server.
  • soft: Stops or restarts the application instance, while leaving the application server running.

group size for group rollout

Specifies the number of servers to update when rolloutStrategy is grouped.
  • integer

drainage interval

Specifies the number of seconds to wait before stopping an application edition instance during the rollout such that sessions can complete. The default is 30 seconds.
  • integer

Return value

The command returns:
  • true: success
  • false: failure

Batch mode example usage

Interactive mode example usage

validateEdition

The validateEdition command validates an edition.

Target object

None.

Required parameters

-appName
Specifies the name of the application. (String, required)
-edition
Specifies the name of the application edition. (String, required)

Optional parameters

-params
Specifies the parameters for the dynamic cluster maximum, minimum, and static size.

Return value

The command returns:
  • true: success
  • false: failure

Batch mode example usage

Interactive mode example usage




Related concepts
Application edition manager
Related tasks
Deploying application editions without loss of service
Reference topic    

Terms of Use | Feedback

Last updated: Nov 30, 2007 4:05:14 PM EST
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/reference/radtaskapped.html