If you have not yet installed IBMs IHS web server, use one of the following articles to install IBMs IHS web server. The admin server is included in the install.
After installating IHS, the <web_server_root>/conf/admin.conf file will have the following:
Listen @@AdminPort@@ User @@SetupadmUser@@ Group @@SetupadmGroup@@ ServerName localhost:@@AdminPort@@
You will need to update these lines to have a port, user, group, and server name. Typically, port 8008 is used. The netstat command can be used to ensure that port 8008 is not in use by some other service on the server.
netstat -an | grep 8008
Let's say you use "john.doe" and "web" for the user and group.
Listen 8008 User john.doe Group webgroup ServerName ihs.example.com:8008
Use the htpasswd command to create a password for john.doe.
Use the adminctl command to start the admin server.
You should now be able to use the admin server. There is no web interface for the admin server. If you navigate to http://hostname:8008/wasadmin, there will be a prompt for your username and password.
If the wasadmin page produces something like "page cannot be displayed", SSL may be enabled in admin.conf. You'll want to comment out the SSL directives in admin.conf and then restart the admin server so that you can access the admin server over HTTP.
#SSLEnable #SSLServerCert default #Keyfile "/path/to/keyfile.kdb"
When you provide your username and password, the following page will be displayed. This is normal, and not suggestive of a problem.
Likewise, the admin_access_log should have a 200 OK event, like this.
x.x.x.x - john.doe [14/Aug/201906:56:05 -0500] "GET /wasadmin HTTP/1.1" 200 91
If you want to be able to start or stop IHS from a WebSphere deployment manager, you will need to provide the admin server port and credentials when adding the web server to the dmgr.
You may want to also configure the admin server to automatically start when the system is rebooted.