| Contents | Support |
|
||
|
| Previous | Contents |
This chapter describes how to install the JAMS Scheduler on
Windows Server.
2.1 Prerequisites
The JAMS Scheduler relies on some optional components of
Microsoft Windows Server. These optional components must be installed
before you install the JAMS Scheduler.
2.1.1 Message Queuing Services
JAMS uses Message Queuing Services to provide reliable message transfers between services.
Message Queuing Services is included with Microsoft Windows Server but,
it is not installed by default.
2.1.1.1 Windows Server 2003
To see if Message Queuing Services is installed or to install it, follow these steps:
To see if Message Queuing Services is installed or to install it, follow these steps:
JAMS is built on top the the Windows .NET Framework 1.1. The
.NET Framework 1.1 is installed as part of the operating system with
Windows Server 2003. If you are using Windows 2000 or Windows XP, go to
http://windowsupdate.microsoft.com/ to install the latest patches and
the .NET Framework.
2.1.3 SQL Server or MSDE
JAMS uses Microsoft SQL Server or MSDE for data storage. MSDE is a limited version of SQL Server. We reccommend that you install the JAMS Scheduler on the same machine that will run SQL Server but, that is not a requirement.
If you do not have SQL Server, you can download MSDE at no cost from
http://www.microsoft.com/sql/msde/download/download.asp
2.2 Installing the JAMS Scheduler
The installation generally takes only a few minutes.
Installation of the JAMS Scheduler does not require a reboot.
Installation of the JAMS Scheduler does not replace system DLLs.
The installation will present a number of screens which require a response:
2.2.1.1 SQL Server
Use this field to specify which SQL Server it use for the JAMS
Database. If SQL Server is installed locally, the default will be
"(local)" which is the recommended configuration.
2.2.1.2 Location of JAMS Database Files
The JAMS Database is divided into four functional storage areas. You need to specify a location (device and directory) for each area.
The Primary file contains most of the JAMS tables. Much of this data is fairly static, once it's defined, it may not change very much.
The Volatile file contains tables are are updated frequently. These tables have records inserted and deleted each time a job executes.
The History file contains the JAMS History table. This table could get quite large if you run a large number of jobs or keep history for a long time.
This directory is where database log files will be kept. If possible,
this should be on a different physical device than the rest of the
database files. This will provide the most protection from a device
failure.
2.2.1.3 Location of JAMS Files
JAMS may need to create a temporary command procedure when it runs a job. This is the directory where that command procedure will be kept.
When a job runs, JAMS creates a log file of the run. This is
the default location for these logs. You can override this location in
a job's definition.
2.3 Getting Started
After installing the JAMS Scheduler, you must install the
JAMS Client on at least one machine. You can install the
Client on the same machine as the Scheduler.
2.3.1 Define Usernames in JAMS
In order to run a job under Windows, the JAMS Scheduler must
supply a valid username and password. You must use either the JAMS SET
USERNAME command or the Management->Usernames menu option to define
the username/password combinations. You can also specify an access
control list (ACL) which is used to determine who can submit jobs under
the username.
2.3.2 Grant "Log on as a batch job" to NT accounts or groups
JAMS jobs run as batch processes under Windows. The Windows
account that the batch job will run as must have the "Log on as a
batch job" user right. You can grant this right to specific
accounts or, grant the right to a group and make the accounts members
of the group.
2.3.2.1 Granting rights under Windows 2000
Under Windows 2000, you can grant the "Log on as a batch job" right at the domain level or local level.
To manage rights under Windows 2000 you use the "Local Security
Policy" or "Domain Security Policy" Administrator
Utilities.
2.3.2.2 Granting rights under Windows NT V4.0
Under Windows NT V4.0, you must grant the "Log on as a batch job" right on each machine which will be running the JAMS Agent. You only have to grant the right on one domain controller and it will propagate to the other domain controllers in the domain. It will not propagate to member servers or workstations, you must grant the right on each of those machines.
You can use User Manager for Domains to grant the right for both the domain and individual machines. Select the User Rights option from the Policy menu. You must check the "Show Advanced User Rights" check box to display the "Log on as a batch job" user right.
To manage user rights on member servers and workstations, select the
Select Domain... option from the User
menu. Enter "\\machinename" in the Domain field and click Ok.
You will then be connected to the specified machine and you will be
able to manage the user rights on that machine.
2.3.2.3 Granting rights with the NTRights.exe Utility
The NTRights.exe utility is included in the Windows NT Server 4.0 Resource Kit supplement 3 and in the Windows 2000 Resource Kit. If you have this utility you can grant the "Log on as a batch job" right with a command like this:
ntrights +r SeBatchLogonRight -u user_or_group -m \\computername |
Note that the rights name is case sensitive.
2.4 Error Conditions
If the installation procedure fails for any reason, a message is displayed and the installation is not performed.
If you cannot determine the cause of the problem, please contact technical support.
If you have questions about JAMS please feel free to call JAMS technical support at (866) 259-5267. Technical support is available around the clock, 24 hours a day, 7 days a week. The mailing address is:
| Previous | Next | Contents |
 | Copyright © 2004, MVP Systems, Inc. All rights reserved. |