Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,15 +1,21 @@
1		-Required .NET Hosting Bundles:
	1	+===== **Required .NET Hosting Bundles:** =====
2	2
3	3	* [[.NET 6 Hosting Bundle>>https://dotnet.microsoft.com/en-us/download/dotnet/6.0]]
4	4
5	5
6		-Ensure the following .NET Runtimes are installed:
	6	+===== **Ensure the following .NET Runtimes are installed:** =====
7	7
8	8	[[image:image-20250527112257-1.png]]
9	9
10	10
11		-Deployment Considerations:
	11	+===== **Testing and Debugging:** =====
12	12
	13	+* Check the system event viewer for any errors. Framework related and logs appear here if not successfully written to the logs. This may point to folder permission issues.
	14	+
	15	+===== =====
	16	+
	17	+===== **Deployment Considerations:** =====
	18	+
13	13	* IIS project name should be in the name of the domain in reversed:
14	14	** Format: ~{~{host_name}}
15	15	** Example: za.co.site.uapi
...	...	@@ -16,13 +16,20 @@
16	16	* Each API under the CRM project should have Its own app pool.
17	17	** Format: ~{~{host_name}}.~{~{api_name}}.~{~{version}}
18	18	** Example: za.co.site.uapi.identity.v1
	25	+* App pool considerations:
	26	+** .NET CRL Version: No Managed Code
	27	+** Managed Pipeline: Integrated
19	19	* Each API project should be in the root directory of the project.
20	20	* Under the root directory, there is a wwwroot folder, which should contain a blank folder for each of the API projects.
21	21	* Ensure you replace all the connection strings, file paths and branding of the currently client with the new one.
22	22	* Clear out all the logs for each of the API projects and ensure IIS user has required permission to write to this directory
23	23	** Directory: za.co.site.uapi\EBSphere.Api.v1.Workflow\logs
24		-*
25		-
26	26
	34	+===== =====
27	27
	36	+===== **Database Considerations:** =====
	37	+
	38	+
	39	+
	40	+
28	28