Host Tab

Context

You define the settings for the host on this tab.

On the Plant Connectivity Management Console screen, select an agent instance and choose the Host tab.

Enter the necessary data in the Log Level field using the following table:

Log Level	Description
Off	No log information is output. This setting is not recommended.
Critical	Only critical messages are logged. This setting is rarely used.
Error	Critical and error messages are logged. This is the default setting.
Warning	Critical, error, and warning messages are logged.
Information	Critical, error, warning, and information messages are logged. Information messages are used for important agent instance events such as starting and stopping the system.
Verbose	Messages of all log levels are logged as well as messages with the status `Verbose`. You should use this setting only if you want to diagnose a vulnerability. Caution Do not use the Verbose setting for a longer period. This has a negative impact on system performance and consumes a lot of memory.

If you select the Run Agent Instance as an Executable checkbox, the agent instance runs as a “normal” Windows process instead of as a Windows service. The agent instance runs with the rights of your user account while you are logged on. When you log off, the agent instance is stopped. Please bear this in mind for productive use.

Note

In this case, steps 4, 5, and 6 are not necessary.

If you do not select this checkbox, the agent instance is run as a Windows service.

Note

A Windows service is created automatically for each agent instance. You can display the list of all services by right-clicking on the computer name in the Windows Explorer, choosing the Manage option, and then selecting Services and Applications.
If the agent instance is to run as a Windows service, you can specify the service user name and the service user password:
- The default service user password is set as \localsystem.
- However, you can choose to enter the domain user name instead: domain\username.

With the help of the following table, enter the necessary information in the Service Start Mode field:

Service Start Mode	Description
Automatic	The agent instance is started automatically when the operating system starts.
Automatic (Delayed Start)	The agent instance is started automatically when the operating system starts. However, the start is delayed (default in the Windows system: two minutes). You can use this start mode if there are connection problems between the agent instance and communication partners that also do not start until the operating system is restarted. Note If necessary, check using the Maintain Dependent Services pushbutton whether you can model the dependency of the agent instance on other services, in order to improve the reliability of starting the agent instance after the operating system is restarted.
Manual	The agent instance is started manually via the Plant Connectivity Management Console or the Windows service. This is the default setting.
Disabled	The agent instance is never started.

If you want to display or configure dependent services of the agent instance, choose the Maintain Dependent Services pushbutton.
If you add any services, they are started before the agent instance service.
Note

The following dependent service is set as standard:
- Windows Event Log
Change the value in the Startup Timeout field as required. The default setting is 5 minutes. This is the maximum amount of time that can be taken to start the agent instance. After this, the start process is terminated.
If necessary, choose a starting group for the agent instance in the Starting Group field or create a new one. By assigning agent instances that belong together from a business point of view to one starting group, you can start and stop agent instances together. (See Using Starting Groups for Agent Instances.)

Note

You should maintain the relevant attributes of the services of the agent instances entirely in the PCo Management Console. Changes that you make to the Windows services of the agent instances in the Microsoft Management Console (MMC) are not included in the PCo configuration. The changes made in the MMC can therefore be overwritten by PCo.