If your Softrip instance is on-premise and you do not have Softrip’s automated deployments enabled, you can update your instance’s SoftripNext applications following this guide.
Terminology
SoftripNext
The general term for SoftripNext applications.
STServerWeb
The middle/business logic tier of the SoftripNext platform. This is a .Net Core IIS application, typically hosted on your application server.
AppsNext
The back-office applications. This is an HTML/JS/CSS virtual directory hosted in IIS, typically on your web server.
ResWebNext
The public-facing front-end of the SoftripNext platform. This includes:
CMS Next
Reservations Next
CRM Next
Process
Notes
When updating SoftripNext to a new version, make sure to update all applications (STServerWeb, ResWebNext, and AppsNext).
Each component is designed and tested against the other components on the same version. Having different versions for each component is not supported and is likely to cause outages and issues.
Back Up All Applications
All backups should be done as a full copy of the applicable physical folder. Backups should be moved to their own folder and named according to the date and time (in 24-hour format) the backup was performed.
For example:STServerWeb_BKP_202307021045
for a backup of STServerWeb that occurred on 02 Jul 2023 at 10:45 AMSTServerWeb_BKP_202310041744
for a backup of STServerWeb that occurred on 04 Oct 2023 at 05:44 PMResWebNext_BKP_202305101224
for a backup of ResWebNext that occurred on 10 May 2023 at 12:24 PM
STServerWeb
On your application server, make a physical backup of the STServerWeb folder (sometimes named STSW depending on your installation).
ResWebNext
On your web server, make a physical backup of the ResWebNext folder (sometimes named RWN depending on your installation).
AppsNext
On your web server, make a physical backup of the AppsNext folder (sometimes named SoftripNext depending on your installation).
Get the Softrip Packages for the New Version
Obtain the .zip
files for the applications from your Softrip contact. There will typically be four .zip
files to download:
STServerWeb
AppsNext
ResWebNext (core application + default templates)
ResWebNext Templates (custom templates for your instance and environment)
Replace Physical Files with New Versions
Copy each package to the appropriate server, on the desktop
Extract each
.zip
file on the desktopStop the IIS application pool to ensure the copy can complete
This will cause an outage while application files are being replaced
IIS application pools are typically named according to the application (STSW or RWN)
AppsNext is not an application pool, just a virtual directory (no application pool to stop)
Copy the extracted files to the physical location for each application
Replace the existing files if prompted
Remove older files from the AppsNext (or SoftripNext) folder
[TBD]