setup and usage instructions -...

Setup and UsageInstructions

The FRS LinXML Module (pronounced links A M A L) was designed to provide a complete, full-featured data interchange solution for FRS utilizing a set of XML schemas which were developed asa hybrid of the HR-XML Consortium's Background Checking standard. This module will allow youto seamlessly exchange data with any of your clients or criminal researchers no matter whichtechnology platform they currently use. You can interface with other FRS sites via the Internet ratherthan by modem, provided that they too are licensed for the LinXml Module. Examples of otherimplementations possible with this module include interfacing with HR software packages, humanresource, recruiting, and applicant-tracking web-based services, or your client's or vendor’sproprietary technologies.

This user guide will detail all of the features and capabilities of the FRS LinXml Module and provideyou with assistance for setting up and utilizing this powerful tool. The LinXml features in this moduleare listed in the outline below and are covered in detail within this user guide.

Topics Covered in this LinXml User Guide:I. Overview of FRS LinXml and this User GuideII. Configuring the LinXml Default SettingsIII. Setting Up Your Clients and Researchers for LinXmlIV. Interfacing with your FRS and Non-FRS Clients and ResearchersV. Processing SubjectsVI. Setting Up the Automation Server for LinXml ProcessingVII. How Client Requests and Researcher Results are Received/Imported through LinXmlVIII. Delivering Results to Clients Through LinXmlIX. Delivering Research Assignments to Vendors Through LinXmlX. Tracking of LinXml ProcessingXI. Tracking Errors and Troubleshooting

Appendix A: Configuring FTP and Virtual Directories for the Delivery of “Web Link” PDF or TXT Results

Each of these options is covered in detail on the pages that follow in this User Guide

I. Overview of FRS LinXml and this User Guide

The LinXml module in FRS provides powerful XML tools needed to enable the automated dataexchange of background checking requests and results with any of your clients or researchers.For more information about XML (eXtensible Markup Language), view the introduction chapter in the“FRS LinXml Specifications Document” under “Reports” – “LinXml” in FRS.

For the client side of LinXml, support is provided for accepting orders from your clients that cancover any of the background screening searches that you provide through FRS and will send theresults for any of those provided searches back to them.

For the researcher side of LinXml, support is provided for sending orders to your vendors that cancover only the following search types:• Criminal search types• Civil search types• Federal search types• Any of your Criminal-Level Other Search Types• Workers Compensation searches• Any of your Main-Level Other Search Types

Many system-wide, client-level and researcher-level settings are provided to allow you tocustomize the LinXml module to best suit your company’s needs. These are covered in SectionsII and III of this user guide.

As a follow-up to Section III - Setting Up Your Clients and Researchers for LinXml, Section IVcovers the differences between interfacing with FRS and Non-FRS clients and researchers. Thissection also explains how to provide the LinXml specifications to Non-FRS sites so that theirconsultants or programming staffs can build an XML interface to your system.

Section V covers the general information and guidelines for processing subjects through LinXmland it details the special subject-level settings specific to the LinXml module.

The FRS Automation Server is a key tool in the handling of the automated, hands-off processingof LinXml requests and results. Section VI covers all of the LinXml capabilities provided withinthe Automation Server and explains how to configure it for this use.

Section VII explains how the background checking requests are retrieved and received into yourFRS system from your clients. This section also covers how background checking results arereceived into FRS whenever you send search requests to another researcher through LinXml.

Section VIII explains the different methods available to deliver results to your clients throughLinXml. Section IX explains the different methods available to deliver requests to vendors throughLinXml.

Section X covers the LinXml features in FRS for tracking the exchange of research requests andresults through FRS. The tools detailed in this section will allow you to monitor the many LinXmlprocesses that are handled automatically by the Automation Server.

And finally, Section XI provides a comprehensive troubleshooting section for determining andtracking problems with the data exchange in LinXml. A maintenance and support plan is notavailable with the FRS LinXml Module, other than an initial thirty days of support for assistancein getting the LinXml module set up and operational. The reason for this is that operationalsupport for this module will involve programming and development-level consultation with otherprogrammers and consultants employed by your clients and researchers. This type of supportrequires the use of our senior-level engineers and will be billable. Therefore, this section is vitallyimportant to your operations in order to provide your staff with the tools and knowledge neededto be more self-sufficient in troubleshooting LinXml problems with your clients and researchers.

LinXml.com Web Service vs. Manual Processing of XML Requests and Results:If you have purchased the FRS LinXml Module under the “Gold Plan”, you will have the ability totransfer LinXml requests and results “Manually” through email or FTP that you and your IT staffhandle yourselves, as well as through the www.LinXml.com “Web Service”. If you choose to usethe “Manual” processing option, the following sections of this user guide touch on certain areaswith information of which you should be aware.• III. Setting Up Your Clients and Researchers for LinXml

• VI. Setting Up the Automation Server for LinXml Processing

• VII. How Client Requests and Researcher Results are Received/Imported through LinXml

• VIII. Delivering Results to Clients Through LinXml

• IX. Delivering Research Assignments to Vendors Through LinXml

FRS LinXml Licensing and Feature Information Available before Purchasing this Module:If you are not yet licensed for the FRS LinXml Module, you can view pricing, licensing and otherinformation about this module by going to the following menu options in FRS:• Choose “Reports” from the menu across the top• Select the “FRS LinXml” option

To assist you in growing your business and securing new clients, prior to purchasing a license tothe FRS LinXml Module, FRS still provides you with the ability to email LinXml specifications toclients or researchers who desire to interface with you via XML. To find out more about thisoption, see Section IV - Interfacing with your FRS and Non-FRS Clients and Researchers.

II. Configuring the LinXml Default Settings

There are a variety of system-wide settings that should be configured to optimize your company’suse of the LinXml module. These are available in the following areas within FRS:a. FRS LinXml Control Centerb. Results Delivery System Defaultsc. Freeze Settings under the System Defaults

a. FRS LinXml Control Center

The “FRS LinXml Control Center” is accessed by doing the following:• Choose “Reports” from the main FRS menu across the top• Select the “FRS LinXml” option from the Reports Menu• A screen similar to the following will be displayed:

ì In this area, configure the reports to be printed by the Automation Server when LinXml requests areimported. Note: These are the same four reports that can be printed by the Web Site Server when auto-importing web requests, but the options above must be checked to enable them for LinXml requests.

í This section displays your LinXml Site Identifier (which is the same as your FRS Connect Site Identifier)which is used to distinguish your site from others when exchanging data through LinXml. Also in thissection, checkboxes are displayed to indicate which LinXml delivery methods your site is licensed for.

î These options are covered in Section VII - How Client Requests and Researcher Results areReceived/Imported through LinXml.

ï These options are covered in Section X. ð These options are covered in Section IV.

b. Results Delivery System Defaults

The “Results Delivery Default Settings” are accessed by doing the following:• Choose “Setup” from the main FRS menu across the top• Select the “Maintain System Defaults” option from the Setup Menu• Click on the “Results Delivery Defaults” option• A screen similar to the following will be displayed:

Each of these results delivery defaults has been expanded to also apply to the delivery andprocessing of LinXml results.

c. Freeze Settings under the System Defaults

The “Freeze and Discrepancy Settings” are accessed by doing the following:• Choose “Setup” from the main FRS menu across the top• Select the “Maintain System Defaults” option from the Setup Menu• Click on the “Freeze and Discrepancy Settings” option• A screen similar to the following will be displayed:

Each of these “Freeze” settings has been expanded to also apply to imported LinXml requests.

In addition, the following new behind-the-scenes “Freeze” options have be programmed into theLinXml module:• When invalid Criminal-Level Other Search Types are imported that do not match your Other Search

Types table• When invalid Statewide states are ordered that you have not configured as valid under “Research

Coverage by State” in the Maintain System Defaults option• When invalid Workers Comp states are ordered that you have not configured as valid under “Research

Coverage by State” in the Maintain System Defaults option• When invalid Main-Level Other Search Types are imported that do not match your Other Search Types

table• When research results other than Criminal/Civil/Other/Federal, Workers Comp or Main-Level Other

Search Types are imported from LinXml researchers

III. Setting Up Your Clients and Researchers for LinXml

To set up a client for the XML method of transmitting results and receiving requests, follow thesesteps to edit a client and configure it for LinXml:• Choose “Setup” from the main FRS menu across the top• Select the “Maintain Client List” option from the Setup Menu• Highlight a client in the list and double-click the item to edit the client• A screen similar to the following will be displayed:

Choose one of these two LinXml “Result Delivery Methods” to begin setting up a client for theLinXml method of transmission.• XML (Web Service) - This delivery method utilizes the secure web service at www.LinXml.com for

transmitting requests and results. The Automation Server handles all processes and transmissionsin a hands-off fashion with its automatic features when using this method and any user processes are

