The Command-Line Tool: Overview and Reference

The Application Center command-line tool supports automated administration and management of Application Center by providing commands that can be executed from the command line or from within a script or batch file.

The command-line tool is implemented in the form of an executable file named AC.EXE. Because the Application Center Setup program adds the program path to the Application Center installation directory, which is in the operating system path, you can execute the command-line tool from any directory. AC.EXE can be executed locally on any computer that has Application Center installed.

WARNING


If you run AC.EXE locally with the /USER and /PASSWORD parameters, command execution will fail when running commands for the local server. You can only supply credentials when you're administering remote servers.

The command-line tool supports remote execution by allowing you to provide the appropriate security credentials for executing commands against other cluster members. This capability is not limited to full installations of Application Center but extends to Administrative client-only installations as well.

NOTE


If security credentials are not supplied in the remote case, the command-line tool defaults to the current logon information when possible.

Command Overview

The command-line tool supports the following commands:

  • CLUSTER—enables you to manage a cluster by providing parameters that let you perform tasks such as create or disband a cluster, add and remove cluster members, and list all cluster members.
  • LOADBALANCE—enables you to manage Network Load Balancing (NLB) on a cluster by providing parameters that let you perform tasks such as enable or disable load balancing for a cluster member, drain server connections, set NLB weights for a member, and obtain load-balancing related status information.
  • CLB—enables you to manage Component Load Balancing (CLB) on a cluster by providing parameters that let you perform tasks such as create a CLB routing list on the controller of a Web/COM+ routing cluster, add or remove entries in the routing list, and obtain routing list information.
  • DEPLOY—enables you to manage application deployment and synchronization on a cluster by providing parameters that let you perform tasks such as deploy an application, specify deployment targets, set deployment options, enable/disable synchronization on cluster members, and obtain deployment status information.
  • APPLICATION—enables you to manage applications on a cluster by providing parameters that let you perform tasks such as create applications, identify application resources (which allows you to create or delete an application on a cluster or member), list applications, and add or remove resources from an application.
  • HELP—provides descriptions of the available command-line tool commands and their syntax.

General Syntax Rules

The Application Center command-line tool syntax is similar to the NET command syntax, and has the following syntax rules:

  • Capital letters represent words that must be typed as shown. Lowercase letters represent names of items that may vary, such as server names.
  • Brackets ([ and ]) enclose optional items that can be supplied with the command.
  • Braces ({ and }) enclose lists of items where you must supply at least one of the items with the command.
  • The vertical bar (|) separates items in a list. Only one of the items can be supplied with the command.
  • Ellipsis within brackets ([...]) mean that you can repeat the previous item. Separate items with spaces.
  • A comma (,) or semi-colon (;) followed by an ellipsis enclosed within brackets([…]) mean that you can repeat the previous item, but you must use the punctuation shown before the ellipsis, not spaces, to separate items.
  • When typed at the command prompt, names of two words or more must be enclosed in quotation marks.

Command-line execution times


Several of the Application Center commands can take longer than expected to complete. The following list provides an estimate for the length of time that certain commands may take to complete.

TimeoutCommands for
35 minutes Create cluster and add member.
20 minutesDisband cluster, clean cluster, and remove member.

Command-Line Execution Confirmation

Several of the Application Center commands that have a high impact on cluster operations require execution confirmation. When these commands are used, you will be prompted for additional input to confirm the execution of the specified command. In this case you will see the following prompt:

 "Are you sure (Y/N)?" 

You can bypass the confirmation dialog box by specifying the /Y parameter with the command. When this parameter is used, the command will execute as if you had answered "Y" to the prompt. This parameter only has to be used once for the command, even if the command produces more than one confirmation prompt.

WARNING


The execution confirmation prompt is implemented as a safety mechanism for commands whose result might directly impact the cluster. You should be careful when using this parameter on commands, because it might have an impact on the cluster in ways that you did not intend.

Command Reference

The following reference information provides usage information, parameter descriptions, and examples for each of the commands supported by AC.EXE.

NOTE


The examples that are provided use the test clusters and members that were described in Chapter 8, "Creating Clusters and Deploying Applications."

Command: AC HELP

