/
7.4 Applications

7.4 Applications

 

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.

Table of Contents

Adding

Add the complex application resource to a group.

  1. 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.

  2. 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.

  3. Enter the name of resource and the program for start, termination and monitoring, or the process lists for monitoring target.
    In the start, terminate or monitoring program, click 'File' button to select each script file
    or, click the 'Edit' button to create a script file.

    1. If all of the monitoring program and the process lists for monitoring target are entered, check whether the monitoring program is successful or whether there are process lists for monitoring target.
    2. The default user for running the basic app is the user that runs the MCCS process.
      If the process needs to run for another user other than the default user, then you must designate an execution account as follows.


    [Figure] Complex Application Resource Added 

  4. Click the 'Finish' to see that the complex application resource is created as follows.
    You can immediately check the result in the management web console.

Deleting

Select resource type → right click → delete resource.
The deleted resource will immediately disappear from the management web console.


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.

StatusAgent commandDescriptionNote

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.

 

Fault

 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.

 
OfflineRuns the script registered in the StopProgram attributes.  

 

 

Attribute

Show the unique attribute of complex application resource.

Attribute

Description

type

DefaultEditNote

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 AccountO 

 

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.

 


Related content