only necessary for submitting partial or supplemental results (covered in Section VIII). • XML (Manual) - This delivery method allows you to send XML requests and results by FTP or Email.

This method requires a good deal of manual labor, but also provides the flexibility to interface with in-house processes and other systems. With FTP and Email, the responsibility of security for thesetransmissions will be up to you and your IT staff.

NOTES:• The XML (Manual) option is only available if you purchased the LinXml module under the “Gold Plan”• Explanations of how “Web Service” processes are handled are covered later in this user guide• The handling of “Manual” processes are also covered later in this user guide• If you select the “Web Service” method here, you must also check the option to “[X] Provide Access

through the LinXml.com Web Service for this Client”, covered later in this section

Click on the “LinXml Settings” tab while editing a client to access a wide array of features that havebeen provided for fine-tuning the services that you provide to each client through LinXml.

ì a. You must assign a “Site Identifier” to each LinXml client. The “<=== Assign a Site Identifier” buttonwill take you to a screen to assist with this. Under this option, if the site is another FRS Site, then youwill key in that site’s Site Identifier (which you must obtain from them). If the client is not an FRS site,then a tool is provided here to assign a compatible site identifier.b. If you wish to interface to this client through the LinXml.com web service, then check theappropriate checkbox here to signal to the Automation Server that it should automatically handle allof the retrieval of client requests and delivery of client results with the web service.c. There is a button here to “Email LinXml Specifications” to this client. This feature is covered in more

detail in Section IV.

LinXml Client Setup (continued)

í a. Returned Results Format: You have four different options for the method of returning results toyour clients via XML.

- XML data fields in a fully structured format

- XML data fields in a free-form, text format

- A web link to your generated PDF results file

- A web link to your generated TXT results file

- Post the results to your web site rather than send as XML

If you choose option 3 or 4 to provide results to your clients in a “Web Link”:< An XML file of results will still be sent, but rather than the detailed screening results in the XML data

<Screenings> section, only a link to a results file will be provided< You will also need to specify a location at your web site in the “Path for Delivery of Web Link Results

at Your Web Site” field for the Automation Server to deliver these and for the client to retrieve them< The Automation Server will generate these PDF or TXT files automatically for you and deliver them

(for PDFs, the Adobe Acrobat Distiller is required on the Automation Server machine)< You will need to also choose the “Configure FTP Info >” button to provide the FTP settings for the

Automation Server to use for delivering these results files to your web site (see Appendix A in thisuser guide for detailed information on these settings)

Note: Samples of each of these XML formats can be viewed in Appendix B of the “FRS LinXmlSpecifications Document” (see Section IV.)

b. By choosing the appropriate “Path Type:” setting, you can either deliver a results file through the “WebLink” option, or just provide a link to your web application’s login page. If you choose the secondoption of “Link to a Login Page...” then you must also set this client up for web site access and selectthe setting described in î on the next page.

c. Set up a “Local Folder” under the LinXml\CLIENTS sub-folder to designate a location for creating the XMLresults files for delivery to this client. If the client is set up for Web Service delivery, then the AutomationServer will pull the XML files from this folder and deliver them for you. If the client is set up for “Manual”delivery, see Section VIII for details on how to handle and deliver these results manually.

NOTE: The icons on this screen provide more on-line help info on the two “paths” to set up here.

LinXml Client Setup (continued)

î The LinXml results delivery method can be used simultaneously with the Website Posting deliverymethod to allow you to deliver results via XML and to your web site at the same time. If you wish touse this option, then check this box to “Post a Copy of the Results to your FRS Web Application Also”.This will require that you also set the client up for Website access under the “Web Admin/Special” tab.

ï This setting will allow you to specify that the Automation Server only deliver XML results to this clientif the original request came in through XML. This setting can be used during the conversion period ofswitching a client from one of the other delivery methods to XML, so that you can manually deliver oldrequests via the old method until all new requests are coming in via XML.

ð Check this option if you want to have the Automation Server automatically order an “ExecutiveSummary” on all requests that come in for this client. Note: This setting applies to orders imported from your web site for this client also

ñ Provisions are available in the LinXml module to automatically send emails to your clients (providedthat you are licensed for the FRS Automated Email module):a. To notify when new results have been delivered to the LinXml Web Service for them and are

available for retrievalb. To send a confirmation email when new requests are received via XML

Click on the [ Message > ] buttons to customize these notification and confirmation messages for eachclient. These messages can include substitutable parameters which will be filled in at the time eachmessage is emailed to include some of the following information:%n = Number of Subject Results Delivered%b = LinXml Batch ID%s = List of Subject Names whose Results are being Reported

Important: If you have the second checkbox selected here, “[X] Send Email Confirmation whenNew Requests Received through LinXml for this Client”, if errors are encountered in anyXML request file sent to you through LinXml indicating that this client’s IT staff did notfollow the LinXml Specifications correctly and the requests were not imported, then anemail will be sent to them detailing the problem with the XML request file that was sent.

LinXml Researcher Setup:

To set up a researcher for the XML method of transmitting research requests and receiving results,follow these steps to edit a researcher and configure them for LinXml:• Choose “Setup” from the main FRS menu across the top• Select the “Maintain Researcher List” option from the Setup Menu• Highlight a researcher in the list and double-click the item to edit them• A screen similar to the following will be displayed:

Choose one of these two LinXml “Methods of Transmission for Research Lists” to begin settingup a researcher for LinXml.• XML (Web Service) - This delivery method utilizes the secure web service at www.LinXml.com for

transmitting requests and results. The Automation Server handles all processes and transmissionsin a hands-off fashion with its automatic features when using this method.

• XML (Manual) - This delivery method allows you to send XML requests and results by FTP or Email.This method requires a good deal of manual labor, but also provides the flexibility to interface with in-house processes and other systems. With FTP and Email, the responsibility of security for thesetransmissions will be up to you and your IT staff.

NOTES:• The XML (Manual) option is only available if you purchased the LinXml module under the “Gold Plan”• Explanations of how “Web Service” processes are handled are covered later in this user guide• The handling of “Manual” processes are also covered later in this user guide• If you select the “Web Service” method here, you must also check the option to “[X] Provide Access

through the LinXml.com Web Service for this Researcher”, covered later in this section

Click on the “LinXml Settings” tab while editing a researcher to access a wide array of features thathave been provided for fine-tuning the XML data interchange with each LinXml researcher.

ì a. You must assign a “Site Identifier” to each LinXml researcher. The “<=== Assign a Site Identifier”button will take you to a screen to assist with this. Under this option, if the site is another FRS Site,then you will key in that site’s Site Identifier (which you must obtain from them). If the researcher is notan FRS site, then a tool is provided here to assign a compatible site identifier.b. If you wish to interface to this researcher through the LinXml.com web service, then check theappropriate checkbox here to signal to the Automation Server that it should automatically handle allof the retrieval of researcher results and delivery of this researcher’s requests with the web service.

í Set up a “Local Folder” under the LinXml\VENDORS sub-folder to designate a location for creating theXML request files to be sent to this researcher. If the researcher is set up for Web Service delivery,then the Automation Server will pull the XML files from this folder and deliver them for you. If the

researcher is set up for “Manual” delivery, see Section IX for details on how to handle and deliverthese requests manually.

NOTE: The icon on this screen provides more on-line help info on the “Local Folder” to set up here.

LinXml Researcher Setup (continued)

î Provisions are available in the LinXml module to automatically send emails to your researchers(provided that you are licensed for the FRS Automated Email module):a. To notify when new research requests have been delivered to the LinXml Web Service for them

and are available for retrievalb. To send a confirmation email when new results are received via XML

Click on the [ Message > ] buttons to customize these notification and confirmation messages for eachresearcher. These messages can include substitutable parameters which will be filled in at the timeeach message is emailed to include some of the following information:%n = Number of Subject Requests Delivered%b = LinXml Batch ID

Important: If you have the second checkbox selected here, “[X] Send Email Confirmation whenNew Results Received through LinXml for this Researcher”, if errors are encounteredin any XML result file sent to you through LinXml indicating that this researcher’s IT staffdid not follow the LinXml Specifications correctly and the results were not imported, thenan email will be sent to them detailing the problem with the XML result file that was sent.

ï This button can be used to “Email the LinXml Specifications” to this researcher. This feature is coveredin more detail in Section IV.

IV. Interfacing with your FRS and Your Non-FRS Clients and Researchers

Other FRS Sites Licensed for LinXml:If you want to interface with other FRS sites that are also licensed for LinXml, the process is very simplefor setting up your two sites to exchange through XML. Also, no programming is required and the FRSsoftware handles all of the XML file creation, importing, delivery (when you both use the www.LinXml.comWeb Service), and processing for both of your sites.

The following steps are required to begin interfacing with a non-FRS site:1. Set up the client or researcher under FRS “Setup”, if you have not already done so2. In FRS, go to the FRS LinXml Control Center under “Reports” – “FRS LinXml”3. Click on the large button in the lower-right corner of this screen entitled “View LinXml Specification