The HELP command provides the user with a description of the available Application Center commands, syntax, and usage. HELP covers the following commands:

  • LOADBALANCE
  • DEPLOY
  • CLUSTER
  • CLB
  • APPLICATION

Usage

The first form of the HELP command provides general information about the available help commands:

 AC HELP 

The second form of the HELP command provides information about the specified command:

 AC HELP [command] 

Alternatively, you can use the following syntax to access specific help information about a command:

 AC [command] /?     -or- AC [command] /HELP 

Parameters

Table 11.3 HELP Parameters

ParameterDescription
commandContains the name of the command that the user requires additional information about.

Examples

The following line shows how you would obtain help for the DEPLOY command:

 AC HELP DEPLOY or AC DEPLOY /? 

NOTE


If the command parameter is not specified, a listing of available commands and the basic syntax for the commands is displayed.

Command: AC LOADBALANCE

The AC LOADBALANCE command enables you to manage load balancing for a cluster by supporting the following activities:

  • Enabling or disabling load balancing for a cluster member. As a result of the preceding action the member is either online or offline for load balancing.
  • Setting the NLB weights for a cluster member.
  • Draining active connections to the member.
  • Obtaining NLB-related status information.

Usage

 AC LOADBALANCE  /ONLINE                 [/MEMBER:member_name]                 [/USER:username /PASSWORD:password] AC LOADBALANCE  /ONLINE                 /MEMBERONLY                  AC LOADBALANCE  /OFFLINE                 [/MEMBER:member_name]                 [/USER:username /PASSWORD:password]                 [/DRAIN:time] AC LOADBALANCE  /OFFLINE                   /MEMBERONLY                 [/DRAIN:time]      AC LOADBALANCE  /SETNLBWEIGHT:weight                 [/MEMBER:member_name]                 [/USER:username /PASSWORD:password] AC LOADBALANCE  /STATUS [:All]                 [/MEMBER:member_name]                 [/USER:username /PASSWORD:password] 

Parameters

Table 11.4 LOADBALANCE Parameters

ParameterDescription
/ONLINEEnables load balancing for the specified cluster mem- ber. This does not affect the member's state if it is already in the enabled state. This functionality is avail- able for NLB and CLB clusters only, by default.
/MEMBER:member_nameSpecifies the cluster member on which to apply the specified action. If omitted, the local member is assumed.
/USER:usernameSpecifies the user name to use for authentication, which can be supplied as "domain\username".
/PASSWORD:passwordSpecifies the password to use for authentication.
/MEMBERONLY Sets the server:
  • Online from a suspended state.
  • Offline to a suspended state.

NOTE


When this parameter is used, the LOADBALANCE command must be executed locally. Specifying the /MEMBER parameter in addition to the /MEMBERONLY parameter will result in an error.

/OFFLINEDisables load balancing for the specified cluster member. This does not affect the member's state if it is already in the disabled state. Connections will not be drained from the member unless the /DRAIN parameter is specified. This functionality is available for NLB and CLB clusters only, by default.
/DRAIN:timeDrains the specified cluster member of connections. The value given indicates, in minutes, the timeout value for draining connections. If you do not specify time, the default time specified in the cluster properties is used. If you specify zero, no draining will occur (the same effect as if /OFFLINE was specified without /DRAIN).
/SETNLBWEIGHT:weightSets the relative weight of an NLB cluster member. Valid values are from 0 through 100. (Note that these values do not represent percentages.) This functionality is available for NLB clusters only.
/STATUSProvides load-balancing status information for the specified cluster member. If you specify [:All], status is provided for all cluster members. This functionality is available for NLB and CLB clusters only, by default.

NOTE


If NLB or CLB isn't implemented on a cluster, the /ONLINE, /OFFLINE, and /STATUS parameters only work with the load-balancing devices that are documented in Chapter 13, "Third-Party Load Balancer Support."

Examples

The following example shows how you would set the NLB weight of server1 to 60.

 AC LOADBALANCE /SETNLBWEIGHT:60 /MEMBER:server1 

