For queues, iterators, aggregators, invokers, or transformers, you must associate the step with a message component instance. An instance allows you use a message component in a process step. For information about the component types, see Process Steps and Associated Components.

For SQL step, you must associate it with an SQL session.

Therefore, you must create these component instances and SQL sessions and then associate them to the steps.

Use SQL sessions options to set up pipelines to applications, middleware, or SQL databases. Sessions are an efficient way of opening connections, and leaving them open while performing different operations.

For example, you can issue a drop table statement to one Oracle table, then run a transformation to create or update a different table, without opening and closing the connection to Oracle twice. The session keeps the connection live for both steps.

Sessions are reused. When a step opens a session, that session remains open throughout the process. This means that subsequent steps in the process can see changes to an object in the database. Transactions are associated with sessions, and this enables steps to collaborate within the process.

Go to the Configuration tab > SQL Session section. For more information, see Configuring SQL Session section in Configuring Processes.