[toc]
The Community Server package contains several folders, including one named JobService. The JobService folder contains all the Job Service files needed. This folder can be copied to any location desired, for example a new Telligent folder at Program Files (x86), or to a separate server if the community size warrants.
Install a single instance of the Job Service
To install the Job Service, run the install.bat file located in the folder. (Note: If you had Job Scheduler installed from a previous version of the product, you will need to Remove the Telligent Job Scheduler or Zimbra Job Service before installing this release's Job Service.)
You will need to update several files in the jobservice folder:
- connectionstrings.config (to point back to the site)
- communityserver_override.config if your site uses one (with an override to point to the CFS).
- Any other customizations made in the site’s web folder, such as changes to email templates in \Languages\<language\emails, packages.config, ldap.config, or web.config. As a rule of thumb, any changes made to the web folder should also be made in the JobService folder to ensure consistent operation.
In addition, a communityserver_override.config entry should be added to update the filestorage location. By default, it is stored in the Web\filestorage directory so the path to it needs to be explicitly set in the Job Service. The following override will update the path.
<Override xpath="/CommunityServer/CentralizedFileStorage/fileStoreGroup[@name='default']" mode="change" name="basePath" value="C:\Path\To\FileStorage\Directory" />
Next steps for a single instance
Finally, the Job Service must be started and specific jobs possibly enabled or scheduled:
- Refer to Start or stop the Telligent Job Service to start it.
- To enable specific job plugins, refer to Enable, schedule, or disable specific jobs.
- To adjust the schedule of a specific job, refer to schedule, or disable specific jobs.
Install multiple instances of the Job Service
By default, the service name is “Telligent Job Service.” Windows requires that service names be unique on the system. If multiple Job Services are needed on one machine, the name will have to be changed for other Job Service.
To rename the extra instances:
- Copy the JobService folder to a second location. Give the copied folder a name that makes it easy to identify.
- Update the configuration files as necessary.
- Open jobs.config file in Notepad.
- Change the ServiceName value to the desired name.
- Run install.bat to install the second service.
The re-installation process can be performed multiple times to add any number of Job Services.
The Next Steps section above also applies to each of the created instances.