× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Mark, 

Do you think it would be ok to use eclipse 3.0 instead of WDSc to run this? The 
reason is I want to put it on a server and schedule it to run, and I don't 
really want to go through a WDSc install on the server.  I did a test run and 
it seemed to be ok.

Thanks, 

Chris

>>> markp@xxxxxxxxxxxxxxx 02/22/06 10:22 AM >>>
> Is there a way to copy down the update for WDSC version 6.0 to a network 

> drive instead of me having to use the updater for the next 6 machines I 
> have to install this on?

Yes, Eclipse provides such a facility.  I have been meaning to write this 
up in a formal document and post it, but I have not had the time.  Here is 
the basic gist of it. 

When you are installing updates, you are talking to an Eclipse "Update 
Site" which is just an XML file which points to the updates that are in 
JAR files.  This is all served via a standard HTTP server.

What you can do is create your own internal update site.  Eclipse then 
provides a facility for mirroring and consolidating one or more remote 
update sites to your update site as well as redirecting the install/update 
mechanism to use this internal site instead of the remote site.

Step 1:  Setup an HTTP Server (on any platform/OS).  I am using my OS/400 
Apache Server.  For reference purposes later on, let's assume you can 
access the folder that this HTTP Server is serving from your PC via the 
UNC path name \\WEBSERVER\web-root

Step 2:  Run Eclipse process to create a mirror of the WDSC update sites. 
I created a batch file for this process which I run regularly.  The 
process is intelligent enough to just grab the latest updates.  This is 
what is in my batch file:

REM Modify these variables as appropriate
set drive=C:
set wdsc=\IBM\WDSC\6.0
set local=\wdsc_site
set remote=\\WEBSERVER\web-root\wdsc6_updates
set url=http://webserver/wdsc6_updates 

%drive%
CD %wdsc%\eclipse

REM Get Updates for Product Updater
java -cp startup.jar org.eclipse.core.launcher.Main -application 
org.eclipse.update.core.standaloneUpdate -command mirror -from 
http://www3.software.ibm.com/ibmdl/pub/software/rationalsdp/updater/60/update 
-to %drive%\%local% -mirrorURL %url%/site.xml

REM Get Updates for Rational Web Developer
java -cp startup.jar org.eclipse.core.launcher.Main -application 
org.eclipse.update.core.standaloneUpdate -command mirror -from 
http://www3.software.ibm.com/ibmdl/pub/software/rationalsdp/rwd/60/update 
-to %drive%\%local% -mirrorURL %url%/site.xml

REM Get Updates for WDSC
java -cp startup.jar org.eclipse.core.launcher.Main -application 
org.eclipse.update.core.standaloneUpdate -command mirror -from 
http://www3.software.ibm.com/ibmdl/pub/software/websphere/iseries/wdsc600/update
 
-to %drive%\%local% -mirrorURL %url%/site.xml

REM Copy to Web Server
cd %local%
xcopy . %remote% /S /Y /D

REM End of batch file

To use this batch file you would just need to adjust the set statements at 
the top.  Also, this is only pulling updates for WDSC Standard Edition. It 
could easily be adjusted to update the Advanced Edition by changing the 
IBM URL's being mirrored.

The first time you run this process it has to download nearly 3 GB of 
updates.  It will download them to your local mirror of the update site, 
and then it copies this mirror to your web server.  If you run the Web 
server on Windows, and install Eclipse or WDSC on that server, you could 
avoid having two copies of the mirror.  You could also likely just adjust 
the batch file so that it was mirroring to a mapped network drive that was 
the web server folder.

The Eclipse documentation for the features being used can be found here:
http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html
 

Step 3:  The above process, in addition to mirroring the update sites, 
creates a file named policy.xml which contains the instructions that tells 
Eclipse to redirect to your local update site.  To make WDSC use this 
file, you need to open the Rational Product Updater on each PC.  Then 
choose Preferences -> Update Sites from its menu and enter this URL in the 
field for the policy file:

http://webserver/wdsc6_updates/policy.xml 

Of course update the URL as appropriate.

Once this is done, whenever you check for updates it is checking your 
local web server and installing from it.  You just need to re-run the 
batch file whenever there are some new updates from IBM and it will update 
your local mirror with the latest updates.

This has worked well for us internally.  It may sound daunting and a lot 
of work, but it is a good long term strategy for managing the deployment 
and update of WDSC across multiple systems. 

Mark










_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email 
Security Management Services powered by MessageLabs. 
_____________________________________________________________________________
-------------------------------------------------

This email transmission and any documents, files or previous

email messages attached to it may contain information that is

confidential or legally privileged. If you are not the intended

recipient, you are hereby notified that any disclosure, copying,

printing, distributing or use of this transmission is strictly

prohibited. If you have received this transmission in error,

please immediately notify the sender by telephone or return

email and delete the original transmission and its attachments

without reading or saving in any manner.



The Evangelical Lutheran Good Samaritan Society.

---------------------------------------------------------

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.