Skip to main content

· One min read

Work in Progress​

  • Today the team continued to troubleshoot the cluster issues.
  • The team tried adding custom annotations to disable Dynatrace injections.
  • The team deleted the non-postgreSQL driver related jars (from cpe pods).
  • The team discussed features included in the new version of FileNet. The team thinks upgrading will help resolve these errors.

Currently Tracking​

  • The team will work with the client to upgrade their environment to FileNet 5.5.11
  • We will continue to work closely with IBM support.

Next Steps​

Tracking​

Cases open: 2

  • Case TS014348824
  • Case TS014370797

Cases closed: 1

  • Case TS014232963

· One min read

Work in Progress​

  • Today the team continued to troubleshoot the cluster issues.
  • The team tried adding the oneagent annotation to the CR and that (potentially) caused errors in the operator, stating a syntax error.
  • Despite taking out the entry, the operator began to recreate the pods. The deployments had the annotation, but the init containers were still getting stuck on trying to copy DynaTrace folders, which means the agent was still getting injected.

Currently Tracking​

  • The team will continue to investigate Dynatrace to determine if it is involved with the errors in the cluster.
  • The client's team is working on an alternative way of sending logs. Email is blocking the files.
  • We will continue to work closely with IBM support.

Next Steps​

Tracking​

Cases open: 2

  • Case TS014348824
  • Case TS014370797

Cases closed: 1

  • Case TS014232963

· One min read

Work in Progress​

  • Today the team continued to troubleshoot the cluster issues.
  • The team increased the max connections for Postgres. However, the errors persisted.
  • The team collected more logs from today’s session.
  • There was a discussion around Dynatrace. The team sees a permission denied error in the pods involving Dynatrace. We encountered issues with Dynatrace in previous sessions and it looks like it may have been reenabled. The team speculated that this could be causing issues.

Currently Tracking​

  • The team will continue to investigate Dynatrace to determine if it is involved with the errors in the cluster.
  • We will continue to work closely with IBM support and have provided them logs of today’s session.

Next Steps​

Tracking​

Cases open: 2

  • Case TS014348824
  • Case TS014370797

Cases closed: 1

  • Case TS014232963

· One min read

Work in Progress​

  • Today the team continued to troubleshoot the cluster issues.
  • We had IBM support join this session to assist with the troubleshooting.
  • The team recreated the errors and gathered logs for further evaluation.

Currently Tracking​

  • The team is continuing to work with IBM support and examining the logs.

Next Steps​

Tracking​

Cases open: 2

  • Case TS014348824
  • Case TS014370797

Cases closed: 1

  • Case TS014232963

· One min read

Work in Progress​

  • Today the team continued to troubleshoot the cluster issues.
  • The team tried several troubleshooting steps including:
    • Scaling the cmis pods
    • Scaling the operator
    • Deleting and restarting pods in a crashloopbackoff
  • While the CPE pods did come back, they began to experience issues later in the session.
  • The errors persisted and the team grabbed multiple logs from today’s session.

Currently Tracking​

  • The team thinks that there are underlying issues with the cluster that are unrelated to FileNet.
  • The client's team noted they have a team member who they could work with to assist with troubleshooting the cluster and possibly join a future session.
  • We will continue to work closely with IBM support and have provided them logs of today’s session.

Next Steps​

Tracking​

Cases open: 2

  • Case TS014348824
  • Case TS014370797

Cases closed: 1

  • Case TS014232963

· One min read

Work in Progress​

  • While troubleshooting yesterday’s Postgres issue, the team noticed some failing pods in the client's environment.
  • The team tried several troubleshooting steps, but the pod errors persisted.
  • While troubleshooting, the team was able to validate cluster admin access.

Currently Tracking​

  • The team took logs and screenshots from this session and will be opening a case with IBM support.

Next Steps​

Tracking​

Cases open: 2

  • Case TS014348824
  • Case TS014370797

Cases closed: 1

  • Case TS014232963

· One min read

Work in Progress​

  • Today the team encountered a Postgres issue and the team spent time troubleshooting the error.
  • We pulled the logs from the pod and are currently working with support on the issue.

Currently Tracking​

  • The team is reviewing the most effective way to validate cluster admin access.
  • The team is continuing to work with support to address the error encountered in today’s session

Next Steps​

Tracking​

Cases open: 1

  • Case TS014348824

Cases closed: 1

  • Case TS014232963

· One min read

Work in Progress​

  • Today the team continued the walk-through of some of the functionality of Process Designer.

Currently Tracking​

  • The team is working closely with the support team to address the questions raised in today’s session.

Next Steps​

  • The team will work to answer the questions from today’s session and prep for Event Actions in our next session.

Tracking​

Cases open: 0

Cases closed: 1

  • Case TS014232963

· One min read

Work in Progress​

  • The team continued with the installation of Process Designer in the customer's environment.
  • In the previous session the team was encountering a authentication issue with Process Designer in the customer's environment. The team didn't make any changes to the customer's environment, but the authentication issue was no longer present. We took the logs back to the support team and await their feedback on the situation.
  • The team then began a walk-through of some of the functionality of Process Designer.

Currently Tracking​

  • The team plans to continue the Process Designer walk-through in the next session.
  • The team received the logs from today’s session. We will work with support and get their feedback.

Next Steps​

Tracking​

Cases open: 0

Cases closed: 1

  • Case TS014232963

· One min read

Work in Progress​

  • The team continued to walk through the installation of Process Designer in the client's environment.
  • The team was able to resolve the previous session’s startup error. When unpacking Process Designer, Windows added an additional folder that altered and made the file path incorrect. However, the team encountered a new authentication error while attempting to login.

