Using the Management API

The Management API of WSO2 Micro Integrator is an internal REST API, which was introduced to substitute the admin services that were available in WSO2 EI 6.x.x.

The Micro Integrator CLI and the Micro Integrator dashboard communicates with this service to obtain administrative information of the server instance and to perform various administration tasks. If you are not using the dashboard or the CLI, you can directly access the resources of the management API by following the instructions given below.

Securely invoking the API

The management API is secured using JWT authentication by default. Therefore, when you directly access the management API, you must first acquire a JWT token with your valid username and password.

Tip

See Securing the Management API for information on configuring users, JWT authentication, and other security options for the management API.

Getting a JWT token

Follow the steps given below to acquire the JWT token.

  1. First, encode your username:password in Basic Auth format (encoded in base64). For example, use the default admin:admin credentials.
  2. Invoke the /login resource of the API with your encoded credintials as shown below. 
    curl -X GET "https://localhost:9164/management/login" -H "accept: application/json" -H "Authorization: Basic YWRtaW46YWRtaW4=" -k -i
  3. The API will validate the authorization header and provide a response with the JWT token as follows: 
    {
   "AccessToken":"%AccessToken%"
}

Invoking an API resource

You can now use this token when you invoke a resource.

Info

When the default JWT security handler is engaged, all the management API resources except /login is protected by JWT auth. Therefore, it is necessary to send the token as a bearer token when invoking the API resources.

curl -X GET "https://localhost:9164/management/inbound-endpoints" -H "accept: application/json" -H "Authorization: Bearer %AccessToken%”

Log out from management API

Invoke the /logout resource to revoke the JWT token you used for invoking the api resource.

curl -X GET "https://localhost:9164/management/logout" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i

Accessing API resources

The management API has multiple resources to provide information regarding the deployed artifacts as well as the server itself.

GET USERS

  • Resource: /users

    Description: Retrieves a list of all users stored in an external user store.

    Example:

    curl -X GET "https://localhost:9164/management/users?pattern=”*us*”&role=”role”" -H "accept: application/json" -H "Authorization: Bearer %AccessToken%" -k -i
    {
    count:2
    list:
    [
        userId: user1,
        userId: user2,
        userId: user3,
    ]
}

  • Resource: /users/{user_id}

    Description: Retrieves information related to a specified user stored in the external user store.

    Example:

    curl -X GET "https://localhost:9164/management/users/user1" -H "accept: application/json" -H "Authorization: Bearer %AccessToken%" -k -i
    {
  userid: “user1”,
  isAdmin: true/false,
  roles :
  [
       role1,
      role2,
  ]
}

  • Resource: /users/pattern=”*”&role=admin

    Description: Retrieves information related to user names (stored in an external user store) that match a specific pattern and user role.

    Example:

    curl -X GET "https://localhost:9164/management/users?pattern=”*us*”&role=”role”" -H "accept: application/json" -H "Authorization: Bearer %AccessToken%" -k -i
    {
    count:2
    list:
    [
        userId: user1,
        userId: user2,
        userId: user3,
    ]
}

ADD USERS

  • Resource: /users

    Description: Adds a user to the external user store. Note that only admin users can create other users with admin access.

    Example:

    First create the following JSON file with user details as shown below. Note that this new user is granted the admin role.

    {
 "userId":"user4",
 "password":"pwd1",
 "isAdmin":"true"
}

    Execute the following request and receive the response:

    curl -X POST -d @user "https://localhost:9164/management/users" -H "accept: application/json" -H "Content-Type: application/json" -H "Authorization: Bearer %AccessToken% " -k -i
    {
  "userId":"user4",
  “status”:added
}

REMOVE USERS

  • Resource: /users

    Description: Removes a user from the external user store. Note that only admin users can remove other users with admin access.

    Example:

    The following request deletes the user1 from the user store:

    curl -X DELETE "https://localhost:9164/management/users/user1" -H "accept: application/json" -H "Authorization: Bearer %AccessToken%" -k -i
    {
  "userId":"user1",
  “status”:deleted
}

