© 2002 International Business Machines Corporation. All rights reserved.

Introduction

In Part 1 of this article, we provided an overview of a Web service sample application, IBM Video Central, and introduced its architecture and key technologies. Since then, we have updated the Video Central with new technologies and new development environment provided by IBM. In this second part, we describe the new features of the Video Central, including:

• A new Web service called Movie Search that uses DB2® Net Search Extender
• A new development environment, WebSphere® Studio Application Developer Version 4
• A new version of the Web services server, WebSphere Application Server Version 4
• The implementation of User Infraction Web service by using DB2 XML Extender

We will also describe how you can modify Video Central to use a new approach, a Document Access Definition eXtension (DADX).

For the completeness of the article and the convenience of the description, we will include some contents of the first part of the article.

Back to top

Overview of Web services

IBM Video Central is a sample application that demonstrates how to build a Web services application from development to deployment. Web services is a new development model for integrating e-business applications. A Web services model provides a standard technique for describing, publishing, discovering, and invoking business function in a distributed computing environment. Figure 1 illustrates the basic concepts in Web services.

The Web services programming model is based on emerging technologies:

• Web Services Description Language (WSDL) is a standard XML format for describing Web services, and serves as a recipe for automating the details involved in application communication.
• Universal Description, Discover and Integration (UDDI) creates a global, platform-independent, open framework to enable businesses to discover each other, define how they interact and share information.
• Simple Object Access Protocol (SOAP) is a lightweight protocol for exchange of information in a decentralized, distributed environment. SOAP messages can be transported using the Internet standard protocol, Hyper Text Transfer Protocol (HTTP).
• eXtensible Markup Language (XML) is a standard tag language for exchanging information.

Service providers publish their business function in the form of Web services to a service broker. Service requesters use UDDI to search the available services and invoke the application logic using the WSDL-defined interface. A UDDI business registry is not a requirement to utilize Web services. WSDL documents can be used to invoke the Web service independent of a business registry. The IBM Video Central solution does not use a UDDI registry.

IBM is enabling its key products with Web services capabilities. Tools to automatically generate, publish, find, test and invoke Web services are available. The IBM Video Central tutorial demonstrates how to use the following software:

• WebSphere Studio Application Developer Version 4 is a complete Java^TM development environment to meet the requirements for all new types of applications including Java, J2EE, XML, Web services, and testing.
• WebSphere Application Server Version 4 is a Java 2 Platform, Enterprise Edition (J2EE 1.2) server, integrating enterprise data and transactions within the e-business world. It provides a rich, e-business application deployment environment with a complete set of application services including capabilities for transaction management, security, clustering, performance, availability, connectivity and scalability.
• DB2 Universal Database^TM is a highly scalable database server. The DB2 XML Extender dynamic XML mapping capabilities and the DB2 Net Search Extender high speed full-text retrieval engine extend the capabilities of DB2. By introducing the technology of a document access definition extension (DADX), DB2 can act as a Web services provider.

Back to top

The IBM Video Central scenario

IBM Video Central is a generic (and fictional) Web services provider for video rental applications. It provides a central data repository that can be accessed by registered Web-based applications. We designed one specific business-related Web service: Business Registration, which allows a business (for example, a video store) to register itself with IBM Video Central. After a business registers with IBM Video Central, it is allowed to use the other available Web services.

We designed five specific customer-related Web services, of which Movie Search is a new feature of IBM Video Central.

• Customer Registration, which enables the registered business to register their own customers with the Video Central. After a customer is registered, the other services store, access and analyze useful information about the customer.
• Customer Infraction, which enables the registered business to add and query infraction information to and from the central repository. This allows the business to keep track of customer infractions without having to actually store and manage the data in their local database.
• Customer Rented List, which enables the registered business to add and query rented videos. This collection of data will prove increasingly useful in the future when data mining and business intelligence services are added.
• Customer Wish List, which enables the registered business to add and query the titles of videos that the customer has expressed an interest in watching in the future. The video store can use the lists to determine which videos are in demand, and therefore alter their inventory purchase plan.
• Movie Search, which enables the registered business to search for movie titles and movie plot summaries. Instead of the business manually entering all the data into a local database, they can search online for current and constantly updated movie information.

Back to top

The IBM Video Central architecture

IBM Video Central is implemented as a three-tier application including:

• Web interface layer
• Business logic layer
• Data access layer

