Due to the complex integrated nature of the bundled experience with Planning Analytics and Satellite Connector, our teams are taking extra care to ensure the implementation and migration approach from Secure Gateway to Satellite Connector are as seamless as possible across a variety of customer use cases. We are now targeting an August 2024 delivery of Satellite Connector in Planning analytics on Cloud with removal of the ability to create new connections and gateways by the end of 2024. We are conscious of the Secure Gateway end of support date in October and are confident that our migration utility will help minimize the work needed to adopt Satellite Connector.
As we enter the final stages prior to the Satellite Connector implementation in Planning Analytics on Cloud, we wanted to share a few tips to prepare for the move that can help simplify the migration process.
1. Clean up your gateways - test relevant gateways you want to migrate and delete unnecessary gateways
2. Review the environment requirements for Satellite Agent:
1. Satellite Connector overview | IBM Cloud Docs
2. Migration from from Secure Gateway to Satellite Connector
3. End of Support for Secure Gateway FAQ
4. Configuring Satellite Connector for PA on Cloud
3. Review the appropriate host names and the Satellite Connector Datacenter configuration per customer deployment region table below
|
Current Customer Datacenter
|
Compatible Satellite Connector Datacenter
|
|
Montreal, Canada
|
Toronto, Canada
Host Name :
c-01-ws.ca-tor.link.satellite.cloud.ibm.com, api.link.satellite.cloud.ibm.com
iam.cloud.ibm.com
Protocol and ports :
HTTPS 443
|
|
|
|
|
Amsterdam, Netherlands
|
Frankfurt, Germany
Host Name :
c-01-ws.eu-de.link.satellite.cloud.ibm.com, api.link.satellite.cloud.ibm.com
iam.cloud.ibm.com
Protocol and ports :
HTTPS 443
|
|
|
|
|
Washington DC, USA
|
Washington DC, USA
Host Name :
c-01-ws.us-east.link.satellite.cloud.ibm.com, api.link.satellite.cloud.ibm.com
iam.cloud.ibm.com
Protocol and ports :
HTTPS 443
|
|
|
|
|
San Jose, California, USA
|
Dallas, Texas, USA
Host Name :
c-01-ws.us-south.link.satellite.cloud.ibm.com, api.link.satellite.cloud.ibm.com
iam.cloud.ibm.com
Protocol and ports :
HTTPS 443
|
|
|
|
|
Sydney, Australia
|
Sydney, Australia
Host Name :
c-01-ws.au-syd.link.satellite.cloud.ibm.com, api.link.satellite.cloud.ibm.com
iam.cloud.ibm.com
Protocol and ports :
HTTPS 443
|
|
|
|
|
Frankfurt, Germany
|
Frankfurt, Germany
Host Name :
c-01-ws.eu-de.link.satellite.cloud.ibm.com, api.link.satellite.cloud.ibm.com
iam.cloud.ibm.com
Protocol and ports :
HTTPS 443
|
|
|
|
|
Singapore
|
Tokyo, Japan:
Host Name :
c-01-ws.jp-tok.link.satellite.cloud.ibm.com, api.link.satellite.cloud.ibm.com
iam.cloud.ibm.com
Protocol and ports :
HTTPS 443
|
Thank you for taking the time to read this update. We will share more information on the migration to Satellite Connector as we get closer to general availability of the implementation.