GET PROXY SERVICES

  • Resource: /proxy-services

    Description: Retrieves a list of all deployed proxy services.

    Example:

    curl -X GET "https://localhost:9164/management/proxy-services" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
  "count": 1,
  "list": [
    {
      "name": "TestProxy",
      "wsdl1_1": "http://ThinkPad-X1-Carbon-3rd:8290/services/TestProxy?wsdl",
      "wsdl2_0": "http://ThinkPad-X1-Carbon-3rd:8290/services/TestProxy?wsdl2"
    }
  ]
}

  • Resource: /proxy-services?proxyServiceName={proxyName}

    Description: Retrieves information related to a specified proxy.

    Example: 

    curl -X GET "https://localhost:9164/management/proxy-services?proxyServiceName=helloProxy" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i

ACTIVATE/DEACTIVATE PROXY SERVICES

  • Resource: /proxy-services

    Description: Activate and Deactivate a specified proxy service.

    Example:

        curl -X POST \
      https://localhost:9164/management/proxy-services \
      -H 'authorization: Bearer TOKEN
      -H 'content-type: application/json' \
      -d '{
        "name": "HelloWorld",
        "status": "inactive"
    }' -k -i
    {"Message":"Proxy service HelloWorld stopped successfully"}

ENABLE/DISABLE MESSAGE TRACING for PROXY SERVICES

  • Resource: /proxy-services

    Description: Enable or disable message tracing for a specified proxy service.

    Example:

        curl -X POST \
      https://localhost:9164/management/proxy-services \
      -H 'authorization: Bearer TOKEN' \
      -H 'content-type: application/json' \
      -d '{
        "name": "HelloWorld",
        "trace": "enable"
    }' -k -i
    {"message":"Enabled tracing for ('HelloWorld')"}

GET CARBON APPLICATIONS

Note: This capability to list down faulty applications is released as a WUM update on 16/09/2021 and Update 2.0 on 06/09/2021. If you do not have this update, you can use WSO2 Update Manager(WUM) to get the wum update or use Update 2.0 Tool to get the Update 2.0 update now.

  • Resource: /applications

    Description: This operation provides you a list of available active and faulty Applications.

    Example:

    curl -X GET "https://localhost:9164/management/applications" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
  "count": 1,
  "faultyCount": 1,
  "list": [
    {
      "name": "SampleServicesCompositeApplication",
      "version": "1.0.0"
    }
  ],
  "faultyList": [
    {
      "name": "FaultyCAppCompositeExporter",
      "version": "1.0.0"
    }
  ]
}

ADD CARBON APPLICATION

Note : "This capability is released as a product update on 24/05/2021. If you don't already have this update, you can get the latest updates now.

  • Resource: /applications

    Description: Adds a carbon application to the deployment folder. Once added it will be hot deployed to the server.

    Example:

    curl -X POST "https://localhost:9164/management/applications" --form "file=@path_to_car_file" -H "Authorization: Bearer TOKEN" -k -i
    {"Message":"Successfully added Carbon Application myHttpServiceCompositeExporter_1.0.0-SNAPSHOT.car"}

DOWNLOAD CARBON APPLICATION

Note: This capability is released as a WUM update on 16/09/2021 and Update 2.0 on 06/09/2021. If you do not have this update, you can use WSO2 Update Manager(WUM) to get the wum update or use Update 2.0 Tool to get the Update 2.0 update now.

  • Resource: /applications

    Description: Download a carbon application.

    Example:

        wget \
      https://localhost:9164/management/applications?carbonAppName=myHttpServiceCompositeExporter_1.0.0.car \
      -O myHttpServiceCompositeExporter_1.0.0.car \
      --header 'Authorization: Bearer TOKEN' \
      --header 'accept: application/octet-stream' \
      --no-check-certificate -i

Remove CARBON APPLICATION

