[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

2312.0. "Incorporate existing application into CM" by BACHUS::BHP144::Laroche (Veerle Laroche) Tue Feb 23 1993 09:20

Hi,


I need some ideas to incorporate an existing application into ALL-IN-1 3.0.

The application of the customer has the following structure ;


disk6:[produkte.eupen]	is the top directory

	There are some logicals defined two point to the different 
	subdirectories ;

	eu$lib		contains	form library
	eu$scp		        	scripts
	eu$wpl		        	WPS-PLUS files - I think customer 
					uses this for merge
	eu$com				command procedures
	eu$dat				data files
	eu$temp				for temporary files

We did the upgrade to 3.0 some weeks ago, and now the customer would like to 
incorporate his application into CM.

I thought about the following.

1) create an application e.g. MDG
2) create an application area e.g. MDG_EUPEN

	We tried that and a few logicals were defined, like 
	MDG$LIB_MDG_EUPEN

	Also for the development area some logicals were defined and the 
	develop.flb was created.

	The questions I have ;

	-	how do you define additional directories / logicals for the 
		application area ? e.g. for his data files directory or for 
		the WPS-PLUS directory.	

	-	how do you incorporate his existing form library in CM ?
		- this library contains around 80 forms !

	-	we tried creating a form and move it to the base area.
		This does not work.  			

		It seems that the Move to base area checks the authorized
		location in the form CM$AUTH$LOCATIONS
		E.G. for the MDG application.

			the key for FRM is

				FRM
				MDG$SITE_LIB_MDG_EUPEN:SITEEUPEN.FLB

			When you do the move to base area it does 
			recognition on this key so it does not accept e.g. 
			MDG$LIB_MDG_EUPEN:EUPEN.FLB.

			What is the use of the MOVE TO BASE AREA then ?

			Or am I missing something ?

If there are some additional inputs from someone about how to incorporate an 
application, they are always welcome !


Thanks in advance,


Veerle Laroche.

T.R	Title	User	Personal Name	Date	Lines
2312.1	More info for the Move to Base Area	BACHUS::BHP144::Laroche	Veerle Laroche	`Tue Feb 23 1993 13:09`	46
	I did some more testing with the 'MOVE TO BASE AREA'. These are the results. I created an application called "VLR", within that an application area called "VLR_HICK". Application VLR OEG flag is set to 1 Base root directory = dka300:[vlr] Site root directory = dka300:[vlr.site] Area VLR_HICK Application = VLR Area Code = HICK AREA = VLR_HICK I then went to CM and created an element with type FRM. When I try the 'Move to base Area', it checks whether I can do this through the OEG flag and then gives me the Argument form 'Select Live Location'. Now, this form checks the cm$auth$locations form and the only thing I can enter is 'vlr$site_lib_vlr_hick:sitehick.flb' I cannot enter vlr$lib_vlr_hick:hick.flb. The named data for the form cm$auth$locations contains /rse_valid = cm$auth$locations with .area == #cm_language and .type == #cm_type and .location = location and .open == cm$_y For the 'move to base area', shouldn't that be /rse_valid = cm$auth$locations with .area == #cm_language and .type == #cm_type and .base_location = location and .open == cm$_y (i.e. base_location instead of location) Thanks, Veerle
2312.2	Make sure to use existing locations!	UTES09::EIJS	Simon Eijs @Utrecht; 838-2558	`Fri Mar 05 1993 07:45`	92
	Hi Veerle, There are a few remarks to be made. 1) If the customer only uses one directory to store the final procedures (to be used by a user) then the current directory structure is Ok. However, if the customer wants a Base and SIte environment, you need to adjust your logicals, create a few new directories, etc. E.g.: eu$site_lib contains Site form library eu$lib contains form library eu$site_scp Site scripts eu$scp scripts etc. 2) The logicals created during the creation of an application area are not obligatory to be used. They merely serve as templates. You can still use your own logicals as valid Live/Base locations. > Also for the development area some logicals were defined and the > develop.flb was created. > > The questions I have ; > > - how do you define additional directories / logicals for the > application area ? e.g. for his data files directory or for > the WPS-PLUS directory. Directories needed for forms/procedures for the application itself can /should be defined in CM$AUTH$LOCATIONS (options CM AM MAL). You can define the logicals for the data and WPS-PLUS files directoruies as valid locations, but I suggest you define them in an application specific startup procedure. E.g., in CM$APP (options SM CSZ MA) you can define a specific 'Startup' procedure. Naturaly you can still create a A1V30_SITE_START.COM calling your application specific startup procedure. > - how do you incorporate his existing form library in CM ? > - this library contains around 80 forms ! After creating the application area (MDG_EUPEN) copy all your elements to the appropriate directories in OA$SITE_DEV_REC_MDG_EUPEN:. You'll find �26 directories varying from FRM, DO, SCP, BLP, COM,etc. Copy the form library in the [.FRM] directory. Then, from within ALL-IN-1, enter option CM AM RV and specify the application area MDG_EUPEN to be received. All forms/procedures will now be included in CM. > - we tried creating a form and move it to the base area. > This does not work. The template logicals created refer to a specific directory. However, CM doesn't automatically create Live/Base directories/formlibraries/helplibraries. What I suggest you to do is to delete all entries for application area MDG_EUPEN and create new entries with the existing eu$LIB, eu$scp locations. The criteria is that: 1) logical exist 2) directory referred to by logical exist 3) form/help library entered exist Have a look at the Live/Base location of the SHARE area to get an idea. >When I try the 'Move to base Area', it checks whether I can do this through >the OEG flag and then gives me the Argument form 'Select Live Location'. > >Now, this form checks the cm$auth$locations form and the only thing I can >enter is 'vlr$site_lib_vlr_hick:sitehick.flb' >I cannot enter vlr$lib_vlr_hick:hick.flb. > >The named data for the form cm$auth$locations contains > >/rse_valid = cm$auth$locations with .area == #cm_language > and .type == #cm_type and .location = location >and .open == cm$_y > >For the 'move to base area', shouldn't that be > >/rse_valid = cm$auth$locations with .area == #cm_language > and .type == #cm_type and .base_location = location > and .open == cm$_y This is the correct behaviour. When moving an element to Base CM needs to know the Live location. According to the Live location it figures out the Base location. Ciao, Simon