The shift to digital enables organizations to quickly deliver innovative products and services. As part of this voyage, enterprises must develop their digital transformation blueprints to achieve their business goals.
Organizations are growing their capacities by implementing infrastructure as a service (IaaS) through the cloud using software as a service (SaaS) applications to upgrade their legacy systems. In both scenarios, the use of APIs for integrations has significantly increased – through REST or event-driven architecture (Streaming API capabilities) or GraphQLs, which is a perfect fit for these various scenarios. At the same time, it’s critical to create an API strategy and use technical capabilities to meet current and future business needs.
In this session, we will explore:
- How to create a successful integration and API strategy for digital adoption
- How WSO2 can help enforce your strategy
- Aspects of API-led integration through the WSO2 API management platform in the context of digital adoption, referring to concepts such as event-driven architecture (streaming APIs) and GraphQL
- Creating, life-cycle management, versioning, security, and governance of APIs
- Supporting real-time integrations and APIs - AsyncAPI support
- Managing GraphQL APIs - security, subscription and governance
- Deploy and manage large-scale distributed systems employing a cloud-native, decentralized, lightweight API gateway designed especially for microservices
- Centralized and decentralized deployments of APIs and integrations - using Docker and Kubernetes and API Operator for Kubernetes
- DevOps tooling for managing environments, APIs, and pipelines
- WSO2 API Manager
- WSO2 Micro Integrtor
- WSO2 streaming Integrator
- WSO2 Integration Studio
- Choreo Connect
- WSO2 API Controller
- Backends-Tomcat
- MySQL database preloaded
To build backend docker image run following command navigate to backends
docker build -t tomcat .Then run the container with following command
docker run -d -p 8082:8080 tomcat:latestFor Mac M1 chp users may use following command to download pre-build image
docker run -d -p 8082:8080 dushansachinda/tomcat:backend
curl "http://localhost:8082/train-operations/v1/schedules" docker run -d -p 8083:3306 dushansachinda/mysql-8:latest
docker exec -it [containerid] mysql -uroot -ppassword: pwd
You may also can start vanila API Manager 4.0 container following the command given below; Pleae note that, if you start vanila node, then you need to run Setup scripts that will generate the tenants users required for scenarios
p.s pleaseu use following command to setup ENV properties prior to run setup.sh
export APIM_HOST=localhost RETRY_SEC=10 RE_RUN=truedocker run -it \
-p 9443:9443 \
-p 8243:8243 \
-p 8280:8280 \
wso2am/wso2am:4.0.0-ubuntu
alternativly, you can run pre-configured APIM image by using following command (for Mac M1 chip)
docker run -it \
-p 9443:9443 \
-p 8243:8243 \
-p 8280:8280 \
-v "[source deployment.toml]:/home/wso2carbon/wso2am-4.0.0/repository/conf" \
dushansachinda/wso2am:4.0.0-ubuntuYou can log in to the Publisher Portal and Developer Portal using each tenant's credentials. Publisher portal: https://localhost:9443/publisher/ Developer portal: https://localhost:9443/devportal
To access Publisher tenants use following link
https://localhost:9443/publisher?tenant=quantis.com
https://localhost:9443/publisher?tenant=coltrain.com
https://localhost:9443/publisher?tenant=railco.com
docker build -t mi-4.0.0:demo.
docker run -e CATERING_SERVICE_EP="http://www.urldoesnotexist.com" -e SMTP_PORT="465" -e SMTP_HOST="smtp.gmail.com" -e EMAIL_FROM="[EMAIL_FROM]" -e EMAIL_TO="[EMAIL_TO]" -e SMTP_USERNAME="[SMTP_USERNAME]" -e SMTP_PASSWORD="[SMTP_PASSWORD]" -p 8253:8253 -p 8290:8290 -p 9201:9201 -v "[source]:/home/wso2carbon/file" mi-4.0.0:demo mi-4.0.0:demoRun docker image passing evniroment variables (this may not working for users with Mac M1 chip)
pre configured MI image
https://hub.docker.com/layers/200402421/dushansachinda/mi-4.0.0/demo/images/sha256-c23a8adcdf916387dc404d543d1a8cc978be659773e39b81c8d465ae12399a39?context=repo
docker run -e CATERING_SERVICE_EP="http://www.urldoesnotexist.com" -e SMTP_PORT="465" -e SMTP_HOST="smtp.gmail.com" -e EMAIL_FROM="[EMAIL_FROM]" -e EMAIL_TO="[EMAIL_TO]" -e SMTP_USERNAME="[SMTP_USERNAME]" -e SMTP_PASSWORD="[SMTP_PASSWORD]" -p 8253:8253 -p 8290:8290 -p 9201:9201 -v "[source]:/home/wso2carbon/file" dushansachinda/mi-4.0.0:demo
Union Station is a major multimodal railway transportation hub. It is one of the busiest stations in the country and serves thousands of passengers a day. The train shed, platforms, and tracks are owned by GOGO transit, and they operate the station. Trains are owned by the companies named Quantis, ColTrain, and RailCo. To provide a digital ecosystem, all four companies are planning to develop their day to day business operations with WSO2 technology. These development ranges from providing different kinds of APIs to external/internal users, providing real time notifications, stream data processing, integrating with partners/external systems etc.
(admin user password: admin , other user password : user123)
- Scenario 1: Create a REST API from an OpenAPI Definition
- Scenario 2: Engage Access Control to the API
- Scenario 3: Signing up a New User
- Scenario 4: Getting the Developer Community Involved
- Scenario 5: Rate Limiting
- Scenario 6: GraphQL Support
- Scenario 7: Analytics
- Scenario 8: External Key Manager Support
- Scenario 9: Implementing an API
- Scenario 10: Integrating with Data Sources
- Scenario 11: Integrate with Services via Connectors
- Scenario 12: Gauranteed Message Delivery
- Scenario 13: Realtime Data with WebSocket API
- Scenario 14: Notifications Using Webhooks
- Scenario 15: Deploy and manage large-scale distributed systems employing a cloud-native, decentralized, lightweight API Gateway (Choreo-connect)
- Scenario: 16: Devops CICD pipelines