Merge branch '4.3.0' into 4.3-vscode-docs

wso2 · Dec 16, 2024 · eb1feb8 · eb1feb8
2 parents 549e501 + 9a79f3a
commit eb1feb8
Show file tree

Hide file tree

Showing 61 changed files with 439 additions and 318 deletions.
diff --git a/en/docs/assets/attachments/jar/ISO8583TestClient-1.0.jar b/en/docs/assets/attachments/jar/ISO8583TestClient-1.0.jar
diff --git a/en/docs/assets/img/develop/create-artifacts/create-rest-api/add-resource.png b/en/docs/assets/img/develop/create-artifacts/create-rest-api/add-resource.png
diff --git a/en/docs/assets/img/develop/create-artifacts/create-rest-api/available-apis.png b/en/docs/assets/img/develop/create-artifacts/create-rest-api/available-apis.png
diff --git a/...ocs/assets/img/develop/create-artifacts/create-rest-api/available-resources.png b/...ocs/assets/img/develop/create-artifacts/create-rest-api/available-resources.png
diff --git a/en/docs/assets/img/develop/create-artifacts/create-rest-api/edit-api-interface.png b/en/docs/assets/img/develop/create-artifacts/create-rest-api/edit-api-interface.png
diff --git a/...ts/img/develop/create-artifacts/create-rest-api/edit-api-resource-interface.png b/...ts/img/develop/create-artifacts/create-rest-api/edit-api-resource-interface.png
diff --git a/...velop/create-artifacts/create-rest-api/generate-api-from-openapi-definition.png b/...velop/create-artifacts/create-rest-api/generate-api-from-openapi-definition.png
diff --git a/...ts/img/develop/create-artifacts/create-rest-api/generate-api-from-wsdl-file.png b/...ts/img/develop/create-artifacts/create-rest-api/generate-api-from-wsdl-file.png
diff --git a/en/docs/assets/img/develop/create-artifacts/create-rest-api/generate-api.png b/en/docs/assets/img/develop/create-artifacts/create-rest-api/generate-api.png
diff --git a/...ts/img/develop/create-projects/create-integration-project/add-artifact-pane.png b/...ts/img/develop/create-projects/create-integration-project/add-artifact-pane.png
diff --git a/...te-projects/create-integration-project/create-project-using-command-palette.png b/...te-projects/create-integration-project/create-project-using-command-palette.png
diff --git a/...create-projects/create-integration-project/create-project-using-design-view.png b/...create-projects/create-integration-project/create-project-using-design-view.png
diff --git a/...rojects/create-integration-project/create-project-using-mi-project-explorer.png b/...rojects/create-integration-project/create-project-using-mi-project-explorer.png
diff --git a/.../img/develop/create-projects/create-integration-project/new-project-details.png b/.../img/develop/create-projects/create-integration-project/new-project-details.png
diff --git a/en/docs/assets/img/develop/create-projects/importing-projects/open-mi-project.gif b/en/docs/assets/img/develop/create-projects/importing-projects/open-mi-project.gif
diff --git a/en/docs/assets/img/develop/mi-for-vscode/command-palette.png b/en/docs/assets/img/develop/mi-for-vscode/command-palette.png
diff --git a/en/docs/assets/img/develop/mi-for-vscode/mi-overview.png b/en/docs/assets/img/develop/mi-for-vscode/mi-overview.png
diff --git a/en/docs/assets/img/develop/mi-for-vscode/project-explorer.png b/en/docs/assets/img/develop/mi-for-vscode/project-explorer.png
diff --git a/en/docs/assets/img/develop/mi-for-vscode/reload-window.png b/en/docs/assets/img/develop/mi-for-vscode/reload-window.png
diff --git a/en/docs/assets/img/develop/mi-for-vscode/samples.png b/en/docs/assets/img/develop/mi-for-vscode/samples.png
diff --git a/en/docs/assets/img/develop/mi-for-vscode/switch-to-project-explorer.gif b/en/docs/assets/img/develop/mi-for-vscode/switch-to-project-explorer.gif
diff --git a/en/docs/assets/img/integrate/connectors/iso8583-inbound-form.png b/en/docs/assets/img/integrate/connectors/iso8583-inbound-form.png
diff --git a/en/docs/assets/img/integrate/connectors/iso8583-inbound.png b/en/docs/assets/img/integrate/connectors/iso8583-inbound.png
diff --git a/en/docs/assets/img/integrate/connectors/mongodb-connector-store.png b/en/docs/assets/img/integrate/connectors/mongodb-connector-store.png
diff --git a/en/docs/assets/img/integrate/connectors/sqs-inbound-form.png b/en/docs/assets/img/integrate/connectors/sqs-inbound-form.png
diff --git a/en/docs/assets/img/integrate/connectors/sqs-inbound.png b/en/docs/assets/img/integrate/connectors/sqs-inbound.png
diff --git a/en/docs/assets/img/integrate/tutorials/using-templates/create-new-project.png b/en/docs/assets/img/integrate/tutorials/using-templates/create-new-project.png
diff --git a/en/docs/assets/img/learn/tutorials/data-service/create-new-project.png b/en/docs/assets/img/learn/tutorials/data-service/create-new-project.png
diff --git a/...ocs/assets/img/learn/tutorials/exposing-several-services/create-new-project.png b/...ocs/assets/img/learn/tutorials/exposing-several-services/create-new-project.png
diff --git a/en/docs/assets/img/learn/tutorials/message-routing/create-new-project.png b/en/docs/assets/img/learn/tutorials/message-routing/create-new-project.png
diff --git a/.../img/learn/tutorials/send-email-from-integration-service/create-new-project.png b/.../img/learn/tutorials/send-email-from-integration-service/create-new-project.png
diff --git a/...ts/img/learn/tutorials/sending-simple-message-to-service/create-new-project.png b/...ts/img/learn/tutorials/sending-simple-message-to-service/create-new-project.png
diff --git a/...sets/img/learn/tutorials/storing-and-forwarding-messages/create-new-project.png b/...sets/img/learn/tutorials/storing-and-forwarding-messages/create-new-project.png
diff --git a/.../assets/img/learn/tutorials/transforming-message-content/create-new-project.png b/.../assets/img/learn/tutorials/transforming-message-content/create-new-project.png
diff --git a/en/docs/assets/img/learn/tutorials/using-scheduled-tasks/create-new-project.png b/en/docs/assets/img/learn/tutorials/using-scheduled-tasks/create-new-project.png
diff --git a/en/docs/develop/create-integration-project.md b/en/docs/develop/create-integration-project.md
@@ -1,11 +1,15 @@
-# Creating an Integration Project
+# Create a Project
 
-1. Launch Visual Studio Code with the Micro Integrator extension installed.
+An integration project in WSO2 Micro Integrator (MI) is a structured collection of artifacts designed to facilitate seamless communication and data exchange between diverse systems, applications, and services.
+
+Follow the below steps to create an integration project using the WSO2 Micro Integrator for VS Code extension (MI for VS Code):
+
+1. Launch Visual Studio Code with the MI for VS Code extension installed.
 
     !!! info
         Follow the [Install Micro Integrator for VS Code]({{base_path}}/develop/mi-for-vscode/install-wso2-mi-for-vscode) documentation for a complete installation guide.
 
-2. Click on the WSO2 icon on the **Activity Bar** of the VS Code editor.
+2. Click on the Micro Integrator icon on the **Activity Bar** of the VS Code editor.
 
     <a href="{{base_path}}/assets/img/develop/mi-for-vscode/mi-vscode-extension.png"><img src="{{base_path}}/assets/img/develop/mi-for-vscode/mi-vscode-extension.png" alt="Mi VS Code Extension" width="80%"></a>
 
@@ -41,7 +45,7 @@
 
 4. In the **Project Creation Form**, enter a suitable name for the integration project under **Project Name**.
 
-5. Provide a location under the **Select Project Directory**.
+5. Provide a location under **Select Project Directory**.
 
     <a href="{{base_path}}/assets/img/develop/create-projects/create-integration-project/new-project-details.png"><img src="{{base_path}}/assets/img/develop/create-projects/create-integration-project/new-project-details.png" alt="New Project Details" width="70%"></a>
 
