Manage Dependent Integration Projects¶ Overview¶ When building integration solutions, you may need to reuse common artifacts or share functionality across multiple projects. Managing integration project dependencies allows you to reference one project inside another, ensuring better reusability, modularity, and maintainability. This guide explains how to configure and use integration project dependencies in WSO2 Integrator: MI for Visual Studio Code (VS Code). Create a utility project¶ First, create a utility project that contains reusable artifacts. Follow the Create a Project guide to create a new integration project named integration-utils. Then, create two reusable sequences by following the Create a Reusable Sequence guide: requestLoggerSeq authValidatorSeq For simplicity, both sequences use log mediators: requestLoggerSeq <?xml version="1.0" encoding="UTF-8"?> <sequence name="requestLoggerSeq" trace="disable" xmlns="http://ws.apache.org/ns/synapse"> <log category="INFO" logMessageID="false" logFullPayload="false"> <message>request payload = ${payload}</message> </log> </sequence> authValidatorSeq <?xml version="1.0" encoding="UTF-8"?> <sequence name="authValidatorSeq" trace="disable" xmlns="http://ws.apache.org/ns/synapse"> <log category="INFO" logMessageID="false" logFullPayload="false"> <message>validating...</message> </log> </sequence> Before using this project as a dependency, it needs to be built by creating a CApp. Make sure to note the groupId, artifactId, and version, as these values are required when referencing it in another project. Add utility project as an integration project dependency¶ Next, create a new project that depends on the utility project. Create a new project named order-service. Go to the Overview page in VS Code. In the Project Summary section, locate Integration Project Dependencies. Click Manage Dependencies. In the dependency list, click Add Dependency. Enter the groupId, artifactId, and version of the integration-utils project. Click Update Dependencies to save changes and load artifacts from the dependency. Now, create an API in the order-service project: Follow the Create an API guide to create an API named test. Add a Call Sequence mediator to its resource. From the available options, you will see the sequences from the integration-utils project (e.g., requestLoggerSeq, authValidatorSeq). Enable the FAT CAR option¶ When building a project with dependencies, you can choose whether to bundle all artifacts including artifacts in dependent projects into a single CApp file or not. Open the Project Overview and go to Build Details. Locate the Enable FAT CAR option. By default, this is set to false. Build and run the project¶ FAT CAR enabled¶ All dependent projects’ artifacts are packaged into a single CApp file. You only need to deploy this single CApp file to the MI server. If multiple projects share the same dependent project and need to be deployed on the same server, FAT CAR packaging should be disabled to prevent dependency conflicts. FAT CAR disabled (recommended)¶ Only the current project’s CApp file is built. All dependent CApp files must also be present in the MI_HOME/deployment/server/carbonapps directory. Use the Export option on the Overview page to export the necessary dependencies. When starting the MI server, the server generates a dependency graph from the available CApp files and deploys them in the correct order. This eliminates the need to rename CApp files manually.