The next example shows how a user, working on a remote server, can retrieve status information for any cluster member. Whenever you submit a request from a server outside of the cluster, you have to explicitly provide credentials or the wildcard character, the asterisk (*), shown in our example. In this particular case, a prompt is displayed in response to the wildcard.

 AC LOADBALANCE /STATUS:All /MEMBER:server1 /username:user1 /password:* 

Command: AC DEPLOY

The AC DEPLOY command lets you perform several application deployment tasks on a cluster. You can deploy applications from a cluster controller or a cluster member. AC DEPLOY supports the following activities:

  • Deploying Application Center applications within a cluster or from outside the cluster, as in the case of stagers.
  • Listing deployments.
  • Synchronizing an entire cluster or specific member(s).
  • Enabling or disabling automatic synchronization for specific cluster members.
  • Terminating a deployment job.

Usage

The following lines show different ways of using the DEPLOY command with parameters:

 AC DEPLOY   /START             [/DEPNAME:depname]             [/SOURCE:sourcename             /SOURCEUSER:username /SOURCEPASSWORD:*|pwd]             [/TARGETS:targetname1[,...]             /TARGETUSER:username /TARGETPASSWORD:*|pwd]             [/APPNAME:appname1[,...] | /APPGUID:appguid1[,...]]             [/NOACL]             [/COMPLUS]             [/WAIT]       AC DEPLOY   /LISTDEPLOYMENTS             [/SOURCE:sourcename]             [/SOURCEUSER:username /SOURCEPASSWORD:*|pwd] AC DEPLOY   /TERMINATE             {/JOBID:jobid | /DEPNAME:depname} 

NOTE


You should specify /JOBID or /DEPNAME, but not both.

             [/SOURCE:sourcename             /SOURCEUSER:username /SOURCEPASSWORD:*|pwd] AC DEPLOY   /ENABLESYNC             [/SOURCE:sourcename             /SOURCEUSER:username /SOURCEPASSWORD:*|pwd] AC DEPLOY   /DISABLESYNC             [/SOURCE:sourcename             /SOURCEUSER:username /SOURCEPASSWORD:*|pwd] AC DEPLOY   /STATUS[:All]             [/SOURCE:sourcename             /SOURCEUSER:username /SOURCEPASSWORD:*|pwd] 

Parameters

Table 11.5 DEPLOY Parameters

ParameterDescription
/STARTStarts the deployment job.
/DEPNAME:depnameSpecifies a friendly name for the deployment.
/SOURCE:sourcenameSpecifies the source (the cluster controller or cluster member) for deployment. Also specifies the member on which to enable or disable automatic synchronization or obtain status. If you want to authenticate on the source computer, use the /SOURCEUSER and /SOURCEPASSWORD options with /SOURCE. If omitted, the source is assumed to be the local computer.
/SOURCEUSER:usernameSpecifies the user name to use for credentials when authenticating on the source computer, which can be supplied as "domain\username".
/SOURCEPASSWORD:*|pwdSpecifies the password to use for credentials when authenticating on the source computer.
/TARGETS:targetname1[,...]Specifies a list of targets on which to deploy the specified applications.

NOTE


If this parameter is omitted, the application will be deployed to the members of the source cluster.

/TARGETUSER:usernameSpecifies the user name to use for credentials when authenticating on the target computer, which can be supplied as "domain\username".
/TARGETPASSWORD:*|pwdSpecifies the password to use for credentials when authenticating on the target computer.
/APPNAME:appname1[,...] Specifies a list of applications to deploy (by application name). If no applications are specified, the command will deploy all applications from the source.
/APPGUID:appguid1[,...]Specifies a list of applications to deploy (by application GUID). If no applications are specified, the command will deploy all applications from the source.
/NOACLSpecifies that Access Control Lists (ACLs) should not be deployed. ACLs are deployed by default.

NOTE


ACLs are not deployed on partitions that do not support ACLs (for example, FAT), or in nondomain configurations.

