Easysoft Data Access Middleware
Price: Free for single users, commercial licenses vary
Reviewer: Jon Valesh
Easysoft provides interfaces between data and the applications that use it. With Easysoft's products, you can access any ODBC data source from just about any computer system, and you can allow access to many Linux databases from ODBC clients. To use real-world examples, you can access Access on a Win98 desktop from your Linux web server, or your MySQL database from Excel.
Very few assumptions are made about what you will do with that data once you have it. Use it with PHP or iHTML, write custom C code, access it from Python or Perl or a Java applet; Easysoft doesn't care.
Easysoft provides a combination of their own ODBC-ODBC bridge software to allow access to remote database servers, and unixODBC 1.8.10 to access Linux database software. Access to SQL databases is through Easysoft's SQL-ODBC gateway package. This standardization on ODBC for all database access gives two important benefits: your programs will be totally free of database-specific dependencies, and you can seamlessly access multiple databases without special code. Not only databases, you can access any data source that has an ODBC driver.
On Easysoft's web page (http://www.easysoft.com/), they claim you can install their ODBC-ODBC bridge in one to two minutes. They aren't far off. It actually took closer to five minutes, but perhaps I was having a slow day.
Easysoft supports Linux as just one of about a dozen platforms, and they obviously know having a distribution that works regardless of one's system type is very important. In the Linux arena, they have libc5 and glibc 2.1 versions for Intel x86 and Alpha processors. Installation is done without the use of a system package tool and requires superuser access, because several new libraries are added and files in your /etc directory are changed. All files are placed in the /usr/local/easysoft directory. If downloaded from Easysoft's web page, the software is packaged in a compressed tar file and installation is a two-step process. First, you must unpack the obscenely long-named tar file, change to the newly created directory and run the install script.
The install script is a model of how self-installing Linux programs should behave. You are asked a series of questions about which components you would like installed, what directory to place the files in and how everything should be set up. Given the quality of the installation script, very little would be gained by using distribution-specific package tools, and Easysoft's already daunting array of download options would increase unnecessarily.
One stage of the setup includes running Easysoft's license management software. This application collects personal information about you and how you will use the product, and contacts Easysoft's servers through the Internet to request a license key. If you don't have an Internet connection, you can print out the collected data and mail it to Easysoft via real-space mail.
The Easysoft's installation script installs unixODBC. Easysoft listens on port 8888 for ODBC requests and 8890 for HTTP requests.
Easysoft's package is made up of separate client/server applications. The clients and servers are a rather mix-and-match affair. You can run a Windows server and Linux clients, or Linux and OpenVMS servers and Java clients (using the ODBC-JDBC bridge), or whatever your application demands. For most users, the servers would be installed on the company database server computers, and the clients would end up wherever the data was needed. This could be your web server, a desktop computer running a database client application, or both. This gives you great flexibility in choosing your data sources, and even allows some unlikely combinations like using spreadsheets on desktop computers as data sources for dynamically updating web pages.
Easysoft's tools are designed to facilitate getting data for your applications, not writing them. In fact, they don't really even provide the API. If you know how to use database tools, Easysoft's products will give you access to a wider range of data sources. If you don't, they provide some tutorial information to point you in the right direction, but that's about it.
The APIs you use are specific to your language or development environment, not Easysoft's product. Most aren't that complicated, but it is totally a matter of what tools you are using. If writing PHP scripts, you connect to your databases with the PHP ODBC support. A command such as @odbc_pconnect(<datasource>, <username>, <password> ) establishes the connection to the data source, returning a string if the connection is successful. Once connected, you request data by assembling a string with your query, and running another API command to execute it. If you are writing in Perl, you use the DBM::ODBC API to access the data sources. If your development tools include an ODBC API, chances are you can use Easysoft's tools to provide access to a wider range of data sources.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Google's SwiftShader Released
- Interview with Patrick Volkerding
- SUSE LLC's SUSE Manager
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Returning Values from Bash Functions
- SuperTuxKart 0.9.2 Released
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide