Thanks Zen.
I tried to follow that article, and created 2 files iam_siteminder.ear.dodeploy and castylesr5.1.1.ear.dodeploy in the deployment directory. I just made them using touch, hence they are 0 Kb files.
however after the restart, its failing with below message in the server.log:
it looks like it is searching for other .dodeploy files corresponding to the other ear files in iam_siteminder.ear.
2019-04-22 12:12:06,346 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found iam_siteminder_identityminder_ejb.jar in deployment directory. To trigger deployment create a file called iam_siteminder_identityminder_ejb.jar.dodeploy
2019-04-22 12:12:06,346 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found management_console.war in deployment directory. To trigger deployment create a file called management_console.war.dodeploy
2019-04-22 12:12:06,346 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found user_console.war in deployment directory. To trigger deployment create a file called user_console.war.dodeploy
2019-04-22 12:12:06,346 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found sso-restapi-services.war in deployment directory. To trigger deployment create a file called sso-restapi-services.war.dodeploy
2019-04-22 12:12:06,346 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found workflow.rar in deployment directory. To trigger deployment create a file called workflow.rar.dodeploy
2019-04-22 12:12:06,346 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
2019-04-22 12:12:06,346 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
2019-04-22 12:12:06,346 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found iam_siteminder_wpServer.jar in deployment directory. To trigger deployment create a file called iam_siteminder_wpServer.jar.dodeploy
2019-04-22 12:12:06,346 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found api-doc.war in deployment directory. To trigger deployment create a file called api-doc.war.dodeploy
2019-04-22 12:12:06,346 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found policyserver.rar in deployment directory. To trigger deployment create a file called policyserver.rar.dodeploy
2019-04-22 12:12:06,346 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found sso-security-services.war in deployment directory. To trigger deployment create a file called sso-security-services.war.dodeploy
2019-04-22 12:12:06,346 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015010: The deployment scanner found a directory named META-INF that was not inside a directory whose name ends with .ear, .jar, .rar, .sar or .war. This is likely the result of unzipping an archive directly inside the /apps/CA/siteminder/adminui/standalone/deployments directory, which is a user error. The META-INF directory will not be scanned for deployments, but it is possible that the scanner may find other files from the unzipped archive and attempt to deploy them, leading to errors.
2019-04-22 12:12:06,377 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 18) JBAS014613: Operation ("add") failed - address: ([("deployment" => "smjavasdk2.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"smjavasdk2.jar\")]"
2019-04-22 12:12:06,381 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "JBAS014784: Failed executing subsystem deployment-scanner boot operations"