The process of deploying code changes is different depending on the nature of the change and the components that have to be updated. The following deployment methodologies are recommended.
Custom Step Changes
Custom Steps that do not involve database changes can be deployed by copying the DLL of the CustomStep project to the Tctep installation folder of each target environment.
Right click on StopTConnect.bat on the Windows desktop and select ‘Run As Administrator’ Alternatively, open Services.msc and stop the following services
- TctepDbPollingService
- TctepHttpService
- TctepRoutingService
- TctpValidationService
Open Tctep.sln and build the CustomSteps project
Updated assembly DLLs are placed in the $Solution\Deployment\ folder. Copy any updated DLLs (CustomSteps.dll, CustomSteps.pdb) to the Tctep runtime directory on the application Server. Typically C:\Tctep\
Right click on StartTConnect.bat on the Windows desktop and select ‘Run As Administrator’ Alternatively, open Services.msc and start the following services
- TctepDbPollingService
- TctepHttpService
- TctepRoutingService
- TctpValidationService
Other Code Changes within the TCTEP Visual Studio Solution
Other code changes follow the same procedure as custom step changes except for the following:
- In Step 2 – build the entire solution instead of the CustomSteps.csproj project
- In Step 3 – Copy all DLL and PDB files
Database Changes
Database changes can be deployed by running database scripts on the target environment within SQL Server Management Studio (SSMS). Scripts are manually created, or can be sourced through the use of the adm.pGenerateMergeScript stored procedure referenced in the Deployment Script article
Management Portal Changes
Portal deployment can best be accomplished by either building a web deploy package from Visual Studio, or exporting a deployment package from within IIS. The web deploy packages can then be imported into the target environment through IIS. Below is a walkthrough of the manual process, but a PowerShell script is available that can automate the package creation and deployment.
First, backup the web.config and appsettings.json from the target environment. Typically C:\intepub\tconnect\Portal.API & Portal.Web
Building the web deploy package (Visual Studio)
- Open Portal.sln and build Portal.Web and Portal.API projects
- Right click on Portal.API and select ‘Publish’
- Use the XXX profile
- Copy the generated zip file from C:\Deploy\Portal\ to the target environment
Building the web deploy package (IIS)
- Open IIS
- Right click on TConnect/Portal.API à Deploy à Export Application
- Follow default prompts to create a zip file, and copy to target environment
- Do the same for TConnect/Portal.Web
Deploying the web deploy package (IIS)
- Open IIS
- Right click on TConnect à Deploy à Import Application
- Select the Portal.API.zip created in previous steps
- Follow default prompts, select override when promoted to override existing files
- Right click on TConnect à Deploy à Import Application
- Select the Portal.Web.zip created in previous steps
- Follow default prompts, select override when promoted to override existing files
- Restore the app.settings.json and app.config files from the backup copy saved in previous steps to retain the correct connection string and host name settings.
