Configurator/IniFiles - Revision history

Ori@inlogic.dk: /* How to run/install on IIS */

2025-10-28T09:53:46Z

How to run/install on IIS

← Older revision		Revision as of 09:53, 28 October 2025
Line 155:		Line 155:

	Remember to copy '''IniFiles.json''' into the bin folder along with the ini files specified in the json file.		Remember to copy '''IniFiles.json''' into the bin folder along with the ini files specified in the json file.

			=== HTTP Error 500.35 - ASP.NET Core does not support multiple apps in the same pool ===
			If you encounter the following error message:

			[[File:HTTP Error 500.35- ASP.NET.png\|frameless\|500x500px]]

			Try the following:

			* Stop the Install Site in IIS
			* Go to the application pool of the site that is experiencing the error
			* Recycle the application pool
			* If the error persists try stopping the application pool entirely before starting it again

			The error in question has to do with how the UMS install manager interacts with ASP.NET Core and IIS. If some processes are not shutdown cleanly, they will continue to run and create issues, which in turn will impact the order of when sites reset, ultimately creating this error where multiple apps are running within the same application pool, which ASP.NET does not allow.

2025-09-16T11:18:00Z

← Older revision		Revision as of 11:18, 16 September 2025
Line 57:		Line 57:
	'''[inetpub\Guardian]''' for UMS Guardian installation.		'''[inetpub\Guardian]''' for UMS Guardian installation.

			====== Logo files for UMS Academic Web & Guardian ======
			1. Go to Web Setup for the customer (PAP Setup for Guardian)

			2. Change logo filename to something unique for the customer like (customer_name_logo.png)

			3. Make sure your filename and type matches what you entered earlier

			4. Add the new logo file under the folder named CustomStyle

			4. IIS reset

	==== Copy inifile.json and [usermanagement - customerfilename.ini] files ====		==== Copy inifile.json and [usermanagement - customerfilename.ini] files ====

2025-02-28T12:19:40Z

Copy inifile.json and all customerfilename.ini

← Older revision		Revision as of 12:19, 28 February 2025
Line 58:		Line 58:


	==== Copy inifile.json and ~~all~~ customerfilename.ini ====		==== Copy inifile.json and [usermanagement - customerfilename.ini] files ====
	Inifiles created in usermanagement folder for the above setting must be copied to:		Inifiles created in usermanagement folder for the above setting must be copied to:

2025-02-28T12:16:01Z

Name

← Older revision		Revision as of 12:16, 28 February 2025
Line 72:		Line 72:

	==== Name ====		==== Name ====
	This is an abbreviated name for the ~~ini file~~. This can only contain [a-zA-Z0-9].		This is an abbreviated name for the customer. This can only contain [a-zA-Z0-9].

	This is used for two things:		This is used for two things:

	* When running the programs from the commandline with the parameter "'''/IniFilesName:~~Customer1~~'''"~~. Change Customer1 to the name you want to use~~.		* When running the programs from the commandline with the parameter "'''/IniFilesName:[Name]'''".
	* It will generate new log files with the prefix "'''GetStudents ~~Customer1~~.log'''" for each row ~~name~~. This will allow you to see the log file just you would when this is not used.		* It will generate new log files with the prefix "'''GetStudents [Name].log'''" for each row. This will allow you to see the log file just you would when this is not used.

	==== Filename ====		==== Filename ====

2025-02-28T11:00:23Z

Description

@@ Line 1: / Line 1: @@
 == Description ==
 This setting allows UMS Software to run multiple Configurations (customers) from the same server.
 To enable this feature, you must create an entry in the Configurator.
 After configuration a file will be generated in the UMS installation (Usermanagement) folder containing these settings. '''They are not stored in a database.'''
 An example of the generated '''IniFiles.json''' (see below).
@@ Line 39: / Line 40: @@
+   ]
+  }
 ==Settings==

2025-02-28T10:19:06Z

Description

← Older revision		Revision as of 10:19, 28 February 2025
Line 1:		Line 1:
	== Description ==		== Description ==
	This setting allows UMS ~~backend~~ to run multiple ~~UMS installation~~ (customers) from the same ~~backend~~ server.		This setting allows UMS Software to run multiple Configurations (customers) from the same server.

	Options for this setting can be found under Settings -> IniFiles		Options for this setting can be found under Settings -> IniFiles

	~~A file will be generate under~~ the ~~UMS installation folder containing these settings. '''They are not stored in a database~~.~~'''~~		To enable this feature, you must create an entry in the Configurator.

	~~The~~ file ~~is called~~ '''IniFiles.json''' ~~and the contents of the file looks like this~~.		After configuration a file will be generated in the UMS installation (Usermanagement) folder containing these settings. '''They are not stored in a database.'''

			An example of the generated '''IniFiles.json''' (see below).
	{		{
	"IniFiles": [		"IniFiles": [

2025-01-08T10:48:32Z

Program name

← Older revision		Revision as of 10:48, 8 January 2025
Line 78:		Line 78:

	For UMS Services this is still the *.exe file name.		For UMS Services this is still the *.exe file name.

			You can enter some reserved Keywords:

			* Programs
			** All backend programs that are not services
			* Services
			** All backend services
			* *
			** All backend programs and services

			The order in which the program or service decides the concurrency is:

			# Specified with the program name
			# Programs or Services keyword
			# *

	==== Max concurrency ====		==== Max concurrency ====

2025-01-08T08:19:33Z

How to run on IIS

← Older revision		Revision as of 08:19, 8 January 2025
Line 97:		Line 97:
	Then change to this setting under Settings -> IniFiles -> Change Setting. This will cause UMS to say that the file does not exist and ask you to fill out the SQL connection information.		Then change to this setting under Settings -> IniFiles -> Change Setting. This will cause UMS to say that the file does not exist and ask you to fill out the SQL connection information.

	== How to run on IIS ==		== How to run/install on IIS ==
	You install UMS Academic web into a web site.		You install UMS Academic web into a web site.

2025-01-08T08:18:57Z

How to run on IIS

← Older revision		Revision as of 08:18, 8 January 2025
Line 101:		Line 101:

	Then you create new websites that points into the same physical folder. This website name is used in the IniFiles.json under the tag "'''Web site name'''" as described in under [[Configurator/IniFiles#Web site name]]		Then you create new websites that points into the same physical folder. This website name is used in the IniFiles.json under the tag "'''Web site name'''" as described in under [[Configurator/IniFiles#Web site name]]

			Remember to copy '''IniFiles.json''' into the bin folder along with the ini files specified in the json file.

2025-01-08T08:17:06Z

How to run on IIS

← Older revision		Revision as of 08:17, 8 January 2025
Line 100:		Line 100:
	You install UMS Academic web into a web site.		You install UMS Academic web into a web site.

	Then you create new websites that points into the same physical folder. This website name is used in the IniFiles.json under the tag "'''Web site name'''" as described in ~~the~~		Then you create new websites that points into the same physical folder. This website name is used in the IniFiles.json under the tag "'''Web site name'''" as described in under [[Configurator/IniFiles#Web site name]]