Mid-tier优化参数建议

关于Mid-tier的一点建议，目前普通使用的Java应用服务器都是Tomcat，我一向是开源软件的粉丝，但是，还是建议如果有条件的话，还是上商业的产品，如Weblogic或者Websphere。这样可以获得能多一点的支持。

鉴于大多数系统还都是用的BMC的产品自带的Tomcat，下面是一些建议的参数配置。

1-HTTP keep-alive

Keep-alive count:infinite (minimum 5000)

Connectiontimeout:90000 ms (minimum 60000 ms)

2-JVM settings

JVM heap：-Xms1024m –Xmx1024m

MaxPermSize：-XX:MaxPermSize=256m

以Windows系统为例，可以使用Tomcat的配置界面工具，配置这两个参数。

3-Threadsconfiguration of the application server hosting the mid tier

maxThreads：500

acceptCount：100

关于1和3的参数文件：tomcatdir/conf/sever.xml的实例代码：

?

1

2

3

4

5

<ConnectorURIEncoding="UTF-8" acceptCount="100"connectionTimeout="90000"

 

maxHttpHeaderSize="8192"maxKeepAliveRequests="-1" maxThreads="500"

 

port="80"protocol="HTTP/1.1" redirectPort="8443"/>

以上参数配置并不是万能的，只是给出一个优化配置的基础，以此为起点调起来可能会更靠谱。

Fine tuning the midtier

Mid tier parameter or service： Recommendedvalue

Enable Cache Persistence：Always on for aproduction environment

Prefetch or preload service： Use prefetchonly when a specific set of AR System forms are known. Otherwise, use preload(recommended).

Recommended preload procedure： 1.Turn onEnable Cache Persistence. 2.Turn on preload. 3.Allow preload to finishpreloading all user facing AR System forms. 4.Turn off preload (allowingstatistical service to take over).

arsystem.formhtmljs_expiry_interval和arsystem.resource_expiry_interval： Set bothparameters to the same value to reflect how often you want the browser to checkwith the mid tier for updates. In a deployment environment where the AR Systemapplications are not modified, set to 604800 (1 week) or higher. The minimumrecommended value is 86400 (1 day). For the new values to take effect, restartthe mid tier.

Definition Change Check Interval： In adeployment environment where the AR System applications are not modified, turnthis off. Otherwise, map this to the frequency of your AR System applicationmodification. For example, if you push changes out every Sunday, set thisfrequency to 604800 (1 week).

arsystem.log_level： Severe. Thiscan also be set through the Mid Tier Configuration Tool

ARS优化参数建议

打开ar.cfg参考一下参数，修改后重启ARS服务。

Delay-Recache-Time:300

Max-Entries-Per-Query:2000

Next-ID-Block-Size:100

Server-Side-Table-Chunk-Size:1000

Allow-Unqual-Queries:F

Cache-Mode:0

Debug-mode:0

Submitter-Mode:1

CMDB-Cache-Refresh-Interval:600

数据库优化参数建议

数据库方面一定要依靠有经验的DBA，靠他们帮你搞定下面这两条：

• Configuring yourAR System database server for optimal performance

• Diagnosing andresolving issues.

另外如果你是Oracle11g的数据库，可以自己动手搞定下面这一条：

Oracle 10g/11gdatabase settings are recommended: Cursor_sharing = FORCE

在数据库上做如下操作：

?

1

alter system setcursor_sharing=FORCE scope=both;

然后在ar.cfg里面加入这个参数。

Oracle-Cursor-Sharing:FORCE

然后重启ARS服务即可。

以上参数配置部分参考了BMC的官方文档《BMC Remedy AR System Server 7.6 Performance Tuning forBusiness Service Management 199037.pdf》，感兴趣的话可以去官方站点的文档下载里下载，该文章对以上参数有详细的解释。