0 - 3 of 3 tags for thread local context

One of the biggest benefits of Query Banding is the ability to pass parameters into an SQL script.

Establishing an associative security table lookup between a userid and allowable company codes may allow easy access to the base data tables.  

Last week we concluded by challenging you to consider how a Connection Pool contributes to the performance of Web and Web service applications. Further we suggested that this week we would expand on this thought by exploring what you can do, during the development of an Active Integration application, to achieve improved performance through collaborating with the Database on Workload Management.

Until now nothing that we have discussed has been dramatically different from any other Spring Framework / DAO / Web services / JEE / POJO tutorial, however, there is method to this madness in that it was necessary to introduce the Teradata Masters out there to some new Java concepts while leading the Java Masters into the Teradata fold. While this has taken a reasonable number of weeks to accomplish it should now be safe for the entire readership to enter the world of Teradata Workload Management and Query Banding together.

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.