Failover Scheduling Engine Installation

%3cdiv style%3d%22float%3a left%3b line-height%3a 14px%3bfont-family%3a Verdana%3b font-size%3a 10pt%3b%22%3eHere are the basic instructions for installing a JAMS Failover server%3a%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%3col%3e
    %3cli%3eInstall the first Primary JAMS Scheduler.%3c/li%3e
    %3cli%3eIf you want redundant databases%2c configure a SQL Server mirror of the JAMS Database.%3c/li%3e
    %3cli%3eStop the JAMS Scheduler service on the Primary Engine.%3c/li%3e
    %3cli%3eInstall the JAMS Scheduler on the second node%3b when prompted for the database server%2c specify the same SQL Server%2c Instance%2c and database name as the first server.%26nbsp%3b You will receive a dialog that says “Database already exists.” Click “Use Database.”%3c/li%3e
    %3cli%3e%3cimg alt%3d%22%22 src%3d%22http%3a//www.jamssupport.com/Uploads/Images/Installation_DatabaseExists.bmp%22 /%3e%3c/li%3e
    %3cli%3eStop the JAMS Scheduler service on the second machine.%3c/li%3e
    %3cli%3eCreate%5cEdit the Failover.config file in the X%3a%5cProgram Files%5cMVPSI%5cJAMS%5cScheduler directory.%3c/li%3e
    %3cli%3eCopy the Failover.config to both machines. Failover.config should be identical on both machines.%3c/li%3e
    %3cli%3eStart the JAMS Scheduler service on both machines.%3c/li%3e
%3c/ol%3e
Here is a sample Failover.config%3a%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%26lt%3bFailoverConfig%26gt%3b%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%26nbsp%3b%26nbsp%3b%26nbsp%3b%26nbsp%3b%26lt%3bPrimary%26gt%3bServer1%26lt%3b/Primary%26gt%3b%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%26nbsp%3b%26nbsp%3b%26nbsp%3b%26nbsp%3b%26lt%3bSecondary%26gt%3bServer2%26lt%3b/Secondary%26gt%3b%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%26nbsp%3b%26nbsp%3b%26nbsp%3b%26nbsp%3b%26lt%3bPort%26gt%3b4773%26lt%3b/Port%26gt%3b%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%26nbsp%3b%26nbsp%3b%26nbsp%3b %26lt%3bInterval%26gt%3b60%26lt%3b/Interval%26gt%3b%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%26lt%3b/FailoverConfig%26gt%3b%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
It is also necessary to add a user to the JAMS database to allow the Secondary engine to connect. This can be done by running the following SQL statements on the JAMS database.%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%28Note%3a You will need to replace the login name with your machine name.%29%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%3cp%3eexec sp_grantlogin @loginame%3d%27YourDomain%5cYourMachineName%24%27%3c/p%3e
%3cp%3eexec sp_grantdbaccess @loginame%3d%27YourDomain%5cYourMachineName%24%27%2c @name_in_db%3d%27JAMSMachine%3cspan style%3d%22color%3a %231f497d%3b%22%3e2%3c/span%3e%27%3c/p%3e
%3cp%3eexec sp_addrolemember @rolename%3d%27JAMSApp%27%2c @membername%3d%27JAMSMachine%3cspan style%3d%22color%3a %231f497d%3b%22%3e2%3c/span%3e%27%3c/p%3e
%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e
%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3e%3cspan style%3d%22font-size%3a 4pt%3b%22%3e%3cp%3e%3c/p%3e%3c/span%3eMVP Systems - Support%3cbr /%3ehttp%3a//www.jamssupport.com/KnowledgebaseArticle50054.aspx%3c/div%3e