Here are a couple of helpful links in Teradata Relationship Manager (TRM).  These allow you to see all of the security privileges and user groups assigned to the logged in user, as well as a report of the TRM version and detailed environmental information.

Right out-of-the box, custom processing engine tasks may be created without having to write new Java components. These tasks are application components that implement common functionalities. There are several base processing engine tasks that are also based on these common tasks. Built-in processing engine tasks are limited in scope and functionality to what they’re capable of and cannot be extended or changed.

Teradata Warehouse Miner provides an array of data profiling and mining functions ranging from data exploration and transformation to analytic model development and deployment that are performed directly in the Teradata Database. While many data mining solutions require analysts to extract data samples to build and run analytic models, Teradata Warehouse Miner allows you to analyze detailed data without moving it out of the data warehouse, thus streamlining the data mining process. Teradata Warehouse Miner, and its derivative products Teradata Analytic Data Set (ADS) Generator, Teradata Data Set Builder for SAS and Teradata Profiler, can provide both a framework for the data mining process and a significant savings of time and resources in implementing the process.

Processing Engine Extension represents mapping of customized processing engine tasks, properties, and dependencies whose purpose is to change or extend the processing flow of base processing engine capabilities defined in the base definition files. The purpose of this functionality is to allow for flexibility while maintaining the core product, or at least the processing engine configurations, unchanged.

Once you've installed the Evaluation Copy of Teradata Warehouse Miner (described in the article "Getting Started Installing and Configuring Teradata Warehouse Miner"), there are now two ways to get to know Teradata Warehouse Miner.  First, you can get started quickly by loading and viewing a supplied tutorial project.  Second, you can learn how to build a project from scratch, with specific examples in on the following:

• Create a Histogram Analysis
• Create a Scatter Plot Diagram
• Create a Decision Tree Model
• Create a Decision Tree Score Table

It is easy to install the Teradata Warehouse Miner Evaluation software. First, download the software package. Then open the “TWM.msi” file and follow the instructions, including accepting the license agreement and, if necessary, installing the appropriate version of the .NET runtime package if prompted to do so.  After the installation, start the application via its desktop icon or start-program item and then select Contents & Index on the Help menu (or simply press F1).  Open the Configuration sub-chapter in the Installation and Configuration chapter of the Help system.  You can follow the instructions in this chapter to configure Teradata Warehouse Miner to work against the desired data in your Teradata data warehouse. 

In parts 1 and 2, we looked at how to load and retrieve large objects using Teradata BLOBs and CLOBs. In part 1, I put forward my unbreakable golden rule that you shouldn’t simply store Object Models as Large Objects. Rather, always map your objects’ attributes to columns in a table; don’t just serialize a bunch of classes and store them in a BLOB.

In part 3, I present another of my unbreakable golden rules; which is “Rules were made to be broken”. The focus of this article is how to serialize and persist (store) an Object Model into a BLOB on Teradata and reinstate it.

Expect 
"It will not do to leave a live dragon out of your plans if you live near one." ~ The Hobbit

No matter what you do, no matter how long you prepare, your plan will begin to slowly, or not so slowly, unravel before your eyes.  Plans fail, that is the one constant you can actually plan for.  

In the first two parts of this Mini Section we have been looking at the concept of Embedding analytical processing directly within the Teradata Database. Part one used a SQL Stored Procedure to act as an Isolation layer between the Enterprise Application and the Teradata Database. Part two replicated this isolation concept using the Java External Stored Procedure (JXSP) approach. Part three combined the JXSP with the previously prepared, Spring Framework based, Business Processes. This final Part illustrates how to little code is now required in the Presentation Veneer (Web service process) due to the embedding of the Business Logic within the Teradata Database.