This three-tier approach is a flexible component-based implementation that is designed to facilitate future enhancements through an extensible framework. Figure 2 shows the architecture of IBM Video Central.

Web interface layer

The Web interface layer can be implemented to support different Web interfaces, such as Web services, HTTP Servlet or Java^TM Server Pages (JSPs), and so on. This provides the maximum flexibility in end-user interface design. In Video Central, we implemented a Web services interface by using the SOAP runtime for Web service invocation.

Business logic layer

The business logic layer is designed using Web services as the level of abstraction. Each Web service defines a set of business procedures, and the interface is described using WSDL. In turn, the WSDL interface can be published to a public or private UDDI registry. Web services in this layer are invoked by the SOAP runtime contained in the WebSphere Application Server sitting on the site of the service provider, and Web services components send requests to the Data Access Layer for all database access.

Data access layer

The data access layer is responsible for all database access. DB2 Universal Database is a highly scalable database server. Two of DB2 Extenders^TM, DB2 XML Extender and DB2 Net Search Extender are demonstrated in IBM Video Central. One Web service in the Video Central, Customer Infraction, involves the use of DB2 XML Extender to manage the customer infraction repository for storage and retrieval. The benefit of using XML Extender is that programmers do not need to write programs to parse and compose XML documents from DB2. The Movie Search Web service involves the use of the DB2 Net Search Extender to provide the high-speed in-memory search for video titles and plot summaries.

In Part 1 of this article, we described the steps of how to build the Web services applications from development to deployment, including the technologies and tools available in June of 2001. We will not repeat these steps here, but instead will focus on the new technologies adopted by the new version of IBM Video Central.

Back to top

Rapid application development using WebSphere Studio Application Developer

WebSphere Studio Application Developer is a complete Java, Web, Web services, Enterprise JavaBeans (EJB), and XML development environment. It provides wizards and other tools to enable rapid development of Web services applications. The Web services development tools provided in WebSphere Studio Application Developer are based on open, cross-platform standards: Universal Description Discovery and Integration (UDDI), Simple Object Access Protocol (SOAP) and Web Services Description Language (WSDL). WebSphere Studio Application Developer facilitates the following processes to assist with building and deploying Web services-enabled applications:

• Create or transform. Create Web services from existing artifacts, such as Java beans and XML document.
• Build. Wrap existing artifacts as SOAP and HTTP accessible services and describe them in WSDL. The Web services wizards assist you in generating a SOAP proxy to Web services described in WSDL and in generating bean skeletons to classes.
• Deploy. Deploy Web services in the WebSphere Application Server or Tomcat test environments.
• Develop. Generate sample applications to assist you in creating a Web service client application.
• Test. Test Web services running locally or remotely.
• Publish. Publish Web services to the UDDI business registry, advertising your Web services so that other businesses can access them.
• Discover. Browse the UDDI business registry to locate existing Web services for integration.

WebSphere Studio Application Developer provides a comprehensive XML development environment that includes tools for building Document Type Definitions (DTDs), XML schemas, and XML files. It also supports integration of relational data and XML. You can use the Relational Database (RDB) to XML Mapping Editor to easily map relational data to XML formats. The editor can map columns in one or more relational tables to elements and attributes in an XML document. It can generate a Document Access Definition (DAD) file, which is used by DB2 XML Extender to either compose XML documents from existing DB2 data, or to decompose XML documents into DB2 data.

WebSphere Studio Application Developer contains a relational database environment to create and manipulate the data design for projects. It is an environment for exploring, importing, designing and querying databases. The SQL Query Builder provides a visual interface for creating and executing SQL statements.

WebSphere Studio Application Developer provides testing and publishing tools for testing enterprise applications. It provides a unit test environment for testing JSPs, servlets, and HTML files. It also provides the capability to configure other local or remote servers for integrating testing and debugging of Web and EJB applications. The server can be WebSphere Application Server, Apache Tomcat, or TCP/IP Monitoring Server.

To summarize, the WebSphere Studio Application Developer is a powerful integrated development environment, which provides an entire solution for Web services application development. We would like to point out that there are many additional features available with WebSphere Studio Application Developer, which have not been discussed in this article.

Back to top

Using DB2 XML Extender for storing and retrieving XML data

