Cover image for Implementing Web Applications with CM Information Integrator for Content and OnDemand Web Enablement Kit.
Implementing Web Applications with CM Information Integrator for Content and OnDemand Web Enablement Kit.
Title:
Implementing Web Applications with CM Information Integrator for Content and OnDemand Web Enablement Kit.
Author:
Redbooks, IBM.
Personal Author:
Physical Description:
1 online resource (624 pages)
Contents:
Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Introduction -- Chapter 1. Web application basics -- 1.1 Overview -- 1.1.1 Common features -- 1.1.2 Web server -- 1.1.3 Web application packaging -- 1.1.4 Web services: Service-oriented application -- 1.1.5 Web services standards -- 1.2 Java servlet -- 1.2.1 Servlet container -- 1.2.2 Servlet API -- 1.2.3 Servlet life cycle -- 1.2.4 Sharing information -- 1.2.5 Filtering requests and responses -- 1.2.6 Maintaining client and application state -- 1.2.7 Packaging servlets -- 1.3 JavaServer Pages (JSP) -- 1.3.1 JSP elements -- 1.3.2 JSP Standard Tag Libraries (JSTL) -- 1.3.3 JSP life cycle -- 1.3.4 JSP translation and compilation -- 1.3.5 JSP advantages -- 1.3.6 Packaging JSPs -- 1.4 JavaServer Faces technology (JSF) -- 1.4.1 JSF APIs -- 1.5 Model-View-Controller architecture -- 1.5.1 MVC advantages -- 1.6 Java 2 Platform Enterprise Edition (J2EE) -- 1.6.1 J2EE architecture -- 1.6.2 Component technologies -- 1.6.3 Packaging J2EE applications -- 1.7 Struts -- Chapter 2. Content Manager overview -- 2.1 Overview -- 2.1.1 System components -- 2.1.2 System configuration -- 2.2 Data modeling -- 2.2.1 Items and item types -- 2.2.2 Attributes and attribute groups -- 2.2.3 Root and child components -- 2.2.4 Item type classifications -- 2.2.5 Versioning -- 2.2.6 Links, references, and foreign keys -- 2.3 Document Routing -- 2.3.1 Key concepts -- 2.3.2 Process -- 2.3.3 Work nodes -- 2.3.4 Work packages -- 2.3.5 Worklists -- 2.4 Security and privilege sets -- 2.4.1 Access control list (ACL) -- 2.4.2 Privilege and privilege set -- 2.5 Information Integrator for Content -- 2.5.1 Information access -- 2.5.2 Services -- 2.5.3 Administration database and client -- Chapter 3. OnDemand overview -- 3.1 Overview.

3.2 Basic concepts -- 3.2.1 Applications -- 3.2.2 Application groups -- 3.2.3 Folder -- 3.2.4 Indexing methods and documents -- 3.3 Servers and server programs -- 3.3.1 System configuration -- Chapter 4. Case study -- 4.1 Business case -- 4.1.1 Current building permit process -- 4.2 Redbrook County legacy system -- 4.3 Business problem -- 4.3.1 User requirements -- 4.4 Proposed solution -- 4.4.1 System architecture -- 4.4.2 Web-based application modules -- 4.4.3 Content Manager data model -- 4.4.4 OnDemand system setup -- Part 2 Developing CM Web applications with Information Integration for Content -- Chapter 5. Information Integrator for Content programming overview -- 5.1 API overview -- 5.2 Information Integrator for Content Java classes -- 5.3 Information Integrator for Content Java beans -- 5.3.1 Non-visual beans -- 5.3.2 Visual beans -- 5.4 Java viewer toolkit -- 5.5 Content server and DDO concept -- 5.5.1 Content server -- 5.5.2 Dynamic data object (DDO) and extended data object (XDO) -- 5.6 Mapping the terminology -- Chapter 6. Quick start in Web application development -- 6.1 Introduction -- 6.2 Development environment setup -- 6.2.1 Setting up the development directory -- 6.2.2 Setting up a new Web project -- 6.2.3 Setting up a new server project to run the sample code -- 6.3 Developing sample code with the Java OOAPIs -- 6.3.1 Adding the common files to the Web project -- 6.3.2 Working with attributes -- 6.3.3 Working with item types -- 6.3.4 Working with items -- 6.4 Conclusion -- Chapter 7. Building a generic application -- 7.1 Introduction -- 7.2 Development environment setup -- 7.3 Sample application -- 7.3.1 How to get the most benefit from this chapter -- 7.3.2 Set up and run the sample application -- 7.3.3 Import the beans into the code -- 7.3.4 The Controller program: RBController -- 7.3.5 Listing available servers: CMBConnection.

