Informatica resources are the database connections, files, directories, node names, and operating system types required by a task. You can configure the PowerCenter Integration Service to check resources. When you do this, the Load Balancer matches the resources available to nodes in the grid with the resources required by the workflow. It dispatches tasks in the workflow to nodes where the required resources are available. If the PowerCenter Integration Service is not configured to run on a grid, the Load Balancer ignores resource requirements.
For example, if a session uses a parameter file, it must run on a node that has access to the file. You create a resource for the parameter file and make it available to one or more nodes. When you configure the session, you assign the parameter file resource as a required resource. The Load Balancer dispatches the Session task to a node that has the parameter file resource. If no node has the parameter file resource available, the session fails.
Resources for a node can be predefined or user-defined. Informatica creates predefined resources during installation. Predefined resources include the connections available on a node, node name, and operating system type. When you create a node, all connection resources are available by default. Disable the connection resources that are not available on the node. For example, if the node does not have Oracle client libraries, disable the Oracle Application connections. If the Load Balancer dispatches a task to a node where the required resources are not available, the task fails. You cannot disable or remove node name or operating system type resources.
User-defined resources include file/directory and custom resources. Use file/directory resources for parameter files or file server directories. Use custom resources for any other resources available to the node, such as database client version.
The following table lists the types of resources you use in Informatica:
Any resource installed with PowerCenter, such as a plug-in or a connection object. A connection object may be a relational, application, FTP, external loader, or queue connection.
When you create a node, all connection resources are available by default. Disable the connection resources that are not available to the node.
Any Session task that reads from or writes to a relational database requires one or more connection resources. The Workflow Manager assigns connection resources to the session by default.
A resource for the name of the node.
A Session, Command, or predefined Event-Wait task requires a node name resource if it must run on a specific node.
A resource for the type of operating system on the node.
A Session or Command task requires an operating system type resource if it must run a specific operating system.
Any resource for all other resources available to the node, such as a specific database client version.
For example, a Session task requires a custom resource if it accesses a Custom transformation shared library or if it requires a specific database client version.
Any resource for files or directories, such as a parameter file or a file server directory.
For example, a Session task requires a file resource if it accesses a session parameter file.
You configure resources required by Session, Command, and predefined Event-Wait tasks in the task properties.
You define resources available to a node on the Resources tab of the node in the Administrator tool.
When you define a resource for a node, you must verify that the resource is available to the node. If the resource is not available and the PowerCenter Integration Service runs a task that requires the resource, the task fails.
You can view the resources available to all nodes in a domain on the Resources view of the domain. The Administrator tool displays a column for each node. It displays a checkmark when a resource is available for a node