Documents, Deliver them to Clients and Researchers......”4. Click on either of the “Email the LinXml Specs to a Client” (or “Researcher”) buttons and email your

Site-Specifics Specifications Document to them5. Have them do the same here and email their specs to you6. Then each of you should use the Site Identifier and other “Site-Specific” information to set up each

other’s sites for LinXml communication with the settings covered in Section III7. Then, once each of your sites have completed all of the other LinXml setup options covered in this

User Guide, each of your Automation Servers should handle the rest to link you up via XML

NOTE: More details about the FRS LinXml Control Center and emailing specs to your clients andresearchers are covered later in this section

Non-FRS Clients and Researchers: This can include HR software packages, human resource,recruiting, or applicant-tracking web-based services, or yourclient's or vendor’s proprietary technologies

Interfacing to your Non-FRS clients and researchers is just as simple for you, but they will have to programtheir systems to meet the LinXml specifications in order to exchange requests and results with you viaXML. That is the reason that we created our XML schemas as a hybrid of the HR-XML Consortium’sBackground Checking standard as it is becoming the most widely accepted XML standard for backgroundscreening. If the other party with whom you wish to communicate is already XML-Ready, then hopefullythey have an XML format in place that is very close to this specification.

The following steps are required to begin interfacing with another FRS site:1. Set up the client or researcher under FRS “Setup”, if you have not already done so2. In FRS, go to the FRS LinXml Control Center under “Reports” – “FRS LinXml”3. Click on the large button in the lower-right corner of this screen entitled “View LinXml Specification

Documents, Deliver them to Clients and Researchers......”4. Click on either of the “Email the LinXml Specs to a Client” (or “Researcher”) buttons and email your

Site-Specifics Specifications Document to themNote: The FRS LinXml Specifications Document is very comprehensive, contains 100+ pages ofdetailed specifications and provides everything that a component programmer with XML experiencewould need to develop an interface to your FRS software.

5. Work with their IT staff to assist them with testing their new interface into your system. If needed, youcan purchase senior-level consulting services from Imagination Technologies to assist with this project,just submit a Work Order (covered later in this section)

6. Then, once the other party’s interface is ready and has been tested, set up that client or researcher’sLinXml settings as covered in Section III

7. Then, provided that you have completed all of the other LinXml setup options covered in this UserGuide, the two of you may begin to exchange requests and results via XML

The FRS LinXml Control Center and LinXml Specifications

The “FRS LinXml Control Center” is accessed by doing the following:• Choose “Reports” from the main FRS menu across the top• Select the “FRS LinXml” option from the Reports Menu• A screen similar to the following will be displayed:

ì and í See Section II - Configuring the LinXml Default Settings

î See Section VII - How Client Requests and Researcher Results are Received/Imported through LinXml

ï See Section X - Tracking of LinXml Processing

ð Click on this button to access the “FRS LinXml Specifications” screen

All of the options on the “FRS LinXml Specifications”screen are covered on the next page

FRS LinXml Specifications:

LinXml Specifications Document:The FRS LinXml Specifications Document is a very comprehensive set of XML specifications which coversthe different LinXml schemas in great detail. It contains more than 100 pages of XML programmingspecifications with many XML samples and fully commented programming samples provided in six differentweb-enabled development languages. This specifications document was created for you to email to yourNon-FRS clients and researchers so that they can develop an interface to your FRS software via XML.

ì This option can be selected if you wish to view a copy of the specifications document that is emailedto your clients and researchers. Please feel free to study and review this document so that you canassist your clients with generating their unique orders in XML format to send to you. One specialprovision with the LinXml schema is for a client to send the work LOOKUP in the <County> tag if theywant you to “look up” the appropriate county according to the subject’s address for performing thecriminal searches. The LOOKUP feature is covered in that specifications document.

LinXml Site-Specific Document:Through the incredible flexibility of the Flexible Research System, each FRS site has the ability to performscreening in a different way. Each of your clients can be configured with many different flexible optionsand settings as well. Therefore, to go along with the overall FRS LinXml Specifications document, whenemailing these specs, a customized “Site-Specific Document” is generated for each of your clients andresearchers during the email process to provide them with the unique settings they will need to use in orderto do business with you via XML.

The Site-Specific Document includes:• The needed site identifiers and acct codes to identify your site and theirs when sending requests and results• LinXml.com Web Service authentication settings for added security of the transmissions• Your client’s customized Package Billing Code information to help ensure that your billing is correct• Special settings for criminal, MVR and Other Search Types based on your service offerings

ð By keying them into these fields, you can also provide additional information or instructions to beincluded in each generated Site-Specific document for your clients or researchers.

A generic example of one of these Site-Specific Documents is displayed later in this section.

î Click on these buttons to view client and researcher Site-Specific samples that will be sent for “your site”.

FRS LinXml Specifications (continued):

Emailing the Specifications to Clients or Researchers:After setting up a client or researcher for LinXml, you will need to email the LinXml Specifications to them.For other FRS sites, this is mainly so that they can obtain the “Site Identifiers” and other details neededto set your company up on their end. For the Non-FRS sites, they will need your specifications documentsso that they can develop an interface to your FRS system.

í These buttons have been provided to email these specifications to your clients and researchers. The“Site-Specifics Document” is unique to each site, so these options must be used to generate the correctinformation and send it to each client or researcher.

Other documents or attachments that are sent in these emails will be listed within the blue text box in thescreen above.

Work Order, User Guide and LinXml Pricing / Licensing:

ï Since operational support for LinXml requires the use of our senior-level engineers and will be billable,a work order must be submitted to request these support services. Click on this button to view a WorkOrder in Adobe Acrobat format. Print it out, fill it in and fax it over to our offices so that we canschedule the resources to assist you.Important: Before submitting a Work Order and requesting our consulting services, make sure that youhave thoroughly exhausted the resources in Section XI for troubleshooting common LinXml problems.

ñ Click on this button to view this FRS LinXml User Guide at any time

ò Click on this button to view the latest licensing and pricing information as well as the additional servicesavailable with the FRS LinXml module

Sample of a LinXml Site-Specific Document:

LinXml Site-Specific Settings for Image-I-Nation Research For ABC Company Charlotte, NC

SPECIAL XML TAGS:=================> Image-I-Nation Research's LinXml "Site Identifier" is ITI_RESEARCH - Pass this identifier in the <DestSiteIdentifier> tag when submitting XML requests - This identifier will be in the <SourceSiteIdentifier> tag in XML results returned to you> Your LinXml "Site Identifier" is SAMPLESITEID - Pass this identifier in the <SourceSiteIdentifier> tag when submitting XML requests - This identifier will be in the <DestSiteIdentifier> tag in XML results returned to you> Your LinXml "Account Code" is CLIENT - Pass this code in the <AcctCode> tag when submitting XML requests - This code will also be in the <AcctCode> tag in XML results returned to you> Use the <Reference2> tag to pass "Position" information when submitting requests.

WEB SERVICE AUTHENTICATION:===========================> Authentication for https://www.LinXml.com: - The current LinXml User ID value to pass in the "userId=" parameter of the <BackgroundCheck....> tag of your submitted requests is: SampleID example: <BackgroundCheck....userId="SampleID"...> - The current LinXml Password value to pass in the "password=" parameter of the <BackgroundCheck....> tag of your submitted requests is: SamplePW example: <BackgroundCheck....password="SamplePW"...>

<PackageID> TAG SETTINGS FOR YOUR REQUEST ORDERS:=================================================When submitting orders to us, if the package of requests meet any of the following, then you should include the specified "Package Name" in the <PackageID> tag within your submitted XML requests.

Package Name Crim MVR WkComp Credit STrace Employ Educat ProfLic Other------------ ---- --- ------ ------ ------ ------ ------ ------- ----- STANDARD X X X X MVRONLY X CRIMONLY X MANAGEMENT X X X X X X

REQUIRED FIELDS FOR MVR ORDERS:===============================> If ordering MVR searches from any of the following states, a valid birthdate for the subject is required in the <DateOfBirth> tag: - AR, AZ, CO, GA, ID, MT, OK, TX> If ordering MVR searches from any of the following states, a valid gender or the sex of the subject is required in the <GenderCode> tag: - GA, ID, MT> If ordering MVR searches from any of the following states, the subject's middle name is not required, but helps to ensure a positive match when provided in the <MiddleName> tag: - AZ, GA, ID, MT, NE, NY, OK, UT, VA

CRIMINAL/CIVIL/FEDERAL ORDERING SPECIFICS:==========================================

<BackgroundCheck> Requests Schema---------------------------------For ordering Criminal, Civil, Federal and Other Court Searches, the following

guidelines must be used for passing the correct information in the<Screening type="criminal" qualifier="???"> tag as well as the other XMLtags within that section of this LinXml schema.

