[
https://issues.apache.org/jira/browse/AMBARI-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Barca updated AMBARI-7929:
----------------------------------
Attachment: AMBARI-7929.0.patch
> Automate the installation of the SQL Server JDBC driver
> -------------------------------------------------------
>
> Key: AMBARI-7929
> URL: https://issues.apache.org/jira/browse/AMBARI-7929
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: branch-windows-dev
> Environment: Windows Server 64-bit
> Reporter: Florian Barca
> Assignee: Florian Barca
> Fix For: branch-windows-dev
>
> Attachments: AMBARI-7929.0.patch
>
>
> The SQL Server JDBC driver is only available as a self-extracting GUI
> application, which is unsuitable for download and install via the Ambari
> services. The styrategy to overcome this limitation is as follows:
> 1. Require the user to install the SQL Server JDBC Driver manually. This will
> comply to the EULA, and will give us green light to distribute the bits to
> all the machines in the cluster.
> 2. Pick up the bits and save them in the Server's resources directory.
> 3. The Agent will download the bits from the resources directory, and drop
> them on the machine in a standard directory, where they will be visible to
> all the components in the HDP stack.
> This is actually the same approach as the Linux one, the only difference will
> be that the driver comes in 2 pieces - the sqljdbc4.jar file, and the
> sql_auth.dll shared lib, which is needed for integrated authentication, and
> which needs to be registered in the PATH environment variable (which is
> something the Ambari Agent will be in charge of).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
