User Guide : Getting Started : Cosmos.ini Settings : Optional Settings
Share this page             
Optional Settings
The following table provides the optional settings in the cosmos.ini file.
Note:  The optional settings can be included in the file based on the requirement. Do not include the settings without any value.
Default Value
Used to set the method of writing to a URL as a file.
MIME type used when writing to a URL.
Turns EZscript profiling on or off.
0: Off
1: On
If set, the profile information is written to this file.
Indicates the number of seconds the integration products waits for various network operations to complete such as establishing connections and receiving packets.
Path to the connections directory. Do not change this setting.
Set this option if you want to override the connection file location.
Location of the connections directory.
Allows overriding the source connections location.
Allows overriding the target connections location.
Allow to specify the location of the factory-provided connection files.
Points the Java Virtual Machine to the location of the user-defined packages and classes up to the file level. Set the class path if you are using any user-defined Java classes or packages which are not located in the Runtime Engine working directory or, if the Java objects are Process Designer components, not located in the Plug-ins directory.
Do not enclose the path name in quotation marks.
Points to directories that contain Java .jar files. If set, this value is considered as a list of directories separated by the standard class path separator—semicolon for Windows and colon for Linux.
Do not enclose the path name in quotation marks.
If set, JavaVirtualMachine points to the jvm.dll file for the Java virtual machine to be run. If not set, the integration platform will attempt to load the default for the system.
Do not enclose the path name in quotation marks.
A set of command line arguments for an instance of a Java Virtual Machine. It defines the memory allocated to a JVM when starting integration platform applications.
In addition to the JvmArgs property, you can define separate JVM memory allocations for instances of selected applications. These settings allow more precise memory management for JVM instances competing for system resources.
If set, points to a directory used for storing lookup file indexes.
Lookup subdirectory in the LibraryPath entry.
NamePartAdd or NamePartReplace
Use NamePartAdd function to add entries to the name part. Use NamePartReplace function, to replace the existing entries.
Indicate whether the EZscript compiler must consider OptionExplicit the default.
If set to 0, then OptionExplicit is the default.
If set to true, indicates that other programs can be called during transformation. Else, set to false.
The engine checks for a value when an attempt is made to execute an external command. If execution is not allowed, a shell function causes a type mismatch run-time exception, and an Application step in a process fails. In both cases, the log message is "external program execution disabled."
Indicates whether the white-list entries can be executed. If set to no, false, or 0, there is additionally a whiteListCount, a numeric value indicating the number of white list entries available, and one or more allowlist-n entries (where n ranges from 1 to the value of whiteListCount), each providing the name of an executable that is allowed.
Indicate whether the integration platform uses the older EBCDIC code pages or the newer, corrected versions. The corrected versions are used by default.
If V7compat is set to 1, then the integration platform uses the old code pages.
If V7compat is not set or uses another value, the integration platform uses the new code pages.
Owner of the installed product. Do not change this setting.
Maximum number of concurrent threads in the process engine. Number of threads used will be minimum of this value, and max threads licensed.
Used with delimited ASCII and Unicode source connectors when a map defines only one record type. Values are:
0: Engine does not check the source file against the schema at run time.
1: Check the schema and follow schema mismatch settings if required.