/COMPLUSSpecifies that COM+ applications should be deployed as part of the deployment job.
/WAIT Indicates that the deployment should happen synchronously; that is, the command should not return until the deployment is complete. The default behavior happens asynchronously; that is, the command returns immediately.
/LISTDEPLOYMENTSLists the current ongoing deployment jobs and their identifiers, which have been started on the source computer.
/TERMINATETerminates the deployment job. This parameter requires execution confirmation.
/JOBID:jobidSpecifies the job identifier of the deployment job to terminate. This parameter requires execution confirmation.
/ENABLESYNCTurns on synchronization for the specified cluster member. This places it in the synchronization loop. This parameter is not allowed if the cluster controller is specified as the source.
/DISABLESYNCTurns off synchronization for the specified cluster member, taking it out of the synchronization loop. This parameter is not allowed if the cluster controller is specified as the source. This parameter requires execution confirmation.
/STATUS[:All]Displays the current deployment-related status information. If :All is specified, status is given for all members.

Examples

The following example shows how to deploy applications app1, app2, and app3 from controller0 to server1 and server2.

 AC DEPLOY /START /SOURCE:controller0 /TARGETS:server1,server2  /APPNAME:app1,app2,app3 /SOURCEUSER:dba018 /SOURCEPASSWORD:******** /TARGETUSER:dba018 /TARGETPASSWORD:********** 

Remember, if you enter an asterisk (*), rather than a password for the SOURCEPASSWORD and TARGETPASSWORD, the command-line tool will prompt you for both passwords and validate this information before executing the entire command string.

Command: AC CLUSTER

The AC CLUSTER command provides several parameters that enable you to manage a cluster. This command supports:

  • Creating a cluster.
  • Disbanding a cluster.
  • Changing the cluster controller.
  • Adding or removing a member from a cluster.
  • Listing the cluster members.
  • Listing the network adapters on a computer that can be used for load balancing.
  • Removing all of the Application Center cluster settings from a computer.

Usage

NOTE


Different usages are shown for the /CREATE, /ADD, and /REMOVE parameters. Following each parameter are instructions on how to use the parameter.

 AC CLUSTER   /CREATE              [/CONTROLLER:controller_name]              [/USER:username /PASSWORD:password]              /NAME:cluster_name              [/DESCRIPTION:cluster_desc]              /TYPE:web | complusrouting              /LOADBALANCING:nlb              /CLUSTERIP:cluster_ip              /CLUSTERIPSUBNETMASK:ip_subnetmask              [/DEDICATEDIP:dedicated_ip              /DEDICATEDIPSUBNETMASK:ded_subnetmask]              [/AFFINITY:single | class_C | none]              /LBNIC:nic_id              /MANAGEMENTNIC:nic_id 

Use the preceding set of parameters for a Web or COM+ routing cluster with NLB and a clean installation.

 AC CLUSTER   /CREATE              [/CONTROLLER:controller_name]              [/USER:username /PASSWORD:password]              /NAME:cluster_name              [/DESCRIPTION:cluster_desc]              /TYPE:web | complusrouting              /LOADBALANCING:nlb              /KEEPNLBSETTINGS              /MANAGEMENTNIC:nic_id 

Use the preceding set of parameters for a Web or COM+ routing cluster with NLB when upgrading NLB.

 AC CLUSTER   /CREATE               [/CONTROLLER:controller_name]              [/USER:username /PASSWORD:password]              /NAME:cluster_name              [/DESCRIPTION:cluster_desc]              /TYPE:web | complusrouting              /LOADBALANCING:other              [/LBNIC:nic_id]              /MANAGEMENTNIC:nic_id 

Use the preceding set of parameters for a Web or COM+ routing cluster when using a load-balancing method other than NLB.

 AC CLUSTER   /CREATE               [/CONTROLLER:controller_name]              [/USER:username /PASSWORD:password]              /NAME:cluster_name              [/DESCRIPTION:cluster_desc]              /TYPE:web | complusrouting              /LOADBALANCING:none              /MANAGEMENTNIC:nic_id 

Use the preceding set of parameters for a Web or COM+ routing cluster with no load balancing.

 AC CLUSTER   /CREATE               [/CONTROLLER:controller_name]              [/USER:username /PASSWORD:password]              /NAME:cluster_name              [/DESCRIPTION:cluster_desc]              /TYPE:complusapp              /LOADBALANCING:clb              /MANAGEMENTNIC:nic_id 

