Setting properties from a command line

You can use the iisAdmin command to set or change certain InfoSphere Information Analyzer properties from a command line.

Location

The iisAdmin command is installed on the services tier in the following location:

IS_install_path/ASBServer/bin/iisAdmin.sh
IS_install_path\ASBServer\bin\iisAdmin.bat

Syntax

iisAdmin
	[-{verbose | v}]
	[-{results | res} value ]
	[-{log | l} value ]
	[-{logerror | error} value ]
	[-{loginfo | info} value ]
	[-{loglevel | level} value ]
	[-{log | l} value]
	[-{help | ?} ]
	[-{display | d}]
	[-{set | s}]
	[-{unset | u}]
	[-{key | k} value]*
	[-{value | val} value]*
	[-{load | loa} value]*

where -key or -k precedes the name of the property to set or change and value is the value of the property. For information about all of the parameters of this command, see iisAdmin command.

To view a list of the properties and values that are set for InfoSphere Information Analyzer, enter the following command in the IBM/InformationServer/ASBServer/bin directory on an engine tier computer:

iisAdmin.bat -display -key com.ibm.iis.ia.*

Note: The directory in which to enter the command is one of the following:

C:\IBM\InformationServer\ASBServer\bin (on Windows-based systems)
/opt/IBM/InformationServer/ASBServer/bin (on Unix-based systems)

InfoSphere Information Analyzer properties

The following table lists the properties that you can change that affect InfoSphere Information Analyzer processes.

Table 1. InfoSphere Information Analyzer properties
Property	Possible values or range	Default value	Description
com.ibm.iis.ia.engine.jobs.status.maxDelay	1 - 600	5	Interval in seconds at which the status of the generated InfoSphere DataStage jobs will be checked.
com.ibm.iis.ia.router.retries.max	3 - 10	10	The maximum number of times to retry an operation when a retryable operation occurs.
com.ibm.iis.ia.router.name	Any alphanumeric string. Spaces and special characters are not allowed.	IARouter	The name of the router that is set up for InfoSphere Information Analyzer jobs.
com.ibm.iis.ia.engine.handler.logging.debug	true false	false	If set to `true`, detailed logging is enabled for the engine handler. Log files are created in files namedasb.agent-`n`.out during job runs. These files are located in the following directory on the engine tier computer:IBM/InformationServer/ASBNode/logs .
com.ibm.iis.ia.server.job.logging.debug.process.detail	true false	false	Enables detailed logging during job run; useful for debugging. The detailed logging occurs in the application server log files, and any trace files that are created in the same directory.
com.ibm.iis.ia.server.jobs.keyanalysis.lockscolumns	true false	false	If set to `true`, columns are locked during cross-key analysis.
com.ibm.iis.ia.server.enableDB2Compression	true false	false	If set to `true`, if the database type that is used for the analysis database is DB2, the tables are compressed to save space. This value should be set to `true` if the analysis database is DB2.
com.ibm.iis.ia.server.jobs.doJoinsOnSource	true false	true	If set to `true`, data rule executions will attempt to perform joins in the source database instead of in the engine tier, to save time. For joins to occur in the source database, the following must be true: This property must be set to `true`. The left and right tables of the join must belong to the same physical source. The type of the physical source is one of DB2, Microsoft SQL Server, Oracle, Teradata, MySQL, Sybase, Netezza. The type of the keys on each side of the join must be the same data type (numerical or string). The key cannot be a virtual column. If a numeric key is paired with a string key, then the join will not be pushed to the source database. Note that for MySQL and Sybase, full outer joins will not be pushed to the source, because those databases do not support full outer joins.
com.ibm.iis.ia.server.jobs.parallel.defer.period	100 - 100000	60000	Wait period in milliseconds for a deferred job to resume again.
com.ibm.iis.ia.server.agent.timeout.period	86400 - 432000	86400	Agent connectivity timeout period (in seconds). The default sets the period to 24 hours (86400 seconds).
com.ibm.iis.ia.engine.instances.min	1 - `com.ibm.iis.ia.engine.instances.max`	1	The minimum number of handler instances to be active.
com.ibm.iis.ia.engine.instances.max	1 - 30	20	The maximum number of handler instances that can run in parallel. The value of this variable limits the number of jobs that can be concurrently submitted to the workload management queue. If an analysis job is submitted that requires the creation of more DataStage jobs than the value of this variable, the submission of some DataStage jobs to the workload management queue will be delayed until some of them have terminated.
com.ibm.iis.ia.server.jobs.columnsPerTable.max	100 - 500	500	Maximum number of columns that are allowed in column analysis for one job.

Example

Assuming that you want to use the DB2 table compression feature on the tables created in the analysis database and if your DB2 license allow you to use this feature, use the following command:

iisAdmin -set -key com.ibm.iis.ia.server.enableDB2Compression -value true