We highly recommend to fully encapsulate all your Axon Ivy Projects from Axon Ivy Portal. This is already possible since Axon Ivy 8.0 with the iFrame-Approach. If you do that, you will experience smooth upgrades of the Axon Ivy Portal itself and also of your own projects.
Portal in own application
With Axon Ivy 10, it is now possible to have the Axon Ivy Portal itself in an own application as part of your security context. You will have less troubles if you just want to update or maintain the Axon Ivy Portal.
Read more about this topic here:
How to split an existing installation
You may have an existing Axon Ivy Engine recently upgraded to Axon Ivy 10 . First of all, you need to ensure that none of your Axon Ivy Projects has any dependency to the portal. This means, you need to ensure that you already use the iFrame-Approach.
Side-Note: The portal has been splitted into the portal and portal-components. You should no longer have a dependency to portal. But it's ok to have a dependency to portal-components, because there we provide reusable components. If you use such components, then you also need to bundle portal-components as part of your application.
1) Create own application
You can create a new application e.g. portal in Engine-Cockpit. There you can deploy the application zip of the Axon Ivy Portal, which is provided via Axon Ivy Market choose Portal App (zip).
2) Move configuration
Move the portal configurations parts of the app.yaml into the app.yaml of your new application (portal).
3) Delete old portal projects
Now go to Engine Cockpit and delete old portal projects in the existing application.
I highly recommend to make such a change on test system, first!