@@ -50,24 +54,7 @@
     Upon clicking **Create**, you will now see the below interface.
 
     <a href="{{base_path}}/assets/img/develop/create-projects/create-integration-project/add-artifact-pane.png"><img src="{{base_path}}/assets/img/develop/create-projects/create-integration-project/add-artifact-pane.png" alt="Add Artifact Pane" width="80%"></a>
-
-Now you can start creating your integration project by creating artifacts. You can also incorporate the AI-powered assistance experience with Micro Integrator Copilot. 
-
-The following are the synapse artifacts that can be added to an integration flow:
-
-| Artifact              | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **API**               | An endpoint with a URL, specifying the context and resources accessible through HTTP methods such as GET, PUT, POST, DELETE. When requests arrive, they are processed by the input sequence (inSequence) of the API, where the Micro Integrator uses mediators to process the message and forward it to the backend service. Upon receiving the response from the backend, the same inSequence or a designated faultSequence (in case of errors) processes the response and forwards it to the client, ensuring a streamlined flow of messages without the need for an output sequence. |
-| **Endpoint**          | Defines external reference points for sending out messages from the integration server to external services or APIs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| **Sequence**          | A reusable set of mediation instructions that processes incoming or outgoing messages. Sequences are used in the proxy service and the REST APIs. Each sequence is a set of mediators where messages are processed.                                                                                                                                                                                                                                                                                                                                                                     |
-| **Proxy**             | Acts as an intermediary that accepts client requests, optionally applies mediation logic through sequences, and routes them to external services or internal components for processing, thereby decoupling the client and backend service endpoints.                                                                                                                                                                                                                                                                                                                                    |
-| **Inbound Endpoint**  | A listener that facilitates the receiving of messages from external systems into the MI ecosystem. They can be configured dynamically without restarting the server. Messages move from the transport layer to the mediation layer without going through the Axis2 engine.                                                                                                                                                                                                                                                                                                              |
-| **Message Store**     | Temporarily stores messages that are processed asynchronously, allowing for reliable messaging and delayed processing. The delivery of a message to the endpoint can be guaranteed with this, since it is only deleted from the Store when an endpoint receives the message correctly.                                                                                                                                                                                                                                                                                                  |
-| **Message Processor** | Handles the processing of messages stored in message stores, managing the delivery of messages to endpoints based on specific conditions or schedules. The message processor extracts a queue, memory or database from it and sends it to an endpoint.                                                                                                                                                                                                                                                                                                                                  |
-| **Task**              | A scheduled job that executes specific logic at predefined intervals to automate integration workflows. Tasks can also be customized.                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| **Local Entry**       | Static configurations stored locally within the server, used to define simple values or XML configurations that can be referenced within synapse configurations.                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| **Template**          | A reusable configurations that can be parameterized and applied to multiple integration scenarios to promote reusability.                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| **Data Service**      | A deployable artifact that exposes data operations as web services, allowing for CRUD (Create, Read, Update, Delete) operations on underlying data sources through SOAP or RESTful APIs.                                                                                                                                                                                                                                                                                                                                                                                                |
-| **Data Source**       | A configuration element that defines the connection details to a database, enabling the Micro Integrator to interact with it for data operations.                                                                                                                                                                                                                                                                                                                                                                                                                                       | 
-| **Class Mediator**    | A custom Java class that implements the `org.apache.synapse.Mediator` interface, allowing developers to execute custom logic within the flow of a Synapse configuration.                                                                                                                                                                                                                                                                                                                                                                                                                |
-| **Registry**          | A centralized configuration management system used to store, manage, and retrieve configuration artifacts and resources for integration solutions.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+
+Now you can start creating your integration by developing artifacts. Additionally, you can enhance your experience by incorporating AI-powered assistance with [Micro Integrator Copilot]({{base_path}}/develop/mi-for-vscode/mi-copilot).
+
+See the [Integration Artifacts Overview]({{base_path}}/develop/creating-artifacts/creating-artifacts-overview) documentation to learn about the integration artifacts.