APTARE IT Analytics System Administrator Guide
- Preparing for updates
- Backing up and restoring data
- Monitoring APTARE IT Analytics
- Accessing APTARE reports with the REST API
- Defining NetBackup estimated tape capacity
- Automating host group management
- Categorize host operating systems by platform and version
- Bulk load utilities
- Automating NetBackup utilities
- Attribute management
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the portal
- Host discovery: EMC Avamar
- 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
- Portal and data collector log files - reduce logging
- Data collector log file naming conventions
- Portal log files
- Defining report metrics
- SNMP trap alerting
- SSL certificate configuration
- Configure virtual hosts for portal and / or data collection SSL
- Keystore on the portal server
- Portal properties: Format and portal customizations
- Advanced configuration for NetBackup discovery
- Data retention periods for SDK database objects
- Configure multi-tenancy data purging retention periods
- Troubleshooting
Configuring Oracle passwords in system configuration files
Once you've made the change in Oracle, changes must be made in two files: datrarcvrproperties.xml and portal.properties.
Revise the credentials using the portal.properties file:
Linux:
/opt/aptare/portalconf/portal.properties
Windows:
C:\opt\aptare\portalconf\portal.properties
Modify the following lines (for the Database User ID):
db.user=portal(preset value) db.password=portal db.password.encrypted=
Modify the following lines (for the System DBA):
db.sysdba_user=system (preset value) db.sysdba_password= db.sysdba_password.encrypted=
Note:
For encryption, the system completes the part after the "=" sign and removes the clear text password entry once Tomcat portal services are restarted.
Revise the credentials using the datrarcvrproperties.xml file:
Linux:
/opt/aptare/datarcvrconf/datrarcvrproperties.xml
Windows:
C:\opt\aptare\datarcvrconf\datrarcvrproperties.xml
Add the following lines (for the Database User ID):
db.user=portal(preset value) db.password=portal db.password.encrypted=
Add the following lines (for the System DBA):
<sysdba_user>system</sysdba_user> <sysdba_password>new_password</sysdba_password> <oracle_service_name>SCDB</oracle_service_name>
Restart the portal and data receiver Tomcat services.
Note:
When the Tomcat service is restarted, credentials will be replaced with the encrypted string, so it's important to make note of the original values.
For example:
<db.user>Tij0nQG/IWdtAjwPmFX8xw==</db.user> <db.password>hs47wbzenhnzTgI0JP62kw==</db.password> and
For example:
<sysdba_user>Tij0nQG/IWdtAjwPmFX8xw==</sysdba_user> <sysdba_password>hs47wbzenhnzTgI0JP62kw==</sysdba_password> <oracle_service_name>SCDB</oracle_service_name>