DB2 XML Extender integrates the power of DB2 Universal Database with the flexibility of XML. It provides the ability to store and access XML documents, and to generate XML documents from existing relational data. It can shred XML documents into relational data, which means that it deconstructs the document and stores untagged elements or attribute content, which can be indexed by DB2 and accessed using SQL. It also provides new data types, functions, and stored procedures to manage XML data in DB2. IBM Video Central demonstrates how to use the composition and decomposition stored procedures provided by XML Extender.

Shredding an XML document

Figure 3 shows the processing flow of an Add Customer Infraction request. The XML document containing the infraction data is sent to the Customer Infraction Web service of IBM Video Central. This service calls the XML Extender's stored procedure, db2xml.dxxShredXML(), and passes values for the DAD and XML document parameters. The XML Extender then shreds the infraction data in the XML document into the DB2 database. The data is stored in the USERINFRACT table according to the generic relational database mapping in the DAD file.

Composing an XML document

Figure 4 shows the flow of a Query Customer Infraction request. We use the composition stored procedure of XML Extender, db2xml.dxxGenXML(), to generate the customer infraction data in XML document. To call this stored procedure, we need to provide the DAD file for the mapping of XML document to the data in the table. We use a single result table to store the XML document generated from the execution of the stored procedure. When calling db2xml.dxxGenXML(), we can specify a SQL statement that can override the SQL SELECT statement in the DAD file. After execution, the infraction data is stored in an XMLCLOB column. The dynamically generated XML document is then returned to the Web services client with the response object.

XML Extender Version 7.2 FixPack 4 introduced a new composition stored procedure called db2xml.dxxGenXMLCLOB(). This stored procedure is similar to db2xml.dxxGenXML except that the XML document is returned in memory as an output stored procedure parameter. The following is the signature of this composition stored procedure:

Listing 1: XML Extender dxxGenXMLCLOB stored procedure

 
db2xml.dxxGenXMLCLOB( 
                  CLOB(100K)         dadBuf, 
                  integer            overrideType, 
                  varchar(32672)     override, 
                  CLOB(1M)           resultDoc, 
                  integer            valid, 
                  integer            numDocs, 
                  integer            returnCode, 
                  varchar            returnMsg)

As input, db2xml.dxxGenXMLCLOB takes a buffer containing the DAD file. It constructs XML documents using data that is stored in the XML collection tables that are specified by the in the DAD file and returns the first and typically the only XML document generated into the CLOB output parameter resultDoc. Listing 2 shows how to use db2xml.dxxGenXMLCLOB in Java programs.

Listing 2. Using dxxGenXMLCLOB in Java

 
public String genXMLClob(String dadOverride) throws IvcException 
{ 
     String dad = null; 
     String xmlOut = null; 
 
     // prepare the CALL statement 
     java.sql.CallableStatement stmt = null; 
     Connection conn = null; 
     String sql = "Call DB2XML.DXXGENXMLClob " + "(?,?,?,?,?,?,?,?)"; 
 
     try 
     { 
     conn = getDataSource().getConnection(); 
     stmt = conn.prepareCall (sql); 
 
     //Retrieve DAD file 
     dad = getDAD(); 
 
     // Set all input parameters 
     byte[] dadBytes = dad.getBytes(); 
     int dadSize = dad.length(); 
     ByteArrayInputStream dadStream = 
	                   new ByteArrayInputStream(dadBytes); 
 
     stmt.setBinaryStream (1, dadStream, dadSize); 
     stmt.setInt (2, 1); 
     stmt.setString (3, dadOverride); 
     stmt.setInt(5, 0); 
 
     // Register the output parameters 
     stmt.registerOutParameter (4, Types.CLOB); 
     stmt.registerOutParameter (5, Types.INTEGER); 
     stmt.registerOutParameter (6, Types.INTEGER); 
     stmt.registerOutParameter (7, Types.INTEGER); 
     stmt.registerOutParameter (8, Types.VARCHAR); 
 
     // call the stored procedure 
     stmt.execute (); 
 
     // Retrieve output parameters 
     int errCode = stmt.getInt(7); 
     String errMsg = stmt.getString (8); 
     Clob custInfract = stmt.getClob(4); 
     int clobLength = (int) custInfract.length(); 
     if (clobLength > 0) 
     { 
          xmlOut = custInfract.getSubString((long)1, clobLength); 
     }else 
	 { 
          System.out.println("XML Clob size is " + custInfract.length()); 
     } 
     } catch (Exception e) 
     { 
          System.out.println("Err in genXMLClob: "); 
          try 
          { 
                 conn.rollback(); 
          } catch (Exception ex){} 
                 e.printStackTrace(); 
          } finally 
          { 
                 try 
                 { 
                      if (stmt != null) 
                            stmt.close(); 
                      if (conn != null 
                            conn.close(); 
                 } catch (Exception e) 
                       e.printStackTrace(); 
                 } 
          } 
          return xmlOut.trim(); 
     } 

