{"id":11858,"date":"2021-10-26T00:00:16","date_gmt":"2021-10-26T07:00:16","guid":{"rendered":"https:\/\/www.couchbase.com\/blog\/?p=11858"},"modified":"2024-03-01T09:10:09","modified_gmt":"2024-03-01T17:10:09","slug":"your-guide-to-syncing-data-between-couchbase-and-relational-databases-with-gluesync","status":"publish","type":"post","link":"https:\/\/www.couchbase.com\/blog\/your-guide-to-syncing-data-between-couchbase-and-relational-databases-with-gluesync\/","title":{"rendered":"Your Guide to Syncing Data between Couchbase and Relational Databases with GlueSync"},"content":{"rendered":"\r\n

Introduction<\/span><\/h2>\r\n\r\n\r\n\r\n

Are you modernizing your development process? Are you following a rapid development approach to deliver higher quality and more frequent capabilities to your customers? Part of that process often requires us to work with multiple databases for a transition period when we need both databases available. We need a way to sync the data between the databases, the more seamlessly, the better. Using Couchbase with GlueSync<\/a><\/span> fits that purpose.\u00a0<\/span><\/p>\r\n\r\n\r\n

\r\n\r\n\r\n

GlueSync allows you to replicate data to and from RDBMS (Microsoft SQL Server and Oracle) in real time with Couchbase.<\/span><\/em><\/p>\r\n\r\n\r\n

\r\n\r\n\r\n

We\u2019ll use Docker in this post as we go through the steps to setup and configure Couchbase, Microsoft SQL Server, and GlueSync, demonstrating the syncing of data between the two.<\/span><\/p>\r\n\r\n\r\n\r\n

Before We Get Started<\/span><\/h2>\r\n\r\n\r\n\r\n

Docker<\/span><\/h3>\r\n\r\n\r\n\r\n

First, this tutorial uses Docker and if you don\u2019t have Docker, you can find more information here <\/span>https:\/\/www.docker.com\/<\/span><\/a>. You\u2019ll need to install Docker to complete the steps below.<\/span><\/p>\r\n\r\n\r\n\r\n

GlueSync<\/span><\/h3>\r\n\r\n\r\n\r\n

Next, GlueSync requires a license. To complete this tutorial, you\u2019ll need a license from the GlueSync team. You can go to <\/span>https:\/\/gluesync.com\/plans\/<\/span><\/a> and view more info on their plans and <\/span>https:\/\/gluesync.com\/contact-sales\/<\/span><\/a> to contact the GlueSync team.<\/span><\/p>\r\n\r\n\r\n\r\n

High-level Steps<\/span><\/h2>\r\n\r\n\r\n\r\n
    \r\n
  1. Run and Configure Couchbase and MSSQL<\/span><\/a><\/li>\r\n
  2. Create the configuration file for GlueSync<\/a><\/span><\/li>\r\n
  3. Configure and Run GlueSync for Couchbase to MSSQL<\/span><\/a><\/li>\r\n
  4. Watch the magic<\/a><\/span><\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n

    Run Couchbase and MSSQL<\/span><\/h2>\r\n\r\n\r\n\r\n

    Couchbase<\/span><\/h3>\r\n\r\n\r\n\r\n

    We\u2019ll use Couchbase 6.6.3 for this tutorial. The following Docker command will get Couchbase up and running, exposing the ports we need.<\/span><\/p>\r\n\r\n\r\n\r\n

    docker run -d --name cb-663 -p 8091-8096:8091-8096 -p 11210-11211:11210-11211 couchbase:enterprise-6.6.3<\/pre>\r\n\r\n\r\n\r\n
    MSSQL<\/span><\/h3>\r\n\r\n\r\n\r\n
    For the MSSQL Docker run command, notice we\u2019re including the SA password. Update that and make a note of it, we\u2019ll use it later.<\/span><\/p>\r\n\r\n\r\n\r\n
    docker run -d --name mssql -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=RandomMSSQLPass2!' -p 1433:1433 -d mcr.microsoft.com\/mssql\/server:2019-CU10-ubuntu-20.04<\/pre>\r\n\r\n\r\n\r\n
    Verify Containers<\/span><\/h3>\r\n\r\n\r\n\r\n
    Now you should have two containers running, Couchbase and MSSQL. We’ll start the GlueSync container after we get these configured.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n
     <\/p>\r\n\r\n\r\n\r\n
    Configure Couchbase with GlueSync and MSSQL<\/span><\/h2>\r\n\r\n\r\n\r\n\r\n\r\n
    We\u2019ll start with Couchbase and do a basic installation.<\/span><\/p>\r\n\r\n\r\n\r\n
    Setup New Cluster<\/span><\/h3>\r\n\r\n\r\n\r\n
    Running the Docker commands above would have started Couchbase and exposed the ports so you can open<\/span> the Couchbase UI by going to <\/span>https:\/\/localhost:8091\/ui\/index.html<\/span><\/a>.<\/span><\/p>\r\n\r\n\r\n\r\n
    We\u2019ll choose <\/span>Setup New Cluster<\/b> and set up a cluster of one node (not recommended for production, but works great for dev and doing a tutorial).\u00a0<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    Enter the new cluster information and click <\/span>Next: Accept Terms<\/b>. Make a note of your password, we\u2019ll need it later. We\u2019re using <\/span>RandomCBPass2!<\/b> for this instance.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    If you accept the terms and conditions, check that option, and click <\/span>Finish With Defaults<\/b>.<\/span><\/p>\r\n\r\n\r\n\r\n
    NOTE<\/b> GlueSync works with Couchbase using a couple of Couchbase technologies, Sync Gateway and the Eventing service. We are using the Eventing option in this tutorial. The Eventing feature will be installed with the <\/span>Finish With Defaults<\/b> selection below.\u00a0<\/span><\/p>\r\n\r\n\r\n
    \r\n\r\n\r\n
    Couchbase offers a single install where you can enable all the services or pick and choose to customize to the needs of your project. This tutorial will install all the services for convenience. Learn more<\/a> about Couchbase services and multi-dimensional scaling<\/span>.\u00a0\u00a0<\/span><\/em><\/p>\r\n\r\n\r\n
    \r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    You should be redirected to the Dashboard. We will use data from the sample bucket in this tutorial. To install the data, click <\/span>Sample Buckets<\/b>.<\/span><\/p>\r\n\r\n\r\n\r\n
    If, for some reason, you don\u2019t see the <\/span>Sample Bucket<\/b> link on the dashboard, go to <\/span>Settings <\/b>from the left menu, look near the top right of the UI, and you\u2019ll see a menu item for <\/span>Sample Buckets<\/b>, as shown below.\u00a0<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    Check beer-sample and click <\/span>Load Sample Data<\/b>.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    Give it a few minutes to load, then click <\/span>Buckets<\/b> in the navigation on the left.<\/span><\/p>\r\n\r\n\r\n\r\n
    \u00a0<\/span>You should see the beer-sample bucket we just loaded.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    Let’s view the documents. Click the <\/span>Documents<\/b> link on the right, next to <\/span>Statistics<\/b>.<\/span><\/p>\r\n\r\n\r\n\r\n
    We’re going to sync documents of type beer. You can put a filter (type=”beer”) in the N1QL WHERE box and click <\/span>Retrieve Docs<\/b> to get those documents; it’ll be a little easier to see and test this way.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n
     <\/p>\r\n\r\n\r\n\r\n
    Create Couchbase User<\/h3>\r\n\r\n\r\n\r\n
    We\u2019ll create a user for the GlueSync application to use. This is for tutorial purposes and you should follow your security practices when managing your users in conjunction with Couchbase and GlueSync requirements.<\/span><\/p>\r\n\r\n\r\n\r\n
    Go to the <\/span>Security<\/b> link on the left then click <\/span>ADD USER<\/b> in the top right.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    Fill out the user information, as shown below. We\u2019re using the Username of <\/span>cb-user<\/b> and Password <\/span>RandomCBPass2!<\/b>; keep this info for later. Make sure you check <\/span>Full Admin<\/b> under the roles. Once it\u2019s filled out, click the <\/span>Add User<\/b> button.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    You should see the user we just created.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n
     <\/p>\r\n\r\n\r\n\r\n
    Add a GlueSync Metadata bucket<\/span><\/h3>\r\n\r\n\r\n\r\n
    GlueSync uses Couchbase\u2019s Eventing service. Eventing requires a Metadata bucket, and we\u2019ll create one now. Get more info<\/a> on GlueSync and the Metadata bucket.<\/span><\/p>\r\n\r\n\r\n\r\n
    Go to <\/span>Buckets <\/b>on the left menu and click <\/span>ADD BUCKET<\/b> in the top right.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    Enter the Metadata Name and click <\/span>Add Bucket<\/b>. We\u2019ll use the defaults for the other options.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    You should see two buckets now.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n
     <\/p>\r\n\r\n\r\n\r\n
    MSSQL<\/span><\/h2>\r\n\r\n\r\n\r\n
    We\u2019ll use SQL Server Management Studio to configure MSSQL, which was installed in the step above. If you need to install the management studio, you can find it here<\/a>.<\/span>\u00a0<\/b><\/p>\r\n\r\n\r\n\r\n
    Login with the credentials passed to the Docker command from the earlier step, in this case, Login: <\/span>sa<\/b> and Password: <\/span>RandomMSSQLPass2!<\/b>.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n
     <\/p>\r\n\r\n\r\n\r\n
    Create New Database<\/span><\/h3>\r\n\r\n\r\n\r\n
    We\u2019ll create a new database where the data from Couchbase will be loaded.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    In this case, since I\u2019m very creative, I\u2019ll use <\/span>cb<\/b>, and choose Ok.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n
     <\/p>\r\n\r\n\r\n\r\n
    Create Login<\/span><\/h3>\r\n\r\n\r\n\r\n
    Next, create a MSSQL Login. Right-click the Login folder and choose <\/span>New Login\u2026<\/b>.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    The Login name we\u2019re using is <\/span>mssql-user <\/b>and Password is <\/span>RandomMSSQLUserPass2!<\/b>.<\/span><\/p>\r\n\r\n\r\n\r\n
    Set Default database to <\/span>cb<\/b>, the database created above.<\/span><\/p>\r\n\r\n\r\n\r\n
    You should follow your security standards when creating users. The instructions in this article\u00a0 are for tutorial purposes only and some options I\u2019m picking are for simplicity. <\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    Go to <\/span>User Mapping<\/b>, on the left under <\/span>Select a page<\/b>, and select <\/span>cb <\/b>under <\/span>Users mapped to this login<\/b> and <\/span>db_owner<\/b> under the <\/span>Database role membership<\/b>.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    Now that we\u2019ve got that setup, verify you can login with the user. Log out of sa and log back in with the new user.<\/span><\/p>\r\n\r\n\r\n\r\n
    Create Table<\/span><\/h3>\r\n\r\n\r\n\r\n
    Let\u2019s create a table for the data to be synced to, from Couchbase. Go to the <\/span>Databases<\/b>, then <\/span>cb<\/b>, then open a <\/span>New Query<\/b> window. The table fields in this table match the attributes in the Couchbase beer-samples document. The SQL to create the table is below.<\/span><\/p>\r\n\r\n\r\n\r\n
    \"\"<\/figure>\r\n\r\n\r\n\r\n
    Run the create table statement.<\/span>\u00a0<\/span><\/p>\r\n\r\n\r\n\r\n
    \r\n
    create\u00a0table\u00a0beer\r\n(\r\n \u00a0\u00a0\u00a0name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0varchar(200)\u00a0\u00a0not\u00a0null\u00a0constraint\u00a0beer_pk\u00a0primary\u00a0key\u00a0nonclustered,\r\n \u00a0\u00a0\u00a0abv\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0numeric(5,\u00a02)\u00a0not\u00a0null,\r\n \u00a0\u00a0\u00a0brewery_id\u00a0\u00a0varchar(max)\u00a0\u00a0not\u00a0null,\r\n \u00a0\u00a0\u00a0category\u00a0\u00a0\u00a0\u00a0varchar(max),\r\n \u00a0\u00a0\u00a0description\u00a0varchar(max)\u00a0\u00a0not\u00a0null,\r\n \u00a0\u00a0\u00a0ibu\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0int\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0not\u00a0null,\r\n \u00a0\u00a0\u00a0srm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0int\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0not\u00a0null,\r\n \u00a0\u00a0\u00a0style\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0varchar(max),\r\n \u00a0\u00a0\u00a0upc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0int\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0not\u00a0null,\r\n \u00a0\u00a0\u00a0updated\u00a0\u00a0\u00a0\u00a0\u00a0varchar(max)\u00a0\u00a0not\u00a0null\r\n)\r\ngo<\/pre>\r\n<\/div>\r\n\r\n\r\n\r\n
    Configure and Run GlueSync for Couchbase to MSSQL<\/span><\/h2>\r\n\r\n\r\n\r\n
    GlueSync has two components, one for Couchbase to MSSQL, and another for MSSQL to Couchbase. This will set up the application to sync data from Couchbase to MSSQL. Setting up the other direction is a very similar setup.\u00a0 \u00a0<\/span><\/p>\r\n\r\n\r\n\r\n
    Make config folder<\/span><\/h3>\r\n\r\n\r\n\r\n
    Make a folder for the GlueSync configuration file. We’ll share this with the Docker container when starting it.<\/span><\/p>\r\n\r\n\r\n\r\n
    \r\n
    mkdir\u00a0c:\\a\\gluesync\\config<\/pre>\r\n
    \u00a0<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n
    Get Docker network IP addresses for Couchbase and MSSQL<\/span><\/h3>\r\n\r\n\r\n\r\n
    We need the Docker network information for the Couchbase and MSSQL containers to configure GlueSync.<\/span><\/p>\r\n\r\n\r\n\r\n
    Get the container IDs.<\/span><\/p>\r\n\r\n\r\n\r\n
    \r\n
    C:\\Users\\David\u00a0Elliott>\u00a0docker\u00a0container\u00a0ls\u00a0-a\r\nCONTAINER ID\u00a0\u00a0\u00a0IMAGE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0COMMAND\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0CREATED\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0STATUS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0PORTS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0NAMES\r\n10b985792024\u00a0\u00a0\u00a0mcr.microsoft.com\/mssql\/server:2019-CU10-ubuntu-20.04\u00a0\u00a0\u00a0\"\/opt\/mssql\/bin\/perm\u2026\"\u00a0\u00a0\u00a034 minutes ago\u00a0\u00a0\u00a0Up 34 minutes\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a00.0.0.0:1433->1433\/tcp, :::1433->1433\/tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0mssql\r\nd2df1bad1647\u00a0\u00a0\u00a0couchbase:enterprise-6.6.3\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"\/entrypoint.sh couc\u2026\"\u00a0\u00a0\u00a040 minutes ago\u00a0\u00a0\u00a0Up 40 minutes\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a00.0.0.0:8091-8096->8091-8096\/tcp, :::8091-8096->8091-8096\/tcp, 11207\/tcp, 0.0.0.0:11210-11211->11210-11211\/tcp, :::11210-11211->11210-11211\/tcp, 18091-18096\/tcp\u00a0\u00a0\u00a0cb-663<\/pre>\r\n<\/div>\r\n\r\n\r\n\r\n
    \r\n
    Now, get the IP addresses for the containers using those IDs by using the Docker Inspect command on Couchbase.<\/p>\r\n<\/div>\r\n\r\n\r\n\r\n
    \r\n
    C:\\Users\\David\u00a0Elliott>\u00a0docker\u00a0inspect\u00a0d2df1bad1647\u00a0|\u00a0Select-String\u00a0IPAddress\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"SecondaryIPAddresses\":\u00a0null,\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"IPAddress\":\u00a0\"172.17.0.2\",\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"IPAddress\": \"172.17.0.2\",<\/pre>\r\n
    Run the Docker Inspect command on MSSQL.<\/span><\/p>\r\n<\/div>\r\n\r\n\r\n\r\n
    \r\n
    \r\n
    C:\\Users\\David\u00a0Elliott>\u00a0docker\u00a0inspect\u00a010b985792024\u00a0|\u00a0Select-String\u00a0IPAddress\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"SecondaryIPAddresses\":\u00a0null,\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"IPAddress\":\u00a0\"172.17.0.3\",\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"IPAddress\":\u00a0\"172.17.0.3\",<\/pre>\r\n<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n
    The IP addresses are:<\/span><\/p>\r\n\r\n\r\n\r\n