Integrating Surveillance Insight with the Financial Crimes Insight interface

You can integrate the Surveillance Workbench, Design Studio, and Complaints Workbench applications with the IBM Financial Crimes Insight Investigative UI.

Procedure

  1. Log in to the NFS server as the root user.
  2. Open the /fcicore/fci-cui-web/nginx.conf file in text editor.
  3. Uncomment the following section, and save the file:
    upstream fci-si {
    server sifs-base-liberty.default.svc.cluster.local:9443;
    }
    location /surveillance {
        proxy_pass https://fci-si;
        client_max_body_size 0;
     }
     location /SIFSServices {
        proxy_pass https://fci-si;
        proxy_read_timeout 10d;
        client_max_body_size 0;
     }
     location /ui.complaintsdashboard {
        proxy_pass https://fci-si;
        client_max_body_size 0;
     }
     location /complaintsservices {
        proxy_pass https://fci-si;
        proxy_read_timeout 10d;
        client_max_body_size 0;
     }
     location /surveillancetool {
        proxy_pass https://fci-si;
        client_max_body_size 0;
     }
     location /SIFSModelServices {
        proxy_pass https://fci-si;
        proxy_read_timeout 10d;
        client_max_body_size 0;
     }
     location /CommServices {
        proxy_pass https://fci-si;
        proxy_read_timeout 10d;
        client_max_body_size 0;
     }
     location /SIFSVoiceDataService {
        proxy_pass https://fci-si;
        proxy_read_timeout 10d;
        client_max_body_size 0;
     }
     location /SIFSVoiceIngestionService {
        proxy_pass https://fci-si;
        proxy_read_timeout 10d;
        client_max_body_size 0;
     }   
     location /righttoforget {
        proxy_pass https://fci-si;
        client_max_body_size 0;
     }
  4. Log in to the Kubernetes master node as the root user.
  5. Open the fcco-common-ui config map by using following command:
    kubectl edit cm fcco-common-ui
  6. Add the following values to the existing keys and save the file:
    APP_ROLE_ANALYST: case-manager,surveillance/search/index.html
    APP_ROLE_DATA_SCIENTIST: case-manager,surveillancetool/
    APP_ROLE_INVESTIGATOR: case-manager,surveillance/search/index.html
    APP_ROLE_SUPERVISOR: case-manager,surveillance/dashboard/index.html,ui.complaintsdashboard/
    Note: Do not add spaces between multiple values.
  7. On Kubernetes master node, run the following commands to delete the existing Common-UI pods. After the pods are deleted, Kubernetes will automatically start fresh pods with your changes.
    kubectl delete pod $(kubectl get pods -l release=fcco,app=common-ui-nodejs -o jsonpath='{.items[*].metadata.name}')
    kubectl delete pod $(kubectl get pods -l release=fcco,app=common-ui-nginx -o jsonpath='{.items[*].metadata.name}')
  8. After the pods are up and running, log in to the application at https://<web-server-host>:443/ and access the applications by clicking on the appropriate card.

    Design Studio is accessible only to users with a data_scientist role.

    Surveillance Dashboard is accessible only to users with a supervisor, investigator, or analyst role.

    Complaints Dashboard is accessible only to user with a supervisor role.