Use the preceding set of parameters for a COM+ application cluster when using CLB.

 AC CLUSTER   /CREATE               [/CONTROLLER:controller_name]              [/USER:username /PASSWORD:password]              /NAME:cluster_name              [/DESCRIPTION:cluster_desc]              /TYPE:complusapp              /LOADBALANCING:nlb              /CLUSTERIP:cluster_ip              /CLUSTERIPSUBNETMASK:ip_subnetmask              [/DEDICATEDIP:dedicated_ip               /DEDICATEDIPSUBNETMASK:ded_subnetmask]              /LBNIC:nic_id              /MANAGEMENTNIC:nic_id 

Use the preceding set of parameters for a COM+ application cluster with NLB and a clean installation.

 AC CLUSTER   /DELETE              /CONTROLLER:controller_name              [/USER:username /PASSWORD:password] AC CLUSTER   /ADD              /CONTROLLER:controller_name              [/MEMBER:member_name]               /USER:username /PASSWORD:password | *              [/DEDICATEDIP:dedicated_ip              /DEDICATEDIPSUBNETMASK:ded_subnetmask]              [/NOSYNCONADD]              [/DISABLELOADBALANCING]              [/LBNIC:nic_id]              /MANAGEMENTNIC:nic_id 

Use the preceding set of parameters only when adding a new member to a cluster that is using NLB.

 AC CLUSTER   /ADD              /CONTROLLER:controller              [/MEMBER:member_name]               /USER:username /PASSWORD:password | *              [/NOSYNCONADD]              [/DISABLELOADBALANCING]              [/LBNIC:nic_id]              /MANAGEMENTNIC:nic_id 

Use the preceding set of parameters only when adding a new member to a cluster that is using CLB or a load-balancing method other than NLB.

 AC CLUSTER   /ADD              /CONTROLLER:controller_name              [/MEMBER:member_name]              /USER:username /PASSWORD:password | *              [/NOSYNCONADD]              [/DISABLELOADBALANCING]              /MANAGEMENTNIC:nic_id 

The preceding set of parameters only applies when adding a new member to a cluster with no load balancing.

 AC CLUSTER   /REMOVE              [/MEMBER:member_name]              /USER:username /PASSWORD:password | * AC CLUSTER   /REMOVE              /MEMBER:member_name              /CONTROLLER:controller_name              /USER:username /PASSWORD:password | * 

Use the preceding set of parameters to remove a cluster member that does not have Application Center installed or to remove a cluster member that cannot be reached.

 AC CLUSTER   /SETCONTROLLER              [/MEMBER:member_name]              [/USER:username /PASSWORD:password | *]               [/FORCE] AC CLUSTER   /CLEAN              [/KEEPIPS] AC CLUSTER   /LISTMEMBERS              [/MEMBER:member_name]              [/USER:username /PASSWORD:password | *] AC CLUSTER   /LISTNICS              [/COMPUTER:computer_name]              [/USER:username /PASSWORD:password | *] 

Parameters

Table 11.6 CLUSTER Parameters

ParameterDescription
/CREATECreate a new cluster
/CONTROLLER:controller_nameSpecifies the computer to be used as the cluster controller.
/USER:usernameSpecifies the user name to use for authentication, which can be supplied as "domain\username".
/PASSWORD:passwordSpecifies the password to use for authentication.
/NAME:cluster_nameSpecifies a friendly name for the cluster that will be created.
/DESCRIPTION:cluster_desc Provides a text description of the cluster.
/TYPE:web | complusapp | complus-routing Specifies one of three cluster types to create:
  • web: a Web cluster.
  • complusrouting: a COM+ routing cluster.
  • complusapp: a COM+ application cluster.
/LOADBALANCING:NLB | clb | other | none Specifies which type of load balancing to use for the cluster:
  • nlb: Network Load Balancing.
  • clb: Component Load Balancing, which is valid for a COM+ application cluster only.
  • other: third-party load balancing.
  • none: no load balancing supported.