Search Type qualifier="???" <County> tag <CourtType> tag -------------------- --------------- ---------------- ---------------------Felony/Misdemeanor county (county to search) Felony MisdemeanorFelony Only county (county to search) FelonyMisdemeanor Only county (county to search) MisdemeanorCriminal Statewide statewide STATEWIDE Felony MisdemeanorUpper and Lower Civil county (county to search) Upper / Lower CivilUpper Civil county (county to search) Upper CivilLower Civil county (county to search) Lower CivilFederal Criminal county (district to search) Federal

Other Court-Level Searches that we Provide:-------------------------------------------Search Type: Bankruptcy qualifier="???": Bankruptcy <County> tag: (the particular jurisdiction to search)<Region> tag: (the particular state to search)<CourtType> tag: Bankruptcy

Search Type: Federal Civil Search qualifier="???": Federal Civil Search <County> tag: (the particular jurisdiction to search)<Region> tag: (the particular state to search)<CourtType> tag: Federal Civil Search

Search Type: Nationwide Wants & Warrants qualifier="???": Nationwide Wants & Warrants <County> tag: NATIONWIDE<Region> tag: US<CourtType> tag: Nationwide Wants & Warrants

<BackgroundReports> Results Schema----------------------------------When Criminal, Civil, Federal and Other Court Search results are returned,the following parameters will be used for passing this information in the<Screening type="criminal" qualifier="???"> tag as well as the other XMLtags within that section of this LinXml schema.

Search Type qualifier="???" <County> tag <CourtType> tag ---------------- --------------- ---------------- -------------------------Criminal criminal (county searched) Felony and/or MisdemeanorCivil civil (county searched) Upper and/or Lower CivilFederal Criminal federal (district searched) FederalAny Other Court- (the other (jurisdiction (the other search type) Level Search search type) searched)

"OTHER" SEARCH TYPES AVAILABLE FOR ORDERING WITH <Screening type="other"...>:=============================================================================The search types below can be ordered in the qualifier="?????" attribute ofthe <Screening type="other"...> tag.

Search Type: Character References

Search Type: Drug Testing

Search Type: Tenant Screening Ordering Instructions for the <OtherSearchCriteria> tag: -------------------------------------------------------- Please provide the name of the apartment complex, the property management company (if known), the apartment number, the name of the on-site apartment manager, the rent amount, the occupancy date range and whether or not the security deposit was returned (if known).

We only accept requests through the LinXml.com Web Service.

V. Processing Subjects

When processing subjects that have been imported through LinXml and that are configured forresults delivery through LinXml, the standard research of the subject remains essentially the same.With LinXml subjects, there are just a few added enhancements which are covered here for youto utilize as needed.

Supporting Documentation Field:This is a free-form field that is available for each subject and can be used in conjunction with yourclients or researchers to pass additional information, supporting documentation, links to supportingdocumentation, etc. This field is based on the HR-XML Consortium’s Background Checkingspecification and is provided in the LinXml specification for a variety of uses. This field is intendedas a flexible container that allows a client to pass through additional information needed in supportof the background search to their screening provider. This field can be used by you and yourclients or researchers to exchange screening-specific information such as release forms, links torelease forms or other important criteria required to conduct a background screening.

Another use of this field within FRS is as follows. When sending searches to a vendor from FRS,only three basic search types are supported within the LinXml specification. These arecriminal/civil/other, workers comp, and main-level other search types. So, if any results are everreturned to you through LinXml that fall outside of these supported search types, the XML resultsare placed into the Supporting Documentation field to prevent you from losing that information andresults. Should this ever happen, you can cut-and-paste those results into the appropriate profileediting screens. Also, if this does happen, the subject will automatically be frozen and thefollowing comment will be placed into the Internal Comments field: "FREEZE: Unsupported profileresults returned through LinXml - View the LinXml Supporting Docs for more details".

See the screenshots on the next page for an illustration

on the use of the “Supporting Documentation” field

Supporting Documentation Field (continued):

í Check this box if you want to send a subject’s “Supporting Documentation” information to anyresearchers to which this subject’s search requests are sent via LinXml

• Your clients can send Supporting Documentation to you in their LinXml requests in the<SupportingDocumentation> XML tag and they will appear here for each subject sent

• If you need to send this client Supporting Documentation or other that you key to one of your LinXml

researchers through this <SupportingDocumentation> XML tag, then check the box í displayed above• Any time the [ LinXml Supporting Docs ] field contains information either transmitted by one of your

clients, automatically populated by the Automation Server for non-supported XML results, or keyed by

your staff then the blue checkmark indicated above as ì will appear next to the editing/viewing button

î If your client sends over a requested “Returned Results Format” (see the FRS LinXml SpecificationsDocument) in their LinXml requests, then that requested method of the format will be displayed here

VI. Setting Up the Automation Server for LinXml Processing

The FRS Automation Server handles all of the automation for the FRS LinXml module. Below isa list of the many processes handled by the Automation Server as part of this very full-featuredmodule:• Imports client requests• Exports client results• Exports search requests for researchers• Imports search results from researchers• Interfaces to the LinXml.com Web Service to....

....retrieve screening requests from your clients

....send screening results to your clients

....send screening requests to your researchers

....retrieve screening results from your researchers

....enable and disable which of your clients and researchers are allowed access to your businessthrough the web service

• Submits confirmation and notification emails when configured under client and researcher setup• Generate PDF and TXT versions of results reports for “Web Link” XML results and when delivery to

“Website Also” (PDF report generation requires Adobe Acrobat Distiller running on the same machineas the Automation Server)

So, as you can see, with LinXml, the Automation Server further expands its impressive “workhorse”capabilities for you.

Automation Server Setup:

1. SOAP and XML Toolkit:There is basically one special requirement to set up the Automation Server to handle the LinXml processesdescribed above. This is that the SOAP and XML Toolkit is loaded onto the machine that is running yourAutomation Server application. If you are already set up and utilizing the MVR X-Change, FRS PASSTReports or the FRS i-Credit module on your Automation Server, then you already have the SOAP andXML Toolkit installed. If you are not utilizing any of these FRS tools, then you will need to install the SOAPand XML Toolkit. We provide a download to this toolkit at the FRS Web-Tech if you need it. For completedetails on how to download and install the SOAP and XML Toolkit, please do the following in the main FRSapplication:• Choose “Help” from the main FRS menu across the top• Select the “Other FRS Manuals” option from the Help Menu• Select either the “FRS MVR X-Change User Guide” or the “FRS PASST User Guide” option• Locate Section “V. Setting Up and Configuring the FRS Automation Server” in either of these user

guides and follow the instructions there for downloading and installing the SOAP and XML Toolkit foryour Automation Server’s workstation

2. Adobe Acrobat Distiller:In addition, if you will be generating PDF versions of results reports for “Web Link” XML results or will bedelivering results to your “Website Also” simultaneously with LinXml results, then the Adobe AcrobatDistiller must be installed and running on the same machine as the Automation Server. If you are alreadylicensed and configured with the FRS Web Application or are delivering PDF results with the FRSAutomated Email module, then you should already have the Adobe Acrobat Distiller running on theAutomation Server’s workstation. If not, then please turn to page 6.68 in the main FRS User Guide whichcan also be found under the “Help” menu in FRS for details on purchasing, installing and setting up theAdobe Acrobat Distiller. Note: This requires the “Professional” version of Adobe Acrobat ver. 6.0 or higher.

LinXml.com Web Service vs. Manual Processing of XML Requests and Results:

The FRS Automation Server handles the processing of both LinXml request and result processing totallyin an unattended fashion. When you have your clients and researchers set up to process through theLinXml.com Web Service, then no manual intervention is necessary for any of these processes.

But, if you have any of your clients or researchers configured for “XML (Manual)” delivery, then as its nameimplies, manual intervention will be required by your staff. For these “XML (Manual)” delivery (and import)sites, once you have received their XML request files (from clients) or XML results files (from researchers),you will need to save or copy these XML files into the <main frs folder>\LINXML\IMPORT folder. For anexact path to this folder, go to the FRS LinXml Control Center by selecting “Reports” from the main FRSmenu, then “FRS LinXml” from the reports menu. Then, click on the button in the middle of that screenentitled [ Click Here to View Instructions for XML Files Delivered or Picked Up Manually ] to determine theexact path where manually delivered files should be dropped off. The Automation Server will read thisimport folder once every two minutes and attempt to import all files found there. For more information on

how XML files are imported into FRS, see Section VII.

For the manual delivery of your client results, the Automation Server will create these XML result files inspecial directories and you will have to pick these files from there and deliver them to your clients. Eachof your clients’ result delivery folders will reside under <main frs folder>\LINXML\CLIENTS. You willactually name these folders when setting up your clients for LinXml. To see where each client’s result fileswill be created for you to deliver manually, turn to page 9 in this user guide and read the explanation for

