[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

2095.0. "Customization transfer between systems" by GOTA1::AGUSTAFSSON () Fri Jan 15 1993 14:37

Hello ALL-IN-1'ers

I am planning an ALL-IN-1 upgrade on a customized 2.3-system to 
3.0. I want to make necessary changes and tests to  the customizations 
on a separate 3.0-system before performing the upgrade on the "live"
system.

What is the best way of moving the customizations between the 
systems? What about this:



       LIVE SYSTEM                  TEST SYSTEM
       -----------                  -----------

           2.3                         3.0

     Pack my custimizations
     using the GIP ASSET

                                 Import them using Restore Application

                                      Make the changes

                                 Pack the new elements using Stor Appl.

       Upgrade to 3.0

     Import customizations
     using Restore Appl.



Is this possible? Is there a better way?


-----------
�sa Gustafsson
T.RTitleUserPersonal
Name		DateLines
2095.1Upgrade V2.3 on Test systemUTES09::EIJSSimon Eijs @Utrecht, 7838-2558Fri Jan 15 1993 15:5385
Hi �sa,

The way you explained in .0 won't work. Any ALL-IN-1 application packaged
via GIP cannot be restored via the 'Restore Application' in ALL-IN-1 V3.0.

To answer your question, there are a few options:

1)
In case of V2.3 production and V3.0 test system:

Copy the elements from CM to the Receive areas in ALL-IN-1 V3.0. Make sure that 
forms moved to the Live area are copied back into Development first (option
CFL). Copy from OA$SITE_DEV_SHARE and OA$SITE_DEV_<language>. The Receive areas
on V3.0 can be found next to the Development areas:

	[ALLIN1.SITE.DEV_SHARE]
	[ALLIN1.SITE.DEV_<language>]
	[ALLIN1.SITE.DEV_REC_SHARE]
	[ALLIN1.SITE.DEV_REC_<language>]

In the Receive areas you find a number of directories:

	[ALLIN1.SITE.DEV_REC_SHARE.BLP]
	[ALLIN1.SITE.DEV_REC_SHARE.DO]
	[ALLIN1.SITE.DEV_REC_SHARE.COM]
	[ALLIN1.SITE.DEV_REC_SHARE.FRM]
	[ALLIN1.SITE.DEV_REC_SHARE.SCP]

In case your elements belong to the SHARE area, copy the Boilerplates into
[.BLP], the command files into [.COM], etc. You can copy the DEVELOP.FLB into
[.FRM]. Do the same for the <language> elements, but then in the directories
of [ALLIN1.SITE.DEV_REC_<language>].

From within ALL-IN-1 V3.0 enter the 'Application Maintainer menu' and use option
RV (Receive from VMS). Voil�, elements in CM, in the right application area, 
known under the right type.


2)
Install ALL-IN-1 V2.3 on the Test system. Upgrade the test system to V3.0. The 
CM datafiles will be converted so all modifications to elements are available 
right away. This has a secondary advantage that you'll see what might go wrong
if the production system is upgraded.


The second approach is easier from a CM point of view. However, it requires an
additional installation.


Once the elements have been upgraded to work with ALL-IN-1 V3.0, depending on 
how you will perform the upgrade of the production system you need to install
the modified elements afterwards. If you do an upgrade:

Pre-upgrade: 

- Package the new elements via AM SA SS (Store site elements) and then PA 
  (Package application)

Post-upgrade perform:

- delete all you 'V2.3' modifications
- restore packaged application via MA RA

If you perform a brand new installation on the live system:

Pre-upgrade: 

- Package the new elements via AM SA SS (Store site elements) and then PA 
  (Package application)

Post-upgrade perform:

- restore packaged application via MA RA

If you copy the ALL-IN-1 V3.0 from the Test system to the Live system, from 
CM point of view you don't need to do much.


I hope this gives you an idea on the possibilities.

Ciao,

	Simon
2095.2Why CFL?GOTA1::AGUSTAFSSONMon Jan 18 1993 09:1515
Thanks Simon for the quick and in detailed answer.
I think we'll have to settle for the first option.

Another (dumb?) question though:

>>Copy the elements from CM to the Receive areas in ALL-IN-1 3.0.
>>Make sure that forms moved to the Live area are copied back 
>>into Development first (option CFL).

Why cant't I just copy them from their live locations?

-----------
�sa Gustafsson
2095.3No problemUTES09::EIJSSimon Eijs @Utrecht, 7838-2558Tue Jan 26 1993 08:2712
    
    Hi �sa,
    
    You can copy from Live, no problem. However, I thought it easier to
    have the forms in one library, DEVELOP, instead of multiple Live form
    libraries. In V2.*, a form moved to Live is deleted from DEVELOP, so
    assuming working with DEVELOP you need to make sure it's back in
    DEVELOP.
    
    Ciao,
    
    	Simon