Updating SQL and server migration - Revision history

Admin: /* School Dinners */

2019-11-29T10:32:15Z

School Dinners

Admin: /* School Dinners */

2019-11-29T10:31:51Z

School Dinners

Admin: /* Migrating the Insight Website / Migrating IIS */

2019-11-29T09:57:09Z

Migrating the Insight Website / Migrating IIS

Admin: /* Migrating the Insight Website / Migrating IIS */

2019-11-29T09:41:40Z

Migrating the Insight Website / Migrating IIS

Admin: /* Migrating the Insight Website / Migrating IIS */

2019-11-29T09:41:25Z

Migrating the Insight Website / Migrating IIS

Admin: /* Migrating the Insight Website / Migrating IIS */

2019-11-29T09:41:04Z

Migrating the Insight Website / Migrating IIS

Admin: /* Migrating the Insight Website / Migrating IIS */

2019-11-29T09:40:49Z

Migrating the Insight Website / Migrating IIS

Admin: /* Migrating the Insight Website / Migrating IIS */

2019-11-29T09:40:14Z

Migrating the Insight Website / Migrating IIS

Admin: /* Migrating the Insight Website / Migrating IIS */

2019-11-29T09:38:25Z

Migrating the Insight Website / Migrating IIS

Admin: /* Installing Insight on the new server */

2019-11-29T09:36:07Z

Installing Insight on the new server

@@ Line 66: / Line 66: @@
 ===School Dinners===
-If your original server was configured to link to a cashless catering system, you can simply copy the relavant INI file from the \bin folder of the old server to its counterpart on the new.  Alternatively to configure the link again from the beginning, please follow the steps on this page: <br>
+If your original server was configured to link to a cashless catering system, you can simply copy the relevant initialisation (INI) file from the \bin folder of the old server to its counterpart on the new.  Alternatively to configure the link again from the beginning, please follow the steps on this page: <br>
 '''[[School dinners]]''' <br> <br>
 [[Category:Technical]]

@@ Line 66: / Line 66: @@
 ===School Dinners===
-If you are using, or plan to use, Insight to display School Dinner information then follow the steps on this page: <br>
+If your original server was configured to link to a cashless catering system, you can simply copy the relavant INI file from the \bin folder of the old server to its counterpart on the new.  Alternatively to configure the link again from the beginning, please follow the steps on this page: <br>
 '''[[School dinners]]''' <br> <br>
 [[Category:Technical]]

@@ Line 24: / Line 24: @@
 #First perform a new installation of Insight on the new IIS server (see the '''[[installation]]''' page for instructions). <br> <br>
 #Make a copy of the _Personalisation folder from the old Insight server. The _Personalisation folder is found in the Insight directory which is usually '''c:\inetpub\wwwroot\INSIGHT\_Personalisation''' Copy this folder into the Insight directory on the new server. <br> <br>
 #Update the local/shared connect.ini files on the new IIS server. The servername and database fields in these files needs to be set to the SQL server instance. The connect.ini files are typically found in '''c:\program files\sims\sims. net\connect.ini''' and '''s:\sims\connect.ini''' <br><br>
 #Re-run the Insight service pack on the new IIS server. On the '''Data tier''' tab, make sure that the '''Connect INI location''' field matches the location for the local connect.ini file on the new IIS server. If you have changed this location go to the '''Commit''' tab and click '''Begin'''. <br> <br>
 #Delete the Insight website from the old IIS server using IIS Manager. <br> <br>
-#If you make sure of the Batch PDF conversion functionality, this will also need to be reconfigured on the new server as per the '''[[Batch_PDF_processes]]''' page <br>
 ===Making Insight externally available===
-At this stage Insight will work using internal addresses such as localhost or the server name in the URL. To make Insight work externally you will need to copy the site bindings and any other IIS rules from the old IIS server. <br> <br>
+At this stage Insight will work using internal addresses such as localhost or the server name in the URL. To make Insight work externally you will need to copy the site bindings and any other IIS rules from the old IIS server. <br> <br>  At this point you should be linking your SSL certificate to the site.  Please see '''<span class="plainlinks">[https://www.tascsoftware.co.uk/wiki/INSIGHT/index.php?title=Configuring_External_Route here]</span>''' for further details. <br><br>
 ===The SIMS Agent process===
