InTrust 11.6 - Customization Kit

SystemInformationObject

Example

The following script displays all available information about the "SERVER" computer.

try
{
    var si = new SystemInformationObject();
    print(si.GetComputerName("server"));
    print(si.GetDomainName("server"));
    print(si.GetPlatformId("server"));
    print(si.GetVersionMajor("server"));
    print(si.GetVersionMinor("server"));
    print(si.IsLocalHost("server"));
    
    var ti = si.GetTimeOfDayInfo("server");
    print(ti.elapsedt);
    print(ti.msecs);
    print(ti.hours);
    print(ti.mins);
    print(ti.secs);
    print(ti.hunds);
    print(ti.timezone);
    print(ti.tinterval);
    print(ti.day);
    print(ti.month);
    print(ti.year);
    print(ti.weekday);
}
catch (err)
{
    print("Error: " + err);
}

TextStream

TimeOfDayInfoObject

See also the example for the SystemInformationObject object.

InTrust-Specific Objects

Glossary

An InTrust organization parameter is a setting that affects some aspect of InTrust operation related to agents, jobs, licenses and so on. In InTrust Manager, these settings can be configured in the properties of the InTrust root node, an InTrust server or an agent.

A facet is a file with an agent's organization parameter settings. An agent has one facet per InTrust server; if an agent responds to multiple servers, it has multiple facets. The file is located in the config subfolder of the agent installation folder, and the file name is the GUID of the server from which the agent inherits organization parameter settings.

A facet can contain organization parameter values defined at the following three levels:

1. Organization level, if any parameters are inherited all the way down

2. Server level, if any parameters are defined for the InTrust server and inherited by the agent

3. Agent level, if any parameters are defined specifically for the agent

Organization parameter settings can be read using the ADCEnvironment object. See Organization Parameter Editor for details about setting parameter values for organizations, servers and agents.

Generic Objects

• ScriptState

• GlobalState

• Reference

• ADCEnvironment

Audit Script Object Model

The following objects are available to scripts in custom text log data sources. In addition, these data sources can use all objects available to custom scripted data sources.

• GlobalObject

• AuditProvider

• Event

• Position

• ErrorInfo

Script Callbacks

Provider callbacks

Comparer callback

Audit Script Engine and Audit Script Host Cooperation

The audit script engine exposes a C++ interface to ECMAScript.

This interface does the following:

• Supports the scripting object model

• Dispatches calls between the audit script host and the scripting machine

• Converts parameters from C++ types to scripting types and vice versa

Type conversion takes place as follows:

• C++ type to script callback:

• Script object model to C++ type:

Audit Script Position Processor and Audit Script Host Cooperation

Audit script position processor is a middle layer between Audit script host and position comparer script. Audit script position processor should dispatch calls from AuditScriptPositionProcessor::ComparePositions to the script's Audit_ComparePositions callback.

Error Reporting

Audit script engine errors can be reported in two ways:

• Using the ErrorInfo object (the result is written to the InTrust Server log)

• As exceptions of the ADCException type for the audit script host to catch (the result is included in the InTrust session information)

Notes about exceptions:

• Scripting callbacks should raise a JScript exception if they encounter any exceptional situation.

• The audit script engine should catch such exceptions, translate them to ADCException objects and throw them again as C++ exceptions.

• Script exceptions are translated into C++ exceptions. Exception information appears in session details.

• The audit script position processor has the same error handling model as the audit script engine.