Required .NET Hosting Bundles:
Ensure the following .NET Runtimes are installed:

Testing and Debugging:
- 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.
Deployment Considerations:
- IIS project name should be in the name of the domain in reversed:
- Format: {{host_name}}
- Example: za.co.site.uapi
- Each API under the CRM project should have Its own app pool.
- Format: {{host_name}}.{{api_name}}.{{version}}
- Example: za.co.site.uapi.identity.v1
- App pool considerations:
- .NET CRL Version: No Managed Code
- Managed Pipeline: Integrated
- Each API project should be in the root directory of the project.
- Under the root directory, there is a wwwroot folder, which should contain a blank folder for each of the API projects.
- Ensure you replace all the connection strings, file paths and branding of the currently client with the new one.
- Clear out all the logs for each of the API projects and ensure IIS user has required permission to write to this directory
- Directory: za.co.site.uapi\EBSphere.Api.v1.Workflow\logs
Database Considerations: