Content Management and Capture

 View Only
  • 1.  GraphQL - Best Practice for Instalation/deploy location Traditional WebSphere

    Posted Tue March 21, 2023 06:01 PM

    In a traditional WebSphere FileNet environment are there any best practices to follow about where to install and deploy GraphQL?

    What I mean is, given: ICN on one VM running in an App Server, CPE on another VM running in an App Server.   

    1. Does GraphQL need to go on another VM or can we spin up an additional App Server to run along side ICN or CPE. 
    2. If we can just add an App server, where does it make the most sense to add it. Along side ICN or CPE.

    Thank you for your insights.



    ------------------------------
    Chuck Hauble
    Minneapolis MN
    ------------------------------


  • 2.  RE: GraphQL - Best Practice for Instalation/deploy location Traditional WebSphere

    Posted Wed March 22, 2023 05:34 AM

    Hi Chuck,

    from a deployment perspective, you could install GraphQL into the same WAS instance as CPE (or ICN) or into its own WAS instance.

    In most scenarios, GraphQL will talk to the CPE, thus deploying it next to CPE might be useful to reduce network traffic. 

    I'd recommend to look into the install docs

    https://www.ibm.com/docs/en/filenet-p8-platform/5.5.x?topic=tasks-installing-configuring-content-services-graphql-api

    as it gives some advise on LTPA token, SSO, etc.

    Also very helpful is Rogers blog entry on the implementation of SSO.

    Hope this helps?

    Best regards,

    Michael



    ------------------------------
    Michael Kirchner
    Sr. Business Automation Partner Technical Specialist
    IBM Technology
    Germany
    ------------------------------



  • 3.  RE: GraphQL - Best Practice for Instalation/deploy location Traditional WebSphere

    Posted Fri March 24, 2023 10:30 AM

    Hello, Do you have a document valid for websphere cluster setup? I suspect we do not need to export and copy the ltpa key



    ------------------------------
    Maarten Vekens
    ------------------------------



  • 4.  RE: GraphQL - Best Practice for Instalation/deploy location Traditional WebSphere

    Posted Fri March 24, 2023 12:42 PM

    Hi Maarten,

    did you check out https://www.ibm.com/docs/en/filenet-p8-platform/5.5.x?topic=tasks-installing-configuring-content-services-graphql-api?

    Best regards,

    Michael



    ------------------------------
    Michael Kirchner
    Sr. Business Automation Partner Technical Specialist
    IBM Technology
    Germany
    ------------------------------



  • 5.  RE: GraphQL - Best Practice for Instalation/deploy location Traditional WebSphere

    Posted Mon March 27, 2023 04:22 AM

    yes, The connection to CPE is working. But I receive a badclass error, 2023-03-24T15:50:31.579 000000D7 ENG  FNRCE0002E - ERROR MethodName: determineBadClassRetry, 



    ------------------------------
    Maarten Vekens
    ------------------------------



  • 6.  RE: GraphQL - Best Practice for Instalation/deploy location Traditional WebSphere

    Posted Fri March 24, 2023 11:40 AM

    Hi Michael,

    From performance and best practices stand point, to handle 100k-200k GraphQL API calls per day , is it a better option to host the GraphQL on a dedicated t-WAS Cluster and instead of collocating with CPE JVM?

    Thanks & Regards,

    Sathish A Rajan



    ------------------------------
    Sathish Rajan
    ------------------------------



  • 7.  RE: GraphQL - Best Practice for Instalation/deploy location Traditional WebSphere

    Posted Fri March 24, 2023 01:04 PM

    Hi Sathish,

    I'm not aware that we have a best practise advise for this question.

    It'll definitively depend on the load you already see on the CPE and also on the nature of the requests you want to process. In case you would ingest the documents already via GraphQL, CPE and GraphQL may compete for the JVM memory, especially when handling very large documents or batches. This may not be critical in case the GraphQL requests will be only simple queries with low memory consumption. Maybe @Joe Raby has an educated guess on this question.

    In any way, using separate JVMs gives you a higher degree of freedom to fine tune and/or scale both components separately. Hosting them on the same machine should reduce the network bandwith consumed between GraphQL and the CPE, especially when uploading or downloading content via GraphQL.

    Best regards,

    Michael



    ------------------------------
    Michael Kirchner
    Sr. Business Automation Partner Technical Specialist
    IBM Technology
    Germany
    ------------------------------



  • 8.  RE: GraphQL - Best Practice for Instalation/deploy location Traditional WebSphere

    Posted Thu March 23, 2023 11:07 AM

    Hi Chuck.  One factor to consider is what applications will be connecting to the GrapQL service, and where those applications reside.  If the GraphQL client application is an external service (as is the case when using the Salesforce Connector for FileNet app) then the GraphQL service must be accessible from the public internet.  Otherwise, the Salesforce.com based app will not be able to reach it.  In this scenario, the best practice is to have the GraphQL service be hosted separately, on a public network, while the CPE service is hosted behind the corporate firewall, for better security.

    Aside from the networking requirements, generally speaking, an architecture of loosely coupled independent services is a good strategy, maximizing scalability, flexibility, and maintainability, and this would imply hosting separately.  But sometimes there are cost or network efficiency considerations which would favor co-hosting, especially for POC or demo systems.

    Regards,

    Joe



    ------------------------------
    Joe Raby
    ------------------------------