orbeon.warinto the Liferay deploy directory (e.g.
~/liferay/deploy). At this point, you should see message indicating that Orbeon is being deployed. Monitor the Liferay output as well as the
logs/orbeon.logfor possible errors.
webapps/orbeon/META-INF/context.xmland restart Liferay. For more information on what this does, see note 2 below.
WEB-INF/resources/config/properties-local.xmlwhich declares the following properties (and other properties you might want to override):
localhost), port (
8080), and context path (
orbeon) must be updated to match your local configuration.
META-INF/context.xmlwhich is not present in the distribution of Orbeon Forms. This file contains:
webapps/orbeon. That copy is removed when the server shuts down, and will be done again the next time the server is started. This makes starting Liferay slower, but more importantly this means that changes you make to files under
webapps/orbeonafter the server started will never be picked up. So any modification to the resources (
WEB-INF/resources) of your application will require a restart of Liferay. This can be quite time consuming and annoying, hence our recommendation to remove the
META-INF/context.xmlgenerated by Liferay.
('Administrator', 'Power user', 'User')
AddLiferayUserHeadersFilter, extracts Liferay user information and sets it as headers ("properties" in portlet API parlance). This sets the following properties/headers:
Orbeon-Liferay-User-First-Name[SINCE Orbeon Forms 2018.1]
Orbeon-Liferay-User-Middle-Name[SINCE Orbeon Forms 2018.1]
Orbeon-Liferay-User-Last-Name[SINCE Orbeon Forms 2018.1]
AddOrbeonAuthHeadersFilter, handles either container or header-based auth, and then sets the following headers/properties:
WEB-INF/resources/home.xhtml, with content such as: