An application is similar to Process resource, but it is more flexible and can be managed by batch script which contains multiple processes.
The reason why program is executed using batch script is because it will make it possible managed by MCCS even when the name of starting program and running program is not the same. Besides this, it not only monitors the existence of process but also monitors the response of process with this.
For these reasons, batch script will provide more detail monitoring and flexibility and an application agent manages this.
Same as process, application is basically executed with the system account, but is can be executed with particular user by using attributes of User, Password, Domain.

이 페이지의 주요 내용

Adding

There are two way to add a resource which one is select this from a group name and another is select this from a resource type.

Adding in Group

When add a resource from a group name, select a group → right click → 'Add Resource'. Or select Edit(E) from the main menu bar → select 'Add Resource'. Or select 'Add Resource' icon from the tool bar.

[Figure] Adding Resource in a group
Select 'Application' from Resource Type lists and click 'Next' button. When add a resource from the Application resource type name, this step will be skipped.

[Figure] Resource Wizard Selection View
Next steps are same as adding in resource type.

Adding in Resource Type

ResourceType → Right Click → Click Add Resource

[Figure] Adding Resource in a resource type
Enter Resource name, pre-script file name in the StartProgram, StopProgram and MonitorProgram box.

[Figure] Adding application resource view
You can browse pre-scripted file when select the file selection icon.

[Figure] Entering script file View
You can browse pre-scripted file when select the file selection icon.

[Figure] Script file selection View
You can also write the script through selecting write script icon.

[Figure] File Editor View
After you have completed all of the input screen.

MCCS checks the list of monitor process list and monitor program when all the value of MonitorProgram and MonitorProcesses is entered.

[Figure] Enter the script files and path for each attribute
If you have an account that can execute application resource, you can enter the account as below.

[Figure] Defining user account
Click 'Finish' and resource is added.

[Figure] Adding Application resource is completed

Deleting

Select resource type → right click → delete resource.

  Select delete menu.

  [Figure] Deleting application resource view

Status

The following table explains the status switching of the MCCS resource caused by a user's command and the status.
The command assumes that it is generated by a user

Application agent: It manages general application items.
It provides a more complex, wider expandability than processes to manage applications and services.

Status	Agent command	Description
Online All the processes registered in MonitorProcesses are running and MonitorProgram returns '0'.	Offline	Runs the script registered in the StopProgram attributes.
	Monitoring	Runs the scripts registered in the MonitorProgram attributes. When the scripts are used for monitoring, the final value of 0 means success and other value means failures. When you use the list of processes registered in the MonitorProcesses attributes for monitoring, if all the processes registered in the list are running, it is success. If not, it is failures. When you register both the process list and the script, both the conditions should be met to be success. If there is no process list or the script is not successful, it is regarded as a failure.
Offline If any one of the processes registered in MonitorProcesses is terminated or the monitoring program returns a non-zero value, it is deemed as offline.	Online	Runs the script registered in the StartProgram attribute. StartProgram attributes allow you to use the batch scripts to run the program in a more flexible way than the process resource. If the wrong path is entered, MCCS will display an error log and the resource cannot be used.
	Monitoring	Refer to the description of monitoring as above.
Trouble When the online resource is switched to offline without using the agent termination command, it is defined as the trouble state.	Online	Refer to the above online command.
	Offline	Runs the script registered in the StopProgram attributes.

Attribute

[Figure] Application Attribute

Attribute	Description	type	Default	Edit	Note
Domain	It specifies domain of user account. It will be ignored if it is not specified by the user account.	STRING		O
MonitorProcesses	It is the list of the process to be monitored. Name of each process is simply the name of the executables. If there is more than one process, they are separated by (','). One of MonitorProcesses and MonitorProgram must be inserted. (ex : dfssvc.exe)	STRING		O	If Monitor Program does not exist, this is required and is able to insert both attributes Both must be satisfying when insert both attributes.
MonitorProgram	It is a program that executes programs for monitoring or inserts the path name of the batch script. One of the values of MonitorProgram and Monitor Processes must be inserted.	FILE		O	If MonitorProcesses does not exist, this is required and is able to insert both attributes Both must be satisfying when insert both attributes.
Password	It is the password defined by the user. If user name is not specified, it is ignored.	PASSWORD		O
StartProgram	It is a program to bring online the Application in each node.	FILE		O
StartupDirectory	It is a work directory. it means %MCCS_HOME if it does not have a input value.	DIRECTORY	(.)	O
StopProgram	It is a program to take offline the Application of each node.	FILE		O
User	It is a user name which has received the permission to use the application. It is MCCS service account if there is no input value.	STRING	System Account	O

Attribute value of ArgList arguments are the values that are added resources and the value can be changed or viewed through ’Specified Attribute’ list on the detailed information panel.

7.4 Applications