Merge pull request #1089 from wso2/4.3.0

Sync main branch with 4.3.0 branch

Author: chanikag

en/docs/develop/customizations/creating-custom-task-scheduling.md

@@ -433,7 +433,19 @@ In order to deploy and run the project, refer the [build and run]({{base_path}}/
 
 ### Start the back-end service
 
-Download the backend service from [GitHub](https://github.com/wso2-docs/WSO2_EI/blob/master/Back-End-Service/stockquote-deployable-jar-2.2.2.jar) and run it.
+1. Download the [back-end service](https://github.com/wso2-docs/WSO2_EI/blob/master/Back-End-Service/axis2Server.zip).
+2. Extract the downloaded zip file.
+3. Open a terminal, navigate to the `axis2Server/bin/` directory inside the extracted folder.
+4. Execute the following command to start the axis2server with the SimpleStockQuote back-end service:
+
+    === "On MacOS/Linux"   
+          ```bash
+          sh axis2server.sh
+          ```
+    === "On Windows"               
+          ```bash
+          axis2server.bat
+          ```
 
 ### Create the text file
 

en/docs/install-and-setup/setup/deployment-best-practices/basic-health-checks.md

@@ -11,13 +11,41 @@ The health check API gives a **ready** status only if all the CApps are deployed
 
 `http://localhost:9201/healthz`
 
+!!! Note
+    The health check can be performed over HTTPS APIs by adding the below configuration to the deployment.toml file.
+
+    ```toml
+    
+    [readiness_probe]
+    protocols = "http https"
+    ```
+    
+    Sample Request: 
+    ```
+    curl GET 'https://localhost:9164/healthz' -k
+    ```
+
 ### Liveness Check API
 
 The liveness check API gives a **ready** status when the server starts successfully.
 The health check API serves at:
 
 `http://localhost:9201/liveness`
 
+!!! Note
+    The liveness check can be performed over HTTPS APIs by adding the below configuration to the deployment.toml file.
+
+    ```toml
+    
+    [liveness_probe]
+    protocols = "http https"
+    ```
+    
+    Sample Request: 
+    
+    curl GET 'https://localhost:9164/liveness' -k
+    ```
+
 !!! Note
     If you are running the server instance with a different port offset other than the default (which is 10), the heath
     check API serves at 9191 + offset.  

en/docs/reference/connectors/amazonsqs-connector/2.x/amazonsqs-connector-2.x-example.md

@@ -20,7 +20,7 @@ If you do not want to configure this yourself, you can simply [get the project](
 
      - [apache-client-2.20.26.jar ](https://mvnrepository.com/artifact/software.amazon.awssdk/apache-client/2.26.20)
      - [auth-2.26.20.jar](https://mvnrepository.com/artifact/software.amazon.awssdk/auth/2.26.20) 
-     - [aws-core-2.26.20.jar](https://mvnrepository.com/artifact/software.amazon.awssdk/sdk-core/2.26.20)
+     - [aws-core-2.26.20.jar](https://mvnrepository.com/artifact/software.amazon.awssdk/aws-core/2.26.20)
      - [checksums-2.26.20.jar](https://mvnrepository.com/artifact/software.amazon.awssdk/checksums/2.26.20) 
      - [checksums-spi-2.26.20.jar](https://mvnrepository.com/artifact/software.amazon.awssdk/checksums-spi/2.26.20) 
      - [endpoints-spi-2.26.20.jar](https://mvnrepository.com/artifact/software.amazon.awssdk/endpoints-spi/2.26.20) 

en/docs/reference/connectors/smpp-connector/smpp-connector-config.md

@@ -269,6 +269,34 @@ To use the SMPP connector, need to have a SMSC connection. To create a SMSC conn
          <td>Content of the SMS message.</td>
          <td>Yes</td>
       </tr>
+    <tr>
+        <td>smscDeliveryReceipt</td>
+        <td>This parameter is used to request an SMSC delivery receipt. The following values can be defined:
+            <table>
+                <tr>
+                    <th>Value</th>
+                    <th>Description</th>
+                </tr>
+                <tr>
+                    <td>DEFAULT</td>
+                    <td>No SMSC Delivery Receipt requested. This is the default value.</td>
+                </tr>
+                <tr>
+                    <td>SUCCESS_FAILURE</td>
+                    <td>SMSC Delivery Receipt requested where final delivery outcome is delivery success or failure.</td>
+                </tr>
+                <tr>
+                    <td>FAILURE</td>
+                    <td>SMSC Delivery Receipt requested where the final delivery outcome is delivery failure.</td>
+                </tr>
+                <tr>
+                    <td>SUCCESS</td>
+                    <td>SMSC Delivery Receipt requested where the final delivery outcome is success. This is supported from SMPP 5.0.</td>
+                </tr>
+           </table>
+        </td>
+        <td>Optional</td>
+    </tr>
       <tr>
          <td>esmClass</td>
          <td>

en/docs/reference/connectors/snowflake-connector/snowflake-connector-reference.md

@@ -2,7 +2,7 @@
 
 The following operations allow you to work with the Snowflake Connector. Click an operation name to see parameter details.
 
-## Snowflake Connector Configuration
+## Snowflake connector configuration
 
 ??? note "Connection configuration"
     In the 'Properties' section of each operation, users can configure connection-related information. Once the configuration is created, it can be re-used in other operations.
@@ -32,6 +32,11 @@ The following operations allow you to work with the Snowflake Connector. Click a
             <td>Snowflake Account password.</td>
             <td>Yes</td>
         </tr>
+        <tr>
+            <td>keepAlive</td>
+            <td>Indicates whether to create a new connection after a period of inactivity in the session. Accepted values: `true`: Snowflake keeps the session active indefinitely as long as the connection is active, even if there is no activity, `false`: A new connection is created again after four hours of inactivity. The default value is `false`</td>
+            <td>No</td>
+        </tr>
     </table>