LabLynx KB:JOB Manager install
| This is an article specific to the Category:LabLynx knowledge base. Its context outside of LabLynx, Inc may not be apparent, thus why it appears inside the LabLynx KB namespace.
LabLynx JOB Manager installation and setup
If you already have the JOB Manager installed and running, please close the program. This will allow the install to copy over it with the latest version.
1. Place the LABLynx_Job_Install.zip file on the server. Required components on the server include:
- Windows Script Host v5.6 or higher
- Microsoft Office 2000 (For Access reporting & Excel reporting)
- MDAC 2.6
2. Unzip the LABLynx_Job_Install.zip file to a directory of your choosing.
3. Right click on the LABLYNX_JOBMANAGER_INSTALL.BAT file.
4. Choose Edit from the drop down.
5. When the file opens update the values of these three variables:
- FromPath: Replace the “??” with the path to the directory where the files were unzipped.
- ToPath: Replace this path with one of your choosing. You may already have a LABLYNX directory on this server. If so, you should point it to the parent directory of the LABLYNX folder.
- WinntPath: Replace this path with the one to the Windows WINNT folder.
6. Save the BAT file after you have made your changes.
7. Double click the BAT file to run it. This will create a Job_Manager_Components directory under the LABLYNX folder in the path you defined above.
8. Check this directory to make sure it loaded the following files:
- a ???_Report_Mod.mdb file for Access reports
9. If you don’t already have a Report_Mod.mdb file, copy this one. Rename it to your choosing. This will now become your main Access reporting database. Every time the install is run the original .mdb file is copied over. If you don’t rename yours, you will lose any modifications to the reports you have made.
10. If you haven’t installed the JOB Manager tools before, you will need to create a shortcut to the LABLynxJobQueManager.exe in the All Users startup folder.
11. Find the LABLynxJobQueManager.exe in the newly created Job_Manager_Components Folder. Drag it to the All Users\Start Menu\Programs\Startup folder and create a shortcut.
12. If you haven’t created a DSN on the Server to point to the LabLynx database, you will need to do so now. To do this:
- Go to Control Panel\Administrative Tools\Data Source (ODBC).
- Choose the System DSN tab.
- Click Add.
- If you have a SQL Server system, choose SQL Server from the bottom of the list. If you have an Oracle system, choose Microsoft ODBC for Oracle or the Native Oracle driver. Click Finish.
- Name the DSN and fill in the appropriate login and server info. Test the DSN if possible.
13. Once the DSN has been created, you will now need to point the LABLynxJobQueManager.exe shortcut to the database. Right click on the LABLynxJobQueManager.exe shortcut in the startup folder and choose Properties. In the target text box after the reference to the LABLynxJobQueManager.exe type a space then the reference to the DSN already made. It should look something like this:
"C:\Program Files\LABLYNX\Job_Manager_Components\LABLynxJobQueManager.exe" DSN=?DSN?;UID=?USERID?;PWD=?PASSWORD?,S
In this example replace:
- ?DSN? with your DSN name
- ?USERID? with your DB login name
- ?PASSWORD? with your DB password
- The ",S" in the string refers to the database type. If you have an Oracle system use "O". If you have a SQL Server system use "S".
14. Now when the server is started it will immediately fire off the LABLynxJobQueManager.exe. Start polling the queue and firing off agents.
You have now finished the setup process for the Job Manager system.
Other issues to note
1. The path to the job agents is stored in the LabLynx database under client specific settings. Make sure this path matches the path to the Job_Manager_Components folder. Example: C:\Program Files\LABLYNX\Job_Manager_Components\
2. In the job types pick list the names of the agents should match the names of each job types' command text. The job agent path and command text are used by the Job Queue Manager to call the agents.
3. E-mail job templates must have a valid e-mail server name as one of the attributes. You may need to change the given templates to match your e-mail server name.
4. If you are using the Access report agent, Access must be installed on the server where the JOB Manager and Access report agent reside.
5. Access report job templates need to have a valid path to your Access .mdb file as one of the required attributes. Example: C:\Program Files\LABLYNX\Job_Manager_Components\YOUR_ACCESS.mdb Note: This file should be the one copied and saved in the above install.
6. If you want the latest module level reports, open your saved Access database. Open the one saved in the Job_Manager_Components folder on install. You can drag new reports to your Access reports and save them. Follow the next process to link in the appropriate tables for the reports.
7. If you are running Access reports you will need to create table links from the LabLynx database to the Access database. To do so follow these steps:
- Open Access on the server.
- Under the Tables section right click in the white area and choose Link Tables.
- Choose ODBC Databases() from the Files of Type drop down box.
- Click the Machine Data Source tab.
- Choose the DSN you created earlier from the list.
- Log into the system and check the Save Password box. Failure to do so will cause the LABLynxAccessRptAgent.exe to error out and fail.
- Link the specified table name to the Access database using the ODBC DSN mentioned above.
- Click OK then OK again.
- Open the Reports area in Access.
- Choose the specified report and open it in design view.
- In the View Menu item choose Properties.
- Choose the Data tab.
- In the Record Source drop down box choose the table you just linked to.
- Close the dialog box and hit Save.
- In the View Menu item choose Print Preview.
- In the File Menu item choose Print.
- Select the printer you want this report to always print to. Print the report (one page if you like) and save. This assures the report is saved with the correct printer.
- You have completed the report set up. The LABLynxAccessRptAgent.exe will now be able to print this report. You can close Access.
8. As the Job Manager system runs, errors may occur. They are logged in the "Event Log" table, accessible from the "Event Log" screen. Window events are also created in the event of an error.
9. Security settings on the LABLYNX folder may need to be adjusted to get the job agents to fire correctly.