Configuring security

Security credentials must be set up properly for the unstructured text correlation engine to connect to appropriate systems.

Security credentials to other systems

For property details, see Configuring credentials for unstructured text correlation.
Table 1. Systems and security credentials for the unstructured text correlation engine
System Description
MDM database The security credential is stored in these properties in the configgenerator.properties file:
  • MDMHubConfiguration_ Database_User
  • MDMHubConfiguration_ Database_Password

The user must have permission to read the MDM tables.

MDM operational server The security credential is stored in these properties in the configgenerator.properties file:
  • MDMHubConfiguration_ Instance_User
  • MDMHubConfiguration_ Instance_Password
The user must have permission to start the MDM interactions to read the entities and members of this source:
  • DataModelConfiguration_ StructuredDataSourceCode
The user must have permission to start the MDM interactions to read and write to the entities and members of these sources:
  • DataModelConfiguration_ UnstructuredDataSourceCode
  • DataModelConfiguration_ Document_SourceCode
Review store database The security credential is stored in these properties in the configgenerator.properties file:
  • ReviewStoreConfiguration_ Database_User
  • ReviewStoreConfiguration_ Database_Password

The user must have permission to read and write to the review store tables.

JMS repository The security credential is stored in these properties in the configgenerator.properties file:
  • UpdateHandlerConfiguration_JMS_User
  • UpdateHandlerConfiguration_JMS_Password

The user must have permission to read and write to the JMS queue for the unstructured text correlation component.

JNDI lookup for JMS administrative objects The security credential for looking up the JMS administrative objects from WebSphere® JNDI repository is stored in these properties in the TEXTCORREALTION_HOME/config/sas.client.props file:
  • com.ibm.CORBA.loginUserid
  • com.ibm.CORBA.loginPassword
The user must have permission to connect to the WebSphere Application Server and lookup the JMS administrative objects for unstructured text correlation. The information for connecting to the WebSphere Application Server is stored in this property in the configgenerator.properties file:
  • UpdateHandlerConfiguration_ProviderURL
To encrypt the com.ibm.CORBA.loginPassword property, run the following commands:
  • Windows:
    $NODE_HOME\bin\PropFilePasswordEncoder.bat filepath\sas.client.props com.ibm.CORBA.loginPassword
  • Linux:
    $NODE_HOME/bin/PropFilePasswordEncoder.sh file path/sas.client.props com.ibm.CORBA.loginPassword

File system security

The unstructured text correlation engine performs numerous tasks to manipulate the files. The installer has setup the engine with the file permissions to enable the unstructured text correlation component user to run the TEXTCORRELATION_HOME/bin/TextCorrelation.sh or TEXTCORRELATION_HOME\bin\TextCorrelation.bat files without extra setup.

When you add files into the TEXTCORRELATION_HOME/work/documents/toprocess folder or add control set files into the TEXTCORRELATION_HOME/tuningassistant/controlset folder, the component user must have read, move, and delete permissions for all files.



Last updated: November 6, 2015