Summary

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

Details

Page properties

Content

...	...	@@ -1,19 +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		-Testing and Debugging:
	11	+===== **Testing and Debugging:** =====
12	12
13	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	14
15		-Deployment Considerations:
	15	+===== =====
16	16
	17	+===== **Deployment Considerations:** =====
	18	+
17	17	* IIS project name should be in the name of the domain in reversed:
18	18	** Format: ~{~{host_name}}
19	19	** Example: za.co.site.uapi
...	...	@@ -20,6 +20,7 @@
20	20	* Each API under the CRM project should have Its own app pool.
21	21	** Format: ~{~{host_name}}.~{~{api_name}}.~{~{version}}
22	22	** Example: za.co.site.uapi.identity.v1
	25	+* Each API under the CRM should be deployed as a virtual application linked to its relative app pool.
23	23	* App pool considerations:
24	24	** .NET CRL Version: No Managed Code
25	25	** Managed Pipeline: Integrated
...	...	@@ -27,8 +27,36 @@
27	27	* Under the root directory, there is a wwwroot folder, which should contain a blank folder for each of the API projects.
28	28	* Ensure you replace all the connection strings, file paths and branding of the currently client with the new one.
29	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		-*
	33	+** Directory: "//za.co.site.uapi\EBSphere.Api.v1.Workflow\logs//"
32	32
	35	+===== =====
33	33
	37	+===== **Database Considerations:** =====
	38	+
	39	+* Some databases are setup to require a reference number when making structural changes to the database:
	40	+** Create a session reference: (% style="color:#2980b9" %)//exec//(%%)// sp_set_session_context 'ReferenceNo', '123456789'//
	41	+** The reference number is the ticket number of the project, as found on our Issue log system.
	42	+* Depending on the state of the database, there might be tables, procedures, views and even data that need to be added. Is a list of some of some these objects, that need to be present in the database for the CRM to work correctly (//Please feel free to added on//):
	43	+
	44	+|=Object Type|=Name|=Dependencies
	45	+| |api.sp_AddSupplier_Se|
	46	+| |api.sp_BankAccountTypes_SelectV2|
	47	+| |api.sp_Communication_Add|
	48	+| |api.sp_Communication_AddProperty|
	49	+| |api.sp_Content_Add|
	50	+| |api.sp_Content_AddProperty|
	51	+| |api.sp_CreateSupplier|
	52	+| |api.sp_CRM_RegisterUser|
	53	+| |api.sp_CRM_ResetPassword|
	54	+| |api.sp_DocumentCategories_SelectV2|
	55	+| |api.sp_Documents_SelectV2|
	56	+| |api.sp_GetBBBEE_Levels|
	57	+| |api.sp_GetPersonDetailsV2|
	58	+| |api.sp_GetSupplierTypes|
	59	+| |api.sp_GetUniversalBankBranch|
	60	+| |api.sp_MemberBankDetails_SelectV2|
	61	+| |api.sp_MemberBeneficiaries_SelectV2|
	62	+
	63	+
	64	+
34	34