APTARE IT Analytics System Administrator Guide
- Preparing for updates
- Backing up and restoring data
- Best practices for disaster recovery
- Oracle database backups
- File system backups
- Oracle database: Cold backup
- Oracle database: Export backups
- Scheduling the oracle database export
- Oracle database: On demand backup
- Restoring the APTARE IT Analytics system
- Import the oracle database
- Manual steps for database import / export using data pump
- Monitoring APTARE IT Analytics
- Accessing APTARE reports with the REST API
- Defining NetBackup estimated tape capacity
- Automating host group management
- About automating host group management
- Task overview: managing host groups in bulk
- Preparing to use PL/SQL utilities
- General utilities
- Categorize host operating systems by platform and version
- Identifying a host group ID
- Move or copy clients
- Organize clients by attribute
- Move host group
- Delete host group
- Move hosts and remove host groups
- Organize clients into groups by backup server
- Merge duplicate backup clients
- Bulk load utilities
- Veritas NetBackup utilities
- Automating NetBackup utilities
- Organize clients into groups by management server
- Set up an inactive clients group
- Set up a host group for clients in inactive policies
- Set up clients by policy
- Set up clients by policy type
- IBM Tivoli storage manager utilities
- Set up clients by policy domain
- Set up clients by IBM Tivoli storage manager instance
- Scheduling utilities to run automatically
- Example--Scheduling Utilities to Run Automatically
- Sample .sql file (setup_ora_job.sql) to set up an automatic job
- Attribute management
- Attribute bulk load utilities
- Attribute naming rules
- Rename attributes before upgrading
- Load host attributes and values
- Load attributes and values and assign to hosts
- Load array attributes and values and assign to arrays
- Overview of application attributes and values
- Load application database attributes and values
- Load MS Exchange organization attributes and values
- Load LUN attributes and values
- Load switch attributes and values
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the portal
- System configuration in the portal
- System configuration: functions
- Navigation overview
- System configuration parameter descriptions: Additional info
- Data collection: Capacity chargeback
- Database administration: database
- Host discovery: EMC Avamar
- Host discovery: Host
- Custom parameters
- Adding/editing a custom parameter
- Portal customizations
- Configuring global default inventory object selection
- Restricting user IDs to single sessions
- Customizing date format in the report scope selector
- Customizing the maximum number of lines for exported reports
- Customizing the total label display in tabular reports
- Customizing the host management page size
- Customizing the path and directory for File Analytics database
- Configuring badge expiration
- Configuring the maximum cache size in memory
- Configuring the cache time for reports
- Performance profile schedule customization
- Configuring AD/LDAP
- Configuring single sign-on (SSO) using security assertion markup language (SAML)
- Changing Oracle database user passwords
- Integrating with CyberArk
- Tuning APTARE IT Analytics
- Working with log files
- About debugging APTARE IT Analytics
- Turn on debugging
- Database logging
- Portal and data collector log files - reduce logging
- Database SCON logging - reduce logging
- Refreshing the database SCON log
- Logging user activity in audit.log
- Logging only what a user deletes
- Logging all user activity
- Data collector log files
- Data collector log file organization
- Data collector log file naming conventions
- General data collector log files
- Find the event / meta collector ID
- Portal log files
- Database log files
- Installation / Upgrade log files
- Defining report metrics
- SNMP trap alerting
- SSL certificate configuration
- SSL certificate configuration
- SSL implementation overview
- Obtain an SSL certificate
- Update the web server configuration to enable SSL
- Configure virtual hosts for portal and / or data collection SSL
- Enable / Disable SSL for a Data Collector
- Enable / Disable SSL for emailed reports
- Test and troubleshoot SSL configurations
- Create a self-signed SSL certificate
- Configure the Data Collector to trust the certificate
- Keystore file locations on the Data Collector server
- Import a certificate into the Data Collector Java keystore
- Keystore on the portal server
- Add a virtual interface to a Linux server
- Add a virtual / secondary IP address on Windows
- Portal properties: Format and portal customizations
- Introduction
- Configuring global default inventory object selection
- Restricting user IDs to single sessions
- Customizing date format in the report scope selector
- Customizing the maximum number of lines for exported reports
- Customizing the total label display in tabular reports
- Customizing the host management page size
- Customizing the path and directory for file analytics database
- Configuring badge expiration
- Configuring the maximum cache size in memory
- Configuring the cache time for reports
- Configuring LDAP to use active directory (AD) for user group privileges
- Advanced configuration for NetBackup discovery
- Data retention periods for SDK database objects
- Data retention periods for SDK database objects
- Find the domain ID and database table names
- Retention period update for SDK user-defined objects example
- SDK user-defined database objects
- Capacity: default retention for basic database tables
- Capacity: default retention for EMC Symmetrix enhanced performance
- Capacity: Default retention for EMC XtremIO
- Capacity: Default retention for Dell EMC Elastic Cloud Storage (ECS)
- Capacity: Default retention for Windows file server
- Capacity: Default retention for Pure Storage FlashArray
- Cloud: Default retention for Amazon Web Services (AWS)
- Cloud: Default retention for Microsoft Azure
- Cloud: Default retention for OpenStack Ceilometer
- Configure multi-tenancy data purging retention periods
- Troubleshooting
Setting up the portal to integrate with CyberArk
Setting up the Portal to work with CyberArk requires a properties file with specific values and executing a script to enable the feature. Most values required in the properties file are derived from entries in the CyberArk application. There are two steps to setup the portal; Setting up properties and running the utility.
Set Up the Properties File on the APTARE IT Analytics Portal
- Create a properties file in the tmp directory. For example:
/tmp/dbvaultconnection.properties or C:\tmp\dbvaultconnection.properties
- Configure the properties file with the following information:
Field Name
Value
vault_vendor_name
CyberArk
Note:
Use only CyberArk as a value in this field.
host
IP Address or hostname of the machine where Agentless AAM(Central Credential Provider) web service is running.
port
port # of Agentless AAM(Central Credential Provider) web service.
https
Set this value to true if Agentless AAM(Central Credential Provider) is running as https service otherwise false
schedule_frequency
The value of this field is in hours. Defines the frequency that APTARE IT Analytics will poll CyberArk for password updates. This field is optional. The default is every hour.
app_id
Name/ID of the application as defined in CyberArk. For example: APTARE IT Analytics.
user_safe_id
Name of the CyberArk Safe, where 'Portal' user account password is stored.
user_password_folder_name
Name of the CyberArk folder, where the 'Portal' user account password is stored. This field is optional.
user_password_object
Name of the 'Portal' user account password object in CyberArk
For each user account repeat the following. This sample describes the aptare_ro user.
ro_safe_id
Name of the CyberArk Safe, where 'aptare_ro' user account password is stored.
ro_password_folder_name
Name of the CyberArk folder where the 'aptare_ro' user account password is stored. This field is optional.
ro_password_object
Name of the 'aptare_ro' user account password object in CyberArk
Sample of dbvaultconnection.properties containing 'portal' user account configured: vault_vendor_name=CyberArk host=10.x.x.x port=443 https=true schedule_frequency=2 app_id=testappid user_safe_id=safe1 user_password_object=portal_account Sample of dbvaultconnection.properties" containing all the users account configured: vault_vendor_name=CyberArk host=10.x.x.x port=443 https=true schedule_frequency=2 app_id=testappid user_safe_id=safe1 user_password_object=portal_account ro_safe_id=safe2 ro_password_object=ro_account
Run the Utility to enable the CyberArk Integration.
- Navigate to the OS-specific utility on the Portal.
<APTARE_HOME>/utils/configure-db-vault-connection-info.sh
<APTARE_HOME/utils/configure-db-vault-connection-info.bat
- Execute the utility as a root/tomcat user.
On Linux:
<APTARE_HOME>/utils/configure-db-vault-connection-info.sh /tmp/dbvaultconnection.properties
On Windows
<APTARE_HOME>/utils/configure-db-vault-connection-info.bat
/tmp/dbvaultconnection.properties
The utility validates the connection parameter by invoking the REST API for each user configured in the properties file. If the validation is successful, the properties file is copied to the <HOME>/datarcvrconf/passwordvault/ folder. If the validation fails, a message is displayed and the CyberArk integration is not enabled.
- If required, navigate to the log file to troubleshoot further:
<APTARE_HOME>\logs\passwordVaultValidator.log