|
|
|
|
NullifyXMLSourceNonExistentTagValue=
|
In Magic xpi, when a tag does not exist in an XML Source, the value that is passed to the Destination is the default value of the data type. For example, a non-existent numeric type returns 0.
This flag determines whether this value will remain as the default for the data type, or will instead be null. There are two possible options that you can set for this flag:
N (default) – The passed value remains as the default for the data type.
Y – The passed value is null.
|
|
NullifyJSONSourceNonExistentTagValue=
|
In Magic xpi, when a tag does not exist in a JSON Source, the value that is passed to the Destination is the default value of the data type. For example, a non-existent numeric type returns 0.
This flag determines whether this value will remain as the default for the data type, or will instead be null. There are two possible options that you can set for this flag:
N (default) – The passed value remains as the default for the data type.
Y – The passed value is null.
Since version: 4.5
|
|
JMSIncludeMessageInArgumentsXML
|
The JMS component trigger's argument XML contains both the message properties and the message itself encoded in Base 64. When messages are very large, the argument XML is too big to allow the Data Mapper to extract the actual message.
When this flag is set to N, the argument XML only includes the message properties, and not the message itself. To get both the message and the properties, you need to use the Data Mapper to map the message content and the argument XML.
The default value for this flag (and if this flag does not exist) is Y.
|
|
UseDBdateFormat
|
This flag determines the format of the Oracle DB string that is returned from the database SELECT statement.
When this flag is set to Y, the Oracle DB string format will be exactly the same as the format that Oracle returns.
The default value for this flag (and if this flag does not exist) is N.
|
|
DCRM2013OnPremise
|
This flag determines whether a project can connect to a Dynamics CRM on-premise machine. This flag is only relevant for the on-premise version of the Dynamics CRM connector.
There are two possible options that you can set for this flag:
N – A project cannot connect to a Dynamics CRM on-premise machine.
Y (default) – A project can connect to a Dynamics CRM on-premise machine.
Since version: 4.1
|
|
DCRMOnlineSDK
|
This flag is used by the Dynamics CRM connector to determine its runtime implementation. By default, it does not appear in the Magic.ini file and you need to add it if required.
There are two possible options that you can set for this flag:
N – The DCRM 2011 Soap API will be used at runtime.
Y (default) – The DCRM 2016 SDK will be used at runtime.
|
|
When the flag is set to Y, the runtime implementation is available only on Windows OS servers.
|
Since version: 4.6
|
|
SVCUtil=
|
This flag is used by the Dynamics AX 2012 connector and the WCF Client connector. This flag points to the Svcutil.exe file, which is part of the SDK and used for the generation of the C# client code and the client.config file.
For example: SVCUtil = C:\Program Files (x86)\Microsoft SDKs\Windows\<v7.xx>\Bin\NETFX 4.0 Tools\x64\SvcUtil.exe
For use with: 4.1 and above
|
|
SvcConfigEditor=
|
The full path to the Service Configuration Editor. When you click the WCF Client resource's Service Configuration button, this property is used to invoke the SvcConfigEditor.exe file. If this property is not available, Magic xpi will try and locate it using the path defined in the SVCUtil flag.
Since version: 4.5
|
|
DotNetCompiler=
|
This flag is used by the Dynamics AX 2012 connector and the WCF Client connector. This flag points to the default C# compiler, which is part of the .NET Framework installed on the computer and compiles the generated code created by the Svcutil.exe file.
For example: DotNetCompiler = C:\Windows\Microsoft.NET\Framework\<.NET 4.0.xxx or .NET 3.5 folder name>\csc.exe
For use with: 4.1 and above
|
|
ActivityBlobFileLocation=
|
This flag is used to set the full path where you want to write the SaveMessage BLOB. It is recommended to use a shared drive or logical names.
If the flag is not configured, then the temporary Blob files for all the projects will be created at a temporary location under the Apache Tomcat installation: <Magic xpi installation>\Runtime\RTView\base\webapps\magicmonitor\TempDownloadBlob. Since this location is common to all the projects, these temporary files will not be deleted as a part of the Activity Log delete process.
This flag is available by default in the ifs.ini file. For migrated projects, this flag is not available by default.
See also: Behavior changes for Magic xpi 4.5
Since version: 4.5
|
|
For Oracle Database Blob up to 2k is supported by default. To get support for blob field with more than 2k bytes, define the following path in the ifs.ini file of the project which will then create the file for the data at the specified location and run successfully through monitor as well.
[MAGIC_IBOLT]activityBlobFileLocation=c:\\temp\\
|
|
|
ActivityBlobFileFallbackToDB=
|
When this flag is set to Y, if the write to file in the ActivityBlobFileLocation flag failed, Magic xpi will try to write directly to the database's ifs_actlog table.
When this flag is set to N (default), the data is lost.
This flag is available by default in the ifs.ini file. For migrated projects, this flag is not available by default.
See also: Behavior changes for Magic xpi 4.5
Since version: 4.5
|
|
DCRMAD
|
This flag is used by the Dynamics CRM connector.
When you set the Dynamics CRM resource's Secured Connection property to Yes and the Deployment Type to On Premise, you should add this flag to the Magic.ini file and set it to Y.
Since version: 4.5
|
|
WCFCustomFault
|
This flag is used by the WCF Client to disable or enable the Custom Fault support. Set this flag value to N to disable the Custom Fault support . By default, it does not appear in the Magic.ini or ifs.ini file and Custom Fault support is enabled.
Since version: 4.9
|
|
SFDCremoveNewLineDelimiterInData
|
This flag is used by the Salesforce connector.
When this flag is set to Y, all the Line separator (CRLF) characters in the CSV file, generated by the Salesforce connector, will be replaced with a space(s).
By default, it does not appear in the Magic.ini or ifs.ini file. To enable the behavior add the flag and set the value to Y.
Since version: 4.9
|
|
DCRMContinueRequestOnError
|
This flag is used by the Dynamics Connector.
By default, it does not appear in the Magic.ini or ifs.ini file. To enable the behavior add the flag to the [MAGIC_IBOLT] section of the Magic.ini file or add [MAGIC_IBOLT]DCRMContinueRequestOnError to the ifs.ini file and set the value to Y.
When this flag is set to Y, the Dynamics CRM connector, in case of failure to process a record, will not halt the execution but continue to process the subsequent requests.
When this flag is set to N (default), and if there is a failure in processing a record the subsequent requests will not be processed.
Since version: 4.7.7
|
|
SUGARCRM_Max_Number
|
This flag is used to enter the number of records to be fetched in one iteration from the Sugar CRM server.
By default it does not appear in the Magic.ini or ifs.ini file. When this flag is not present in any of these files, the default value will be considered as 1000 in one iteration.
Add this flag to the [MAGIC_IBOLT] section of the Magic.ini file or add [MAGIC_IBOLT]SUGARCRM_Max_Number to the ifs.ini file and set the value, when you need to control the number of records to be fetched from the Sugar CRM server.
|
|
The maximum number of the records to be fetched at a time is limited to 1000 on the server side. So a value exceeding 1000 will be treated as 1000.
|
Since version: 4.7.7
|
|
DBTriggerSyncMode
|
This flag will control the mode of DBTrigger execution.
To run the DBTrigger in synchronous mode, add the flag under the [MAGIC_IBOLT] section of the Magic.ini file or add [MAGIC_IBOLT]DBTriggerSyncMode to the ifs.ini file and set the value to Y.
To run in asynchronous mode, set the value to N or keep it blank. The default value for this flag (and if this flag does not exist) is N.
Since version: 4.13
|
|
UseUnescapeSequence
|
Add this flag under the [MAGIC_IBOLT] section of the Magic.ini file and set the value to Y to prevent the Data Mapper from adding an extra '\' (backslash) character in the '\n' (new line), '\r' (carriage return) and '\t' (tab) in the resulting JSON.
Since version: 4.13.1
|
|
EDISyncMode
|
This flag will control the mode of EDI Trigger execution.
To run the EDI trigger in synchronous mode, add the flag under the [MAGIC_IBOLT] section of the Magic.ini file or add [MAGIC_IBOLT]EDISyncMode to the ifs.ini file and set the value to Y.
Running the trigger in synchronous mode might degrade the performance.
To run in asynchronous mode, set the value to N or keep it blank. The default value for this flag (and if this flag does not exist) is N.
Since version: 4.13.1
|
|
OverwriteStartXMLFile
|
This flag is used to prevent the Magic xpi Studio from overwriting the contents of the start.xml file on building or rebuilding the project. By default, it does not appear in the Magic.ini file. To enable the behavior, add the flag under the [MAGIC_IBOLT] section of the Magic.ini file and set the value to N.
Since version: 4.13.1
|
|
RestClientPathParamURlEncode
|
This flag is used to prevent the encoding of the special characters in the Path Parameters of the REST Client component.
The default value of this flag (and if the flag does not exist) is N.
By default, it does not appear in the ifs.ini file.
To encode the parameters, add the [MAGIC_IBOLT]RestClientPathParamURlEncode flag to the ifs.ini file and set the value to Y.
Since version: 4.13.1
|
|
HTTPTrigSeparator
|
Magic xpi uses the hash (#) character as the trigger name separator. To use any other separator, like a slash (/), this flag can be used. The flag is not present by default and has to be added under the [MAGIC_IBOLT] section of the Magic.ini file and provided with the required value.
The default value for this flag (and if this flag does not exist) is # character. Only one character is allowed. If more than one character is provided then the first character will be used.
The flag is only supported in Magic.ini and not supported as part of ifs.ini.
|
|
-
The value provided here will not be validated by Magic xpi. It is recommended to select the character with caution. Some HTTP reserved characters like *, % may result in failure. Any failure due to an inappropriate character would be the user's responsibility.
-
If this feature is used with the Java Web Requester, then do the following for the changes to take effect:
-
|
Since version: 4.13.2
|
|
MQTTSyncProcessMode
|
This flag determines the order in which the messages are processed by the MQTT trigger.
To receive the messages synchronously, add this flag to the Magic.ini file under the [MAGIC_IBOLT] section and set the value to Y.
Since version: 4.13.3
|
|
SDKConnectorLanguage
|
This flag is used to set the localization language for the SDK connector in the Studio. Add this flag to the [MAGIC_IBOLT] section of the Magic.ini file or add to the ifs.ini file and set the value as per the required language. The value for the language should match with one of the languages defined in the translation.xml. If the language provided in the flag does not exist in the translation.xml, then the base language (EN or JP) as per the installation will be used. If the base language is not present in the translation.xml, then the translation will not be applied.
Since version: 4.13.4
|
|
WriteBigdecimalAsPlain
|
This flag is used to prevent the conversion of numeric values to exponent notation format and show the values in plain text as-is.
For example, the number 12345678 is converted to 1.2345678E7 in exponent notation format. To prevent this conversion, add the WriteBigdecimalAsPlain flag under the [MAGIC_IBOLT] section of the Magic.ini file and set the value to Y.
By default, it does not appear in the Magic.ini file. When the flag is not added, the default value will be considered as N.
Since version: 4.13.4
|
|
DBConnectionClean
|
This flag is used to clean the connections for the internal database resource periodically.
Add the flag to the [MAGIC_IBOLT} section of the Magic.ini file and set its value to Y.
By default, it does not appear in the Magic.ini file. The default value of this flag and when it does not exist is N.
Since version: 4.13.4
|
|
SwapShutdownTime
|
The flag is used in conjunction with the HotSwap feature. This flag is added to the ifs.ini file of the swapped project with the default value of 300 seconds. During the HotSwap process, the original project will wait for the time defined in the flag to shutdown gracefully. After the time defined under this flag is elapsed, if the original project is running then it will be forcefully shutdown and all its running workers will be terminated.
The flag is only supported in ifs.ini and not supported in Magic.ini.
Since version: 4.13.5
|
