Develop Integration Solutions¶ The contents on this page will walk you through the topics related to developing integration solutions using WSO2 Integrator: MI for Visual Studio Code extension: MI for VS Code. WSO2 Integrator: MI for Visual Studio Code (MI for VS Code)¶ MI for VS Code is the comprehensive developer tool, which you will use to develop, build, and test your integration solutions before the solutions are pushed to your production environments. See the topics given below for details. Overview of MI for VS Code extension Get introduced to the main functions of MI for VS Code. Installing MI for VS Code extension Find the instructions on how to download and install the MI for VS Code on your operating system. Troubleshooting MI for VS Code extension Find details on how to troubleshoot errors you might encounter as you use MI for VS Code. WSO2 Integrator Copilot Explore the conversational AI assistant built into MI for VS Code — Ask, Edit, and Plan modes, checkpoints, attachments, and more. Development workflow¶ Integration developers will follow the workflow illustrated by the following diagram. Set up the workspace¶ To start developing integration solutions, you need to first install and set up Mico Integrator VS Code extension. Develop¶ Create an Integration project: An integration project will include all the artifacts of your integration solution. Create artifacts Message Entry Points REST API Proxy Service Inbound Endpoint Scheduled trigger Message Processing Units Message Store Message Processor Endpoint Endpoint Template Sequence Template Reusable Sequences Registry Resources Registry Resource Local Entry Data Services Resources Data Service Datasource Extensions Custom Mediator Custom Inbound Endpoint Custom Connector Custom Scheduled trigger Synapse Handler Other Import Artifacts Secure the artifacts Encrypting Sensitive Data Encrpting Secrets Docker Secrets Kubernetes Secrets Symmetric Encryption Securing APIs and Services Securing REST APIs Securing Proxy Services Securing Data Services Build and run¶ Package The artifacts and modules should be packaged in a Composite Exporter before they can be deployed in any environment. Deploy You can easily deploy and try out the packaged integration artifacts on your preferred environment: Deploy on the Embedded WSO2 Integrator: MI Deploy on a Remote WSO2 Integrator: MI Unit Tests Use the integration test suite of MI for VS Code to run unit tests on the developed integration solution. Iterate and improve¶ As you build and run the integration flow, you may identify errors that need to be fixed, and changes that need to be done to the synapse artifacts. Debug Mediations Use the Mediation Debug function in MI for VS Code to debug errors while you develop the integration solutions. Using Logs You can enable and analyze the following logs to debug various errors: Wire Logs Proxy Service Access Logs REST API Access Logs You must redeploy the integration artifacts after applying changes. If you are testing on a VM, the artifacts will be instantly deployed when you redeploy the synapse artifacts. If you are testing on containers, you need to rebuild the Docker images. Push to production¶ It is recommended to use a CI/CD pipeline to deploy your tested integration solutions in the production environment. On-Premise Environment You can easily push your integration solutions to a CI/CD pipeline. Related topics¶ Integration Use Cases Read about the integration use cases supported by the WSO2 Integrator: MI. Tutorials Develop and try out each integration use case end-to-end. Examples Try out specific integration scenarios by running the samples.