-Insight runs a service called SIMSAgent. This collects data from the SIMS database and stores it in the Insight database. It is important for this service to run correctly so that the data in Insight is correct. <br> <br>
+Once you are sure your site is securely available externally, you will probably need to update your SIMS Agent service configuration.
 Use a text editor such as Notepad to open the following file C:\inetpub\wwwroot\INSIGHT\bin\SIMSAgent.exe.config <br>
-There is a hub setting that shows a URL that the service will use to access Insight.
+There is a "hub" setting that shows a URL that the service will use to access Insight.
-Make sure that the URL specified can be reached using a browser on the server. <br>
+Make sure that the URL specified can be reached using a browser on the server.  If not it is unlikely to be the correct address, but it might also be that proxy reconfiguration is required.<br>
-If this is only possible via a proxy - Please ensure that your proxy details are correctly configured within the simsagentexe.config file. <br>
+If connecting to the specified address is only possible via a proxy , please ensure that your proxy details are correctly configured within the simsagent.exe.config file, ensuring that the proxy address is given as a valid URI and any credentials are accurately given. <br>
 <br>
-If you have changed the URL then use services.msc to restart the InsightSIMSAgent process. <br> <br>
+If you have had to make changes to the configuration then use services.msc to restart the InsightSIMSAgent process with the new settings. <br> <br>
 ===Batch PDF Processes===
-If you are using, or plan to use, Insight to batch convert SIMS reports to PDF format then follow the steps on this page: <br>
+If you were previously using, or plan to use, Insight to batch convert SIMS reports to PDF format then you will need to take to install all the necessary components from the original server.  Please follow the steps on this page: <br>
-'''[[Batch PDF processes]]''' <br> <br>
+'''[[Batch PDF processes]]''' <br>
 ===School Dinners===

@@ Line 27: / Line 27: @@
 #Update the local/shared connect.ini files on the new IIS server. The servername and database fields in these files needs to be set to the SQL server instance. The connect.ini files are typically found in '''c:\program files\sims\sims. net\connect.ini''' and '''s:\sims\connect.ini''' <br><br>
 #Re-run the Insight service pack on the new IIS server. On the '''Data tier''' tab, make sure that the '''Connect INI location''' field matches the location for the local connect.ini file on the new IIS server. If you have changed this location go to the '''Commit''' tab and click '''Begin'''. <br> <br>
-#Delete the Insight website from the old IIS server using IIS Manager. <br> <br> <br>
+#Delete the Insight website from the old IIS server using IIS Manager. <br> <br>
 #If you make sure of the Batch PDF conversion functionality, this will also need to be reconfigured on the new server as per the '''[[Batch_PDF_processes]]''' page <br>
 ===Making Insight externally available===

@@ Line 26: / Line 26: @@
 #Remember also that if you have links to Cashless catering systems - Copy the appropriate files from the old server. Or reconfigure as detailed in the link '''[[School dinners]]''' <br><br>
 #Update the local/shared connect.ini files on the new IIS server. The servername and database fields in these files needs to be set to the SQL server instance. The connect.ini files are typically found in '''c:\program files\sims\sims. net\connect.ini''' and '''s:\sims\connect.ini''' <br><br>
-#Re-run the Insight service pack on the new IIS server. On the '''Data tier''' tab, make sure that the '''Connect INI location''' field matches the location for the local connect.ini file on the new IIS server. If you have changed this location go to the '''Commit''' tab and click '''Begin'''. <br>
+#Re-run the Insight service pack on the new IIS server. On the '''Data tier''' tab, make sure that the '''Connect INI location''' field matches the location for the local connect.ini file on the new IIS server. If you have changed this location go to the '''Commit''' tab and click '''Begin'''. <br> <br>
 #Delete the Insight website from the old IIS server using IIS Manager. <br> <br> <br>
 #If you make sure of the Batch PDF conversion functionality, this will also need to be reconfigured on the new server as per the '''[[Batch_PDF_processes]]''' page <br>