From beee37734152a53874d6306e7983375c4b531550 Mon Sep 17 00:00:00 2001 From: chamindi Abayadeera Date: Fri, 29 Sep 2023 12:18:59 +0530 Subject: [PATCH 1/3] Correct Apim developer assigned urls --- .../administer/key-managers/configure-forgerock-connector.md | 2 +- .../api-gateway/api-gateways-with-dedicated-backends.md | 2 +- .../migration-guide-from-ballerina-api-microgateway.md | 2 +- .../removing-specific-request-headers-from-response.md | 2 +- .../authorization/role-based-access-control-using-xacml.md | 2 +- .../rate-limiting/advanced-topics/custom-throttling.md | 2 +- en/docs/install-and-setup/install-and-setup-overview.md | 2 +- .../setup/deployment-best-practices/backup-recovery.md | 2 +- .../deployment-best-practices/performance-test-results-mi.md | 4 ++-- .../security-guidelines-for-production-deployment.md | 3 +-- .../setup/mi-setup/brokers/configure-with-hornetq.md | 2 +- .../setup/mi-setup/databases/setting-up-mssql.md | 2 +- .../setup/si-setup/configuring-business-rules-deployment.md | 2 +- .../setup/si-setup/configuring-data-sources.md | 2 +- .../setup/si-setup/general-data-protection-regulations.md | 2 +- .../setup/si-setup/supporting-different-transports.md | 2 +- en/docs/integrate/develop/create-kubernetes-project.md | 2 +- en/docs/integrate/develop/using-remote-micro-integrator.md | 2 +- .../configuring-log4j2-properties.md | 2 +- .../employeehealthandwellness.md | 2 +- .../connectors/file-connector/file-connector-config.md | 2 +- .../google-spreadsheet-connector-example.md | 2 +- .../smpp-connector/smpp-inbound-endpoint-example.md | 2 +- .../log-in-to-the-dev-portal-using-social-media.md | 2 +- .../property-reference/accessing-properties-with-xpath.md | 5 ++--- .../routing-requests-based-on-message-content.md | 2 +- en/docs/tutorials/scenarios/scenario12-message-delivery.md | 2 +- .../streaming-tutorials/creating-business-rules-templates.md | 2 +- .../triggering-integrations-via-micro-integrator.md | 2 +- 29 files changed, 31 insertions(+), 33 deletions(-) diff --git a/en/docs/administer/key-managers/configure-forgerock-connector.md b/en/docs/administer/key-managers/configure-forgerock-connector.md index 7b690db3c5..9b12d4fc40 100644 --- a/en/docs/administer/key-managers/configure-forgerock-connector.md +++ b/en/docs/administer/key-managers/configure-forgerock-connector.md @@ -72,7 +72,7 @@ Follow the instructions given below to configure the ForgeRock Authorization Ser [![ForgeRock create OAuth Provider]({{base_path}}/assets/img/administer/forgerock-create-oauth-provider.png)]({{base_path}}/assets/img/administer/forgerock-create-oauth-provider.png) 5. Navigate to **Root Realm** -> **Services** add Oauth2 provider as a new service as follows, - [![ForgeRock add OAuth Provider]({{base_path}}/assets/img/administer/forgerock-add-oauth-provider.png)]({{base_path}}/assets/img/administer/forgerock-create-add-provider.png) + [![ForgeRock add OAuth Provider]({{base_path}}/assets/img/administer/forgerock-create-oauth-provider.png)]({{base_path}}/assets/img/administer/forgerock-create-oauth-provider.png) 6. Configure the scopes and the signing algorithm of the created OAuth 2.0 Provider using the following values. diff --git a/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/api-gateways-with-dedicated-backends.md b/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/api-gateways-with-dedicated-backends.md index fe2beedaf1..07bc04493e 100644 --- a/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/api-gateways-with-dedicated-backends.md +++ b/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/api-gateways-with-dedicated-backends.md @@ -60,7 +60,7 @@ Follow the steps below to configure a parameterized endpoint as the API endpoint } } ``` - 2. Add the created JAR file into the `/repository/components/lib` folder of each Gateway. You can download a sample JAR file [here](https://docs.wso2.com/download/attachments/80713829/env-resolver-1.0.0.jar?version=2&modificationDate=1512985782000&api=v2).

+ 2. Add the created JAR file into the `/repository/components/lib` folder of each Gateway. You can download a sample JAR file [here](https://wso2.com/documentation/?version=2&modificationDate=1512985782000&api=v2).

3. Add the following sequence to the `/repository/deployment/server/synapse-configs/sequences` folder of each Gateway. ``` java diff --git a/en/docs/deploy-and-publish/deploy-on-gateway/choreo-connect/migration-guide-from-ballerina-api-microgateway.md b/en/docs/deploy-and-publish/deploy-on-gateway/choreo-connect/migration-guide-from-ballerina-api-microgateway.md index 6186f7e439..59843584fd 100644 --- a/en/docs/deploy-and-publish/deploy-on-gateway/choreo-connect/migration-guide-from-ballerina-api-microgateway.md +++ b/en/docs/deploy-and-publish/deploy-on-gateway/choreo-connect/migration-guide-from-ballerina-api-microgateway.md @@ -122,7 +122,7 @@ Choreo Connect v4.2.0 is only compatible with WSO2 API Manager 4.2.0. Hence you 1. Upgrade WSO2 API Manager version to 4.2.0. - A detailed explanation regarding the above includes in [here]({{base_path}}/install-and-setup/upgrading-wso2-api-manager/320-to-410/upgrading-from-320-to-410/). + A detailed explanation regarding the above includes in [here]({{base_path}}/install-and-setup/upgrading-wso2-api-manager/upgrading-api-manager/ ). 2. Connect Choreo Connect microgateway to API Manager 4.2.0 as a gateway. diff --git a/en/docs/design/api-policies/regular-gateway-policies/removing-specific-request-headers-from-response.md b/en/docs/design/api-policies/regular-gateway-policies/removing-specific-request-headers-from-response.md index 9fabdec55f..24706c2e10 100644 --- a/en/docs/design/api-policies/regular-gateway-policies/removing-specific-request-headers-from-response.md +++ b/en/docs/design/api-policies/regular-gateway-policies/removing-specific-request-headers-from-response.md @@ -12,7 +12,7 @@ To remove request headers from responses for per API or globally, add the name o ``` bash tab="Sample" ``` -Check out [Changing the Default Mediation Flow of API Requests]({{base_path}}/deploy-and-publish/deploy-on-gateway/api-gateway/message-mediation/changing-the-default-mediation-flow-of-api-requests) to learn on how to +Check out [Changing the Default Mediation Flow of API Requests]({{base_path}}/design/api-policies/attach-policy/) to learn on how to add the above mediation policy per API or globally. ## Handling Error Responses diff --git a/en/docs/design/api-security/authorization/role-based-access-control-using-xacml.md b/en/docs/design/api-security/authorization/role-based-access-control-using-xacml.md index 649081caef..138d3a5636 100644 --- a/en/docs/design/api-security/authorization/role-based-access-control-using-xacml.md +++ b/en/docs/design/api-security/authorization/role-based-access-control-using-xacml.md @@ -118,7 +118,7 @@ Based on the requirement, a single API is exposed to add or retrieve order info ![]({{base_path}}/assets/attachments/103334839/103334831.png) -11. Download the [entitlement-1.0-SNAPSHOT.jar](https://docs.wso2.com/download/attachments/57743363/entitlement-1.0-SNAPSHOT.jar?version=1&modificationDate=1515491619000&api=v2) and add it to the `/repository/components/lib` directory. This JAR file contains the `APIEntitlementCallbackHandler` class which passes the username, HTTP verb and the resource path to the XACML entitlement server. If you want to view the source code of the JAR, go [here](https://github.com/nadeesha5814/XACML-APIManager) . +11. Download the [entitlement-1.0-SNAPSHOT.jar](https://github.com/nadeesha5814/XACML-APIManager/blob/master/target/entitlement-1.0-SNAPSHOT.jar) and add it to the `/repository/components/lib` directory. This JAR file contains the `APIEntitlementCallbackHandler` class which passes the username, HTTP verb and the resource path to the XACML entitlement server. If you want to view the source code of the JAR, go [here](https://github.com/nadeesha5814/XACML-APIManager) . 12. Restart the server once the JAR file is added. diff --git a/en/docs/design/rate-limiting/advanced-topics/custom-throttling.md b/en/docs/design/rate-limiting/advanced-topics/custom-throttling.md index fcfb9e4f70..b05b02c2e0 100644 --- a/en/docs/design/rate-limiting/advanced-topics/custom-throttling.md +++ b/en/docs/design/rate-limiting/advanced-topics/custom-throttling.md @@ -1,6 +1,6 @@ # Custom Rate Limiting -Custom rate limiting allows system administrators to define dynamic rules for specific use cases, which are applied globally across all tenants. When a custom rate limiting policy is created, it is possible to define any policy you like. The Traffic Manager acts as the global rate limiting engine and is based on the same technology as WSO2 Complex Event Processor (CEP), which uses the [Siddhi query language](https://docs.wso2.com/complex-event-processor/SiddhiQL+Guide+3.1) . Users are therefore able to create their own custom rate limiting policies by writing custom Siddhi queries. The specific combination of attributes being checked in the policy need to be defined as the key (also called the key template). The key template usually includes a predefined format and a set of predefined parameters. It can contain a combination of allowed keys separated by a colon (:), where each key must start with the prefix $. The following keys can be used to create custom rate limiting policies: +Custom rate limiting allows system administrators to define dynamic rules for specific use cases, which are applied globally across all tenants. When a custom rate limiting policy is created, it is possible to define any policy you like. The Traffic Manager acts as the global rate limiting engine and is based on the same technology as WSO2 Complex Event Processor (CEP), which uses the [Siddhi query language](https://siddhi-io.github.io/siddhi/) . Users are therefore able to create their own custom rate limiting policies by writing custom Siddhi queries. The specific combination of attributes being checked in the policy need to be defined as the key (also called the key template). The key template usually includes a predefined format and a set of predefined parameters. It can contain a combination of allowed keys separated by a colon (:), where each key must start with the prefix $. The following keys can be used to create custom rate limiting policies: `resourceKey, userId, apiContext, apiVersion, appTenant, apiTenant, appId, clientIp` diff --git a/en/docs/install-and-setup/install-and-setup-overview.md b/en/docs/install-and-setup/install-and-setup-overview.md index 06f33c1826..4ee29cec72 100644 --- a/en/docs/install-and-setup/install-and-setup-overview.md +++ b/en/docs/install-and-setup/install-and-setup-overview.md @@ -579,7 +579,7 @@ To set up and configure the Micro Integrator runtime, see the topics given below Securing the Management API
  • - Customizing Error Messages + Customizing Error Messages
    • diff --git a/en/docs/install-and-setup/setup/deployment-best-practices/backup-recovery.md b/en/docs/install-and-setup/setup/deployment-best-practices/backup-recovery.md index a8815ac00f..e083f29355 100644 --- a/en/docs/install-and-setup/setup/deployment-best-practices/backup-recovery.md +++ b/en/docs/install-and-setup/setup/deployment-best-practices/backup-recovery.md @@ -21,4 +21,4 @@ We also recommend the following: The following steps include how to recover your setup using the backups: 1. Recover the hot-deployment artifacts by replacing the MI_HOME/repository directory with the backed up copy. -2. To recover the databases, follow the recovery strategy recommended by the databases you are using. For information on supported and tested databases, see [Tested Database Management Systems](https://docs.wso2.com/display/compatibility/Tested+DBMSs). +2. To recover the databases, follow the recovery strategy recommended by the databases you are using. For information on supported and tested databases, see [Tested Database Management Systems](https://wso2docs.atlassian.net/wiki/spaces/compatibility/pages/20578309/Tested+DBMSs ). diff --git a/en/docs/install-and-setup/setup/deployment-best-practices/performance-test-results-mi.md b/en/docs/install-and-setup/setup/deployment-best-practices/performance-test-results-mi.md index 80299bb8b1..daf0cf00fc 100644 --- a/en/docs/install-and-setup/setup/deployment-best-practices/performance-test-results-mi.md +++ b/en/docs/install-and-setup/setup/deployment-best-practices/performance-test-results-mi.md @@ -105,10 +105,10 @@ The complete results can be found [here](https://github.com/wso2/micro-integrato #### Throughput (requests/sec) vs. concurrent users The following results compare the throughput against the number of concurrent users for different message sizes. -![Throughput]({{base_path}}/assets/img/setup-and-install/performance-test-results/mi/catplot-throughput-2G-0ms.png) +![Throughput](/assets/img/setup-and-install/performance-test-results/mi/catplot-average-response-time-2G-0ms.png) #### Average response time (ms) vs. concurrent users The following results compare the average response time of the Micro Integrator server against the number of users for different message sizes. -![Response Time]({{base_path}}/assets/img/setup-and-install/performance-test-results/mi/catplot-average-response-time-2G-0ms.png) +![Response Time](/assets/img/setup-and-install/performance-test-results/mi/catplot-average-response-time-2G-0ms.png) diff --git a/en/docs/install-and-setup/setup/deployment-best-practices/security-guidelines-for-production-deployment.md b/en/docs/install-and-setup/setup/deployment-best-practices/security-guidelines-for-production-deployment.md index d41d93eaf9..35914c6713 100644 --- a/en/docs/install-and-setup/setup/deployment-best-practices/security-guidelines-for-production-deployment.md +++ b/en/docs/install-and-setup/setup/deployment-best-practices/security-guidelines-for-production-deployment.md @@ -557,8 +557,7 @@ data cleanup task in high load scenarios. To mitigate this, configure the follow session_data with the required chunk size. This value is in the number of records and depends on the database type and server capacity. It also depends on the amount of load generated by single sign-on (SSO). A higher value increases the chances of deadlocks and a lower value increases the time it takes for a cleanup.

    [session_data]
 cleanup.clean_expired_session_data_in_chunks_of = 8192
    -

    For more information on configuring sessions in production, see Authentication Session Persistence in the WSO2 API Manager +

    For more information on configuring sessions in production, see Authentication Session Persistence in the WSO2 API Manager documentation.

    diff --git a/en/docs/install-and-setup/setup/mi-setup/brokers/configure-with-hornetq.md b/en/docs/install-and-setup/setup/mi-setup/brokers/configure-with-hornetq.md index fd21246d0b..c9e07a37ea 100644 --- a/en/docs/install-and-setup/setup/mi-setup/brokers/configure-with-hornetq.md +++ b/en/docs/install-and-setup/setup/mi-setup/brokers/configure-with-hornetq.md @@ -261,7 +261,7 @@ Now you have configured the JBoss EAP Server. The next section describes how to !!! Note After copying the `jboss-client.jar` file from the `EAP_HOME/bin/client` directory to the `MI_HOME/lib` directory, be sure to remove the `javax.jms` package from the `jboss-client.jar` file. - [![delete package]({{base_path}}/assets/img/integrate/broker-configs/hornetq/delete-package.jpg)]({{base_path}}/assets/img/assets/img/integrate/broker-configs/hornetq/delete-package.jpg) + [![delete package]({{base_path}}/assets/img/integrate/broker-configs/hornetq/delete-package.jpg)]({{base_path}}/assets/img/integrate/broker-configs/hornetq/delete-package.jpg) Now you have configured WSO2 Micro Integrator with HornetQ embedded in a JBoss EAP server. diff --git a/en/docs/install-and-setup/setup/mi-setup/databases/setting-up-mssql.md b/en/docs/install-and-setup/setup/mi-setup/databases/setting-up-mssql.md index d7d765a0d6..dd3322984f 100644 --- a/en/docs/install-and-setup/setup/mi-setup/databases/setting-up-mssql.md +++ b/en/docs/install-and-setup/setup/mi-setup/databases/setting-up-mssql.md @@ -32,7 +32,7 @@ You can run the scripts on one database instance or set up separate instances fo mssql_cluster.sql - This script creates the database tables that are required for cluster coordination (i.e., coordinating the server nodes in your VM deployment).This is only applicable if you have stateful integration artifacts deployed in a clustered setup. + This script creates the database tables that are required for cluster coordination (i.e., coordinating the server nodes in your VM deployment).This is only applicable if you have stateful integration artifacts deployed in a clustered setup. diff --git a/en/docs/install-and-setup/setup/si-setup/configuring-business-rules-deployment.md b/en/docs/install-and-setup/setup/si-setup/configuring-business-rules-deployment.md index d88fb507a0..b406b6d509 100644 --- a/en/docs/install-and-setup/setup/si-setup/configuring-business-rules-deployment.md +++ b/en/docs/install-and-setup/setup/si-setup/configuring-business-rules-deployment.md @@ -42,7 +42,7 @@ To configure a Streaming Integrator node to use specific rules templates, follow ``` !!! tip - If required, you can enter a specific rule template under multiple nodes as shown below. Before doing so, ensure the you have selected **Many** for the **Instance Count** field of the template. For more information, see [Creating a Business Rules Template]({{base_path}}/use-cases/streaming-tutorials/creating-business-rules-templates/creating-business-rules-templates/#creating-a-business-rules-template).

    + If required, you can enter a specific rule template under multiple nodes as shown below. Before doing so, ensure the you have selected **Many** for the **Instance Count** field of the template. For more information, see [Creating a Business Rules Template]({{base_path}}/use-cases/streaming-tutorials/creating-business-rules-templates/#creating-a-business-rules-template).

    ```yaml deployment_configs: - :: diff --git a/en/docs/install-and-setup/setup/si-setup/configuring-data-sources.md b/en/docs/install-and-setup/setup/si-setup/configuring-data-sources.md index 02f6b3531a..4741507fcf 100644 --- a/en/docs/install-and-setup/setup/si-setup/configuring-data-sources.md +++ b/en/docs/install-and-setup/setup/si-setup/configuring-data-sources.md @@ -344,7 +344,7 @@ The following tables explain the default data sources configured in the Streamin Database Access Requirement - To display information relating to the status of your Streaming Integrator deployment, the Status Dashboard needs to retrieve carbon metrics data, registered Streaming Integrator server details and authentication details within the cluster from the database. For more information, see Monitoring Stream Processor . + To display information relating to the status of your Streaming Integrator deployment, the Status Dashboard needs to retrieve carbon metrics data, registered Streaming Integrator server details and authentication details within the cluster from the database. For more information, see Monitoring Stream Processor . Required/Optional diff --git a/en/docs/install-and-setup/setup/si-setup/general-data-protection-regulations.md b/en/docs/install-and-setup/setup/si-setup/general-data-protection-regulations.md index 05a76d9a4f..73485fc3f9 100644 --- a/en/docs/install-and-setup/setup/si-setup/general-data-protection-regulations.md +++ b/en/docs/install-and-setup/setup/si-setup/general-data-protection-regulations.md @@ -239,7 +239,7 @@ All configurations related to this tool can be found inside the `/wso2/ - **Log file name regex**: The regex patterns defined in all the files in the `/wso2/tools/identity-anonymization-tool/conf/log-config` directory are considered. -For information on changing these configurations, see [Configuring the config.json file](https://docs.wso2.com/display/ADMIN44x/Removing+References+to+Deleted+User+Identities+in+WSO2+Products#RemovingReferencestoDeletedUserIdentitiesinWSO2Products-Configuringtheconfig.jsonfile) in the Product Administration Guide. +For information on changing these configurations, see [Configuring the config.json file](https://wso2docs.atlassian.net/wiki/spaces/ADMIN44x/pages/6687734/Removing+References+to+Deleted+User+Identities+in+WSO2+Products#RemovingReferencestoDeletedUserIdentitiesinWSO2Products-MasterConfigConfiguringthemasterconfigurationfile) in the Product Administration Guide. ### Running the Forget-me tool in the standalone mode diff --git a/en/docs/install-and-setup/setup/si-setup/supporting-different-transports.md b/en/docs/install-and-setup/setup/si-setup/supporting-different-transports.md index b94ce50445..3391cf69b5 100644 --- a/en/docs/install-and-setup/setup/si-setup/supporting-different-transports.md +++ b/en/docs/install-and-setup/setup/si-setup/supporting-different-transports.md @@ -45,7 +45,7 @@ To configure the **Apache ActiveMQ** message broker, follow the steps below: 1. Install [Apache ActiveMQ JMS](http://activemq.apache.org/). !!!info - This guide uses ActiveMQ versions 5.7.0 - 5.9.0. If you want to use a later version, for instructions on the necessary changes to the configuration steps, go to [Apache ActiveMQ Documentation](http://activemq.apache.org/activemq-580-release.html). + This guide uses ActiveMQ versions 5.7.0 - 5.9.0. If you want to use a later version, for instructions on the necessary changes to the configuration steps, go to [Apache ActiveMQ Documentation](https://activemq.apache.org/activemq-5008000-release). 2. Download the `activemq-client-5.x.x.jar` from [here](https://activemq.apache.org/components/classic/download/). diff --git a/en/docs/integrate/develop/create-kubernetes-project.md b/en/docs/integrate/develop/create-kubernetes-project.md index 8f095f8423..d52d8a7b70 100644 --- a/en/docs/integrate/develop/create-kubernetes-project.md +++ b/en/docs/integrate/develop/create-kubernetes-project.md @@ -2,7 +2,7 @@ Create a Kubernetes Exporter if you want to deploy your integration solutions in a Kubernetes environment. -The Kubernetes Exporter allows you to package multiple [integration modules]({{base_path}}/integrate/develop/create-integration-project) into a single Docker image. Also, a file named **integration_cr.yaml** is generated, which can be used to carry out Kubernetes deployments based on the [API K8s Operator]({{base_path}}/setup/deployment/kubernetes_deployment/#ei-kubernetes-k8s-operator). +The Kubernetes Exporter allows you to package multiple [integration modules]({{base_path}}/integrate/develop/create-integration-project) into a single Docker image. Also, a file named **integration_cr.yaml** is generated, which can be used to carry out Kubernetes deployments based on the [API K8s Operator]({{base_path}}/install-and-setup/setup/kubernetes-operators/k8s-api-operator/manage-integrations/integration-deployments/). ## Creating the Kubernetes project diff --git a/en/docs/integrate/develop/using-remote-micro-integrator.md b/en/docs/integrate/develop/using-remote-micro-integrator.md index 54aa8875bc..687e871984 100644 --- a/en/docs/integrate/develop/using-remote-micro-integrator.md +++ b/en/docs/integrate/develop/using-remote-micro-integrator.md @@ -34,7 +34,7 @@ However, when your solutions are ready to be moved to your production environmen !!! Note - If you selected an Enterprise Integrator server in the previous step, enter the port details required for an Enterprise Integrator. - - If you are already running another server on these ports, give unused ports. See [Default ports](../../setup/changing_default_ports) of the Micro Integrator for more information. + - If you are already running another server on these ports, give unused ports. See [Default ports]({{base_path}}/install-and-setup/setup/deployment-best-practices/changing-the-default-ports-with-offset/) of the Micro Integrator for more information. ## Deploy and run artifacts in a remote instance diff --git a/en/docs/observe/micro-integrator/classic-observability-logs/configuring-log4j2-properties.md b/en/docs/observe/micro-integrator/classic-observability-logs/configuring-log4j2-properties.md index 6b57775cb7..43b9c60184 100644 --- a/en/docs/observe/micro-integrator/classic-observability-logs/configuring-log4j2-properties.md +++ b/en/docs/observe/micro-integrator/classic-observability-logs/configuring-log4j2-properties.md @@ -203,7 +203,7 @@ This logger generates logs for APIs deployed in the Micro Integrator. It refers logger.API_LOG.name=API_LOGGER.TestAPI ``` - See the instructions on [monitoring per-API logs]({{base_path}}/install-and-setup/setup/mi-setup/observability/logs/enabling-logs-for-api). + See the instructions on [monitoring per-API logs]({{base_path}}/integrate/develop/monitoring-api-level-logs/). ```xml tab='API_LOGGER' logger.API_LOGGER.name= API_LOGGER diff --git a/en/docs/reference/connectors/ceridiandayforce-connector/employee-personal-information/employeehealthandwellness.md b/en/docs/reference/connectors/ceridiandayforce-connector/employee-personal-information/employeehealthandwellness.md index 545bcacfbf..055a60b3fe 100644 --- a/en/docs/reference/connectors/ceridiandayforce-connector/employee-personal-information/employeehealthandwellness.md +++ b/en/docs/reference/connectors/ceridiandayforce-connector/employee-personal-information/employeehealthandwellness.md @@ -65,7 +65,7 @@ Given below is a sample response for this operation. ``` **Related Dayforce documentation** - +Using the following link to register and thereafter peruse the relevant documentation [https://developers.dayforce.com/Build/API-Explorer/Employee-Personal-Information/Employee-Health-and-Wellness/GET-Employee-Health-and-Wellness.aspx](https://developers.dayforce.com/Build/API-Explorer/Employee-Personal-Information/Employee-Health-and-Wellness/GET-Employee-Health-and-Wellness.aspx) ### Sample configuration diff --git a/en/docs/reference/connectors/file-connector/file-connector-config.md b/en/docs/reference/connectors/file-connector/file-connector-config.md index de5b4156ff..288b4da317 100644 --- a/en/docs/reference/connectors/file-connector/file-connector-config.md +++ b/en/docs/reference/connectors/file-connector/file-connector-config.md @@ -15,7 +15,7 @@ The File connector can be used to deal with two types of file systems: There are different connection configurations that can be used for the above protocols. They contain a common set of configurations and some additional configurations specific to the protocol. -types of file connections +types of file connections !!! Note diff --git a/en/docs/reference/connectors/google-spreadsheet-connector/google-spreadsheet-connector-example.md b/en/docs/reference/connectors/google-spreadsheet-connector/google-spreadsheet-connector-example.md index e325fa5921..f08f22a9e3 100644 --- a/en/docs/reference/connectors/google-spreadsheet-connector/google-spreadsheet-connector-example.md +++ b/en/docs/reference/connectors/google-spreadsheet-connector/google-spreadsheet-connector-example.md @@ -39,7 +39,7 @@ Follow these steps to set up the Integration Project and the Connector Exporter 3. Provide the API name as `SpreadsheetAPI` and the API context as `/insert`. 4. First we will create the `/insert` resource. Right click on the API Resource and go to **Properties** view. We use a URL template called `/insert` as we have two API resources inside single API. The method will be `Post`. - Adding the API resource. + Adding the API resource. 5. In this operation we are going to receive input from the user, which are `properties`, `sheets`, `range` and `values`. - properties - It can provide the spreadsheet properties such as title of the spreadsheet. diff --git a/en/docs/reference/connectors/smpp-connector/smpp-inbound-endpoint-example.md b/en/docs/reference/connectors/smpp-connector/smpp-inbound-endpoint-example.md index 22ff308f4b..079ebe9f17 100644 --- a/en/docs/reference/connectors/smpp-connector/smpp-inbound-endpoint-example.md +++ b/en/docs/reference/connectors/smpp-connector/smpp-inbound-endpoint-example.md @@ -4,7 +4,7 @@ The SMPP inbound endpoint allows you to consume messages from SMSC. The WSO2 SMP ## What you'll build -This scenario demonstrates how the SMPP inbound endpoint works as an message consumer. In this scenario, you should have a connectivity with SMSC (Short Message service center) via SMPP protocol. For this we are using **SMSC simulator** to accomplish the required requirements. Please refer the [Setting up the SMPP Connector]({{base_path}}/reference/connectors/smpp-connector/smpp-connector-configuration/) documentation for more information. +This scenario demonstrates how the SMPP inbound endpoint works as an message consumer. In this scenario, you should have a connectivity with SMSC (Short Message service center) via SMPP protocol. For this we are using **SMSC simulator** to accomplish the required requirements. Please refer the [Setting up the SMPP Connector]({{base_path}}/reference/connectors/smpp-connector/smpp-connector-configuration) documentation for more information. The SMPP inbound endpoint is listening to the Short Message service center for consuming messages using defined port number in the Inbound Endpoint configurations. If SMSC generates some message by itself or user injects SMS messages to the SMSC, the WSO2 SMPP Inbound Endpoint will receive and notify. Then just log the SMS message content. In your own scenarios, you can inject that message into the mediation flow for getting the required output. diff --git a/en/docs/reference/customize-product/customizations/log-in-to-the-dev-portal-using-social-media.md b/en/docs/reference/customize-product/customizations/log-in-to-the-dev-portal-using-social-media.md index 0f0c5fdaca..b514cce69e 100644 --- a/en/docs/reference/customize-product/customizations/log-in-to-the-dev-portal-using-social-media.md +++ b/en/docs/reference/customize-product/customizations/log-in-to-the-dev-portal-using-social-media.md @@ -33,7 +33,7 @@ You can integrate WSO2 Identity Server with WSO2 API Manager and use your social 7. Go to **Set Up the Facebook SDK for JavaScript** and click **Next** until the steps are complete. 8. Click **Settings** and select **Basic**. You can find your `App ID` and the `App Secret` as shown in the image below. - ![Facebook App Id]({{base_path}}/assets/img/learn/appId-facebook.png) + ![Facebook App Id](/assets/img/learn/appid-facebook.png) 9. Select a **Category** for you application. diff --git a/en/docs/reference/mediators/property-reference/accessing-properties-with-xpath.md b/en/docs/reference/mediators/property-reference/accessing-properties-with-xpath.md index 332ee4a941..59a5dfe631 100644 --- a/en/docs/reference/mediators/property-reference/accessing-properties-with-xpath.md +++ b/en/docs/reference/mediators/property-reference/accessing-properties-with-xpath.md @@ -492,8 +492,7 @@ In this example, the property definition, \ is equivalent to \. Similarly, you -can use $trp prefix with [HTTP Transport -Properties](_HTTP_Transport_Properties_) . +can use $trp prefix with [HTTP Transport Properties]({{base_path}}/reference/mediators/property-reference/http-transport-properties) . ### $url @@ -534,7 +533,7 @@ The prefix used to get the URI element of a request URL. The prefix used to refer to a particular parameter value passed externally by an invoker such as the [Call Template -Mediator](_Call_Template_Mediator_) . +Mediator]({{base_path}}/reference/mediators/call-template-mediator/) . **Example of $func usage:** diff --git a/en/docs/tutorials/integration-tutorials/routing-requests-based-on-message-content.md b/en/docs/tutorials/integration-tutorials/routing-requests-based-on-message-content.md index 88f9ea576d..863713cb30 100755 --- a/en/docs/tutorials/integration-tutorials/routing-requests-based-on-message-content.md +++ b/en/docs/tutorials/integration-tutorials/routing-requests-based-on-message-content.md @@ -119,7 +119,7 @@ Let's create three different HTTP endpoints for the above services. You have now created the three endpoints for the hospital back-end services that will be used to make appointment reservations. !!! Tip - You can also create a single endpoint where the differentiation of the hospital name can be handled using a variable in the URI template. See the tutorial on [Exposing Several Services as a Single Service](exposing-several-services-as-a-single-service). + You can also create a single endpoint where the differentiation of the hospital name can be handled using a variable in the URI template. See the tutorial on [Exposing Several Services as a Single Service]({{base_path}}/tutorials/integration-tutorials/exposing-several-services-as-a-single-service). Using three different endpoints is advantageous when the back-end services are very different from one another and/or when there is a requirement to configure error handling differently for each of them. diff --git a/en/docs/tutorials/scenarios/scenario12-message-delivery.md b/en/docs/tutorials/scenarios/scenario12-message-delivery.md index 1e9adf3c89..d76a95a21b 100644 --- a/en/docs/tutorials/scenarios/scenario12-message-delivery.md +++ b/en/docs/tutorials/scenarios/scenario12-message-delivery.md @@ -14,7 +14,7 @@ This will be implemented with Message Store and Message Processor in Micro Integ Guaranteed Message Delivery -If you look at the `docker-compose.yml` file, you can see that ``CATERING_SERVICE_EP`` is defined as ‘[http://www.urldoesnotexist.com](http://www.urldoesnotexist.com)’ under mi-runtime service. If you send a request to this endpoint, it will fail and the message will be stored in the Message Store database. +If you look at the `docker-compose.yml` file, you can see that ``CATERING_SERVICE_EP`` is defined as ‘`http://www.urldoesnotexist.com`’ under mi-runtime service. If you send a request to this endpoint, it will fail and the message will be stored in the Message Store database. ## Step 1: Invoke the API diff --git a/en/docs/use-cases/streaming-tutorials/creating-business-rules-templates.md b/en/docs/use-cases/streaming-tutorials/creating-business-rules-templates.md index e9815ce015..2e8a97258d 100644 --- a/en/docs/use-cases/streaming-tutorials/creating-business-rules-templates.md +++ b/en/docs/use-cases/streaming-tutorials/creating-business-rules-templates.md @@ -695,7 +695,7 @@ There are two permission levels for a business rules application: This section covers how to configure Business Rules Manager permissions. !!!tip "Before you begin:" - Before configuring Business Rules Manager permissions, the user roles to be assigned permissions must be already defined in the user store with the required user IDs. For detailed instructions, see [User Management](https://docs.wso2.com/display/SP440/User+Management). + Before configuring Business Rules Manager permissions, the user roles to be assigned permissions must be already defined in the user store with the required user IDs. For detailed instructions, see [User Management](https://wso2docs.atlassian.net/wiki/spaces/SP4xx/pages/29130933/User+Guide). You need to define the roles related to the Business Rules Manager under the `wso2.business.rules.manager` component namespace in the `/conf/server/deployment.yaml` file. diff --git a/en/docs/use-cases/streaming-tutorials/triggering-integrations-via-micro-integrator.md b/en/docs/use-cases/streaming-tutorials/triggering-integrations-via-micro-integrator.md index 4959ed6a57..4a0907a357 100644 --- a/en/docs/use-cases/streaming-tutorials/triggering-integrations-via-micro-integrator.md +++ b/en/docs/use-cases/streaming-tutorials/triggering-integrations-via-micro-integrator.md @@ -8,7 +8,7 @@ To understand this, consider a scenario where the Streaming Integrator receives ## Before you begin -- [Start WSO2 Streaming Integrator server]({{base_path}}/setup/installing-si#starting-the-si-server). +- [Start WSO2 Streaming Integrator server]({{base_path}}/install-and-setup/install/installing-the-product/installing-si). - [Start Streaming Integrator Tooling]({{base_path}}/develop/streaming-apps/streaming-integrator-studio-overview#starting-streaming-integrator-tooling). From 2e03ddfdc650b7f22f88ad9f0cd672fc20e3f31e Mon Sep 17 00:00:00 2001 From: chamindi Abayadeera Date: Sat, 30 Sep 2023 00:09:37 +0530 Subject: [PATCH 2/3] Correct the dev corrected errors --- .../key-managers/configure-custom-connector.md | 2 +- .../installing-api-m-as-a-windows-service.md | 2 +- .../configuring-different-endpoint-types.md | 2 +- .../setup/si-setup/production-checklist.md | 2 +- .../reference/connectors/develop-connectors.md | 2 +- .../get-credentials-for-google-spreadsheet.md | 17 +++++++---------- .../redis-connector/redis-connector-overview.md | 2 +- .../salesforcebulk-connector-example.md | 2 +- .../salesforcebulk-connector-example.md | 2 +- .../adding-internationalization.md | 2 +- .../customizing-api-template-for-gateway.md | 4 ++-- .../datasource-configuration-parameters.md | 2 +- .../rabbitmq-transport-parameters.md | 2 +- 13 files changed, 20 insertions(+), 23 deletions(-) diff --git a/en/docs/administer/key-managers/configure-custom-connector.md b/en/docs/administer/key-managers/configure-custom-connector.md index 66e0adf192..ba97eb9ee2 100644 --- a/en/docs/administer/key-managers/configure-custom-connector.md +++ b/en/docs/administer/key-managers/configure-custom-connector.md @@ -461,4 +461,4 @@ When registering a third-party Identity Provider as a Key Manager in the Admin P !!! tip If you want to generate the tokens with scopes, make sure that those scopes are defined in the Authorization Server. -6. You can now use the generated token to [invoke an API]({{base_path}}/en/docs/consume/invoke-apis/invoke-apis-using-tools/include-additional-headers-in-the-api-console.md). \ No newline at end of file +6. You can now use the generated token to [invoke an API]({{base_path}}/consume/invoke-apis/invoke-apis-using-tools/include-additional-headers-in-the-api-console/). \ No newline at end of file diff --git a/en/docs/install-and-setup/install/installing-the-product/installing-api-m-as-a-windows-service.md b/en/docs/install-and-setup/install/installing-the-product/installing-api-m-as-a-windows-service.md index 78de4e664a..ec7fe47899 100644 --- a/en/docs/install-and-setup/install/installing-the-product/installing-api-m-as-a-windows-service.md +++ b/en/docs/install-and-setup/install/installing-the-product/installing-api-m-as-a-windows-service.md @@ -20,7 +20,7 @@ The configuration file used for wrapping Java Applications by YAJSW is `wrapper. !!! info - If you want to set additional properties from an external registry at runtime, store sensitive information like usernames and passwords for connecting to the registry in a properties file and secure it with [secure vault]({{base_path}}/administer/product-security/General/logins-and-passwords/admin-carbon-secure-vault-implementation). + If you want to set additional properties from an external registry at runtime, store sensitive information like usernames and passwords for connecting to the registry in a properties file and secure it with [secure vault]({{base_path}}/install-and-setup/setup/security/logins-and-passwords/working-with-encrypted-passwords/). !!! note diff --git a/en/docs/install-and-setup/setup/api-controller/advanced-topics/configuring-different-endpoint-types.md b/en/docs/install-and-setup/setup/api-controller/advanced-topics/configuring-different-endpoint-types.md index 0835fc2fe4..29fe514019 100644 --- a/en/docs/install-and-setup/setup/api-controller/advanced-topics/configuring-different-endpoint-types.md +++ b/en/docs/install-and-setup/setup/api-controller/advanced-topics/configuring-different-endpoint-types.md @@ -225,7 +225,7 @@ The following is an example parameters file for this scenario. (Make sure to spe ``` !!! tip - When importing an API, if you are specifying the endpoint type as `dynamic`, you can include a message mediation policy with a `To` header inside the `Sequences` directory of your API Project. (Refer [Adding Dynamic Endpoints]({{base_path}}/deploy-and-publish/deploy-on-gateway/api-gateway/message-mediation/adding-dynamic-endpoints/#adding-dynamic-endpoints) to learn more about Dynamic endpoints and message mediations associated with that.) + When importing an API, if you are specifying the endpoint type as `dynamic`, you can include a message mediation policy with a `To` header inside the `Sequences` directory of your API Project. (Refer [Adding Dynamic Endpoints]({{base_path}}/design/api-policies/regular-gateway-policies/adding-dynamic-endpoints//) to learn more about Dynamic endpoints and message mediations associated with that.) ### AWS Lambda Endpoints diff --git a/en/docs/install-and-setup/setup/si-setup/production-checklist.md b/en/docs/install-and-setup/setup/si-setup/production-checklist.md index 2aef9a6bbb..7316d817a5 100644 --- a/en/docs/install-and-setup/setup/si-setup/production-checklist.md +++ b/en/docs/install-and-setup/setup/si-setup/production-checklist.md @@ -38,7 +38,7 @@ If you want to allow business users with limited coding knowledge to write busin ## Monitoring the Streaming Integrator -To monitor the performance of your Streaming Integrator setup, configure WSO2 SI to publish its statistics in Dashboards as described in [Configuring Grafana Dashboards]({{base_path}}/install-and-setup/setup/si-setup/setting-up-grafana-dashboards). +To monitor the performance of your Streaming Integrator setup, configure WSO2 SI to publish its statistics in Dashboards as described in [Configuring Grafana Dashboards]({{base_path}}/https://observe/streaming-integrator/setting-up-si-statistics-dashboards/) diff --git a/en/docs/reference/connectors/develop-connectors.md b/en/docs/reference/connectors/develop-connectors.md index 94b815ae1c..1758f45e1a 100644 --- a/en/docs/reference/connectors/develop-connectors.md +++ b/en/docs/reference/connectors/develop-connectors.md @@ -785,7 +785,7 @@ Connection timeout is an environment dependent configuration. Developers may def **Handle errors meaningfully. Use ERROR CODES** Sometimes it is required to handle errors within the connector. Sometimes it is required to let the calling template handle the error. Sometimes it is required to forward the error message back to the connector operation invoker as it is. It is good to analyze use cases, and then design which errors need to be handled at which instance. However, it is a good practice to define and use error codes. -Please read the [WSO2 Error Code guide]({{base_path}}/reference/error_handling/). +Please read the [WSO2 Error Code guide]({{base_path}}/troubleshooting/error-handling/#error-codes). **Write test cases** diff --git a/en/docs/reference/connectors/google-spreadsheet-connector/get-credentials-for-google-spreadsheet.md b/en/docs/reference/connectors/google-spreadsheet-connector/get-credentials-for-google-spreadsheet.md index cc2eaaf2fb..a40b1e63ec 100644 --- a/en/docs/reference/connectors/google-spreadsheet-connector/get-credentials-for-google-spreadsheet.md +++ b/en/docs/reference/connectors/google-spreadsheet-connector/get-credentials-for-google-spreadsheet.md @@ -1,4 +1,4 @@ -# Get Credentials for Google Spreadsheet +the next screen# Get Credentials for Google Spreadsheet To obtain the Access Token, Client Id, Client Secret and Refresh Token, we need to follow the below steps. @@ -11,16 +11,13 @@ To obtain the Access Token, Client Id, Client Secret and Refresh Token, we need 4. Click **Configure consent screen** in the next screen. - Consent Screen - + Consent Screen
    5. Provide the Application Name as `SpreadsheetConnector` in the Consent Screen. - Consent Screen - + Consent Screen
    6. Click Create credentials and click OAuth client ID. - Create Credentials - + Create Credentials
    7. Enter the following details in the Create OAuth client ID screen and click Create. | Type | Name | @@ -29,12 +26,12 @@ To obtain the Access Token, Client Id, Client Secret and Refresh Token, we need | Name | SpreadsheetConnector | | Authorized redirect URIs | https://developers.google.com/oauthplayground | - +
    8. A Client ID and a Client Secret are provided. Keep them saved. Credentials - +
    9. Click Library on the side menu, search for **Google Sheets API** and click on it. - +
    10. Click **Enable** to enable the Google Sheets API. Enable Google Sheets API diff --git a/en/docs/reference/connectors/redis-connector/redis-connector-overview.md b/en/docs/reference/connectors/redis-connector/redis-connector-overview.md index c651b641c6..55c27f7544 100644 --- a/en/docs/reference/connectors/redis-connector/redis-connector-overview.md +++ b/en/docs/reference/connectors/redis-connector/redis-connector-overview.md @@ -20,7 +20,7 @@ For older versions, see the details in the connector store. ## Redis Connector documentation -* **[Setting up the Redis Environment]({{base_path}}/reference/connectors/redis-connector/redis-connector-configuration/)**: This involves setting up the Redis server and a backend to test the flow. +* **[Setting up the Redis Environment]({{base_path}}/reference/connectors/redis-connector/2.4.x/redis-connector-reference/)**: This involves setting up the Redis server and a backend to test the flow. * **[Redis Connector Example]({{base_path}}/reference/connectors/redis-connector/redis-connector-example/)**: This example demonstrates how to work with the Redis Connector and access the Redis server using Redis commands. diff --git a/en/docs/reference/connectors/salesforce-connectors/salesforcebulk-connector-example.md b/en/docs/reference/connectors/salesforce-connectors/salesforcebulk-connector-example.md index 1b5af421d8..28bcd0b124 100644 --- a/en/docs/reference/connectors/salesforce-connectors/salesforcebulk-connector-example.md +++ b/en/docs/reference/connectors/salesforce-connectors/salesforcebulk-connector-example.md @@ -42,7 +42,7 @@ Now follow the steps below to add configurations to the `insertEmployeeBulkRecor 1. Initialize the connector. - 1. Follow these steps to [generate the Access Tokens for Salesforce]({{base_path}}/reference/connectors/salesforce-connectors/salesforcebulk-connector-configuration) and obtain the Client Id, Client Secret, Access Token, and Refresh Token. + 1. Follow these steps to [generate the Access Tokens for Salesforce]({{base_path}}/includes/reference/connectors/salesforce-connectors/sf-access-token-generation) and obtain the Client Id, Client Secret, Access Token, and Refresh Token. 2. Navigate into the **Palette** pane and select the graphical operations icons listed under **Salesforcebulk Connector** section. Then drag and drop the `init` operation into the Design pane. diff --git a/en/docs/reference/connectors/salesforcebulk-connector/salesforcebulk-connector-example.md b/en/docs/reference/connectors/salesforcebulk-connector/salesforcebulk-connector-example.md index 5f4739f2a4..9f4db38d0e 100644 --- a/en/docs/reference/connectors/salesforcebulk-connector/salesforcebulk-connector-example.md +++ b/en/docs/reference/connectors/salesforcebulk-connector/salesforcebulk-connector-example.md @@ -42,7 +42,7 @@ Now follow the steps below to add configurations to the `insertEmployeeBulkRecor 1. Initialize the connector. - 1. Follow these steps to [generate the Access Tokens for Salesforce](salesforcebulk-connector-configuration/) and obtain the Client Id, Client Secret, Access Token, and Refresh Token. + 1. Follow these steps to [generate the Access Tokens for Salesforce]({{base_path}}/includes/reference/connectors/salesforce-connectors/sf-access-token-generation/) and obtain the Client Id, Client Secret, Access Token, and Refresh Token. 2. Navigate into the **Palette** pane and select the graphical operations icons listed under **Salesforcebulk Connector** section. Then drag and drop the `init` operation into the Design pane. diff --git a/en/docs/reference/customize-product/customizations/adding-internationalization.md b/en/docs/reference/customize-product/customizations/adding-internationalization.md index 4a8f3f3a79..8108f2e458 100644 --- a/en/docs/reference/customize-product/customizations/adding-internationalization.md +++ b/en/docs/reference/customize-product/customizations/adding-internationalization.md @@ -182,7 +182,7 @@ Follow the instructions below to change the direction of the UI: ``` !!! tip - Learn more about [Tenant theming]({{base_path}}/consume/customizations/customizing-the-developer-portal/overriding-developer-portal-theme/#uploading-via-the-admin-portal-tenants-only). + Learn more about [Tenant theming]({{base_path}}/reference/customize-product/customizations/customizing-the-developer-portal/overriding-developer-portal-theme/#uploading-devportal-theme-via-the-admin-portal-tenants-only). ## Enabling the language switch diff --git a/en/docs/reference/customize-product/extending-api-manager/extending-gateway/customizing-api-template-for-gateway.md b/en/docs/reference/customize-product/extending-api-manager/extending-gateway/customizing-api-template-for-gateway.md index 69fc6750f0..14a2711193 100644 --- a/en/docs/reference/customize-product/extending-api-manager/extending-gateway/customizing-api-template-for-gateway.md +++ b/en/docs/reference/customize-product/extending-api-manager/extending-gateway/customizing-api-template-for-gateway.md @@ -6,7 +6,7 @@ An API's gateway configuration file(Synapse configuration) content contains API ## Engaging a custom handler based on API Properties -In API Manager, you can implement and engage custom handlers to customize the default mediation flow of API requests. See [Writing a custom handler]() for more information. The [API properties]({base_path}/learn/design-api/create-api/adding-custom-properties-to-apis/) can be used to conditionally engage these custom handlers for APIs. +In API Manager, you can implement and engage custom handlers to customize the default mediation flow of API requests. See [Writing a custom handler]() for more information. The [API properties]({{base_path}}/design/create-api/adding-custom-properties-to-apis/) can be used to conditionally engage these custom handlers for APIs. Following steps illustrate how you can enable a custom handler for a selected set of APIs which are having a particular property value. @@ -74,7 +74,7 @@ Following steps illustrate how you can enable a custom handler for a selected se 3. Save the changes. - 4. Add `custom_authentication=true` as an [additional property]({base_path}/learn/design-api/create-api/adding-custom-properties-to-apis/) for those APIs which you need to enable the custom handler. + 4. Add `custom_authentication=true` as an [additional property]({{base_path}}/design/create-api/adding-custom-properties-to-apis/) for those APIs which you need to enable the custom handler. Add Custom Property diff --git a/en/docs/reference/synapse-properties/data-services/datasource-configuration-parameters.md b/en/docs/reference/synapse-properties/data-services/datasource-configuration-parameters.md index 04144d997b..17fc0663d4 100644 --- a/en/docs/reference/synapse-properties/data-services/datasource-configuration-parameters.md +++ b/en/docs/reference/synapse-properties/data-services/datasource-configuration-parameters.md @@ -7,7 +7,7 @@ The datasource configuration in a data service specifies how the service connect Shown below is the synapse configuration of an RDBMS datasource in a data service. See the complete list of [JDBC connection pool parameters](http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html) and the [DBCP configuration guide](http://commons.apache.org/proper/commons-dbcp/configuration.html) for more details. !!! Note - The default values of the following parameters might not be optimal for the specific hardware/server configurations in your environment. We recommend that you carry out load tests in your environment to tune them accordingly. See [Tuning Datasource Configuration Parameters]({{base_path}}/install-and-setup/performance_tuning/jdbc_tuning) for information on how you can select the best values for these parameters. + The default values of the following parameters might not be optimal for the specific hardware/server configurations in your environment. We recommend that you carry out load tests in your environment to tune them accordingly. See [Tuning Datasource Configuration Parameters](/install-and-setup/setup/mi-setup/performance_tuning/jdbc_tuning/) for information on how you can select the best values for these parameters. ```toml diff --git a/en/docs/reference/synapse-properties/transport-parameters/rabbitmq-transport-parameters.md b/en/docs/reference/synapse-properties/transport-parameters/rabbitmq-transport-parameters.md index 226f518945..87fb616f11 100644 --- a/en/docs/reference/synapse-properties/transport-parameters/rabbitmq-transport-parameters.md +++ b/en/docs/reference/synapse-properties/transport-parameters/rabbitmq-transport-parameters.md @@ -3,7 +3,7 @@ When you implement an integration use case that requires a RabbitMQ connection, you can use the following RabbitMQ parameters in your [proxy service]({{base_path}}/integrate/develop/creating-artifacts/creating-a-proxy-service) artifact. !!! Info - The Micro Integrator can listen to a RabbitMQ instance or send messages to a RabbitMQ instance only if the RabbitMQ transport listener and sender are enabled and configured at the server level. Read about the [RabbitMQ transport]({{base_path}}/install-and-setup/brokers/configure-with-rabbitMQ). + The Micro Integrator can listen to a RabbitMQ instance or send messages to a RabbitMQ instance only if the RabbitMQ transport listener and sender are enabled and configured at the server level. Read about the [RabbitMQ transport]({{base_path}}/install-and-setup/setup/mi-setup/performance_tuning/rabbitmq_transport_tuning/). ## Service-Level Parameters (Receiving Messages) From d54d4d8f6c19119e7ffad28476f334326e43ddc2 Mon Sep 17 00:00:00 2001 From: chamindi Abayadeera Date: Mon, 2 Oct 2023 15:16:07 +0530 Subject: [PATCH 3/3] Correct PR reviews comments --- en/docs/install-and-setup/install-and-setup-overview.md | 2 +- .../employee-personal-information/employeehealthandwellness.md | 2 +- .../get-credentials-for-google-spreadsheet.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/en/docs/install-and-setup/install-and-setup-overview.md b/en/docs/install-and-setup/install-and-setup-overview.md index 4ee29cec72..b383f13b9f 100644 --- a/en/docs/install-and-setup/install-and-setup-overview.md +++ b/en/docs/install-and-setup/install-and-setup-overview.md @@ -579,7 +579,7 @@ To set up and configure the Micro Integrator runtime, see the topics given below Securing the Management API
  • - Customizing Error Messages + Customizing Error Messages
    • diff --git a/en/docs/reference/connectors/ceridiandayforce-connector/employee-personal-information/employeehealthandwellness.md b/en/docs/reference/connectors/ceridiandayforce-connector/employee-personal-information/employeehealthandwellness.md index 055a60b3fe..24fe6f9a1f 100644 --- a/en/docs/reference/connectors/ceridiandayforce-connector/employee-personal-information/employeehealthandwellness.md +++ b/en/docs/reference/connectors/ceridiandayforce-connector/employee-personal-information/employeehealthandwellness.md @@ -65,7 +65,7 @@ Given below is a sample response for this operation. ``` **Related Dayforce documentation** -Using the following link to register and thereafter peruse the relevant documentation +Use the following link to register and thereafter peruse the relevant documentation [https://developers.dayforce.com/Build/API-Explorer/Employee-Personal-Information/Employee-Health-and-Wellness/GET-Employee-Health-and-Wellness.aspx](https://developers.dayforce.com/Build/API-Explorer/Employee-Personal-Information/Employee-Health-and-Wellness/GET-Employee-Health-and-Wellness.aspx) ### Sample configuration diff --git a/en/docs/reference/connectors/google-spreadsheet-connector/get-credentials-for-google-spreadsheet.md b/en/docs/reference/connectors/google-spreadsheet-connector/get-credentials-for-google-spreadsheet.md index a40b1e63ec..fd0eac92b8 100644 --- a/en/docs/reference/connectors/google-spreadsheet-connector/get-credentials-for-google-spreadsheet.md +++ b/en/docs/reference/connectors/google-spreadsheet-connector/get-credentials-for-google-spreadsheet.md @@ -1,4 +1,4 @@ -the next screen# Get Credentials for Google Spreadsheet +# Get Credentials for Google Spreadsheet To obtain the Access Token, Client Id, Client Secret and Refresh Token, we need to follow the below steps.