Overview 


This topic covers the process to request, action and go live to an upgraded release of IntraMaps in the Spatial Cloud. It will outline any actions required post upgrade and any specific configuration updates required by the organisations' Spatial Administrator(s).


The Spatial Cloud, in line with the T1 software life-cycle, supports only the last 2 releases. This necessitates an upgrade every year and if running a retired or matured release you will be required to upgrade. See the Software Support Maturity & Retirement Dates Customer Community article for more information.


For Spatial Only Customers


Customers running IntraMaps only and no other T1 product or solution will be automatically upgraded to the latest release within 6-8 weeks of the general release date, occurring around November and May each year.

See the Software Support Maturity & Retirement Dates Customer Community article for more information.


For CiA Customers


If you are a T1 SaaS customer (running any CiA product or solution) with a Spatial Cloud configuration, this will be triggered at the same time as your SaaS CiA upgrade. If you believe this has not been actioned for your organisation please contact your business unit responsible for working on CiA upgrades who can then raise a case if required. 

It is strongly recommended spatial administrators work closely with the team in their organisation responsible for CiA upgrade scheduling and sign off. 


Your existing configuration is upgraded as is to a {site}-upgrade.spatial.t1cloud.com environment. For example a customer with a site name of RIVERCITY would get a RIVERCITY-UPGRADE environment. This allows for any acceptance testing your organisation requires prior to going live with the new release. As this is a like for like upgrade the configuration will be as functional as your existing live configuration. If something doesn't work in your live version, it will also be non functional in the upgrade configuration.


The upgrade does not create, copy or modify any of your existing data and affects configuration only.


Your Spatial Cloud upgrade environment will be made available at the same time as your UAT CiA environment is upgraded. Your upgraded Spatial Cloud go live will coincide with your CiA Prod go live on the upgraded release. You cannot go live with CiA and not Spatial Cloud and vice versa, the release versions must always match.


The process of going live on the latest release will deploy your tested upgrade configuration to your production URL - {site}.spatial.t1cloud.com. 

As the upgrade configuration runs side by side with the existing production configuration, any changes made to your production config will also need to be made to the upgrade config to keep the two in sync for go live on the latest release.



Post Upgrade Tasks and Considerations


  • Download the upgrade ConfigManager provided and extract it to a location of your choice. It is recommended it be run on your local machine in a folder that indicates it is the UPGRADE version. DO NOT extract the new ConfigManager files over your current production ConfigManager files.

  • If using Azure Active Directory as an Identity Provider you will need to ensure the upgrade URLs (using the {site}-upgrade.spatial.t1cloud.com host name) are added to your Azure AD App registration. For more information see the Azure Active Directory URLs page. There is no need to create a new\separate AzAD app registration.


  • To test maps published for WMS\WFS you will need to update the Online Resource URL to use the new {site}-upgrade.spatial.t1cloud.com host name. Once updated you will also need to Publish to OWS in MapManager. For more information see the Publishing OWS data sources page


  • A reminder the upgrade is of configuration only. You can make changes to maps, spatial catalogue, layer templates, CiA integration URLs and IntraMaps configuration without impacting production configuration. However, any changes to the underlying data will be reflected in both production and upgrade configurations.

Go Live on New Release


  • Launch your Production ConfigManager and you will be alerted to download the latest version and be redirected to the ConfigManager download page. Once downloaded delete your existing Production ConfigManager folder and extract the new version in its place. DO NOT extract the new ConfigManager files to replace existing files as this can result in files from mixed releases and prevent proper function.

  • Any maps published for WMS\WFS will need to ensure the Online Resource URL uses the production host name {site}.spatial.t1cloud.com. You will also need to Publish to OWS in MapManager. For more information see the Publishing OWS data sources page