7.3.6 Connecting to server: CMBConnection, CMBConnectionPool -- 7.3.7 Schema: CMBSchemaManagement -- 7.3.8 Listing entities: CMBEntity -- 7.3.9 Listing search templates: CMBSearchTemplate -- 7.3.10 Listing attributes: CMBAttribute -- 7.3.11 Listing search criteria: CMBSTCriterion -- 7.3.12 Sorting arrays of beans -- 7.3.13 Conducting a search: CMBQueryServices -- 7.3.14 Processing search results: CMBSearchResults -- 7.3.15 Representing items: CMBItem -- 7.3.16 Displaying item information -- 7.3.17 Managing content: CMBDataManagement -- 7.3.18 Viewing content: CMBDocumentServices -- 7.3.19 Content Manager Version 8 Document Routing system -- 7.4 Conclusion -- Chapter 8. Building a case study application -- 8.1 Introduction -- 8.2 Application framework description -- 8.3 Development environment setup -- 8.3.1 Create a new EAR and WAR project -- 8.3.2 Set up the Java build path and required libraries -- 8.3.3 Create a server project to run the sample code -- 8.3.4 Create the basic framework setup -- 8.4 Login use case -- 8.4.1 Use case description -- 8.4.2 Design -- 8.4.3 Model layer implementation -- 8.4.4 Session bean implementation -- 8.4.5 Controller layer implementation -- 8.4.6 View layer implementation -- 8.4.7 Test -- 8.5 Building permit application approval process use case -- 8.5.1 General use case description -- 8.5.2 RedBrook DB2 legacy system setup -- 8.5.3 Content Manager definition setup -- 8.5.4 Create building permit application folder use case -- 8.5.5 Process building permit application folder use case -- 8.5.6 Document import use case -- 8.6 External application -- 8.6.1 Internet sample application use cases -- 8.6.2 Framework file descriptions -- 8.6.3 Import Internet sample application WAR file -- 8.6.4 Testing -- 8.7 Conclusion -- Chapter 9. Adding text search capability -- 9.1 Introduction -- 9.1.1 Text search syntax.

9.2 Start Content Manager text search service -- 9.3 System setup -- 9.4 Integrating the text search module with the Web application -- 9.5 Conclusion -- Chapter 10. Adding document rendering capability -- 10.1 Introduction -- 10.1.1 Viewer architecture -- 10.2 Integrating the viewer toolkit -- 10.2.1 Environment setup -- 10.2.2 Import the necessary viewer toolkit files -- 10.2.3 Implement code changes to use the viewer toolkit -- 10.2.4 Run and test the viewer functionality -- 10.2.5 Viewer toolkit certificates -- 10.3 Conclusion -- Part 3 Developing OnDemand Web applications -- Chapter 11. Web enabling OnDemand -- 11.1 Introduction -- 11.1.1 OnDemand Web Enablement Kit -- 11.1.2 ODWEK platforms and Web environments -- 11.2 ODWEK samples -- 11.2.1 CGI and servlet HTML samples -- 11.2.2 ODWEK documentation -- 11.2.3 Viewing and transforming documents -- 11.3 Comparing ODWEK to Information Integrator for Content -- 11.3.1 API differences -- 11.3.2 ODWEK -- 11.3.3 eClient/Information Integrator for Content -- 11.3.4 Viewing technology differences -- 11.3.5 EBCDIC or transaction/line reports -- 11.3.6 Viewing image data stored in OnDemand -- 11.3.7 Xenos transforms -- 11.3.8 IBM printing systems AFP2WEB transforms -- 11.4 Comparing OnDemand clients -- Chapter 12. ODWEK installation and configuration -- 12.1 Installing CGI ODWEK on Windows -- 12.1.1 Installing Java Runtime Environment (JRE) -- 12.1.2 Installing IBM HTTP server -- 12.1.3 Installing ODWEK base code -- 12.1.4 Installing ODWEK releases, modifications, and PTFs -- 12.1.5 Configuring HTTP and ODWEK -- 12.1.6 Testing CGI ODWEK -- 12.2 Line data applets -- 12.3 Installing the ODWEK servlet on Windows -- 12.3.1 Installing Java Runtime Environment (JRE) -- 12.3.2 Installing WebSphere Application Server 5.0 for Windows -- 12.3.3 Installing the ODWEK servlet -- 12.3.4 Installing ODWEK servlet fixes.

12.3.5 Copying files -- 12.3.6 Setting up the system environment -- 12.3.7 Assembling the servlet -- 12.3.8 Deploying the ODWEK servlet -- 12.3.9 Customizing arswww.ini -- 12.3.10 Testing the ODWEK servlet -- 12.3.11 Customizing IBM HTTP server -- 12.3.12 Customizing ODWEK -- 12.3.13 Testing the sample application -- 12.4 Conclusion -- Chapter 13. Building a Web application with ODWEK APIs -- 13.1 ODWEK Java APIs overview -- 13.1.1 ODServer class -- 13.1.2 ODFolder class -- 13.1.3 ODCriteria class -- 13.1.4 ODHit class -- 13.2 Set up development environment -- 13.3 Developing the sample Web application -- 13.3.1 The RBMgrServlet implementation details -- 13.3.2 Login and logoff -- 13.3.3 Retrieving OnDemand folders -- 13.3.4 Retrieving OnDemand folder reports -- 13.4 Packaging and deploying Web applications -- 13.5 Running the sample Web application -- 13.6 Conclusion -- Part 4 Appendixes -- Appendix A. Setting up case study infrastructure -- A.1 Set up RedBrook County legacy database system -- A.2 Set up Content Manager system -- A.2.1 Configuration scripts -- A.2.2 Content Manager System Administration UI -- A.3 Set up OnDemand system -- A.4 Set up WebSphere Studio Application Developer -- A.5 Getting familiar with project files -- A.5.1 Set up Config.properties files -- A.5.2 Run the Web sample applications -- A.6 Navigate the Web sample application -- A.6.1 Internal application navigation -- A.6.2 External application navigation -- A.7 Redbrook County legacy system database schema -- A.8 Content Manager system definition -- A.9 OnDemand system definition -- A.9.1 Property Owner folder -- A.9.2 Permits -- A.9.3 Tax Information folder -- A.9.4 Attributes mapping among DB2, OnDemand, and CM -- Appendix B. Sample code -- B.1 Quick start sample code -- B.2 Generic Web application sample code -- B.3 Building permit application folder use case.

Appendix C. Additional material.
Local Note:
Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2017. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries.
Electronic Access:
Click to View
Holds: Copies: