ibm-client-engineering / solution-filenet-aws Goto Github PK

Solution to deploy IBM FileNet Content Manager on AWS EKS

Home Page: https://ibm-client-engineering.github.io/solution-filenet-aws/

License: Apache License 2.0

JavaScript 1.20% TypeScript 0.82% CSS 97.99%

aws-eks business-automation filenet-content-manager

solution-filenet-aws's Introduction

sidebar_position	slug	title	full_website
1	/	Flight Path	https://ibm-client-engineering.github.io/solution-filenet-aws/

Bottom Line Up Front

This is a Solution Blueprint

This "Flight Path" is a living document that showcases an adoption journey and blueprint for a successful Proof of Technology implementation showcasing the capabilities of IBM FileNet Content Manager on Amazon Elastic Kubernetes Service (EKS). This repository and its contents is the result of a real customer engagement.

All of this journey, along with all code, architecture and assets is published and maintained in this repository. Click above to go to the GitHub repo.

Value Engineering Method

graph LR;
    A(Innovate) --> B(Prepare);
    B --> C(Create);
    C --> D(Transition);

The Value Engineering Method is a human and design-led approach to solve complex business problems with transformative technology. This approach uses a proven co-creation methodology that aligns our experts, utilize leadership based on thousands of projects, with key client stakeholders to quickly identify business or technology challenges and build Proof of Experiences (PoXs) that solve and ‘de-risk’ those problems using IBM technology.

Working In The Open

The Flight Path approach embodies IBM Client Engineering's dedication to transparency and collaboration, which is evident through the creation of this accessible repository that showcases real-life customer experiences. By sharing this knowledge, IBM aims to develop user-friendly and scalable landing zones for customers that encourage the adoption of IBM Technology while prioritizing innovation and user experience. This repository represents IBM Client Engineering's commitment to working in the open, where stakeholders and interested parties can participate, provide feedback and benefit from collective knowledge.

Feel free to peruse other documented journeys On our GitHub Open Solutions Library

:::info

IBM Client Engineering is a no-cost investment in IBM's customers to co-create and innovate leveraging IBM technology and methodologies. We partner with you to help you solve your most complex business challenges. Engage us today!

:::

solution-filenet-aws's People

Contributors

Stargazers

Watchers

Forkers

awang129 vivin12 lukasng

solution-filenet-aws's Issues

Ingress doesn’t come up correctly for the /acce url

Description:
The ingress for the /acce URL in FileNet 5.5.10 running on AWS EKS is not working correctly. When accessing the /acce URL and logging in, a blank screen is displayed. However, if the fncmdeploy-cpe-svc is port-forwarded, login is successful.

Steps to Reproduce:

Access the /acce URL.
Log in and observe the blank screen.

Expected Behavior:
Logging in through the /acce URL should display the expected content.

Ingress Description:

Name:             fncmdeploy-fncm-ingress
Labels:           app=fncmdeploy-fncm-ingress
Namespace:        filenet
Address:          k8s-ingressn-ingressn-2a2a87bca6-cbe86a7bf0ba4eaa.elb.us-east-1.amazonaws.com
Ingress Class:    <none>
Default backend:  <default>
TLS:
  fncmdeploy-fncm-ext-tls-secret terminates filenet.filenet-east.frwd-labs.link
