General Question Regarding Prod/Staging Pull/Push

[Oscar]

Hi all, 

I have a general question regarding the Production/Staging environment push and pull for the forms. 

I have already set this up in  our environment, but it seems that only the Form runner Definition is upgraded. My question is, does the Form Builder definition get upgraded as well when you push/pull a form? or will this only push/pull the Form Runner Definition?

Thank you,

Oscar

[Alessandro Vernet]

Hi Oscar,

The remote server operations (see link below) only work on published forms.
So if you do a "Push to remote" on a form, you'll find that published form
on the remote, but it won't show in Form Builder on that remote (unless, of
course, it was already there before). Does this make sense?

https://doc.orbeon.com/form-runner/features/home-page#remote-server-operations

‑Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

[Oscar]

Alex, 

Thank you for your response. I have a followup question.

In our forms, we are using a custom XPL to send the form to another application. However, in that third party application we have both a production and test servers. Is there a way to Update this once the forms are pushed into production? or would the original XPLs located in test need to be updated?

Regards, 

Oscar

[Alessandro Vernet]

Hi Oscar,

So it is a URL in an XPL that you need to be different depending on the
environment. You could define that URL in your own property, in your
`properties-local.xml`, and in your XPL refer to it form XPath with
`p:property()`, which is the same as `xxf:property()`.

https://doc.orbeon.com/xforms/xpath/extension-functions/extension-core#xxf-property

If want to deploy the exact same war file in all environments, you could
also have the `properties-local.xml` defined outside the war, storing just
that file in an "external resource directory". More on this at:

https://doc.orbeon.com/xml-platform/resources/external-resources

You'll let me know if this works for you.

[Alessandro Vernet]

Hi Oscar, did you get a change to try "externalizing" the URL as suggested in
my previous message? If so, did that work for you?

[Oscar]

Alex, 

We are having an issue with the Push/Pull methodology. We installed Orbeon on a brand new production server. When we attempt to deploy the form definitions that are in test, we do not see the forms come through. 

We do not see any error or other failures except that the process finishes and the new forms do not get pushed to production. We are utilizing an account that has the orbeon-service role attached to it. 

regards, 

Oscar

[Alessandro Vernet]

Hi Oscar,

Just to confirm, are you saying that after pushing the forms to the
production server, on that server they are not showing up on the Form Runner
homepage (for instance: http://localhost:8080/orbeon/fr/)?

[Oscar]

This is correct.  

We have two customers with this implementation, but we are not seeing the forms come into Form Runner. I have created the following:

Tomcat user with the orbeon-service role

defined the role in Properties-local.xml

Added Basic authentication on the forms

given permissions through form-builder

setup the configuration on properties local with the format:

<property as="xs:string" name="oxf.fr.home.remote-servers">

[

{

"label": "Staging",

"url": "http://staging.example.org:8080/orbeon"

},

{

"label": "Production",

"url": "http://prod.example.org:9090/orbeon"

}

]

</property>

Anything I am missing?

[Alessandro Vernet]

Hi Oscar,

I think that we will be able to help you better with this through support,
since you are using Orbeon Forms PE. Do you already have access to a private
Basecamp? If so could you start a thread there? If not could you send me an
email with your organisation name?