How to connect Acquia through SSH with SharePoint

This "how-to-connect" documentation will explain the initial configuration of an example connection from Acquia to a SharePoint Online List in Office 365. We will be synchronizing data stored in Acquia.

 

This guide presupposes that you have installed the Layer2 Cloud Connector and that you are familiar with its basic functionality. The Layer2 Cloud Connector User Documentation will provide you with all necessary information.

 

 

Contents

1. Configuring Acquia

2. Configuring the Layer2 Cloud Connector

2.1 Creating a new connection

2.2 Configuring the Data Entity 1

2.3 Configuring the Data Entity 2

2.4 Running your connection

3. Hints and known issues

3.1 Connection direction

3.2 Data model

1. Configuring Acquia

To connect to Acquia with SSH you must generate a public and private key. We used the Acquia Dev Desktop. Download it and install here. Open it and go to Acquia Dev Desktop / Preferences.

 

Acquia preferences

 

In the General tab click on Generate to create a new key pair.

 

Acquia generate

 

Save the generated key pair.

 

Acquia save key pair

 

Open your Acquia and in the desired environment go to Users & SSH Keys. Open your account page.

 

Acquia SSH page load open

 

Go to SSH Keys and add the public key you created.

 

Acquia SSH Keys

Acquia Add SSH key

 

Go back to your environment and in the Overview note the SSH URL.

 

Acquia SSH URL

 

Expand the Databases tab and go to Details.

 

Acquia Databases Information

 

Note the SSH Host, Name, Username and Password from your database.

Download and install the MySQL Connector/NET here.

Open the local folder installation from the connector. In our case C:\Program Files (x86)\MySQL\MySQL Connector Net 8.0.17\Assemblies\v4.5.2 and copy the file Renci.SshNet.dll into the Layer2 Cloud Connector Server folder. In our case C:\Program Files (x86)\Layer2 Cloud Connector\Server. Please note if you update your Cloud Connector, this file will be deleted and you must copy it into this folder again.

 

2. Configuring the Layer2 Cloud Connector

2.1. Creating a new connection

Create a new connection by using the Create New Connection option in the Actions pane (right-hand side). The new connection will appear at the bottom of the Connection Manager List (left-hand side). Click on your newly created connection to open the connection configuration settings.

 

Choose a meaningful name for your connection and replace the current "New Connection" Connection Title with it.

 

Connections to Acquia can be bi-directional. An initial connection should always be uni-directional to assure that both data entities are identical before switching to bi-directional. Therefore, choose Left to Right as Direction. You can change this setting after your initial synchronization finished successfully.

 

Step 1 Acquia connection setup.png

 

 

2.2. Configuring the Data Entity 1

We will now set up our Data Entities. Go to the data entity “Data Entity 1” to open the configuration settings.

 

Choose a Data Entity Title. It is recommended to give your entities meaningful names to maintain an overview when you decide to set up multiple connections.

 

Select the Data Provider for MySQL from the data provider list. You can search for MySQL by typing into the selection box.

 

Step 2 Acquia integration source setup.png

 

For the Connection String, we need the information mentioned in step 1. You can copy the below connection string and adjust it to match your gathered information. Use the Verify Connection String option to evaluate if the provided connection string is valid.

 

 

SshUserName=layersolutions.dev;SshHostName=free-7085.devcloud.hosting.acquia.com;Server=localhost;Port=3306;User=s296888;Database=layersolutionsdetnkqrpve;SshKeyFile=C:\Users\csantos\Desktop\id_rsa.ppk;

 

 

  • "SshUserName=yoursshusername" this value is the left side from the @ symbol in the SSH Url.
  • "SshHostName=yourhostname" this value is the right side from the @ symbol in the SSH Url.
  • "Server=localhost" this value is the address from your MySQL server in the Acquia cloud.
  • "Port=3306" this value is the default port value for the MySQL server.
  • "User=yourusername" this value is the username we get in the first step.
  • "Database=yourdatabasename" this value is the database name we get in the first step.
  • "SshKeyFile=pathtoprivatekey" this property must be set to your created private key. If you get any errors here try to change the extension from your key to .ppk

 

