Generator connection to PC fails

Question ID: 109052
1
0

We are currently using Performance Center 12.55 with Windows 2012 Server R2.

This issue is our Performance Center Load Generators are configured as a process when running TruClient scripts.
We do not see this issue for Load Generators that are configured as a service. It appears that we must set these generators as a process for TruClient Vusers. They will almost spontaneously come back as failed, which is resolved immediately by logging onto the generator and manually enabling the generator in ALM. While this mitigation is easy, it doesn’t remove the root issue, and the generator fails again later.

Consequently, we’ve investigated as an issue of session disconnects. We have not found any information in the LR logs or server logs. We’re unable to replicate the issue on the machine itself, since logging back on resolves the issue.

Mitigation through automatic login isn’t possible, as domain security rejects any automatic connections or saved credentials. Any input would be great.

Marked as spam
Posted by (Questions: 104, Answers: 6)
Asked on July 23, 2019 10:52 am
2 views
Answers
1
Private answer

The random failing of the Load Generators that have the Agent set to run as a process will fail if the user who logs in manually logs off, or a security policy forces a log off. Please work with your security team to ensure that the system user logged on is not logged out.

The following Knowledge Base article was published by Micro Focus and explains the reason why some protocols require the Agent to be run as a process:

* Document ID: KM182623
* Micro Focus Product(s): Performance Center

Summary

What is the difference between running the Performance Center Agent as a process versus a service?

Solution

The Performance Center Agent differs between service and process in the following ways:

1. Login:

Running the Agent as a process requires you to log into the machine in order to connect to it as a Load Generator. The Agent service does not require login, but the system needs to be booted.
The Performance Center Agent service is started in the background as and when system is booted like any other service at windows OS level.

2. Vuser limitation:

The Agent service cannot run GUI, or GUI-like scripts (TruClient, Citrix, SAPGUI), etc.. This is due to the constraints that the operating system puts on services when they run. The Agent process does not have such limitations. It is only limited by the permissions of the user who is logged in.

In light of the KB article referenced above, there is no other option except to run as a process.

I hope this helps

Marked as spam
Posted by (Questions: 104, Answers: 6)
Answered on July 23, 2019 10:53 am