/CLUSTERIP:cluster_ipSpecifies the cluster (shared or virtual) IP address. This parameter is valid only for NLB clusters.
/CLUSTERIPSUBNETMASK: ip_subnetmask Specifies the subnet mask of the cluster IP address.
/DEDICATEDIP:dedicated_ipSpecifies the dedicated IP address of the cluster controller. This parameter is valid only for NLB clusters.
/DEDICATEDSUBNETMASK: ded_subnetmaskSpecifies the dedicated subnet mask of the cluster controller.This parameter is valid only for NLB clusters.
/AFFINITY:single | class_c | noneSpecifies the NLB affinity of the cluster. This parameter is valid only for NLB clusters.
/KEEPNLBSETTINGSIndicates that an NLB upgrade should be performed and to maintain existing NLB settings. This is valid only if the load balancing type is NLB, the cluster type is not complusapp, and NLB is already being used on the computer on which the cluster is being created.
/MANAGEMENTNIC:nic_idSpecifies the instance number of the management network adapter to use on the computer. This identifier can be obtained by executing the command AC CLUSTER /LISTNICS.
/LBNIC:nic_idSpecifies the instance number of the load balancing network adapter to use on the computer. This identifier can be obtained by using /LISTNICS.
/DELETEDisband a cluster.
/ADD Adds the given computer to the cluster. Once the computer is added to the cluster, it will be synchronized with the cluster controller unless /NOSYNCONADD is specified. Note that a different set of options applies depending on whether you are adding a member to an NLB cluster or a non-NLB cluster.
/MEMBER:member_nameSpecifies a cluster member. If omitted, the local computer is assumed.
/NOSYNCONADDSpecifies that once a member is added to a cluster, it should not be synchronized with the controller.
/DISABLELOADBALANCINGSpecifies that the newly added member should not be set online once it is added to the cluster.
/REMOVESpecifies that a member should be removed from the cluster it currently belongs to.

NOTE


Two sets of syntax are shown for use with /REMOVE. Use the second set to remove a cluster member that does not have Application Center installed. You can also use the second set of syntax to remove a member that cannot be reached; in that case, the message "Some settings in the member could not be removed" may be displayed. Use AC CLUSTER /CLEAN to remove these settings from the removed member.

/FORCESpecifies that a controller change should be forced even if the existing controller is not available. This flag must be used in conjunction with /SETCONTROLLER.
/SETCONTROLLERSpecifies that the member identified by /MEMBER should be promoted to cluster controller for the cluster to which it currently belongs.
/CLEAN Specifies that all cluster information should be removed from the local computer. Use this option on computers that are no longer part of a cluster. If the computer on which you want to use /CLEAN is part of cluster, first use AC CLUSTER /REMOVE to remove the member from the cluster. You can also use this command to remove a cluster member while the controller is unavailable. The parameter is available locally only and cannot be executed remotely. This parameter requires execution confirmation.
/KEEPIPSIndicates that when cleaning a computer the cluster IP addresses should not be removed. You can only use this parameter with NLB clusters. Use this parameter only on the cluster controller (when it is the last member in the cluster) or it may result in IP address conflicts.
/LISTMEMBERSDisplays a list of all cluster members in the cluster containing the specified member. When you execute the AC CLUSTER command with /LISTMEMBERS, you receive the following output:
  • Server name.
  • Online status, which can be online, offline, or UNKNOWN.
  • Drain status, which can be draining, blank (if the server is not draining), or UNKNOWN.
  • Alive status, which can be alive, dead, or UNKNOWN.
  • Synchronization status, which can be replicating, blank (if synchronization is not taking place on the computer), or UNKNOWN.
  • Member status, which can be controller, blank (if the computer is a member rather than a controller), or UNKNOWN.
Column headings are not shown in the output. If there are any ambiguities (because of blank or UNKNOWN values), use the order specified in the preceding list to ascertain which status values correspond to which properties.
/LISTNICSDisplays a list of all network adapters on the computer that can be used for load balancing or management traffic.

NOTE


The following sample output identifies, in bold type, the location of the network adapter id:

Network adapters on <machine>

0: [00000000] <description>

1: [00000001] <description>

/COMPUTER:computer_nameSpecifies a computer name to use for listing network adapter information. If this parameter is omitted, the local computer is used.

Examples

The following example shows how to designate server2 as the new controller for the cluster RKWebCluster.

 AC CLUSTER /SETCONTROLLER /MEMBER:server2 

Command: AC CLB

