Some of the things you can try ... These notes are for ARS 7.0. Hope they help,
Mid-tier Configuration Settings http://itsm7rtm/arsys/shared/config/config.jsp
Cache Settings
Ø Uncheck the perform check box. Having this box checked makes the
mid-tier check to see if any changes have been made to the form dynamically.
You want to manually re-cache when you make changes so the mid-tier doesnt
check each time.
Ø Change the Resource Check Interval from the default of 300 seconds
to 86400 seconds which means update once a day.
Log Settings → Log Level: For best performance, this value should be
set to SEVERE. (Log options Fine/Warning/Sever) I also noticed that by default
we are logging the following Reporting, Cache, Session Management, Performance
& Servlet. If you try and uncheck all logs the defaults return. If you check
one box it will allow that. If you select Reporting this would probably be the
one least used.
ServletExec Configuration Settings (These settings probably dont apply to
our demo environments as we dont have enough memory.) Program Files =>New
Atlanta=> Servlet Exec 5.0 ISAPI=>ServletExec Admin
Username = admin Password = password
In Servlet Exec, adjust the following settings as appropriate:
· Virtual Machine Settings → Minimum Heap Size: Default =
128000 Kbytes change to 500000 Kbytes. (Ive also heard the number 1MB
suggested.)
· Virtual Machine Settings → Maximum Heap Size: This setting
depends on how many applications are hosted. Default is 384000 Kbytes change to
500000 Kbytes.
· Web Applications → Manage → ARSYSTEM → Static
Content:
Set to Web Server for better performance.
IIS Configuration Settings Theres an IIS option for Idle Timeout that
looks like it may be causing problems with decaching forms in the ITSM 7 Demo
VM. In this VM the timeout value is set to 20 minutes, which means that if
youve cached forms and then dont do anything for 20 minutes, New Atlanta
shuts down and the cache is cleared.
The fix is to uncheck the idle timeout. You can do this from IIS
Administration. (Control Panel => Administrative Tools => Internet Information
Services Manger) Open it up, right click on the Application Pools folder and
go to the Performance tab. At the top of the tab is an option for Idle
Timeout. Just uncheck that option and then press OK.
Also, there is also another setting called Recycle worker processes (in
minutes) that should be unchecked, to keep ServletExec from restarting as
well.
config.properties File (Note: This is not appropriate for Demo VMs) To tune
the Remedy Mid-Tier, increase the maximum pooling total connections and
connections per server parameters.
cd <midtier_install_dir>/WEB-INF/classes
In the config.properties file, adjust the following settings as appropriate:
· arsystem.pooling_max_connections_per_server: Default is 80. Change
to 1000 (Production setting not demo environment I would think)
This should be set to the approximate number of expected concurrent operations
to a single AR System server. This maps fairly well to the number of active
users (not just those logged in, but those that are truly active at the same
time).
· arsystem.pooling_max_total_connections: Change to 2000.
This should be set to the approximate number of expected concurrent operations
to all AR System servers with which this mid tier communicates.
The defect that led to this change is, SW00247275, if youre interested.
MISC Add the following Environment Variable
Program Files=> Control Panel => System Go to the advanced tab and click on
the Environment Variables button. Click New
Ø Variable name = ARRPC_RESPONSE_SIZE
Ø Variable Value = 500000
The default RPC response size is 50K. Changing it to 500 KB will result in
better throughput. Instead of 50K chucks across the network, the packets will
be in 500 KB chucks for the RPC Response packets. If you recommend this setting
for a customer, keep in mind that network admin will cringe at this setting.
Additionally, they may have configured the routers to prioritize smaller packet
traffic
Installing ServletExec as a separate service Support suggest this approach
because the AS version (separate service) of ServletExec allows them to
troubleshoot problems much more easily and it has also seemed to provide better
stability in the past. Also, it allows the admin to prioritize the process to
above normal (Task manager -> Processes -> right click and set priority.)
Here is the information regarding how to install ServletExec as a separate
service:
- Shut down the IIS admin service and all dependent services.
- Uninstall ServletExec ISAPI.
- Reboot
- Install ServletExec AS. (download ServletExec AS 5.0 for Windows which you
may download free of charge from http://www.newatlanta.com. You may need to
create an account with NewAtlanta)
- Install ServletExec AS as an instance
- During installation select the option to set up ServletExec AS as a service.
- After install start the WWW Publishing Service and the ServletExec service
(if not already started).
- Set the ServletExec service to automatic startup
When the installation completes (make sure the IIS services has been
restarted) give the following accounts (Authenticated Users, SYSTEM, and
IUSR_WebserverName) full control to the ?:\inetpub\scripts directory,
midtier_install_dir and the ?:\program files\new atlanta directories
Restart the ServletExec Service
If you haven't installed the midtier yet, install the midtier and be sure you
select "Other" as your JSP engine.
- Open http://yourserver/servlet/admin for SE 5.0, the URL is
http://yourserver/servletexec/admin
- Click License and Security under General
- Type or cut and paste this license key into the license field:
NJQL6-EFB-FQ5BD
- Click Submit.
- Click Manage under Web Applications.
- Click Add Web Application.
- Add the following information:
Application Name: ARSYSTEM
URL Context Path: /arsys
Location: C:\Program Files\AR System\Mid-Tier (adjust path accordingly for
your environment) The rest of the settings you can leave on the defaults.
- Click Submit.
- Edit the following file: C:\Program Files\New Atlanta\ServletExec
AS\se-servername\StartServletExec.bat (adjust path accordingly for your
environment)
- Add the -Xms and -Xmx parameters to the java command:
"C:\jdk1.2.2\bin\java" -Xms16m -Xmx512m -classpath "... (rest of line)
- Restart both IIS and NewAtlanta
- Reboot the server if you receive any errors.
Ashley Henderson <[EMAIL PROTECTED]> a écrit : ** All,
Does anyone have some type of documentation for enhancing the performance of
Mid-Tier version 6.3? We are getting slow response from our server and are
trying to determine if this is the actual size of the server that is the
problem of if it is a configuration issue.
Thanks,
Ashley
__20060125_______________________This posting was submitted with HTML in it___
---------------------------------
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur
Yahoo! Questions/Réponses.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
