Wiki source code of Helpdesk Web Interface installieren

Last modified by Sabrina V. on 2025/03/03 07:42

version	line-number	content
1.1	1	{{aagon.priorisierung}}
	2	100
	3	{{/aagon.priorisierung}}
	4
	5	{{aagon.floatingbox/}}
	6
20.1	7	= Installation requirements =
1.1	8
20.1	9	* The Internet Information Service (IIS) must be installed or be in the process of being installed.
	10	* The.NET Framework 4.7.1 is already installed or will be installed with the IIS.
	11	* Port 80 or the port set in the IIS settings must be accessible.
1.1	12
	13
20.1	14	To be able to use the Helpdesk to its full extent, first install the IIS and the.NET Framework. After that, configurations must be made in the ACMP Console.
1.1	15
20.1	16	This is how you proceed:
1.1	17
	18
20.1	19	= Installation of Internet Information Services (IIS) =
1.1	20
20.1	21	IIS is supplied as standard from Windows XP as an additional Windows component; however, it must be installed in advance in order to use it. Since the newer Windows versions also come with newer IIS versions, this chapter explains the installation of IIS for the various Windows server versions. In each case, it is the IIS version that is provided by the corresponding Windows version by default:
1.1	22
20.1	23	IIS 10: Windows Server 2016 / Windows Server 2019 / Windows Server 2022
1.1	24
20.1	25	== Installation on Windows Server 2016 ==
1.1	26
20.1	27	~1. Open Server Manager and go to //Manage// > //Add Roles and Features//. This opens the Add Roles and Features Wizard.
	28	2. Under //Installation type//, select //Role-based or feature-based installation//.
	29	3. Under //Server selection//, select the target server on which IIS is to be installed.
	30	4. Under //Server roles//, navigate to //Web Server (IIS).//
	31	//5. Under Web Server //and //Administration Tools,// activate the following roles by ticking the box:
1.1	32
	33	(% style="width:666.778px" %)
20.1	34	\|Web server\|Hooking role
	35	\|General HTTP Features\|Static content (installed)
	36	\|Performance\|Compression of static content (installed)
	37	\|Security\|Requirement filtering (installed)
	38	\| \|Windows Authentication (Installed)
	39	\|System status and diagnostics\|HTTP logging (installed)
	40	\| \|Requirements monitoring (installed)
	41	\|Application development\|.NET extensibility 4.7
	42	\| \|ASP.NET 4.7
	43	\|Management programmes\|
	44	\| \|IIS Management Console
	45	\|Compatibility with IIS6 administration\|IIS6 meta compatibility (installed)
	46	\|Administrative service (installed)\|Administrative service (installed)
1.1	47
	48	{{figure}}
	49	[[image:1695733411358-461.png]]
	50
	51	{{figureCaption}}
20.1	52	Server Manager for Windows Server 2016
1.1	53	{{/figureCaption}}
	54	{{/figure}}
	55
20.1	56	6. Click //Next//.
	57	7. On the next page, leave the ticked features as they are and then click //Install//. Only then will IIS be installed.
1.1	58
20.1	59	== Installation under Windows Server 2019 ==
1.1	60
20.1	61	~1. Open the Server Manager and go to //Manage// > //Add Roles and Features//. This opens the Add Roles and Features Wizard.
	62	2. Under //Installation Type//, select //Role-based or feature-based installation//.
	63	3. Under //Select Server//, select the target server on which IIS is to be installed.
	64	4. Under //Server Roles//, go to //Web Server (IIS). Under Web Server //and //Administrative Tools,// activate the following roles by checking the box:
1.1	65
	66	(% style="width:666.778px" %)
20.1	67	\|Web server\|Hooking role
	68	\|General HTTP Features\|Static content (installed)
	69	\|Performance\|Compression of static content (installed)
	70	\|Security\|Requirement filtering (installed)
	71	\| \|Windows Authentication (Installed)
	72	\|System status and diagnostics\|HTTP logging (installed)
	73	\| \|Requirements monitoring (installed)
	74	\|Application development\|.NET extensibility 4.7
	75	\| \|ASP.NET 4.7
	76	\|Management programmes\|
	77	\| \|IIS Management Console
	78	\|Compatibility with IIS6 administration\|IIS6 meta compatibility (installed)
	79	\|Administrative service (installed)\|Administrative service (installed)
