| |
Results |
|
DA: How to reconfigure DA agents to connect with a new server
|
DA : How to reconfigure DA agents to connect with a new server
|
|
|
How to Cause a DA Agent to Connect to a New DA Server
|
If assistance is needed, please contact Micro Focus Customer Support and be prepared to offer the log files and any other details regarding error messages or status. Change the Agent’s Server – Option 2 – Using a DA Global Process
|
|
|
|
DA: "Windows could not start the Agent Relay on the Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to the service-specific error code 0"
|
DA: "Windows could not start the Agent Relay on the Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to the service-specific error code 0"
|
|
|
|
How To: Import SSL certificates into the Java keystore used by DA Agent
|
If the Web Services process step is used, the same thing would apply. When a process step attempts to connect to one of these services and the connection is rejects because of improper or missing certificates, the error message will usually contain something like the following:
|
|
|
|
DA: Launching Agents with conflicting names - do they need a different internal id?
|
However, the id should always be unique, this is how we distinguish agents. The general recommendation for such cases is to keep the internal id empty in the AMI. When the agent starts with an empty ID it will generate this ID automatically and will connect to DA without any issues.
|
|
|
|
SRA: Server no longer connects to the agents since mutual authentication has been enabled.
|
locagent1, 12-Aug-2013, trustedCertEntry, Certificate fingerprint (SHA1): F3:31:36:EA:D3: DA :F3:7A:39:1D:D4:E0:B5:9C:8B:EF: DD:27:E8:EE
|
|
|
|
DA: Reinstall or Replace an agent and avoid having to redo component mapping
|
When the agent connects to the server, this property value will insure that the new agent is regarded just as if it were the old one.
|
|
|
|
Checking DA Agent Status
|
Connected – An agent that shows as connected has usually started up and communicated with the server via the JMX port (by default this is 7918). The server will then respond by passing the HTTP connection URL to the agent (this is defined in Administration | Settings | System Settings). Once the agent receives this URL, the agent will attempt to use it to download a small file.
|
|
|
|
DA: Notes on agent upgrade or reinstallation
|
Allow the agent to start, run several minutes, then stop it. We do this so the agent begins to run, attempts to connect to the server, and rewrite the installed.properties file for the new agent.
|
|
|
|
DA: How to run DA Component Process on only one resource/agent at a time
|
Insert the Acquire Lock process step as the first step in the process. Connect the links for process flow from Start to the following steps.
|
|
|
