• JDELIST is celebrating its 20 year anniversary today!
  • Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

XE Upgrade

Hi,

Upgrade 7.3.2.2 to Xe
NT and Oracle (Deployment and Enterprise)

We want be sure that we can develop in 7.3.2.2 during the upgrade process.

It will be necessary to change the Visual C++ from 5.0 to 6.0 in the deployment, Enterprise and Workstation.

We can maintain a workstation in the old version (this is no problem for us) but we don't know if the Visual C++ can give a problems in the Check-in, Check-out, Building Packages,...

Has anybody proof the same case ?.

Thanks in Advance.
 

SSAJAROFF

Reputable Poster
Andreu :

You should stop all your development during upgrade process, because the
philosophy of upgrade
is to concentrate all your customs on a single environment, upgrade that and
then migrate the
remaining environments.
Strictly speaking, you shouldn't develop on environment XXXB732 while it's
is being upgraded,
but you can (though shouldn't!) do it on environment YYYB732.
You'll be able to locally build your BSFN, but checkin process will go wrong
because of
different compiler versions (.OBJ generated by VC5 are different to those
generated by VC6).
The big problem is package building, compiling parameters and .H files
differ from VC5 to VC6.
Last year, I tried to compile B732x BSFN with VC6 and it didn't work at all.

Sebastian

-----Mensaje original-----
De: Andreu_Valls [mailto:andreu.valls@es.origin-it.com]
Enviado el: Jueves 16 de Noviembre de 2000 07:12 AM
Para: jdelistml@jdelist.com
Asunto: XE Upgrade ~~0:1205



Hi,

Upgrade 7.3.2.2 to Xe
NT and Oracle (Deployment and Enterprise)

We want be sure that we can develop in 7.3.2.2 during the upgrade process.

It will be necessary to change the Visual C++ from 5.0 to 6.0 in the
deployment, Enterprise and Workstation.

We can maintain a workstation in the old version (this is no problem for us)
but we don't know if the Visual C++ can give a problems in the Check-in,
Check-out, Building Packages,...

Has anybody proof the same case ?.

Thanks in Advance.



--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=1
205
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

b_gilmore

Well Known Member
Re: [XE Upgrade ]

You can develop in the pathcodes you are not upgrading the same as you always
have. However, you cannot use the deployment server to build B732.2 packages
once you upgrade it. Therefore, all package builds for B732.2 must be
performed from a designated B732.2 developer workstation w/ VC++5.0.
Package builds for XE take place on the deployment server with the VC++6.0
compiler installed.

As for the enterprise server, you will most likely not want to upgrade the
compiler because you will not be able to successfully build server packages
that contain business functions for B732.2. You will want to maintain the
ability to build PRODB732 packages during your XE pilot phase.
Once the XE pilot phase is complete and you're ready to move all pathcodes to
XE is when you will upgrade the compiler on the Enterprise Server to allow the
generation of XE packages.

During the XE pilot phase you'll probably want to partition all of the logic
to the LOCAL workstation since you will only be capable of building client
packages on XE and that sending XE logic to the production enterprise server
will likely consume additional resources.
Another option here is to set up a temporary (or permanent) XE Logic Server
that you can submit jobs to.



Andreu_Valls <andreu.valls@es.origin-it.com> wrote:
>
> Hi,
>
> Upgrade 7.3.2.2 to Xe
> NT and Oracle (Deployment and Enterprise)
>
> We want be sure that we can develop in 7.3.2.2 during the upgrade process.
>
> It will be necessary to change the Visual C++ from 5.0 to 6.0 in the
deployment, Enterprise and Workstation.
>
> We can maintain a workstation in the old version (this is no problem for us)
but we don't know if the Visual C++ can give a problems in the Check-in,
Check-out, Building Packages,...
>
> Has anybody proof the same case ?.
>
> Thanks in Advance.
>
>
>
> --------------------------
> Visit the forum to view this thread at:
>
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=1205

> *************************************************************
> This is the JDEList One World / XE Mailing List.
> Archives and information on how to SUBSCRIBE, and
> UNSUBSCRIBE can be found at http://www.JDELIST.com
> *************************************************************


____________________________________________________________________
Get free email and a permanent address at http://www.amexmail.com/?A=1
 

owguru

Well Known Member
Andreu,

Here are just a few thoughts...I'm sure others have plenty to add.

By keeping your B7322 development workstation at Visual C++ 5.0, you will be
fine during development, checkin, and checkout.

Package builds will be a slightly different matter:

1 - You will need to build workstation packages from a workstation with
Visual C++ 5.0. And even though the results of the package are stored on
the deployment server (with 6.0), that is no problem. You just need the
actual build of all the c components to happen with 5.0.

2 - Server packages are where you will have the biggest challenge. Since
the build process for these takes place on the destination enterprise
server, there are a few things to consider. A) Are you moving to a new
enterprise server when you upgrade? If so, yippee!!! You can put 5.0 on
the old server and 6.0 on the new server and have no problems. B) You are
working with one server for both releases in which case you're not going to
be a happy administrator. The server needs to go to 6.0 for the new
release, which means no more server packages on the old release. (Note,
some may argue that you could still deploy certain types of objects that
don't involve the compiler, but that's a bit tedious.)

