Hi
I inherit a web-enabled application composed of 6 databases residing on Domino R5x . The Public Address Book (PBA) also had been customized extensively to interact with the application as well as automatically create and maintain userids & passwords for the application . Now my client wants to migrate the whole application to a newly built Domino 6.0.3 box.
My question is : how can I migrate the PBA + the application and force the R6 server to take my R5x PBA instead of the default PBA . Also, if that is feasible then, when I upgrade the R5x PBA to R6 , should I worry that those changes made in that PBA will be wiped out ? Or do I need to upgrade it at all ?
What are the things I need to watch out for ? Do’s and Dont’s !
Your helps are very much appreciated . Many thanks in advance.
Best regards,
Hung Tran
tranh@us.ibm.com
Subject: Migrating a Public Address Book R5 to R6
How about just setting the “Prohibit design refresh or replace to modify” flag for all the custom design elements? Then upgrade to ND6. Maybe it will still work okay.
Subject: RE: Migrating a Public Address Book R5 to R6
Thanks to both of you. At least I know now what I need to watch out for.
Again, many thanks .
Subject: RE: Migrating a Public Address Book R5 to R6
maybe - take it for granted it won’t … thanks for the good laugh, I love the maybe
Subject: Migrating a Public Address Book R5 to R6
Hm, seems to be a bunch of a problems what you’re having.
The bad news is that there is no “click-and-it-will-work-solution”.
First of all, if you run an R6 server with an R5 NAB (PBA), you’ll have more than problems, including most of the interesting new features not working. So, please don’t do this. You will have to upgrade your PAB design.
I’m afraid you will have to go through the painful process of creating an R6 version of your customizations. Depending on the depth and quality of the documentation and on the approach used in customizing the R5 PAB, this may be fairly easy or extremely annoying.
For example: if you’ve only added views or other elements, you could just flag those elements to “not be upgraded during design updates”.
If you have incorporated changes to forms by using subforms, you will only have to re-add those subforms to their respective forms. If you however have made changes directly in the forms of the NAB, you will have to pick each individually and re-apply your customizations one after the other - painful and error-prone.
Sorry that there are no better prospects - if you touch the NAB or Mail templates (which IBM/Lotus doesn’t recommend, but everybody does) you unluckily have to make your changes with upgrades in mind, or you’ll end up in much handwork.