with IBM FileNet P8 APIs" />
Read it now on the O’Reilly learning platform with a 10-day free trial.
O’Reilly members get unlimited access to books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
Book description
This IBM® Redbooks® publication can help you develop content and process management applications with IBM FileNet® APIs. The IBM FileNet P8 suite of products contains a set of robust APIs that range from core platform APIs to supporting application APIs. This book focuses specifically on Content Engine and Process Engine APIs.
Content Engine API topics that we discuss include creating, retrieving, updating, and deleting objects; querying and viewing documents; and batching and batch execution. We also explore more complex topics, including permissions and authorization, versioning, relationships, annotations, workflow subscriptions and event actions, metadata discovery, and dynamic security inheritance.
Process Engine API topics that we discuss include launching a workflow, searching for and processing work items, and working with process status. The more complex topics we cover include, Component Integrator application space, role, workbasket, resource navigation in Process Engine REST API, ECM Widgets, and building a custom Get Next In-basket widget.
To help you better understand programming with IBM FileNet APIs, we provide a sample application implemented for a fictional company. We include the data model, security model, workflows, and various applications developed for the sample. You can download them for your reference.
This book is intended for IBM FileNet P8 application developers. We recommend using this book in conjunction with the online ECM help.
Show and hide more
Table of contents Product information
Table of contents
- Front cover
- Figures
- Notices
- Trademarks
- The team who wrote this book
- Become a published author
- Comments welcome
- 1.1 Platform overview
- 1.2 IBM FileNet API overview
- 1.2.1 Content Engine APIs
- 1.2.2 Process Engine APIs
- 1.2.3 Records Manager Java API
- 1.2.4 The eForms APIs
- 1.2.5 Capture APIs
- 1.2.6 Image Services Resource Adapter
- 2.1 Content Engine Java development setup
- 2.1.1 Required libraries
- 2.1.2 Transport protocols
- 2.1.3 Thick client versus thin client requirements
- 2.1.4 Sample Content Engine Java API application setup in Eclipse
- 2.2.1 Required libraries
- 2.3.1 Prerequisites
- 2.3.2 Running the sample application supplied by IBM
- 2.3.3 Configuring VisualStudio.NET 2005
- 3.1 Content Engine API class overview
- 3.1.1 Content Engine API class model
- 3.2.1 User authentication
- 3.2.2 Java
- 3.2.3 .NET
- 3.4.1 Pending actions
- 3.4.2 Creating objects
- 3.4.3 Working with properties
- 3.4.4 Retrieving objects
- 3.4.5 Deleting objects
- 3.4.6 Retrieving content
- 3.4.7 Working with property filters
- 3.6.1 SearchSQL
- 3.6.2 Search scope
- 3.6.3 Content searches
- 3.6.4 Paging support
- 3.7.1 User tokens
- 4.1 Permissions and authorization
- 4.2 Versioning
- 4.3 Relationships
- 4.3.1 Object-valued properties
- 4.3.2 Filing in a folder
- 4.3.3 Compound documents
- 5.1 Process Engine API overview
- 5.1.1 Functional groups
- 5.1.2 Available API functionality
- 5.1.3 Naming conventions
- 5.1.4 Core classes
- 5.1.5 Functional relationship
- 5.2.1 Java API scenario
- 5.2.2 PEWS API scenario
- 5.2.3 REST API scenario
- 5.3.1 VWException object
- 5.3.2 Steps to handle an exception
- 5.4.1 REST API scenario
- 5.5.1 Query a roster
- 5.5.2 Workflow queues
- 5.5.3 Query event log
- 5.6.1 Retrieve step element
- 5.6.2 Get step element parameters
- 5.6.3 Set step element parameter values
- 5.6.4 Complete work items
- 5.7.1 Retrieve process history
- 5.7.2 Retrieve process milestones
- 6.1 Component Integrator
- 6.1.1 CE_Operations component
- 6.1.2 Implementing a custom Java component
- 6.2.1 Retrieve role list
- 6.2.2 Retrieve role description and attributes
- 6.2.3 Retrieve workbasket
- 6.2.4 Query work items from workBasket
- 6.4.1 ECM Widgets concepts
- 6.4.2 ECM Widgets system architecture
- 6.5.1 Use case for the Get Next widget
- 6.5.2 Setup development environment
- 6.5.3 Code structure of the Get Next widget
- 6.5.4 Defining the Get Next widget
- 6.5.5 Code skeleton for GetNext.js
- 6.5.6 Rendering the Get Next widget user interface
- 6.5.7 Invoking PE REST service to fetch queue element
- 6.5.8 Invoking PE REST service to fetch role and In-basket list
- 6.5.9 Deploying the widget
- 6.5.10 Building the solution
- 7.1 Introduction to sample applications
- 7.2 Business use cases
- 7.3 User view of the sample applications
- 7.3.1 User view: Reservation Web application
- 7.3.2 User view: Kiosk application
- 7.3.3 User view: Agent handheld application
- 7.3.4 User view: Fleet Status Manager Web application
- 7.3.5 User view: Billing Report application
- 7.4.1 Base classes
- 7.4.2 ITSOVechicle
- 7.4.3 ITSOPhotoGallery
- 7.4.4 ITSOThumbnail
- 7.4.5 ITSOVehicleActivity
- 7.4.6 ITSOSingleton
- 7.4.7 ITSORentalActivity
- 7.4.8 ITSOMaintenanceActivity
- 7.4.9 ITSODisposalActivity
- 7.4.10 ITSOIdleActivity
- 7.4.11 ITSOCustomer
- 7.4.12 ITSOCommentary
- 7.4.13 ITSOFranchise
- 7.4.14 ITSORole
- 7.6.1 Isolated region configuration
- 7.6.2 Component queues
- 7.6.3 Vehicle reservation workflow
- 7.6.4 Vehicle maintenance workflow
- 7.7.1 Architecture: Reservation Web application
- 7.7.2 Architecture: Kiosk application
- 7.7.3 Architecture: Fleet Status Manager Web application
- 7.7.4 Architecture: Billing Report application
- 7.8.1 Application package structure
- 7.8.2 Content Engine artifacts
- 7.8.3 Process Engine artifacts
- 7.8.4 Deployment: Reservation Web application
- 7.8.5 Deployment: Kiosk application
- 7.8.6 Deployment: Fleet Status Manager Web application
- 7.8.7 Deployment: Billing Report application
- 8.1 Logging
- 8.1.1 CE Java API
- 8.1.2 CE .NET API
- 8.1.3 Content Engine Web Services
- 8.1.4 PE Java API
- 8.1.5 Process Engine Web Services
- 8.1.6 PE REST Service
- 8.2.1 log4j debugging
- 8.2.2 Content Engine troubleshooting techniques
- 8.2.3 Process Engine troubleshooting techniques
- 8.2.4 Data must be gathered for troubleshooting
- Locating the Web material
- Using the Web material
- IBM Redbooks
- Online resources
- How to get Redbooks
- Help from IBM
Show and hide more
Product information
- Title: Developing Applications with IBM FileNet P8 APIs
- Author(s): Wei-Dong Zhu, Bill Carpenter, Tim Lai, Wei Liao, Michael Oland, James S Pagadala, Juan Saad
- Release date: December 2009
- Publisher(s): IBM Redbooks
- ISBN: None
You might also like
Check it out now on O’Reilly
Dive in for free with a 10-day trial of the O’Reilly learning platform—then explore all the other resources our members count on to build skills and solve problems every day.