By using the above Java code, we no longer need a result table (the QUERY_RESULT_TAB table in Figure 4), which means we do not need to generate a temporary table and we avoid the problem of keeping a common permanent result table when many clients are requesting the infraction data at the same time. To retrieve the CLOB output parameter that contains the XML document, we use the getClob() method provided by the java.sql.CallableStatement class. The new version of IBM Video Central does not use the new stored procedure db2xml.dxxGenXMLCLOB(). However, you can try it out yourself by using the sample code shown in Listing 2. If you do want to try it, use the following FixPack levels:

• DB2 XML Extender Version 7.2, FixPack 6
• DB2 Universal Database Version 7.2, FixPack 6

Back to top

Using DB2 Net Search Extender for high speed text search

For its Movie Search Web service, IBM Video Central uses the DB2 Net Search Extender's fast text search engine. Net Search Extender provides the following features that complement the functionality of DB2 Text Extender and DB2 Text Information Extender:

• Indexing:
• Provides a very fast index type called Ngram.
• Allows multiple indexes on the same text column.
• Processes indexing without locking data.
• Updates indexes incrementally to reflect changes in the database.
• Search:
• Provides a stored procedure on the server.
• Allows word, phrase, stemmed, or fuzzy search.
• Identifies and restricts searching to sections in the documents that have been marked by special tags.
• Offers numeric search on a range of values.
• Supports Boolean and wildcard operations.
• Search result:
• Lets you specify how the search results are sorted at indexing time, or uses rank values for sorting.
• Lets you specify search result subsets when large data volumes are searched and large result lists are expected.
• Lets you set a limit on search terms with a high hit count.
• Allows positioning (cursor setting) access on search results.

The Net Search Extender has the benefits of fast indexing of very large data volumes, and in-memory searching at high speed with a large number of concurrent users.

In the Video Central, we have two tables, IVC.TITLEINFO and IVC.TITLEPLOT, to store the movie titles and movie plots summaries, respectively. The Movie Search Web service allows searching by title information or by movie plot. Figure 5 shows the steps that are needed to support the functionality of high-speed movie search in Video Central. We need to enable a database for using the Net Search Extender and enable the text columns for the table before we can use the provided stored procedure, textSearch(). The search results are returned from the stored procedure as a result set. Refer to the class MovieDataAccess for how to use the stored procedure provided by Net Search Extender from Java program.

In the sample client of IBM Video Central, when a Movie Search request is processed a movie search handler (class MSHandler) is created from the class ReqHandlerFactory. In movie search handler, MovieSearchProxy (generated from the movie search WSDL documents of the Video Central) is instantiated and the search request is invoked through the proxy and sent to the SOAP runtime in the Video Central. For the detailed information, refer to the class of MSHandler in the client code.

Back to top

Using WebSphere Application Server Version 4.0 as Web services server

The Java^TM 2 platform, Enterprise Edition (J2EE) offers a roadmap for companies to develop portable and highly scalable applications. WebSphere 4.0 is compliant with J2EE 1.2, which consists of the following three categories:

• Components
• Enterprise JavaBeans (EJB) 1.1
• JavaServer Page (JSP) 1.1
• Servlet 2.2
• Services
• Java Naming and Directory Interface (JNDI) 1.2
• JDBC 2.0
• Communications
• Java Message Service (JMS) 1.0
• JavaMail 1.1

Other technologies are provided with WebSphere Application Server version 4.0 including:

• J2EE 1.3 preview features
• Java 2 Connectors (J2C)
• JMS/XA
• JMS Listener
• Workload management (scalability support)
• Web services

Compared with WebSphere 3.5, WebSphere 4.0 also has new and improved tools:

• Application Assembly Tool (AAT). Assembles enterprise applications in EAR or WAR file for deployment into WebSphere.
• EJBDeploy. Prepares Enterprise JavaBeans for deployment, and is a command-line tool that is called by the graphical AAT behind the scenes.
• SEAppInstall. Installs applications on the Single Server editions
• Improved Log Analyzer. Sorts, organizes, separates and analyzes logs, displaying more details on things like which thread and which process ID were the source of an event.
• Improved Resource Analyzer. Records details about what requests WebSphere is handling and how fast it is handling them.

WebSphere 4.0 has a strong support for Web services. Figure 6 hows how WebSphere 4.0 supports Web services.

WebSphere Application Server provides support for both SOAP server and client environments. This enables WebSphere applications to send and receive SOAP messages. WebSphere's integration of a Java interface to UDDI enables WebSphere applications to publish and find Web services. Integration of SOAP enables Web services deployed on the WebSphere platform to use platform strengths such as security, transaction monitoring and trace/debug functions. To enable an enterprise application to use the SOAP environment, WebSphere provides the SOAPEarEnable script, which creates a SOAP enabled EAR file from the original EAR file and the SOAP deployment descriptor file. If WebSphere Studio Application Developer is used as the development tool, the SOAP enabled EAR file can be generated automatically from the Web services application.

Back to top

An alternative data access mechanism using DADX

The current version of IBM Video Central does not utilize DADX. This section highlights the DADX technology and how to use it to simplify the implementation of Web services provided by IBM Video Central.

The DADX is an XML technology for creating Web services that access relational databases. It is an extension of the XML Extender document access definition (DAD) file. The DADX makes it easy to create Web services that store and retrieve XML and relational data. A DADX document specifies how to create a Web service using a set of operations that are defined by SQL statements and, optionally, DAD files. As previously discussed, a DAD file is used to define the mapping of XML and relational data. Web services specified in a DADX file are called DADX Web services. Listing 3 is a simple DADX file:

Listing 3. A DADX file

 
 
<?xml version="1.0" encoding="UTF-8"?> 
  <DADX xmlns="http://schemas.ibm.com/db2/dxx/dadx"> 
     <operation name="listDepartments"> 
      <query> 
        <SQL_query>SELECT * FROM DEPARTMENT</SQL_query> 
      </query> 
     </operation> 
  </DADX> 

DADX Web services are implemented by Web services Object Runtime Framework (WORF) tools. WORF provides the runtime support for invoking DADX documents as Web services in SOAP 2.2, which is supported by WebSphere Application Server and Jakarta Tomcat. WORF supports the following operations:

• SQL operations:
• <query>: Queries the database
• <update>: Updates the database
• <call>: Calls stored procedures
• XML collection operations:
• <retrieveXML>: Generates XML documents
• <storeXML>: Stores XML documents

WORF supports generating and storing XML documents by using the XML collection method, and it also allows stored procedures and SQL statements to be exposed as Web service operations. In addition, WORF can generate a test page, WSDL document and XML Schema Definition (XSD) according to the command specified in the URL of service requests:

• Test: Generates a test page with documentation for DADX services. It takes inputs from the test page, invokes the Web service and returns the result in XML document.
• WSDL: Generates the WSDL document for DADX services. The WSDL document can be provided to service requesters.
• XSD: Generates XSD, which contains the data types used in the Web services interface.

Figure 7 is an overview of the WORF framework. Listing 4 shows the DADX file invoked by the service request.

Listing 4. DADX invoked to request a list of departments

 
<?xml version="1.0" encoding="UTF-8"?> 
  <DADX xmlns="http://schemas.ibm.com/db2/dxx/dadx"> 
  <operation name="listDepartments"> 
    <retrieveXML> 
       <DAD_ref>departments.dad</DAD_ref> 
       <no_override> 
    </retrieveXML> 
  </operation> 
  </DADX> 

WORF receives a HTTP SOAP GET or POST service request. The URL of the request specifies a DADX, which can also contain input parameters, and the requested action, which can be a DADX operation or a command. WORF loads the DADX file specified in the request. Then for operations, it loads a DAD file if requested, replaces parameters with requested values, connects to DB2 and runs any SQL statements including SQL calls, and formats the result into XML. For commands, it generates necessary files, test pages, or other responses required.

WebSphere Studio Application Developer provides tools to create DADX files. The XML from the SQL wizard supports the creation of a DADX file from SQL queries, DAD files, or both, as shown in Figure 8. This makes it much easier to create data access Web services.

Note that DB2 Web services can also be created outside of WebSphere Studio Application Developer using any text editor to create the necessary DADX files.

