Planning Analytics

 View Only

Preparing for the Migration to Satellite Connector - Planning Analytics on Cloud

By SAMI EL CHEIKH posted 5 days ago

  

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. 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

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

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. 

2 comments
55 views

Permalink

Comments

4 days ago

I think IBM is menaging shallow the transition. 

My company uses IBM Planning Analytics in the forecast and budget process that starts in September and end in November.

In August IT and Sales Department are on holiday: we cannot menage the migration phase from August to November.

the Secure Gateway Client End date must be postponed!

Paola

4 days ago

Hi Sami,
 
to be honest, I don't think the whole approach in this story is right.
 
IBM is burdening its customers with a complex task that requires sufficient preparation time in a larger company.  As a banking company communication with systems outside our company is a delicate matter and therefore the introduction of new software for this purpose is subject to various security checks and test requirements, which take time.
Not forgetting that we also need to procure and set up new hardware, as far as I understand it (unlike the Secure Gateway Client each PA Cloud environment needs a separate Satellite Connector on its own server).
 
All this has to be done by the end of September. Right in the middle of the vacation season. And now the delivery of the necessary software has been delayed by another month. While the end date of September remains unchanged. This does not seem fair to your customers.
 
In view of these points, I would at least have expected the transition phase to be extended.
Regards,
Ralf