Rules:
  Host                                 Path  Backends
  ----                                 ----  --------
  filenet.filenet-east.frwd-labs.link  
                                       /acce                       fncmdeploy-cpe-svc:9443 (192.168.30.142:9443,192.168.80.197:9443)
                                       /ibm/wsatservice            fncmdeploy-cpe-svc:9443 (192.168.30.142:9443,192.168.80.197:9443)
                                       /P8CE                       fncmdeploy-cpe-stateless-svc:9443 (192.168.30.142:9443,192.168.80.197:9443)
                                       /FileNet                    fncmdeploy-cpe-stateless-svc:9443 (192.168.30.142:9443,192.168.80.197:9443)
                                       /wsi                        fncmdeploy-cpe-stateless-svc:9443 (192.168.30.142:9443,192.168.80.197:9443)
                                       /peengine                   fncmdeploy-cpe-stateless-svc:9443 (192.168.30.142:9443,192.168.80.197:9443)
                                       /pewsi                      fncmdeploy-cpe-stateless-svc:9443 (192.168.30.142:9443,192.168.80.197:9443)
                                       /ibmccepo                   fncmdeploy-cpe-stateless-svc:9443 (192.168.30.142:9443,192.168.80.197:9443)
                                       /restReg                    fncmdeploy-cpe-stateless-svc:9443 (192.168.30.142:9443,192.168.80.197:9443)
                                       /clientDownload             fncmdeploy-cpe-stateless-svc:9443 (192.168.30.142:9443,192.168.80.197:9443)
                                       /content-services-graphql   fncmdeploy-graphql-svc:9443 (192.168.34.67:9443,192.168.95.110:9443)
                                       /openfncmis_wlp             fncmdeploy-cmis-svc:9443 (192.168.26.66:9443,192.168.33.49:9443)
                                       /taskManagerWeb             fncmdeploy-tm-svc:9443 (192.168.3.80:9443,192.168.51.120:9443)
                                       /contentapi                 fncmdeploy-es-svc:9443 (192.168.1.166:9443,192.168.86.4:9443)
                                       /sync                       fncmdeploy-navigator-svc:9443 (192.168.40.9:9443,192.168.65.66:9443)
                                       /navigator                  fncmdeploy-navigator-svc:9443 (192.168.40.9:9443,192.168.65.66:9443)
Annotations:                           kubernetes.io/ingress.class: nginx
                                       nginx.ingress.kubernetes.io/affinity: cookie
                                       nginx.ingress.kubernetes.io/backend-protocol: HTTPS
                                       nginx.ingress.kubernetes.io/force-ssl-redirect: true
                                       nginx.ingress.kubernetes.io/secure-backends: true
                                       nginx.ingress.kubernetes.io/session-cookie-hash: sha1
                                       nginx.ingress.kubernetes.io/session-cookie-name: route
                                       nginx.ingress.kubernetes.io/use-regex: true
Events:
  Type    Reason  Age                From                      Message
  ----    ------  ----               ----                      -------
  Normal  Sync    18m (x6 over 46m)  nginx-ingress-controller  Scheduled for sync

Bug: ibm-fncm-secret is incorrect

Investigating why CPE initialization fails, I noticed that in
fncm-secret creation phase the username is incorrect

kubectl create secret generic ibm-fncm-secret \
--from-literal=gcdDBUsername="ceuser" --from-literal=gcdDBPassword="p@ssw0rd" \
--from-literal=osDBUsername="ceuser" --from-literal=osDBPassword="p@ssw0rd" \
--from-literal=appLoginUsername="filenet_admin" --from-literal=appLoginPassword="p@ssw0rd" \
--from-literal=keystorePassword="p@ssw0rd" \
--from-literal=ltpaPassword="p@ssw0rd"

--from-literal=appLoginUsername="filenet_admin" needs to be `--from-literal=appLoginUsername="cpadmin" per the LDAP being set up here HERE

Official https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/20.0.x?topic=pifcm-creating-secrets-protect-sensitive-filenet-content-manager-configuration-data#taskd48794e30 clearly states the user is the LDAP user

ibm-client-engineering / solution-filenet-aws Goto Github PK

solution-filenet-aws's Introduction

Bottom Line Up Front

This is a Solution Blueprint

Value Engineering Method

Working In The Open

solution-filenet-aws's People

Contributors

Stargazers

Watchers

Forkers

solution-filenet-aws's Issues

Ingress doesn’t come up correctly for the /acce url

Bug: ibm-fncm-secret is incorrect

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent