Another thing to keep in mind is CMIS as an API is also mothballed and we are switching to GraphQL moving forward: NOTE The future client API for FCM/FNCM/Content Services is the GraphQL API. (Per IBM DEV)" I don't think that there is any formal deprecation of the CMIS API, but it is worth noting that the CMIS standard is no longer active." SUB NOTE: On PREM GraphQL requires one or more GraphQL servers to handle the calls... (This (GraphQL server) is included in the new ORBIT [non Cloud pak, FNCM offering on OCP under AWS], ROSA SaaS config on AWS.) ( Please also be aware of the following two CMIS tech notes; (a) the support policy: https://www.ibm.com/support/pages/node/6584445, and (b) The impact of the Apache Chemistry project moving into the Attic : https://www.ibm.com/support/pages/node/6571191 )
Original Message:
Sent: Wed March 29, 2023 06:36 AM
From: Ankit Garg
Subject: What is your opinion around GraphQL
Hi Anup Reddy Mereddy, GraphQL is modernized query language comparing traditional CE Java API. In terms of advantages, please refer to https://www.howtographql.com/basics/1-graphql-is-the-better-rest/ and https://graphql.org/ which is also applicable to FileNet CE Java development. If you are looking for specific published certified say which is better and which is not, unfortunately this is not available. You may explore both implementation yourself and test via JMeter OR any other QA tool for your requirements.
** Please be mindful that not all query based operations are supported by GraphQL
The Content Services GraphQL API provides a schema and an easy-to-understand query language system that simplifies application development for your Content Platform Engine.
The API schema definition of types and fields matches Content Engine Java API object model closely, with necessary and desirable extensions for natural GraphQL developer consumption.
The feature set focuses on end-user runtime support, including the following operations:
- Metadata discovery - ClassDescription, PropertyDescription, ChoiceList, and sub-ClassDescriptions
- Document and Folder operations:
- Create, Read, Update, Delete (CRUD):
- Change class
- Update properties
- Update securities - ACLs and ACEs, delegated permissions, role permissions
- Object type-specific operations:
- Document - content upload and download, check in and check out, versioning, and cancel document checkout
- Folder - document file in and out
- Search and query
- Matches the Content Engine object model closely
- Metadata search and full text search
- Browse - folder hierarchy query of contained subfolders and documents:
- Containees can be obtained by selecting fields corresponding to similar Content Engine properties that return the containees of a folder.
- Alternatively the SQL-like search API can be used to obtain containees with control over filter and ordering criteria. The search API also allows the results from multiple queries to be returned in a single contiguous result set, allowing subfolders, documents and even custom objects to be retrieved in one set.
- Implicit support for columns and properties to return in the list based on data shaping.
- Paging, sorting, and so on.
Some more references:
https://community.ibm.com/community/user/automation/blogs/matt-vest1/2019/07/11/simplify-your-application-development-with-graphql
https://community.ibm.com/community/user/automation/blogs/kathryn-tirador1/2021/07/19/collaborate-search-develop-and-analyze-with-the-la
------------------------------
Ankit Garg Architect
Original Message:
Sent: Wed March 29, 2023 05:42 AM
From: Anup Reddy Mereddy
Subject: What is your opinion around GraphQL
well, I read the above documentation earlier but it does not give the perspective and comparative study of Graphql over Java api for content services. Why one should choose Graphql over Java api? What is the extra edge does it provide that doesn't meet by Java api?
------------------------------
Anup Reddy Mereddy
Original Message:
Sent: Mon March 27, 2023 01:27 AM
From: Ankit Garg
Subject: What is your opinion around GraphQL
Hi Anup Reddy Mereddy, Please refer to contextual thread below.
https://community.ibm.com/community/user/automation/discussion/graphql-best-practice-for-instalationdeploy-location-traditional-websphere#bmf30c11c5-1bb3-419e-a88a-018714439e5f
Please explore this also https://www.ibm.com/docs/en/filenet-p8-platform/5.5.x?topic=development-overview
Hope this would help. I doubt there is any specific performance testing OR white paper published. Thanks
------------------------------
Ankit Garg Architect
Original Message:
Sent: Fri March 24, 2023 05:36 PM
From: Anup Reddy Mereddy
Subject: What is your opinion around GraphQL
Please share your opinion in the context of http integrations such as integrations with non-FileNet web apps for operations like search, update metadata, retrieve and store single document. Consider metadata operations like search/update data in 2-3 millions of transactions per day.
Would you prefer to use FileNet GraphQL services over a RESTful service built using FileNet Java API.
What is the performance aspects of using Content JavaAPI based REST vs FileNet GQL?
Do you think GQL is fully developed with all capabilities that Java APIs offers, if not what are the limitations in GQL that can only be achieved by JavaAPI?
Which use cases does it best suitable in your perspectives.
Thanks in advancefor your time thinking about this question and providing responses.
------------------------------
Anup Reddy Mereddy
------------------------------