• 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!

Handy script for package installs


Legendary Poster
Some customers (like the one I am at presently) have a LOT of OneWorld development - and therefore a large number of packages get created throughout the week. This means that as many as 10 update packages a day can be created so that developers can test their code on Citrix and Java based platforms.

As such, installing a new development machine with as many packages as we have been involved with can call for a long, long installation session. I got pretty fed up with this, so decided to create a batch script to ensure the job was done properly.

All packages at where I am working come with a standard naming convention :

{pathcode}{F}{A - Version}{00 - full, 01-99 - Updates}
eg : DV7333FG00 is the Full package for version 'G'
or DV7333FH45 is the 44th update package for full package DV7333FH00

You may have a different naming convention for your packages - but maybe the following script may help !

rem -------------------------------------------------------------
rem script INSTALLXE.BAT to install lots of packages and uses the
rem Silent Install routine to install to C:\B7. Expects packages
rem to be named xxxxxxx00 to xxxxxxx99 and JDEDPY1 as Deploy Svr.
rem Written by Jon Steel erpSOURCING - http://www.erpsourcing.com
rem this script may be passed on provide the first 7 lines remain
rem -------------------------------------------------------------
@echo off
if "%1" == "}{" goto %2
for %%a in (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99) do call %0 }{ SecA %%a
goto End
echo Installing ... DV7333FI%3
if exist c:\jdeinst.log del c:\jdeinst.log
if not exist \\jdedpy1\b7333\package_inf\DV7333FI%3.inf echo DV7333FI%3 does not exist...
if exist \\jdedpy1\b7333\package_inf\DV7333FI%3.inf "\\jdedpy1\b7333\OneWorld Client Install\Setup.exe" -S -P DV7333FI%3 -D C:\B7
if exist c:\jdeinst.log copy c:\jdeinst.log DV7333FI%3-Install.log

Jon Steel

ERP Sourcing


Legendary Poster

neat script. I'm confused though. Our experience is that OW update packages when built automatically update their parent package. Therefore there is no need to apply updates after installing a full package on a machine.

Am I missing something?

Larry Jones
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials


Active Member
Don't forget that even though the update package does update the parent
package (Xe), you will have to recompress the parent package to get the
update integrated with the parent. Ie, you have one set of directories with
the uncompressed files for the package, but it is the compressed files from
which it deploys from. If you want to deploy a parent package and want to
ensure all of your updates are deployed with it, recompress it.


Xe, SP14.2, Nt/SQL/Metaframe


Legendary Poster
Re: RE: Handy script for package installs

Maybe thats why my CNC admin doesn't use compression on packages :)

Larry Jones
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials
Call Orchestrations From Excel – The Easy Way to Make the Orchestrator Work for You.


Active Member
Smart script Jon.
Further to Larry's comment... The parent is automatically updated... the
specs get updated that is, not the .cab files. The parent will therefore
need to be recompressed before installing a DV client.
Maybe you could set up a script to recompress every night, so that each
morning your parent package will be updated with all the update packages
from the previous day. That way you'll only ever have to install one package
to be up to date.