Technologies

This topic provides an overview of the operating system and platform technologies supported by Content Engine. For specific platform dependencies and supported version numbers, refer to the IBM FileNet P8 Hardware and Software Requirements. To download IBM FileNet documentation from the IBM support page, see Accessing IBM FileNet documentation.

J2EE Platform

Content Engine is implemented within a Java™ 2 Enterprise Edition (J2EE) standards-compliant application server environment. Therefore, it supports a wide variety of operating systems, directory service providers, application servers, and database servers. The J2EE platform also provides a distributed environment for improved scalability, reliability, and high availability through the use of clustering.

Operating Systems

Content Engine supports operating system platforms from Microsoft, Sun, IBM, Hewlett Packard, and Red Hat.

Application Servers

Content Engine supports J2EE compliant application servers from BEA, IBM, and JBoss.

Database Servers

Content Engine supports the relational database management functionality of Microsoft SQL Server, Oracle Database, and IBM DB2. Property information describing the Content Engine's objects is contained in object stores that reside in database servers. Configuration information describing the IBM FileNet P8 domain is also stored within a database.

Content Engine supports content storage either as items in a file system or protected storage device, or as binary large objects (BLObs) in the database.

Content Engine clients, including users of Workplace XT or Workplace, can execute property (metadata) and content (CBR) searches using native APIs, which also support querying a single object store or across multiple object stores.

Directory Service Providers

Content Engine supports directory servers such as Microsoft Active Directory, Novell eDirectory, IBM Tivoli Directory Server, Sun Java System Directory Server.

Client and Database Communication Protocols

Content Engine uses industry standard communication protocols such as TCP/IP and Java Database Connectivity (JDBC) for communication with the database server, and HTTP, Remote Method Invocation (RMI), and SOAP for communications with client applications.

Microsoft Management Console

Enterprise Manager is designed as a Microsoft Management Console (MMC) snap-in. The MMC provides a common framework for presenting and managing management applications. For example, you could snap in Enterprise Manager to the same MMC console as SQL Server's Enterprise Manager.

MMC itself provides no management behavior, but rather acts as a host for management applications. It provides a multiple-document interface (MDI) in which each window is a console. Each console can contain one or more administrative components that supply the management behavior.

Content Engine system administrators can save different MMC configurations with customized functions for different sets of operators and administrators. For example, a backup operator could be given a customized MMC console that includes just the backup and restore functionality needed for a particular job.

See Enterprise Manager for more information.