Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Appendix A: Sizing and Platform Requirements
  9. Appendix B: Application Components
  10. Appendix C: IDD Security Configuration
  11. Appendix D: Data Security
  12. Appendix E: Example Role-Based Security Configuration
  13. Appendix F: Data Masking
  14. Appendix G: Siperian BPM Workflow Engine
  15. Appendix H: Locale Codes
  16. Appendix I: Troubleshooting
  17. Appendix J: Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Informatica Data Director Stops Responding When You Switch Entities

Informatica Data Director Stops Responding When You Switch Entities

Informatica Data Director stops responding when you switch entities for hierarchy manager relationships for source systems that are not enabled for state management override.
The behavior occurs for JBoss environments running on Java 1.7. To resolve this issue, you must configure the
standalone-full.xml
file.
  1. Open the
    standalone-full.xml
    file for editing. The file is in the following directory:
    • On UNIX.
      <
      JBoss installation directory
      >/jboss-eap-6.1/standalone/configuration
    • On Windows.
      <
      JBoss installation directory
      >\jboss-eap-6.1\standalone\configuration
  2. Add the following XML code to the
    standalone-full.xml
    file to configure asynchronous handling for the logger:
    <async-handler name="ASYNC"> <level name="INFO"/> <queue-length value="1024"/> <overflow-action value="BLOCK"/> <subhandlers> <handler name="FILE"/> <handler name="CONSOLE"/> </subhandlers> </async-handler>
  3. Under <subsystem xmlns="urn:jboss:domain:logging:1.2"> in the
    standalone-full.xml
    file, add the following XML code to configure asynchronous handling for the root logger:
    <root-logger> <level name="INFO"/> <handlers> <handler name="ASYNC"/> </handlers> </root-logger>
  4. Restart the application server.

0 COMMENTS

We’d like to hear from you!