|
|
|
|
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.
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 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
|