1.1	80
	81	{{figure}}
5.1	82	[[image:Server-Manager 2022.PNG\|\|data-xwiki-image-style-alignment="center" height="750" width="810"]]
1.1	83
	84	{{figureCaption}}
20.1	85	Server Manager for Windows Server 2019
1.1	86	{{/figureCaption}}
	87	{{/figure}}
	88
20.1	89	6. Click //Next//.
	90	7. On the next page, leave the ticked features as they are and then click //Install//. Only then will IIS be installed.
1.1	91
20.1	92	== Installation under Windows Server 2022 ==
1.1	93
20.1	94	~1. Open the Server Manager and go to //Manage// > //Add Roles and Features//. An assistant for adding roles and features will open.
	95	2. Under //Installation type//, select //Role-based or feature-based installation//.
	96	3. Under //Server selection//, select the target server on which IIS is to be installed.
	97	4. Under //Server Roles//, go to //Web Server (IIS). Under Web Server //and //Administration Tools,// also enable the following roles by checking the box:
1.1	98
	99	(% style="width:666.778px" %)
20.1	100	\|Web server\|Hooking role
	101	\|General HTTP Features\|Static content (installed)
	102	\|Performance\|Compression of static content (installed)
	103	\|Security\|Requirement filtering (installed)
	104	\| \|Windows Authentication (Installed)
	105	\|System status and diagnostics\|HTTP logging (installed)
	106	\| \|Requirements monitoring (installed)
	107	\|Application development\|.NET extensibility 4.7
	108	\| \|ASP.NET 4.7
	109	\|Management programmes\|
	110	\| \|IIS Management Console
	111	\|Compatibility with IIS6 administration\|IIS6 meta compatibility (installed)
	112	\|Administrative service (installed)\|Administrative service (installed)
1.1	113
	114	{{figure}}
5.1	115	[[image:Server-Manager 2022.PNG\|\|data-xwiki-image-style-alignment="center" height="750" width="810"]]
1.1	116
	117	{{figureCaption}}
20.1	118	Server Manager for Windows Server 2022
1.1	119	{{/figureCaption}}
	120	{{/figure}}
	121
20.1	122	6. Click //Next//.
	123	7. On the next page, leave the ticked features as they are and then click //Install//. Only then will IIS be installed.
1.1	124
20.1	125	= Installing the Web Interface =
1.1	126
20.1	127	The installation file for the web interfaces can be found under the path //%programfiles%\Aagon\ACMP Server\Clients\WebInterfaceSetup//. Execute the file WebSetups.msi to install both web interfaces on an IIS. Follow the installation instructions to complete the installation. The web interfaces are now installed in the directory //%programfiles%\Aagon\ACMP Web Interfaces//.
8.1	128
20.1	129	= Configuration in the ACMP Console =
8.1	130
20.1	131	To allow any requests from the Web Interface, the IP address of the web server must be trusted. The IP address is entered in the ACMP Console.
1.1	132
20.1	133	In the ACMP Console, navigate to //System > Settings > ACMP Server > Networks.// The server on which the web interface is installed and whose requests are to be allowed is specified in the area under //Trusted web servers//.
1.1	134
	135	{{aagon.infobox}}
20.1	136	All incoming web interface requests from a server not listed here will be rejected!
1.1	137	{{/aagon.infobox}}
	138
	139	{{figure}}
5.1	140	[[image:vertrauenswürdige webserver.png\|\|data-xwiki-image-style-alignment="center" height="420" width="800"]]
1.1	141
	142	{{figureCaption}}
20.1	143	Enter trusted web severs
1.1	144	{{/figureCaption}}
	145	{{/figure}}
	146
20.1	147	If the web interface is installed on the same machine as the ACMP Server, it is already entered with the address 127.0.0.1. If this is not the case, then add the IP address of the server via //Add//.
1.1	148
20.1	149	== Activate Web Interfaces ==
1.1	150
20.1	151	To use the web interface, it must first be activated via the ACMP Console. In the ACMP Console, go to //System > Settings > Web Interface > General settings//. Then enable the option //Helpdesk Web Interface is active.//
1.1	152
	153
