fr/to the path on which you deployed Orbeon Forms. If you deployed Orbeon Forms on
http://www.example.com/orbeon/, then you can access the From Runner home page at
form-builder-permissions.xml, a view with admin privileges is presented:
form-builder-permissions.xml. For example, with:
oxf.fr.home.remote-serversproperty, which allows configuring multiple remote servers:
labelproperty indicating the label to display to the user when selecting a remote server, and a non-empty
urlproperty indicating the location of the remote server.
oxf.fr.production-server-uriis deprecated. Since Orbeon Forms 4.7 and newer, if the
oxf.fr.production-server-uriis set and not empty, it takes precedence over the new
oxf.fr.home.remote-serversproperty, for backward compatibility.
orbeon.waron the remote server, and you add this property to the remote server's
orbeon-authwebapp to authenticate requests for services or pages which are not public.
orbeon-authrequires that all external requests to Form Runner services are authenticated with
BASICauthentication and have the
orbeon-servicerole. It blocks any other request.
orbeon-service. For example, in
orbeon-authto authenticate the connection.
orbeon-authrequires that the username/password provided authenticate as a valid Tomcat user with the
orbeon-servicerole. If that's successful, then the service proceeds, otherwise it fails.
orbeon_i_control_text, so when upgrading to 2016.2, for Form Runner to work properly, you'll need to initially populate those tables in an operation referred to as reindexing. After you've upgraded and done the initial reindexing, you shouldn't need to reindex the database manually, as Form Runner will incrementally update the index when needed.
debuglevel, to avoid your log growing unnecessarily in case you have lots of documents, while all the other messages are logged at the
infolevel. For instance, you'll see something along those lines in your
debuglevel, add the following to your
newpage, based on which page the user has access to. If the user has access to both, then it links to the
summarypage, in essence giving the priority to the
summarypage. [SINCE Orbeon Forms 2017.2] You can also change this priority by setting the value of the following property, of which the default is shown below.
new summary, the priority will be given to the
newinstead of the
summarypage. If you list only one page, say
new, then entries in the table will only link to the
newpage, of course if the user has access to it. If you leave the value blank, the forms will only be listed, with no link.