Skip to content

Commit f6422df

Browse files
Merge pull request mendix#10675 from mendix/kk-pmp-maia-install
Maia PMP
2 parents 108c0d4 + c0d48e8 commit f6422df

1 file changed

Lines changed: 45 additions & 3 deletions

File tree

content/en/docs/private-platform/pmp-quickstart.md

Lines changed: 45 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -394,9 +394,51 @@ Install the Private Mendix Platform by doing the following steps:
394394
395395
{{< figure src="/attachments/private-platform/pmp-install10.png" class="no-border" >}}
396396
397-
### Adding Additional Components After Installing the Private Mendix Platform
397+
### Installing Maia for the Private Mendix Platform
398398
399-
To ensure that components such as svix and PCLM work correctly, you should install them before you install the Private Mendix Platform itself. If you want to add a component after the Platform installation (for example, if you want to install svix because you decided to enable webhooks), you must perform the following steps:
399+
[Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) refers to Mendix Platform capabilities that leverage [artificial intelligence (AI)](https://www.mendix.com/glossary/artificial-intelligence-ai/) and [machine learning (ML)](https://www.mendix.com/glossary/machine-learning/) to assist developers in application development. Private Mendix Platform currently offers support for Maia-assisted app creation. Other Maia capabilities, such as Maia Chat, will be made available in future releases.
400+
401+
{{% alert color="info" %}}
402+
This feature is available as a beta release, available to selected customers. For more information about beta releases, see [Release Status](/releasenotes/release-status/).
403+
{{% /alert %}}
404+
405+
To enable Maia for Private Mendix Platform, perform the following steps:
406+
407+
1. Ensure that you fulfill the following prerequisites:
408+
409+
* Prepare the Amazon Bedrock LLM API key.
410+
* Make sure that you can expose the Maia service. The installer currently only support the Ingress method. If you are using other methods (for example, Openshift route, HAPROXY, or others), contact the Private Mendix Platform team for assistance.
411+
* Make sure that you know the Private Mendix Platform URL.
412+
413+
2. Download the *maia-appgen-pmp.zip* file from your Private Mendix Platform download portal.
414+
3. Unzip the *maia-appgen-pmp.zip* file.
415+
4. Copy the *maia-appgen-pmp* directory the *images* sub-directory of the installer by running the following command: `cp -r maia-appgen-pmp <your installer>/pmp-binary-linux/images`
416+
5. Upload the Maia directory to your private registry by using the `installer init` command.
417+
6. Run the following command: `./installer component -n=<Private Mendix Platform namespace>`. Maia must be installed at the same namespace as Private Mendix Platform.
418+
7. In the **Components at PMP ns** section, select **Maia**.
419+
8. Configure the following settings:
420+
421+
* **Image Prefix** - The registry and namespace (if it exists) where the *maia-appgen-pmp* image is located
422+
* **Image Name** - The image name, for example, *maia-appgen-pmp*
423+
* **Image Tag** - The image tag of the AppGen image
424+
* **Enable Ingress** - Enable or disable Nginx ingress
425+
* **MXASSIST_COPILOT_AWS_SERVICE_REGION** - The Copilot AWS service region
426+
* **MXASSIST_COPILOT_AWS_BEDROCK_REGION** - The Copilot AWS Bedrock region
427+
* **Amazon_Bedrock_API_KEY** - An AWS Bedrock API key
428+
* **MXASSIST_COPILOT_MXID3_URL** - The OIDC URL of Private Mendix Platform, in the following format: `<your Private Mendix Platform URL>/oidc/`
429+
430+
9. After installing Maia, perform the following steps to connect to it from Studio Pro:
431+
432+
1. Download the patch file for Studio Pro 11.6 from the Private Mendix Platform download portal.
433+
2. Manually set the `MaiaAppGenServiceBaseUrlP` key to the exposed URL of your *maia-appgen-pmp*.
434+
435+
#### Uninstalling Maia
436+
437+
If you want to uninstall Maia, you must do it manually, by running the following command: `helm unstall maia-appgen -n=< maia namespace>`.
438+
439+
### Adding the Svix and PCLM Components After Installing the Private Mendix Platform
440+
441+
To ensure that the svix and PCLM components work correctly, you should install them before you install the Private Mendix Platform itself. If you want to add a component after the Platform installation (for example, if you want to install svix because you decided to enable webhooks), you must perform the following steps:
400442
401443
1. Install the component as described in [Installing Private Cloud License Manager](#install-pclm) and [Installing the Svix Component](#install-svix).
402444
2. Run the command `./installer platform -n=<namespace name>`, where `-n` is the same namespace as the one where you installed Svix and PCLM.
@@ -428,7 +470,7 @@ If you have installed Private Mendix Platform before, you can upgrade it by doin
428470
{{< figure src="/attachments/private-platform/pmp-upgrade2.png" class="no-border" >}}
429471
430472
{{% alert color="info" %}}
431-
To upgrade the PCLM component, select the option **Upgrade PCLM** in the upgrade wizard. For the Svix component, you can use the Svix panel to upgrade directly.
473+
To upgrade the PCLM or Maia components, select the relevant option in the upgrade wizard. For the Svix component, you can use the Svix panel to upgrade directly.
432474
{{% /alert %}}
433475
434476
## Running the Private Platform Configuration Wizard {#wizard}

0 commit comments

Comments
 (0)