In this recipe, we will learn how to get the JNDI tree view of your WildFly instances, by invoking a command to the CLI. This might be useful in case you need to check whether some application context exits, if you need to know a datasource JNDI name, or if you need to lookup for an EJB.
Remember I'm running WildFly remotely, bound to 192.168.59.103
as IP. WildFly is already up and running.
Open a new terminal window and execute the as following:
$ cd $WILDFLY_HOME $ ./bin/jboss-cli.sh -c --controller=192.168.59.103:9990 --user=wildfly --password=cookbook.2015 –command="/subsystem=naming:jndi-view" { "outcome" => "success", "result" => { "java: contexts" => { "java:" => {"TransactionManager" => { "class-name" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate", "value" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@16b89a30" ...