Note : "This capability is released as a product update on 24/05/2021. If you don't already have this update, you can get the latest updates now.

  • Resource: /applications

    Description: Removes a carbon application from the deployment folder. Once removed it will be un deployed from the server.

    Example:

    curl -X DELETE "https://localhost:9164/management/applications/myHttpServiceCompositeExporter_1.0.0-SNAPSHOT"  -H "Authorization: Bearer TOKEN" -k -i
    {"Message":"Successfully removed Carbon Application(s) named myHttpServiceCompositeExporter_1.0.0-SNAPSHOT"}

  • Resource: /applications?carbonAppName={appname}

    Description: Retrieves information related to a specified carbon application.

    Example: 

    curl -X GET "https://localhost:9164/management/applications?carbonAppName=HelloCApp" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i

GET ENDPOINTS

  • Resource: /endpoints

    Description: Retrieves a list of available endpoints.

    Example:

    curl -X GET "https://localhost:9164/management/endpoints" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "count": 2,
    "list": [
    {
        "name": "FailOver_EP",
        "type": "failover"
    },
    {
        "name": "WSDL_EP",
        "type": "wsdl"
    }
    ]
}

  • Resource: /endpoints?endpointName={endpointname}

    Description: Retrieves information related to a specified endpoint.

ACTIVATE/DEACTIVATE ENDPOINTS

  • Resource: /endpoints

    Description: Activate or deactivate a specified endpoint.

    Example:

    curl -X POST \https://localhost:9164/management/endpoints \ -H 'authorization: Bearer TOKEN -H 'content-type: application/json' \ -d '{"name": "HTTPEP", "status": "inactive"} -k -i
    {"Message":"HTTPEP : is switched Off"}

ENABLE/DISABLE MESSAGE TRACING for ENDPOINTS

  • Resource: /endpoints

    Description: Enable or disable message tracing for a specified endpoint.

    Example:

        curl -X POST \
      https://localhost:9164/management/endpoints \
      -H 'authorization: Bearer TOKEN' \
      -H 'content-type: application/json' \
      -d '{
        "name": "HTTPEP",
        "trace": "enable"
    }' -k -i
    {"message":"Enabled tracing for ('HTTPEP')"}

GET APIs

  • Resource: /apis

    Description: Retrieves a list of available apis.

    Example:

    curl -X GET "https://localhost:9164/management/apis" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "count": 2,
    "list": [
    {
        "name": "api",
        "url": "http://localhost:8290/test"
    },
    {
        "name": "helloApi",
        "url": "http://localhost:8290/api"
    }
    ]
}

  • Resource: /apis?apiName={api}

    Description: Retrieves information related to a specified api.

ENABLE/DISABLE MESSAGING TRACING for APIs

  • Resource: /apis

    Description: Enable or disable message tracing for a specified api.

    Example:

        curl -X POST \
      https://localhost:9164/management/apis \
      -H 'authorization: Bearer TOKEN' \
      -H 'content-type: application/json' \
      -d '{
        "name": "helloApi",
        "trace": "enable"
    }' -k -i
    {"message":"Enabled tracing for ('helloApi')"}

GET SEQUENCES

  • Resource: /sequences

    Description: Retrieves a list of available sequences.

    Example:

    curl -X GET "https://localhost:9164/management/sequences" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "count": 3,
    "list": [
    {
        "tracing": "disabled",
        "stats": "disabled",
        "name": "fault"
    },
    {
        "container": "[ Deployed From Artifact Container: helloCompositeApplication ] ",
        "tracing": "disabled",
        "stats": "disabled",
        "name": "sequenceForSampler"
    },
    {
        "tracing": "disabled",
        "stats": "disabled",
        "name": "main"
    }
    ]
}

  • Resource: /sequences?sequenceName={sequence}

    Description: Retrieves information related to a specified sequence.

