https://answers.axonivy.com/questions/3174/should-i-use-the-shipped-portal-application-in-engine<p>Do you have any recommendations to use the shipped portal application in the engine? Are there any benefits or or even disadvantages?</p>enTue, 03 Apr 2018 10:53:18 -0400https://answers.axonivy.com/questions/3174/should-i-use-the-shipped-portal-application-in-engine/3175<p>We recommend to <strong>not</strong> use the shipped portal application. There are some disadvantages:</p> <ul> <li>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.</li> <li>The migration of the shipped portal application is confusing. The shipped portal application relies <strong>always</strong> 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 <strong>missing</strong> after the engine migration.</li> </ul> <p>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.</p>Alex SuterTue, 03 Apr 2018 10:53:18 -0400https://answers.axonivy.com/questions/3174/should-i-use-the-shipped-portal-application-in-engine/3175