íc. For more information on submitting client results and how they should be delivered, see Section VIII.

For the manual delivery of your researcher requests, the Automation Server will create these XML requestfiles in special directories and you will have to pick these files from there and deliver them to yourresearchers. Each of your researchers’ request delivery folders will reside under <main frsfolder>\LINXML\VENDORS. You will actually name these folders when setting up your researchers forLinXml. To see where each researcher’s request files will be created for you to deliver manually, turn to

page 12 in this user guide and read the explanation for í there. For more information on submittingresearcher requests and how they should be delivered, see Section IX.

VII. How Client Requests and Researcher Results are Received/Imported through LinXml

The FRS Automation Server handles the importing of client requests and researcher results automatically.When you have clients and researchers set up to process through the LinXml.com Web Service, then theAutomation Server retrieves these XML files and then imports them.

If you have any of your clients or researchers configured for “XML (Manual)” delivery, then when youreceive new requests or results manually, you will need to to save or copy these XML files into the <mainfrs folder>\LINXML\IMPORT folder. For an exact path to this folder, go to the FRS LinXml Control Centerby selecting “Reports” from the main FRS menu, then choose “FRS LinXml” from the reports menu. The

following screen will be displayed. Click on the button indicated by î below to see the exact path wheremanually delivered files should be dropped off. Under this button you will also find the location of the\SAVE folder where these XML files are saved for 30 days in case you need to archive or investigate themlater.

These reports can bec o n f i g u r e d t oautomatically print onthe Aut o m at i onServ er’s defaul tprinter as requestsare imported.

N o t e : M a n u a limporting is onlyavailable when youare licensed underthe “Gold Plan”purchase of theLinXml module. Ifyou are licensed formanual importing anddelivery, it will beindicated by thesetting in í here.

ï Whether loaded/imported by the LinXml.com web service or manually, the option available under thisbutton will show you a history of these loaded batches.

ð When requests or results are imported, errors can occur, especially if coming from a Non-FRS sitewhere your client’s or researcher’s programmers have not successfully followed the LinXmlSpecifications when developing their XML files. Therefore it is important to use this option to checkon import errors. This option is covered in more detail in Section X - Tracking of LinXml Processing.

Note: See Section II for system default “Freeze” settings that affect imported LinXml requests andResearch Result Delivery settings that affect imported results.

Confirmation Emails:When you have clients or researchers set up with LinXml settings to send confirmation emails, then asrequests or results are imported, emails will be sent to these sites by the Automation Server letting themknow that you received this XML information. Also, if there were any errors importing their XML files, anemail is sent to them indicating the error(s) encountered while attempting to import their XML files.

VIII. Delivering Re sults to Clients T hrough LinXml

XML results files are generated by the Automation Server. For clients configured for web servicedelivery, these results are automatically sent to the LinXml.com web service for your clients to retrieve.For clients configured for manual delivery, the XML files are deposited into the folders that you actuallyname when setting up your clients for LinXml. To see where each client’s result files will be createdfor you to deliver manually, turn to page 9 in this user guide and read the explanation for íc. You willhave to take care of delivering these manual results outside of FRS.

The LinXml module has been designed with many flexible options and customizable settings foreach of your clients’ results delivery. These are covered in Section III in this user guide.

How Res ult s are Sent to the Autom ati on Se rver f or L inXml Del ivery:

Completed Results:Completed subject results are automatically exported to XML for delivery to clients within two minutes ofbeing completed. To prevent these completed results from automatically exporting before they have been“Proofed”, see the default setting in Section II of this user guide to find out how to require proofing beforeauto-delivery by the Automation Server.

Partial Results:Partial results can be sent through LinXml, butthere is no provision to send them automatically.

To send a partial result for a subject, from themain Subjects List, right-click over a subject andchoose the “Send LinXml Partial Results” menuoption from the right-click menu..

Supplemental Results:Once a subject’s completed results have beendelivered through LinXml automatically by the AutomationServer, you may have an occasion to send supplementalresults due to an update to the subject’s results.

To send a supplemental result for a subject, from themain Subjects List, right-click over a subject and choosethe “Send LinXml Supplemental Results” menu optionfrom the right-click menu..

NOTE: When you right-click over any subject in thesubject list that is assigned to a client configured forLinXml delivery, then either of the two extra delivery itemsillustrated above will appear on the right-click menu,depending upon whether the subject is completed (supplemental) or not (partial).

How Results are Sent to the Automation Server for LinXml Delivery (continued):

Re-Submitting Completed Results:If you have a need to resend a completed, previously-delivered result to a LinXml client, but you want tosend it as a “COMPLETE” status rather than in “SUPPLEMENTAL” status, then do the following.

Select the subject from the main Subjects List,then right-click over the subject to display thesubject right-click menu. From this menu, choosethe “Reset to Re-Send” option. The subject’sresults will be reset for delivery, then within twominutes, the Automation Server will export thesubject’s results again for XML delivery.

Other Settings and Information Pertaining to the Delivery of Results to Clients with LinXml:

Daily Status Reporting:There is no XML method of sending Daily Status information through LinXml. So you still have the twooriginal choices if you wish to send Daily Status Reports to your LinXml clients.

The first option is to set these clients up to simultaneously publish results as XML and to your web site.This will force a new Daily Status Report to your web site every hour for these clients.

The second option is to fax or email Daily Status Reports to your clients at intervals that you wish to. Thisis accomplished by choosing “Reports” from the main menu across the top in FRS and selecting “DailyStatus Reports” from the Reports Menu. You can either choose clients one at a time, or you can generate

for “All Clients”. If you generate for all clients, you should select the “¤ Include Web/LinXml Clients”setting in order to include clients set up for LinXml delivery in the list of Daily Status Reports generated.

Adjudication and Discrepancy Reporting:If you are licensed for the FRS Adjudication Module and you have any of your LinXml clients set up for

“x - Discrepancy Reporting Only for this Client (Hire/Don’t Hire)” under the client’s “Advanced Settings”tab, then those client’s results will be delivered within the XML files with a “Results Status” of “HIRE” or

“DONTHIRE” and the subject’s actual “Reason for Discrepancy”. If you have the “x - Include Full Resultson the Hire/Don’t Hire Report” checked under the client’s “Advanced Settings”, then the full screeningresults will be delivered in the XML files. Otherwise, just the “Results Status” and “Reason forDiscrepancy” will be reported.

Archived Result XML Files:Each XML result file created for a client is saved into a folder named \SAVE under the “Local Folder” you

define for each (see the explanation for íc. on page 9 in this user guide). These XML files are retainedin these SAVE folders for 60 days in case you need to investigate any on behalf of your client or theirprogramming staff.

IX. Delivering Research Assignments to Vendors Through LinXml

XML research request files are generated by the Automation Server. For researchers configured forweb service delivery, these requests are automatically sent to the LinXml.com web service for yourresearchers to retrieve. For researchers configured for manual delivery, the XML files are depositedinto the folders that you actually name when setting up your researchers for LinXml. To see whereeach researcher’s request files will be created for you to deliver manually, turn to page 12 in this userguide and read the explanation for í there.

The LinXml module has been designed with many flexible options and customizable settings fordelivering each of your researchers’ requests. These are covered in Section III in this user guide.

Search Types Supported within the FRS LinXml Module for Delivery to Researchers:

For the researcher side of LinXml, support is provided for sending orders to your vendors that cancover only the following search types:• Criminal search types• Civil search types• Federal search types• Any of your Criminal-Level Other Search Types• Workers Compensation searches• Any of your Main-Level Other Search Types

Assigning Searches for Distribution through the FRS LinXml Module:

Criminal/Civil/Other/Federal Search Types:These searches are assigned through the normal methods under the “Maintain Researcher List” optionof assigning “Geographical Coverage”. Then, when a researcher’s “Method of Transmission for ResearchLists” is set to either “LinXml (Web Service)” or “LinXml (Manual)”, then the Automation Server will exportthese requests to XML files for delivery to the researcher. Also, all researchers set to LinXml delivery fortheir research assignments will be excluded from the “One-Touch Search List Distribution” option so thatthey remain available for XML distribution by the Automation Server.

Workers Compensation Searches:Workers Comp searches are assigned through the normal methods under the “Maintain Researcher List”option of assigning “Geographical Coverage”. When an assigned researcher’s “Method of Transmissionfor Research Lists” is set to either “LinXml (Web Service)” or “LinXml (Manual)”, then the AutomationServer will export these requests to XML files for delivery to the researcher. Also, all researchers set toLinXml delivery for their research assignments will be excluded from the “One-Touch Search ListDistribution” option so that they remain available for XML distribution by the Automation Server.

Main-Level Other Search Types (MLOST):Main-Level Other Searches are assigned for LinXml research in a different manner fromCriminal/Civil/Other and Workers Comp searchers. Each individual MLOST ordered for your subjects mustbe assigned to a LinXml researcher individually and the Automation Server will export these requests toXML files.