After you create a DADX file in WebSphere Studio Application Developer, you can use the Web services DADX Group Configuration wizard to configure your database connections, and then use the Web Services wizard to generate your WSDL documents, deployment descriptors, client proxy, property mappings, deployment mappings, and test your DADX Web services in preparation for publishing your Web services to the UDDI registry.

The generated DADX file is shown in Listing 5.

Listing 5. A DADX file that was generated by WebSphere Studio Application Developer

 
<?xml version="1.0" encoding="UTF-8"?> 
<dadx:DADX xmlns:dadx="http://schemas.ibm.com/db2/dxx/dadx" 
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
      xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
      xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
      xsi:schemaLocation="http://schemas.ibm.com/db2/dxx/dadx dadx.xsd 
                          http://schemas.xmlsoap.org/wsdl/ wsdl.xsd"> 
   <dadx:operation name="updateDepartment"> 
        <wsdl:documentation xmlns="http://www.w3.org/1999/xhtml"> 
            This operation updates the department name and location. 
        </wsdl:documentation> 
		<dadx:update> 
            <dadx:SQL_update> 
<![CDATA[ 
                UPDATE YIYING.DEPARTMENT SET DEPTNAME = :deptname, LOCATION = 
  :location WHERE YIYING.DEPARTMENT.DEPTNO = :deptno 
]]> 
            </dadx:SQL_update> 
            <dadx:parameter name="deptno" type="xsd:string"/> 
            <dadx:parameter name="deptname" type="xsd:string"/> 
            <dadx:parameter name="location" type="xsd:string"/> 
        </dadx:update> 
   </dadx:operation> 
   <dadx:operation name="listDepartment"> 
        <wsdl:documentation xmlns="http://www.w3.org/1999/xhtml"> 
            This operation lists the information of a department. 
        </wsdl:documentation> 
        <dadx:query> 
            <dadx:SQL_query> 
<![CDATA[ 
               SELECT * FROM YIYING.DEPARTMENT WHERE 
YIYING.DEPARTMENT.DEPTNO = :deptno 
]]> 
           </dadx:SQL_query> 
           <dadx:parameter name="deptno" type="xsd:string"/> 
       </dadx:query> 
    </dadx:operation> 
</dadx:DADX> 

You can try using a DADX to implement IBM Video Central services. Listing 6 is a sample of DADX for Customer Wish List Web service. It is generated from WebSphere Studio Application Developer. You can try it out by yourself to modify IBM Video Central by using DADX.

Listing 6. A DADX to process wish list information

 
<?xml version="1.0" encoding="UTF-8"?> 
<dadx:DADX xmlns:dadx="http://schemas.ibm.com/db2/dxx/dadx" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
     xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
     xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
     xsi:schemaLocation="http://schemas.ibm.com/db2/dxx/dadx dadx.xsd 
                         http://schemas.xmlsoap.org/wsdl/ wsdl.xsd"> 
   <dadx:operation name="queryWishList"> 
     <wsdl:documentation xmlns="http://www.w3.org/1999/xhtml"> 
         This is to query wish list information. 
     </wsdl:documentation> 
     <dadx:query> 
          <dadx:SQL_query> 
<![CDATA[ 
               SELECT DISTINCT IVC.USERWISHES.TITLEID FROM IVC.USERWISHES 
WHERE IVC.USERWISHES.USERID = :userid 
]]> 
          </dadx:SQL_query> 
          <dadx:parameter name="userid" type="xsd:int"/> 
     </dadx:query> 
   </dadx:operation> 
   <dadx:operation name="addTitleToWishList"> 
     <wsdl:documentation xmlns="http://www.w3.org/1999/xhtml"> 
         This is to add movie titles to the wish list. 
     </wsdl:documentation> 
     <dadx:update> 
         <dadx:SQL_update> 
<![CDATA[ 
             INSERT INTO IVC.USERWISHES ( USERID, BUSINESSID, TITLEID, 
TITLEDESC, DATE ) VALUES ( :userid, :businessid, :titleid, :titledesc, :idate 
) 
]]> 
         </dadx:SQL_update> 
         <dadx:parameter name="userid" type="xsd:int"/> 
         <dadx:parameter name="businessid" type="xsd:int"/> 
         <dadx:parameter name="titleid" type="xsd:int"/> 
         <dadx:parameter name="titledesc" type="xsd:string"/> 
         <dadx:parameter name="idate" type="xsd:date"/> 
     </dadx:update> 
   </dadx:operation> 
   <dadx:operation name="deleteTitlesFromWishList"> 
     <wsdl:documentation xmlns="http://www.w3.org/1999/xhtml"> 
         This is to remove movie titles from the wish list. 
      </wsdl:documentation> 
      <dadx:update> 
         <dadx:SQL_update> 
