Configuring the LIMS-plus to ChainLinx Integration

Starting in LIMS-plus v3.7.24, you can configure your LIMS-plus system to communicate with JusticeTrax ChainLinx servers used by your submitting agencies. Once configured, LIMS-plus users can query outside agencies for the presence of evidence on lab cases and request that the evidence be transferred to the laboratory.

Define the ChainLinx Integration Directory


Each lab must have a directory defined on the network share where the import and export files for the ChainLinx integration reside. It will typically be on your LIMS-plus server.

In system administration, click System Defaults then click Default Directory Settings.
Click Browse next to the ChainLinx Integration Directory and select the directory where you would like the integration files to be stored.
Click Apply then Close.

Define an Agency's ChainLinx Server


For each agency that uses ChainLinx to which you want to integrate, you will need to enter the URL for the server that hosts their ChainLinx web service. This address must be obtained from that agency.

In system administration, click Agency Info, select the agency you want to configure from the list and click the Edit button.
In the ChainLinx details section, enter the URL for the ChainLinx web service that was provided to you by that agency.
Set the Status to "Active." (You can deactivate an integration by changing this to "Inactive."
The Authentication Method or Token field can be left blank for now. (The token feature will be enabled in a future release.)
Click OK.

Installing the Mail Reader


The integration uses a separate application to interpret the data from Chainlinx, this application is called iPrelog Mailreader (as it was originally created for our iPreLog application). This application runs in the background and polls the ChainLinx folder for any new submissions and inserts them into the Accept Evidence queue automatically. Mailreader runs as a service on the workstation in which it is installed.

The server/workstation on which you are running the install must have:
1.    The 2005 SMO (SQL Server Management Objects) saved to the GAC (Global Assembly Cache.) To determine the server has the SMO objects in question, browse to C:/Windows/Assembly and look for Microsoft.SQLServer.SMO v. or higher.
2. SQL Client Connectivity components.

The user installing the Mailreader must be an administrator on the workstation or server AND a Database Administrator on the LIMS-plus database. The installer runs scripts on that database that will create the SQL authenticated user and give that user the appropriate permissions.

Double-click iPrelogMailReaderInstaller.exe (NOT iPrelogMailReaderSetup.msi. The exe will call the MSI.)
Follow the prompts in the installation wizard.
In the Database Connectivity tab, enter the information about your LIMS-plus database.
On the Email Connectivity tab, check the No email account (poll folder only) check box and browse to the location of the ChainLinx Integration Directory you specified above for the the File Path.

Changing the Account for the Mail Reader

iPrelog Mailreader can be installed anywhere as long as it has permission to read the Chainlinx folder, write to the Chainlinx folder and delete from the Chainlinx folder. Generally, if the Mailreader is installed on a separate workstation than the ChainLinx folder resides you will need to run the service as a specific account, since, by default, the service runs as the Local System Account. Your IT may want to set up an account specifically for this where the password does not expire.

After Mailreader is installed, to change the service account on Mailreader, Go to Control Panel, Administrative Tools, Services, right-click on the iPrelog Mail Reader service and select Properties.

Go to the Logon Tab and choose the “This account” radio button and enter the credentials for the account that will have access to the ChainLinx folder.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk