Settings that apply to this tenant overall are found here in the ‘Tenant Settings’ page.
You can modify the settings of a specific task instead of the overall tenant using task level settings, or you can change the settings for all tasks that use a particular agent using agent level settings.
Each setting for the tenant is listed on this page. Each setting you change will be applied to the entire tenant, unless you have individually modified the settings of a specific task or agent.
You can change any of the following settings and then click Save Changes at the top right to save your updated settings.
|Tenant Setting||Data Type||Description|
|Azure Batch Pool Expiry||Minutes||This setting controls how long the Azure Batch task will wait in minutes before attempting to remove the Azure Batch Pool upon completion of the task.|
|Bulk Copy Batch Size||Number of rows||This setting determines the number of rows to be committed per batch in the Data Migration task.|
|Bulk Copy Timeout||Seconds||This setting controls the timeout value in seconds for data migrations, SQL statements and Stored Procedures for SQL tasks. Set the value to 0 to have the task wait indefinitely.|
|Culture Info||CultureInfo||Loome Integrate uses this value for the culture info setting. This setting identifies the country from where Loome Integrate is used.|
|Flat File Detect Data Type Max Row||Number of rows||This setting controls how many rows will be read in a flat file to detect column lengths. Increase this value if you are having problems with truncation. Set this value to 0 to use max column lengths.|
|Job Dependency Wait Secs||Seconds||The number of seconds to wait before checking if a dependent job has completed.|
|Task Timeout Minutes||Minutes||This is the number of minutes that the service will wait before a task is considered to be timed out. The service will set jobs that have timed out to the status ‘Failure’.|
|Bulk Copy Enable Streaming||Toggle on/off||This setting will improve performance when moving large blobs in a Data Migration task.|
|Instant Switch Migration||Toggle on/off||Loads data in to a table in a separate schema, upon successful completion of the data migration, the table will be switched with the original table. This allows for near complete uptime of a table. This only applies to SQL target connections.|
Instant Switch Migration is used in a data migration task. It will load data into a table in a separate schema, upon successful completion of the data migration, the table will be switched with the original table. This allows for near complete uptime of a table. This only applies to SQL Server target connections.
The Instant Switch Migration is in tenant settings and is set to be false by default.
You can enable it here to turn it on at the tenant level or you can enable it in the task level settings or agent level settings to override the tenant settings.
You can change your tenant name on this ‘Manage Tenant’ page.
Type in the new name that will identify this tenant, and click Save Change.
There are currently five levels of user access. These roles can be assigned and edited by Admin.
BI User: Can view reports and data currency.
BI Manager: Can execute and view history for jobs.
BI Developer: Can manage content assigned to a Department. This Role has full access to all site content for the department. Users assigned as BI Developer can also deploy Jobs.
Group Admin: Manages Projects and Users. This Role has full access to all site content.
Similarly to adding new users, to edit current user roles, select Manage Tenant from the dropdown menu in the top right corner.
Next, select Manage Users from the tabs on the left.
Click on the dropdown arrow next to the user role of your chosen user.
You can learn more about the access of each role using the list above.
Click Update to confirm the changes.