crm

Required .NET Hosting Bundles:

• .NET 6 Hosting Bundle

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
• Each API under the CRM should be deployed as a virtual application linked to its relative app pool.
• 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:

• Some databases are setup to require a reference number when making structural changes to the database:
  • Create a session reference: exec sp_set_session_context 'ReferenceNo', '123456789'
  • The reference number is the ticket number of the project, as found on our Issue log system.
• 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):
  •