Merge pull request #1143 from wso2/4.3.0

Sync main branch with 4.3.0 branch

en/docs/develop/creating-artifacts/creating-a-message-store.md

@@ -50,7 +50,7 @@ To add a message store to the integration sequence, use the [Store Mediator]({{b
 
     <a href="{{base_path}}/assets/img/develop/create-artifacts/create-message-store/store-message.png"><img src="{{base_path}}/assets/img/develop/create-artifacts/create-message-store/store-message.png" alt="Store message" width="80%"></a>
 
-3. Enter the name of the message store artifact you previously created.
+3. Select the name of the message store artifact you previously created from the dropdown.
 
     <a href="{{base_path}}/assets/img/develop/create-artifacts/create-message-store/store-message-details.png"><img src="{{base_path}}/assets/img/develop/create-artifacts/create-message-store/store-message-details.png" alt="Store message details" width="30%"></a>
 

en/docs/develop/injecting-parameters.md

@@ -142,9 +142,6 @@ In the following example, the endpoint URL is configured as a dynamic value.
 
 ### Data service parameters
 
-!!! Tip
-    Note that you cannot inject parameters to data service using a file. You can only use environment variables.
-
 Listed below are the data service parameters that can be dynamically injected.
 
 -   `Driver`

en/docs/develop/mi-for-vscode/install-wso2-mi-for-vscode.md

@@ -4,18 +4,16 @@ This page walks you through how to get started with the Micro Integrator for VS
 
 ## Prerequisites
 
-- Download and install Java SE Development Kit (JDK) version 11 or 17. See [tested JDK versions]({{base_path}}/install-and-setup/setup/reference/product-compatibility/#tested-jdks) for more information.
+- **Java Development Kit (JDK) 17**
+    1. Download and install Java SE Development Kit (JDK) version 17. For more information on compatible JDK versions, see the [Tested JDKs]({{base_path}}/install-and-setup/setup/reference/product-compatibility/#tested-jdks) documentation.
+    2. Set the `JAVA_HOME` environment variable in the system settings. For more information on setting `JAVA_HOME`, see the [Install and Setup]({{base_path}}/install-and-setup/install/installing-mi/#setting-up-java_home) documentation.
 
-- Set the `JAVA_HOME` environment variable in the [system settings]({{base_path}}/install-and-setup/install/installing-mi/#setting-up-java_home).
+- **Apache Maven**
+    1. Download and install [Apache Maven](https://maven.apache.org/download.cgi) (version 3.6.0 onwards).
+    2. Set the path for Apache Maven in the [system's PATH environment variable](https://maven.apache.org/install.html).
 
-- Download and install [Apache Maven](https://maven.apache.org/download.cgi) (version 3.6.0 onwards).
-
-- Set the path for Apache Maven in the [system's PATH environment variable](https://maven.apache.org/install.html).
-
-- Download and install the Visual Studio Code editor from [here](https://code.visualstudio.com/download).
-
-    !!! info
-        For more information on installing Visual Studio Code, refer to [Visual Studio Code documentation](https://code.visualstudio.com/docs/setup/setup-overview).
+- **Visual Studio Code**
+    Download and install the Visual Studio Code editor from [here](https://code.visualstudio.com/download).
 
 ## Install the MI VS Code extension
 

en/docs/get-started/quick-start-guide.md

@@ -8,12 +8,12 @@ In this guide, you'll learn the basics of setting up and using WSO2 MI to create
 
 The following software and configurations are required to proceed with this tutorial:
 
-- **Java Development Kit (JDK):** Version 11 or 17 is required. Set up a [compatible JDK]({{base_path}}/install-and-setup/setup/reference/product-compatibility/#tested-jdks). Ensure the JDK is properly configured in your [system's PATH environment variable]({{base_path}}/install-and-setup/install/installing-mi).
+- **Java Development Kit (JDK) 17**
 
-    !!! Info
-        For more information on setting the `JAVA_HOME` environment variable for different operating systems, see the [Install and Setup]({{base_path}}/install-and-setup/install/installing-mi) documentation.
+    1. Download and install Java SE Development Kit (JDK) version 17. For more information on compatible JDK versions, see the [Tested JDKs]({{base_path}}/install-and-setup/setup/reference/product-compatibility/#tested-jdks) documentation.
+    2. Set the `JAVA_HOME` environment variable in the system settings. For more information on setting `JAVA_HOME`, see the [Install and Setup]({{base_path}}/install-and-setup/install/installing-mi/#setting-up-java_home) documentation.
 
-  - **Apache Maven:** Ensure <a target="_blank" href="https://maven.apache.org/download.cgi">Apache Maven</a> is installed (version 3.6.0 onwards) and its path is correctly set within the <a target="_blank" href="https://maven.apache.org/install.html">system's PATH environment variable</a>.
+- **Apache Maven:** Ensure <a target="_blank" href="https://maven.apache.org/download.cgi">Apache Maven</a> is installed (version 3.6.0 onwards) and its path is correctly set within the system's PATH environment variable.
 
     !!! info
         For more information on installing Apache Maven, see the <a target="_blank" href="https://maven.apache.org/install.html">Apache Maven documentation</a>.

en/docs/includes/setting-up-workspace-for-mi-for-vscode.md

@@ -1,7 +1,7 @@
 The following software and configurations are required to proceed with this tutorial:
 
 - **Visual Studio Code (VS Code):** with the Micro Integrator extension installed.
-- **Java Development Kit (JDK):** Version 11 or 17 is required. Ensure the JDK is properly configured in your system's PATH environment variable.
+- **Java Development Kit (JDK):** Ensure the JDK is properly configured in your system's PATH environment variable.
 - **Apache Maven:** Ensure Apache Maven is installed and its path is correctly set within the system's PATH environment variable.
 
 !!! info

en/docs/install-and-setup/setup/brokers/configure-with-weblogic.md

@@ -1,13 +1,14 @@
 # Connecting to Oracle WebLogic
 
-This section describes how to configure WSO2 Micro Integrator to connect with Oracle WebLogic 10.3.4.0.
+This section describes how to configure WSO2 Micro Integrator to connect with Oracle WebLogic v14.1.1.0.
 
 ## Starting WebLogic and WSO2 Micro Integrator
 
-1.  Download and set up [Oracle WebLogic Server](http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html).
-2.  Download and [start WSO2 Micro Integrator]({{base_path}}/install-and-setup/install/running-the-mi) .
-3.  Wrap the WebLogic client jar and build a new OSGi bundle using the following [pom.xml](https://svn.wso2.org/repos/wso2/scratch/lasantha/weblogic-wrapper/pom.xml). The exporting of `javax.jms` package and `javax.xml.namespace` package of the client JAR should be prevented.
-4.  Copy the client libraries file (`wlfullclient.jar`) from the `WEBLOGIC_HOME/wlserver_XX/server/lib` directory to the `MI_HOME/dropins` directory.
+1.  Download and set up [Oracle WebLogic Server v14.1.1.0](http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html) using the generic installer.
+2.  Install Oracle JDK 11 and set the `JAVA_HOME` environment variable.
+3.  [Download and install WSO2 Micro Integrator](https://mi.docs.wso2.com/en/4.3.0/install-and-setup/install/installing-mi/).
+4.  Copy `wlthint3client.jar` from the `<WebLogic_HOME>/server/lib/` directory to the `<MI_HOME>/lib/` directory.
+5.  [Start WSO2 Micro Integrator]({{base_path}}/install-and-setup/install/running-the-mi).
 
 ## Configuring the WebLogic server
 

en/docs/learn/examples/template-examples/using-sequence-templates.md

@@ -161,13 +161,13 @@ You can test this out with the following payload sent to the proxy via `http://l
 </body>
 ```
 
-## Example 2: Mandatory parameters and default values
+## Example 2: Optional parameters and default values
 
 Following are the integration artifacts we can use to implement this scenario. See the instructions on how to [build and run](#build-and-run-example-2) this example.
 
 ### Synapse configuration
 
-In this example, the sequence template is configured to log the greeting message that is passed from the mediation sequence in the REST API. According to the sequence template, a value for the greeting message is mandatory. However, the REST API is not passing a greeting message to this template. Therefore, the <b>default</b> greeting message specified in the template is effectively applied.
+In this example, the sequence template is configured to log the greeting message that is passed from the mediation sequence in the REST API. According to the sequence template, a value for the greeting message is optional. The REST API is not passing a greeting message to this template. Therefore, the <b>default</b> greeting message specified in the template is effectively applied.
 
 === "Sequence Template"
     ```xml  

en/docs/reference/troubleshooting/error-handling-mi.md

@@ -103,8 +103,47 @@ This section describes the error codes for endpoint failures. For more informati
 |----------------|------------------------------|
 | 601000         | Malform XML or JSON received |
 
-## Custom Error Codes
+## Custom error codes
 
 | **Error Code** |   **Detail**                                                                                    |
 |----------------|-------------------------------------------------------------------------------------------------|
 | 500000         | Endpoint Custom Error - This error is triggered when the endpoint is prefixed by `<property>name="FORCE_ERROR_ON_SOAP_FAULT" value="true"/>`, which enhances the failover logic by marking an endpoint as suspended when the response is a SOAP fault. |
+
+## Data service error codes
+
+<table>
+    <tr>
+        <th>Error Code</th>
+        <th>Detail</th>
+    </tr>
+    <tr>
+        <td><code>DATABASE_ERROR</code></td>
+        <td>This exception is thrown at the point of invoking a request if there are errors occurring while querying the database or while processing the result of a query. For example, a syntax error thrown from the database, a primary key constraint violation, etc.</td>
+    </tr>
+    <tr>
+        <td><code>CONNECTION_UNAVAILABLE_ERROR</code></td>
+        <td>This error occurs at the point of <a href="{{base_path}}/develop/creating-artifacts/data-services/creating-data-services">creating a data service</a> if the connection to the datasource cannot be established.</td>
+    </tr>
+    <tr>
+        <td><code>VALIDATION_ERROR</code></td>
+        <td>This error occurs when an input parameter in the request for a query fails the <a href="{{base_path}}/reference/synapse-properties/data-services/input-validators">validation</a> defined for that parameter. See the <a href="{{base_path}}/learn/examples/data-integration/data-input-validator">example on validators</a> to understand how validations work.</td>
+    </tr>
+    <tr>
+        <td><code>INCOMPATIBLE_PARAMETERS_ERROR</code></td>
+        <td>This error occurs in the following instances:
+        <ul>
+            <li>When a request is invoked, the number of parameters passed in the request should match the number of input parameters defined in the query. Otherwise, there need to be <a href="{{base_path}}/reference/synapse-properties/data-services/query-parameters/#input-parameters">default values</a> specified in the corresponding query for the parameters that are not passed in the request. If either of these requirements is not fulfilled, this error will occur when invoking the request.</li>
+            <li>When a request is invoked, the list of parameters given for the operation defined in your data service should match the input parameters given in the corresponding query definition. If there is a mismatch, this error will occur.</li>
+        </ul>
+        </td>
+    </tr>
+    <tr>
+        <td><code>UNKNOWN_ERROR</code></td>
+        <td>For all other types of errors.</td>
+    </tr>
+</table>
+
+!!! Note
+    When logging the errors by default it prints the service name, operation or resource, parameters, error code, and the exception. You can use the following system property to avoid printing request parameters in the logs.
+
+    `-Ddss.disable.current.params=true`

en/docs/reference/troubleshooting/utilizing-runtime-diagnostic-tool.md

@@ -16,14 +16,15 @@ There are four main components in the tool:
 
 ## Configuration Guide
 
-The tool is packaged inside the product distribution with default configurations. The configurations can be customized based on user requirements. 
+The tool is packaged inside the product distribution with default configurations. The configurations can be customized based on user requirements. By default, the diagnostic tool is enabled.
 
 ### Server Configurations
 
 The table given below describes the server configurations.
 
 | Configuration | Description                                         |
 | --- |-----------------------------------------------------|
+| `diagnostic_tool_enabled` | Option to disable/enable diagnostics tool |
 | `deployment_toml_path` | Path to the deployment.toml file in the WSO2 server |
 | `logs_directory` | Path to the logs directory.                         |
 | `updates_config_path` | Path to the updates config file.                    |
@@ -37,6 +38,7 @@ Given below is a sample configuration for the WSO2 Micro Integrator.
 
 ```toml
 [server_configuration]
+diagnostic_tool_enabled = "true"
 deployment_toml_path = "../conf/deployment.toml"
 logs_directory = "../repository/logs"
 updates_config_path = "../updates/config.json"