This Quick Start Guide enables prospective Attunity customers to configure Attunity Replicate to load / replicate data from on-premises databases to Azure SQL Database and/or to Databases on Azure Virtual Machines.

The entire process can be set up in minutes and consists of the following stages:

Stage 1: Review the Prerequisites

1. Source Environment:  Windows 64-bit Server (dedicated to running 'Attunity Replicate' software)

  • Located in same local network / region as Source Database(s)
  • Will host 'Attunity Replicate' software (download made available by Attunity Sales).  
  • Minimum Hardware Requirements:  Windows Server 2008 R2, Quad-Core processor, 8 GB RAM, and 320 GB of disk space. Detailed hardware requirements are outlined in the User Guide

2. Target Environment:  Windows 64-bit Server / Azure Virtual Machine (dedicated to running 'Attunity Replicate' software)

3. Connectivity & Ports:  

  • From source Windows Server, default port is 9090 (data transfer, one-way, outbound)
  • On Windows Server / Azure VM, default port is 9090 (data transfer, one-way, inbound) 

4. Attunity Replicate Console is web-based and requires one of the following browsers:

  • Microsoft Internet Explorer Version 9 or higher
  • Mozilla Firefox Version 38 and above
  • Google Chrome

5. Database Client:  Install the relevant client (on the Windows servers, source & target environments, dedicated to hosting 'Attunity Replicate' software) to enable source database connectivity.

Source DatabaseClient
OracleOracle Instant Client for Microsoft Windows (x64) Version 11.2.0.3.0
SQL Server (2005 & higher)Microsoft SQL Server Native Client 11.0 
File name = ENU\x64\sqlncli.msi
MySQL (version 5.5 & higher)MySQL ODBC 5.2.7 64-bit client

Note: Attunity Replicate is only compatible with 64-bit ODBC provider clients and that the Azure VM has the Oracle and SQL Server drivers already installed. All other clients must be manually installed.

6. Make sure that following information about the Azure SQL DB instance is readily available:

  • DB Instance Endpoint
  • DB Instance Port
  • DB Instance Master Username & Password
  • Azure SQL Database Name
  • Necessary User Permissions for Azure SQL DB are in place

7. Licensing:

Please contact Attunity Sales for full pricing options and to enable support for the full range of heterogeneous source and target platforms.

Attunity CloudBeam for Azure Data and Analytic Services is a BYOL offering which ships with the Attunity Replicate Express license to allow you to start replicating data immediately, with the following limitations:

  • Targets: Hadoop, SQL and Oracle
  • Sources: Oracle, SQL, MySQL, Informix, Sybase ASE
  • Up to 250,000 records processed per day
  • Run one task at a given time
  • Limited in Replicate Express: No Task Scheduler, No File Transfer Service, User Profiles cannot be modified 
Stage 2: Download, Install and Configure Attunity Replicate for Source Environment

1: Attunity Sales will provide the download link for 'Attunity Replicate' if an On Premises installation is required.
2: Install 'Attunity Replicate' on the Windows Server machine (same local network as source database).

 (Back to Top)


HTTPS Security for Replicate Console

In line with current industry security standards, the Attunity Replicate web user interface enforces the use of HTTPS to protect against eavesdropping and data leakage. Using HTTPS requires a valid server certificate to be installed on the Attunity Replicate server machine.

Due to the way the HTTPS protocol works, there is no way for Attunity Replicate to automatically provide and install a valid SSL server certificate. Still, in the event that no SSL server certificate is installed, Attunity Replicate automatically generates and installs a self-signed SSL server certificate (as a temporary measure). This certificate is generated on the Replicate machine and cannot be exported or used elsewhere.

It should be noted that browsers do not consider the certificate to be valid because it was not signed by a trusted certificate authority (CA). 
When connecting with a browser to a server that uses a self-signed certificate, a warning page is shown such as this one in Chrome:

 Or this one in Firefox:

 

The warning page informs you that the certificate was signed by an unknown certificate authority. All browsers display a similar page when presented with a self-signed certificate. If you know that the self-signed certificate is from a trusted organization, then you can instruct the browser to trust the certificate and allow the connection. Instructions on how to trust the certificate vary between browsers and even between different versions of the same browser. If necessary, refer to the help for your specific browser.

Full details Security Considerations for Attunity Replicate and how to install an SSL certificate that is trusted by a CA can be found in the Attunity Replicate User Guide

Stage 3: Target Environment - Configure 'Attunity Replicate' on Azure VM

Enable File Channel Service (only Available after acquiring a Valid License from Attunity Sales):

1.  Top / Left of Console, Drop Down menu --> Select 'Server'

2.  Left menu, Select 'File Transfer Service' --> Select 'Enabled'.  


 

Create File Channel Database Source

1:  EC2 Environment:  Open Attunity Replicate and click on 'Manage Databases'. 

  • Click 'Add Database'
  • Supply a 'Name' (no spaces) ... make note of 'Name' for use within File Channel Target Configuration.  
  • Role = "Source"
  • Type = "File Channel"
  • Optional:  Supply a Staging 'Storage Folder'.  

2:  Click 'Advanced' --> Select option: "Input files are received via file transfer service". 

General Tab 

Advanced Tab

 
(Back to Top)

Create Database Target (Azure SQL Database or SQL Server on Azure VM)

