Contents

List of Examples

List of Figures

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Conventions

1 Introduction to Content Management SPI

• 1.1 Content Management SPI FAQ
  • 1.1.1 What is the CM SPI?
  • 1.1.2 Why Write an SPI?
  • 1.1.3 What are the Structures and Data Types that can be Exposed?
  • 1.1.4 What is the Difference Between an SPI Implementation and a Repository?
  • 1.1.5 Who Uses the SPI?
  • 1.1.6 How is an SPI Implementation Packaged and Made Available to the VCR?
  • 1.1.7 Where Does the SPI Implementation Run?
• 1.2 Architecture Overview of an SPI Implementation
  • 1.2.1 What components are involved in the SPI?
  • 1.2.2 What is the Relationship of the VCR Repository Construct and the WebLogic Portal Application?
  • 1.2.3 What Authentication Models are Available?
  • 1.2.4 How Does the VCR Interact With the SPI Implementation?

2 SPI Data Model

• 2.1 About the Content Management Data Model
• 2.2 Type Data Representation
• 2.3 Node Data Representation

3 SPI Capabilities and Versions

• 3.1 About SPI Capabilities
• 3.2 VCR Detection of the SPI Implementation Capabilities
• 3.3 SPI Interface Versions

4 Implementing an SPI

• 4.1 VCR SPI Implementation Interaction
• 4.2 Primary Classes for a Basic SPI Implementation
• 4.3 Repository Guidelines when Creating an SPI Implementation
• 4.4 Basic SPI Implementation
  • 4.4.1 Basic SPI Repository Implementation Code Example
  • 4.4.2 Basic SPI Ticket Implementation Code Example
• 4.5 Optional SPI Interfaces Implementation
  • 4.5.1 Exposing an Optional SPI Interface
• 4.6 SPI Interface Result Collections, Sorting, and Filtering
  • 4.6.1 Filtering and Sorting Results with the SPI
  • 4.6.2 Common SPI Interface Objects for Sorting and Filtering
• 4.7 Configuring Security
  • 4.7.1 Authorization and Identity Management Overview
  • 4.7.2 No Authentication
  • 4.7.3 WLP-Secured Resource Management
    • 4.7.3.1 WLP-Secured/Global User Identity Configuration
    • 4.7.3.2 WLP Secured/Mapped Credential User Configuration
  • 4.7.4 Natively-Secured Resource Management
    • 4.7.4.1 Natively-Secured/Global User Identity Configuration
    • 4.7.4.2 Natively-Secured/Mapped Credential User Configuration
  • 4.7.5 Identity Propagation with Native Security
• 4.8 Connecting and Logging Into a Third-Party Repository
• 4.9 Search Cache Configuration

5 Interface Topics

• 5.1 NodeOpsV1 SPI Interface Topics
  • 5.1.1 What Types of Operations are Supported by the NodeOpsV1 SPI Interface?
  • 5.1.2 What Type of Hierarchical Paths are Passed To and From the SPI layer?
  • 5.1.3 How Should the SPI Implementation Create Node Data Objects to be Returned?
  • 5.1.4 How Should the SPI Implementation Create Property Data Objects to be Returned
  • 5.1.5 What Should the SPI Implementation Do when Node Metadata is not Available?
  • 5.1.6 How are the Node ID and Property ID related?
  • 5.1.7 What Node Names are Valid?
  • 5.1.8 Example – Creating a Node with no ObjectClass
  • 5.1.9 Example – Creating a Node with an ObjectClass and Property Values
• 5.2 ObjectClassOpsV1 SPI Interface Topics
  • 5.2.1 What are the Supported Operation Types?
  • 5.2.2 How Should the SPI Implementation Create ObjectClass Objects?
• 5.3 SearchOpsV1 SPI Interface Topics
• 5.4 Indexing Content
  • 5.4.1 How Is Content Indexed?
  • 5.4.2 How Can an Event Listener Perform Content Indexing?
• 5.5 SPI Testing Topics
  • 5.5.1 How to Configure a Repository for SPI Parameter and Response Data Checking
  • 5.5.2 How to Monitor Repository and Ticket Method Invocations and Performance
  • 5.5.3 How to Monitor SPI Operation Interface Method Invocations and Performance