How to automate the Installation of NetIQ Access Manager using Ansible

How to automate the Installation of NetIQ Access Manager using Ansible

1. Introduction:

This article discusses about how to Install Access Manager. For the current scenario we are considering the Installation of NetIQ Access Manager from 4.5. 

2. Abbreviations:

  • NAM: NetIQ Access Manager
  • AC: Admin Console
  • IDP: Identity Server
  • AG: Access Gateway

3. Pre-requisites:

        a. Ansible version 2.7 or above. (For more info refer:   https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html).

For checking the current Ansible version, run the following command in the terminal of the host machines:

            ansible --version

Ansible_version.png

 

Fig 1: Checking the Ansible version.

      bFor this scenario, we are considering Linux based client and hosts with python version 2.7.10 or above installed on them.

      c. Download the auto-install.zip and extract it into the /etc/ansible (Warning: If the auto-upgrade.zip is directly extracted into the /etc/ansible folder It will overwrite the existing file in that folder.)

      d.  For the current scenario, we are considering setup with oneAdmin Consoles (AC), oneIdentity Servers (IDP) and oneAccess Gateways (AG), all running on individual Linux based systems with required Repositories configured.(For list of supported OS, required repositories and RPM’s refer the following link).

      e.  Enter the IP Addresses of the AC, IDP and AG in the Hosts file as follows.

 

 hostfilesyntax.png

 

Fig 2: Syntax of the HOSTS file.

hostfilewithentries.png

 Fig 3: Example of entries in the HOSTS file.

     f.  The credentials for the Admin Console are Assumed to be

           Username: admin

           Password: novell

           If using other credentials, make the changes in the following roles:

  • /etc/ansible/roles/ac.install/tasks/main.yml
  • /etc/ansible/roles/idp.install/tasks/main.yml
  • /etc/ansible/roles/ag.install/tasks/main.yml

usernameanddownloadlocation.png

Fig 5: The underlined text shows the location of the build on the web server and the credentials.

     g.  We are downloading the installer from our local servers, if using some other location for downloading the build, then specify that specific location in the files mentioned in prerequisites h, as shown in Fig 5.

    h All the hosts should be accessible through the client machine using SSH.

4. Steps to run the Automation :

  1. Run the playbook ( main.yml ) to install NAM 4.5.0,
    for doing so execute the following command:

           ansible-playbook main.yml -e “build_version=4.5”

           And wait for the process to complete.

Output:

sampleoutputinstall.png

 Fig 7: Sample Output

5. Checking the version of the components:

  1. Log in to the Admin Console with your credentials, and click on Troubleshooting.
    clicktrblshooting.png
    Fig 8: Click on Troubleshooting in the Admin Console.
  2. On the Troubleshooting page click on the version tab.Untitledclick_version.jpg

    Fig 9: Click on Version on the troubleshooting page.

  3. The displayed page will have information about the versions of all the components.
    version450.png  

Fig 10: Version Details of all the components.

Labels (1)
Attachments

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Comments

Coincidentally, I was starting to investigate ansible to install Identity Governance.

 

I would like to take inspiration in your script, but it seems like the attached file is empty.

Thank you @msira for letting us know about the empty attachment.

The attachment has been updated now, you can have a look at it and let us know if it has some other issues.

 

Top Contributors
Version history
Revision #:
5 of 5
Last update:
‎2019-08-20 06:01
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.