ENABLE/DISABLE MESSAGE TRACING for SEQUENCES

  • Resource: /sequences

    Description: Enable or disable message tracing for a specified sequence.

    Example:

        curl -X POST \
      https://localhost:9164/management/sequences \
      -H 'authorization: Bearer TOKEN' \
      -H 'content-type: application/json' \
      -d '{
        "name": "helloSequence",
        "trace": "enable"
    }' -k -i
    {"message":"Enabled tracing for ('helloSequence')"}

GET LOCAL ENTRIES

  • Resource: /local-entries

    Description: Retrieves a list of available local entries.

    Example:

    curl -X GET "https://localhost:9164/management/local-entries" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "count": 2,
    "list": [
    {
        "name": "testEntry1",
        "type": "Inline Text"
    },
    {
        "name": "testentry2",
        "type": "Inline XML"
    }
    ]
}

  • Resource: /local-entries?name={entryName}

    Description: Retrieves information related to a specified entry.

GET TASKS

  • Resource: /tasks

    Description: Retrieves a list of available tasks.

    Example:

    curl -X GET "https://localhost:9164/management/tasks" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "count": 1,
    "list": [
    {
        "name": "testTask"
    }
    ]
}

  • Resource: /tasks?taskName={taskName}

    Description: Retrieves information related to a specified task.

GET MESSAGE STORES

  • Resource: /message-stores

    Description: Retrieves a list of available message stores.

    Example:

    curl -X GET "https://localhost:9164/management/message-stores" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "count": 2,
    "list": [
    {
        "size": 0,
        "name": "testMessageStore",
        "type": "in-memory-message-store"
    },
    {
        "size": 0,
        "name": "jdbc_sample_store",
        "type": "jdbc-message-store"
    }
    ]
}

  • Resource: /message-stores?name={messageStore}

    Description: Retrieves information related to a specified message store.

GET MESSAGE PROCESSORS

  • Resource: /message-processors

    Description: Retrieves a list of available message processors.

    Example:

    curl -X GET "https://localhost:9164/management/message-processors" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "count": 2,
    "list": [
    {
        "name": "testMessageProcessor",
        "type": "Scheduled-message-forwarding-processor",
        "status": "active"
    },
    {
        "name": "TestSamplingProcessor",
        "type": "Sampling-processor",
        "status": "active"
    }
    ]
}

  • Resource: /message-processors?name={messageProcessors}

    Description: Retrieves information related to a specified message processor.

ACTIVATE/DEACTIVATE MESSAGE PROCESSORS

  • Resource: /message-processors

    Description: Used to activate or deactivate a specific message processor.

    Example:

    curl -X POST \
  https://localhost:9164/management/message-processors \
  -H 'authorization: Bearer Token
  -H 'content-type: application/json' \
  -d '{
    "name": "testMessageProcessor",
    "status": "inactive"
}'

GET INBOUND ENDPOINTS

  • Resource: /inbound-endpoints

    Description: Retrieves a list of available inbound endpoints.

    Example:

    curl -X GET "https://localhost:9164/management/inbound-endpoints" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "count": 1,
    "list": [
    {
        "protocol": "http",
        "name": "HTTPIEP"
    }
    ]
}

  • Resource: /inbound-endpoints?inboundEndpointName={inboundEndpoint}

    Description: Retrieves information related to a specified inbound endpoint.

ENABLE/DISABLE MESSAGE TRACING for INBOUND ENDPOINTS

  • Resource: /inbound-endpoints

    Description: Enable or disable message tracing for a specified inbound-endpoint.

    Example:

        curl -X POST \
      https://localhost:9164/management/inbound-endpoints \
      -H 'authorization: Bearer TOKEN' \
      -H 'content-type: application/json' \
      -d '{
        "name": "HTTPIEP",
        "trace": "enable"
    }' -k -i
    {"message":"Enabled tracing for ('HTTPIEP')"}

