Data Governance Administrator Guide > Configuring Axon > Configure Access to Data Privacy Management
  

Configure Access to Data Privacy Management

If you selected the advanced configuration option during Axon installation, you would have entered the configuration settings for Data Privacy Management. If you did not select advanced configuration during Axon installation or if you want to update the connection settings for Data Privacy Management after the installation, go to the Axon Admin Panel.
You must have the Super Admin profile to perform this task.
    1. From the Axon toolbar, click the Admin Panel menu item under your user name.
    2. In the menu on the left, under the Customize & Configure category, click System Settings.
    3. In the Group list, select Data Privacy Management.
    4. Click Edit, and configure the following properties:
    Property
    Description
    Data Privacy Management Server Host
    URL of the Data Privacy Management service in the following format: http(s)://<host_name> or http(s)://<IP_address>
    Data Privacy Management Server Port
    Port number of the Data Privacy Management service
    Data Privacy Management Server Login User Name
    User name to log in to the Data Privacy Management server
    Data Privacy Management Server Login Password
    Password to log in to the Data Privacy Management server
    Data Privacy Management Server Login Namespace
    User security domain of Data Privacy Management
    5. Click Save.
    6. In the Linux environment, run the following command to clear the Axon cache and restart the necessary services:
    sh <INSTALLATION_DIR>/axonhome/third-party-app/scripts/paramsync
    When you run the paramsync script, Axon restarts the HTTPD, Memcached, and email notification services.
Note: When you clear the cache and restart the Axon services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the System Settings pages. Additionally, perform this action during a maintenance period when very few users are using Axon.