Skip to main content Skip to complementary content

Configuring the Implicit Context Load feature

You can configure the Implicit Context Load feature either in Project Settings so that it can be used across Jobs within the project, or in the Job view for a particular Job.

The following example shows how to configure the Implicit Context Load feature in the Job view for this particular Job. If you want to configure the feature to be reused across different Jobs, select File > Edit Project properties from the menu bar to open the Project Settings dialog box, go to Job Settings > Implicit context load, select the Implicit tContextLoad check box, and set the parameters following steps 2 through 6 below. Then in the Job view, select the Use Project Settings check box to apply the settings to the Job.

Procedure

  1. From the Job view, select the Extra vertical tab, and select the Implicit tContextLoad check box to enable context loading without using the tContextLoad component explicitly in the Job.
  2. Select the source to load context parameters from. A context source can be a two-column flat file or a two-column database table. In this use case the database connection details are stored in database tables, so select the From Database option.
  3. Define the database connection details just like defining the basic settings of a database input component.

    In this example, all the connection parameters are used just for this particular Job, so select Built-In from the Property Type list and fill in the connection details manually.

  4. Fill the Table Name field with the context variable named db_connection defined in the Contexts view of the Job so that we will be able to choose the database table to load context parameters from dynamically at Job execution.
  5. As we will fetch all the connection details from the database tables unconditionally, leave the Query Condition field blank.
  6. Select the Print operations check box to list the context parameters loaded at Job execution.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here