Important Update: Cohesity Products Knowledge Base Articles


All Cohesity Knowledge Base Articles are now managed via the Cohesity Support Portal: https://support.cohesity.com/s/searchunify. The Knowledge Base articles available here will not reflect the latest information or may no longer be accessible.

NetBackup IT Analytics - How to change the Portal Domain URLs used for Portal access and Data Receiver / Data Collection

Article: 100045314
Last Published: 2025-02-05
Ratings: 0 0
Product(s): NetBackup IT Analytics, NetBackup

Description

This document describes how to change the NetBackup IT Analytics Portal Domain URLs used for Portal access and Data Receiver / Data Collection from (olddomain.com) to a new domain name (newdomain.com). 


Note: Make a backup of any files that needs to be edited.

1) Stop all NetBackup IT Analytics services: 

Unix: 
/opt/aptare/bin/aptare stop 

Windows: 

c:\opt\aptare\utils\stopallserverices.bat 


2) Update the URLs in the Apache VirtualHost stanza referenced in the httpd.conf file. 

/opt/apache/conf/httpd.conf 


Portal: 
<VirtualHost *> 
ServerName itanalyticsportal.olddomain.com 
ServerAlias itanalyticsportal itanalyticsportal.* 


Agent: 
<VirtualHost *> 
ServerName itanalyticsagent.olddomain.com 
ServerAlias itanalyticsagent itanalyticsagent.* 



Edit to 

Portal: 
<VirtualHost *> 
ServerName itanalyticsportal.newdomain.com 
ServerAlias itanalyticsportal itanalyticsportal.* 


Agent: 
<VirtualHost *> 
ServerName itanalyticsagent.newdomain.com 
ServerAlias itanalyticsagent itanalyticsagent.* 



3) Update the portal.properties file in the portalconf directory to reference the new URL: 

/opt/aptare/portalconf/portal.properties

Edit line:
portal.applicationUrl=http://itanalyticsportal.newdomain.com 


4) Update the collectorConfig.global.properties in the datarcvrconf directory to reference the new URL:

/opt/aptare/datarcvrconf/collectorConfig.global.properties 


This file contains the datarcvr URL – e.g. 
global_agentUrl=itanalyticsagent.newdomain.com 

This value is used when creating a new collector configuration file. It’s also inspected by the upgrader to try to determine what the URL prefix is if the upgrader was unable to determine this from the http.conf file (due e.g. to customization). 



5) Start the services. 

Unix: 
/opt/aptare/bin/aptare start 

Windows 
c:\opt\aptare\utils\startallserverices.bat


6) Manually update the LDAP user ID within the database: 

su - aptare
sqlplus portal/portal@scdb 

update ptl_user set LDAP_ID = 'admin@newdomain.com' where LDAP_ID = 'admin@olddomain.com';
commit;

exit
 

7) Modify the Super User password within the database: 

Unix: 
/opt/aptare/utils/updateUser.sh admin@newdomain.com <newpassword> 

Windows: 
c:\opt\aptare\utils\updateuser.bat admin@newdomain.com <newpassword> 

***Replace <newpassword> with a temporary password*** 

 

8) Log into the Portal Web UI with the new URL using the Super User account from Step 7 and you will be prompted to change the password again for security.


9) On the Data Collector servers, update the collector.properties file in the conf directory to reference the new URL. 

Unix:
/usr/openv/analyticscollector/mbs/conf/collector.properties


Windows: 
C:\Program Files\Veritas\AnalyticsCollector\mbs\conf\collector.properties


10) Restart data collector services:
 

Unix:
/usr/openv/analyticscollector/mbs/bin/aptare_agent restart

Windows: 
C:\Program Files\Veritas\AnalyticsCollector\mbs\bin\stopservice.bat
C:\Program Files\Veritas\AnalyticsCollector\mbs\bin\startservice.bat

 

Was this content helpful?