The AC CLB command enables you to work with the CLB routing list on a Web or COM+ routing cluster. By using this command with parameters you can:

  • Set the CLB routing list on the cluster controller.
  • Add members to or remove members from the CLB routing list.
  • Load all of the cluster members in which a specified member exists to the CLB routing list for a specified cluster.
  • List all the servers in a CLB routing list.

Usage

 AC CLB      /SETCLBMEMBERS             [/ROUTINGMEMBER:routing_member]             [/ROUTINGUSER:username /ROUTINGPASSWORD:*|pwd]             /COMPLUSMEMBERS:member[,...] AC CLB      /LOADCLBMEMBERS             [/ROUTINGMEMBER:routing_member]             [/ROUTINGUSER:username /ROUTINGPASSWORD:*|pwd]             /COMPLUSMEMBER:clbmember             [/COMPLUSUSER:username /COMPLUSPASSWORD:*|pwd] AC CLB      /ADDCLBMEMBER             [/ROUTINGMEMBER:routing_member]             [/ROUTINGUSER:username /ROUTINGPASSWORD:*|pwd]             /COMPLUSMEMBER:clbmember              AC CLB      /REMOVECLBMEMBER             [/ROUTINGMEMBER:routing_member]             [/ROUTINGUSER:username /ROUTINGPASSWORD:*|pwd]             /COMPLUSMEMBER:clbmember              AC CLB      /LISTCLBMEMBERS             [/ROUTINGMEMBER:routing_member]             [/ROUTINGUSER:username /ROUTINGPASSWORD:*|pwd]  

Parameters

Table 11.7 CLB Parameters

ParameterDescription
/SETCLBMEMBERSSets the CLB routing list on the controller of the cluster to which the routing member belongs. The routing list is updated with a list of members specified by /COMPLUSMEMBERS. No verification is performed in the list specified by /COMPLUSMEMBERS.
/LISTCLBMEMBERSLists all of the members contained in the CLB routing list.
/ROUTINGMEMBER:routing_memberSpecifies the name of a member in the COM+ routing cluster. If not specified, routing_member is assumed to be the local computer.
/ROUTINGUSER:usernameSpecifies the user name to use for credentials when authenticating on the routing cluster.
/ROUTINGPASSWORD:*|pwdSpecifies the password to use for credentials when authenticating on the routing cluster.
/COMPLUSMEMBERS:member[,...]Specifies the COM+ application cluster members used in the CLB routing list.
/LOADCLBMEMBERS Loads all the members of the cluster that /CLBMEMBER is in to the routing list for the cluster that /ROUTINGMEMBER is a member of.
/COMPLUSMEMBER:clbmemberSpecifies a member of the COM+ application cluster.
/COMPLUSUSER:usernameSpecifies the user name to use for credentials when authenticating on a COM+ application cluster.
/COMPLUSPASSWORD:*|pwdSpecifies the password to use for credentials when authenticating on the back-end COM+ application cluster.
/ADDCLBMEMBERSpecifies that the clbmember should be added to the routing list on the controller of the cluster to which the routing member belongs.
/REMOVECLBMEMBERSpecifies that the clbmember should be removed from the CLB routing list on the controller of the cluster to which the routing member belongs.

Examples

The following example shows how you can retrieve a list of members contained in the CLB routing list. Additionally, the example shows how to provide a user name for authentication and request a prompt to enter a password:

 AC CLB /LISTCLBMEMBERS /ROUTINGMEMBER:machine1 /ROUTINGUSER:user1  /ROUTINGPASSWORD:* 

Command: AC APPLICATION

The AC APPLICATION command allows you to manage applications on a cluster. An application is defined as a collection of resources and can include:

  • Web sites and certificates.
  • COM+ applications.
  • Registry keys.
  • Files and DSNs.

The AC APPLICATION command allows you to:

  • Create an application on or delete an application from a cluster or member.
  • Add resources to or remove resources from an application.
  • List applications and resources.

Usage

 AC APPLICATION   /CREATE                  [/MEMBER:member_name]                  [/USER:username /PASSWORD:password]                  /NAME:appl_name                  [/MEMBERONLY] AC APPLICATION   /DELETE                  [/MEMBER:member_name]                  [/USER:username /PASSWORD:password]                  {/NAME:appl_name | /GUID:appl_guid}                  [/MEMBERONLY] AC APPLICATION   /LIST                  [/MEMBER:member_name]                  [/USER:username /PASSWORD:password]                  [/MEMBERONLY] AC APPLICATION   /ADDRESOURCE                  [/MEMBER:member_name]                  [/USER:username /PASSWORD:password]                  {/NAME:appl_name | /GUID:appl_guid}                   /RESOURCETYPE:resource_type                  /RESOURCEPATH:resource_path                  [/MEMBERONLY] AC APPLICATION   /REMOVERESOURCE                  [/MEMBER:member_name]                  [/USER:username /PASSWORD:password]                  {/NAME:appl_name | /GUID:appl_guid}                   /RESOURCETYPE:resource_type                  /RESOURCEPATH:resource_path                  [/MEMBERONLY] AC APPLICATION   /LISTRESOURCES                  [/MEMBER:member_name]                  [/USER:username /PASSWORD:password]                  {/NAME:appl_name | /GUID:appl_guid}                  [/MEMBERONLY] 

Parameters

Table 11.8 APPLICATION Parameters

ParameterDescription
/CREATESpecifies that you want to create an application on an existing cluster or member.
/MEMBER:member_nameSpecifies a cluster member. If omitted, the local member is assumed.
/USER:usernameSpecifies the user name to use for authentication, which can be supplied as "domain\username".
/PASSWORD:password Specifies the password to use for authentication.
/NAME:appl_name Specifies the name of the application being managed.
/MEMBERONLYSpecifies that the command should be run on the specified member, not on the controller.
/DELETEIndicates that you want to delete an application on a cluster member.
/GUID:appl_guidSpecifies the GUID of the application being managed.
/LISTRESOURCESDisplays a list of all existing resources for a given application.
/ADDRESOURCEIndicates that you want to add a single resource to a single application on the controller of the cluster to which the specified member belongs. You must specify the fully qualified path to the resource to add it to the designated application. If /MEMBERONLY is specified, the resource is added only to the specified member, not to the controller.
/RESOURCETYPE:resource_typeSpecifies the resource to be added to or removed from the application. The following are valid resource types:
  • FileSystem
  • IIS
  • Registry
  • DSN
  • COMPlusApp
/RESOURCEPATH:resource_pathSpecifies the path to the resource to add to or remove from the application. Paths are specified as follows:
  • IIS: the complete metabase path. For example, "/LM/W3SVC/3" or site name ("My Web Site").
  • Registry: the complete registry path. For example, "HKEY_CURRENT_USERS\ Software\Microsoft\ Active Setup\{guid}".
  • FileSystem: the complete file system path. For example, "C:\Program Files\Misc\ MyResource.txt".
  • DSN: the friendly name of the DSN (for example, "My DSN") or unique registry path, such as "My Computer\ HKEY_LOCAL_MACHINE\Software\ ODBC\ODBC.INI\Name".
  • COMPlusApp (COM+ application): the friendly name of the COM+ application or its GUID (CLSID).
/REMOVERESOURCEIndicates that you want to remove a single resource from a single application on the controller of the cluster to which the member belongs. If /MEMBERONLY is specified, the resource is removed only from the specified member, not from the controller.

Examples

The following example shows how to create an application named gamescentral on all the members for an existing cluster.

 AC APPLICATION /CREATE /NAME:gamescentral 

The following example shows how to add a Web site resource to the application salesui.

 AC APPLICATION /ADDRESOURCE /NAME:salesui /RESOURCETYPE:iis /RESOURCEPATH:host1/b_svc/2/root/myvirtualdirectory 

The following example shows how to remove a file resource from the application salesui.

 AC APPLICATION /REMOVERESOURCE /NAME:salesui /RESOURCETYPE:filesystem /RESOURCEPATH:"c:\Program Files\Resources\MyFile.txt" 



Microsoft Application Center 2000 Resource Kit 2001
Microsoft Application Center 2000 Resource Kit 2001
ISBN: N/A
EAN: N/A
Year: 2004
Pages: 183

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net