Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • image-20250527112257-1.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.rudim
	1	+XWiki.kyleh

Content

...	...	@@ -1,1 +1,34 @@
	1	+Required .NET Hosting Bundles:
	2	+
1	1	* [[.NET 6 Hosting Bundle>>https://dotnet.microsoft.com/en-us/download/dotnet/6.0]]
	4	+
	5	+
	6	+Ensure the following .NET Runtimes are installed:
	7	+
	8	+[[image:image-20250527112257-1.png]]
	9	+
	10	+
	11	+Testing and Debugging:
	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	+Deployment Considerations:
	16	+
	17	+* IIS project name should be in the name of the domain in reversed:
	18	+** Format: ~{~{host_name}}
	19	+** Example: za.co.site.uapi
	20	+* Each API under the CRM project should have Its own app pool.
	21	+** Format: ~{~{host_name}}.~{~{api_name}}.~{~{version}}
	22	+** Example: za.co.site.uapi.identity.v1
	23	+* App pool considerations:
	24	+** .NET CRL Version: No Managed Code
	25	+** Managed Pipeline: Integrated
	26	+* Each API project should be in the root directory of the project.
	27	+* Under the root directory, there is a wwwroot folder, which should contain a blank folder for each of the API projects.
	28	+* Ensure you replace all the connection strings, file paths and branding of the currently client with the new one.
	29	+* Clear out all the logs for each of the API projects and ensure IIS user has required permission to write to this directory
	30	+** Directory: za.co.site.uapi\EBSphere.Api.v1.Workflow\logs
	31	+*
	32	+
	33	+
	34	+

image-20250527112257-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.kyleh

Size

...	...	@@ -1,0 +1,1 @@
	1	+11.7 KB

Content