RE: V5R3 - Original Servers gone, completely!

Well, I'm converting from Cern to Apache in advance of our V5R1 to V5R3
upgrade.  I've been working on it all morning and just got it going, or
so it appears anyway.

I used the wizard to do the initial migration.  I'd strongly recommend
doing that unless you're familiar with Apache directives.  All if does
is convert your HTTP config from Cern to Apache, re-writing everything
it can in the new syntax.

As to why it has taken me all morning, we authenticate access via OS/400
user profile.  From there the site is a combination of static pages &
net.data macros.  After the migration, I started the Apache instance and
it came up OK.  The authentication worked but the net.data macros that
retrieve the user profile name (as an environment variable) weren't
getting the profile name returned.  This one little thing is what I've
spent the morning working on.  The online doc floats from V5R1 to R2 to
the net.data site to ignite400.com.  Eventually I found a link to a list
of the environment variables that appeared to be fairly current:
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/rzaie/rzaieenvvar
.htm  But all that showed was that what I was using, REMOTE_USER, should
be valid.  Reading the scant detail revealed that the script needed to
be protected.  OK, I thought it would inherit that since the whole site
is protected but apparently not.  I've made the change and my macros now
work as they did under the Cern version.

Unfortunately, REMOTE_USER, according to the link above, doesn't work
for SSL sites and part two of my migration is to SSL-enable the site.
So now that I have a working config, I'm about to break it again.


BTW, I'd recommend using the migration tool on the new machine.  It has
gotten better with every release.  At V4R5 it was fairly primitive.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] 
Sent: Friday, September 24, 2004 8:20 AM
To: Web Enabling the AS400 / iSeries
Subject: Re:[WEB400] V5R3 - Original Servers gone, completely!

Well one option is to upgrade the older systems OS first. 

Failing that, does anyone know what is done by the conversion?  Is it
simply converting the cern configuration file to an apache one?  Didn't
someone just post that they could find the file on their V5R3 machine,
but they had to do some special option?  What I am wondering is, could
the file be moved over to the V5R3 machine, converted and then the
converted file be moved back to the older machine and tested there too?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com



"Jim Franz" <franz400@xxxxxxxxxxxx> 
Sent by: web400-bounces@xxxxxxxxxxxx
09/24/2004 07:44 AM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
"Web Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx>
cc

Fax to

Subject
Re:[WEB400] V5R3 - Original Servers gone, completely!


Later this year i will take do a side by side upgrade from v4r5 (where
the
upgrade
to apache was not so clean....). Are there any options?
jim
----- Original Message ----- 
From: "Evan Harris" <spanner@xxxxxxxxxx>
To: "Web Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx>
Sent: Friday, September 24, 2004 3:29 AM
Subject: Re: [spam] [WEB400] V5R3 - Original Servers gone, completely!



This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.