Guru Agents provide a way to automatically move Guru Objects (Files, like STDF test data) from the "local" guru (i.e. Cassini System Controller) or "Guru Server" to a FTP location, local file system (including network mounted drives), or another Guru Server that is not already configured as a "Backup" Guru in the Address Book. Guru Agents are created and edited from the Guru Agent Editor application and usually automatically launched from the "Guru Agent" application.

Example Diagram



A Guru Agent can run directly from a Cassini System or from a Guru Server. If available, it is preferred that the agents are run from the Guru Server instead of from the system. This allows Guru to transfer data at it's own pace (via the "Backup" process), assuring that it doesn't impact test performance while still providing near real-time access to the data.

Agent Configuration Checklist

• Create Guru Agent - Once per System or Guru Server. See Guru Agent Editor User Guide for details.
  Example: "Source Guru, Desination FTP, Execution Type = STDF"
• Network Settings- Share (FTP username/password) or Mount Network Drive (SMB or NSF) locally (gets a drive letter, i.e. "Z:").
  See Connecting a Network Share for details.
• Set Test Exec "Data" tab. See Administrative Tasks - Package Executive Management for details.
• Prepare STDF Reconstruct Agent to use, if needed.

Verify Agent Functionality (Status)

Agents are intended to run transparently, with no visibility to the operator. You can verify that the Agent is running by finding recent data files in the destination (folder or FTP host). If data is not appearing, change the Logging Level from Execution | Settings menu to "2: Log Normal Activity and Errors" and use Guru Browser to find objects with "RiErrorLog" as the ObjectType.

Other Tips

Agents are highly advanced, there can be multiple Sources and Destinations configured in the same agent. See Guru Agent Editor User Guide for details.

The "STDF Copy Agent" waits for an "STDF Summary" record to appear before collecting and assembling the pieces into a single STDF file. The assembled pieces comprise the STDF header, detail, and summary. Typically (depending on handler behavior) the assembly will consist of 100 part sequences (or less).
Normally the Lot is completed when the user presses STOP on the Test Exec. However, it is possible for testing to be interrupted in such a way that the STDF Summary file is not created.
In this case, running an STDF Reconstruct Agent will cause the unprocessed STDF file to be assembled and copied.

Data log entries are stored in guru using the attribute: "ri.sys.ObjClass=RiDataLog". STDF and ATDF data can be distinguished by the ri.dlog.Format=STDFV4" or "ri.dlog.Format=ATDFV2" key value pairs.

Agents can also be used to deploy Released testplans after an external review process. See documentation about "User Agents" for details.