CL Connect is a customized solution. There are several ways to accomplish this, and these steps below will outline how CampusLogic prefers to do this.
Copy the existing CL Connect:
1. Setup the CL Connect and get it to functioning state.
2. Copy the CL-Connect-master folder and paste it into the same directory (default: C:\inetpub\wwwroot).
3. Rename the CL-Connect-master - Copy folder to match the purpose for this instance.
Example: CL-Connect-master-production
NOTE: The copied folder does not always transfer permissions so make sure that the IIS User has Full Control for the new instance folder.
Rename the database and database log files:
4. Rename the .mdf and .ldf files in the new CL Connect instance App_Data folder to reflect the new name that will be used for this additional instance.
Example: CampusLogic-prod.mdf, CampusLogic-prod_log.ldf
5. Edit the new instance web.config file in the parent folder for the new instance.
NOTE: Depending on the version of CL Connect that is installed will determine if there will be 2 lines or 3 lines of code to change in the web.config file.
3.13.4 - older versions have 3 lines of code to change for the database values.
3.13.5 - current versions have 2 lines of code to change for the database values.
6. Do a search for "CampusLogic.mdf" and update the name to what the new name is for the .mdf file in the App_Data folder. There will be 2 or 3 CampusLogic.mdf entries to update, depending on the version of CL Connect installed.
Example: CampusLogic-prod.mdf
7. Next do a search for "Catalog=CampusLogic" and there will entries equal to the previous .mdf search that have to be updated to the new name only. Do not include the .mdf extension for these catalog entries.
Example: Catalog=CampusLogic-prod
8. After the edits have been completed, save the web.config file and close it.
IIS Configure:
9. Open IIS to create an Application Pool for the additional instance of CL Connect.
10. Select Application Pools under the Connections section on the left, and click Add Application Pool... under the Actions menu on the right.
Add Application Pool:
11. Name the Application Pool to coincide with the new instance of CL Connect and click on the OK button.
12. Select the new application pool and click on the Advanced Settings... under the Actions menu on the right.
App Pool Advanced Settings:
13. Update the following selections and click on the OK button.
14. Under the Connections section on the left, select on Sites, and then click Add Website... under the Actions menu on the right.
Add Website:
Site Name: Name the website for its purpose.
INFO: The application pool will start to auto-populate in relation to the site name. If the site name is different than the new application pool that was just created then it will have to be selected with the Select... button.
Content Directory: Fill out the physical path for the new folder or select it from the ... button.
Binding: Change the local port to be different than the default.
15. Click on the OK button.
16. Make sure the new website is selected on the left and click on Browse *.port (https) under the Actions menu on the right.
17. The CL Connect landing page should be the result.
18. Now the new instance of CL Connect needs to be configured properly and the IIS bindings setup for https communication and added to the Keep-Alive Scheduled Task.
