Migrate from Exalate on premises to Exalate Cloud

 
2
1
0

Hello,


We have Jira Data Center with the Exalate addon, Exalate application on it own server inside a docker container, and ServiceNow.


We want to add Salesforce to the picture. From the documentation at https://docs.idalko.com/exalate/display/ED/Salesforce it seems there is no on-premises option for Salesforce. There is no page documenting how to install Exalate on your own server, as in ServiceNow (https://docs.idalko.com/exalate/display/ED/Install+Exalate+for+ServiceNow+on+your+own+server) and in HP ALM/QX (https://docs.idalko.com/exalate/pages/viewpage.action?pageId=19630792). 


  1. Can anyone confirm that we need to use Exalate Cloud for Jira - Salesforce integration?

  2. How is the license model here? There is no documentation about Exalate Cloud vs Exalate on-premises at https://docs.idalko.com/exalate/display/ED/Pricing+and+licensing

  3. Can we reuse the license we already have for Exalate on-premises server in the Exalate Cloud?



I am attaching a picture with the current and future status for more clarity.


Thanks,


Enrique


    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      Hello, Enrique Cadalso 


      1. The officially supported version is, indeed the cloud version for Exalate for Salesforce.
        However, you may try to deploy Exalate for SF the same way as described in docs for Exalate for ServiceNow, but using the image from idalko/salesforcenode:5.2.2

        1. for authentication, please try creating a connected app, and then
          use the access token, refresh token, client id, client secret to populate the general settings.
          if the option to upsert them through UI is not possible,
          insert the following structure into general_settings table:

          id           | 1
url          | https://AAA.my.salesforce.com
exalate_url  | https://salesforcenode-BBB.exalate.cloud
instance_uid | 
field_values | {"access_token":"CCC","refresh_token":"DDD","client_secret":"EEE","orgtype":"Production","client_id":"FFF"}
      2. How is the license model here? There is no documentation about Exalate Cloud vs Exalate on-premises
        Licensing in Exalate is not different depending on the deployment type
      3. Can we reuse the license we already have for Exalate on-premises server in the Exalate Cloud?
        Kind of - I'd suggest to request a separate license key for every separate Exalate instance.

      Please, let me know, how it goes.

      UPDATE:

      Hence my question if we can use the license on the Exalate on-premises (for ServiceNow)

      You can exchange the license you have via Mariia Onyshchenko without any additional charge.

      Can you confirm that we can use Exalate Cloud to connect to both ServiceNow and Salesforce,


      Yes, you may host Exalate for Snow and Exalate for Salesforce in Exalate Cloud.

      as on the diagram

      No, I'm afraid, at the moment Exalate has a single-tenant architecture, which means one web application, one DB one sandbox per customer (to ensure security for scripting).


      Do we need two "instances" of Exalate Cloud in this case?

      Yes, exactly so.


      Regards, Serhiy.

      1. Enrique Cadalso

        Hi Serhiy,


        We don't want to configure another Exalate server on-premises because there is no point in maintaining two Exalate servers on-premises if we can use Exalate Cloud for both ServiceNow and Salesforce. Hence my question if we can use the license on the Exalate on-premises (for ServiceNow). If we cannot, and a new license is required, then I assume the price is the same (Exalate on-prem vs Exalate Cloud).


        Can you confirm that we can use Exalate Cloud to connect to both ServiceNow and Salesforce, as on the diagram?

        Do we need two "instances" of Exalate Cloud in this case?


        Thanks,


        Enrique

      2. Serhiy Onyshchenko

        Hello, Enrique Cadalso , updated my answer, please review ☝️

      3. Enrique Cadalso

        Thanks! That answers all my questions.


      CommentAdd your comment...