Long Full Package Builds - Three Possible Solutions

We used to have this problem too. Now our Full Package Builds, both Client and Server, take about 5 hours, combined. What did we change?

1. Turned off real time virus protection. Prior to the actual builds, thousands of files are copied. JDE uses UNC pathing (\\server\volume\path\filename) for these copies and virus programs scan every file and can take hours to finish. UNC = Universal Naming Convention

2. Load the following two LMHOSTS settings and nothing else on your Enterprise and Deployment Servers.

###.###.###.### EnterpriseServerName #PRE
###.###.###.### DeploymentServerName #PRE

###.###.###.### = IP address for respective server

These instructions preload the two entries for these related servers and reduce name resolution time. Keep additional entries to a minimum and do not include any comments. The whole file is parsed including comments on each lookup, so keeping entries and comments to a minimum will improve performance.

3. Remove all unnecessary network protocols from both servers and any workstations used for builds. Move the TCP/IP protocol to the top whenever possible.

I hope this help someone. We wasted countless hours prior to making these changes.


Ray W. Justus
Kitchell Corporation
1707 East Highland Avenue, Suite 100
Phoenix, AZ 85016-4679
(602) 631-6157
mailto: [email protected]

Hi Ray,

Where are your Central Objects stored? And what is the configuration OW runs at your site? Are you running XE?

BTW we turn of the UNC flag when we build packages. For some update packages it saves around 30% of the time.

We are now building a full client/server package in 19 hours ((
15.5 hours for the clientside (Gbrspecs takes 9 hours) and 3.5 hours for the server side.

Richard Stam
CNC/System Administration
LIVE: B733.3 SP13, AS400 Enterprise Server on V4R4
Citrix <100 users (so far) and some NT/W2K Clients

Richard,

Our Central Objects are on our Enterprise Server.

OneWorld Xe, SP 14
Enterprise Server: NT 4.0, SP 6a
Deployment Server: NT 4.0, SP 6a
Workstations: NT 4.0, SP 6a, Windows 2000, SP 1 and Citrix Terminal Server 1.8, SP 2 (NT 4.0 SP 6a)
SQL Server 7.0, SP 2 with Hot Fix 851
Network Protocols: TCP/IP (Primary), IPX/SPX, NetBIOS

Questions: Are you saying you turn off the UNC flags in OneWorld? How are the different servers and workstations communicating path information. Are you mapping logical drives? Obviously, I am not understanding something here.

Ray W. Justus
Kitchell Corporation
1707 East Highland Avenue, Suite 100
Phoenix, AZ 85016-4679
(602) 631-6157
mailto: [email protected]

Hi Ray,

Where are your Central Objects stored? And what is the configuration OW runs at your site? Are you running XE?

BTW we turn of the UNC flag when we build packages. For some update packages it saves around 30% of the time.

We are now building a full client/server package in 19 hours ((
15.5 hours for the clientside (Gbrspecs takes 9 hours) and 3.5 hours for the server side.

Richard Stam
CNC/System Administration
LIVE: B733.3 SP13, AS400 Enterprise Server on V4R4
Citrix <100 users (so far) and some NT/W2K Clients

Hi Ray,

Have you added the entry:

WaitForBusbuild=Y to the JDE.INI of the Deployment
Server under the [INSTALL] Stanza ? (case sensitive)

Since SP10.1 this new entry improves package build
performance by more than 50% because it builds the
specs first and the does NER Generation and Busbuild.

JDE SAR Number 4162736

Jorge Arrieta
Independent CNC Specialist




--- RJustus <[email protected]> wrote:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=9423


__________________________________________________

Yes, we have that entry, Jorge. Thanks for the tip anyway. Someone else out there can probably use it. However, I think it does just the opposite, i.e., it builds the business functions first and then builds the specs.

Ray W. Justus
Kitchell Corporation
1707 East Highland Avenue, Suite 100
Phoenix, AZ 85016-4679
(602) 631-6157
mailto: [email protected]

Hi Ray,

Have you added the entry:

WaitForBusbuild=Y to the JDE.INI of the Deployment Server under the [INSTALL] Stanza ? (case sensitive)

Since SP10.1 this new entry improves package build performance by more than 50% because it builds the specs first and then does NER Generation and Busbuild.

JDE SAR Number 4162736

Jorge Arrieta
Independent CNC Specialist

Ray,

Yes we turn off UNC Flags only for packagebuilds. We have seen an improvement in speed with this (we tested it with update packages).

There is however one thing you have to do after the package build(being either update or full). You have to edit the packagename.inf file before deploying/installing the package.

When we turn off this UNC flag you have to enter the full path name.
>> when UNC is on you'll see within pathcode master only B7333. When turning it off you have to state it like E:\JDEdwardsOneWorld\B7333.

This last thing you'll also see in this INF file and has to be replaced with \\DEPLOYMENTSERVERNAME.

As soon as we have finished the build we turn UNC back on as it might cause problems in OMW for BSFN's & Tables (we found this out the hard way).

Communication of servers/workstations go through ODBC/OCM and servermap settings so you can temporarily change this UNC flag as they point to the right sources.



Richard Stam
CNC/System Administration
LIVE: B733.3 SP13, AS400 Enterprise Server on V4R4
Citrix <100 users (so far) and some NT/W2K Clients

I know it is probably minutae but I was wondering what
others have seen on this point. I haven't paid a lot
of attention and seem to recall on Server Builds one
(Specs/BusBuild) goes first and on Client Builds
another goes first. Just curious.




http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=9465


__________________________________________________

I'm sorry but... which are UNC flags?
Thanks