All docs This doc
Skip to end of metadata
Go to start of metadata


In this section, we test our first environment of WSO2 Microgateway.

  1. Explore the Spinnaker Dashboard.

    Navigate to the Spinnaker dashboard at https://spinnaker and select Applications > wso2mgw > Pipelines.

    The Spinnaker dashboard shows the progress of the deployment. You are presented with three pipelines where one is active.

      • Deploy Dev: Pipeline is responsible for executing the tasks in deploying the changes to Dev environment.

      • Deploy Staging: Pipeline responsible for executing the tasks in deploying the changes to the Staging environment.

      • Deploy Prod: Pipeline responsible for executing the tasks in deploying the changes to the Production environment. 

  2. Once the changes have been deployed to the Dev environment, you will be prompted to provide a manual input in order to proceed to make a deployment to Staging.

  3. Before proceeding with the manual judgment, let us examine our WSO2 API Microgateway in the Dev environment. Navigate to Infrastructure tab > Load Balancers tab> ingress wso2micro-gw-ingress

    Ingress information of current deployments can be observed here. The Ingress IP address of the Microgateway Dev environment can be obtained from the sidebar to the right.

    • Copy the ingress IP address and add it as a host entry in /etc/hosts.

      <INGRESS_IP> wso2mgw-dev

    • Invoke the sample API

      1. Obtain a token

        After the APIs are exposed via WSO2 API Microgateway, you can invoke an API with a valid JWT token or an opaque access token.

        In order to use JWT tokens, WSO2 API Microgateway should be presented with a JWT signed by a trusted OAuth2 service.

        Let's use the following sample JWT token for the quick start guide.

        Sample Token

        eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ik5UQXhabU14TkRNeVpEZzNNVFUxWkdNME16RXpPREpoWldJNE5ETmxaRFUxT0dGa05qRmlNUSJ9.
        eyJhdWQiOiJodHRwOlwvXC9vcmcud3NvMi5hcGltZ3RcL2dhdGV3YXkiLCJzdWIiOiJhZG1pbiIsImFwcGxpY2F0aW9uIjp7ImlkIjoyLCJuYW1lIjoiSldUX
        0FQUCIsInRpZXIiOiJVbmxpbWl0ZWQiLCJvd25lciI6ImFkbWluIn0sInNjb3BlIjoiYW1fYXBwbGljYXRpb25fc2NvcGUgZGVmYXVsdCIsImlzcyI6Imh0dH
        BzOlwvXC9sb2NhbGhvc3Q6OTQ0M1wvb2F1dGgyXC90b2tlbiIsImtleXR5cGUiOiJQUk9EVUNUSU9OIiwic3Vic2NyaWJlZEFQSXMiOltdLCJjb25zdW1lcktl
        eSI6Ilg5TGJ1bm9oODNLcDhLUFAxbFNfcXF5QnRjY2EiLCJleHAiOjM3MDMzOTIzNTMsImlhdCI6MTU1NTkwODcwNjk2MSwianRpIjoiMjI0MTMxYzQtM2Q2MS
        00MjZkLTgyNzktOWYyYzg5MWI4MmEzIn0=.b_0E0ohoWpmX5C-M1fSYTkT9X4FN--_n7-bEdhC3YoEEk6v8So6gVsTe3gxC0VjdkwVyNPSFX6FFvJavsUvzTkq
        528mserS3ch-TFLYiquuzeaKAPrnsFMh0Hop6CFMOOiYGInWKSKPgI-VOBtKb1pJLEa3HvIxT-69X9CyAkwajJVssmo0rvn95IJLoiNiqzH8r7PRRg_iu305WAT3
        cymtejVWH9dhaXqENwu879EVNFF9udMRlG4l57qa2AaeyrEguAyVtibAsO0Hd-DFy5MW14S6XSkZsis8aHHYBlcBhpy2RqcP51xRog12zOb-WcROy6uvhuCsv-hje_41WQ==
      2. Invoke the API

        Invoke the API using the sample JWT token using the following commands:

        $TOKEN=eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ik5UQXhabU14TkRNeVpEZzNNVFUxWkdNME16RXpPREpoWldJNE5ETmxaRFUxT0dGa05qRmlNUSJ9
        .eyJhdWQiOiJodHRwOlwvXC9vcmcud3NvMi5hcGltZ3RcL2dhdGV3YXkiLCJzdWIiOiJhZG1pbiIsImFwcGxpY2F0aW9uIjp7ImlkIjoyLCJuYW1lIjoiSldUX0FQUC
        IsInRpZXIiOiJVbmxpbWl0ZWQiLCJvd25lciI6ImFkbWluIn0sInNjb3BlIjoiYW1fYXBwbGljYXRpb25fc2NvcGUgZGVmYXVsdCIsImlzcyI6Imh0dHBzOlwvXC9sb
        2NhbGhvc3Q6OTQ0M1wvb2F1dGgyXC90b2tlbiIsImtleXR5cGUiOiJQUk9EVUNUSU9OIiwic3Vic2NyaWJlZEFQSXMiOltdLCJjb25zdW1lcktleSI6Ilg5TGJ1bm9oOD
        NLcDhLUFAxbFNfcXF5QnRjY2EiLCJleHAiOjM3MDMzOTIzNTMsImlhdCI6MTU1NTkwODcwNjk2MSwianRpIjoiMjI0MTMxYzQtM2Q2MS00MjZkLTgyNzktOWYyYzg5MWI
        4MmEzIn0=.b_0E0ohoWpmX5C-M1fSYTkT9X4FN--_n7-bEdhC3YoEEk6v8So6gVsTe3gxC0VjdkwVyNPSFX6FFvJavsUvzTkq528mserS3ch-TFLYiquuzeaKAPrnsFMh
        0Hop6CFMOOiYGInWKSKPgI-VOBtKb1pJLEa3HvIxT-69X9CyAkwajJVssmo0rvn95IJLoiNiqzH8r7PRRgV_iu305WAT3cymtejVWH9dhaXqENwu879EVNFF9udMRlG4l5
        7qa2AaeyrEguAyVtibAsO0Hd-DFy5MW14S6XSkZsis8aHHYBlcBhpy2RqcP51xRog12zOb-WcROy6uvhuCsv-hje_41WQ==
        $ curl -X GET "https://wso2mgw-dev/petstore/v1/pet/findByStatus?status=available" -H "accept: application/xml" -H "Authorization:Bearer $TOKEN" -k

