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 shipped portal application. engine version. There is no real migration scenario. scenario, because the portal application may use internal ivy api calls. The custom projects which are has been deployed to the portal application will be **missing** in after the new portal application directory.engine migration. The main intend of the shipped portal application is to have a running application within seconds. For production environement 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.

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 shipped portal application. There is no real migration scenario. The custom projects which are deployed to the portal will be **missing** in the new portal application directory. The main intend of the shipped portal application is to have a running application within seconds. For production environement 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.