Use case: Defining a variable accessible to multiple Jobs

This use case creates a variable that is accessible to Jobs. It also gives examples on how to access the variable.

Creating a routine and declaring a static variable

Procedure

In the Repository tree view, create a new routine MyRoutine.
Declare a static variable in the routine and set its value as null, for example:
```
private static String name = null;                      
```

Add the setter/getter methods for this variable and press Ctrl+S to save the changes.

public static synchronized void setValue(String message) {
                     name=message;
                     }
                     
                     public static synchronized String getValue() {
                     return name;
                     }

Note: The complete Java code for this routine is as below:

package routines;
                        /*
                        * user specification: the function's comment should contain keys as follows: 1. write about the function's comment.but
                        * it must be before the "{talendTypes}" key.
                        *
                        * 2. {talendTypes} 's value must be talend Type, it is required . its value should be one of: String, char | Character,
                        * long | Long, int | Integer, boolean | Boolean, byte | Byte, Date, double | Double, float | Float, Object, short |
                        * Short
                        *
                        * 3. {Category} define a category for the Function. it is required. its value is user-defined .
                        *
                        * 4. {param} 's format is: {param} <type>[(<default value or closed list values>)] <name>[ : <comment>]
                        *
                        * <type> 's value should be one of: string, int, list, double, object, boolean, long, char, date. <name>'s value is the
                        * Function's parameter name. the {param} is optional. so if you the Function without the parameters. the {param} don't
                        * added. you can have many parameters for the Function.
                        *
                        * 5. {example} gives a example for the Function. it is optional.
                        */
                        public class MyRoutine {
                        private static String name = null;
                        
                        /**
                        * helloExample: not return value, only print "hello" + message.
                        *
                        *
                        * {talendTypes} String
                        *
                        * {Category} User Defined
                        *
                        * {param} string("world") input: The string need to be printed.
                        *
                        * {example} helloExemple("world") # hello world !.
                        */
                        public static void helloExample(String message) {
                        if (message == null) {
                        message = "World"; //$NON-NLS-1$
                        }
                        System.out.println("Hello " + message + " !"); //$NON-NLS-1$ //$NON-NLS-2$
                        }
                        
                        public static synchronized void setValue(String message) {
                        name = message;
                        }
                        
                        public static synchronized String getValue() {
                        return name;
                        }
                        }

Setting up the child Jobs

The example below shows how to share a value between different Jobs via the routine defined earlier.

Procedure

Create a Job named childJob1, and add two components by typing their names on the design workspace or dropping them from the Palette to the design workspace:
- A tFixedFlowInput to generate an input data flow
- A tJavaRow to receive the data and in which the Job calls the setter method to give a new value to the variable
Double-click the tFixedFlowInput component to open its Basic settings view.
Click the [...] button next to Edit schema to open the [Schema] dialog box and define the schema of the input data. In this example, the schema has only one column name of the string type.
In the Mode area, select Use Single Table option, and define the corresponding value for the message column in the Values table. In this example, the value is "Talend".

Information noteNote: The tJava component is calling the getter method and assigning the return value to a string variable, then printing the variable value in the console.
Double-click the tJavaRow component to open its Basic settings view.
In the Code area, enter the following code to add the setter method.
```
MyRoutine.setValue(input_row.name);
```
Create a Job called childJob2 and then create a tJava component in this Job.
Double-click the tJava component to open its Basic settings view.
In the Code area, enter the following code to add the getter method.
```
String name=MyRoutine.getValue();
                     System.out.println(name);
```

Setting up the parent Job

Procedure

Create a Job named parentJob and add two tRunJob components.
Connect the second tRunJob component to a first tRunJob component with a OnSubjobOk link.
Double-click on both tRunJob component to open its Basic settings view.
Fill the Job field of tRunJob1 and tRunJob2 respectively with childJob1 and childJob2 to call the two child Jobs created.

This approach of defining a variable in routine and sharing it across different Jobs does not work with the Use an independent process to run subjob feature on the tRunJobcomponent.

Executing the Jobs to call the routine

Procedure

Execute the parentJob. You can see the following results in the console:

Starting job parentJob at 19:52 21/06/2013.
                     [statistics] connecting to socket on port 3397
                     [statistics] connected
                     Talend
                     [statistics] disconnected
                     Job parentJob ended at 19:52 21/06/2013. [exit code=0]

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