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,115 @@
	1	+===== **Required .NET Hosting Bundles:** =====
	2	+
1	1	* [[.NET 6 Hosting Bundle>>https://dotnet.microsoft.com/en-us/download/dotnet/6.0]]
	4	+
	5	+(% class="wikigeneratedid" %)
	6	+===== =====
	7	+
	8	+===== **Ensure the following .NET Runtimes are installed:** =====
	9	+
	10	+[[image:image-20250527112257-1.png]]
	11	+
	12	+
	13	+===== **Testing and Debugging:** =====
	14	+
	15	+* 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.
	16	+
	17	+===== =====
	18	+
	19	+===== **Deployment Considerations:** =====
	20	+
	21	+* IIS project name should be in the name of the domain in reversed:
	22	+** Format: ~{~{host_name}}
	23	+** Example: za.co.site.uapi
	24	+* Each API under the CRM project should have Its own app pool.
	25	+** Format: ~{~{host_name}}.~{~{api_name}}.~{~{version}}
	26	+** Example: za.co.site.uapi.identity.v1
	27	+* Each API under the CRM should be deployed as a virtual application linked to its relative app pool.
	28	+* App pool considerations:
	29	+** .NET CRL Version: No Managed Code
	30	+** Managed Pipeline: Integrated
	31	+* Each API project should be in the root directory of the project.
	32	+* Under the root directory, there is a wwwroot folder, which should contain a blank folder for each of the API projects.
	33	+* Ensure you replace all the connection strings, file paths and branding of the currently client with the new one.
	34	+* Clear out all the logs for each of the API projects and ensure IIS user has required permission to write to this directory
	35	+** Directory: "//za.co.site.uapi\EBSphere.Api.v1.Workflow\logs//"
	36	+
	37	+===== =====
	38	+
	39	+===== **Database Considerations:** =====
	40	+
	41	+* Some databases are setup to require a reference number when making structural changes to the database:
	42	+** Create a session reference: (% style="color:#2980b9" %)//exec//(%%)// sp_set_session_context 'ReferenceNo', '123456789'//
	43	+** The reference number is the ticket number of the project, as found on our Issue log system.
	44	+* 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 these objects, that need to be present in the database for the CRM to work correctly (//Please feel free to added on//):
	45	+
	46	+|=Object Type|=Name|=Dependencies
	47	+|Procedure|api.sp_AddSupplier_Se|
	48	+|Procedure|api.sp_BankAccountTypes_SelectV2|
	49	+|Procedure|api.sp_Communication_Add|
	50	+|Procedure|api.sp_Communication_AddProperty|
	51	+|Procedure|api.sp_Content_Add|
	52	+|Procedure|api.sp_Content_AddProperty|
	53	+|Procedure|api.sp_CreateSupplier|
	54	+|Procedure|api.sp_CRM_RegisterUser|
	55	+|Procedure|api.sp_CRM_ResetPassword|
	56	+|Procedure|api.sp_DocumentCategories_SelectV2|
	57	+|Procedure|api.sp_Documents_SelectV2|
	58	+|Procedure|api.sp_GetBBBEE_Levels|
	59	+|Procedure|api.sp_GetPersonDetailsV2|
	60	+|Procedure|api.sp_GetSupplierTypes|
	61	+|Procedure|api.sp_GetUniversalBankBranch|
	62	+|Procedure|api.sp_MemberBankDetails_SelectV2|
	63	+|Procedure|api.sp_MemberBeneficiaries_SelectV2|
	64	+|Procedure|api.sp_MemberClaimStatus_SelectV2|
	65	+|Procedure|api.sp_MemberCouncilRates_SelectV2|
	66	+|Procedure|api.sp_MemberNotes_InsertV2|
	67	+|Procedure|api.sp_MemberNotes_SelectV2|
	68	+|Procedure|api.sp_MemberNoteVariableGroups_SelectV2|
	69	+|Procedure|api.sp_MemberNoteVariables_SelectV2|
	70	+|Procedure|api.sp_MemberPayments_SelectV2|
	71	+|Procedure|api.sp_MemberPaypoints_SelectV2|
	72	+|Procedure|api.sp_MemberSalaries_SelectV2|
	73	+|Procedure|api.sp_MemberSinglePremiums_SelectV2|
	74	+|Procedure|api.sp_MemberTaxApplications_SelectV2|
	75	+|Procedure|api.sp_People_SelectV2|
	76	+|Procedure|api.sp_Scheduler_AddNote|
	77	+|Procedure|api.sp_Scheduler_AddProperty|
	78	+|Procedure|api.sp_Scheduler_CompleteActivity|
	79	+|Procedure|api.sp_Scheduler_CreateProcess|
	80	+|Procedure|api.sp_Scheduler_CurrentActivities|
	81	+|Procedure|api.sp_Scheduler_GetActivityActions|
	82	+|Procedure|api.sp_Scheduler_GetNotes|
	83	+|Procedure|api.sp_Scheduler_GetProcessProperties|
	84	+|Procedure|api.sp_SearchPersonDetails|
	85	+|Procedure|api.sp_SearchPersonMembershipV2|
	86	+|Procedure|api.sp_Workflow_AddNote|
	87	+|Procedure|api.sp_Workflow_AddProperty|
	88	+|Procedure|api.sp_Workflow_CompleteActivity|
	89	+|Procedure|api.sp_Workflow_CreateProcess|
	90	+|Procedure|api.sp_Workflow_GetActivityActions|
	91	+|Procedure|api.sp_Workflow_GetLinkedContent|
	92	+|Procedure|api.sp_Workflow_GetNotes|
	93	+|Procedure|api.sp_Workflow_GetProcessProperties|
	94	+|Procedure|api.sp_Workflow_LinkContent|
	95	+|Procedure|api.sp_Workflow_Reallocate|
	96	+|Procedure|api.sp_Workflow_SearchActivities|
	97	+|Procedure|api.sp_Workflow_SearchProcess|
	98	+|Procedure|api.sp_Workflow_SearchStreamResources|
	99	+|Procedure|api.sp_Workflow_SearchStreams|
	100	+|Procedure|api.sp_Workflow_UpdateProperty|
	101	+|Procedure|dbo.sp_InsertImageToDocDatabase|
	102	+|Procedure|dbo.sp_MaritalStatus|
	103	+|Procedure|dbo.sp_SchedulerAddNote|
	104	+|Procedure|dbo.sp_Update_frmPeople|
	105	+|Procedure|dbo.sp_UserLevels|
	106	+|Procedure|dbo.sp_WorkflowAddNote|
	107	+|Procedure|prg.sp_ProviderParameters_select|
	108	+|Procedure|scr.sp_BankBranches_Member|
	109	+|Procedure|scr.sp_MFGMemberCFLO|
	110	+|Procedure|scr.sp_MFGMemberPaypoints|
	111	+|Procedure|scr.sp_Paypoints|
	112	+|Procedure|web.sp_UserWebLogin|
	113	+
	114	+
	115	+

image-20250527112257-1.png

Author

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

Size

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

Content