Do you have any recommendations to use the shipped portal application in the engine? Are there any benefits or or even disadvantages?

asked 03.04.2018 at 10:43

SupportIvyTeam's gravatar image

SupportIvyTeam ♦♦
accept rate: 77%

edited 03.04.2018 at 10:44

Alex%20Suter's gravatar image

Alex Suter ♦♦

We recommend to not use the shipped portal application. There are some disadvantages:

  • It is still not possible to change the security system of an application. If you need another security system you have to create anyway a new application.
  • The migration of the shipped portal application is confusing. The shipped portal application relies always on the engine version. There is no real migration scenario, because the portal application may use internal ivy api calls. The custom projects which has been deployed to the portal application will be missing after the engine migration.

The main intend of the shipped portal application is to have a running application within seconds. For production environment I recommend our slim engine. This comes without a shipped portal and without a shipped jre (java runtime). It uses the jre from the system, which you might to update every day.


answered 03.04.2018 at 10:53

Alex%20Suter's gravatar image

Alex Suter ♦♦
accept rate: 84%

edited 05.04.2018 at 06:23

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 03.04.2018 at 10:43

Seen: 2,455 times

Last updated: 05.04.2018 at 06:23