Hi Ute
On 4 Nov 2009, at 09:55, ute Hoffmann wrote:
Hi Elizabeth,
thank you for your answer.
I found this in the WIKI but thought it was mainly for development
but what I speak of is deployment.
So I thought it would be easier to put the 5.4 frameworks to a
folder not using them now,
have the 5.3 frameworks in the default place (I can copy them from
the old deployment server
which is to be replaced by the new one) and start WebObjects without
further changes.
Yes - that's basically what we did - we did set up the 'swap' scripts
because we were doing that on the development machine anyway. That
list of WO frameworks is very useful - stick to that and don't just
swap over *all* 'Java*' frameworks.
If I used the old Wonder 5.3 Frameworks everything should be well
for wonder... to say the truth the singe
not wonder App comes up ok on the current install without rebuilding
it, it really is a change in wonder API
that brings me into this situation... :-(
So you did not change/import Javamonitor/WOTasked from 5.3, right?
I believe we carried on using the 5.4 versions that came with the
Leopard server. I do recall we got into some issues with actually
accessing the app through Apache - everything started up ok but
attempts to use the app frequently got 'server busy' alerts. We had
to change something completely non-obvious in the Apache config.
Perhaps you won't encounter this issue!
Liz
Regards,
Ute
Am 04.11.2009 um 10:22 schrieb Elizabeth Lynch:
Hi Ute
On 4 Nov 2009, at 08:17, ute Hoffmann wrote:
Hi,
is it possible to
a) put the WebObjects 5.4 Frameworks into another folder
b) put the WebObjects 5.3 Frameworks from another server into the
default folder
Yes, we have done this and it seems to work OK using the 5.3
frameworks. However, the installation on which we did this is not
using Wonder. Have a look at this extract from a post to the WO-
Dev list from Mike Schrag in October 2007. The thread is titled:
'The Official What-I-Did-To-Run-5.3-On-Leopard Post'.
* The following can be done a couple ways, but this is just how I
happened to have things setup in betas, so I kept it (it worked for
me):
** Make a /System/Library/Frameworks/WebObjects54 folder, and move
the following frameworks from the 5.4 install into it:
JavaDTWGeneration.framework
JavaDirectToWeb.framework
JavaEOAccess.framework
JavaEOApplication.framework
JavaEOControl.framework
JavaEODistribution.framework
JavaEOGeneration.framework
JavaEOInterface.framework
JavaEOInterfaceCocoa.framework
JavaEOInterfaceSwing.framework
JavaEOProject.framework
JavaEORuleSystem.framework
JavaEOTool.framework
JavaFoundation.framework
JavaJDBCAdaptor.framework
JavaJNDIAdaptor.framework
JavaWOExtensions.framework
JavaWOJSPServlet.framework
JavaWebObjects.framework
JavaWebServicesClient.framework
JavaWebServicesGeneration.framework
JavaWebServicesSupport.framework
JavaXML.framework
** Make a /System/Library/Frameworks/WebObjects53 folder, and move
the following frameworks from your old 5.3 install into it (I tar'd
these up from 5.3 before upgrading, but you can download 5.3 and
extract these from the pkg, or POSSIBLY install them with the
actually installer ... YMMV on that one)
JavaDTWGeneration.framework
JavaDirectToWeb.framework
JavaEOAccess.framework
JavaEOApplication.framework
JavaEOCocoa.framework
JavaEOControl.framework
JavaEODistribution.framework
JavaEOGeneration.framework
JavaEOInterface.framework
JavaEOInterfaceCocoa.framework
JavaEOInterfaceSwing.framework
JavaEOProject.framework
JavaEORuleSystem.framework
JavaEOTool.framework
JavaFoundation.framework
JavaJDBCAdaptor.framework
JavaJNDIAdaptor.framework
JavaWOExtensions.framework
JavaWOJSPServlet.framework
JavaWebObjects.framework
JavaWebServicesClient.framework
JavaWebServicesGeneration.framework
JavaWebServicesSupport.framework
JavaXML.framework
** I then use the following two scripts to be able to switch
between using 5.3 and 5.4 system wide:
bash-3.2# cat wo53
for framework in `ls /System/Library/Frameworks/WebObjects53`; do
rm /System/Library/Frameworks/$framework; ln -sf /System/Library/
Frameworks/WebObjects53/$framework /System/Library/Frameworks/
$framework; done
bash-3.2# cat wo54
for framework in `ls /System/Library/Frameworks/WebObjects54`; do
rm /System/Library/Frameworks/$framework; ln -sf /System/Library/
Frameworks/WebObjects54/$framework /System/Library/Frameworks/
$framework; done
** At this point, you should have NO WO frameworks in /System/
Library/Frameworks -- they should be in subfolders.
** Now go ahead and run wo53, which should now give you WO 5.3
framework symlinks
and thus run WebObjects 5.3 on this server without any reinstall
and being able to switch
back to WO 5.4 in the future without a reinstall.
Will wotasked and Monitor work correctly in this scenarion?
Or do I need to substitute them as well?
Will ths startup mechanism of that server regarding WebObjects
work as expected?
Anyone who has tried this before?
Regards,
Ute
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected]
)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/liz%40plsys.co.uk
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
