 | Openness and Standards Content Manager is based on industry standards and internet protocols. It supports HTTP, FTP, RTSP, JDBC, SQL, and LDAP. Designed to be fully open to any application. Content Manager publishes a robust set of application programming interfaces (APIs) to handle different types of content for unified search, retrieval, workflow, access control management and system administration. | Standards | Benefits |
|---|
| Federal Information Processing Standards (FIPS) 140-2 are NIST security requirements for cryptographic modules used in computer systems protecting sensitive but unclassified information. Compliance is mandated for all US government IT systems and product procurements. | DB2® Content Manager Enterprise Edition V8.3 uses the FIPS 140-2 approved cryptographic provider(s): - IBMJCEFIPS (certificate 376),
- IBMJSSEFIPS (certificate 409) and
- IBM® Crypto for C (certificate 384) for cryptography.
The certificates are listed on the NIST web site. |
|---|
| LDAP (Lightweight Directory Access Protocol) | Allows creation of single sign-on and creates secure, controlled access to any or all components of the IBM Content Manager system. |
|---|
| Unicode fully enabled for Content Manager Servers (mid-tier server, Library Server and Resource Managers), the eClient and all Java™ APIs | The emergence of the Internet and other distributed networks puts increasing importance on the ability to create software that can be developed independently of the countries or languages of intended users -- and then translated for multiple countries or regions. |
|---|
| Powerful XPath based query language | exploits the enhanced data model, including integrated parametric and text search, versioning, etc. |
|---|
| SQL Select statements | support direct, and authorized, access to information about documents, folders or other business objects |
|---|
Fully mirrored C++ and Java APIs optimized for performance, usability, and network efficiency.
Java Bean support for - versioning, links, child components
- document routing
- annotation functions and
- conversion functions for the Document Services Bean
- servlet and tag library
| Content can be tightly and seamlessly integrated into existing applications with less developer time and cost.
Different platforms or clients can be intermixed within the same solution. |
|---|
| |
|
