Nav

To Inspect Input and Output (Design Center)

In this procedure, you inspect input and output payloads and attributes from the procedures you performed earlier to create a basic Mule app and to add an expression to make dynamic requests. You can also inspect variables and errors.

Input and output data is lost by any one of the following actions:

  • Reloading the Design Center browser

  • Making changes to a running app

  • Closing and opening a Design Center project

If you lost input and output data due to reloading the browser, you do not have to rerun the app. Just execute the flow to start the data flowing into the app. If you lost input and output data due to making changes to the app or closing and opening the project, rerun the app and re-exeute the flow as described in this procedure.

  1. Click Run.

  2. Re-execute the flow:

    • When the app is running, click options run app design env design center 2428b.

    • Click Copy Link.

    • Paste the link in a browser or client, and type /getpath?path=users at the end.

      The HTTP Listener hears the request, and starts the app. The JSON Placeholder profile of each user appears in the browser. The green status indicator appears in all parts of the flow.

  3. Open HTTP Request in myproject.

  4. In Input, in Show, select Attributes.

  5. In History, select an execution time. Attributes appear. For example:

    {
      "listenerPath": "/getpath",
      "relativePath": "/getpath",
      "version": "HTTP/1.1",
      "scheme": "http",
      "method": "GET",
      "requestUri": "/getpath?path=users",
      "queryString": "path=users",
      "remoteAddress": "/54.89.250.13:34894",
      "queryParams": {
        "path": "users"
      },
      "uriParams": {},
      "requestPath": "/getpath",
      "headers": {
        "host": "myproject-trod.stgx.cloudhub.io",
        "x-forwarded-port": "80",
        "accept-language": "en-US,en;q=0.8",
        "x-real-ip": "172.1.61.20",
        "accept-encoding": "gzip, deflate",
        "x-forwarded-for": "172.1.61.20",
        "upgrade-insecure-requests": "1",
        "user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36",
        "x-forwarded-proto": "http",
        "accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8"
      }
    }
    ...
  6. Select Output. The response attributes appear. For example:

    {
      "statusCode": 200,
      "reasonPhrase": "OK",
      "headers": {
        "set-cookie": "__cfduid=d2af63d4b5612974bb61977f6eacaefbb1504465208; expires=Mon, 03-Sep-18 19:00:08 GMT; path=/; domain=.typicode.com; HttpOnly",
        "x-content-type-options": "nosniff",
        "pragma": "no-cache",
        "connection": "keep-alive",
        "transfer-encoding": "chunked",
        "access-control-allow-credentials": "true",
        "via": "1.1 vegur",
        "expires": "Sun, 03 Sep 2017 23:00:08 GMT",
        "server": "cloudflare-nginx",
        "content-type": "application/json; charset=utf-8",
        "cache-control": "public, max-age=14400",
        "cf-ray": "398af342a6be0f33-IAD",
        "cf-cache-status": "HIT",
        "x-powered-by": "Express",
        "vary": "Origin, Accept-Encoding",
        "etag": "W/\"160d-1eMSsxeJRfnVLRBmYJSbCiJZ1qQ\"",
        "date": "Sun, 03 Sep 2017 19:00:08 GMT"
      }
    }
  7. In Show, select Payload. The todos list appears for the one execution and the users and posts lists appears for the other executions.

Now, you are ready to transform a full set of data to a subset.

In this topic: