You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/support/_index.md
+31-25Lines changed: 31 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,11 +101,11 @@ If there is an issue with the Mendix Platform that affects multiple customers, o
101
101
102
102
### Reporting Issues
103
103
104
-
If, after your analysis, you suspect there is an issue with the Mendix Platform (or if you have questions about your analysis), you can reach out to Mendix Support. We will provide pointers on how to solve the issues yourself or redirect you to Expert Services for further assistance. If we suspect a platform issue, we will involve second- and third-line support for confirmation and, if it is a platform issue, we will fix it. If the issue is commercial (for example, because your app requires a larger app container or more file storage), we may refer you to your Customer Success Manager directly.
104
+
If, after your analysis, you suspect there is an issue with the Mendix Platform (or if you have questions about your analysis), you can reach out to Mendix Support. We will provide guidance on how to resolve the issues yourself or direct you to Expert Services for further assistance. If we suspect a platform issue, we will involve second- and third-line support for confirmation and, if it is a platform issue, we will fix it. If the issue is commercial (for example, because your app requires a larger app container or additional file storage), we may refer you directly to your Customer Success Manager.
105
105
106
106
### Large-Scale Testing
107
107
108
-
You may sometimes want to perform testing on your app which could impact cloud operations. This might include the following:
108
+
You may want to perform testing on your app, which could impact cloud operations. This might include the following:
109
109
110
110
* Load test
111
111
* Performance test
@@ -115,15 +115,15 @@ Your SLA contains the following clause:
115
115
116
116
> Without first obtaining the prior written consent of Mendix, Customer may not intentionally perform any actions, such as load tests, performance tests, or similar tests that might interfere with or disrupt the integrity or performance of the App Platform or Cloud Services.
117
117
118
-
If you are planning this sort of testing you must raise a ticket with Mendix Support and include as much information as possible, including:
118
+
If you are planning this sort of testing, you must raise a ticket with Mendix Support and include as much information as possible, including:
119
119
120
120
* type of test
121
121
* IP addresses
122
122
* environment IDs
123
123
* exact timings
124
124
* contact details of parties directly involved – including any third parties who are assisting
125
125
126
-
Please provide this information as early as possible, at least two weeks in advance of the test date. Mendix may refuse permission to do some kinds of test if they break local laws or pose too high a risk to the Mendix infrastructure or other customers.
126
+
Please provide this information as early as possible, at least two weeks in advance of the test date. Mendix may refuse permission to conduct certain types of tests if they violate local laws or pose an excessive risk to the Mendix infrastructure or other customers.
127
127
128
128
If you want to perform penetration tests, your Customer Success Manager (CSM) can provide you with an indemnification agreement. This should be signed by all parties, confirming the information above, and agreeing that your tests are legal and do not impact other customers. If you don't know who your CSM is, Mendix Support can provide you with their contact details.
129
129
@@ -135,84 +135,90 @@ Mendix cannot change any standard settings for your environments to support your
135
135
136
136
## Product Support Period
137
137
138
-
Mendix supports the current major release and the two prior major releases (and we support each major release for a minimum of 24 months). Because of this, Mendix recommends upgrading your apps to the latest version of Studio Pro at least once a year. We will reach out to you in time if you are running on a version that will become unsupported so that you have ample time to perform an upgrade.
138
+
Mendix supports the current major release and the two prior major releases (and we support each major release for a minimum of 24 months). Because of this, Mendix recommends upgrading your apps to the latest version of Studio Pro at least once a year. We will reach out to you in time if you are running on a version that will become unsupported, so that you have ample time to perform an upgrade.
139
139
140
140
## Components of the Mendix Stack {#components}
141
141
142
142
These are the components of the Mendix stack described in the section above. Please read an extensive description of the [Mendix architecture](https://www.mendix.com/evaluation-guide/enterprise-capabilities/architecture-intro) in the Evaluation Guide.
143
143
144
144
### Database, File Storage, and Network
145
145
146
-
The database component includes the database service and the creating, storing, downloading, uploading, and restoring of backups.
147
-
The file storage component refers to the file storage service and the creating, storing, downloading, uploading, and restoring of backups.
148
-
The network component consists of the connection between the front-facing web server and the application, between the application and an external end point.
146
+
The database component includes the database service and the creation, storage, downloading, uploading, and restoration of backups.
147
+
The file storage component refers to the file storage service and the creation, storage, downloading, uploading, and restoration of backups.
148
+
The network component consists of the connection between the front-facing web server and the application, between the application and an external endpoint.
149
149
150
150
Mendix Support can analyze this component if your app is running on Mendix Cloud or Mendix Cloud Dedicated.
151
151
152
152
### Infrastructure
153
153
154
-
The infrastructure component includes all web servers, runtime servers, and database servers, with their Operating Systems and configuration.
154
+
The infrastructure component includes all web servers, runtime servers, and database servers, with their Operating Systems and configurations.
155
155
156
156
Mendix Support can analyze this component if your app is running on Mendix Cloud or Mendix Cloud Dedicated.
157
157
158
+
Mendix is responsible for setting up and maintaining the component, as well as applying the default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers.
159
+
158
160
### Container Runtime Platform
159
161
160
162
The container runtime platform refers to the platform for managing, creating, destroying, and scaling of runtime containers. In Mendix Cloud and Mendix Cloud Dedicated, Kubernetes is used.
161
163
162
-
Mendix Support can analyze this component if your app is running on Mendix Cloud or Mendix Cloud Dedicated. If it is running on SAP BTP instead, the selected third party can analyze this component.
164
+
Mendix Support can analyze this component if your app is running on Mendix Cloud or Mendix Cloud Dedicated.
165
+
166
+
Mendix is responsible for setting up and maintaining the component, as well as applying the default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers. If it is running on SAP BTP instead, the selected third party can analyze this component.
163
167
164
168
### Buildpack, m2ee, and Service Console
165
169
166
-
The Mendix buildpacks for [Cloud Foundry](https://github.com/mendix/cf-mendix-buildpack) and [Docker](https://github.com/mendix/docker-mendix-buildpack) are available in GitHub repositories. The documentation for the buildpacks and m2ee tools is contained within these GitHub repositories and, because they are released under an Open Source license, the code can be inspected and the functionality and options can be understood by customers who wish to use these buildpacks.
170
+
The Mendix buildpacks for [Cloud Foundry](https://github.com/mendix/cf-mendix-buildpack) and [Docker](https://github.com/mendix/docker-mendix-buildpack) are available in GitHub repositories. The documentation for the buildpacks and m2ee tools is contained within these GitHub repositories. Because they are released under an open-source license, the code can be inspected, and the functionality and options can be understood by customers who wish to use these buildpacks.
167
171
168
-
If you want to run Mendix apps on a Unix-like server you will need the [m2ee tools](https://github.com/mendix/m2ee-tools), available on GitHub. Read more about installing on systems running Unix-like operating systems in [Linux Deployment](/developerportal/deploy/linux/).
172
+
If you want to run Mendix apps on a Unix-like server, you will need the [m2ee tools](https://github.com/mendix/m2ee-tools), available on GitHub. Read more about installing on systems running Unix-like operating systems in [Linux Deployment](/developerportal/deploy/linux/).
169
173
170
-
Mendix Support can analyze these components if your app is running on Mendix Cloud or Mendix Cloud Dedicated. Because Mendix has no control over the context in which the buildpack or m2ee tools are run outside of Mendix Cloud and Mendix Cloud Dedicated, you will have to demonstrate that the bug is in the supported component by showing the behavior independently from the context in which you are using it.
174
+
Mendix Support can analyze these components if your app is running on Mendix Cloud or Mendix Cloud Dedicated. Mendix is responsible for setting up and maintaining the component, as well as applying the default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers.
171
175
172
-
If you want additional features or some other change in a buildpack or m2ee tools, you can make a Pull Request, create an Issue in the GitHub repository, or contact [Mendix Support](https://support.mendix.com/).
176
+
Because Mendix has no control over the context in which the buildpack or m2ee tools are run outside of Mendix Cloud and Mendix Cloud Dedicated, you will have to demonstrate that the bug is in the supported component by showing the behavior independently from the context in which you are using it.
173
177
174
-
If you wan to run Mendix apps on Windows server you will need the [Windows Service](/releasenotes/studio-pro/windows-service/). The release notes and installation manual can be found in the [Windows Service](/releasenotes/studio-pro/windows-service/) release notes. Read more about installing on systems running Windows operating systems in [Microsoft Windows](/developerportal/deploy/deploy-mendix-on-microsoft-windows/).
178
+
If you require additional features or other changes in a buildpack or m2ee tools, you can submit a Pull Request, create an Issue in the GitHub repository, or contact [Mendix Support](https://support.mendix.com/).
175
179
176
-
If you want additional features or some other change in the Windows Service, you can contact [Mendix Support](https://support.mendix.com/).
180
+
If you want to run Mendix apps on a Windows server, you will need the [Windows Service](/releasenotes/studio-pro/windows-service/). The release notes and installation manual can be found in the [Windows Service](/releasenotes/studio-pro/windows-service/) release notes. Read more about installing on systems running Windows operating systems in [Microsoft Windows](/developerportal/deploy/deploy-mendix-on-microsoft-windows/).
181
+
182
+
For additional features or other changes in the Windows Service, contact [Mendix Support](https://support.mendix.com/).
177
183
178
184
### Application Operation
179
185
180
186
The application operation component is used for stopping and starting environments and configuring constants, scheduled events, and runtime settings.
181
187
182
-
Mendix Support can analyze this component if your app is running on Mendix Cloud, Mendix Cloud Dedicated, Mendix on Kubernetes Connected, or SAP BTP through the Mendix Portal.
188
+
Mendix Support can analyze this component if your app is running on Mendix Cloud, Mendix Cloud Dedicated, Mendix on Kubernetes Connected, or SAP BTP through the Mendix Portal. Mendix is responsible for setting up and maintaining the component, as well as applying default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers.
183
189
184
190
### Logs and Metrics
185
191
186
-
The logs component takes care of viewing and downloading application log files.
192
+
The logs component handles viewing and downloading application log files.
187
193
The metrics component refers to viewing application metrics.
188
194
189
-
Mendix Support can analyze these components if your app is running on Mendix Cloud or Mendix Cloud Dedicated.
195
+
Mendix Support can analyze these components if your app is running on Mendix Cloud or Mendix Cloud Dedicated. Mendix is responsible for setting up and maintaining the component, as well as applying the default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers.
190
196
191
197
### Deployment Pipeline
192
198
193
-
The deployment pipeline takes care of creating and deploying deployment packages. Read more about deployment options in [Deploying Apps](/deployment/).
199
+
The deployment pipeline handles creating and deploying deployment packages. Read more about deployment options in [Deploying Apps](/deployment/).
194
200
195
201
Mendix Support can analyze this component if your app is running on Mendix Cloud, Mendix Cloud Dedicated, Mendix on Kubernetes Connected, or SAP BTP through the Mendix Portal.
196
202
197
203
### Runtime
198
204
199
-
The runtime component includes the Mendix Runtime, and all of its supported features.
205
+
The runtime component includes the Mendix Runtime and all of its supported features.
200
206
Please read all about the Mendix Runtime in [Mendix Runtime](/refguide/runtime/).
201
207
202
208
Mendix Support needs application logs to analyze this component. Because Mendix has no control over the context in which the runtime is run, outside of Mendix Cloud and Mendix Cloud Dedicated, you will have to demonstrate that the bug is in the supported component by showing the behavior independently from the context in which you are using it.
203
209
204
210
### Marketplace Components
205
211
206
-
Platform-supported Marketplace content refers to all Marketplace content marked as platform-supported in the Mendix Marketplace. Community-supported Marketplace content includes all Marketplace content not marked as platform-supported in the Mendix Marketplace
212
+
Platform-supported Marketplace content refers to all Marketplace content marked as platform-supported in the Mendix Marketplace. Community-supported Marketplace content includes all Marketplace content not marked as platform-supported in the Mendix Marketplace.
207
213
208
-
For details about the levels of Support for Marketplace components, see the [Marketplace Content Support](/appstore/marketplace-content-support/) section in *Marketplace Overview*.
214
+
For details about the levels of Support for Marketplace components, refer to the [Marketplace Content Support](/appstore/marketplace-content-support/) section in *Marketplace Overview*.
209
215
210
-
Mendix Support needs application logs to analyze these components. Because Mendix has no control over the context in which the Marketplace content is run outside of Mendix Cloud and Mendix Cloud Dedicated, you will have to demonstrate that the bug is in the supported component by showing the behavior independently from the context in which you are using it.
216
+
Mendix Support needs application logs to analyze these components. Because Mendix has no control over the context in which the Marketplace content is run outside of Mendix Cloud and Mendix Cloud Dedicated, you will have to demonstrate that the bug is in the supported component by showing the behavior independently of the context in which you are using it.
211
217
212
218
### Application
213
219
214
220
This includes the implementation and configuration of features, as well as the data and files in the Mendix app itself.
215
221
216
-
These components are not accessible for Mendix Support and issues in the application are out of the scope of Mendix Support, although we will gladly assist in case of questions.
222
+
These components are not accessible to Mendix Support, and issues in the application are outside the scope of Mendix Support, although we will gladly assist with any questions.
0 commit comments