Skip to main content
jv83421-Visitor
1-Visitor
October 6, 2010
Question

Windchill Configuration Assistant

I just installed and executed WCA on a HP-UX server with 8 CPU's and 32 GB
of RAM. It recommended only 3 method servers. I would have guessed more
than 3.

I'm just wondering what others have found using WCA. Are you making use of
the recommended values?

Jim

Jim Van Dragt
Product Development Systems Analyst/Developer - Lead
Information Technology
hermanmiller.com
616 654 5285 OFFICE
616 836 8394 MOBILE
HermanMiller

31 replies

Show previous replies
ssenthil1-Visitor
1-Visitor
March 29, 2012
As indicated by Mike, one should navigate to the directory containing WindchillConfigAssistant.xml

The documentation is available in Windchill® Administration - Configuring Your Windchill Environment Guide - under the section General Procedure for Running the Assistant.

HTH
Swamy Senthil
Swasen Inc.
Translate
IgorVarshavsky10-Marble
10-Marble
March 29, 2012
Hi Robert,

You do not type xml in the command

ant -f WindchillConfigAssistant.xml -projecthelp



d:\ptc\Windchill_10.0\Windchill>ant -f utilities\wca\WindchillConfigAssistant.xml -projecthelp
Buildfile: d:\ptc\Windchill_10.0\Windchill\utilities\wca\WindchillConfigAssistant.xml
Translate
Robert-Altman10-Marble
10-Marble
April 17, 2012




Curious what the groups thoughts are on the recommended settings when
running the Windchill Configuration Assistant? For the most part do you
go with the defaults? Or have you found anything that should be set
differently?



These were the software's recommendations:



ant -f WindchillConfigAssistant.xml configure -Dinteractive=true
-Dpropagate=false



[input] Enter Oracle database user for gathering Oracle parameters:
[#######]

[input] Enter Oracle database password for gathering Oracle
parameters: [#######]

[input] skipping input as property pga.aggregate.target has already
been set.

[input] skipping input as property RDBMS.memory.requirement has
already been set.

[input] Percent of physical memory to reserve for Operating System
[20]

[input] Allocate Windchill Memory region from total (8191 MB) or
free (5965 MB) physical memory ([free], total)

[input] Enter % of free RAM (5965 MB) to allocate to Windchill: [80]

[input] Enter % of Windchill Memory (4772) to allocate to
ServerManager Heap: [5]

[input] Enter number of MethodServers to configure (current=1): [2]

[input] Enter MethodServer max heap size (MB): [2266]

[input] Enter MethodServer initial heap size (MB): [2266]

[input] Enter ServerManager max heap size (MB): [238]

[input] Enter ServerManager initial heap size (MB): [238]

[input] Do you want to enable authenticated (non-SSL) remote JMX
access (y/n)? (y, [n])

[input] Do you want to enable anonymous remote JMX access (y/n)? (y,
[n])

[input] Set PolicyAcl Cache Size (max=10000): [200]

[input] Set RemoteObjectInfo Cache Size (max=10000): [1000]

[input] Set ContainerTeam Cache Size (max=2000): [100]

[input] Set WTContainer Cache Size (max=2000): [100]

[input] Set WTPrincipal Cache Size (max=30000): [5000]

[input] Estimated peak number of active users: [10]

[input] Set Session Cache Size (max=2000): [500]

[input] Set RoleAccess Cache Size (max=20000): [1343]

[input] Set Preference Cache Size (max=10000): [1013]

[input] Set AdministrativeDomain Cache Size (max=2000): [2000]

[input] Set PagingSession Cache Size (max=1000): [100]

[input] Set IBADefinition Cache Size (max=10000): [118]

[input] Maximum number of database connections each MethodServer may
open simultaneously: [15]

[input] Minimum number of database connections each MethodServer may
open simultaneously: [5]

[input] Statement Cache Size: [50]

[input] PreparedStatement rowPretch count: [20]

[input] Refresh Cache Size: [300]

[input] Maximum row count to be processed in a paged query (enter -1
for no maximum): [-1]

[input] Search queryLimit (enter -1 for no maximum): [5000]

[input] Search global wt.pom.queryLimit (enter -1 for no maximum):
[-1]

[input] Bind optimization cardinality: [-1]

[input] Use InClause use Bind optimization: [true]

[input] Database connection hard limit (includes pooled and
nonpooled): [25]

[input] Do you want to remove the xterm/cmd terminal windows (y/n)?
(y, [n])

[input] Do you want to enable automatic termination of requests to
avoid OutOfMemory (y/n)? ([y], n)

[input] Minimum percentage of heap available: [5]

[input] E-mail addresses for JMX adminstrators (comma-delimited
list): [-]

[input] Set servlet engine JSP mode: ([prod], dev)




This e-mail and any files transmitted with it are the property of Arthrex, Inc. and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender at 239-643-5553 and delete this message immediately from your computer. Any other use, retention, dissemination forwarding, printing or copying of this e-mail is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, while Arthrex uses virus protection, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
Translate
jessh12-Amethyst
12-Amethyst
April 17, 2012
Just to be clear, many software's recommendations are depend on the
amount of data in various database tables and the server resources (CPU
and RAM) available -- and thus will be quite different from one
Windchill installation to the next.

--
Jess Holle

Translate
sbugros6-Contributor
6-Contributor
April 17, 2012
Robert,

I accepted the defaults and all went well. About 1 year after we went live I had this problem in the Server Status window:

[cid:image001.png@01CD1C92.24906C20]

And this was the solution:

I'd like you to increase the max perm size to 256 and see if that clears things up. I would suggest shutting down Tomcat before following these steps.


1) In Tomcat/config.properties change the max perm size to 256
maxPermSize=256

2) Open a Windchill shell

