Collaboration enables the ability to "assign" schedules to other CRD machines. Though the management and editing of the schedules will occur on the primary CRD machine, processing and running of the schedule will occur on the collaborator (the other CRD installation).
With Collaboration, resource intensive schedules can be processed on more powerful servers. Also, numerous schedules can be spread out across an array of CRD machines to reduce the overall load and run schedules more efficiently.
Note: CRD servers/instances that are set up as collaborators only run schedules delegated to them by the Primary Server. Collaborators DO NOT process their own local schedules.
Combined with Multi-threading, each CRD Collaborator will have up to 4 threads. Therefore quadrupling the number of concurrent schedules you can run simultaneously with every collaborator added.
Note: In the example picture shown above, there would be 16 available threads.
This feature best fits organizations that desire enterprise-wide reporting when it is necessary that thousands of reports be distributed.
The remainder of this guide will walk you through setting up collaboration with another CRD server. It is imperative that you follow the steps below carefully. Failure to do so may result in an unsuccessful setup.
Any issues that arise from setting up a collaboration are outside the scope of normal technical support. This is because many of the steps required for collaboration to work successfully are modifications done outside of CRD. Therefore, it is highly recommended that you allow one of our internal Professional Services consultants to set up the collaboration for you. This will not only ensure a smooth set up but minimal to no downtime, as well as minimal resources/time spent completing the setup. If you would like to inquire about Professional Services, please contact our Customer Relations department at 1-888-781-8966, Option 2.
- More than one CRD Installation is required in order to properly set up collaboration. If you currently only have one installation of CRD, please see the following links for more information regarding installing CRD on another server:
- Each CRD instance must be accessible through your internal network.
- Each remote server with CRD installed must have the correct email, database, and system settings in order to ensure proper processing and delivery of the reports/schedules. Each collaborator's settings should match the main scheduler.
- The Primary Machine's database must be migrated to your own SQL Server instance (See Migrate to SQL Server / ODBC ). Additionally, each collaborator must be connected to the primary scheduler's database (See Switch - To ODBC / Local SQL).
Setting up Collaboration
To set up a collaboration between the primary machine/server and a secondary machine/server, perform the following:
On the Primary Server
1. Navigate to the System tab in CRD.
2. Click Collaboration from the ribbon menu.
3. Click the gray Off button next to Enable server Collaboration to turn Collaboration On.
4. Click the Add button to the right of the Collaborators popup. This will bring up a window that will prompt you to select the CRD configuration file on the remote machine.
5. Browse through the network and select the CRD Collaborator machine.
6. CRD will automatically display two folders for CRD: ChristianSteven and crdconfigshare. Double-click the crdconfigshare folder.
7. From the list of files that display, select the crdlive.config file.
8. Please read the information on the next pop-up carefully. If you would still like to continue setting up collaboration, click OK.
9. On the authentication window that displays, enter the appropriate Windows credentials to authenticate to the collaborator machine. Then, click OK.
Note: Ensure that the user is a local administrator with full read/write access to the collaborator.
10. Once you have authenticated, you may receive a message stating that CRD cannot access the process list on the remote machine. If this is the case, ensure that the remote machine's CRD and Scheduler are closed. Then, click OK and attempt to authenticate again.
11. Once Finished, the new Collaborator will appear on the Collaborators window.
If you would like to add more collaborators, repeat steps 1-11.
On the Collaborating Server
1. Under Options > Scheduler, change the scheduling option to Use NT Service.
Note: ALL collaborators MUST use the NT Service as the Scheduler.
2. Enter the appropriate NT Service Logon Credentials. For more information regarding the NT Service and it's applicable credentials, click here.
Assigning Schedules to other Collaborators
To assign a schedule to a collaborating server, perform the following:
1. On the primary server, right-click the schedule you want the collaborator to run and click Properties.
2. On the Schedule tab, check the box next to Enable this schedule and execute it on. Then, from the drop-down list to the right, select the name of the collaborator this schedule should run on.
3. Click Apply then OK at the bottom of the Schedule Properties window.
The schedule will now execute on the assigned collaborating server.
Removing A Collaborator
To remove a Collaborator from the system, perform the following:
1. On the Collaborator server, under Options > Scheduler, change the scheduling option to No Scheduling Required. For more information regarding the No Scheduling Required option, click here.
2. On the primary server, navigate to the System tab and click Collaboration (as pictured above).
3. From the list of available collaborators, select the one you wish to remove and click the Delete button.
Note: You must click on the name of the collaborator so that it is highlighted prior to clicking Delete. Failure to ensure the server name is highlighted may result in an unsuccessful deletion.
4. On the confirmation message that appears, click OK. This will begin the removal process.
5. On the Authentication window that pops up, enter the appropriate Windows credentials to authenticate to the remote machine. Then, click OK.
The Collaborating server should no longer display under the Collaboration list, and it can now be operated independently of the primary CRD installation.