What’s next:


Try with Jenkins:  Refer Point 4 in installation  

Try carbon consoles : 

  1. When the dev-stack status changes to CREATE_COMPLETE , open the Output tab in the AWS Console. 

  2. Click on the value of ConsoleURL to access the WSO2 API Manager console. Login with admin/admin credentials

  3. Management console of each environment can be accessed similarly by clicking on the value of ConsoleURL in the outputs tab of each environment stack.







Try invoking services : 

  1. Login to API Manager Management console.

  2. Refer Try Invoking an API to try out API Manager services.

Try  Logs : 

  1. When the dev-stack status changes to CREATE_COMPLETE , open the Output tab in the AWS Console. 

  2. Click the value of LogDashboardURL to access the Kibana dashboard that contains the product deployment log.

Try Monitoring : 

  1. When the prod-stack status changes to CREATE_COMPLETE , open the Output tab in the AWS Console. 

  2. Click on the value of MonitoringDashboardURL to access the Grafana dashboard to visualize product monitoring. Login using admin/admin credentials. You may change the username and password when requested to do so.

  3. Monitor dashboard of each environment can be accessed similarly by clicking on the value of MonitoringDashboardURL in the outputs tab of each environment stack.

  4. There are four different dashboards for monitoring the following.

    1. Probe Monitoring

    2. Resource Monitoring

    3. JMX Monitoring

    4. JVM Monitoring

What’s next:


  • No labels