Skip to end of metadata
Go to start of metadata

Work in progress...

Make sure you have added the user using add-user.sh.

This is simple operation that is equivalent of running :read-resource with CLI in root directory

Here's an example of an operation on a resource with a nested address and passed paramters

this is same as if you would run /host=master/server=server-01:read-attribute(name=server-state)

Following example will get us information from http connection in web subsystem including run-time attributes

This is the same as running /subsystem=undertow/server=default-server/http-listener=default:read-resource(include-runtime=true) in CLI

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

3 Comments

comments.show.hide

  1. May 13, 2014

    Fai Gao

    It doesn't work with wildfly8,throws error 401.I'm sure username and password are right.

    [root@mdwarejboss2 ~]#  curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '

    Unknown macro: {"operation"}

    ' -u admin
    Enter host password for user 'admin':
    HTTP/1.1 401 Unauthorized
    Connection: keep-alive
    WWW-Authenticate: Digest realm="ManagementRealm",domain="/management",nonce="mwCBX1T55lMNMTM5OTk3MjEzNzIwMQ+1Ikugn3KqVjq/94wxq3M=",opaque="00000000000000000000000000000000",algorithm=MD5
    Content-Length: 77
    Content-Type: text/html
    Date: Tue, 13 May 2014 09:08:57 GMT

    <html><head><title>Error</title></head><body>401 - Unauthorized</body></html>

    

  2. Jul 14, 2015

    Eugeun Pomnikov

    Hi! How did you get this reponse?

    HTTP/1.1 200 OK
    Transfer-encoding: chunked
    Content-type: application/json
    Date: Tue, 17 Jul 2012 15:48:39 GMT

    {
    "outcome" : "success",
    "result" : {
    "bytesReceived" : "14727204",
    "bytesSent" : "2544228",
    "enable-lookups" : false,
    "enabled" : true,
    "errorCount" : "8",
    "executor" : null,
    "max-connections" : null,
    "max-post-size" : 2097152,
    "max-save-post-size" : 4096,
    "maxTime" : "1865",
    "name" : "http",
    "processingTime" : "12920",
    "protocol" : "HTTP/1.1",
    "proxy-name" : null,
    "proxy-port" : null,
    "redirect-port" : 8433,
    "requestCount" : "134",
    "scheme" : "http",
    "secure" : false,
    "socket-binding" : "http",
    "ssl" : null,
    "virtual-server" : null
    }
    }

    I am interested in proxy-name and proxy-port attributes because I need to setup wildfly behind reverse proxy and I haven't found yet where I can put these ones. I made the same request to my wildfly instance and got response without any proxy-* attributes.

    request
    response

    1. Jul 26, 2015

      Eugeun Pomnikov

      I finally found alternatives for proxy-name and proxy-port on the https://docs.jboss.org/author/display/WFLY8/Web+services+configuration. In general it is all you need but if you have an axis2 application (as I am) it won't work because of one has its own life.