GET CONNECTORS

  • Resource: /connectors

    Description: Retrieves a list of available connectors.

    Example:

    curl -X GET "https://localhost:9164/management/connectors" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "count": 2,
    "list": [
    {
        "package": "org.wso2.carbon.connector",
        "name": "fileconnector",
        "description": "wso2 file connector",
        "status": "enabled"
    },
    {
        "package": "org.wso2.carbon.connector",
        "name": "gmail",
        "description": "WSO2 Gmail connector library",
        "status": "enabled"
    }
    ]
}

GET TEMPLATES

  • Resource: /templates

    Description: Retrieves a list of available templates.

    Example:

    curl -X GET "https://localhost:9164/management/templates" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "sequenceTemplateList": [
    {
        "name": "testSequenceTemplate"
    }
    ],
    "endpointTemplateList": [
    {
        "name": "endpointTemplate"
    }
    ]
}

  • Resource: /templates?type=TYPE

    Description: Retrieves a list of available templates of a given type. Supported template types are as follows. 1. endpoint 2. sequence

    Example:

    curl -X GET "https://localhost:9164/management/templates?type=sequence" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "count": 1,
    "list": [
    {
        "name": "testSequenceTemplate"
    }
    ]
}

  • Resource: /templates?type={type}&name={template}

    Description: Retrieves information related to a specific template. However this requires the template type to be included in the request as a query parameter in addition to the template name.

    Example:

    curl -X GET "https://localhost:9164/management/templates?type=sequence&name=testSequenceTemplate" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "Parameters": [],
    "configuration": "<template xmlns=\"http://ws.apache.org/ns/synapse\" name=\"testSequenceTemplate\"><sequence/></template>",
    "name": "testSequenceTemplate"
}

ENABLE/DISABLE MESSAGE TRACING for SEQUENCE TEMPLATES

  • Resource: /templates

    Description: Enable or disable message tracing for a specified sequence template.

    Example:

        curl -X POST \
      https://localhost:9164/management/templates \
      -H 'authorization: Bearer TOKEN' \
      -H 'content-type: application/json' \
      -d '{
        "name": "testSequenceTemplate",
        "type": "sequence",
        "trace": "enable"
    }' -k -i
    {"message":"Enabled tracing for ('testSequenceTemplate')"}

GET SERVER INFORMATION

  • Resource: /server

    Description: Retrieves information related to the micro integrator server instance.

    Example:

    curl -X GET "https://localhost:9164/management/server" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "productVersion": "1.1.0",
    "repositoryLocation": "/Users/Sachith/IdeaProjects/micro-integrator-public/distribution/target/wso2mi-1.1.0-SNAPSHOT/repository/deployment/client/",
    "osVersion": "10.14",
    "javaVersion": "1.8.0_171",
    "workDirectory": "/Users/Sachith/IdeaProjects/micro-integrator-public/distribution/target/wso2mi-1.1.0-SNAPSHOT/tmp/work",
    "carbonHome": "/Users/Sachith/IdeaProjects/micro-integrator-public/distribution/target/wso2mi-1.1.0-SNAPSHOT",
    "javaVendor": "Oracle Corporation",
    "osName": "Mac OS X",
    "productName": "WSO2 Micro Integrator",
    "javaHome": "/Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre"
}

SHUTDOWN SERVER

Note: This capability is released as a WUM update on 16/09/2021 and Update 2.0 on 06/09/2021. If you do not have this update, you can use WSO2 Update Manager(WUM) to get the wum update or use Update 2.0 Tool to get the Update 2.0 update now.

  • Resource: /server

    Description: Shutdown the micro integrator server instance forcefully.

    Example:

        curl -X PATCH \
      https://localhost:9164/management/server \
      -H 'authorization: Bearer TOKEN' \
      -H 'content-type: application/json' \
      -d '{
        "status": "shutdown"
    }' -k -i
    {
"Message":"The server will start to shutdown."
}

SHUTDOWN SERVER GRACEFULLY

