Skip to content

Proofreading task for ms-windows #9547

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: development
Choose a base branch
from
Open

Proofreading task for ms-windows #9547

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e3260ea
proofreading task for ms-windows
OlufunkeMoronfolu May 19, 2025
2bbcfa3
adding missing image
OlufunkeMoronfolu May 23, 2025
2d318bf
image renaming
OlufunkeMoronfolu May 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 13 additions & 12 deletions content/en/docs/deployment/on-premises-design/ms-windows/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@ This document describes the installation and configuration of Mendix software on

## Prerequisites {#Prerequisites}

To set up an environment to run Mendix applications, you will need to install the Mendix software. For each Mendix application that will be run, a separate user (service) account is required. This section presents an overview of the setup.
To set up an environment to run Mendix applications, you will need to install the Mendix software. You must also create a separate user (service) account for each Mendix application you plan to run.

{{< figure src="/attachments/deployment/on-premises-design/ms-windows/18580733.png" >}}
{{< figure src="/attachments/deployment/on-premises-design/ms-windows/ms-windows-setup.png" >}}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This new image doesn't seem to be part of the PR.
Have you forgotten to add it - or is it in a different folder somewhere?
image

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing this out. Now fixed.


Before starting this how-to, make sure you have the following prerequisites:

Expand All @@ -40,7 +40,7 @@ Before starting this how-to, make sure you have the following prerequisites:
* MS IIS URL Rewrite installed (for more information, see [URL Rewrite](https://www.iis.net/downloads/microsoft/url-rewrite))
* Java Runtime, version depending on your Mendix Server Distribution. See [System Requirements](/refguide/system-requirements/#java) for more information.
* The Mendix Deployment Archive (MDA) of your Mendix project
* The Mendix server distribution corresponding with your Mendix Studio Pro version (see the [Mendix Marketplace](https://marketplace.mendix.com/link/studiopro/))
* The Mendix server distribution corresponding to your Mendix Studio Pro version (see the [Mendix Marketplace](https://marketplace.mendix.com/link/studiopro/))
* A database with sufficient security rights

* Suitable database servers are MariaDB, MS SQL Server, MySQL, Oracle Database and PostgreSQL. See [System Requirements](/refguide/system-requirements/#databases) for more information
Expand All @@ -52,20 +52,17 @@ Before starting this how-to, make sure you have the following prerequisites:
To download and install the Mendix Service Console, follow these steps:

1. Download the latest version of the [Mendix Service Console](https://marketplace.mendix.com/link/component/223425) module from the Marketplace.

{{< figure src="/attachments/deployment/on-premises-design/ms-windows/service_console_download.png" >}}

2. Install the Mendix Service Console by following the installation wizard.

3. Start the Mendix Service Console after completing the installation. The first time you launch the application, a popup will be shown (it will always be shown if no valid location is configured for the apps and server files):
3. Start the Mendix Service Console after completing the installation. The first time you launch the application, you will see a dialog box (it will always be shown if no valid location is configured for the apps and server files):

{{< figure src="/attachments/deployment/on-premises-design/ms-windows/service_console_first_run.png" >}}

4. Click **Yes**. The **Preferences** dialog box will be shown:

{{< figure src="/attachments/deployment/on-premises-design/ms-windows/18580730.png" >}}

5. In the **Preferences** dialog box, enter a **Location of apps and server files**. This location is used for storing your app files and Mendix server files. Mendix recommends using a directory:
5. In the **Preferences** dialog box, enter the **Location of apps and server files**. This location is used for storing your app files and Mendix server files. Mendix recommends using a directory:

* that is NOT on the system partition
* where you can easily control the security rights
Expand Down Expand Up @@ -101,7 +98,7 @@ To deploy a Mendix app using the Mendix Service Console, follow these steps:

{{< figure src="/attachments/deployment/on-premises-design/ms-windows/service_console_selectapp.png" >}}

6. Now select the **MDA** file that was [created in Studio Pro](/refguide/create-deployment-package-dialog/) and contains your application logic. After the installation of your MDA file, you will see which Mendix server (Mendix Runtime) version is needed.
6. Now select the **MDA** file that was [created in Mendix Studio Pro](/refguide/create-deployment-package-dialog/) and contains your application logic. After the installation of your MDA file, you will see which Mendix server (Mendix Runtime) version is needed.

7. Configure the **Database Settings**:

Expand Down Expand Up @@ -137,7 +134,7 @@ In order to use the proxy functionality within ARR, you need to enable this feat
To create a website, follow these steps:

1. Open the IIS Manager.
2. In the **Connections** pane, click the **Sites** node in the tree. If **Default Website** or any other website is present under **Sites**, please check if it is being used.
2. In the **Connections** pane, click the **Sites** node in the tree. If **Default Website** or any other website is present under **Sites**, check if it is being used.
3. Right-click **Sites** and select **Add Web Site**.
4. In the **Add Web Site** dialog box, enter a friendly name for your web site in the **Web site name** field.
5. In the **Physical path** field, enter the physical path of your application-project-web folder (for example, *D:\Mendix\Apps\Application\Project\Web*).
Expand Down Expand Up @@ -203,7 +200,11 @@ Rule | Name | Pattern | Rewrite URL
10 | p | `^(p/)(.*)` | `http://localhost:8080/{R:1}{R:2}`
11 | manifest | `^(manifest.webmanifest)(.*)` | `http://localhost:8080/{R:1}{R:2}`

Follow the instructions below and replace *[Name]* with the name of the rule in the table above, *[Pattern]* with the regular expression pattern, and *[Rewrite URL]* with the Rewrite URL. Note that some patterns contain a trailing slash, `/`, when they need to point to an exact path (for example, `/ws-doc/mydoc/1234`).
Follow the instructions below and replace *[Name]* with the name of the rule in the table above, *[Pattern]* with the regular expression pattern, and *[Rewrite URL]* with the Rewrite URL.

{{% alert color="info" %}}
Some patterns contain a trailing slash, `/`, when they need to point to an exact path (for example, `/ws-doc/mydoc/1234`).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find this example confusing as the example given does not include a trailing slash.
With a lot of thought I can see what it means (the pattern for ws-doc is ^(ws-doc/)(.*) which has a trailing slash as part of it, which means that the path has to begin with ws-doc/ and cannot be ws-documentation/.

Also, the example has a leading / which doesn't seem to be in the patterns.

If you can't get a quick response from the Slack channel, then perhaps put this on the Jira backlog to pick up later?

Copy link
Collaborator Author

@OlufunkeMoronfolu OlufunkeMoronfolu May 23, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your insight and pointing this out. Following up right away.

{{% /alert %}}

1. Open the IIS Manager and navigate to the website you want to manage.
2. In the **Features View**, double-click **URL Rewrite**.
Expand All @@ -214,7 +215,7 @@ Follow the instructions below and replace *[Name]* with the name of the rule in
7. Set **Using** to *Regular Expressions*.
8. In the **Pattern** field, enter `[Pattern]`.
9. In the **Action** section, set **Action type** to *Rewrite*.
10. In the **Rewrite URL** field, enter `[Rewrite URL]` (in the rules above this is always `http://localhost:8080/{R:1}{R:2}`).
10. In the **Rewrite URL** field, enter `[Rewrite URL]` (in the rules above, this is always `http://localhost:8080/{R:1}{R:2}`).
11. Ensure the **Append query string** checkbox is set to *true* (checked).
12. Click **Apply**.
13. Click **Back to Rules**.
Expand Down
Binary file removed static/attachments/deployment/on-premises-design/ms-windows/18580733.png
View file
Open in desktop
Binary file not shown.
Binary file added static/attachments/deployment/on-premises-design/ms-windows/ms-windows-setup.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed ...tachments/deployment/on-premises-design/ms-windows/service_console_download.png
View file
Open in desktop
Binary file not shown.