The application resource is the resource where MCCS can start or terminate the program and monitor the status.
It is similar to the process resource. But, it can achieve more complex process and combination by using scripts beside general process execution. In addition, the application resource can set the execution path for starting, terminating or monitoring.
We execute the programs by using the batch scripts because we can handle everything even if the name of start program is different from the name of running process as in the case of service applications.
Sometimes, in the list of running processes, we need to monitor (response test) whether the process is providing proper service as well as monitoring the existence of process (existence test). To process such tasks flexibly, we can use the batch scripts.
In the application resource, you can enter the scripts. Just like the process resource, the applications can basically run on the root account, but by using User attributes, you can run it on a specific user account.

Table of Contents

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

Select a group → right click → 'Add Resource'.
[Figure] Adding Resource in a group
Select 'Application' from Resource Type lists and click 'Next' button.

[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 Application Resource in a resource type
Enter pre-script file name in the StartProgram, StopProgram and MonitorProgram box.

[Figure] Entering script file View
You can click on the Start, Terminate or Monitoring program icon to run each script.

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

[Figure] Select file editor View
You can also write the script through selecting write script icon.

[Figure] Screen Appearing when You Select File Editor
After you have completed all of the input screen.

MCCS checks the list of monitor process list and monitor program when all the 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, then if all the processes registered in the list are running, it is success. If not, it is failures. When both the process list and script are registered, meeting both the conditions means success, and 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
MonitorProcesses	It is the list of processes to monitor. The process name is the name of execution file. If more than one, use a comma (',') as a separator. Either of this value and 'MonitorProgram' must be entered.	STRING		O	If there is no MonitorProgram, you must enter the attribute. You can enter the both attributes. If you do, the both of them should meet the requirements.
MonitorProgram	Enter the path for the program or batch script used to monitor status Either of the value and the 'list of monitoring processes' should be entered.	FILE		O
StartProgram	Enter the path for the batch script or program to run when starting the resource.	FILE		O
StartupDirectory	It is the working directory where the program starts. If there is no input, it means $MCCS_HOME.	DIRECTORY	(.)	O
StopProgram	It is the path for the batch script or program to run when terminating the resource.	FILE		O
User	It is a user account having the rights to use the program. Can run the programs such as Clean, Monitor, Start or Stop. If there is no input, it uses the MCCS execution account.	STRING	root	O

The attribute value is entered to register the resource, and you can change or check it in the 'Specified Attribute'.

7-4 Applications