Enter the user's database password we get from step 1 into the Password field. The field masks the value for better security.

 

The Select Statement text box is used to define specific data queries. We will be gathering values from the node_revision__field_recipe_instruction table. You can copy the below select statement and adjust it to match your needs. Save your changes by using the right-hand pane option Save Changes.

 

SELECT * FROM layersolutionsdetnkqrpve.node_revision__field_recipe_instruction GROUP BY entity_id

 

Step 2.5 Acquia integration connection string setup.png

 

To check if all necessary columns are received, you can use the Preview Data option on the right-hand pane which will provide you with a pop-up window showing your sample data from your Acquia entity.

 

 

Preview data of Acquia integration.png

 

2.3. Configuring the Data Entity 2

We are going to send the data to a custom SharePoint Online list. It's required that you set up this list prior to the next steps. Your list should contain matching columns according to your source entity.

 

Use the left-hand pane to switch to the data entity "Data Entity 2". We will be using the Layer2 SharePoint Provider for this setup. 

 

For more information about the SharePoint provider visit:

https://www.layer2solutions.com/support/cloud-connector-faqs/layer2-csom-sharepoint-ado-net-provider.

 

You can copy the below Connection String which contains the minimum of required properties to connect to your custom SharePoint Online list.

 

URL=https://your_custom_sharepoint_list_url/AllItems.aspx;Authentication=Microsoft_Modern;

 

  • "URL=https://your_custom_sharepoint_url/AllItems.aspx;" this property defines the URL of your custom list that will be addressed.
  • "Authentication=Microsoft_Modern;" this property will determine the authentication method used. Microsoft_Modern is the default authentication method to access Microsoft Office 365 / SharePoint Online and should work in most cases, even if the SharePoint site is connected to an ADFS. This authentication does not need any further connection string settings, other than the URL of the connected system.
  • "[email protected];" this property should describe the user you wish to connect to SharePoint to. 

 

Save your changes by using the right-hand pane option Save Changes.

 

Step 3 Acquia integration target setup.png

 

In the next step, we will configure our mapping settings. Click on the Mappings option on the left-hand pane. If your fields from SharePoint are named identical to the fields from your source system, the Enable Auto Mapping option will match those columns. Disabling this option allows you to match your columns as needed. We enabled auto-mapping in our setup. Save your changes by using the right-hand pane option Save Changes.

 

Step 4 Acquia integration mapping.png

 

2.4. Running your connection

To run your connection switch back to the main connection configuration node and use the Run Now Button located on the bottom of the setup page. The Run Synchronization Toolbox will also display the synchronization process. 

 

Step 5 Acquia data integration start.png

 

Below is a data preview of the information we have access in our source entity:

 

Acquia integration ready.png

 

This will be the result in our SharePoint Online list after our initial successful synchronization:

 

Finished Acquia integration.png

If you want to use a bi-directional synchronization, you can now switch your connection direction after our first initial synchronization run finished successfully. See section 3.1 for further information.

3. Hints and known issues

 

3.1. Connection direction

As far as tested, this connection supports uni-directional as well as bi-directional synchronizations. 

 

After adjusting the direction to bi-directional, you should check your Mappings settings again because some systems might include read-only columns that cannot be mapped directly.

 

 

We also recommend choosing a Conflict Resolution that matches your environment's needs. You can find out more about the different conflict resolutions in our Layer2 Cloud Connector User Documentation.

3.2. Data model

To see all the tables use this query:

 

 

SELECT * FROM information_schema.tables WHERE table_schema = 'yourschema'

 

 

If there are more tables available, you can load them with the option "load more" in the popup window.

 

 

 

↑Top

Search for more data integration & synchronization solutions

Icon of Contact us - Chat - Layer2 leading solutions

Any Questions?

Drop us a short note with your inquiry by filling out the contact us form.

 

Icon for Layer2 Solutions Finder- Layer2 leading solutions

About the Layer2 Cloud Connector

Get more information about the Layer2 Cloud Connector on the product page.

 

 

Ifoc for free trial product regsitration - Layer2 leading solutions

Register for a free trial

Get your free trial version of the Layer2 Cloud Connector by a quick registration.