- JAMS 7.0 or higher
- Windows Server 2012 or higher
- .NET 4.6
- IIS 8 or 8.5
- Edge, Chrome, or Firefox recommended for the best experience
Begin by installing the Microsoft Web Deployment Tool with Typical installation options.
Next, enable the Web Server IIS Role through the Server Configuration screen.
Ensure the following components are enabled within Application Development:
Download the JAMS Installer. During the Installation, ensure the "JAMS Web Client" component is selected.
In the Web Client Details section, select the web site where the JAMS Web Client should be installed.
Once the JAMS Installation is complete, open the Common.Config file for the Web Client, located at C:\Program Files\MVPSI\JAMS\WebClient\ by default.
Edit the Common.Config file as necessary for the given environment:
- Verify that the the connection string value matches the desired server.
- If the JAMS Site is installed within a Domain, set the ContextType value to "Domain" and ContextName value to the domain itself. (In the image below, the domain is "JAMS")
- If the JAMS Site is not installed within a domain, set the ContextType value to "Machine" and ContextName value to the name of the machine.
- If the JAMS REST API/Web Client is installed on a different server than the JAMS Scheduler Server, set the SchedulerName value and SchedulerPort value accordingly.
If the scheduler is not on another server, setting values for SchedulerName and SchedulerPort will cause issues.
- If the JAMS REST API/Web Client is installed on a different server than the JAMS Scheduler Server AND a failover is not configured, the key
<add key="EnableRemoteAccess" value="true" />must be added to the Common.config file on the JAMS Server, located by default at
C:\Program Files\MVPSI\JAMS\Scheduler\Common.config. This will open port 4773, allowing the web client to communicate with the scheduler. In an environment with a Failover configured, port 4773 will already be open.
After configuring the JAMS Server common.config file, restart the JAMS Server service.
- If the JAMS REST API/Web Client is installed on a different server than the JAMS Scheduler Server, the JAMS fat client must be installed on the web server. The client can be downloaded here. The Web Server and Scheduler Server must be running the same version of the fat client.
- If the JAMS REST API/Web Client is installed on a different server than the JAMS Scheduler Server, users must grant the Web Server full permissions to the jamsrequests Queue on the Scheduler Server. Follow our article to grant access to the MSMQ, using the naming format MyWebServer$.
App Pool Settings
Add the user running the App Pool to the JAMSApp Role on the JAMS Database created during the initial installation. This will give proper permissions to the JAMS Database.
NOTE: It may be necessary to give the DefaultAppPool the JAMSApp Role in SQL.
Users are recommended to run DefaultAppPool under LocalSystem for local machine installations.
For domain installations, it may be necessary to run the DefaultAppPool as NetworkService.
If your JAMS services are running as a domain account, it is also recommended to run the DefaultAppPool as that same domain account.
Restart IIS services.
The REST API includes built-in documentation displaying the endpoints and corresponding Headers that can be passed. There are two variants of Documentation that can be accessed based upon your preference: