Rather than replicating data, OpenAccess exposes a real-time SQL view into the actual SaaS data. The SaaS application is not modified. This means that third-party tools can access the data as if they were accessing a relational database, such as Oracle or SQL Server. You have the ability to use all the features of these tools because the tools think they are connecting to a SQL database. Even a 10 year-old application can then connect to the newest data sources available in the Cloud.

In terms of performance, one of the objectives with this type of connectivity is to reduce how many rows have to be transferred over the Internet. These changes can reduce query times for certain queries from minutes to mere seconds since update and delete operations can be performed in batches. This leads to 30x improvements when updating 100 or more records.

The bottom-line: OpenAccess enables SaaS and Cloud applications to look like a SQL database, supporting standards-based APIs like ODBC, JDBC, and ADO.NET.  To learn more check out our resource page: http://ow.ly/lKrj3.

Stay tuned next week for the third installment of this series (see part one here: http://ow.ly/lKrGV) where we’ll address yet another data access issue!

Undoubtedly, applications consume an abundance of data and require adaptability to new cloud environments. To rapidly implement or update those applications for Cloud, organizations need to build on existing skill sets such as enterprise programming or SQL for data access. Another party is required to support the frequent API changes happening in the cloud in order to reduce costs. Consider collaborating with a partner who is knowledgeable in Cloud connectivity for integral SaaS-based services.

Remember how the Higgs boson particle was finally coaxed into existence for less than a nanosecond and the collaborative effort required – 10,000 scientists and engineers from 600 institutions in more than 100 countries (hurrah for grid computing!). It was because of this collaboration that the discovery was made. The team was able to draw from many different data elements for extreme collaboration –by collecting data and information from multiple sources, synthesizing the data, and using Big Data to trigger appropriate changes and actions. Providing as much intelligence and analytics as possible enabled the research team to adapt quickly and achieve astounding discoveries.

Business applications are the same way, and being able to adapt quickly to Cloud environments by reusing existing, prevalent skill sets and collaborating with key technology partners that are experts in new world environments are both important to obtain fast ROI. By leveraging IDEs like Progress OpenEdge and starter kits for data connectivity like Progress DataDirect OpenAccess, we enable integration with SaaS data using prominent BI and ETL tools. Bottom-line: reuse existing skills and speed up application development.

When the goal is to adapt to changes in an application as data migrates to the cloud, traditional basic data driver connectivity is not enough. Data-driven applications need the fusion of mobile application development, cloud service technologies and intelligent data connectivity solutions – such as the solutions delivered by Progress OpenEdge, Progress DataDirect Cloud, and Progress DataDirect OpenAccess.

Applications also require the fusion of application deployment and SaaS data access to mobile users for rapid responsiveness and adaptation to changes. In short, organizations need an adaptive application development environment that leverages a cohesive data-aware Cloud-based service to progress revenue growth significantly in the near future – through quicker and lower-cost application development and deployment. Still not getting it? Leave a comment below or ask us at @DataDirect_News!

The beauty of the SQL injection attack is that hackers are using the inherent functionality of the database against itself. Fundamentally, a successful SQL injection attack is basically the result of an unprotected or “un-sanitized” question being asked of a database. As it is the very nature of a database to allow for the querying or “asking of properly formatted questions” to retrieve data, SQL injection is little more than a database doing what it is was built to do. The problem with this method is that you can access data that is never intended to be returned, as well as access stored functionality in the database that was never intended to be used by an over-the-internet interface.

So, how do we fix it? Well, that is not so easy. If it were easy, we would just install a tool or a patch and move on, like we did with NIMDA, a quick-spreading computer worm released back in 2001. This is no NIMDA and the “fix” is multi facetted. First, it requires training and awareness of the DBA and Web team of the vulnerabilities that exist in database driven content served up over the internet. Second, it requires a professional environment where it is acceptable to ask for help and/or training so that an employee is not made to feel inferior for not having the complex issue resolved. Next, management needs to support their coders with a professional development infrastructure that fosters a solid and practical implementation of secure coding principles. If you are using third party or outsourced development teams, considerable care should be given to understanding which controls, frameworks and methodologies are in place to ensure you get functionality and security in your apps. Finally, test your applications for negative and positive results from perspectives outside of the basic, intended functionality. Peer and third party review of all “go-live” code should happen as a normal QA function, at every major and minor revision.

If you’re looking for a secure diver to help alleviate your vulnerabilities, try the Progress DataDirect ODBC and JDBC drivers, which can reinforce your security measures by enabling you to automatically encrypt your server communications and reduce the risk of SQL injection. Have more questions? Ask us at @DataDirect_News!

“By artfully smashing ideas together—Luke Williams upends the ordinary, providing a motivational and pragmatic blueprint for innovative thinking.”

—Jamyn Edis, Vice-President of Emerging Technology R&D at HBO

We can’t wait to hear him live in October on our stage! Save your seat by registering now.

First up: Why do we need standard-based connectivity?

Most SaaS applications like Salesforce.com expose their functionality through the Web interface to allow it to be used from any Web browser from any platform – this is how most users will connect. SaaS applications also expose their data through Web service APIs, which are proprietary APIs unique to each vendor. Salesforce.com has its own, so does NetSuite, and many others. However, there is no standardized Web service API. There is also no standardized API or language for SaaS applications, which means that each client application must be coded for each specific SaaS application.

Imagine you want to use your favorite reporting tool – one that you use regularly against your relational databases. What if you want to synchronize the data in SaaS with on-premise databases like SQL Server and Oracle? Users of your application demand best-of-breed third-party applications to access data. They are familiar with powerful reporting and analysis tools like Crystal Reports and MS Excel, and they want to use them against various data sources. Additionally, developers want to use products like Visual Studio and Java that have many capabilities for writing applications that connect to SQL-compliant databases. These third-party applications know how to connect using standards-based API and SQL data models, but they don’t necessarily know how to use proprietary APIs or file formats.

So, what can you do to solve this connectivity issue? Standard-based connectivity! It is the key to getting these different applications to “talk” to SaaS applications and data sources and effectively get the job done.

We had a lot of very interesting conversations about Salesforce integration from different point of views – the architects, the project managers and end users.

So, what’s it all about?

Progress DataDirect JDBC and ODBC drivers for Salesforce basically enable you real- time access to Salesforce data from any reporting, ETL  or query tool – Cognos, Informatica PowerCenter, Pentaho, Tibco Spotfire, Tableau, SAP Business Objects Universe, SAS –  you name it –  even if you use MS Access or Excel PowerPivot as your BI tool for your self-service analytics. We bring standards-based connectivity to Cloud and make Salesforce.com look like any relational data source to your data integration software. We can even enable Oracle-based databases integration with Salesforce – just read about RightNow, Azure, Salesforce, Netsuite SQL integration across the Oracle enterprise, OBIEE and Oracle Database Gateway.

You can leverage the Salesforce bulk load API without making code changes to reduce costs.

DataDirect can help you simplify your architecture and integration for Force developed applications allowing you to reduce costs.

We admit, there is a lot going on. Do you have any questions? Feel free to contact us, or see us at our next stop in July in Munich.

And if you wanted just to read a little bit more, read about SQL access via ODBC/JDBC versus web services APIs to SaaS in the cloud and 5 reasons to choose next generation ETL data integration with Salesforce from Progress DataDirect.

IBM Cognos Ecosystem meets the Hadoop Ecosystem

With DataDirect XE Hadoop Big Data Connectors, IBM Cognos shops have a full range of connectivity options for Hadoop Hive across Windows, AIX, Linux, Solaris, and HP-UX:

Tutorial for integrating Cloudera 4.1 Hive2 with Cognos BI 10.1

1- Download a trial of the DataDirect Connect XE for ODBC Cloudera driver.

2- Configure ODBC data source to Cloudera 4.1.  On Advanced tab, set Max Varchar Size to be 255 since my character data does not include long strings.

3. Launch Framework Manager and select Data Sources for the metadata model

4. Create new data source matching the name in step #1.

5. Select data source type “ODBC”

6. Navigate to the data source and select objects directly from Cloudera to import

7. Publish the package and launch Report Studio to run a simple list report

8. Run the report to fetch data directly from Cloudera Distribution.  Dummy data returned below is from one of our QA tables, but you can pretend it is something of big data significance like input from web forms.

Cognos shops have been really excited about having reliable connectivity into their big data infrastructure.

How about DQM?

Check back on the blog for the next IBM Cognos tutorial for our JDBC connectors to Hadoop Hive.

What else does the world wide leader in data connectivity know about Big Data?

Call us at N. America: (800)876-3101 | World: +44 (0) 1-344-386-367 to learn more about the latest big data access technologies and our project experience.

When Apollo 13’s lunar landing was aborted in April of 1970, NASA and the Apollo crew had to adapt the Command Module processes in order to stay alive and return safely to Earth. An oxygen tank exploded in the service module upon which the Command Module depended. Despite great hardship caused by limited power, loss of cabin heat, a shortage of potable water, and a critical need to jury-rig the carbon dioxide removal system, they were able to adapt processes, rerouting power for life support and navigation systems – and land safely on April 17^th – 43 years ago.

While that may be an extreme example of optimizing applications and processes in a life-threatening situation, what they were able to accomplish combines many different data elements, incorporates collaboration, and results in a situation-aware solution through quick adaptation. We can implement these tactics in the business world by collecting data and information from a variety of cloud data sources, business processes, cloud and enterprise applications, rule sets, social networks, active content and activities using Big Data to trigger appropriate changes and actions. Business success relies on adapting quickly based on access to as much intelligence and analytics as possible.

To that end, here’s my take on two best practices for ensuring that business applications are able to “see further”, adapt quickly, subsume fast and efficient data connectivity, and realize positive growth and better customer experiences.

Uncover mysterious “dark data” lurking in the depths of data stores for greater business intelligence through better connectivity.
Dark data is much like dark matter in cosmology – we know it exists even if we can’t grasp it. Dark matter is 84% of the universe; dark data, in a sense, is everything we do. To that end, how do we “see further” into the vast amounts of data collected across a variety of data stores on-premise and in the cloud? The revelations that can be uncovered within the hidden dark data are only possible with premium high-performance connectivity to the broad range of data sources in heterogeneous environments today. Greater insights are gained by spelunking through caverns of dark data that exist through the proliferation of Cloud-based data sources.

Understand the new world (or space) environment and adapt to it.
Organizations that don’t have a cloud strategy in place are missing out on a tremendous opportunity. Applications need to adapt to new environments, new APIs, and new data models to dynamically manage the flow of data and address real-time changes. Consider the International Space Station (ISS) – the most visible man-made object in the night sky – which takes humans from being explorers of space to being residents of space. The experiments are adapted to the ISS environment, while the data generated has global implications. The space station provides an ideal environment to study many aspects of humans in space, including balance, digestion, muscles and bone retention, and heart behavior. It also provides a unique window on the Earth and sun – one in which scientists can use their understanding to respond to opportunities as they arise. Like the ISS experiments, our business enterprise applications need to adapt to new environments – in this case in the Cloud. Whether applications are being deployed on-premise or in the Cloud, greater business benefit occurs when leveraging services that understand Web services and APIs used by other Cloud-based applications and data sources.

Implementing these best practices could go a long way in attaining critical business insights and in quickly and effectively adapting changes inside and outside of an application as data migrates to the cloud. Check out my next blog post during which I’ll explain the skills required to accelerate data discovery. Have questions in the meantime? Leave a comment below or ask us at @DataDirect_News!

(Image source: http://www.cosmo.org/re_res_casestudy.htm)

We are happy to be able to share additional information on Progress Exchange 2013 tracks and some of the exciting things we have planned for October. With three full days of valuable content and more than 70 hours of breakout sessions across eight tracks, the event will be packed full of networking opportunities and sessions including:

1. Mobile and Web: Developing applications for any and all devices
2. Business Application Development:  Simplifying development with Progress OpenEdge
3. Developer Productivity: Using the latest tools and frameworks to modernize and speed development
4. Business Productivity: Empowering business analysts and business users
5. Data Management: Maximizing performance, scalability and reliability
6. Cloud and aPaaS: Building applications of the future now—fast
7. Data-Driven Applications: Accessing the world’s data—easily—with Progress DataDirect
8. Partner Growth Strategies:  Monetizing and marketing your applications

Conference attendees will also have the opportunity to take a deeper dive and explore the latest Progress technologies in these instructor-led, hands-on workshops— at no additional cost.

If you want to learn more please register now and take advantage of the savings. We hope to see you in October!

1. Is this going to be able to do the job?
2. Is this the easiest way to do it?
3. Do I like using it?

The answers for WLP were all yes; and you should ask these same questions when choosing your JDBC driver for connectivity.  Here are my answers after following the WLP tutorial and these apply to Websphere Application Server, as well as Tomcat or JBoss. Note: If you’re looking for the Websphere Upgrade to SQL Server tutorial, check here.

Is this going to be able to do the job?

The DataDirect SQL Server JDBC driver will get your job done without any road blocks thanks to:

• Support for NTLM Windows Authentication from Unix/Linux servers to keep your DBAs and auditors happy.
• Includes our patented SQL Server JTA library built by DataDirect without any locking or rollback issues under heavy load.
• High performance and scalability both in terms of increased throughput and decreased memory/CPU/Garbage Collection.  Our daily performance runs against a competing driver show increased throughput up to 91% and up to 2815% memory savings and up to 221% CPU savings across different tests.  Note: Our lab results are not intended to substitute testing in a production like environment.

Is this the easiest way to do it?

• It just works.  Not by coincidence, but because we run 80 million tests across multiple JRE flavors from IBM, HP, Oracle, etc.
• Single JAR supports multiple JREs and SQL Server versions (Microsoft SQL Server 2012, 2008 R1, R2, 2005, 2000 Desktop Engine (MSDE 2000), 2000 and 7.0.
• DataDirect has award wining 24/7 support including member to tsanet.org giving us access to Microsoft and IBM on your behalf.

Do I like using it?

We’ve heard from developers that they are 2x as productive with DataDirect; and can save many dev months with advanced features such as:

• Bulk load (codeless and API) capabilities are built-in and can improve JDBC batch insert jobs from 7 hours down to under 30 minutes.
• High availability features where driver can transparently failover to mirrored server during connection failure in the middle of a result set.

Getting Started with Websphere Liberty Profile JPA project with DataDirect JDBC drivers

1 . Install Progress DataDirect SQL Server Connect for JDBC driver using the instructions in the Progress DataDirect Connect for JDBC installation Guide.  You can download a free, 15-day trial of the Progress DataDirect SQL Server JDBC driver (including DB2, Oracle, Sybase, MySQL and Salesforce).

2. Install JTA support using DataDirect’s patented sqljdbc.dll library that Websphere shops have been using for years for reliable transaction processing.

3. Follow tutorial for getting started with WAS Liberty Profile from IBM.  Note: I used SQL Server Express 2012 and noted the exceptions for each module below to configure the DataDirect Connect for JDBC SQL Server driver.

4. Create table for ReportServer$SQLEXPRESS database in SQL Server instead of DB2 per module Module 1.2 : Create the database and Liberty server.

CREATE TABLE [dbo].[ACCOUNTS](
[C_NUM] [smallint] NOT NULL,
[C_NAME] [varchar](50) NULL,
[C_MONEY] [bigint] NOT NULL,
CONSTRAINT [PK_ACCOUNT] PRIMARY KEY CLUSTERED
(
[C_NUM] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]

5. Configure DataDirect SQL Server JDBC driver instead of DB2 in, Module 2.2 : Configure the server for DB2

Base directory is the DataDirect JDBC installation folder. In this case, I installed to C:\jdbc\Connect_for_JDBC_51.

id is ddsqlserverconnection and JNDI name*: jdbc/SQLServerConnection

Database name is ReportServer$SQLEXPRESS; Server name is locahost\SQLEXPRESS nad URL is jdbc:datadirect:sqlserver://localhost\SQLEXPRESS;AuthenticationMethod=ntlm

6. After creating new JPA Entities from Tables and select Generic JDBC for DataDirect.

Enter URL as jdbc:datadirect:sqlserver://localhost\SQLEXPRESS;AuthenticationMethod=ntlm;DatabaseName=ReportServer$SQLEXPRESS

Note: If using Windows Authentication from Unix/Linux (for example AMERICAS\SUMITS), enter your Windows Authentication user “SUMITS” without the domain and password; and then add the following properties to your deployment profile to Linux, AIX, Solaris or HP-UX:

;AuthenticationMethod=ntlmjava;Domain=AMERICAS;

7. Modify DBInteractions.java with the the following line for SQL Server instead of DB2:

@Resource(name = “jdbc/SQLServerConnection”, type = javax.sql.DataSource.class, shareable =

8. Run the index.html per Module 6.2 : Complete and test the JPA application with DB2

Finally, if you run into any issues, here is a link to generate WLP tracing.

So, did I like using it?

I had a good time!  Call us at N. America: (800)876-3101 | World: +44 (0) 1-344-386-367 to learn more about DataDirect SQL Server JDBC drivers for use in the world of Websphere.