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.
The command-line tool supports the following commands:
The Application Center command-line tool syntax is similar to the NET command syntax, and has the following syntax rules:
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.
Timeout Commands for 35 minutes Create cluster and add member. 20 minutes Disband cluster, clean cluster, and remove member.
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.
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."
The HELP command provides the user with a description of the available Application Center commands, syntax, and usage. HELP covers the following commands:
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
Parameter | Description |
---|---|
command | Contains 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.
The AC LOADBALANCE command enables you to manage load balancing for a cluster by supporting the following activities:
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
Parameter | Description |
---|---|
/ONLINE | Enables 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_name | Specifies the cluster member on which to apply the specified action. If omitted, the local member is assumed. |
/USER:username | Specifies the user name to use for authentication, which can be supplied as "domain\username". |
/PASSWORD:password | Specifies the password to use for authentication. |
/MEMBERONLY | Sets the server:
|
/OFFLINE | Disables 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:time | Drains 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:weight | Sets 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. |
/STATUS | Provides 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:*
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:
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
Parameter | Description |
---|---|
/START | Starts the deployment job. |
/DEPNAME:depname | Specifies a friendly name for the deployment. |
/SOURCE:sourcename | Specifies 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:username | Specifies the user name to use for credentials when authenticating on the source computer, which can be supplied as "domain\username". |
/SOURCEPASSWORD:*|pwd | Specifies 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.
|
/TARGETUSER:username | Specifies the user name to use for credentials when authenticating on the target computer, which can be supplied as "domain\username". |
/TARGETPASSWORD:*|pwd | Specifies 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. |
/NOACL | Specifies that Access Control Lists (ACLs) should not be deployed. ACLs are deployed by default.
|
/COMPLUS | Specifies 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. |
/LISTDEPLOYMENTS | Lists the current ongoing deployment jobs and their identifiers, which have been started on the source computer. |
/TERMINATE | Terminates the deployment job. This parameter requires execution confirmation. |
/JOBID:jobid | Specifies the job identifier of the deployment job to terminate. This parameter requires execution confirmation. |
/ENABLESYNC | Turns 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. |
/DISABLESYNC | Turns 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.
The AC CLUSTER command provides several parameters that enable you to manage a cluster. This command supports:
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
Parameter | Description |
---|---|
/CREATE | Create a new cluster |
/CONTROLLER:controller_name | Specifies the computer to be used as the cluster controller. |
/USER:username | Specifies the user name to use for authentication, which can be supplied as "domain\username". |
/PASSWORD:password | Specifies the password to use for authentication. |
/NAME:cluster_name | Specifies 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:
|
/LOADBALANCING:NLB | clb | other | none | Specifies which type of load balancing to use for the cluster:
|
/CLUSTERIP:cluster_ip | Specifies 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_ip | Specifies the dedicated IP address of the cluster controller. This parameter is valid only for NLB clusters. |
/DEDICATEDSUBNETMASK: ded_subnetmask | Specifies the dedicated subnet mask of the cluster controller.This parameter is valid only for NLB clusters. |
/AFFINITY:single | class_c | none | Specifies the NLB affinity of the cluster. This parameter is valid only for NLB clusters. |
/KEEPNLBSETTINGS | Indicates 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_id | Specifies 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_id | Specifies the instance number of the load balancing network adapter to use on the computer. This identifier can be obtained by using /LISTNICS. |
/DELETE | Disband 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_name | Specifies a cluster member. If omitted, the local computer is assumed. |
/NOSYNCONADD | Specifies that once a member is added to a cluster, it should not be synchronized with the controller. |
/DISABLELOADBALANCING | Specifies that the newly added member should not be set online once it is added to the cluster. |
/REMOVE | Specifies that a member should be removed from the cluster it currently belongs to.
|
/FORCE | Specifies that a controller change should be forced even if the existing controller is not available. This flag must be used in conjunction with /SETCONTROLLER. |
/SETCONTROLLER | Specifies 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. |
/KEEPIPS | Indicates 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. |
/LISTMEMBERS | Displays 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:
|
/LISTNICS | Displays a list of all network adapters on the computer that can be used for load balancing or management traffic.
|
/COMPUTER:computer_name | Specifies 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
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:
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
Parameter | Description |
---|---|
/SETCLBMEMBERS | Sets 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. |
/LISTCLBMEMBERS | Lists all of the members contained in the CLB routing list. |
/ROUTINGMEMBER:routing_member | Specifies the name of a member in the COM+ routing cluster. If not specified, routing_member is assumed to be the local computer. |
/ROUTINGUSER:username | Specifies the user name to use for credentials when authenticating on the routing cluster. |
/ROUTINGPASSWORD:*|pwd | Specifies 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:clbmember | Specifies a member of the COM+ application cluster. |
/COMPLUSUSER:username | Specifies the user name to use for credentials when authenticating on a COM+ application cluster. |
/COMPLUSPASSWORD:*|pwd | Specifies the password to use for credentials when authenticating on the back-end COM+ application cluster. |
/ADDCLBMEMBER | Specifies that the clbmember should be added to the routing list on the controller of the cluster to which the routing member belongs. |
/REMOVECLBMEMBER | Specifies 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:*
The AC APPLICATION command allows you to manage applications on a cluster. An application is defined as a collection of resources and can include:
The AC APPLICATION command allows you to:
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
Parameter | Description |
---|---|
/CREATE | Specifies that you want to create an application on an existing cluster or member. |
/MEMBER:member_name | Specifies a cluster member. If omitted, the local member is assumed. |
/USER:username | Specifies 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. |
/MEMBERONLY | Specifies that the command should be run on the specified member, not on the controller. |
/DELETE | Indicates that you want to delete an application on a cluster member. |
/GUID:appl_guid | Specifies the GUID of the application being managed. |
/LISTRESOURCES | Displays a list of all existing resources for a given application. |
/ADDRESOURCE | Indicates 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_type | Specifies the resource to be added to or removed from the application. The following are valid resource types:
|
/RESOURCEPATH:resource_path | Specifies the path to the resource to add to or remove from the application. Paths are specified as follows:
|
/REMOVERESOURCE | Indicates 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"