Note: This capability is released as a WUM update on 16/09/2021 and Update 2.0 on 06/09/2021. If you do not have this update, you can use WSO2 Update Manager(WUM) to get the wum update or use Update 2.0 Tool to get the Update 2.0 update now.

  • Resource: /server

    Description: Shutdown the micro integrator server instance gracefully.

    Example:

        curl -X PATCH \
      https://localhost:9164/management/server \
      -H 'authorization: Bearer TOKEN' \
      -H 'content-type: application/json' \
      -d '{
        "status": "shutdownGracefully"
    }' -k -i
    {
"Message":"The server will start to shutdown gracefully."
}

RESTART SERVER

Note: This capability is released as a WUM update on 16/09/2021 and Update 2.0 on 06/09/2021. If you do not have this update, you can use WSO2 Update Manager(WUM) to get the wum update or use Update 2.0 Tool to get the Update 2.0 update now.

  • Resource: /server

    Description: Restart the micro integrator server instance forcefully.

    Example:

        curl -X PATCH \
      https://localhost:9164/management/server \
      -H 'authorization: Bearer TOKEN' \
      -H 'content-type: application/json' \
      -d '{
        "status": "restart"
    }' -k -i
    {
"Message":"The server will start to restart."
}

RESTART SERVER GRACEFULLY

Note: This capability is released as a WUM update on 16/09/2021 and Update 2.0 on 06/09/2021. If you do not have this update, you can use WSO2 Update Manager(WUM) to get the wum update or use Update 2.0 Tool to get the Update 2.0 update now.

  • Resource: /server

    Description: Restart the micro integrator server instance gracefully.

    Example:

        curl -X PATCH \
      https://localhost:9164/management/server \
      -H 'authorization: Bearer TOKEN' \
      -H 'content-type: application/json' \
      -d '{
        "status": "restartGracefully"
    }' -k -i
    {
"Message":"The server will start to restart gracefully."
}

GET DATA SERVICES

  • Resource: /data-services

    Description: Retrieves a list of all data services deployed.

    Example:

    curl -X GET "https://localhost:9164/management/data-services" -H "accept: application/json" -H "Authorization: Bearer         TOKEN" -k -i
    {
    "count": 1,
    "list": [
    {
        "name": "StudentDataService",
        "wsdl1_1": "http://Sachiths-MacBook-Pro.local:8290/services/StudentDataService?wsdl",
        "wsdl2_0": "http://Sachiths-MacBook-Pro.local:8290/services/StudentDataService?wsdl2"
    }
    ]
}

  • Resource: /data-services?dataServiceName={dataservice}

    Description: Retrieves information related to a specific data service.

    Example:

    curl -X GET "https://localhost:9164/management/data-services?dataServiceName=StudentDataService" -H "accept:          application/json" -H "Authorization: Bearer TOKEN" -k -i

GET DATA SOURCES

  • Resource: /data-sources Description: Retrieves a list of all data sources deployed. Example: 
    curl -X GET "https://localhost:9164/management/data-sources" -H "accept: application/json" -H "Authorization: Bearer         TOKEN" -k -i
     
    {"count":1,"list":[{"name":"MySQLConnection","type":"RDBMS"}]}
  • Resource: /data-sources?name={datasource} Description: Retrieves information related to a specific data source. Example: 
    curl -X GET "https://localhost:9164/management/data-sources?name=MySQLConnection" -H "accept:          application/json" -H "Authorization: Bearer TOKEN" -k -i
     
    {
"configuration":"<configuration><driverClassName>com.mysql.jdbc.Driver</driverClassName><url>jdbc:mysql://localhost:3307/AccountDetails</url><username>root</username><password>root</password></configuration>",
"driverClass":"com.mysql.jdbc.Driver",
"name":"MySQLConnection",
"description":"MySQL Connection",
"type":"RDBMS",
"url":"jdbc:mysql://localhost:3307/AccountDetails",
"status":"ACTIVE"
}