Currently Tracking​

  • The team updated the open ticket with this new issue and the team is working with support to troubleshoot this error.

Next Steps​

Tracking​

Cases open: 0

Cases closed: 1

  • Case TS014232963

· One min read

Work in Progress​

  • Today the team began to walk through an installation of Process Designer in the client's environment.
  • The team ran into an error while trying to setup Process Designer in the Windows VM.
  • There were some differences in the java versions. We were using the JDK and the client had the JRE. But after setting the JAVA_HOME, it looks like Process Designer was able to locate Java. However, Process Designer gave an error that it was unable to load "main class".

Currently Tracking​

  • We opened a ticket and the team is working with support to troubleshoot this error.

Next Steps​

Tracking​

  • Cases open: 1
    • Case TS014232963

· One min read

Work in Progress​

  • Today the team discussed workflows and its association with Process Designer.
  • The team then proceeded to give a demo of workflows within FileNet.

Currently Tracking​

  • We will await feedback, or any follow up questions.

Next Steps​

· One min read

Work in Progress​

  • Today the team discussed how to setup the Process Designer component within FileNet.
  • The team then walked through a demo of the setup and installation of Process Designer.

Currently Tracking​

  • The team is working on pushing solution documentation to GitHub.

Next Steps​

· One min read

Work in Progress​

  • Today the team discussed synchronous/asynchronous replication and advanced storage within FileNet.
  • The team also walked through a demo of the replication setup and features associated with FileNet.

Currently Tracking​

  • The team is taking the feedback and questions from this session and preparing to move forward with future use cases and demos.

Next Steps​

· One min read

Work in Progress​

  • Today the team walked through a demo of the GraphQL feature associated with FileNet.
  • The client's team had specific questions regarding document creation/retrieve query operations within GraphQL.
  • The team discussed the client's GraphQL use case and implementation.

Currently Tracking​

  • The team is taking the feedback and questions from this session and preparing to move forward with future use cases and demos.

Next Steps​

· One min read

Work in Progress​

  • The team walked through the setup of the Process Designer.
  • The meeting touched on administrative and user privileges for managing workflows.
  • The team went through the admin and navigator console and there was a discussion on some of the functionality.

Currently Tracking​

  • The team is taking the feedback and questions from this session and preparing to move forward with future use cases and demos.

Next Steps​

· One min read

Date​

Flight Log contain information relating to steps completed on 06/09/2023

Key Accomplishments​

  • We had a working session with the IBM Dev team to show them the issues we are experiencing.
  • We decided to go back to using NGINX and validated the secret and certificate were created successfully.

Challenges​

  • We were still experiencing the same issues, so we set up tracelogs for the Ingress and exported these logs for further review.

Action Items​

  • We are going to let the IBM Dev team review the logs from today to see if there is any lead on what the issue could be.

Tracking​

· One min read

Date​

Flight Log contain information relating to steps completed on 06/08/2023

Key Accomplishments​

  • Verified that we can in fact use AWS ALB to create the Ingress instead of NGINX. This can open doors to new possible solutions.

Challenges​

  • We followed the same procedure presented by the IBM Dev team that we tried in our last working session and then verified that the certificate was present in the keystore. We wanted to verify if adjusting the resource quotas could have messed up the process for the pod creations. This resulted in the same error.
  • We attempted to switch the Ingress over to ALB instead of NGINX. To do this we edited the Ingress annotations in the CR and made some edits directly through the Ingress. This also resulted in us not being able to access the ACCE URL.

Action Items​

  • We are going back to the IBM Dev team to see if we can solve this issue through AWS ALB or NGINX.

Tracking​

· 2 min read

Date​

Flight Log contain information relating to steps completed on 06/06/2023

Key Accomplishments​

  • Successfully edited the CR with our certificate secret.  The Ingress needs to have a certificate in its trust store, so we forced it to redo and recreate secrets to include the certificate. To do this we used the Ingress secret ‘filenet-poc-tls’ that we created before and added it to the CR at the line ‘sc_ingress_tls_secret_name’. We also added it to the trusted certificate list within the CR.
  • Deleted and recreated the ‘fncmdeploy-fncm-custom-ssl-secret’ and ‘fncmdeploy-ban-custom-ssl-secret’.
  • We edited the resource quota and upgraded it from ‘large’ to ‘x-large’.  Edited the Value.yaml through GitHub and sent in a PR with the change (could not change it from command line because we got authorization issues).
  • We set the replica count of the Navigator back to 2 and all pods were up and running.

Challenges​

  • We initially received an error when trying to visit the ACCE URL. This was fixed after we added the certificate secret to the CR and reapplied it.
  • We are still having issues logging in to ACCE and Navigator even after applying the certificate secret to the CR and redeploying pods.

Action Items​

  • We followed the steps laid out by IBM Dev team but are still running into the Ingress issue of having a blank page after logging into ACCE and not being able to login to the Navigator.  We exported Ansible logs and will bring it back to the IBM Dev team to see what the issue could be.

Tracking​

· One min read

Date​

Flight Log contain information relating to steps completed on 06/01/2023

Key Accomplishments​

  • Successfully edited CR with necessary attributes needed by CR to spin up the Navigator pods.
  • We were able to successfully deploy Navigator and confirmed it was initialized and bootstrapped with port forwarding.

Challenges​

  • Operator would not create Navigator pod after initially reapplying CR.
  • There were errors pertaining to spinning up all Navigator pods. Operator would create first pod but had resource issues in spinning up the second. After confirming the resources were set to their intended values, we scaled the Navigator replicas down to 1 so the Operator would only make one Navigator pod, and this fixed the issue.

Action Items​

  • IBM Dev team is still working on Ingress issue. Once this is fixed, we can move forward to the next phase.

Tracking​