20.1	154
1.1	155	{{figure}}
5.1	156	[[image:Web Interfaces aktivieren.png\|\|data-xwiki-image-style-alignment="center" height="361" width="800"]]
1.1	157
	158	{{figureCaption}}
20.1	159	Enabling the Helpdesk Web Interface
1.1	160	{{/figureCaption}}
	161	{{/figure}}
	162
20.1	163	== Accessing Web Interface ==
1.1	164
20.1	165	To access the web interfaces, you have the following three options:
1.1	166
	167	=== Self Service ===
	168
20.1	169	The Self Service web interface allows employees to submit tickets that can be processed by Helpdesk staff. To access the Self Service web interface, a user account must be created in the ACMP Console.
1.1	170
20.1	171	The call is made via the following link: http:~/~/[Server IP]/Self-Service/
1.1	172
	173	=== Self Service SSO ===
	174
20.1	175	You can activate a single sign-on for the Self Service web interface. To do this, the user must be logged on to an Active Directory. In addition, the AD authentication must be activated in the ACMP Console.
1.1	176
20.1	177	The call is made via the following link: http:~/~/[Server IP]/Self-Service/SSO
1.1	178
	179	=== Helpdesk ===
	180
20.1	181	As a Helpdesk employee, you can access the tickets assigned to you via the Helpdesk Web Interface and edit them as you would in the ACMP Console.
1.1	182
20.1	183	The ACMP Helpdesk Web Interface can be accessed via the following link: http:~/~/[Server-IP]/Helpdesk/
1.1	184
20.1	185	= Updating the Web Interfaces =
1.1	186
20.1	187	After installing an ACMP Updates, it may be necessary to update the Helpdesk Web Interface. Normally, when ACMP is patched to a new version, all the solutions you have installed are patched. One exception is the Web Interface, because it is a standalone application. Therefore, if an ACMP update affects the Web Interface, it must also be updated. If the Web Interface is affected by an Update, you will be informed via the Release Notes.
1.1	188
20.1	189	If you need to reinstall the Web Interface, please follow these steps:
1.1	190
20.1	191	~1. Navigate to //%programfiles%\Aagon\ACMP Server\Clients //in the //WebInterfaceSetup// folder. Execute the //WebSetup.msi //file to install the web interfaces on the IIS.
	192	2. Go through the installation wizard. To install the web interfaces in the directory you have selected, select //Install//. The installation of the update will now begin.
	193	3. After the update, check whether the correct port and the correct IP address of the ACMP Server are entered in the configuration files:
1.1	194
	195	{{aagon.infobox}}
20.1	196	Usually when installing or updating the web interface, the server port is not taken over if it was changed during the installation of the ACMP Server. Therefore you have to check the values in this step and change them if necessary!
1.1	197	{{/aagon.infobox}}
	198
	199	{{aagon.infobox}}
20.1	200	If you are not sure about the server name and the server port, you can look up the values in the Settings.ini file on the ACMP network share in the //ACMP Server > Clients// directory. Otherwise you can skip tot he next step.
1.1	201	{{/aagon.infobox}}
	202
	203	{{figure}}
5.1	204	[[image:settings.ini.png\|\|data-xwiki-image-style-alignment="center"]]
1.1	205
	206	{{figureCaption}}
20.1	207	Reading the values in settings.ini
1.1	208	{{/figureCaption}}
	209	{{/figure}}
	210
20.1	211	Open the web interface configuration file via //C:\Program Files (x86)\Aagon\ACMP Web Interfaces\Helpdesk Webinterface\Web.config// and the second configuration file via //C:\Program Files (x86)\Aagon\ACMP Web Interfaces\SSO\web.config//.
1.1	212
20.1	213	The following values may need to be changed in both files:
1.1	214
	215	{{figure}}
5.1	216	[[image:webconfig.png\|\|data-xwiki-image-style-alignment="center"]]
1.1	217
	218	{{figureCaption}}
20.1	219	Customizing the values
1.1	220	{{/figureCaption}}
	221	{{/figure}}
	222
20.1	223	The Update is then complete.
1.1	224
	225	{{aagon.infobox}}
20.1	226	The settings and configurations in web.config are retained during an update. To secure all continuing individual settings of the Web Interfaces, such as customised and modified graphics or texts, you must make a backup of these and import them after the update of the Web Interfaces!
1.1	227	{{/aagon.infobox}}