SAP Knowledge Base Article - Public

2965124 - Landscape domain update of all SAP Analytics Cloud (SAC) CN1 tenants on sapanalytics.cloud or sapbusinessobjects.cloud domains

Symptom

  • To ensure the best possible server stability of your SAP Analytics Cloud (SAC) system hosting on CN1 data center, we will be internally updating the current landscape domain:

Environment

  • SAP Analytics Cloud (Enterprise) 2020.20 for fast-track tenants
  • SAP Analytics Cloud (Enterprise) 2020.14.21 for QRC tenants
  • CN1 data center
  • sapanalytics.cloud domain or sapbusinessobjects.cloud domain

Cause

This update of platform URLs will secure continued access to your SAP Analytics Cloud, so you can experience all the upcoming product updates planned for future releases. With this change, we hope to improve your product experience.

Resolution

System Administrators are required to take action as below:

  • Please perform any necessary updates on your side (bookmarks, firewalls, reverse proxies, etc).

  • Please whitelist the following URLs if you have a whitelist for public URLs:
    • cn1.sapanalyticscloud.cn
    • authn.cn1.platform.sapcloud.cn
    • cloudanalytics-cn.accounts.sapcloud.cn
    • sapui5.cn1.platform.sapcloud.cn

  • If you are using Analysis Office (AO) to access SAC:
    => you will need to update your SAC URL to use the new URL in Analysis Office.

  • If your tenant has oauth clients defined:
    => The OAuth authorization and token URLs will be updated to use a new domain. You can check the System Administration > App Integration tab to see the new URLs and then update your clients to use the new URLs.
          For example:
          https://oauthasservices-xxx.cn1.hana.ondemand.com/oauth2/api/v1/authorize → https://oauthasservices-xxx.cn1.platform.sapcloud.cn/oauth2/api/v1/authorize
          https://oauthasservices-xxx.cn1.hana.ondemand.com/oauth2/api/v1/token → https://oauthasservices-xxx.cn1.platform.sapcloud.cn/oauth2/api/v1/token

  • If your tenant has a custom IdP enabled:
    => There are some changes to the SAP Analytics Cloud SAML service provider metadata, so please download the current metadata XML file in the System Administration > Security tab and then upload to your IDP.
    => Please also note the redirection URLs have changed to https://authn.cn1.platform.sapcloud.cn/, so please update this in your infrastructure if necessary.

  • If your tenant is using an SDI Connection:
    => The domain name of the HANA server will be updated with a new domain that is under the .cn top level domain.  In order for your on-premise SDI Data Provisioning agent to continue to work, the following steps need to be taken:
    1. Stop your SDI Data Provisioning agent.
    2. Edit the dpagentconfig.ini  file under your SDI Data Provisioning agent installation folder.
    3. Modify the hana.server  property to point to the new domain name.  For example, you would change "server.cn1.hana.ondemand.com" to "server.cn1.platform.sapcloud.cn".
    4. Save dpagentconfig.ini.
    5. Start your SDI Data Provisioning agent.

  • if your tenant is using a live connection to:
    • S/4HANA cloud
      1. Edit existing connection, download the current certificate from connection dialog.
      2. In S/4HANA cloud system, find 'Communication System' created before. Update 'Host Name', 'Provider Name' (if get changed after migration), re-upload current certificate
    • HANA on SAP Cloud Platform with SAML (HCP)
      1. Edit existing connection, download the current metadata from connection dialog.
      2. In the XS Admin page of your SAP HANA system, select 'SAML Identity Provider', find your tenant's SAML provider configuration, re-upload new metadata file.
    • HANA Tunnel
      1. Edit existing connection, download the current metadata from connection dialog.
      2. In the XS Admin page of your SAP HANA system, select 'SAML Identity Provider', find your tenant's SAML provider configuration, re-upload new metadata file.
      3. Setting in cloud connector (system mapping, principle propagation sync) should keep same, if subaccount needs to be re-created, these settings need to be added back.
    • HANA with Advanced section enabled (Mobile)
      1. Edit existing connection, download the current metadata from connection dialog.
      2. In the XS Admin page of your SAP HANA system, select 'SAML Identity Provider', find your tenant's SAML provider configuration, re-upload new metadata file.
      3. Setting in cloud connector (system mapping, principle propagation sync) should keep same, if subaccount need to be re-created, these settings need to be added back.
    • Direct - only for customers with tenant url change after migration, and customer specify SAC URL in whitelist of allowed origins
    • HANA on SAP Cloud Platform deployed on CN landscape
      • Perform the following action for existing live connections only
        1. Edit existing live connections.
        2. Change Landscape back to CN1.
        3. re-input username/password if need.
        4. Save connection.

  • If the tenant is using Cloud Connector for import data connection
    => The region host of your subaccount will be changed to cn1.platform.sapcloud.cn, so you need to reestablish Cloud Connector setup.
    => Before you proceed, check your Cloud Connector connectivity status and backup existing subaccount Access Control settings.

    Steps:
    1. Go to SAC, System > Administration > Datasource Configuration. Obtain the updated region host value.
    2. Go to Cloud Connector. Click Add Subaccount and use information provided in Self-Service UI.
    3. After successful connection creation, click Cloud To On-Premise to configure Access Control.
    4. Click Import System setting button. Change Source to Subaccount then pick the subaccount prior to CN1 migration. Then complete Import; this will copy all mappings from one subaccount to current subaccount.
    5. Repeat the procedure if you have setup Multi-Location Cloud Connector.

      Note:
      a) In your existing Cloud Connector, Select Region dropdown during Add Subaccount workflow may only have the existing/old China region host value, "cn1.hana.ondemand.com".  You may have to manually input the new value or download a later version of Cloud Connector. 
      b) If your Cloud Connector is behind a strict firewall, you will need to reconfigure IP restrictions.

See Also

Your feedback is important to help us improve our knowledge base.

Keywords

SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, sap analyst cloud, connected, failure, stopped , KBA , LOD-ANA-AUT , SAC Authentication / Login , Product Enhancement

Product

SAP Analytics Cloud 1.0