General Collector Properties

How quickly in seconds internal collectors balance themselves across a cluster as nodes get added or removed

How frequently in seconds to poll data-caputre folders for Indirect file transfers

Indirect data capture files will be deleted automatically after they have reached this age. Should be set to Indefinate if attaching by reference.

Most intervals are in seconds (s)

Frequency in seconds that a collector pings the server to update its status and make sure LIMS is alive.

Same as “Server Ping”. This (shorter) frequency occurs when the collector is being viewed in the monitor dashboard and a user has enabled this faster ping.

Frequency (seconds) to poll the instruments (data sources) if no other values  are set

Length of time (seconds) before a direct collector type will switch to indirect mode if pings of the LIMS server are unsuccessful.

Files larger than this size will not be hashed. This applies only to indirect collectors where hashing is enabled.

Recommended value is 3600 seconds. This would mean once an hour, the collector checks the disk space on its host and signals an alert if the availabe space falls below the threshold you have on your collector. Checking available disk space can put a demand on system resources. It is recommended to keep this at a minimum.

How many poll intervals must be missed to alert a collector might be hung. This may occur if your collector is busy capturing files when the next interval check is supposed to occur.

Limits the amount of log information available to be viewed through the dashboard. Recommended max is 48 hours to reduce memory allocated to this feature.

Recommended max is 5000.

Pause or continue collecting after an error

Allows you to temporarily suspend all data captures when the instrument's collector type encounters an error. You will be required to manually resume collection of additional instrument data.

Allows you to temporarily suspend all data captures when the instrument's Attachment Handler encounters an error. You will be required to manually resume collection of additional instrument data once resolved.

This section only applies to External Collectors. If you are not deploying external to the LIMS application server, these properties are not used.

External collectors will communicate with LIMS at this address

Defaults to:

[labvantagehome]/console/install/externalapps/sdmscollector/product

This is a path on the LabVantage application server. It is created when you install LIMS. When an external collector's installer is created, LabVantage will read the Windows or UNIX files in this path. The files will then be zipped and presented to the user for download through the browser. Specify the full path. This could use a variable such as is shown in the default.

Defaults to:

[labvantagehome]/console/install/ear

When an external collector's installer is created, LabVantage will read the sapphire.jar and sdmscollector.jar files in this directory. This could use a variable such as is shown in the default.

Defaults to:

[labvantagehome]/console/install/externalapps/sdmscollector/custom

When an external collector's installer is created, LabVantage will read any custom JAR files you placed in this directory and include them in the download. This is necessary if you have created any custom Collector Types.

Choose Bundle, Local Path, or Local Java Home

Java parameter for memory allocated to this process.

Java parameter for memory allocated to this process.

For advanced users.

Choose None, Fatal, Error, Warn, Status, Info, or Debug to control the level of detail in your log files.

If a log file grows to this size, the Collector spawn a new log file.

After this number of log files are in the logs directory, the oldest log file will be deleted before creating a new log file.

Yes enables the detection of deadlocks. If detected, the system can send you an email. See below.

Yes will log detailed information at the INFO level each time an email is sent.

The Wrapper will attempt to connect to this email host.

The port number of your SMTP host when sending email.

Configures the subject of the email.

Specifies the from address of the email.

Specifies the recipient(s) of the emails. When more than one email is specified, they must be separated by a semicolon (;)

Yes or No

Assumes deadlock detection is enabled above.

Occurs whenever the JVM has exited in a state which results in a restart.

Occurs whenever the JVM has exited in a state which results in a restart and the total number of consecutive failed invocations is more than 5

Occurs whenever the JVM process disappears for an unexpected reason.

Occurs whenever the JVM process is terminated.

Specifies the email body to be sent when JVM restart event occurs.

Allows a URL to be created within LIMS linking a Data Capture to items affected by an Attachment Handler.

Choose an SDC. For example "Sample". This provides a link to this SDC's primary table data from the Data Capture

Specify which page to open. For example: SampleView

Add a value here (such as _blank) if the link should open the page in a new window.