Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
Español
  • Multidomain MDM 10.4 HotFix 2
  • Todos los productos

Índice

Search

  1. Prólogo
  2. Resumen de la instalación
  3. Tareas previas a la instalación
  4. Instalación del almacén del concentrador
  5. Instalación del servidor del concentrador
  6. Tareas posteriores a la instalación del Servidor del concentrador
  7. Instalación del Servidor de procesos
  8. Tareas posteriores a la instalación del Servidor de procesos
  9. Tareas de ActiveVOS posteriores a la instalación para el servidor de aplicaciones
  10. Tareas de ActiveVOS posteriores a la instalación para el adaptador de entidades de negocio
  11. Personalizar ActiveVOS
  12. Instalación del kit de recurso
  13. Solución de problemas de MDM Hub
  14. Desinstalación

Guía de instalación de Microsoft SQL Server with Oracle WebLogic

Guía de instalación de Microsoft SQL Server with Oracle WebLogic

Anterior Siguiente

Troubleshooting the Installation Process

Troubleshooting the Installation Process

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

Cannot launch the Hub Console

After installation, the Hub Console fails to launch and generates the following error in the log file: 
SIP-09131: General Decryption failure and [ERROR] com.delos.util.StringUtil: Unable to decrypt
Encrypt and update the MDM Hub Master Database password or Operational Reference Store password.
  1. To encrypt a database schema password, run the following command from a command prompt: 
    java -classpath siperian-api.jar;siperian-common.jar;siperian-server.jar com.delos.util.PublicKeyBasedEncryptionHelper <plain text password> <Hub Server
installation directory>
    The results are echoed to the terminal window.
  2. To update your Master Database password or Operational Reference Store password, connect as the
    cmx_system
     user and run the following statement: 
    UPDATE [dbo].[C_REPOS_DATABASE] SET PASSWORD = '<new_password>' WHERE USER_NAME =
<user_name>
  3. Run the
    postInstallSetup
     script.

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 <
directorio de instalación de MDM Hub
>/server/bin
./sip_ant.sh hash_users_passwords
./sip_ant.sh add_application_users
On Windows. 
cd <
directorio de instalación de MDM Hub
>\server\bin
sip_ant.bat hash_users_passwords
sip_ant.bat add_application_users

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
Servidor de procesos
, 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
Almacén de referencias operativas
 (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
Servidor de procesos
, 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
Servidor de procesos
.

Cannot add the application users using the sip_ant script

The following applications are affected: Business Process Manager (formerly known as ActiveVOS), Data Director, MDM Hub Console and Provisioning Tool.
To add the application users, run the
sip_ant
command, using the
add_app_users
 parameter.
You can fetch the connect URL from the following location:
hub/server/bin/build.properties (masterdatabase.jdbc.url)
)
Run the following command:
  • On Windows. 
    sip_ant.bat add_app_users -Ddatabase.password=<cmx system password> -Dmaster.​connecturl="jdbc:oracle:thin:@<Database Host name>:<DB Port>:<SID>" -Dmaster.username=cmx_system​
  • On Unix. 
    ./sip_ant.sh add_app_users -Ddatabase.password=<cmx system password> -Dmaster.​connecturl="jdbc:oracle:thin:@//<Database Host name>:<DB Port>:<SID>" -Dmaster.username=cmx_system​​
Run the following command on the SQL Server: 
./sip_ant​.sh add_app_users -Ddatabase.password=<cmx system password> -Dmaster.connecturl="jdbc:sqlserver://<Database Host Name>:<DB Port>;DatabaseName=cmx_system" -Dmaster.username=cmx_system
​

The Certificates folder is not created

The Certificates folder is not created as expected, after you back up the existing Certificates folder from
\infamdm\hub\server\resources\
, and run the
sip_ant.sh hash_users_passwords
 script. ​​This issue occurs when the
sip_ant.sh hash_users_passwords
 script updates the C_REPOS_USER table in
cmx_system
.
To resolve this issue, restart the application server. As a result, the Certificates folder is created in the expected location:
\infamdm\hub\server\resources\
.
The folder will contain only the
MDM_KEYSTORE_FILE_JKS
 keystore.
To generate other certificates, run the following command: 
./sip_ant.sh add_app_users