Turn to the next page for details on the two different methods available for making these research assignments.

Main-Level Other Search Types (MLOST) (continued):The two methods for assigning LinXml researchers to MLOST orders are described below.

1. Assigning LinXml Researchers to MLOST Orders IndividuallyWhen adding or editing a Main-Level Other Search Type Verification for a subject, you can assign a

researcher by selecting the “Researched By” button illustrated below k. A listing will display showing allof the researchers that have been assigned with that particular MLOST as one of their geographicalcoverage assignments. You will then be able to choose and assign a researcher to the request.

2. Assigning Researchers to a Batch of Unassigned MLOST OrdersA new option has been provided to assign researchers to MLOST orders as a batch. Any unassigned MLOSTcan be assigned in multiples from this option, which also allows you to view the current workloads of all LinXmlresearchers, permitting you to make better decisions about distributing the pending MLOST searches amongyour LinXml vendors. This option is accessed by “Reports” – “Search Lists” – “LinXml Verif ication Research Assignments”.

ì A listing o f al lunassigned MLOSTorders will display here

í Use these buttons toselect the search(es) formaking the assign-ments. A checkmark willbe displayed in the firstco l um n fo r eac hselected search

î After selecting all of thedesired searches, choosethis button to display a listof the researcher(s)assigned to providecoverage for the selectedMLOST and choose oneto assign to the selecteds e a r c h e s . T h a tresearcher’s code willthen be displayed in the“Assigned” column on theright.

ï After all searches thatyou wish to assign have been assigned to a researcher, you must choose this button to apply the assignments to theactual search requests. Once the assignments are applied to the search requests, they will disappear from the listing,until all verifications have been assigned.

ð At any time, you may select this button to view a listing of all of your researchers who have been set up to provide coveragefor verifications along with their current assignment counts to determine current workloads in making these assignments.

NOTE: When selecting the î option above, the researcher costs will or will not be listed for each researcher.This option is controlled within the “Maintain Search Lists Default” option under “Maintain System Defaults”.

Other Settings and Information Regarding the Processing of Researcher Requests with LinXml:

Returned Results:After XML results are returned from LinXml researchers, the Automation Server will load them in andmatch them back to their original subjects. See the “Results Delivery System Defaults” topic in SectionII of this user guide for special options that can be configured to process these returned results.

Archived Researcher Request XML Files:Each XML request file created for a researcher is saved into a folder named \SAVE under the “Local

Folder” you define for each (see the explanation for í on page 12 in this user guide). These XML filesare retained in these SAVE folders for 60 days in case you need to investigate any on behalf of yourresearcher or their programming staff.

X. Tracking the LinXml Processing

A variety of tools are provided in FRS for the tracking of LinXml processing. Since so much ofthe processing in this module is handled automatically by the FRS Automation Server and theLinXml.com Web Service, these tracking tools are very important to keep your management andIT staff aware of all of the LinXml processes which are happening behind-the-scenes. Therefore,we encourage you to read through this section and use these tools in your daily operations withLinXml.

Audit-Tracking:More than 50 LinXml audit-tracking points are provided to give you a clear picture of all LinXml processesperformed for each subject. These processes include the importing of requests and results, the deliveryof each of these, and the special processes available such as “freezing” of requests for various reasons.If you have any questions or issues with the LinXml processing for a particular subject, the first step forinvestigating this should be to view the subject’s “Audit Trail” by right-clicking over the subject from thesubject editing list.

Email Notifications:Each LinXml client and researcher can be configured to receive email confirmations as requests andresults are imported. Likewise, if any of these imported requests or results cause an error, (usually dueto failure by the other party to follow the LinXml schemas and specifications when dealing with non-FRSsites), the confirmation emails will be sent as an error notification and will include details as to the reasonwhy the delivered XML file failed to import. Also, each client and researcher can be configured for emailnotification when new results or requests are posted for them at the LinXml.com web service. Any of these emails can be tracked, viewed and printed by going to the Utilities menu and choosing“Maintain the Automated Email Log”. The emails described above will show up with either "Linxml Noti."for notifications or "Linxml Conf." for confirmations in the Type column there.

LinXml Listing Screens:For the tracking of XML import and export processes, there are four listing reports available in the LinXmlControl Center which are illustrated below.

The “FRS LinXml Control Center” isaccessed by doing the following:• Choose “Reports” from the main

FRS menu across the top• Select the “FRS LinXml” option

from the Reports Menu• A screen similar to the one on

the right will be displayed:

These four listing screens ì - ïare very important tools to usefor tracking and investigatingyour system’s LinXml processingand are covered in more detail on the next page.

LinXml Listings (continued):

ì View Listing of XML Request and Result Batches LoadedThis listing will allow you to track the history of all XML files imported from your LinXml clients andresearchers.

í View Listing of XML Request and Result Import ErrorsWhen errors occur importing XML requests or results, the details for these errors can be found underthis listing.

î View Listing of LinXml FTP and HTTP Connectivity ErrorsWhen errors occur sending PDF reports via FTP to your web site, when you are delivering XML resultswith the “link” option, or when HTTP errors occur when the Automation Server is interfacing to theLinXml.com web service, then those errors will be logged in this listing for you to investigate and workto resolve.

ï View Listing of Site Identifier Authentication RegistrationsWhen you set up clients and researchers to allow them access to the LinXml.com web service, theAutomation Server will automatically turn on the access for these companies at www.LinXml.com.When you revoke access to one of these clients, the Automation Server will revoke that access aswell. Each of these Authentication Registrations will be logged to this listing for you to review andtrack as needed.

LinXml Listings (continued):

When any of these listing options are selected, a listing screen similar to the following is displayed:

The legends at the bottom of each of these screens will explain the “Type” column and the color-coding.You can double-click, right-click or select the “View Details...” button on any of these listing screens to seemore detail about any item and a detail screen similar to the following will be displayed.

Please use these LinXml Listing toolsto investigate XML issues and anytime that you feel that something isout of place, missing or abnormal withany of your LinXml clients,researchers, or their requests/results.

Error Notification: You can set upusers in your office to be notified anytime a LinXml import error or FTP /HTTP connectivity error occurs todirect them to come to these listingscreens and investigate the issues.

This error notification can be set upfor the users of your choice by doingthe following:• Choose “Setup” from the main

FRS menu across the top• Select the “Setup for User

Notification” option from the Setup Menu

XI. Tracking Errors and Troubleshooting

This is a comprehensive troubleshooting section for determining and tracking most problems withthe data exchange in LinXml. Since an ongoing maintenance and support plan is not availablewith the FRS LinXml Module, this section is vitally important to your operations in order to provideyour staff with the tools and knowledge needed to be more self-sufficient in troubleshootingLinXml problems with your clients and researchers.

A. Tracking and Troubleshooting Results Delivery to Clients

FAQ: Why are a LinXml client’s results not getting exported or delivered to them?Check the following:1. Make sure that you have the client properly configured for LinXml delivery (see Section III)

2. Read Section VIII to make sure that you understand how the delivery of complete, partial andsupplemental results are handled

3. Make sure the subject is not frozen4. Have you viewed the Audit Trail for the subject to see if it has ever been delivered?5. Have you checked “Results Reporting History” under the “Utilities Menu”?6. Check the proofing flag for LinXml results delivery and see if this applies (see “Results

Delivery System Defaults” in Section II)7. Automation Server:

a. Is your Automation Server currently running? b. Is it set up and configured as specified in Section VI?

c. On the Automation Server monitoring screen, is the : FRS LinXML checkbox selected?d. Watch the Automation Server screen to ensure that every two minutes (??:02:00,

??:04:00, etc.), one of the “LinXml Processing” messages is displayed8. If you have a client configured for delivery through the LinXml.com web service:

a. Make sure that you have the “Results Delivery Method” set to “LinXml (Web Service)” -see Section III

b. Have you checked the “View Listing of LinXml HTTP and FTP Connectivity Errors” option(see Section X) to ensure that your Automation Server hasn’t encountered any errors whileinterfacing to the LinXml.com web service or your web site?

c. Have you checked the “View Listing of Site Identifier Authentication Registrations” option(see Section X) to ensure that your client was successfully registered with the LinXml.comWeb Service?

d. Are your monthly, semi-monthly or annual gateway fees paid and up-to-date?9. If you have a client configured for manual delivery of their XML files, then search this PDF

document for the word “manual” to fully understand where these manual-delivery XML resultsfiles are created, and remember that these manual XML files must be delivered to your clientsby you, outside of FRS.

10. Is the client set up to “only deliver results via XML that came in through XML”? If so, did the

request actually come in through XML or was it via another method? (see ï on page 10of this guide in Section III for more on this setting)

B. Tracking and Troubleshooting Request Delivery to Researchers

