Skip to Content

16 Comments

You must be Logged on to comment or reply to a post.

  1. Simen Huuse

    Hi Meghna! This is great, thank you so much for your post.

    We have a scenario where we want to connect C4C to a backend SAP ERP, and I’m thinking that the cloud connector might do the trick. We know which HCI account we wish to use, but my question is then: Do we connect the SCC to SCP or to HCI? I’m finding it hard to understand the technical relations between a Cloud Integration account and a SCP account 🙂

    Best regards,

    Simen

    (0) 
    1. Meghna Shishodiya
      Post author

      The Cloud Connector needs to be configured with the Cloud Platform. Cloud Platform Integration takes the information about the configured cloud connectors from the platform – in case multiple cloud connectors are configured with the same Cloud Platform account, the location ID parameter can be used. I hope this clarifies.

       

       

      (1) 
  2. Former Member

    Hi Meghna thank you for your post,

     

    I dont know where we should install de Cloud Connector or what should be the best practice for this… should we install it in the same place as the on-premise system (i.e. the same server/machine/vm) or we should get an additional Machine for this?

     

    thank you again,

    Mike

     

    (0) 
    1. Midhun VP

      Hi Mike,

      I would suggest you install it on a separate server rather than installing it on a server with other software though technically there are no restrictions to do it. But, if you have a dedicated server for SCC it is not affected if you need a downtime for other software updates.

      You can find sizing guide here: https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e23f776e4d594fdbaeeb1196d47bbcc0.html

      Thanks Midhun

      Customer Success team

       

      (2) 
      1. Meghna Shishodiya
        Post author

        As pointed by Midhun, as the SAP Cloud Connector connects to multiple backend systems, there should be a separate host used for it.

        Also, to add, we recommend to setup the Cloud Connector on a system located in the DMZ. However, a setup directly in the network of the attached systems is also ok.

        (0) 
  3. Gunnlaugur Th Einarsson

    Hi Meghna.

    Regarding this note “Note that even if you are using https between SCC and the back-end system, you need to use http on the URL for the iflow. This is however not a security risk since the Cloud Connector proxy / connectivity agent runs on the same application VM.

    Any thoughts or experience if this is needed using the LDAP adapter?

    Regards,

    Gulli

    (0) 
    1. Meghna Shishodiya
      Post author

      Hello Gulli,

      Connecting to an LDAP server using the LDAP adapter of Cloud Platform Integration can only happen via the Cloud connector – this is mandatory.

      Thanks and Regards,
      Meghna

      (0) 
  4. Jens Schwendemann

    Meghna / all

     

    with interest I saw that you could specify the location ID in a SOAP receiver channel. We are to integrate standard content that uses IDoc as receiver channel. However, there seems no field for location ID with that channel type. Is this a missing functionality or not possible due to technical reasons?

     

    Cheers

    Jens

    (0) 
      1. Jens Schwendemann

         

        Thanks for coming back 🙂 This is good news (I think it has been available for some time now, however, not at the time of the initial post). SAP seems to be getting there, though still some rough edged on CPI that need to be smoothened out.

         

        Cheers

        Jens

        (0) 
  5. Former Member

    Hi Meghna, thank you for your post

    It is possible to install the SAP Cloud Connector in the same server where the Saprouter is installed?, what are the technical problems we will experience if we install the SAP Cloud connector in the same server?

    Or it is strongly recommended that install it in a separate server?

     

    regards

     

    William

    (0) 
  6. Manjunath Nataraj

    Hi Meghana

     

    W.r.t this step ,

    Select the entry you have created. Under “Resources Accessible on …” click on “Add…” and configure the path(s) that should be accessible on the internal host (from the virtual host). For all, use “/”.

     

    Along with can we add like ”  /#/site ” as white-listing  to a on premise system ?

     

    It is throwing errors as “/#/site is not a valid path”  .

     

    What are the special characters allowed ? Do we any help documentation ?

     

    Thanks in advance .

     

    Regards

    Manjunath

    (0) 

Leave a Reply