The <AdHocParameters> section is used to provide registry definitions that override the existing ones. Unlike the <ParameterVariables> section, a whole registry object definition can be specified in this section. When the XAI server starts, it first reads the registry definitions from the database and then it reads the <AdhocParameters> section. If it finds an object definition in this section, it uses it to replace the one read from the database.
Attribute Name | Description |
---|---|
Object Name |
The object name may be one of the following objects: Option Receiver Sender |
Object Attributes | The attributes of the object. Each object type has it own set of attributes: |
'Option' object attributes | |
name | The option flag. Must be defined in the OPTION_FLG table |
value | The value for that option |
'Receiver' object attributes | |
name | The receiver ID |
Class | The JMS provider. May be 'MQ' |
TargetClient | The client type writing/reading to the JMS queue/topic. May be 'JMS' or 'MQ'. Only relevant for interfacing with MQSeries |
JMSProvider | The JMS provider. May be 'MQ' |
TargetClient | The client type writing/reading to the JMS queue/topic. May be 'JMS' or 'MQ'. Only relevant for interfacing with MQSeries |
Executer | The XAI Executer ID for this receiver |
'Sender' object attributes | |
Class | The JMS provider. May be 'MQ' |
JMSProvider | The JMS provider. May be 'MQ' |
TargetClient | The client type writing/reading to the JMS queue/topic. May be 'JMS' or 'MQ'. Only relevant for interfacing with MQSeries |
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.