How To
Summary
You can configure the Content Services GraphQL API container to work with a traditional WebSphere Application Server hosted Content Platform Engine. This configuration is useful if you need to use features or extensions that require the Content Services GraphQL API, but you are not ready to move your environment to containers.
Document Location
Worldwide
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"ARM Category":[{"code":"a8m0z000000cwLDAAY","label":"Container"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.5.4;and future releases","Line of Business":{"code":"LOB76","label":"Data Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
28 April 2025
UID
ibm16210693