<![CDATA[ 
             DELETE FROM IVC.USERWISHES WHERE IVC.USERWISHES.USERID = 
:userid AND IVC.USERWISHES.TITLEID = :titleid 
]]> 
         </dadx:SQL_update> 
         <dadx:parameter name="userid" type="xsd:int"/> 
         <dadx:parameter name="titleid" type="xsd:int"/> 
     </dadx:update> 
   </dadx:operation> 
</dadx:DADX> 

Back to top

Summary

IBM Video Central is a sample application of IBM e-business solutions, and has been implemented using the most advanced technologies provided by IBM. Following the first part of the article, this paper summarizes the new version of IBM Video Central sample application, highlighting the new technologies and DB2 Universal Database as a Web services provider. The purpose of this paper is to outline Web services and IBM Video Central. More information can be found from our IBM Video Central tutorial.

Resources

• IBM Video Central download Web site: http://www-106.ibm.com/developerworks/db2/library/samples/videocentral/videocentral.html
  
  
• Part 1 of the article: http://www-106.ibm.com/developerworks/db2/library/techarticle/zhang/0109zhang.html
  
  
• IBM Video Central for e-business: Web Services Privacy, Security, and Accuracy: http://www-106.ibm.com/developerworks/db2/library/techarticle/alazzawe/0112alazzawe.html
  
  
• IBM Video Central for e-business: Business Rationale, Requirements, and Web Services Description: http://www-106.ibm.com/developerworks/db2/library/techarticle/alazzawe/0111alazzawe.html
  
  
• DB2 XML Extender download Web site: http://www.ibm.com/software/data/db2/extenders/xmlext/support/fixpak.html
  
  
• DB2 Net Search Extender Web site: http://www.ibm.com/software/data/db2/extenders/netsearch/index.html
  
  
• Document Access Definition eXtension (DADX): www.ibm.com/software/data/webservices
  
  
• DB2 Developer Domain: www.ibm.com/software/data/developer
  
  

About the authors

Yiying Zhang got her Ph.D. degree in Computer Science in July 1999 and joined the IBM Toronto Lab in September 2000. Her role is to help customers with DB2 and WebSphere integration problems, deliver tutorials of IBM e-business solutions, and perform solution testing and integration for DB2, WebSphere and other IBM products.

Grant Hutchison leads DB2/WebSphere integration efforts within the DB2 team at the IBM Toronto Lab. Coauthor of the DB2 Certification Guide for Common Servers (Prentice Hall, 1996); Grant has participated in DB2 UDB's growth for 11 years.

DB2 Solution Integration Center team
The DB2 Solution Integration Center provides integration testing, tutorial and white paper development, and assists other IBM product development groups and IBM customers. The team members are (from left to right): Back: Grant Hutchison, Patrick Zeng, Tijana Tripkovic, Quentin Presley, Yiying Zhang, Vivien Page, Kate Kurtz
Front: Samuel Chan, Rahul Kitchlu, Connie Tsui
Missing in this picture: Peter He, Matthew Golec, Jordan Barnes

Comments (Undergoing maintenance)

Back to top

Trademarks  |  My developerWorks terms and conditions

Table of contents

• Introduction
• Overview of Web services
• The IBM Video Central scenario
• The IBM Video Central architecture
• Rapid application development using WebSphere Studio Application Developer
• Using DB2 XML Extender for storing and retrieving XML data
• Using DB2 Net Search Extender for high speed text search
• Using WebSphere Application Server Version 4.0 as Web services server
• An alternative data access mechanism using DADX
• Summary
• Resources
• About the authors
• Comments

Next steps from IBM

• Try: DB2 Enterprise
• Demo: DB2 serving ATOM feed
• Webcast: A smarter way to successful SOA - Information as a trusted strategic asset
• Briefing: Information on Demand
• Buy: DB2 Enterprise

My developerWorks community

Dig deeper into Information Management on developerWorks

DB2 pureScale

See how true transparent scaling architecture can be achieved on distributed platforms

Special offers