Portal Customizations
This section covers customizations for the portal that are not available through the user interface. Use Custom Parameters to add/edit and delete these properties.
Configuring Global Default Inventory Object Selection
To globally configure the selection of default Inventory objects for users, modify the portal.properties files. This is useful for filtering environments with large volumes of data that may be impacted by browser limitations. For new users who have never logged into the portal, the objects defined with this setting are shown selected when they log in. For existing users, this property can be used to reset a users environment when large volumes of data can present issues with certain browsers.
• Use the following:
portal.ocn.defaultVisibleObjectType=HOST,ARRAY,SWITCH,BACKUPSERVER,VM_SERVER,VM_GUEST,
DEDUPLICATION_APPLIANCE,DATASTORE,EC2_INSTANCE,S3_BUCKET,AZURE_STORAGE_ACCOUNT,
AZURE_VIRTUAL_MACHINE
Restricting User IDs to Single Sessions
To restrict a user ID from signing on multiple times using different browsers on the same machine or the same browser on different machines, modify the portal.properties file. The last browser session with the user ID to login will have access to the portal. Other browser sessions with same user ID will be logged out.
• Use the following:
portal.security.allowUserToLoginMultipleTimes=false
Customizing Date Format in the Report Scope Selector
To customize the date format displayed in the report scope selector for all Portal users, you can modify the portal.properties file. For example, you can set the date to display: dd/MM/yyyy or MM/dd/yyyy
• Use the following:
#Formatters that define specific presentations of numbers and dates
formatter.decimalPlaces=2
fileSize.base2=true
formatter.number=###,###,##0
formatter.date=MMM dd, yyyy hh:mm:ssa
formatter.dateZone=MMM dd, yyyy hh:mm:ssa z
formatter.yearMonth=MMM dd
formatter.groupByDate=MMM dd
formatter.designerDate=MM/dd/yyyy
formatter.currency=$ ###,###,##0.00
Customizing the Maximum Number of Lines for Exported Reports
When you export or email a large report, APTARE IT Analytics limits the maximum number of lines to 20,000. The report truncates when that value is exceeded. The report can still be exported or emailed, but will contain a message that the report has been truncated.
• Use the following:
portal.report.maxRowsExported=<enter new limit value here>
Where the <new limit value> is the number of rows greater than 20,000 that your report export requires. For example, if your report has 36,000 rows enter a number greater than 36000. Note that the new limit value cannot contain commas or decimal points. Keep in mind that Portal server performance can degrade considerably for very large reports. For very large reports, you may want to segment the scope into multiple reports.
Customizing the Total Label Display in Tabular Reports
To customize the minimum number of records needed to display the Total label in a report, you can modify the portal.properties file. The default value is 10.
• Use the following:
portal.rowCountDisplayMinimum = <enter numeric value>
Customizing the Host Management Page Size
In the Portal, the Host Management page (Admin > Advanced > Host Management) displays 200 rows by default. You can change the default value by modifying the portal.properties file. System performance will be impacted if you increase the number of rows past the 200 value.
• Use the following:
portal.hostManagementPageSize=xxxx
Customizing the Path and Directory for File Analytics Database
You can customize the location of the File Analytics database. The default paths are:
• Linux: /opt/aptare/fa
• Windows: C:\opt\aptare\fa
Use the following to revise the path:
fa.root=/opt/aptare/fa
For example:
Linux:
fa.root=/opt/aptare/fa_db
Windows:
fa.root= D:\opt\aptare\fa
Configuring Badge Expiration
Configure the expiration of NEW badges in the Home section of the Reports tab. By default, NEW badges will no longer display after 14 days.
• Use the following:
cloudTemplateNewBadgeExpireInDays = 14
Configuring the Maximum Cache Size in Memory
The cache can retain up to 0.5 GB of reporting data and if it reaches capacity, it frees up space for new reports by purging the data for the least frequently used reports.
• Use the following:
portal.reports.cache.maxSizeInMemory
The unit of measure for the cache maxSizeInMemory value is bytes.
Example: portal.reports.cache.maxSizeInMemory=536870912
Configuring the Cache Time for Reports
The cache retains reporting data and if it reaches capacity, it frees up space for new reports by purging the data for the least frequently used reports. Purging also occurs when a cached report is more than 24 hours old.
6. Use the following:
portal.reports.cache.timeOut
The unit of measure for the cache timeOut value is seconds.
Example: portal.reports.cache.timeOut=86400