FAQ: Why aren’t a LinXml researcher’s requests getting exported or delivered to them?Check the following:1. Make sure that you have the researcher properly configured for LinXml delivery (see Section

III)

2. Read Section IX to make sure that you understand how to assign searches to LinXmlresearchers and that you have assigned these correctly

3. Make sure the intended subjects are not frozen4. Have you viewed the Audit Trail for the subject to see if the searches have possibly been

distributed to other researchers or by other means?5. Automation Server:



??:04:00, etc.), one of the “LinXml Processing” messages is displayed6. If you have a researcher configured for request delivery through the LinXml.com web service:

a. Make sure that you have the “Method of Transmission for Research Lists” set to “LinXml(Web Service)” - see Section III


c. Have you checked the “View Listing of Site Identifier Authentication Registrations” option(see Section X) to ensure that your researcher was successfully registered with theLinXml.com Web Service?

d. Are your monthly, semi-monthly or annual gateway fees paid and up-to-date?7. If you have a researcher configured for manual delivery of their XML files, then search this

PDF document for the word “manual” to fully understand where these manual-delivery XMLresults files are created, and remember that these manual XML files must be delivered to yourresearchers by you, outside of FRS.

C. Problems Receiving/Importing Requests from Clients

FAQ: Why aren’t requests being imported for a client who said they were delivered to theLinXml.com web service or that we dropped off in the FRS\LINXML\IMPORT folder formanual importing?Check the following:1. Make sure that you have the client properly configured for LinXml delivery (see Section III)2. Read Section VII to make sure that you understand how XML requests and results are

imported through LinXml3. Automation Server:



??:04:00, etc.), one of the “LinXml Processing” messages is displayed4. If you have a client configured for interfacing through the LinXml.com web service:

a. Make sure that you have the “Results Delivery Method” set to “LinXml (Web Service)” -

see Section IIIb. Have you checked the “View Listing of LinXml HTTP and FTP Connectivity Errors” option

(see Section X) to ensure that your Automation Server hasn’t encountered any errors whileinterfacing to the LinXml.com web service or your web site?

c. Have you checked the “View Listing of Site Identifier Authentication Registrations” option(see Section X) to ensure that your client was successfully registered with the LinXml.comWeb Service?

d. Are your monthly, semi-monthly or annual gateway fees paid and up-to-date?5. Have you checked the “View Listing of XML Request and Result Batches Loaded” option (see

Section X) to determine for sure whether or not the XML request file has been imported byyour Automation Server?

6. Have you checked the “View Listing of XML Request and Result Import Errors” option (seeSection X) to ensure that your Automation Server hasn’t encountered any errors whileimporting the requests?NOTE: If errors are found here, see topic E - “XML Import File Problems” on the next pagefor details on how to troubleshoot this problem

7. If you have a client configured for manual delivery of their XML files, then search this PDFdocument for the word “manual” to fully understand where to place the client’s XML importfiles for the Automation Server to retrieve them

8. If your client submitted the requests to the LinXml.com web service, did they receive aconfirmation and “receipt” that the requests were successfully received at the web service?

D. Problems Receiving/Importing Results from Researchers

FAQ: Why aren’t results being imported from a researcher who said they were delivered to theLinXml.com web service or that we dropped off in the FRS\LINXML\IMPORT folder formanual importing?Check the following:1. Make sure that you have the researcher properly configured for LinXml delivery (see Section

III)2. Read Section VII to make sure that you understand how XML requests and results are

imported through LinXml3. Automation Server:



??:04:00, etc.), one of the “LinXml Processing” messages is displayed4. If you have a researcher configured for interfacing through the LinXml.com web service:

a. Make sure that you have the “Method of Transmission for Research Lists” set to “LinXml(Web Service)” - see Section III


c. Have you checked the “View Listing of Site Identifier Authentication Registrations” option(see Section X) to ensure that your researcher was successfully registered with theLinXml.com Web Service?

d. Are your monthly, semi-monthly or annual gateway fees paid and up-to-date?5. Have you checked the “View Listing of XML Request and Result Batches Loaded” option (see

Section X) to determine for sure whether or not the XML results file has been imported byyour Automation Server?

6. Have you checked the “View Listing of XML Request and Result Import Errors” option (seeSection X) to ensure that your Automation Server hasn’t encountered any errors whileimporting the results?NOTE: If errors are found here, see topic E - “XML Import File Problems” below for details onhow to troubleshoot this problem

7. If you have a researcher configured for manual delivery of their XML files, then search thisPDF document for the word “manual” to fully understand where to place the researcher’s XMLimport files for the Automation Server to retrieve them

8. If your researcher submitted the results to the LinXml.com web service, did they receive aconfirmation and “receipt” that their results were successfully received at the web service?

E. XML Import File Problems

If you encounter problems with the importing of any XML files from your non-FRS clients or researchers,details about these problems can be identified by looking in the “View Listing of XML Request and ResultImport Errors” option in the LinXml Control Center (see Section X). Since support and consulting for theLinXml module requires extra costs to you, we have provided the following guidelines to help you, yourIT staff or your consultants with diagnosing any issues with your non-FRS client’s or researcher’s invalidor malformed XML files:

1. Begin by viewing the details of the error in the “Listing of XML Request and Result Import Errors”. The“Error Message” description there will explain what problem was encountered when trying to importthe XML file.

If the error refers to an XML “parse” or “DOM” error, then this indicates that the XML file was notcreated correctly to match 1) general XML required standards or 2) the LinXml Background Checkingstandards or schema. This error message should provide a lot of detail to point you to the source ofthe problem, but if the XML file is totally unprocessable, then the error message may be vague.

Report this error back to the client or researcher who sent the XML file so that they can refer to theLinXml Specifications documents that you sent them to research and resolve their problems.

NOTE: If you have a client set up for “Email Confirmations”, then they will automatically receive anemail with this specific error message. This email will be sent at the time that the XML importerror was encountered, and you can look in your FRS Fax Server Log to identify exactly whenthis email was sent to your client, and if it was sent from FRS successfully.

2. If the issue can not be resolved from the “Listing of XML Request and Result Import Errors” and theincluded error message details, then you may need to look at the XML file yourself or send it back tothe client or researcher who sent it for them to investigate it.

The name of the invalid XML file will be listed in the “File Name” column in the listing. If you receivedthe file manually and dropped it into the FRS\LINXML\IMPORT folder, then you will now find it in the\SAVE folder under FRS\LINXML\IMPORT\. If the XML file came through the LinXml web service,then you will find it in the FRS\LINXML\WSIMPORT\SAVE\ folder. These XML files will be retainedin these SAVE\ folders for 30 days after the attempted import, then the Automation Server will deleteit.

You can compare the XML file to the specs in the LinXml Specifications Document and the samplesin Appendix A-C to begin your investigation, if you are researching this yourself. You can also openthis XML file with Internet Explorer (IE), and if it is simply a malformed or invalid XML file (disregarding

the requirements of the LinXml specification), then IE may display an error message for you to reportback to your client or researcher. You can also purchase (or download an evaluation version) of aprogram called XMLSpy at www.xmlspy.com which is a tool that may be useful in evaluating a problemwith an XML file.

NOTE: After exhausting all of the resources provided in this section and this entire user guide, if youand your IT staff or consultants, or the programmers who created these invalid XML files cannot resolve this problem, you can submit a Work Order to us to have one of our senior-leveltechnicians assist you with the problems. For instructions on submitting a Work Order to us,turn to Section IV - Interfacing with your FRS and Non-FRS Clients and Researchers in thisuser guide.

F. LinXml.com Web Service Interfacing Problems

If your non-FRS clients or researchers are reporting problems writing their interfaces to the LinXml.comweb service, then suggest the following:

1. Have they looked at the code samples in Chapter 3 of the LinXml Specifications Document?2. Have they tried the testing scenarios provided for them in Chapter 3 of the LinXml Specifications

Document?3. Have they looked at the listing of “Status Codes and Error Messages” provided to them in Chapter 3

of the LinXml Specifications Document?4. Suggest that they make sure they are sending an XML “string” to the web service in their program and

are not trying to send an XML “file”5. Suggest that they make sure that a firewall their system’s location is not preventing them from

interfacing to the LinXml.com web service

NOTE: After exhausting all of the resources provided in this section and this entire user guide, if youand your IT staff or consultants, or the programmers of your clients or researchers are stillhaving problems interfacing to the LinXml.com web service, you can submit a Work Order tous to have one of our senior-level technicians assist you with the problem. For instructionson submitting a Work Order to us, turn to Section IV - Interfacing with your FRS and Non-FRSClients and Researchers in this user guide.

http://www.xmlspy.com

Appendix A:Configuring FTP and Virtual Directories for the Delivery of “Web Link” PDF or TXT Results

When you select either the PDF or TXT Link method for LinXml results delivery, then twoadditional steps must be carried out to set up your systems to accommodate this delivery method.These steps are:1. Configure the FTP settings for each client set with the “PDF Link” method of results delivery2. Set up the virtual directories at your web site for the Automation Server to deliver these PDF

