I think I get it, but let's see. So I import the subset of form(s) from the DA(s), which strips the Roles from the forms. Then just importing the blank application container(s) restores those roles to the forms? Is that documented somewhere, or is this a little gem from your own research and analysis?
Rick On 9/25/07, L. J. Head <[EMAIL PROTECTED]> wrote: > > ** I'm not talking about an "Export Application"...I'm talking about go > into applications, right click on the application in question, export to > def. This will generate a def file similar to just a form export but of the > application instead....not all of the definitions of the app along with > data, blah blah blah. Do you get the difference? Oh...and BTW...if you use > Migrator there is a switch somewhere that tells it to migrate the app first > (same part I'm talking about) and then the form so that everything is > updated properly including permissions > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Rick Cook > *Sent:* Tuesday, September 25, 2007 10:11 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Migrating/Importing forms from Deployable apps > > > ** Yes, I know that the application redeployment retains the perms - but > I'm trying to avoid having to re-deploy an entire application just because > one form was updated, and I am holding to a (probably vain) hope that it > might retain the perms if it already found them on the destination server. > Importing the form changes and THEN re-deploying the entire app. doesn't > sound like the improvement in the process that I'm looking for, since > I could achieve the same effect by just re-deploying in the first place. > > I guess what I'm saying is that I would expect that the initial > installation of a DA should be via deployment, due to the fact that the > forms and possibly the roles do not exist on the destination server, not to > mention potential licensing issues. I mean, that encapsulation is the whole > point of the DA. But why couldn't changes to the DA be migrated relative to > what already exists on the destination server? If I already successfully > deployed it, and have the licenses for it, why do I have to brute force an > entire application redeployment just because 10% of it was modified? > > Rick > > On 9/25/07, L. J. Head <[EMAIL PROTECTED]> wrote: > > > > ** This is a chicken and egg type of problem...so requires a bit more > > work. Here is the problem. Server A has Deployable App A with Form A as a > > member. Server B has Deployable App A where Form A does not belong to it. > > So if you Migrate the Form from Server A to Server B then the form is > > imported...but all of it's permissions are stripped...because it is not a > > member of App A on Server B....now that you have the form imported...you can > > now import the App onto Server B...which will make the Form a member....now > > you can re-import Form A on Server B and it will import with proper > > permissions in tact. > > > > ------------------------------ > > *From:* Action Request System discussion list(ARSList) > > [mailto:arslist@ARSLIST.ORG > > ] *On Behalf Of *Rick Cook > > *Sent:* Tuesday, September 25, 2007 9:42 AM > > *To:* arslist@ARSLIST.ORG > > *Subject:* Migrating/Importing forms from Deployable apps > > > > > > ** If I have two servers with similar sets of forms and applications > > already installed, is it possible to migrate and/or Import a form that is > > part of a deployable application without re-deploying the entire application > > AND without losing the Roles/permissions in that migration process? The > > roles already exist for that form on both servers. > > > > -- > > Rick Cook > > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
