Hi Martin,
No I wasn't aware of changes to the rtb structure and yes I have
upgraded to SP3 and everything appeared to be okay ... but on closer
examination there are a few anomolies which are probably related to
it - so thanks for pointing it out to me -- I'll investigate more
closely, probably this weekend, and get things straightened out then.
Thanks for the heads up
Tom
-Original Message-
Sent: Tuesday, June 25, 2002 11:22 AM
To: 'tomg@degama.com'
Subject: FW: Install of Dynamics SP3
Hi Tom,
Are you aware of this?
Or nothing done yet with SP3?
Martin
-Original Message-
Sent: Tuesday, June 25, 2002 5:15 PM
To: Martin Bos
Subject: RE: Install of Dynamics SP3
Yes - I mentioned that to Anthony and his team - after which I
think the doc
on the Progress Web page was put up there.
Thomas
-Original Message-
Sent: Tuesday, June 25, 2002 4:56 PM
To: Thomas Hansen
Subject: RE: Install of Dynamics SP3
Thomas,
My conclusion is the same as what you say: SP3 is based on
the new structure.
The problem is that the readme that comes with SP3 does
not tell me that!!
That's what confuses me
Martin
-Original Message-
Sent: Tuesday, June 25, 2002 4:41 PM
To: Martin Bos
Subject: RE: Install of Dynamics SP3
Martin,
I am not 100% sure what you mean.
The SP3 package is based on the new structure. You should
chage the structure in any case before you do the partner
load. For the actual load, all that is important is that the
rtb_* dircetories are located off the root of the workspace
yoiur are loading for.
If you have terminal server or the like where I can access
your system, then I can try and help you out if you want.
Might be a good trial run to some of the future work I hope
we will be doing together when we start with the project we
have been talking to Progress about next month.
Regards
Thomas
-Original Message-
Sent: Tuesday, June 25, 2002 4:37 PM
To: Thomas Hansen
Subject: RE: Install of Dynamics SP3
Hi Thomas,
Is it true that rtb_ package which belongs to the SP3, is
actually based on this new structure? In other words: I have
change the structure of my 090dyn-dep workspace before I can
load the rtb package?
Since these new directories exist and they relate to
something outside .../src/icf it must be true I guess.
martin
-Original Message-
Sent: Tuesday, June 25, 2002 4:28 PM
To: Martin Bos
Subject: RE: Install of Dynamics SP3
Hi Martin,
I am not sure if it is in the oducmentation - as must
admit that I
have not read it. I have been using this structure for
some time
in our own development before SP3 came out. I can ask the guys
responsible for the docs to make sure it is covered correctly
though.
Thomas
-Original Message-
Sent: Tuesday, June 25, 2002 4:24 PM
To: Thomas Hansen
Subject: RE: Install of Dynamics SP3
Thomas,
That's clear now.
Thanx!
NOTE:
Did I miss something or was this just not mentioned
clearly in
the documentation?
Martin
-Original Message-
Sent: Tuesday, June 25, 2002 3:58 PM
To: Martin Bos
Cc: dev@icf.possenet.org
Subject: RE: Install of Dynamics SP3
Martin,
Sorry if I confused you
- restructure 090dyn-dep
Yes - just the directory structure.
- extract RTB package in c:\dynamics\090\dep
(this install rtb_* subdirs and overwrites some
src/....)
- partner site load in 090dyn-dep
- build names table in 090dyn-dep
This should be done in ALL workspaces. Make sure that
the changes
to the paths have been loaded correctly into RTb first
though - as
I have seen issues where this does not happen for
some reason -
which I have not yet been able to
identify.
for all other workspaces which depend on 090dyn-dep:
- restructure
- build names table
This could have been done together with the other
workspace - the
order is not so important - as long as it is done BEFORE the
import.
- import changes from 090dyn-dep
Finally, you should naturally recompile everything with
full Xref
in RTB for all of your workspaces. Make sure that the
contained
ADM2 does not break things, and if you have
customisations to the
ADM2 as part of your environment, then you have to
create custom
variants of these so that they are part of your new
environemt -
if you have not done so already.
Regards
Thomas
-Original Message-
Sent: Tuesday, June 25, 2002 3:52 PM
To: Thomas Hansen
Subject: RE: Install of Dynamics SP3
Thomas,
It is a bit confusing:
First you say that the restructure must be done first.
Second you
say that the restucture need to be done just AFTER the
partner load
is is done.
I suppose the correct order is:
- restructure 090dyn-dep
- extract RTB package in c:\dynamics\090\dep
(this install rtb_* subdirs and overwrites some
src/....)
- partner site load in 090dyn-dep
- build names table in 090dyn-dep
for all other workspaces which depend on 090dyn-dep:
- restructure
- build names table
- import changes from 090dyn-dep
Is this the correct procedure?
Martin
-Original Message-
Sent: Tuesday, June 25, 2002 2:13 PM
To: Martin Bos; dev@icf.possenet.org
Subject: RE: Install of Dynamics SP3
Martin,
I would do the restucture first, as you will then be
sure that the
files that are overwritten when you do the
imports between
workspaces overwrites to correct files.
So I would do the restucture as well as the Build Names
Table just
after doing the load of the partner site package into
090dyn-dep.
You have to do this, otherwise you will not pick up
the changed
structure needed to update the other workspaces.
HTH
Thomas Hansen
Managing Director ___________________________________
MIP Europe A/S
Ã…strupvej 53
9800 Hjørring
Denmark
Tel.: +45 98 90 49 16
Fax.: +45 98 90 49 17
Mobile : +45 20 16 19 29
E-mail : thomas@mip-europe.com
Web : www.mip-europe.com
Chairman - Danish Progress User Group
__________________________________
Dynamics-Based Astra2, AstraGen2 Global Application and
AstraFin2 Financial Modules
*** Advanced Future Proof RAD Progress Enterprise
Development ****
-Original Message-
Sent: Tuesday, June 25, 2002 1:54 PM
To: 'dev@icf.possenet.org'
Cc: Thomas Hansen
Subject: RE: Install of Dynamics SP3
Thomas,
Thanx for your great answer.
But do I need to restructure the directory-structure
BEFORE or
AFTER the install of SP3 ?
As far as I can see, the RTB package of SP3 is based
on the NEW
directory structure or am I wrong here?
Martin
-Original Message-
Sent: Tuesday, June 25, 2002 9:28 AM
To: dev@icf.possenet.org
Subject: RE: Install of Dynamics SP3
Martin,
The new structure in RTB should be as
follows off the
root of your
workspace : E.g. c:/dynamics/090/dep
c:/dynamics/090/dep/src
c:/dynamics/090/dep/src/icf/...
c:/dynamics/090/dep/src/adm2/...
c:/dynamics/090/dep/af/sup
(this last one is due to an error in changing
the object
paths, where the file afchartfxd.wrx has not been
moved into
the src/icf structure within the RTB repository)
It is correct that you are using one .ini
file, which
should ONLY
contain the path to your RTB installation
followed by
the default
Dynamics / Progress PROPATH entries. My .ini
file has the
following PROPATH :
PROPATH=.,D:\dynamics\custom\rtb91c,D:\dynamics\custom\rtb91c\
rtb,D:\develop\rtb91c,D:\Dynamics11A\gui,D:\Dynamics11A\gui\ad
ecomm.pl,D:\Dynamics11A\gui\adeicon.pl,D:\Dynamics11A\gui\ades
har.pl,D:\Dynamics11A\gui\adeuib.pl,D:\Dynamics11A\gui\protool
s.pl,D:\Dynamics11A\gui\adeedit.pl,D:\Dynamics11A\gui\adedict.
pl,D:\Dynamics11A\gui\prodict.pl,D:\Dynamics11A\gui\adecomp.pl
,D:\Dynamics11A\gui\adedesk.pl,D:\Dynamics11A\gui\adexml.pl,D:
\Dynamics11A\gui\adeweb.pl,D:\Dynamics11A,D:\Dynamics11A\src,D
:\dlc91c,D:\dlc91c\bin,D:\develop\V91Tools\gui\v91tools.pl
Remember that RTB will manage the rest of
your PROPATH
so that it
point to the correct root workspace paths
and has the
necessary
PROPATH elements you need. Your workspace
paths should
look like
this :
/src/icf /src/icf/af/sup2
/src/icf/scm/custom/rtb
/src/icf/scm/rtb /src/adm2
/src
This will ensure that you have access to all of the
code you need,
as well as the RTB customisations.
(remember that you
have to have
a copy of the customised rtb_evnt.p file in
your RTB root
directory e.g. D:\rtb91c)
The .pf file should also only contain the basic
settings that you
need for running the Progress / Dynamics
environment -
most of the
settings can actually be set in the icfconfig.xml
file that you
use.
I use the -baseADE parameter to prevent the
loading of the
standard Progress .pl files, as I have specified all
of the .pl
files I need from Dynamics in my PROPATH (see the
PROPATH above).
In addition to all of this, for our development with
the Astra
products, we then have all of our source
located in a
sub-directory structure off the root called
"agsrc" -
so that we
have a relatively small number of
directories just off
the root of
the workspace - and can easily identify the
code that
belongs to
each of the components that make up our
environment. So our
directory structures look like this :
/agsrc
/src/icf /src/icf/af/sup2
/src/icf/scm/custom/rtb
/src/icf/scm/rtb /src/adm2
/src
In order to get your other workspaces up to
date with this
structure, you will have to manually rearrange the
directories -
as RTB will not do this for. You should
also check the
following :
- make sure that the new paths have been imported
into your
current RTB repository by checking that the
workspace module
directories now contain src/icf instead of
just "icf" -
so instead
of icf/af/sup (for 090af-sup) the directory
should now be
src/icf/af/sup.
- Run the Build Names Table from RTB (off the
Admin menu) to
ensure that all object paths are correct.
- In each of your other workspaces that are
sourced off the
090dyn-dep workspace and onwards, you must
update your
workspace
sources to include the new products and modules
(mainly 090DLC
which contains the ADM2). This is simply done by
selecting the
workspaces in the correct order (090dyn-dep
- 300-dev - 300-tst etc), entering the
Workspace Sources
screen in RTB and leaving it again - this will
refresh the
sources to get any new products and modules that
have been
added to the source workspace.
HTH. Sorry about the long post. If you have
additional
questions,
let me know.
Regards
Thomas Hansen
Managing Director
___________________________________
MIP Europe A/S
Ã…strupvej 53
9800 Hjørring
Denmark
Tel.: +45 98 90 49 16
Fax.: +45 98 90 49 17
Mobile : +45 20 16 19 29
E-mail : thomas@mip-europe.com
Web : www.mip-europe.com
Chairman - Danish Progress User Group
__________________________________
Dynamics-Based Astra2, AstraGen2 Global
Application and
AstraFin2 Financial Modules
*** Advanced Future Proof RAD Progress Enterprise
Development ****
-Original Message-
Sent: Monday, June 24, 2002 9:26 PM
To: 'dev@icf.possenet.org'
Subject: Install of Dynamics SP3
Hi,
I am trying to install Progress Dynamics SP3. That
comes with a
RTB package. On the progress website, there
is also a
document
which describes how to rearrange the pathnames.
I have a question here:
- In the RTB package, besides the rtb_*
directories, I see also
some directories called:
af
src
Why are these "af" and "src"
directories in it
and should these
overwrite existing files?
Where am I supposed to extract this
package? Normally
it is in the root dir of the
workspace. But how
does this relate
to the document which describes the
change of
the root of the
workspace?
When I extract it in
c:/dynamics/090/dep, the
src directory of
the RTB package
overwrites the existing sources? Is this OK.
And what about
the af directory.
That will (in that case) not overwrite
the src/icf/af .
Anyway it is not clear to me what I
should do now.
- I am struggling a bit with the
combination of
the following
settings:
- PROPATH in INI file
- workspace path
- use of -BaseADE startup parameter
I have the following workspaces:
c:/dynamics/090/dep (partner load
environment)
(contains subdirs:
gui,tty,src/icf...)
c:/dynamics/300/dev (optional own
modifications of Dynamics)
(contains subdirs:
gui,tty,src/icf...)
c:/app1/300/dev (development
application 1;
application is
based on dynamics)
(contains subdirs:
gui,tty,src/icf...,
app1src, app1gui)
c:/app2/300/dev (development
application 2;
application is
based on dynamics)
(contains subdirs:
gui,tty,src/icf...,
app1src, app1gui)
c:/rtb91c (contains
Roundtable
install directory)
c:/rtbwork (Contains
RTB database
and INI, PF, XML
files and shortcuts for startup of develop)
In case this is maintained in 1 RTB database
what should my INI
PROPATH, workspace-pathnames and -BaseADE
startup parameter be?
(as you can see, I am using 1 INI
and 1 PF file
for all of
those workspaces. MAybe this is wrong?)
Best regards,
Martin Bos - mailto:martin.bos@cargomate.com
CargoMate BV -
Meerwal 21 B - 3432 ZV - Nieuwegein - NL tel.
+31(0)30-6048811 - fax +31(0)30-6090000
-CargoMate - Global
Logistics
Software Solutions
Bangkok - Dubai - Amsterdam - Miami - San
Francisco -
Los Angeles
To unsubscribe, e-mail:
dev-unsubscribe@icf.possenet.org For
additional commands, e-mail:
dev-help@icf.possenet.org
To unsubscribe, e-mail:
dev-unsubscribe@icf.possenet.org For
additional commands, e-mail:
dev-help@icf.possenet.org
To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org
For additional commands, e-mail: dev-help@icf.possenet.org
RE: Roundtable setupMartin,
I think you encountered a little RTB bug...here's my email to Jeff at RTB
about it, and a suggested workaround.
-Original Message-
Sent: Thursday, March 28, 2002 11:03 AM
To: Ledbetter, Jeff
Subject: RE: Workspace Module updating
Hi Jeff,
What I have found with regard to the issue of me not being able to change
workspace module path fields:
It looks like the maintenance program is taking the site number from the
first module in the browse and
disabling edit for all workspace modules if it is different from the
current site number. Conversely, if the
site number of the first workspace module in the browse matches the site
number, then editing for every
workspace module is enabled, regardless of site.
I added a test module definition - 0-a (that is zero-dash-a) as site zero,
such that it appear first in the
browse of module definitions, and now the maintenance routine allows me to
change all the 090 site module definitions (as well as my site zero
definitions).
So I am pretty sure there is a bug in RTB in that area. Its easy enough to
work around, but thought you may
want to try to verify it at your end.
Regards
Tom Greenwood
President, DEGAMA Systems Inc.
http://www.degama.com
416-493-0059 x107
-Original Message-
Sent: Wednesday, March 27, 2002 2:38 PM
To: 'Tom Greenwood'
Cc: thomas@mip-europe.com; rtb-support
Subject: RE: Roundtable setup
Hi. I really don't know.. Thomas and the gang may need to inspect their
partner site deployment.
You can't edit anything in the Dynamics workspace... it's a read-only
workspace. If your site is '000' you should be able to edit anything with
no site prefix.
Jeff Ledbetter
Roundtable Team Leader
starbase corporation
-Original Message-
Sent: Wednesday, March 27, 2002 11:31 AM
To: Ledbetter, Jeff
Subject: RE: Roundtable setup
Well its very strange. The module and workspace module definition was
created with my site number set to
zero. However, I tried changing my site number to 090, and voila it
let me change it. Just to make sure, I reset
my site number back to zero and re-created the workspace module
definition. It let me create it, but once I
created it, going immediately back in to re-edit it, the fields and
delete button were disabled. So RTB thinks
for some reason that everything in that workspace is site 090?
-Original Message-
Sent: Wednesday, March 27, 2002 12:11 PM
To: 'Tom Greenwood'
Cc: thomas@mip-europe.com; rtb-support
Subject: RE: Roundtable setup
If you site number is still 091, then that workspace module does not
belong to your site so you cannot change it.
Jeff Ledbetter
Roundtable Team Leader
starbase corporation
-Original Message-
Sent: Wednesday, March 27, 2002 8:40 AM
To: Ledbetter, Jeff
Cc: thomas@mip-europe.com; rtb-support
Subject: RE: Roundtable setup
Hi Jeff,
- fields are disabled. So is the delete button. here's a screen
shot. Tried reconnecting to RTB
without dynamics hooks etc.
- we also upgraded our other environment to RTB 9. There the
fields are enabled. So I dont get it.
-Original Message-
Sent: Wednesday, March 27, 2002 11:21 AM
To: 'Tom Greenwood'
Cc: thomas@mip-europe.com; rtb-support
Subject: RE: Roundtable setup
Hi.
Why can you not change it? Is there an error you are getting?
Jeff Ledbetter
Roundtable Team Leader
starbase corporation
-Original Message-
Sent: Wednesday, March 27, 2002 8:14 AM
To: dev@icf.possenet.org
Cc: thomas@mip-europe.com; rtb-support@starbase.com
Subject: RE: Roundtable setup
...
zero or blank), is the right one. It'll get me around the
workspace module path issue, too.
Which issue is this Tom ?
For some reason in RTB 9, I can't change a workspace module
path -- even if
its one I've just created that's not assigned. I don't know if
this is a
result
of dynamics RTB customization, or some other restriction added
to RTB
recently.
I'm still waiting to hear from RTB on that one. Do you know
anything about
it?
When I create products and modules for the workspace created as
per the RTB
setup doc,
my application subdirectories end up hanging off src/icf. I want
to move
Dynamics
versions through the QA process in tandem with the application,
but have
Dynamics
versions clearly separated via the directory structure.
Loading the aplication can be quite time consuming, as the
combination
of Module load and generating / loading .ado files can take
quite a long
time.
I'm familiar with the dataset export/import process without
Roundtable,
but I am
unsure as to how and where to load .ado's for my objects into
the RTB
repository and
the whole process of SCM'ing dynamics objects, and also
importing these into
other
workspaces and icfdb repositories. My hope is that it will be
easier than
it is now!
Thanks,
Tom