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
English
  • Informatica Data Quality 10.5.3
  • All Products

Table of Contents

Search

  1. Preface
  2. Understanding Domains
  3. Managing Your Account
  4. Using Informatica Administrator
  5. Using the Domain View
  6. Domain Management
  7. Nodes
  8. High Availability
  9. Connections
  10. Connection Properties
  11. Schedules
  12. Domain Object Export and Import
  13. License Management
  14. Monitoring
  15. Log Management
  16. Domain Reports
  17. Node Diagnostics
  18. Understanding Globalization
  19. Managing Distribution Packages
  20. Appendix A: Code Pages
  21. Appendix B: Custom Roles
  22. Appendix C: Informatica Platform Connectivity
  23. Appendix D: Configure the Web Browser

Administrator Guide

Administrator Guide

Back Next

Configuring Node Properties

Configuring Node Properties

You configure node properties on the Properties view for the node. You can configure properties such as the node roles, error severity level, and minimum and maximum port numbers.
  1. In the Administrator tool, click the
    Manage
     tab >
    Services and Nodes
     view.
  2. In the Domain Navigator, select a node.
  3. Click the
    Properties
     view.
    The Properties view displays the node properties in separate sections.
  4. In the
    Properties
     view, click
    Edit
     for the section that contains the property you want to set.
  5. Edit the following properties:
    Node Property
    Description
    Name
    Name of the node. The name is not case sensitive and must be unique within the domain. It cannot exceed 128 characters or begin with @. It also cannot contain spaces or the following special characters:
    ` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [
    Description
    Description of the node. The description cannot exceed 765 characters.
    Host Name
    Host name of the machine represented by the node.
    Port
    Port number used by the node.
    Gateway Node
    Indicates whether the node can serve as a gateway. If this property is disabled, then the node is a worker node.
    Service Role
    Indicates whether the node has the service role. If enabled, application services can run on the node. If disabled, application services cannot run on the node. Disable the property only if the node is assigned to a Data Integration Service grid and you want to dedicate the node to running mappings.
    Default is enabled.
    Compute Role
    Indicates whether the node has the compute role. If enabled, the node can perform computations. If disabled, the node cannot perform computations.
    A node requires the compute role when the Data Integration Service runs jobs on the node. If the Data Integration Service does not run jobs on the node, you can disable the compute role. However, enabling or disabling the compute role does not have a performance impact.
    Default is enabled.
    Backup Directory
    Directory to store repository backup files. The directory must be accessible by the node.
    Error Severity Level
    Level of error logging for the node. These messages are written to the Log Manager application service and Service Manager log files. Set one of the following message levels:
    • ERROR
      . Writes ERROR code messages to the log.
    • WARNING
      . Writes WARNING and ERROR code messages to the log.
    • INFO
      . Writes INFO, WARNING, and ERROR code messages to the log.
    • TRACING
      . Writes TRACE, INFO, WARNING, and ERROR code messages to the log.
    • DEBUG
      . Writes DEBUG, TRACE, INFO, WARNING, and ERROR code messages to the log.
    Default is
    WARNING
    .
    Minimum Port Number
    Minimum port number used by service processes on the node. To apply changes, restart Informatica services. The default value is the value entered when the node was defined.
    Maximum Port Number
    Maximum port number used by service processes on the node. To apply changes, restart Informatica services. The default value is the value entered when the node was defined.
    CPU Profile Benchmark
    Ranks the node's CPU performance against a baseline system. Used by the Load Balancer component of the PowerCenter Integration Service.
    For example, if the CPU is running 1.5 times as fast as the baseline machine, the value of this property is 1.5. You can calculate the benchmark by clicking
    Actions
    Recalculate CPU Profile Benchmark
    . The calculation takes approximately five minutes and uses 100% of one CPU on the machine. Or, you can update the value manually.
    Default is 1.0. Minimum is 0.001. Maximum is 1,000,000.
    Used in adaptive dispatch mode. Ignored in round-robin and metric-based dispatch modes.
    Maximum Processes
    Maximum number of running session tasks or command tasks allowed for each PowerCenter Integration Service process running on the node. Used by the Load Balancer component of the PowerCenter Integration Service.
    For example, if you set the value to 5, up to 5 command tasks and 5 session tasks can run at the same time.
    Set this threshold to a high number, such as 200, to cause the Load Balancer to ignore it. To prevent the Load Balancer from dispatching tasks to this node, set this threshold to 0.
    Default is 10. Minimum is 0. Maximum is 1,000,000,000.
    Used in all dispatch modes.
    Maximum CPU Run Queue Length
    Maximum number of runnable threads waiting for CPU resources on the node. Used by the Load Balancer component of the PowerCenter Integration Service.
    Set this threshold to a low number to preserve computing resources for other applications. Set this threshold to a high value, such as 200, to cause the Load Balancer to ignore it.
    Default is 10. Minimum is 0. Maximum is 1,000,000,000.
    Used in metric-based and adaptive dispatch modes. Ignored in round-robin dispatch mode.
    Maximum Memory %
    Maximum percentage of virtual memory allocated on the node relative to the total physical memory size. Used by the Load Balancer component of the PowerCenter Integration Service.
    Set this threshold to a value greater than 100% to allow the allocation of virtual memory to exceed the physical memory size when dispatching tasks. Set this threshold to a high value, such as 1,000, if you want the Load Balancer to ignore it.
    Default is 150. Minimum is 0. Maximum is 1,000,000,000.
    Used in metric-based and adaptive dispatch modes. Ignored in round-robin dispatch mode.
    Log Collection Directory
    The directory that stores the logs for the application service when you run the log aggregator. The directory must be accessible from all the nodes in the domain. If the log collection directory is not accessible by other nodes, the aggregated logs do not appear in the aggregated logs listgrid. The users who run node processes must have read-write permissions on the directory.
    Configure the log collection directory for the master gateway node in the domain.
    Core Dump Directory
    The directory that stores the core dump files for the domain processes when you run the log aggregator.
    Configure the core dump directory for all the nodes in the domain.
  6. Click
    OK
    .
0 COMMENTS
We’d like to hear from you!