A.21.4 Integrating Notebook with ECM

The notebook is integrated with ECM to enable Case Investigators to investigate cases in the ECM.

Enable Notebook Tab in ECM Case Designer

The pre-configured ECM patch enables the notebook tab for AMLSURV case types. An admin user can add the tab for other case types by using the Case Designer component in the ECM.

For more information, see Adding Optional Entities to the Case Type section in the OFS ECM Administration And Configuration Guide.

Note:

Add case type and notebook Id mappings in the FCC_CM_CTYPE_NB_MAPPING table.

User Role Precedence for Notebook

User role precedence in the FCC_CM_NB_ROLES table to decide which notebook to investigate when users have multiple roles where the mapped notebook ids are different.

To set the precedence among roles by Admin user, follow these steps:

1. Connect to ECM's Atomic Schema.
2. Edit records present in the FCC_CM_NB_ROLES table.
3. Enter the user role in the V_USERROLE column and the precedence in the N_PRECEDENCE column.

   Note:

   Lower value of precedence has higher precedence.

Mapping User Roles and Case Type with Notebook

This section can be used to configure specific roles and case types. An admin user can map the notebook against a role and case type.

Map additional case types, roles, and respective notebook id in the table. You can see examples as listed in following table

Table A-14 Example

V_CA SETY PE	V_USE RROLE	V_NOT EBOOK _ID	V_CREA TED_DA TE	V_CREA TED_BY	V_UP DATE D_BY	V_UP DATE D_DA TE	V_N B_T OOL BAR	V_A DD_ PAR A	V_PA RA_ ACTI ONS	V_PAR A_COD E
CASE_ TYPE_ 1	ROLE_1	noteboo k_id_1	02-02- 2024	02-02- 2024	-	-	N	N	Y	N
CASE_ TYPE_ 1	ROLE_2	noteboo k_id_2	02-02- 2024	02-02- 2024	-	-	N	N	Y	N
CASE_ TYPE_ 2	ROLE_1	noteboo k_id_1	02-02- 2024	02-02- 2024	-	-	N	N	Y	N
CASE_ TYPE_ 2	ROLE_2	noteboo k_id_3	02-02- 2024	02-02- 2024	-	-	N	N	Y	N
CASE_ TYPE_ 2	ROLE_3	noteboo k_id_5	02-02- 2024	02-02- 2024	-	-	N	N	Y	N

Note:

Roll out an update by replacing the existing notebook ids with updated notebook ids.

Authenticate User to Access Notebook Tab in ECM

Note:

The user needs a self-signed certificate to authenticate the user for accessing notebook in ECM.

If the user is not using the self-signed certificate, follow these steps:

1. Copy the following files from <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/ mmg-home/mmg-studio/conf to the server where ECM is installed.
   • studio_server.p12
   • studio_server.jks

   Note:

   Make sure that the "studio_server.p12" and "studio_server.jks" certificates are compatible with Java 8. This is applicable only if the Compliance Studio server is in JDK 11 and the ECM application server is in Java 8. If there is a difference in Java versions, then both the files "studio_server.p12" and "studio_server.jks" need to be recreated in Compliance Studio server and replaced in all necessary locations. For more information about these certificates, see Generate Self-signed Certificate section in the OFS Compliance Studio Installation Guide.
2. Run the following command to create certificate files:

   openssl pkcs12 -in studio_server.p12 -nokeys -out server_cert.pem
   openssl pkcs12 -in studio_server.p12 -nodes -nocerts -out server_key.pem
   keytool -certreq -keystore studio_server.jks -alias studio_server -
   keyalg RSA -file client.csr
   openssl x509 -req -CA server_cert.pem -CAkey server_key.pem -in
   client.csr -out client_certificate.pem -days 365 –Cacreateserial

3. Modify the path and run the following command

   keytool -import -file "/<ECM Installation Path>/client_certificate.pem"
   -alias studio_server -keystore "<JDK Installed Directory>/lib/security/
   cacerts" -storepass "changeit"

   For example,

   keytool -import -file "Testserver/client_certificate.pem" -alias
   studio_server -keystore "jdk-11.0.10/lib/security/cacerts" -storepass
   "changeit"