| ... |
... |
@@ -8,10 +8,6 @@ |
| 8 |
8 |
[[image:image-20250527112257-1.png]] |
| 9 |
9 |
|
| 10 |
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 |
15 |
Deployment Considerations: |
| 16 |
16 |
|
| 17 |
17 |
* IIS project name should be in the name of the domain in reversed: |
| ... |
... |
@@ -20,14 +20,8 @@ |
| 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 |
| 23 |
|
-* App pool considerations: |
| 24 |
|
-** .NET CRL Version: No Managed Code |
| 25 |
|
-** Managed Pipeline: Integrated |
| 26 |
26 |
* Each API project should be in the root directory of the project. |
| 27 |
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 |
31 |
* |
| 32 |
32 |
|
| 33 |
33 |
|