0 - 12 of 12 tags for web services

Does anyone know if there is a way of calling a web service from teradata?  
I'm looking at replacing a process that currently uses oracle.  We have stored procedures created which build some XML and then call a web service.  This uses the oracle package UTL_HTTP.

Hello. I have an inward facing ASP web app that I am changing to connect to Teradata instead of an AIX box.  I am able to connect to the Teradata Server and execute queries using an ODBC connection using VB 6 (so I'm told.

iBatis is now called MyBatis (iBatis 3.0). MyBatis is no longer sponsored by Apache. It is now supported on Google code. The MyBatis framework is a lightweight data mapping framework and persistence API. It couples objects with stored procedures or SQL statements using an XML descriptor.  The Teradata Plug-in for Eclipse allows you to switch between creating projects that use MyBatis or iBatis using the Teradata Project preferences. When you switch to use MyBatis, you can use new features like User Generated Keys.

User Generated Keys are unique identifiers returned from MyBatis during an insert operation. This tutorial will go through creating a Web service using user generated keys with MyBatis.

The iBatis (MyBatis) Stored Procedure Wizard allows you to right click on a Stored Procedure in the Teradata plug-in for Eclipse and quickly create a Web service.

The iBatis Stored Procedure Wizard wraps a Stored Procedure into an iBatis or MyBatis SQL Map. The generated SQL map can then be used to create a Web service or it can be used to create a Java application that uses the iBatis or MyBatis frame works.

So you told your boss about the cool “Consumer Credit Score” SQL algorithm you wrote and all she said was “Great, integrate it into the Call Center application this weekend.” Now all you have to do is turn your SQL algorithm into a BI Web service ready for integration with their Web application... Simple right?

The iBatis DAO with Web Services Wizard will generate a Web Service from an iBatis SQL Map. The wizard derives all of the information needed from the iBatis SQL Map to generate the following components to create a Web service:

  • DAO (Data Access Object)
  • WSDL (Web Service Definition Language)
  • XSD (XML Schema Definition)
  • Spring Configuration files

The wizard will then use the Eclipse Web Tools Platform (WTP) and Apache Axis to generate the server and client classes for the Web service. The generated classes will include code that supports Query Bands via the Teradata Access Session Manager.

 

To join Business Technology Summit 2010 as a speaker is a great opportunity to build brand equity for both you as an individual and for your organization.

Business Technology Summit 2010 – India's First, Largest and Single-most Inspirational Technology Show

Back in FNP #11 Macros and Stored Procedures the Spring Framework concept of referencing a Parent bean was introduced as so:

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.

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.

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.