Showing posts with label integration. Show all posts
Showing posts with label integration. Show all posts
Monday, March 9, 2015
Going Deeper More Integration Examples Available in our Developer Docs
Users love Single Sign-On, but we’ve found the depth and quality of a Marketplace apps integration with Google Apps is a key factor in both the user experience and vendor success in the Marketplace. Deep integration makes users happy, because it helps them avoid entering duplicate data and makes useful information accessible from their day-to-day communication and collaboration tools.
To help you discover ways to integrate your own applications with Google Apps, we added a new section to our developer docs showcasing examples from popular applications in the marketplace. Some examples, like BatchBook’s streamlined sign-up process for users, show simple ways applications can help users get started quicker.
Apps can help users be more productive by displaying information and allowing them to take action right within an e-mail message. Harvest, a time tracking application, allows users to complete their timesheets in gmail when they receive their weekly reminders.
You’ll also find examples for collaboration and document sharing, such as Manymoon’s seamless integration with Google Docs. This makes it easy for users to share information with teams or attach relevant docs to tasks.
You can read more about these and other integrations, or try out the apps yourself by going to the Google Apps Marketplace. Of course these are just a few of many ways to make apps easier for users, and we look forward to seeing even more creative ideas from developers.
P.S. If you want to learn about the APIs which enable these deep integrations, meet with fellow developers and ask questions of Googlers, come to our Google Apps and Apps Marketplace Hackathon at the Google Mountain View campus on August 24th!
To help you discover ways to integrate your own applications with Google Apps, we added a new section to our developer docs showcasing examples from popular applications in the marketplace. Some examples, like BatchBook’s streamlined sign-up process for users, show simple ways applications can help users get started quicker.
Apps can help users be more productive by displaying information and allowing them to take action right within an e-mail message. Harvest, a time tracking application, allows users to complete their timesheets in gmail when they receive their weekly reminders.
You’ll also find examples for collaboration and document sharing, such as Manymoon’s seamless integration with Google Docs. This makes it easy for users to share information with teams or attach relevant docs to tasks.
You can read more about these and other integrations, or try out the apps yourself by going to the Google Apps Marketplace. Of course these are just a few of many ways to make apps easier for users, and we look forward to seeing even more creative ideas from developers.
P.S. If you want to learn about the APIs which enable these deep integrations, meet with fellow developers and ask questions of Googlers, come to our Google Apps and Apps Marketplace Hackathon at the Google Mountain View campus on August 24th!
Monday, February 16, 2015
pentaho data integration PDI basics
Pentaho Online Tutorial
http://infocenter.pentaho.com/help/index.jsp?topic=%2Fpdi_user_guide%2Fconcept_pdi_usr_kettle_components.html
Transformations :
* A Transformation is made of Steps linked by Hops.
* These Steps and Hops form paths through which data flows.
* Therefore its said that a Transformation is data-flow oriented.
Jobs are used to coordinate ETL activities such as:
• Defining the flow and dependencies for what order transformations should be run
• Preparing for execution by checking conditions such as, "Is my source file available?," or "Does a table exist?"
• Performing bulk load database operations
• File Management such as posting or retrieving files using FTP, copying files and deleting files
• Sending success or failure notifications through email
http://infocenter.pentaho.com/help/index.jsp?topic=%2Fpdi_user_guide%2Fconcept_pdi_usr_kettle_components.html
Transformations :
* A Transformation is made of Steps linked by Hops.
* These Steps and Hops form paths through which data flows.
* Therefore its said that a Transformation is data-flow oriented.
Jobs are used to coordinate ETL activities such as:
• Defining the flow and dependencies for what order transformations should be run
• Preparing for execution by checking conditions such as, "Is my source file available?," or "Does a table exist?"
• Performing bulk load database operations
• File Management such as posting or retrieving files using FTP, copying files and deleting files
• Sending success or failure notifications through email
Pentaho Data Integration Components
Pentaho Data Integration is composed of the following primary components:
- Spoon. Introduced earlier, Spoon is a desktop application that uses a graphical interface and editor for transformations and jobs. Spoon provides a way for you to create complex ETL jobs without having to read or write code. When you think of Pentaho Data Integration as a product, Spoon is what comes to mind because, as a database developer, this is the application on which you will spend most of your time. Any time you author, edit, run or debug a transformation or job, you will be using Spoon.
- Pan. A standalone command line process that can be used to execute transformations and jobs you created in Spoon. The data transformation engine Pan reads data from and writes data to various data sources. Pan also allows you to manipulate data.
- Kitchen. A standalone command line process that can be used to execute jobs. The program that executes the jobs designed in the Spoon graphical interface, either in XML or in a database repository. Jobs are usually scheduled to run in batch mode at regular intervals.
- Carte. Carte is a lightweight Web container that allows you to set up a dedicated, remote ETL server. This provides similar remote execution capabilities as the Data Integration Server, but does not provide scheduling, security integration, and a content management system.
Whats with all the Culinary Terms?
If you are new to Pentaho, you may sometimes see or hear Pentaho Data Integration referred to as, "Kettle." To avoid confusion, all you must know is that Pentaho Data Integration began as an open source project called. "Kettle." The term, K.E.T.T.L.E is a recursive that stands for KettleExtraction Transformation Transport Load Environment. When Pentaho acquired Kettle, the name was changed to Pentaho Data Integration. Other PDI components such as Spoon, Pan, and Kitchen, have names that were originally meant to support a "restaurant" metaphor of ETL offerings.
Subscribe to:
Posts (Atom)