Summary

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

Details

Page properties

Content

...	...	@@ -22,6 +22,7 @@
22	22	* Each API under the CRM project should have Its own app pool.
23	23	** Format: ~{~{host_name}}.~{~{api_name}}.~{~{version}}
24	24	** 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.
25	25	* App pool considerations:
26	26	** .NET CRL Version: No Managed Code
27	27	** Managed Pipeline: Integrated
...	...	@@ -29,13 +29,19 @@
29	29	* Under the root directory, there is a wwwroot folder, which should contain a blank folder for each of the API projects.
30	30	* Ensure you replace all the connection strings, file paths and branding of the currently client with the new one.
31	31	* Clear out all the logs for each of the API projects and ensure IIS user has required permission to write to this directory
32		-** Directory: za.co.site.uapi\EBSphere.Api.v1.Workflow\logs
	33	+** Directory: "//za.co.site.uapi\EBSphere.Api.v1.Workflow\logs//"
33	33
34	34	===== =====
35	35
36	36	===== **Database Considerations:** =====
37	37
	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	+**
38	38
39	39
40	40
	47	+
41	41