Optimizing job with MapReduce Connector or JDBC Connector

Overview:

From InfoSphere InformationServer 9.1.2 onwards when a job is optimized using InfoSphere Balanced Optimization by default we get JDBC Connector either at source or target after optimization. If  JAQL Connector is required as optimized job then user need to tweak gandalf.properties file. Based on the configuration settings a user has, optimized job is executed on JDBC Connector and MapReduce Connector environment.

Current Scenario

Let’s say we have job by name BDFSTest01 as given in Figure 1. 

 Figure 1: Sample job

When we optimize the job we get JDBC Connector after optimization as shown in Figure2

Figure 2: Optimized job

If a user environment is configured to JAQL and would like to see MapReduce/JAQL Connector instead of JDBC Connector then user need to tweak an entry in “gandalf.properfies”

Let’s see How?

InfoSphere Balanced Optimization is a client side tool. So open windows explorer on your client machine and if InfoSphere DataStage Client is installed with Administrator user then go to location
C:\Users\Administrator\AppData\Roaming\IBM\InformationServer\DataStage Client\<UniqueKey>\BalOp\etc

For example you will see location as given below
C:\Users\Administrator\AppData\Roaming\IBM\InformationServer\DataStage Client\41e35a53-3b15-4694-875c-8c446f7c0d84\BalOp\etc

Open “gandalf.properties” in any editor and you will see entries as shown below in Figures 3 and 4.

Figure 3: Location of “gandalf.properties”

  Figure 4: Default entries in “gandalf.properties”

Default entries Modify entry jaql.dialect=BIGSQL_JAQL to jaql.dialect=JAQL_JAQL. Then optimize the job again to get MapReduce/JAQL Connector as shown in Figure 5

Note: No restart of Designer required after modifying “gandalf.properties” 

Figure 5: Optimized job with MapReduce Connector 

Disclaimer: “The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions.”