Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Pre-Installation Tasks
  4. Hub Store Installation
  5. Hub Server Installation
  6. Hub Server Post-Installation Tasks
  7. Process Server Installation
  8. Process Server Post-Installation Tasks
  9. ActiveVOS Post-Installation Tasks for the Application Server
  10. ActiveVOS Post-Installation Tasks for the Business Entity Adapter
  11. Resource Kit Installation
  12. Troubleshooting the MDM Hub
  13. Uninstallation

Installation Guide for Microsoft SQL Server with Oracle WebLogic

Installation Guide for Microsoft SQL Server with Oracle WebLogic

Troubleshooting the Installation Process

Troubleshooting the Installation Process

If the installation fails, use the following information to troubleshoot the failure.

MDM Hub users cannot login

If you re-create the CMX_SYSTEM schema after installation of the Hub Server, the MDM Hub cannot recognize the hashed passwords. As a result, users cannot log in to the MDM Hub.
To resolve the issue, run the
postInstallSetup
script again manually. This script ensures that the passwords of the MDM Hub users are hashed again and users can log in.
Alternatively, if you do not want to run the
postInstallSetup
script again, run the following commands to migrate the user passwords to hashed passwords and create application users.
On UNIX.
cd <
MDM Hub installation directory
>/server/bin ./sip_ant.sh hash_users_passwords ./sip_ant.sh add_application_users
On Windows.
cd <
MDM Hub installation directory
>\server\bin sip_ant.bat hash_users_passwords sip_ant.bat add_application_users
In a WebSphere environment, the MDM Hub user must have access and write permissions for the following directory:
<
MDM Hub installation directory
>/server/bin/resources/certificates

WebLogic instance redirects to Data Director

If you install MDM Hub on a WebLogic port other than 7001, the instance is redirected to Data Director with the following error:
javax.faces.application.ViewExpiredException: viewId:/config/config_login.jsf - View /config/config_login.jsf could not be restored.
To resolve the issue, set to the host name and the IP address of the WebLogic host. Do not use localhost.

PostInstallSetUp script fails because the ActiveVOS server deployment times out

When you install the Hub Server, the post-installation setup process might fail after trying to deploy the ActiveVOS server.
To resolve the issue, increase the value of the
deploy.wait.time
property in the
build.properties
file in the following directory:
On UNIX.
<infamdm installation directory>/hub/server/bin
On Windows.
<infamdm installation directory>\hub\server\bin

The Hub Server cannot connect to the cmx_system schema

To verify that the Hub Server cannot connect to the cmx_system schema, review the application server log.
To resolve the issue, resolve the database connection issue. Use the application server console to test the connection to the database. If you cannot resolve the connection to the cmx_system schema, re-create the cmx_system schema.

Failed to verify the need to tokenize records

When you run the Match process, you might receive the following error:
SIP-16062: Failed to verify the need to tokenize records.
Verify the following environment variable settings:
  • The
    PATH
    environment variable must contain the following path:
    On UNIX.
    <
    infamdm_install_directory
    >/hub/cleanse/lib
    On Windows.
    <
    infamdm_install_directory
    >\hub\cleanse\lib
  • The
    SSAPR
    environment variable must include the following path for all users:
    On UNIX.
    <
    infamdm_install_directory
    >/server_install_dir>/cleanse/resources
    On Windows.
    <
    infamdm_install_directory
    >\server_install_dir>\cleanse\resources

major.minor version errors when loading the Process Server

If you see multiple
major.minor
console errors when you try to load the
Process Server
, check that the system has the correct Java version installed.

Informatica Address Verification
exception during certification

Informatica Address Verification
generates an exception during certification. Ensure that the stack size for the JVM is sufficient.
  1. Navigate to the WebLogic home directory.
  2. Open the following file in a text editor.
    On UNIX.
    setDomainEnv.sh
    On Windows.
    startWeblogic.cmd
  3. Use the following command to set the MEM_ARGS variable:
    On UNIX.
    set MEM_ARGS=${MEM_ARGS} -Xss2000k
    On Windows.
    set MEM_ARGS=%MEM_ARGS% -Xss2000k
  4. Save and close the file.

Operational Reference Store does not have a workflow engine configured

If you install the
MDM Hub
and then import an
Operational Reference Store
(ORS) from a previous version, you see a fatal error that indicates that the ORS does not have a workflow engine configured. This error occurs because the Siperian BPM workflow engine is not registered by default. Use the Workflow Manager to register the Siperian BPM workflow engine with the name that the ORS expects to find.

After you deploy the Process Server .ear files, an error occurs

On a Linux environment with WebSphere 8.5.5.9, after you deploy the
Process Server
, the following error occurs:
Too many open files. Unable to start cleanse ear.
Increase the value of the
ulimit
parameter in Linux, and deploy the
Process Server
.

0 COMMENTS

We’d like to hear from you!