...

The frevvo.war file contains a web.xml with branding parameters. In the frevvo-tomcat bundle, frevvo.war is located in: <frevvo-home>\frevvo\tomcat\webapps - when the war file is unzipped, the web.xml file will be found in <frevvo-home>\WEB-INF.  Refer to Installation Tasks for the steps to repackage frevvo.war after parameters in web.xml have been editied.

...

OEM partners can use the context parameter, “frevvo.oem.branding.class” that can be set (in web.xml) to name a css class. This css class will be placed onto the body of the  ui pages (form designer, etc.). OEMs can then create a CSS file(s) with rules based on the body having the oem branding class can be in order to customize the  app.

...

If the OEMs do not want to create a new CSS from scratch, they may also simply edit the oem-branding.css file added as part of v5.0. This file is intended as a starter file for any OEM and the OEM can change any aspect of this file. The default oem-branding.css relies on the context parameter “frevvo.oem.branding.class” being set to “oem”. OEMs would get oem-branding.css from the WAR file and re-WAR it after editing it.Note: The default oem-branding.css does most of the disablement that Oracle would need.

Disabling Submission Repository

...