After restarting the AdminUI, even though the process is getting started, the AdminUI is inaccessible. Re-registering the AdminUI has no effect. The server.log shows the following lines at the start time:

  2018-02-22 11:34:10,315 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final

  2018-02-22 11:34:10,475 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
  
  2018-02-22 11:34:10,544 INFO  [org.jboss.as] (MSC service thread 1-3) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
  
  2018-02-22 11:34:11,883 INFO  [org.jboss.as.controller.management-deprecated]
  (Controller Boot Thread) JBAS014627: Attribute any-ipv4-address is deprecated, and it might be removed in future version!
  
  2018-02-22 11:34:11,930 INFO  [org.jboss.as.server.deployment.scanner]
  (DeploymentScanner-threads - 1) JBAS015003: Found castylesr5.1.1.ear in deployment directory. To trigger deployment create a file called castylesr5.1.1.ear.dodeploy
  
  2018-02-22 11:34:11,930 INFO  [org.jboss.as.server.deployment.scanner]
  (DeploymentScanner-threads - 1) JBAS015003: Found iam_siteminder.ear in deployment directory. To trigger deployment create a file called iam_siteminder.ear.dodeploy
  
  2018-02-22 11:34:11,936 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

  [...omitted for brevity...]

  2018-02-22 11:34:14,294 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 49)
  JBAS011601: Bound messaging object to jndi name jms/wpConnectionFactory
  
  2018-02-22 11:34:14,362 INFO  [org.jboss.as] (Controller Boot Thread)
  JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
  
  2018-02-22 11:34:14,362 INFO  [org.jboss.as] (Controller Boot Thread)
  JBAS015954: Admin console is not enabled
  
  2018-02-22 11:34:14,362 INFO  [org.jboss.as] (Controller Boot Thread)
  JBAS015874: WildFly 8.2.0.Final "Tweek" started in 4296ms - Started 248 of 302 services
  (104 services are lazy, passive or on-demand)

No line such as the following ones can be seen:

  2022-04-12 08:49:45,269 INFO  [ims.Main] (ServerService Thread Pool -- 86)
  ---- CA IAM FW Startup Sequence Initiated. ----

  2022-04-12 08:49:45,275 INFO  [ims.Main] (ServerService Thread Pool -- 86) *
  Startup Step 1 : Attempting to start ServiceLocator. 

  2022-04-12 08:49:47,469 INFO  [ims.Main] (ServerService Thread Pool -- 86) *
  Startup Step 2 : Attempting to start PolicyServerService

  2022-04-12 08:49:47,520 INFO  [ims.Main] (ServerService Thread Pool -- 86) *
  Startup Step 3 : Attempting to start ServerCommandService

  2022-04-12 08:49:47,631 INFO  [ims.Main] (ServerService Thread Pool -- 86) *
  Startup Step 4 : Attempting to start EnvironmentService

 

AdminUI all versions

This can happen when JBoss cannot deploy the ear files needed due to not having enough permissions on the files. First, check if under your /siteminder/adminui/standalone/deployments folder you have the following files along with the .ear files:

  iam_siteminder.ear
  castylesr5.1.1.ear
  iam_siteminder.ear.undeployed 
  castylesr5.1.1.ear.undeployed

Having them means the JBoss scanner could not deploy them before, so stop AdminUI and ensure the user running AdminUI has enough permissions (W/R) over all the standalone folder trees. Then, remove the .undeployed files, leaving only the .ear files in the folder:

  castylesr5.1.1.ear
  iam_siteminder.ear

And then, create the following files (use the "touch" command for this) to indicate to the JBoss scanner to deploy them:

  # touch castylesr5.1.1.ear.dodeploy
  # touch iam_siteminder.ear.dodeploy

So, in the folder, the following files along with the readme one will be seen: castylesr5.1.1.ear:

  iam_siteminder.ear
  iam_siteminder.ear.dodeploy
  castylesr5.1.1.ear.dodeploy

When starting the AdminUI standalone next time, it will try to deploy them again, and the logs should show that with the following entries:

  2018-02-23 10:49:24,265 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "iam_siteminder.ear" (runtime-name: "iam_siteminder.ear") 
  2018-02-23 10:49:24,267 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "castylesr5.1.1.ear" (runtime-name: "castylesr5.1.1.ear")

After that, AdminUI will start properly, and the extension of the files we created in the deployments folder will change from .dodeploy to .deployed to indicate the scanner that, and you are now able to access through the normal URL or to complete the registration process.