Articles on the integration of Teradata into the larger IT ecosystem, and the enterprise-class features, tools, patterns, and best-practices that facilitate mission-critical operation of the Teradata EDW.

Expand All The Latest
The Friday Night Project #11 – Macros and Stored Procedures

Last time we did a full on What, Why and How description of some pretty Teradata specific information around Query Banding and showed how we could weave this into the Web Application and Data Access Layers so as to minimize the impact of this on the Business Service layer and it’s developers.

This week we are going to keep on the core Teradata trail by looking into Macros and Stored Procedures as means to provide for Isolation and Embedded Processing.

The Friday Night Project #9 – Wiring up the Web service

Last week we used the Eclipse WTP Web service Wizard to create the TZA Property Insurance Web service. We automatically created a series of plumbing code (within the com.teradata.tza.insurance.service and com.teradata.schemas.tza.insurance.service packages) plus a single Implementation (PropertyInsuranceSoapBindingImpl.java) class that the author is expected to customize. This class provides an SOA Presentation Veneer (User Interface) that can act as an entry point into the TZA-InsuranceService Business Process.

This week we will demonstrate how to "Wire" up the different parts of the project in order to connect the Web service Presentation Veneer into the Business Process, Business Objects and Repository layer and therefore on through to the database and the data tables.

The Friday Night Project #8 – TZA-InsuranceService

So as we discussed previously TZA-Insurance operates as an Insurance Underwriter, allowing other Insurance Brokers to offer insurance services (insurance quotes and policies) to the final customer. In order to expose the business processes of TZA-Insurance we provide a Web service definition to its various Clients (Insurance Brokers, Web sites, etc) that allows them to create a Web service client interface within their application environment (Java or .Net). This Client interface then operates against the TZA Property Insurance Web service in order to initially get an insurance Quotation based upon the characteristics of the Property to be insured and then if acceptable to the Customer buy an Insurance Policy based around that Quotation.

The Friday Night Project #7 – A Console Veneer

In this session of the Friday Night Project we are finally going to create a Presentation Veneer that will use the Simple Quotation Engine business process we created last week.

However, don’t go getting all excited about MVC Web Pages, Portlets or Web services as we are going back to basics for this one with a plain old Command Line or Console Application interface. Think of it like “Basic Training” Toto, where we establish a usage pattern that we can apply across all further Presentation Veneers.

The Friday Night Project #6 – Simple Quotation Engine

TZA-InsuranceProcess is a set of APIs which provide a Suite of Business Processes that represent TZA-Insurance, ranging from a simple Quotation Engine for the demonstration of the architectural concepts, through Complex Insurance and Quotation Management for Web and Web service applications to Insurance Summaries that can be represented in a Web Portal.

These APIs are written in Java and provide a series of Business Processes that behave independently from each other or which can be orchestrated to provide a larger Business Service or Process. These APIs are embedded into a single jar file [known as TZA-InsuranceProcess.jar] which relies upon other Teradata implicit objects [as jar files] which are included in its classpath, such as tdcommons-context.jar and tdcommons-access.jar.

The Friday Night Project #5 - TZA-Database

Finally it’s time to start some real development within the Friday Night Project. This week we are going to create the TZA-Database project within which we will ultimately collect all of the project information (SQL, Data and build files) necessary to create and maintain a consistent version of the TZA-Database. We will also establish the base infrastructure for an ANT based build that can clear any existing database elements prior to creating the ZipCodeRiskFactors table and loading the base Risk Factors data.

The Friday Night Project #4 - TZA_DB and TZA_USER

Having previously introduced the “What”, “Why” and “How” of Active Integration and Solid Architecture, this week we start to build up the development environment (Eclipse with the Teradata Plug-In), Teradata Database Schema (TZA_DB) and User (TZA_USER) required to support TZA-Insurance.

The Friday Night Project #3 - TZA-Insurance

After a couple of Weeks of Introduction to the “What” and “Why” of Active Integration plus a start at the “How” around creating a Solid Architecture, this episode of the Friday Night Project introduces the Teradata Sample Application (TZA-Insurance).

The Friday Night Project #2 - Solid Architecture

Last Friday we defined the “What” and “Why” of our new Active Integration world.

So why don’t we start getting straight into the “How” and pick out some User Interface for each of our application classes?

Not so fast, let’s get some Solid Architecture principles in place before we start chasing up that pretty road Toto.

The Friday Night Project #1 - Active Integration Introduction

Welcome to the first article in The Friday Night Project series, where we'll starting with a background on the nature and role of the Enterprise Data Warehouse.

Pages