Upgrading the (Session-enabled) Content Service
The Content Service serves content from the Content Data Store to the website. The Session-enabled Content Service does the same, but adds session information.
Before you begin
| Prerequisite | Description |
|---|---|
| Operating system | You can run the scripts on any machine running an operating system that supports any version of Powershell of 5.0 and higher. |
| Powershell software | Running the scripts requires a version of Powershell between 5.0 and higher. |
| Microsoft .NET Framework | Running the scripts requires Microsoft .NET Framework 4.8 or higher. |
| Security | You need to be logged in as a user with sufficient security clearance. For example, to run a script that installs software to a target folder, you must be logged in as a user with write access to that folder. |
- If you are using Digital Experience Accelerator (DXA) to build your website, your (Session-enabled) Content Service needs to continue to be extended with the DXA Model Extension in order to support the DXA data model. So, when upgrading the (Session-enabled) Content Service, you must also upgrade the DXA Model Extension to the same version. Refer to the DXA documentation for installation instructions and a list of compatible versions.
- You must have set up the search feature introduced in SDL Tridion Sites 9.5.
About this task
- Environmental parameters
-
You can set and pass environmental parameters to the microservice scripts in the following ways:
- You can create and set them as environment variables on the operating system of the machine on which the microservice runs.
- You can hardcode them in the application.properties file located in the configuration location of the microservice.
- You can pass them using the
-Dswitch when you run the script from the command line. For example, to specify that the parameterfoohas the valuebar, you would type'-Dfoo=bar'after your script command.
- Script parameters
-
You may want to add script parameters to your installation script. To do so, append them to the installation script command, in the form
--PARAMETER(if it is a Boolean parameter) or--PARAMETER=VALUE(if it is a parameter-value pair) , where PARAMETER is the name of the parameter, and VALUE (when using) is the value you want to set it to.
| Installation type | Name of installation script | When to use |
|---|---|---|
| Microsoft Windows service | installService.ps1 | Choose for long-term use on Windows, say on a production system. The microservice continues to run when you close the PowerShell prompt. It can be stopped and restarted from the Windows Control Panel. It outputs its log as a file. |
| Microsoft Windows process | start.ps1 | Choose for short-term use on Windows, say on a test system. The microservice stops running when you close the PowerShell prompt. It outputs its log in the command prompt window. |
| Unix process | start.sh | Choose if you are installing on a Unix-based operating system. |