3) Navigate to the Tomcat installation directory

4) Uninstall the Tomcat service:
ant -f config.xml uninstallService -DserviceName=Tomcat

5) Install the Tomcat service:
ant -f config.xml installService -DJAVA_HOME=d:\ptc\Windchill_9.1\Java -DserviceName=Tomcat

Other than that no other issue. (that I can recall anyway...)

Steve


Steven Bugros
Brookhaven National Laboratory
Collider-Accelerator Department
Building 911 B
35 Lawrence Drive
Upton, N.Y. 11973
631-344-3259
bugros@bnl.gov


Translate
SteveVinyard1-Visitor
1-Visitor
April 17, 2012
I allow this to do the basics but then I modify the number of MS and memory allocation. It does an "OK" job OOTB though.

[cid:image002.gif@01CD1C7E.63D73E40]

Steve Vinyard
Application Engineer
Translate
GaryMansell12-Amethyst
12-Amethyst
April 18, 2012

I have a couple of follow up questions on the Configuration Assistant recommendations...


When it suggests 2 Methodservers - does that mean 1 FG and 1 BG Methodserver?


When it suggests 3 Methodservers - does this mean 2xFG and 1 BG Methodserver?


Do you accept the wt.pom.querylimit recommendation of -1 (ie unlimited) as I am sure someone from PTC told me to set this at something like 75000 to prevent massive searches killing the machine?


Rgds



Gary

Translate
jessh12-Amethyst
12-Amethyst
April 18, 2012
On 4/18/2012 9:40 AM, Gary Mansell wrote:
>
> I have a couple of follow up questions on the Configuration Assistant
> recommendations...
>
> Do you accept the wt.pom.querylimit recommendation of -1 (ie
> unlimited) as I am sure someone from PTC told me to set this at
> something like 75000 to prevent massive searches killing the machine?

A limiting value for wt.pom.querylimit, i.e. one other than -1, should
only be used as a short-term, temporary workaround to issues like
runaway searches.

The reason is that wt.pom.querylimit limits *all* queries. Thus you run
the risk of preventing queries within the bowels of the software which
are not based on bad user input and that /need /to be performed and left
unlimited for proper operation of the software. Such queries should, of
course, be well constructed to only pull back specific, small columns
and filter those to a reasonable level and may in cases need their own
chunk-based processing logic as well. Simply putting a blanket query
limit on them causes them to err out rather than doing their job.

Instead of a blanket query limit, reasonable configurable
functionality-specific limits need to be placed on functionalities like
search (or some other solution provided, e.g. streaming results with a
capability to interrupt). If such a limit does not exist for some piece
of functionality and it is producing runaway queries, then an SPR should
be produced and wt.pom.querylimit used only as an interim solution until
a fix is delivered.

--
Jess Holle

Translate
GaryMansell12-Amethyst
12-Amethyst
April 18, 2012
Great - thanks for the info


Translate
GaryMansell12-Amethyst
12-Amethyst
April 19, 2012

I have had a look at this and I can see a couple of Configuration Assistant parameters that need changing (at least on my system):


wt.pom.paging.snapshotQueryLimit - seems to be set to only 10000


The first will surely limit search results too drastically?


And the second prevents things like File Vault content verification working as the numbers of vault files in each folder is higher than 10000...


Also, when running it on my Test Server, where I previously had a FG MS with 3GB and a BG MS with a 1GB allocation, it changed this to one FG with 1.7GB and one BG with 1.7GB. My concern with this is that 1.7GB does not seem enough for a FG MS?


I appreciate this is only my Test Server but it is very representative of my Prod server and we had to increase the FG MS to 3GB to get it to stop crashing?


Any ideas on the better memory configuration?


Rgds


Gary

Translate
Show more replies
Terms & ConditionsAccessibility statement