RE: [Openinteract-help] upgrading questions...

[Chris M. <Chr...@te...>]

Hello,

Well, I've finally gotten trying to upgrade my OI installation.  Following
your outline below, I have installed (from cpan) the latest to a local lib
directory (with PREFIX=/var/www/localperl/) and added the use lib statement
to my .conf file - here's a little excerpt:
------------------
<Perl>
 use lib qw( /var/www/commerce );
 use lib qw( /var/www/localperl/lib/site_perl/5.6.1 );
 use lib qw( /var/www/localperl/lib/5.6.1 );
</Perl>
------------------
And I had some troubles starting up the server - here's the output
------------------
[Thu Nov 14 02:38:40 2002] [error] Cannot read configuration file! Error: No
configuration class corresponding to type (ini) at
/usr/local/lib/perl5/site_perl/5.6.1/OpenInteract/Config.pm line 38.

Compilation failed in require at (eval 351) line 1.

Syntax error on line 24 of /var/www/commerce/conf/httpd_modperl_solo.conf:
Cannot read configuration file! Error: No configuration class corresponding
to type (ini) at /usr/local/lib/perl5/site_perl/5.6.1/OpenInteract/Config.pm
line 38.

Compilation failed in require at (eval 351) line 1.
------------------

And it looks to me from the paths in the error message like my local modules
are not being used...  So I tried adding a use lib statement to startup.pl
as well, just to see, and I get the same error.

Using a standalone script with the use lib statements as you suggested seems
to be better - it just complains about a table not existing (which I
expected) but I don't know if it is actually looking in my perllocal dir or
not.

Can anyone help me?  Apologies if the solution is obvious, I have my
wee-hours-of-the-morning-brain on...

Thanks,

Chris McDaniel

-----Original Message-----
From: Chris Winters [mailto:ch...@cw...]
Sent: January 8, 2002 10:11 AM
To: Chris McDaniel
Cc: 'ope...@li...'
Subject: Re: [Openinteract-help] upgrading questions...


On Tue, 2002-01-08 at 09:38, Chris McDaniel wrote:
> I'd like to upgrade my OpenInteract installation (1.21, SPOPS 1.41).  I am
> nervous as I'm working in a production environment and the company would
be
> less than pleased if the site went down for a day because I tried to
upgrade
> and broke it.  So, my questions are, if I upgrade what will break?  How
can
> I minimize breakage?

Hmm hah, good question. To start off with, check out the 'Changes' files
in both OI and SPOPS to get a sense of what's different.

With SPOPS, I don't think there are any backward-incompatible changes,
so you should be ok with this part. An easy way to test it is to install
the newest version to a local lib directory, 'use lib' the dir, create
an $R object using OI::Setup->setup_static_environment() and do some
data fetching, relationship fetching, etc.

With OI, there are quite a few changes. It might be useful to do the
following:

 - Install the latest version to a local lib directory
 - Create a new base installation.
 - Create a new website from that base installation
 - Edit the config file (I recommend the INI version, but YMMV) with
your existing values, including the existing database
 - In conf/httpd_modperl.conf, put a 'use lib' statement for your local
lib directory
 - Install any custom packages you have created to the new site
 - Try and startup OI

Off the top of my head, you may have problems with static pages since
that's done through a new package (base_page) and database setup. You
can continue to use the 'static_page' package if you like though, with
just a couple of server configuration modifications. And the 'base_page'
package comes with a migration script.

Once you've plowed through any problems and the new server looks just
like the old one, you can shutdown the old server, install OI and SPOPS
to the Perl installation, remove the 'use lib' from
conf/httpd_modperl.conf, modify your root Apache setup as necessary
(e.g., change the 'Include' statement) and fire it back up.

I think the key is to first setup a parallel server and modify it so the
rollover time is minimal. I did this fairly recently, from an older
version of OI (1.1) and it worked very well. It wasn't a flip-the-switch
rollover because a number of items had changed, but it worked fine with
minimal impact.

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.