1:  Azure Environment:  Open Attunity Replicate and click on 'Manage Databases'. 

  • Click 'Add Database'
  • Supply a 'Name'
  • Role = "Target"
  • Type = MS SQL
  • Connection String --> Supply value (and Port if necessary)
  • Username / Password --> Supply values
Stage 4: Source Environment - Configure 'Attunity Replicate'

Create a Database Source

Create an Oracle Source

  1. Attunity Replicate uses either Logminer or BFILE to capture changes from the Redo and Archive logs.

         The following Attunity Forum article provides details on enabling Archive Logging:
         http://forums.attunity.com/forums/replicate-console/replicate-consol-warning-no-archive-log-2792.html

  1. Attunity Replicate requires Supplemental Logging to be enabled for each Oracle source table being used for Changed Data Capture (CDC). Supplemental Logging can either be turned on by Attunity Replicate or by the DBA.

          Note: When capturing UPDATE and DELETE operations, a Primary Key or Unique Index is highly recommended to prevent performance issues.

  1. The User Account being used to connect to the Oracle Database must be granted all the Required Security Roles and Privileges described in the Attunity Replicate User Guide
     

Create a SQL Server Source

  1. Attunity Replicate accesses the Transaction Logs (TLOGS) to capture changes from the source Tables.
  2. A full database backup must be completed and the Recovery Model must be set to Full.
  3. Configure SQL Server for MS-Replication by running the Configure Distribution wizard in Microsoft’s SQL Server Management Studio.
  4. Attunity Replicate does not support SQL Server tables without a Primary Key for Changed Data Capture (CDC).
  5. The User Account being used to connect to the SQL Server Database must have the sysAdmin fixed server role defined.

Create a MySQL Source

1: Make sure that MySQL ODBC 5.2.7 64-bit client is installed on the computer where Attunity Replicate is located.

The following MySQL editions are supported:

  • MySQL Community Edition
  • MySQL Standard Edition
  • MySQL Enterprise Edition
  • MySQL Cluster Carrier Grade Edition

2: The Replicate user must have the following administrative privileges:  

  • Replication Client
  • Replication Slave
  • Super.
  • The Replicate user must also have SELECT privileges for the source tables designated for replication.

3: On MySQL Database, Enable Binary Logging.

4: Supply relevant values for:  Name, Role = Source, Type = MySQL, Server Name, Port (Default = 3306), User name, Password, Database name.  

Create a File Channel Target

1: Source Environment:  Open Attunity Replicate and click on 'Manage Databases'.

  • Click 'Add Database'
  • Supply a 'Name'
  • Role = "Target"
  • Type = "File Channel"
  • Optional:  Supply a Staging 'Storage Folder'.

2: Click 'Advanced'

  • Select option:  "Transfer Files to remote file channel".
  • Supply values for:
    • 'Remote file transfer service host'
    • 'Remote file transfer service port'
    • 'Remote file channel database name' (supply 'Name' given to Azure VM "File Channel Source".  

General Tab

Advanced Tab

Stage 5: Create, Run, and Monitor Replicate Tasks & Additional Considerations

Source Environment - Windows Server

In the source environment, create a New Task and use the following settings:
 

 

1.  Drag your source database to the 'Drop source database here' area on the right.

2.  Drag the 'File Channel' database to the 'Drop target database here' area on the right.

 

3.  Select 'Table Selection' on the right.  The 'Select Tables' window opens.  

 

 

4.  From the 'Schema' drop-down list, select a schema.  

5.  Click 'Search' to find the tables in the Schema.  You may then 'add' / 'remove' / 'add all' / 'remove all'.  Then click 'OK'.
 
4.  Click 'Run'.

Target Environment - Windows Server / Azure Virtual Machine

1. Create a 'New Task'.

2. Drag your 'File Channel' source database to the 'Drop source database here' area on the right.

3. Drag the target database to the 'Drop target database here' area on the right.

 
4. Select 'Table Selection' on the right.  The 'Select Tables' window opens.  

5. From the 'Schema' drop-down list, select a schema.  

6. Click 'Search' to find the tables in the Schema.  You may then 'add' / 'remove' / 'add all' / 'remove all'.  Then click 'OK'

7. Click 'Run'. 

8: Monitor the Task.  After you click 'Run', the display automatically switches to monitoring mode.
 

This Guide applies to both 'On-Prem to Azure' and 'Azure Cross-Region':

 To supplement this Quick Start Guide, users may also benefit from these popular resources:

 

Additional Considerations

When transferring data between 'Attunity Replicate' servers, a method called "File Channel" is used.  

  • The File-Channel endpoint does not support the use of BLOBs.
  • The File-Channel endpoint cannot carry out a full load only. You must also carry out a change-processing operation. However, you can carry out change processing only.
  • You cannot use the full-load resume function if you are using the file-channel endpoint. To resume a full-load operation, you must delete the original data and run the task again.
  • You must delete the file-channel folder before re-starting a task for change processing.

 

Dev Tool:

Request: products/cloudbeam/solutions-attunity-cloudbeam-azure-data-analytic-services
Matched Rewrite Rule: (.?.+?)(?:/([0-9]+))?/?$
Matched Rewrite Query: pagename=products%2Fcloudbeam%2Fsolutions-attunity-cloudbeam-azure-data-analytic-services&page=
Loaded Template: page.php