onedata.eagercaching.enabled | |
Enables eager caching. Possible values are: true. false. Default OneData Restart Required: Yes | |
onedata.eagercaching.maxobjects | |
Specifies the maximum number of objects to load in the cache. If 0, then the maximum object count from the licensing module is used. Default value is 100. OneData Restart Required: Yes | |
onedata.eagercaching.multiplicationfactor | |
Specifies the multiplication factor for eager cache personalization and privileges. Default value is 5. OneData Restart Required: Yes | |
onedata.inmemorycaching.enabled | |
Enables in-memory caching. Possible values are: true. false. Default. OneData Restart Required: Yes | |
onedata.inmemorycaching.loaddata.enabled | |
Specifies whether to load data on every startup from all nodes. Possible values are: true. Default. Loads data on every startup from all nodes. false. OneData Restart Required: Yes | |
onedata.inmemorycaching.provider.name | |
Specifies the use of either Coherence or Terracotta for caching. Possible values are: terracotta. coherence. Default. OneData Restart Required: Yes | |
onedata.inmemorycaching.usermetacache.loadonstartup | |
Enables user-meta cache load process on system startup. Possible values are: true. Default. false. OneData Restart Required: Yes | |
onedata.jcs.remotecache.autostart | |
Specifies whether OneData automatically starts the cache server on startup (if distributed caching is enabled). If another service is already running on the port or the port is unavailable, OneData will start, but the cache server will not. In this situation, after the port conflict is resolved, (for example, a listening process on the port is stopped), the cache server will need to be manually started using OneData Cache Console or from the command prompt. Possible values are: true. Automatically restarts the remote cache server. false. Default. Requires manual restart of the remote cache server. OneData Restart Required: Yes | |
onedata.jcs.remotecache.enabled | |
Enables JCS distributed caching. Possible values are: true. Use JCS distributed caching. false. Default. Use JCS standalone caching OneData Restart Required: Yes Note: This property does not start the cache server. | |
onedata.jcs.remotecache.java.maxserverheapsize | |
Specifies the maximum heap size of the JCS remote cache server in megabytes MB (JVM arg -Xmx). Default value is 512. OneData Restart Required: Yes | |
onedata.jcs.remotecache.java.minserverheapsize | |
Specifies the minimum heap size allotted to JCS remote cache server in megabytes MB (JVM arg -Xms). Default value is 128. OneData Restart Required: Yes | |
onedata.jcs.remotecache.java.path | |
Specifies the bin folder location of the local Java installation. If not set, OneData uses the default location set in the classpath.onedata.jcs.remotecache.java.path property. For example: C:\\java\\jdk1.5.0_09\\bin. OneData Restart Required: Yes | |
onedata.jcs.remotecache.name | |
Provides the name of the remote cache configuration. Possible values are: Default value is REMOTE_CACHE. OneData Restart Required: Yes Enabled: NO | |
onedata.jcs.remotecache.nodesize | |
Specifies the number of nodes in a cluster. Multiply this value with the maximum object size of each cache region in the cache server. Default value 1. OneData Restart Required: Yes | |
onedata.jcs.remotecache.servers | |
Specifies the host and port on which cache server(s) are started. The first host:port value starts the primary server. Subsequent values denote failover servers. Failover server(s) are started in standby mode and are designated as the primary server if the primary server fails. host1:port1,host2:port2. OneData Restart Required: Yes | |
onedata.metadatacache.type | |
Specifies whether JCS or Terracotta is used for metadata caching. Possible values are: jcs. Default. OneData caching uses JCS. terracotta. OneData caching is done if Terracotta instance is configured. This property uses the value in the property onedata.terracotta.serverinfo. OneData Restart Required: Yes | |
onedata.terracotta.date.nullvalue | |
Specifies the value Terracotta uses when the date value is null. For example: 1970-01-01 00:00:00. OneData Restart Required: Yes | |
onedata.terracotta.initial.connection.timeout | |
Specifies time in milliseconds that OneData attempts to connect to the Terracotta server when OneData starts. If OneData cannot establish a connection before the timeout limit is reached, OneData will only retry the connection when it receives a cache request. Default value is 1000. OneData Restart Required: Yes | |
onedata.terracotta.numeric.nullvalue | |
Specifies the value Terracotta uses when the numeric value is null. For example: -2147483648. OneData Restart Required: Yes | |
onedata.terracotta.serverinfo | |
Specifies the Terracotta server host name and port. To use multiple Terracotta servers, list each host name separated by a comma. Define the hostname:port, for each Terracotta. For example: localhost:9510. OneData Restart Required: Yes Enabled: Yes | |
onedata.terracotta.string.nullvalue | |
Specifies the value that Terracotta uses when the string value is null. Default value is OD#NULL#OD. OneData Restart Required: Yes |
onedata.charlengthsemantics.enabled | |
Specifies the semantics for multi-byte characters while running conceptual object export jobs. Possible values are: true. OneData uses CHAR semantics. false. Default. OneData uses the default character semantics. In Oracle, default character semantics is set using the parameter NLS_LENGTH_SEMANTICS. OneData Restart Required: Yes | |
onedata.datainterchange.nullify.keyword | |
Specifies, in the data interchange layer, if OneData must nullify an empty field while constructing the XML for an import job. Default value is NULLIFY_FIELD OneData Restart Required: No | |
onedata.datainterchange.survivorship.subscribingSystemCountForPriority | |
Configure the priority count required for survivorship mapping. Default value is 20 OneData Restart Required: No | |
onedata.datainterchange.useCustomNumericFormatter | |
Determines whether custom formatter is used for numeric columns. Possible values are: true. If using non-default driver. false. Default. If using default driver. Note: Interchange Mapping import uses this property when the primary key of the entity contains a numeric field with precision and the imported data is specified without decimal places. OneData Restart Required: No | |
onedata.datainterchange.xmlcsvoptimisation | |
Specifies whether to optimize performance when importing data from an XML file and converting it to a CSV file. Possible values are: true. Default. Optimize performance. false. OneData Restart Required: Yes | |
onedata.deployment.batchsize | |
Specifies the number of records deployed per batch during export. Default is 1000. OneData Restart Required: Yes | |
onedata.dispaly.boolean.servicelayer | |
In the RESTful service, enables XML to display true or false as the boolean value if the object contains column of boolean data type in OneData. Possible values are: true. The XML prints true or false as the boolean value. false. Default. The XML prints Yes or No for the boolean value. OneData Restart Required: No | |
onedata.exceptionqueue.fetchsize | |
Specifies the maximum number of rows to display in the exception queue. Default value is 200. OneData Restart Required: No | |
onedata.exceptionqueue.numberofcolumns | |
Improves error handling of Interchange Mapping profiles containing a large number of fields. Default value is 50 Note: If you change the value of this property to any value above 50, the corresponding change must be done to the exception queue table, OD_MD_QUEUE_RCD. For example: If you set onedata.exceptionqueue.numberofcolumns to 60, in the metadata schema, run the following migration script to add the additional 10 columns: ALTER TABLE OD_MD_QUEUE_RCD ADD ( COLUMN_51 VARCHAR2(2000), COLUMN_52 VARCHAR2(2000), COLUMN_53 VARCHAR2(2000), COLUMN_54 VARCHAR2(2000), COLUMN_55 VARCHAR2(2000), COLUMN_56 VARCHAR2(2000), COLUMN_57 VARCHAR2(2000), COLUMN_58 VARCHAR2(2000), COLUMN_59 VARCHAR2(2000), COLUMN_60 VARCHAR2(2000) ); OneData Restart Required: No | |
onedata.foreignkey.relatedDescription.isDefaultBehaviour | |
Defines the format of the foreign key description in Data Manager and REST GET responses for backward compatibility with earlier OneData versions. This property is applicable to the primary-foreign key configuration when the primary key is set as the related column description in a foreign key. Possible values are: true. Default. OneData uses the foreign key properties. false. OneData uses column properties. OneData Restart Required: No | |
onedata.interchangeexecution.batchsize | |
Specifies the number of records to include in an import batch job. The commit is performed only at the end of the import process. Default value is 100. OneData Restart Required: No | |
onedata.interchangeexecution.pooled | |
Enables the use of pooled connections for interchange. Possible values are: true. Default. Enables pools. false. Disables pools. OneData Restart Required: No | |
onedata.interchangeexecution.poolsize | |
Specifies the size of pool for interchange connections. Default value is 5. OneData Restart Required: No | |
onedata.interchangeexecution.termination.threshold | |
Specifies the maximum number of errors that occur in a batch job before OneData aborts the import process. Default value is 10. OneData Restart Required: No | |
onedata.logjobexecution parameters.enabled | |
Enables configuration parameters like mode, execution type, and execution options that OneData uses. Note: You can only view the execution parameters if this property is set to true. The Job center displays an empty tag <JOB_EXECUTION_INFO> if this property is not enabled. Possible values are: true. Enables execution parameters. false. Default. Disables execution parameters. OneData Restart Required: Yes | |
onedata.message.outbound.realtime.displayForeignKey | |
Enables you to include reference values of foreign keys in outbound JMS XML messages for conceptual objects. Possible values are: true. Includes reference values of foreign keys for child entities. false. Default. Exclude reference values of foreign keys for child entities. OneData Restart Required: No | |
onedata.message.outbound.realtime.ms.discard | |
Specifies whether to display multi-select columns in outbound XML. Possible values are: true. The outbound XML displays multi-select column values. false. Default. The outbound XML hides the multi-select columns. OneData Restart Required: No | |
onedata.opencsv.escapecharacter | |
Specifies the escape character to use in XML and REST service data processing. The default escape character is a backslash. Default value is DEFAULT. Uses backslash. OneData Restart Required: Yes | |
onedata.opencsv.stringqualifier | |
Defines the character that OneData uses as a string qualifier in the CSV operations. Default value is ^. OneData Restart Required: No Note: The property value should be any ASCII value other than ^ and should be a special character that is not likely to appear in the RESTful webservice or Interchange Mapping payload. | |
onedata.rmi.registry.host | |
Specifies the host on which OneData runs when connecting from different clients like PL-SQL or RMI hooks. The following example sets the RMI Registry as localhost. localhost OneData Restart Required: Yes | |
onedata.rmi.registry.port | |
Specifies the RMI registry port. This port number should be changed when another application server uses the default RMI registry port. Default value is 1099 OneData Restart Required: Yes | |
onedata.rmi.service.ports | |
Specifies the service ports, separating each port with a comma. For example: 2090,2091. OneData Restart Required: Yes | |
onedata.service.enableClobUpdateWithoutChangeDetection | |
Enables update of CLOB columns during data quality processing. Possible values are: true. Default. Process CLOB column updates during data quality processing. Note: CLOB columns can contain a large amount of data. When CLOB processing is set to true, for improved performance during batch processing, OneData stores CLOB column data for all records in a batch in the JVM memory heap. Therefore, ensure that you allocate sufficient JVM memory heap. The amount memory heap required is dependent on the average size of data in each CLOB column x Number of CLOB columns in a table x Number of records in a batch x Number of concurrent processing batches. false. Ignore CLOB column updates. OneData Restart Required: No | |
onedata.service.serviceLogConsumerIdleTimeToLive | |
Time to live in seconds for serviceAuditLoggerConsumer thread when service audit logs are enabled. This prevents the exhaustion of OneData connection pools. Default is 86400. OneData Restart Required: No | |
onedata.service.serviceLogLevel | |
Specifies the audit log level for inbound service requests through REST, Interchange Mapping, and JMS. See
Service Layer Logging for Inbound
Requests for a complete list of Master and Detail table entries for each log level. Note: Use either log level 2 or 3 to ensure that REST response requests contain adequate service audit information. Possible values are: 0. No logs are created. 1. Basic logging that provides a summary of the data import process, including, status of the process, duration of the process execution, data source, and so on. 2. Default log level. Detailed log level that includes basic service audit information and details of inbound service request at the record level. 3. Advanced logging level that includes detailed service audit information and additional information about the mapping of payload to OneData entities. OneData Restart Required: No | |
onedata.service.serviceLogRetentionOption | |
Retains or deletes the service audit log entries when the related interchange mappings are deleted. Possible values are: 0. Default. Retains service audit log entries when the related interchange mappings are deleted. 1. Deletes the service audit log entries when the related interchange mappings are deleted. OneData Restart Required: No | |
onedata.webservice.rest.baseVersion | |
Enables the downward compatibility in REST web services for the response output when retrieving data. The value specified in the request parameter overrides the one specified at the system level. true. Generates response output without datarows. false. Default. Generates response output data wrapped within datarows. OneData Restart Required: No | |
onedata.webservice.rest.CO.implicitFilter.support.isEnabled | |
Enables filtering of conceptual object data based on the implicit filters of the constituent data objects. Possible values are: true. false. Default. OneData Restart Required: No | |
onedata.webservice.rest.enableXMLEscapeInJSON | |
Determines if special XML characters must be escaped for JSON response data. The property is applicable only to data values and not to metadata values like table name, column name, and so on. Possible values are: true. Default. Special XML characters are escaped in JSON responses. false. Special XML characters are not escaped in JSON responses. OneData Restart Required: No | |
onedata.webservice.rest.foreignKeyRelatedDescription.format | |
Determines the format in which the multiple column foreign key description is displayed in the REST GET response. Possible values are: 0. Default. Each column of the multiple column description appears as a separate element in the response. 1. Displays the single column description in the response even if you have configured multiple column description. 2. Displays the multiple column description with unique tags containing the child attributes as object/simple structure. OneData Restart Required: No | |
onedata.webservice.rest.ignore.HideInDisplayCol.In.Schema | |
Allows the display of columns in REST schema even when Hide in Display Screen? is enabled. Possible values are: true. Columns that have Hide in Display Screen? enabled are not displayed in the REST schema. false. Default. Columns that have Hide in Display Screen? enabled are displayed in the REST schema. OneData Restart Required: No | |
onedata.webservice.rest.inclause.delimiter | |
Specifies the default character to use as a delimiter in a REST service. Default values is ;. OneData Restart Required: No | |
onedata.webservice.rest.json.enableSupportForDataObjectRepetitionInHierarchy | |
Enables JSON POST actions on a child entity or data object that appears at multiple and different hierarchy levels of a parent object. Possible values are: true. Enables JSON POST actions on child entities or data objects that appear at different levels of the parent object hierarchy. false. Default. Disables JSON POST actions on child entities or data objects that appear at different levels of the parent object hierarchy. OneData Restart Required: No | |
onedata.webservice.rest.objectNamePrefixedInXSD | |
Specifies if the XML/JSON Element Name defined for an object should be prefixed to the object's column names in the implicit interchange mappings (that is, the RESTful GET output and the input POST XMLs, XSDs and JSON), by default. Possible values are: 0. Default. Generates XSD/JSON and handles REST (GET and POST operations) without a prefix to the column names, by default. This enables backward compatibility with objects created in OneData versions 9.7.x and earlier. 1. By default, prefixes the XML/JSON Element Name defined for an object to the column names in XSD/JSON and REST GET output generated, and expects the prefix in the REST POST input. If you do not define an XML/JSON Element Name for an object, OneData uses the physical table name as the column name prefix. OneData Restart Required: No | |
onedata.webservice.rest.post.returnColumn.enableObjectNameRepetitionInTags | |
Determines the appearance of the object name in the REST response when returnColumns is enabled. Possible values are: true. Object name appears once for each batch in the REST response. false. Default. Object name appears only once in the REST response irrespective of the number of batches. OneData Restart Required: No | |
onedata.webservice.rest.processEmptyRow | |
Provides mechanism to invoke interchange mapping using RESTful web service calls, when the payload contains rows with all empty column values. Possible values are: true. false. Default. OneData Restart Required: No | |
onedata.webservice.rest.responseLogLevel | |
Specifies the log level of record audit information for inbound service requests to include in REST responses. Note:onedata.service.serviceLogLevel log level must be set to either 2 or 3 to ensure that REST response requests contain adequate service audit information. Also ensure that you specify returnColumns for 1, 2, 4, 5, and 6. Possible values are: 0. Default log level. No service audit information in REST responses. 1. Includes service audit log information as an attribute for each data row of the record. The log includes basic information like the transaction type, transaction status, service log ID, and primary key of the record. 2. Includes service audit log information as a separate element in a data row of the record. The log includes, in addition to basic information, the status (success or error) message of the service request. 3. Includes service audit log information in the tag SERVICE_AUDIT, as a separate section in the REST response. 4. Combines the information for logging levels 1 and 3 in the REST response, by including service audit log information as attributes in data rows and in separate sections. 5. Combines the information for logging levels 2 and 3 in the REST response, by including service audit log information as elements in data rows and in separate sections. 6. Includes service audit log information only for those records for which service request have failed. The log information appears as elements in data rows. OneData Restart Required: No | |
onedata.webservice.rest.schema.columnOrder.isOldBehavior | |
Configure the synchronization of column order between the XSDs defined and the XML responses. Possible values are: true. Default. When the column order is explicitly modified in the user interface, the column order in XML responses may vary from the XSDs defined. false. The column order in XML responses and the XSDs defined is synchronized. OneData Restart Required: No | |
onedata.webservice.rest.wildcard.op | |
Specifies the default wildcard character in REST web services. This can be overridden in the rest service. Ensure that the character is not used in the data column. Default value is $. Possible values are $`!;@^*( )< >':|~. OneData Restart Required: No | |
onedata.xml.objectcaption.enable | |
Enables the use of caption names of objects as XML/JSON element names. Possible values are: true. OneData uses the object caption name as element name in the outbound XML/JSON. Object caption names cannot contain spaces. false. Default. OneData uses the table names as the element names in the outbound XML/JSON. Object captions can contain spaces. OneData Restart Required: Yes |
onedata.datamanager.bulkupdate.batchcount | |
Configures the maximum number of records to process in a Update Bulk batch. If you select Apply to selected rows, this property is not applicable. Default value is 100. OneData Restart Required: No | |
onedata.datamanager.bulkupdate.partialcommit.enabled | |
Allows the Bulk Update process to process records in batches when it is run as a job using Execute as Job option. You can view the status of batch processing in the View Job Log window. Possible values are: false. Default. On the first instance of failure to process a record in a batch, the Bulk Update process stops processing the records, and rolls back all batches. For example, Bulk Update is run for 1000 records, and each batch is configured to contain 100 records. Records in the first two batches are processed successfully. In the third batch, update fails for the 20th record. OneData stops the Bulk Update process. Then, OneData rolls back the updates to even the first two batches that were successfully processed. true. If a single record in a batch fails, the Bulk Update process rolls back the whole batch immediately. OneData continues to process the remaining batches. When all batches have been processed, OneData commits the successfully processed records. For example, Bulk Update is run for 1000 records, and each batch is configured to contain 100 records. Records in the first two batches are updated successfully. In the third batch, update fails for the 20th record. OneData rolls back all the records in the third batch, and proceeds to process the remaining batches successfully. At the end of the last batch, OneData commits the all 900 records successfully processed. OneData Restart Required: No | |
onedata.datamanager.DataAuditDisplay.isCloneEnabled | |
Controls the display of cloned object in the Data Audit screen. Possible values are: true. Default. Displays the cloned objects details. false. Hides the cloned objects details. OneData Restart Required: No | |
onedata.datamanager.displaygrid.enableViewEditCOLevelTreeHierarchy | |
Enables users to determine whether the level tree hierarchy of conceptual objects is available for viewing and editing (based on user privilege) in the Data Manager grid. Possible values are: true. Default. View Hierarchy and Edit Hierarchy buttons are enabled for conceptual objects level tree hierarchy in the grid. false. Level tree hierarchy for conceptual objects is not displayed in the grid. OneData Restart Required: No | |
onedata.datamanager.displaygrid.keepHTMLPREtag | |
Specifies whether to include or exclude the HTML <PRE> tag in Data Manager grids. Possible values are: true. Default. Allows OneData to: Ignore the column width specified for VARCHAR columns. Display text without wrapping it in the column width specified for VARCHAR columns. Retain the original formatting of data. Include additional spaces between words. false. Exclude the HTML <PRE> tag in Data Manager grids and consider the column width specified for VARCHAR columns when displaying data. OneData Restart Required: No | |
onedata.datamanager.excludeInputValidation.withPattern | |
Allows users to customize XSS validation of submitted fields to a table, enabling OneData to skip XSS validation for specified fields. Possible values are: true. OneData skips text validation in fields which contain partial matching patterns specified in the od_md_mstprop metadata table. Note: Software AG recommends that you do not enable this property as it may lead to a security vulnerability. false. Default. OneData validates data table fields for XSS vulnerability, and displays an error. OneData Restart Required: No | |
onedata.datamanager.newui.dataentryscreen.columnlayout | |
Determines the column layout in edit and insert screens in the new UI, which is deprecated. According to these values, OneData renders the edit or insert screen in the new UI. Possible values are: 1. Default. Single column layout. 2. Two column layout. OneData Restart Required: No | |
onedata.datamanager.nr.copyassibling | |
Determines whether to copy the new node at the same level as the selected node or copy the node as a child of the selected node, when copying a network recursive tree. Possible values are: true. Copies the new node at the same level as the selected node. false. Default. Copies the node as a child of the selected node. OneData Restart Required: No | |
onedata.datamanager.reports.leftAlignMandatoryColumn | |
Aligns column values of type text to left when you download the report in Excel format. Possible values are: true. Text field values are left aligned in the report. false. Default. Text field values are aligned as per Excel formatting in the report. OneData Restart Required: No | |
onedata.datamanager.TrimLeadingAndTrailingSpacesInDataValuesInNovaMode.enabled | |
Enables space as a valid value in string columns. Possible values are: true. Trims the extra space and not process it as a valid value. false. Default. Processes the space as a valid value. OneData Restart Required: No | |
onedata.error.DisplayHookExceptionInErrorPageSummarySection.enabled | |
Displays run-time errors for the hooks module in the Summary section of the error message panel. The Summary section is visible to all users without requiring any additional user action. Set this property to false to enable backward compatibility for displaying run-time error messages for the hooks module in the collapsed Exception Details section of the error message panel. Users must expand the section in order to view the error message. Possible values: true. Display the run-time error messages for the hooks module in the Summary section of the error message panel. No user action is required to view the error message. false. Default. Displaying run-time error messages for the hooks module in the collapsed Exception Details section of the error message panel. Users must expand the section in order to view the error message. OneData Restart Required: No | |
onedata.hook.datamanager.executePreHookBeforeNovaValidation | |
Enables you to configure whether Data Manager must perform Nova validations before or after pre-hook execution. Possible values are: true. Enables pre-hook execution before Data Manager performs Nova validations. false. Default. Enables Data Manager to perform Nova validations before pre-hook execution. OneData Restart Required: No | |
onedata.hook.wf.IncludeTransactionDetailsInExpandedRowSet.option | |
In workflow hook mappings, when approvers either reject or approve conceptual object transactions in the approval pipleline, this property enables you to specify which transaction details OneData must retain in originalExpandedRowSet. Possible values are: 0. Default. Retains all object rows without transaction details. 1. Retains all object rows with transaction details. 2. Retains only rows pending approval with transaction details. OneData Restart Required: Yes | |
onedata.hook.wf.mscolumnprocess.enabled | |
Enables processing of multi-select columns in workflow hooks. Possible values are: true. Default. false. OneData Restart Required: No | |
onedata.novaui.datagrid.hyperlink.navigatetoforeignkeyobject | |
Controls the object that OneData opens for edit when you click the constituent reference value link of a conceptual object in the data grid. Possible values are: true. Default. Constituent reference value link opens the foreign key object for edit. false. Constituent reference value link opens the reference object for edit. OneData Restart Required: No | |
onedata.recursivetree.childnodecount | |
Configures the number of child nodes to display in Nova recursive tree. Default value is 1000. OneData Restart Required: No | |
onedata.reports.excel.keepHTMLPREtag | |
Controls the file size and formatting of a report in Excel format by including or excluding the HTML <PRE> tag set to: true. Default. Includes the HTML <PRE> tag in each character column cell of the Excel report. The original formatting of the report data is retained, including additional spaces between words. However, the increased file size increases the possibility of rendering issues if the browser memory is not sufficient. false. Does not include the HTML <PRE> tag in the Excel report. This option is preferable for a reduced file size and read-only purpose. OneData Restart Required: No Enabled: Yes | |
onedata.tree.treenodecount | |
Specifies the number of rows to display for object hierarchy represented in the tree display mode in Data Manager. Default value is 100. OneData Restart Required: Yes | |
onedata.workflow.enableAutoApproveFromCreatorInitiatedLevel | |
Enables auto-approval of records at Level 1 if the workflow creator approved the record at Level 0. Possible values are: true. If the Level 1 approvers' list contains the creator, and all approvers are linked by the OR condition, OneData automatically approves records at Level 1 if the records were approved by the creator at Level 0. false. Default. Auto-approval at Level 1 does not occur for records previously approved by their creators at Level 0. OneData Restart Required: No | |
onedata.workflow.enableSaveRecordOnRequestInfo | |
Enables updates to any record attribute when a record is pending update action approval at Level 0 and is assigned for information (RequestInfo). OneData saves records depending on the property value: true. If the record is pending update action approval at Level 0 and is assigned for information, based on user privileges, OneData allows updates to the modified attributes and all other record attributes. false. Default. If the record is pending update action approval at Level 0 and is assigned for information, OneData restricts updates to only the modified attributes. Note: When a record is pending approval at Level 0 on an update action and the user requests for information on it, OneData allows updates to the record to move from the Work Area to the Release Area without awaiting approval for the action. Hence, a Reject action is not possible for any subsequent modifications. OneData Restart Required: No | |
onedata.workflow.rewindonupdateaction | |
Rewinds the workflow level of a non-recursive conceptual object that is pending approval in the insert workflow process if a record is updated at the root level or child object level. Possible values are: true. Default. OneData rewinds the workflow level of the non-recursive conceptual object that is pending approval in the insert workflow process to level 1 when a record is updated at the root level or child object level. false. OneData does not rewind the workflow level of the non-recursive conceptual object that is pending approval in the insert workflow process when a record is updated at the root level or child object level. Note: This property is not applicable to data objects. OneData Restart Required: No | |
onedata.workflow.workflowaction.mode | |
Handles all transactions in the workflow pending screen as a single JDBC transaction or each transaction as a separate JDBC transaction. Possible values are: 0. Default. Handles all transactions selected in the workflow pending screen as a single JDBC transaction. 1. Handles each workflow transaction in the workflow pending screen as a separate JDBC transaction. OneData Restart Required: No |
onedata.dataquality.additionalpropertydelimiter | |
Specifies the delimiter used between columns in a data source file. Default value is ;. OneData Restart Required: No | |
onedata.dataquality.batchsize | |
Specifies the maximum batch size for processing data quality records. Default value is 100. OneData Restart Required: Yes | |
onedata.dataquality.countrytranslation.isocountrycodecolumn | |
Specifies the ISO code column in the country code table defined in onedata.dataquality.countrytranslation.tablename. Default value is ISO_CHAR_2_CODE. OneData Restart Required: No | |
onedata.dataquality.countrytranslation.primarykeycolumn | |
Specifies the primary key column in the country code table defined in onedata.dataquality.countrytranslation.tablename. Default value is CNTRY_ID. OneData Restart Required: No | |
onedata.dataquality.countrytranslation.tablename | |
Specifies the table name used for country codes. Default value is GEO_COUNTRY. OneData Restart Required: No | |
onedata.dataquality.creategoldpattern | |
Specifies the string used in the pattern mapping screen for creating gold to execute Interchange mapping. Default value is 101. OneData Restart Required: Yes | |
onedata.dataquality.enableCLOBColumnProcessing | |
Enables update of CLOB columns during data quality processing. Possible values are: true. Process CLOB column updates during data quality processing. false. Default. Ignore CLOB column updates. Note: CLOB columns can contain a large amount of data. When CLOB processing is set to true, for improved performance during batch processing, OneData stores CLOB column data for all records in a batch in the JVM memory heap. Therefore, ensure that you allocate sufficient JVM memory heap. The amount memory heap required is dependent on the average size of data in each CLOB column x Number of CLOB columns in a table x Number of records in a batch x Number of concurrent processing batches OneData Restart Required: No | |
onedata.dataquality.execution.pooled | |
Enables running of batch matches or data-quality-enabled imports in threaded mode or execution pools. true. Enables execution pools. false. Default. Disables execution pools. OneData Restart Required: Yes | |
onedata.dataquality.locate.validAVCCodes | |
Lists the Locate address verification codes (AVC) with # as the separator delimiter. You can also provide the first few characters of the codes instead of the complete codes. The default value of the property is All, which means that all address verification codes are valid. If OneData verifies that a record contains the listed codes, the records are marked as Cleansed. If the codes are not present in the records, the records remain in Unassigned status. For more information on AVC codes, see webMethods OneData Consolidation MDM Guide. Default value is All. OneData Restart Required: No | |
onedata.dataquality.locate.validGACCodes | |
Lists the Locate geo accuracy codes (GAC) with # as the separator delimiter. You can also provide the first few characters of the codes instead of the complete codes. The default value of the property is All, which means that all address verification codes are valid. If OneData verifies that a record contains the listed codes, the records are marked as Cleansed. If the codes are not present in the records, the records remain in Unassigned status. For more information on AVC codes, see webMethods OneData Consolidation MDM Guide. Default value is All. OneData Restart Required: No | |
onedata.dataquality.manualmatch.popupwindow.enablenewalignment | |
Allows you to simultaneously view the maximum amount of details of the staging record and the Gold record simultaneously. Possible values are: true. The match window is positioned and sized relative to the selected Gold record row in the grid. For any record in the first half of the selected record. Also, the height and width of the match window is automatically adjusted to display at maximum height and width. Once the match window opens for a record, the view focus is on the match window. On closing the match window, when the view focus switches to the OneData screen. The only exception is in Microsoft Edge browser, where the match window is not positioned relative to the selected Gold record row in the grid. The match window is always positioned at top-left corner of the browser. false. Default. The match window is displayed at minimal size and at top left-hand corner of the OneData screen in the browser. OneData Restart Required: No | |
onedata.dataquality.matchwindowsize | |
Specifies the count of match candidates selected for matching. Default value is 100. OneData Restart Required: Yes | |
onedata.dataquality.multipleconnections.enabled | |
Enables multiple connections for data quality processing. true. Default. Enables multiple connections to the data quality server. false. Disables multiple connections to the data quality server. OneData Restart Required: Yes | |
onedata.dataquality.rerunmatchingfordataload.enable | |
Enables or disables the rerun of matching for REST API's record insert or import. Possible values are: true. false. Default. OneData Restart Required: No | |
onedata.dataquality.showAdditionalMatchingInformation | |
Enables you to hide the pattern column for multiple Gold model. Possible values are: None. Hides Windowkeys and data quality detail columns. None (Exclude Pattern for Multiple Gold Model). Excludes DQ_MATCH_PATTERN in multiple gold model along with Windowkey, DQ detail columns. Windowkeys Only. Displays only windowkey columns. Windowkeys Only (Exclude Pattern for Multiple Gold Model). Excludes DQ_MATCH_PATTERN in multiple gold model along with DQ detail columns. Matching Details Only. Displays only detailed data quality information. All. Default. Displays all columns. OneData Restart Required: No | |
onedata.dataquality.useGoldObjectIdFromProjectObjectMapping | |
Enables OneData to use only the metadata of the Gold object mapped in the project-object mapping. Possible values are: true. OneData uses only the metadata of the Gold object mapped in the project-object mapping. As a result, the Manual Match window includes all columns mapped in the project-object mapping. If the object used in the project-object mapping is a view, OneData uses the columns from any underlying tables. false. Default. Set this value for either of the following conditions: If the object in project-object mapping and the base object are the same. If you want OneData to include columns from the table set as the base object. OneData Restart Required: No | |
onedata.dataquality.useMatchWindowSize | |
Enables you to use the match window size specified in onedata.dataquality.matchwindowsize or use all the available match candidates. true. false. Default. OneData Restart Required: Yes |
onedata.defineobjects.conceptualobject.cycliccheckhandling | |
Specifies how OneData handles constituent objects having a cyclic relationship in conceptual objects. Possible values are: 0. Default. OneData displays an error in the Definition Object > Structure tab of conceptual objects if the constituent objects have a cyclic relationship. 1. Ignores constituent objects having a cyclic relationship. OneData Restart Required: No | |
onedata.defineobjects.synchronizestructure.retaindefaultvalueincolumn | |
Allows you to define if OneData retains the default value for columns in the object definition while synchronizing the object structure. Possible values are: true. Retains the default value in the object definition instead of overwriting it with the database value. false. Default. Overwrites the default value with the database value. OneData Restart Required: No | |
onedata.multiselect.excludecyclicFK.enabled | |
Excludes multi-select columns from foreign key when checking cyclic relationships. Possible values are: true. Default. false. OneData Restart Required: No |
onedata.search.autocomplete.category.pagesize | |
Specifies the maximum number of auto-complete suggestions to display in the select box. Default value is 5. OneData Restart Required: No | |
onedata.search.autocomplete.mincharlength | |
Specifies the number of characters users must enter before the auto-complete suggestions are displayed for the search string. Default value is 3. Note: It is not recommended to change the value. OneData Restart Required: No | |
onedata.search.contextpane.grid.pagesize | |
Specifies the size of the details pop-up window displayed when the user clicks the record name in the search results list. Default value is 10. OneData Restart Required: No | |
onedata.search.elasticsearch.cluster.clustername | |
Specifies the unique cluster name as given in the elasticsearch.yml file. OneData Restart Required: Yes | |
onedata.search.elasticsearch.descriptioncolumn.weightage | |
Specifies the weightage to assign to the description column compared to other columns that can appear in the search results. The weightage value must be 3 or higher for OneData to consider the weightage of the description column. Default value is 3. OneData Restart Required: No | |
onedata.search.elasticsearch.enabled | |
Enables the Elasticsearch engine. Possible values are: true. Default false. OneData Restart Required: Yes | |
onedata.search.elasticsearch.fuzziness | |
Specifies if Elasticsearch fuzzy matching is enabled and the matching algorithm employed. The other possible values are: Possible values are: AUTO. Enables fuzzy matching. -1. Disable fuzzy matching. 1. Sets the edit distance to one character. 2. Sets the edit distance to two characters. 3. Sets the edit distance to three characters. OneData Restart Required: No | |
onedata.search.elasticsearch.indexanalyzer | |
Tokenizes the data before indexing and stores the tokens and actual data in Elasticsearch indexes. For configuring custom analyzer, see
Customize Elasticsearch analyzer. Possible values are: autocomplete. Default. This is a custom analyzer defined in analyzer.txt. OneData Restart Required: Yes Note: If you have migrated OneData to the latest version and if the property was previously set to autocomplete_analyzer, then manually set the value of this property to autocomplete. Note: Software AG recommends that you perform a proper analysis before changing the value of this property. Changing this analyzer changes the search results. | |
onedata.search.elasticsearch.loaddata.batchsize | |
Specifies the number of table rows to load for processing by Elasticsearch. Default value is 100. OneData Restart Required: Yes | |
onedata.search.elasticsearch.loaddata.loadonstartup | |
Enables the loading of data to Elasticsearch search engine during OneData startup. For clustered Elasticsearch server, set this property to true only on a single node and false on all the other nodes Possible values are: true. Default. false. OneData Restart Required: Yes | |
onedata.search.elasticsearch.loaddata.poolsize | |
Specifies the size of the Elasticsearch connection pool. Default value is 5. OneData Restart Required: Yes Enabled: No | |
onedata.search.elasticsearch.loadmetadataonly | |
Enables Elasticsearch indexing in all schemas (metadata, work area, and release area) or in one schema only (metadata). Possible values are: true. Enables Elasticsearch indexing metadata only. false. Default. Enables Elasticsearch indexing in all schemas (metadata, work area, and release area). OneData Restart Required: Yes | |
onedata.search.elasticsearch.priorityforexactmatch | |
Specifies if exact match in the search has greater priority than fuzzy matches. Possible values are: true. Default. Exact matches have greater priority than the fuzzy match. false. Fuzzy matches have greater priority than the exact match. OneData Restart Required: No | |
onedata.search.elasticsearch.searchanalyzer | |
Tokenizes the search string passed for search. For configuring custom analyzer, see
Customize Elasticsearch analyzer. Possible values are: standard. Default. This is the default analyzer provided by Elasticsearch and not a custom analyzer, so it cannot be seen in analyzer.txt. OneData Restart Required: Yes Note: Software AG recommends that you perform a proper analysis before changing the value of this property. Changing this analyzer changes the search results. | |
onedata.search.elasticsearch.server.httpurl | |
Specifies the Elasticsearch server URL. Default value is http://localhost:9240. OneData Restart Required: Yes | |
onedata.search.elasticsearch.sortanalyzer | |
Controls the sorting of search results in Elasticsearch. For configuring custom analyzer, see
Customize Elasticsearch analyzer. Possible values are: sortable_analyzer. Default. The sortable_analyzer is a custom analyzer defined in analyzer.txt. OneData Restart Required: Yes Note: Software AG recommends that you perform a proper analysis before changing the value of this property. Changing this analyzer changes the search results. | |
onedata.search.elasticsearch.termoperator | |
Specifies the operators to use when the search string contains multiple words. Possible values are: and. Default. or. OneData Restart Required: Yes | |
onedata.search.remoteobject.datarefresh | |
Enables the re-indexing of the remote object in Elasticsearch data refresh job. By default Elasticsearch indexes data when OneData starts. To re-index the changed state of objects, Data refresh jobs in OneData is used. Possible values are: true. Default. false. OneData Restart Required: No | |
onedata.search.searchpane.grid.pagesize | |
Specifies the maximum number of search results to display in the result grid box for each data type. Default value is 5. OneData Restart Required: No | |
onedata.search.server | |
Specifies the search engine server OneData uses. Possible values are: ELASTIC_SEARCH. Default. DB_SEARCH. OneData Restart Required: Yes |
onedata.administration.ui.tabset.enableloadingindicator | |
Enables the data loading indicator in the menu option tabs of OneData. Under rare circumstances, the loading indicator could freeze indefinitely because OneData fails to load data to the selected tab, forcing the user to remain on the tab where the issue occurred. Even restart of the OneData server will not resolve the issue. If this situation occurs, disabling the property will unfreeze the user interface so that the user can switch to other tabs when OneData fails to load data to any particular menu option tab. Possible values are: true. Default. Enables loading indicator while OneData loads data to the menu option tabs. false. Disables the loading indicator on the user interface while loading data to the menu option tabs. OneData Restart Required: No | |
onedata.application.uri | |
Specifies the URI that is used to create a clickable link to OneData in system-generated emails. This URI is required because application servers can be hidden behind load balancing or proxy web servers. For example: http://localhost:8080/onedata/ Note: Update the property with the complete host name of your machine after installing OneData. OneData Restart Required: No | |
onedata.application.version | |
Specifies the application version number. For example: 10.5.0. OneData Restart Required: No | |
onedata.audit.configuration.criticalauditspurge.enable | |
Enables or disables purging of audit logs for the service layer, workflow, and change request modules. Possible values are: true. Enables purging of audit logs for the service layer, workflow, and change request logs, and displays the relevant fields in the Metadata Audit Configuration tab of the System Properties screen. The fields display zero as the default value, which ensures that OneData does not purge these critical audit logs unless you manually change the value to any number greater than zero. false. Default. Disables purging of audit logs for the service layer, workflow, and change request logs, and hides the relevant fields in the Metadata Audit Configuration tab of the System Properties screen. OneData Restart Required: No | |
onedata.broadcastmessage.fetchinterval | |
Specifies the duration (in seconds) for which OneData waits before checking for new broadcast messages. Default value is 60. OneData Restart Required: No | |
onedata.buildNumber | |
Specifies the release build number. For example: 0052. OneData Restart Required: No | |
onedata.clustering.enabled | |
Enables OneData to run in a clustered environment. The quartz scheduler uses this property in a clustered environment. Possible values are: true. OneData is running in a clustered environment. false. Default. OneData is not running in a clustered environment. OneData Restart Required: No | |
onedata.clustering.node | |
Specifies the unique name used to identify the OneData node in a cluster. Set this property for each node in the cluster. For example: server1. OneData Restart Required: No | |
onedata.datamanager.bulkupdate.subtype | |
Enables bulk update for subtypes when performed on Supertype-subtype objects in the Conceptual Object context. Possible values are: true. false. Default. Note: The following conditions have to be met before performing a bulk update for subtype records: Supertype-subtype object has a single primary key. Subtype is selected in Conceptual Object definition. OneData Restart Required: No | |
onedata.i18n.supportedlanguages | |
Specifies the languages that OneData supports. OneData displays this list in the user interface when configuring the preferred language and locale in the Metadata Repository Configuration and User Preferences screens. OneData only uses this property if it cannot automatically detect the supported languages on startup from the available resource bundles. To add more than one supported language, separate each with a comma. For example:en_US, vi_VN, es_ES. Default value is en_US. OneData Restart Required: Yes | |
onedata.notification.contactname | |
Specifies the name of the contact person that OneData sends notifications to when a job fails. For example: Brooks Robinson. OneData Restart Required: No | |
onedata.notification.contactnumber | |
Specifies the contact number that OneData sends notifications to when a job fails. For example: 888-848-2473 OneData Restart Required: No | |
onedata.notification.failuremailid | |
Specifies the email address that OneData sends notifications to when a job fails. For example: brooksrobinson@softwareag.com OneData Restart Required: No | |
onedata.notification.sendWelcomeMailOnUserCreation | |
Enables or disable the welcome email notification. Possible values are: true. Default. Enables the welcome email notification. false. Disables the welcome email notification. OneData Restart Required: No | |
onedata.quartz.explicit.connectionProvider.enable | |
Enables the quartz explicit connection provider. Possible values are: true. Default. false. OneData Restart Required: Yes | |
onedata.reports.enableRowFilter | |
Determines whether to apply the row filter defined for a user while generating the reports. Possible values are: true. Default. false. OneData Restart Required: No | |
onedata.support.email | |
Specifies the email address to use for OneData support, requesting a license, and other requests. For example: support@softwareag.com OneData Restart Required: Yes | |
onedata.transfermetadata.objectidentifer.enabled | |
Enables the object name identifier in metadata transfers. Possible values are: true. Default. false. OneData Restart Required: Yes | |
onedata.webservice.rest.enableFailOverFromTCToDB | |
Allows you to enable Terracotta failover to the database. Possible values are: true. Enable Terracotta failover to the database. If the Terracotta server is unavailable, then a REST GET call to retrieve data results is serviced from the database. If Terracotta server goes down in the midst of servicing the request, OneData reports an error. false. Default. When the Terracotta server goes down, a REST GET call to retrieve data results in an error. OneData Restart Required: No |
onedata.fileupload.invalidcharactersinfilename | |
Specifies the list of invalid characters blocked during file upload and download. The values are separated by #. Default values are ..#BACKWARD_SLASH#FORWARD_SLASH#SEMI_COLON#HASH. Possible values are: BACKWARD_SLASH. FORWARD_SLASH. SEMI_COLON. HASH. OneData Restart Required: No | |
onedata.keystore.dirpath | |
Specifies the directory where the keystore files (such as private key) are stored. If not specified, then OneData uses the config directory as the default path. For example: OneData_directory \profiles\ODE\bin\onedata\config. OneData Restart Required: Yes | |
onedata.ldapimport.batchsize | |
Specifies the number of rows to import in batch transactions. Default value is 100. OneData Restart Required: Yes | |
onedata.ldapimport.pooled | |
Specifies if LDAP import is pooled. Possible values are: true. Default. false. OneData Restart Required: Yes | |
onedata.ldapimport.poolsize | |
Specifies the size of the LDAP connection pool. Default value is 5. OneData Restart Required: Yes | |
onedata.pagelevelauthorizationcheck.enabled | |
Specifies if page level authorization is allowed. Page level authorization is implemented only for those pages set in the Menu toolbar, under Administer > Security. Possible values are: true. OneData verifies the user’s security permission before loading a page. false. Default. Disables page level authorization. OneData Restart Required: No | |
onedata.security.authentication.enhancedSLPassword | |
Determines if OneData uses the standard OneData password encryption mechanism or the industry-standard password encryption mechanism. Note: Software AG strongly recommends that you enable this property. Possible values are: true. Enables industry-standard password encryption mechanism. If you set this value, and you have upgraded from an older version of OneData where user-defined passwords for the service layer are stored in the database, users cannot use REST APIs with the old password. Users must reset their service layer password. false. Default. The service layer uses the user-defined password for access to the OneData user interface to authenticate the user accessing OneData through REST APIs. Note: Password for the service layer security is not available to administrators during their user management actions. It is visible only to the relevant user. OneData Restart Required: Yes | |
onedata.security.cacheControlDirective | |
Determines the usage of cache control directive in OneData. Possible values are: 0. OneData performs caching with revalidation. 1. Default. OneData uses no-cache, no-store, and must-revalidate as the cache control directive. In this case, browsers are not allowed to cache a response, and must pull the response from the server each time upon request. 2. OneData uses no cache control directive. Set this value to 2 only when browser specific issues exist. OneData Restart Required: Yes | |
onedata.security.csvinjection.blacklist | |
Specifies the list of characters to enclose in single quotes to restrict the CSV injection. Possible values are: +-@=. OneData Restart Required: No | |
onedata.security.ESAPI.isResponseEncodingEnabled | |
Enables ESAPI response encoding in the application. Possible values are: true. Default. false. OneData Restart Required: No | |
onedata.security.xxeprotectionoption | |
Disables external entities and external document type declarations or disables external entities (DTDs) completely to avoid an XML external entity attack. Possible values are: Disable_External_Entities_Only. Disables external entities and external document type declarations. Disable_External_Entities_And_DocTypes. Default. Disables DocTypes completely. Note: An XML External Entity attack against an application involves parsing an XML input containing a reference to an external entity. This attack may lead to the disclosure of confidential data. The safest way to prevent XXE is to disable DTDs (External Entities) completely. Disabling DTDs also makes the parser secure against denial of services (DOS) attacks such as Billion Laughs. If it is not possible to disable DTDs completely, then you must disable external entities and external document type declarations. OneData Restart Required: No | |
onedata.service.XSSValidationEnabled | |
Enables XSS validation at the repository level for all data imported or sent to through the OneData service layer. Possible values are: true. Default. Enables XSS validation at the repository level. false. Disables XSS validation at the repository level. The repository-level Python script, Repository Name _validate_input.py, performs the validation. For more information on the OneData Python script, see
Enforcing Data Validation. OneData Restart Required: No |
onedata.ipworks.sftpruntimelicense | |
Specifies the license string that is used in the SFTP library. The ipworks library uses this property to validate the run time license. onedata.ipworks.sftpruntimelicense=31484A38564 13153554252413153554243333841303931350000000000000000000000 000000000046474554593642450000445530364257425A42504D420000 OneData Restart Required: Yes | |
onedata.interchange execution.termination.threshold | |
Specifies the maximum number of errors that occur in a batch job before OneData aborts the import process. Default value is 10. For example: onedata.interchangeexecution.termination.threshold=10 | |
onedata.ipworks.smppruntimelicense | |
Specifies the license string that is used in the notification framework for SMPP, SNPP, or any other components in the ipworks.jar. The ipworks library uses this property to validate the run time license. onedata.ipworks.smppruntimelicense=3150 4A3856413153554252413153554243333841303931350000000000 0000000000000000000000464745545936424500004E50414E463 44843553155500000 OneData Restart Required: Yes | |
onedata.url.dynamic.encryption | |
Specifies if OneData disables dynamic encryption of the URL for OpenSTA testing. Possible values are: true. OneData disables dynamic encryption of the URL. onedata.url.dynamic.encryption=true false. OneData does not disable dynamic encryption of the URL. onedata.url.dynamic.encryption=false OneData Restart Required: Yes | |
onedata.pd4ml.fonts.dirpath | |
Specifies the directory path for fonts that OneData uses for PD4ML. onedata.pd4ml.fonts.dirpath=java:fonts OneData Restart Required: Yes | |
onedata.pd4ml.debug.enabled | |
Enables debugging for PD4ML (HTML to PDF converter for Java and .NET). Possible values are: true. Enables debugging for PD4ML. onedata.pd4ml.debug.enabled=true false. Disables debugging for PD4ML. onedata.pd4ml.debug.enabled=false OneData Restart Required: Yes | |
onedata.scheduler.quartz.duplicateexecutioncheck.enable | |
Stops multiple executions of the same jobs when the Quartz job scheduler triggers in OneData clusters. Possible values are: true. Before starting a OneData job, OneData checks if the job has already been triggered at the scheduled time. Once the job is triggered, OneData does not process other scheduled executions of the job. false. Default. OneData does not interfere with job schedules that the Quartz job scheduler sets up on the OneData cluster nodes. OneData Restart Required: Yes | |
onedata.dataquality.excludelogicallydeletedgoldrecordsfrommatchcandidatelist.enabled | |
Enables you to include or exclude logically deleted records from consolidation Gold tables in match candidates during the data quality matching process. Possible values are: true. Excludes logically deleted records in match candidates. Note: If you choose this value for the multiple Gold model, ensure that you include the FLD_DELETE column from the detail table in the view. false. Default. Includes logically deleted records in match candidates. OneData Restart Required: Yes | |
onedata.trillium.path | |
Specifies the directory path to Trillium. onedata.trillium.path=\\usr\\local\\lib\\bin OneData Restart Required: Yes | |
onedata.trillium.host | |
Specifies the Trillium host name. onedata.trillium.host=trillium.datafoundations.com OneData Restart Required: Yes | |
onedata.trillium.port | |
Specifies the Trillium port number. onedata.trillium.port=8888 OneData Restart Required: Yes | |
onedata.job.attachmentmaxrecordcount | |
Specifies the maximum number of records to include in a generated report when the report is sent as a file attachment. Any reports exceeding the value defined in this property cannot be sent as an attachment. Default value is 1000. onedata.job.attachmentmaxrecordcount=1000 OneData Restart Required: No | |
onedata.jcs.remotecache.lib | |
Specifies the library dependencies for the JCS remote cache server. These libraries should be in the webapp lib folder at runtime. Any changes in the actual jar filenames should also be updated here. Required libraries are jcs-1.3.jar, concurrent.jar, commons-logging.jar, and commons-lang-2.4.jar. Note: Do not change this parameter unless a library has been upgraded. onedata.jcs.remotecache.lib=jcs-1.3.jar,concurrent.jar,commons-logging.jar,commons-lang-2.4.jar OneData Restart Required: Yes | |
onedata.metamap.datafetchsize | |
Specifies the load size for metamap data. onedata.metamap.datafetchsize=100 OneData Restart Required: Yes | |
onedata.xslt.templates | |
Specifies the name of the XSLT templates. onedata.xslt.templates=ARIS Template OneData Restart Required: Yes | |
onedata.security.authentication.sso.type | |
Specifies the type of external authentication required with SSO. Possible case-sensitive values are: none pluggable_SSO for custom SSO SAML_SSO Kerberos_SSO onedata.security.authentication.sso.type=Kerberos_SSO OneData Restart Required: Yes | |
onedata.sso.userid.header | |
Specifies the key that OneData must use to get the username from the request header after external authentication is complete. OneData Restart Required: Yes | |
onedata.sso.logout.uri | |
Specifies the URL to which the user must be directed after logging out of OneData. onedata.sso.logout.uri=<SSO_LOGOUT_URL> OneData Restart Required: Yes | |
onedata.sso.impl.className | |
Specifies the fully qualified class name of the custom SSO (with external authentication) implementation class. onedata.sso.impl.className=[classname] OneData Restart Required: Yes | |
onedata.datamanager.displaygrid.wrapHeaderText | |
Wraps the header text in the display grid in Nova mode. Possible values are: onedata.datamanager.displaygrid.wrapHeaderText=true onedata.datamanager.displaygrid.wrapHeaderText=false. Default. | |
onedata.mdr.classificationschemeitem.conceptualobjectname | |
Specifies the name of the conceptual object for classification schema item. |
onedata.dnb.attributeprefix | |
onedata.dnb.companysearchattributemapping | |
onedata.netrics.loadbatchsize | |
onedata.netrics.enabled | |
onedata.netrics.matches | |
onedata.netrics.host | |
onedata.security.enableclientsidexfscheck | |
onedata.abac.externalrolesreader.class | |
Specifies the external class that contains details for external roles. | |
onedata.abac.externalrolesreader.configuration | |
Specifies whether the logic inside externalrolesreader can be implemented without recompiling the class (for example, external roles reading file path). Possible values are: onedata.abac.externalrolesreader.configuration=true onedata.abac.externalrolesreader.configuration=false | |
onedata.abac.databasefunctionname | |
Specifies whether the database function name checks for role privileges on column. onedata.abac.databasefunctionname=true onedata.abac.databasefunctionname=false | |
onedata.search.elasticsearch.ngram.filter.type | |
Specifies the Elasticsearch ngram tokenizer for the analyzer to use. Default value is nGram. onedata.search.elasticsearch.ngram.filter.type=nGram | |
onedata.search.elasticsearch.ngram.maxgram | |
Specifies the maximum ngram size. Default value is 8. You can modify this value, but it is not recommended. For details on Elasticsearch recommendations, see the Elasticsearch documentation. onedata.search.elasticsearch.ngram.maxgram=8 | |
onedata.search.elasticsearch.ngram.mingram | |
Specifies the minimum ngram size. Default value is 3. You can modify this value, but it is not recommended. For details on Elasticsearch recommendations, see the Elasticsearch documentation. onedata.search.elasticsearch.ngram.mingram=1 | |
onedata.search.elasticsearch.ngram.truncate.filter.type | |
Specifies the token filter for Elasticsearch analyzer. This allows the analyzer to break the search strings into specific lengths. Default value is truncate. onedata.search.elasticsearch.ngram.truncate.filter.type=truncate | |
onedata.search.elasticsearch.ngram.truncate.length | |
Specifies the length parameter for the token filter. This value defines the number of characters in the search string that the analyzer can truncate. Default value is 8. onedata.search.elasticsearch.ngram.truncate.length=8 |