GET LOG LEVEL

  • Resource: /logging?loggerName={logger}

    Description: Retrieves information related to a specific logger.

    Example:

    curl -X GET "https://localhost:9164/management/logging?loggerName=org-apache-coyote" -H "accept: application/json" -H         "Authorization: Bearer Token" -k
    {
    "loggerName": "org-apache-coyote",
    "level":"WARN",
    "componentName":"org.apache.coyote"
    }

UPDATE ROOT LOG LEVEL

  • Resource: /logging

    Description: Updates the log level of root logger.

    Example:

    curl -X PATCH \
    https://localhost:9164/management/logging \
    -H 'authorization: Bearer Token' \
    -H 'content-type: application/json' \
    -d '{
    "loggerName": "rootLogger",
    "loggingLevel": "WARN"
    }' -k
    {
    "message": "Successfully updated rootLogger.level to WARN"
    }

UPDATE LOG LEVEL

  • Resource: /logging

    Description: Updates the log level of a specific logger.

    Example:

    curl -X PATCH \
    https://localhost:9164/management/logging \
    -H 'authorization: Bearer Token' \
    -H 'content-type: application/json' \
    -d '{
    "loggerName": "org-apache-hadoop-hive",
    "loggingLevel": "DEBUG"
    }' -k
    {
    "message": "Successfully updated logger.org-apache-hadoop-hive.level to DEBUG"
}

ADD NEW LOGGER

  • Resource: /logging

    Description: Add a new logger.

    Example:

    curl -X PATCH \
    https://localhost:9164/management/logging \
    -H 'authorization: Bearer Token' \
    -H 'content-type: application/json' \
    -d '{
          "loggerName": "synapse-api",
          "loggingLevel": "DEBUG",
          "loggerClass":"org.apache.synapse.rest.API"
        }' -k
    {
  "message":"Successfully added logger for ('synapse-api') with level DEBUG for class org.apache.synapse.rest.API"
}

GET TRANSACTION COUNT

  • Resource: /transactions/count

    Description: Retrieves the transaction count for the current month.

    Example:

    curl -X GET "https://localhost:9164/management/transactions/count" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
    "Month": 6,
    "Year": 2020,
    "RequestCount": 74087714
}

  • Resource: /transactions/count?year={year}&month={month}

    Description: Retrieves the transaction count for the specified year and month.

    Example:

    curl -X GET "https://localhost:9164/management/transactions/count?year=2020&month=5" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
     {
    "Month": 5,
    "Year": 2020,
    "TransactionCount": 25074026
 }

GET TRANSACTION REPORT DATA

  • Resource: /transactions/report?start={start}&end={end}

    Description: Retrieves the transaction report for the specified period. Generates the transaction report at the <MI_HOME>/tmp directory.

    Example:

    curl -X GET "https://localhost:9164/management/transactions/report?start=2020-01&end=2020-05" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
    {
 "TransactionCountData": [[col1, col2, col3, col4],[val1, val2, val3, val4]]
}

  • Resource: /transactions/report?start={start}

    Description: Retrieves the transaction report for data starting from the specified date. Generates the transaction report at the <MI_HOME>/tmp directory.

    Example:

     curl -X GET "https://localhost:9164/management/transactions/report?start=2020-01" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -k -i
     {
  "TransactionCountData": [[col1, col2, col3, col4],[val1, val2, val3, val4]]
 }

UPDATE HASHICORP SECRET

Info

This functionality is available as a product update from 27/10/2020 onwards. If you don't already have this update, you can get the latest updates now.

  • Resource: /external-vaults/hashicorp

    Description: Dynamically updates the secret token in the HashiCorp server that is connected to the Micro Integrator. Only applicable when the AppRole-pull authentication method is used. see HashiCorp Secrets for more information.

    Example:

    https://HOST_NAME:9164/management/external-vaults/hashicorp -H 'authorization: Bearer TOKEN
  -H 'content-type: application/json' \
  -d '{
    "secretId" : "new_secret_id" 
    }'
    {
"Message" : ""SecretId value is updated in HashiCorp vault runtime configurations. To persist the new SecretId in the next server startup, please update the deployment.toml file"
}
Top