My recommendation is that you decide why you are continuing development in
the old release and set some rules. For example, emergency fixes for
production are quite understandable. And you hope they don't involve
objects that need to be deployed to the enterprise server. Or you go
through the process of determining which objects can be deployed to the
server without the compiler being involved and set rules around that.

If you are looking at an upgrade that may take a long time (<- you define),
then you may want to consider doing your initial dev/crp in XE on a separate
enterprise server...not anything scaled up for real production, but
something to get through the initial testing. When you are ready to cut
over to production on xe, then development would be finished there anyway.

Anyway, since you are coming from 7322, there are a lot of CNC guys out
there that have helped many clients through this predicament. Find one of
them for a planning session, and you can come up with a plan of action that
suits your needs.

Good luck to you.


>From: Andreu_Valls <andreu.valls@es.origin-it.com>
>Reply-To: jdelist@jdelist.com
>To: jdelistml@jdelist.com
>Subject: XE Upgrade ~~0:1205
>Date: Thu, 16 Nov 2000 02:12:14 -0800 (PST)
>
>Hi,
>
>Upgrade 7.3.2.2 to Xe
>NT and Oracle (Deployment and Enterprise)
>
>We want be sure that we can develop in 7.3.2.2 during the upgrade process.
>
>It will be necessary to change the Visual C++ from 5.0 to 6.0 in the
>deployment, Enterprise and Workstation.
>
>We can maintain a workstation in the old version (this is no problem for
>us) but we don't know if the Visual C++ can give a problems in the
>Check-in, Check-out, Building Packages,...
>
>Has anybody proof the same case ?.
>
>Thanks in Advance.
>
>
>
>--------------------------
>Visit the forum to view this thread at:
>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=1205
>*************************************************************
>This is the JDEList One World / XE Mailing List.
>Archives and information on how to SUBSCRIBE, and
>UNSUBSCRIBE can be found at http://www.JDELIST.com
>*************************************************************
>

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at
http://profiles.msn.com.
 

lisa_stinebuck

Active Member
Andreu,
Yes - we are going through this now (upgrade from B7322 to B733.2).
The version difference in C++ is a real pain. I use Snapshot on my
admin machine to apply SARs and have been having to uninstall and
reinstall C++ due to the 5.0/6.0 thing. We opted to use another machine
for the new deployment server so that we wouldn't have to keep doing the
uninstall/reinstall thing there. However, yes you can continue to
develop but it's a pain.....
Lisa
 
He have done one upgrade with the same architecture than old version (B7.3.2.2)and you are right, we can develop and build client packages, but server packages (Business functions).... don't run well!!!!

The second enterprise sounds well, but I don't know how to do the upgrade with two enterprise, could you tell me more about the process?

Someone has told me that it's possible to coexist VC5 and VC6 in the same machine, I don't see the way for telling to OW which version uses, have you proved it?

Thanks in advance
 

SSAJAROFF

Reputable Poster
It's not possible to coexist because they overwrite the same DLLS
(msvcrt.dll, msvcrt20.dll,
etc.)


-----Mensaje original-----
De: Andreu_Valls [mailto:andreu.valls@es.origin-it.com]
Enviado el: Miércoles 22 de Noviembre de 2000 09:12 AM
Para: jdelistml@jdelist.com
Asunto: Re: XE Upgrade ~~1205:1556


He have done one upgrade with the same architecture than old version
(B7.3.2.2)and you are right, we can develop and build client packages, but
server packages (Business functions).... don't run well!!!!

The second enterprise sounds well, but I don't know how to do the upgrade
with two enterprise, could you tell me more about the process?

Someone has told me that it's possible to coexist VC5 and VC6 in the same
machine, I don't see the way for telling to OW which version uses, have you
proved it?

Thanks in advance




--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=1
556
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 
Top