results and provide the security and permissions for your clients to be able to retrieve them

These two topics are covered in this appendix.

1. Configuring the FTP Settings for PDF Results File Delivery to your Web Site

For each client configured for PDF Link results, you will need to configure their LinXml setup as follows.

ì Select the Web Link for PDF (or TXT) in the “Returned Results Format” setting

í Click on this button to “Configure FTP Info” (this option is detailed below)

î Set the exact path of the folder at your web site where your clients will be directed in their XML file tothe “link” for their results.Note: This path must be coordinated with the FTP settings configured below

Configure FTP Info:When you click on the “Configure FTP Info” button, a screen similar to the following is displayed:< The “FTP Server Address” will be the

same for each of your clients as you willonly need to configure one FTP locationat your web site to cover all of your clients

< The “FTP Target Directory” will be aunique folder within the “FTP ServerAddress” location for each of your clients

< You will need to configure just one FTPdrop-off location at the FTP Server Address“Root”, therefore only one “User ID” and“Password” to that location is needed toprovide access for the Automation Server todeliver these reports for any of your clients.Enter this same User ID and Password foreach of your clients here.

< The FTP Access Port should be set to the proper value to allow access from your Automation Server for FTP.Port “21" is the standard for FTP, but if your network has a firewall, this port value may need to be adjusted.

2. Setting Up Virtual Directories at Your Web Site for the Delivery of PDF Results Files

On the computer where your FRS Website is Hosted under Internet Information Services (IIS), VirtualDirectories can be set up for the drop-off and access for XML results created in FRS. Unlike regular websitefolders, these folders don’t have to be contained within the main website at all. They can be set up in acompletely different folder or drive letter, but all will have to be contained in a single main folder.

Once the location of the Folders has been decided, specific folders will need to be set up for each LinXmlclient. If each of the clients will have multiple users, either now or in the future, that will need access to thesedirectories, then you should create a “Group” for each of the folders. Then users can be added or removedfrom the groups as necessary without having to add and delete individual users from each of the VirtualDirectory Folders. Also, as clients are added, additional groups and folders can be added as well.

To add Groups, right click on “My Computer” and select “Manage” from the drop-down menu.

When the “Computer Management” console window comes up, click on the “+” in front of the folder on the leftcalled “Local Users and Groups”. Right click on “Groups” and in the drop-down window choose “New Group”.

On the “New Group” creation window, type in the Name of the Group and a description that clearly describesthe specific company that is referenced by the group and folder to help avoid confusion in the future whenadding users to the group. (Group users could be selected now, but it would be best to wait to add the userslast after setting up all of the groups and virtual directories and assigning the appropriate group permissionsto the company folders.)

TIP: To Simplify things, you may want to decide on a naming convention for the folders and groups, suchas the Client Name or Client Code for example. Just be consistent to avoid confusion!

After Adding the specific company groups into your WindowsManagement Console and creating the folders that each ofthe groups will represent, the next step will be to assign theappropriate permissions. To do this, start with one of theCompany Folders in the Virtual Directory Drop off locationand right click on the folder then click “properties” and selectthe “Security” tab.

Make sure that the “Everyone” group or the “Users” group isnot included in the window under “Group or user names:”.This is to keep the wrong users from viewing results fromother companies.

In order to remove groups that shouldn’t be here, you mustfirst click on the “Advanced” button and un-check the boxbeside “Inherit from the Parent the Permission Entries....”. Inthe window that pops up, choose “Copy” to keep the currentpermissions set. Then Click “OK” to go back to the SecurityTab.NOTE: These windows just described are illustrated on the next page

Once back at the Company folder properties page, click “Add” under the “Group or user names:” window. Atthe “Select Users or Groups” window click on the “Advanced” button. When the “Select Users or Groups”window expands, click on the “Find Now” button to populate your users and groups list. From this list, choosethe Group representing the company that also is representing the folder you are currently working on.

Select this Group and then click “OK”twice.

NOTE: Make sure you have chosenthe correct group to assure thatresults get to the right client!

Now with the Company folder Properties window in front,select the Company Group that was just added under the“Group or other users:” window and click on “Modify” in thePermissions window below. This will put check boxes in allof the boxes except for “Full Control”. Then select the “OK”button to close this box and you will have added theappropriate permissions for this particular folder. Repeatthe previous steps for adding the Specific EstablishedCompany Groups to each of the specific related FolderPermissions

Next, to add users to your groups, first add the users into your system. Right click on “My Computer” andselect “Manage” from the menu. When the “Computer Management” window comes up, click on the “+” in frontof the folder on the left called “Local Users and Groups”. Right click on “Users” and in the drop down windowchoose “New User”.

On the “New User” creation window, type in the Name of the User and a description that clearly describes thespecific company that this user belongs to. By adding this to the description, you will help avoid confusion inthe future when making sure that the user is assigned to the correct group. Then, create a password and typeit again to confirm it. Finally un-check the box that says “User must change password at next logon” and thencheck the box that says “Password never expires” because a user in this case will not have a way to changetheir own password.

Repeat the previous steps to add your users into the system. After you have finished adding users, you canadd the users to the appropriate groups as follows. Right click on a user that you want to add to a specificgroup. Select “Properties” from the drop-down menu.

The next window to display will be the properties window for the highlighted user. Click on the “Member of “tab of this window. When the next window is displayed, click on the “Add” button.

When the “Select Groups” window displays, click on the “Advanced” button, then “Find Now”.

On the extended “Select Groups” window,first select the appropriate group and thenclick “OK”.

Once the user has been added into the appropriate group, they will have the same access permissions to thegroup folder as are assigned to the group.

NOTE: When assigning users to groups, make sure that you are assigning the users to the correct group, asyou don’t want the wrong users getting access to another client’s results or not getting access to their ownresults!

After creating all of the appropriate companyfolders, groups and users in ComputerManagement Console, and assigning theappropriate permissions to the created folders, itis now time to go into IIS (Microsoft’s InternetInformation Services management console) toset up your virtual directories under your website.You can access the IIS console either by goingthrough the “Control Panel” or by going through“Start”, “Administrative Tools”, and selecting“Internet Information Services”, depending onhow your start menu may be customized.

Once in the IIS manager, click on the “+” in front of the name of the computer your IIS is on to reveal the WebSites and FTP folders. Then click on the “+” in front of the Web Sites folder and select your main Web Site.

Then, right-click on the website and choose “New” & “Virtual Directory”

This Brings up the “Virtual Directory Creation Wizard”. Click “Next”.

On the “Virtual Directory Alias” window, you will key the name you want your client to type in order to accesstheir files. To avoid confusion, this name should be entered exactly the same as the specific folder nameassigned to each of your company directories. NOTE: You will be setting up a virtual directory in IIS for each of these company directories. Once set up,when the web user is accessing these directories from the web, they will type your website and a “/” followedby their virtual directory name. For example users for the client ABC_Company would access their site bytyping “www.mysite.com/ABC_Company.

After entering the namefor the virtual directory,click “Next”.

You will then browse to the directory where your company folders are located and select the specific folderthat represents the virtual directory you have just named. Then click “OK”

On the “Access Permissions Screen, make sure that you retain the default permissions of “Read” and “RunScripts such as ASP” selected, then click “Next” and then click “Finish”. You will then repeat the same stepsin IIS for creating Virtual Directories for each of the company folders you have created.

Once you have created your Virtual Directories in IIS, you will need to create a Master FTP site for your MainVirtual Directory Folder that contains all of the other company folders you have already set up.

To achieve this, within theI n t er n e t I n f o rma t io nServices window, right-clickon “FTP Sites”, select“New”, “FTP Site” and the“FTP Site Creation Wizard”will display.

Click “Next” on the “FTP Site Creation Wizard” and enter a name that describes this FTP site, such as“Screening_Results” for example.

Click “Next” and select the appropriate IP address to associate with this FTP site. This will be the IP addressthat will be used by FRS over the internet for transmitting the PDF results into the virtual directories and mustmatch the IP address configured for each client’s LinXml FTP settings (see the “Configure FTP Settings” topicat the beginning of this appendix).

After selecting the appropriate IP address on your Server, click “Next”. In Windows 2003 Server, you will seethe following options.

These options are new in setting up FTP under Windows 2003 Server. For this specific FTP site you shouldchoose the first option of “Do not isolate users” if you are presented with this isolation choice. Click “Next”.

Key in the path to the LinXML parent directory or browse to it and then click next.

Be sure to click on “Write” permissions because the results will be written to the virtual directories through FTP.Then Click “Next” and “Finish” to complete the setup of the FTP access for the virtual directories

At this point you have createdthe directory structure andgroups, assigned users andpermissions to the groups andcreated the virtual directoriesand an FTP site in IIS forposting results to your virtualdirectories.