Next, we review the NAT Network card and identify the Subnet Address and DNS settings as shown in Figure 9.42:
Figure 9.42: The NAT Network card and the Subnet Address and DNS settings are viewed
We can now note down the Gateway IP address as shown in Figure 9.43:
Figure 9.43: The Gateway IP address is noted as 192.168.50.2 for vnnet8 used for the NAT network card
The IP address details are entered using IPv4 Manual configuration mode with the Enter index: 2 option and then the IPv6 configuration mode is set to Automatic with the Enter index: 1 option, the n option is used to exit from the menu as shown in Figure 9.44:
Figure 9.44: The IP address details are entered using IPv4 Manual configuration mode
Select an IPv4 configuration mode:
1: Automatic
2: Manual
Enter index: 2 (Manual)
This then shows the following prompts and our responses, as shown in Figure 9.44:
Enter the IPv4 address: (192.168.50.131)
Enter the IPv4 subnet mask: (255.255.255.0)
Enter the IPv4 default gateway: (192.168.50.2)
Select an IPv6 configuration mode:
1: Automatic
2: Manual
Enter index: 1 (Automatic)
Then we select n for the Next screen option. The time and time zone configuration are also left as the default shown in Figure 9.45:
Figure 9.45: The Time and Time zone configuration is left as the default We now see the Summary of the installation as shown in Figure 9.46:
Figure 9.46: The Summary of the installation is displayed and accepted
There are no DNS servers configured at this point in time (we are using the hosts file of the Windows 10 server).
I selected option: 1 (I used the windows hosts file)
On completion of the system configuration, the system displays the server’s name we gave, ECMUKDEMO77 as shown in Figure 9.47:
Figure 9.47: The System configuration is completed, and we now need to reboot it
We can type help as suggested to get a list of the administration commands available as illustrated in Figure 9.48:
Figure 9.48: The help command gives a list of the Administration commands available
Next, we type reboot as recommended in Figure 9.47 and confirm the reboot by typing in YES as shown in Figure 9.49:
Figure 9.49: The reboot command is entered and YES typed to confirm the reboot
After rebooting, we are prompted to login using the admin/filenet user and password we set during the configuration stage as shown in Figure 9.50:
Figure 9.50: The admin user and password are entered
In the Windows 10 server VMware host, we can check the IP address we set up and see we get a ping response as shown in Figure 9.51:
Figure 9.51: The new IBM Security Directory Services server is pinged
Edit the host windows server c:/windows/system32/drivers/etc/hosts file for ECMUKDEMO77 as shown in Figure 9.52:
Figure 9.52: The Windows 10 server host file is edited with the VMware Linux IP address
We can now launch the IBM Security Directory Service LDAP web application administration client as shown in Figure 9.53:
Figure 9.53: The IBM LDAP administration web application client is loaded using https://ecmukdemo77
After clicking on the Advanced command button shown in Figure 9.53, we see the prompt window pop-up as shown in Figure 9.54
Figure 9.54: The Accept the Risk and Continue pop-up window is displayed by the FireFox web browser
The IBM Security Director Suite login pop-up window is as shown in Figure 9.55:
Figure 9.55: The login window for IBM Security Directory Suite is shown
We can now log into the IBM Security Directory Suite administration web page as shown in Figure 9.56:
Figure 9.56: The IBM Security Directory Suite administration web page
The detail of the web page showing the version (8.0.1.18) and disk space usage is shown in Figure 9.57:
Figure 9.57: The detail of the web page showing the Version (8.0.1.18) and Disk space usage
The Server components are started, and the LDAP Directory Server Web Administration Tool link can be selected to load the LDAP User and Group configuration web pages as highlighted in Figure 9.58:
Figure 9.58: The LDAP Directory Server Web Administration Tool link can be selected as highlighted
The login to console admin is displayed as shown in Figure 9.59:
Note: For the first-time login we have to use the superadmin/secret, user/password combination required for the initial configuration as shown in Figure 9.59.
Figure 9.59: The Login to console admin is displayedThe installed Server LDAP web application administration web page is displayed as show in Figure 9.60:
Figure 9.60: The installed Server LDAP web application administration web page is displayed
