Upgrading the Context Expression Extension
To upgrade Context Expression Extension, upgrade the Content Deployer extension and the Context Expression Extension Cartridge.
Procedure
- On your installation media, navigate to \Content Delivery\expression\extension-deployer\.
- Perform the following steps 3-8 on the combined Content Deployer or, if you have split up the Content Deployer in a worker and an endpoint, to both of those.
- On your target system, navigate to the library location.
- If you are upgrading from SDL Tridion 2013 SP1 HR1, remove the following files, which now have new names, from your library location:
- cx_api.jar
- cx_deployer.jar
- If you are upgrading from SDL Web 8 with Cumulative Update 1 applied, remove the following files, which now have new names, from your library location:
- cx_api-8.1.1-1008.jar
- cx_deployer-8.1.1-1008.jar
- gson-2.3.1.jar
- Copy all files from the installation media subfolder lib\ into the library location, overwriting any files with the same name already present.
- Merge the contents of the installation media file config\deployer-conf.xml with your existing Content Deployer configuration file as found in its config\ subfolder.
- Restart the microservice.
- On your installation media, navigate to \Content Delivery\expression\extension-cartridge\.
- On your target system, navigate to the library location of your Content Service or, if set up, your Session-enabled Content Service.
- If you are upgrading from SDL Tridion 2013 SP1 HR1, remove the following files, which now have new names, from your (Session-enabled) Content Service library location:
- cx_ambient.jar
- cx_api.jar
- If you are upgrading from SDL Web 8 with Cumulative Update 1 applied, remove the following files, which now have new names, from your (Session-enabled) Content Service library location:
- cx_ambient-8.1.1-1008.jar
- cx_api-8.1.1-1008.jar
- gson-2.3.1.jar
- Copy all files from the installation media subfolder lib\ into the Content Service library location, overwriting any files with the same name already present.
- Merge the contents of the installation media file config\cd_ambient_conf.xml with your existing Ambient Data Framework configuration file as found in its config\ subfolder.
- Restart the Content Service or Session-enabled Content Service.