Adobe 38000827 Administration Guide - Page 23

Charting Settings Java and JVM Settings

Page 23 highlights

Charting Settings page The ColdFusion charting and graphing engine lets you produce highly customizable business graphics, in a variety of formats, using the cfchart tag. You use the Charting page in the Administrator to control characteristics of the engine. The following table describes the caching and thread settings for the ColdFusion charting and graphing engine: Setting Cache Type Maximum number of images in cache Max number of charting threads Disk cache location Description Set the cache type. Charts can be cached either in memory or to disk. In memory caching is faster, but more memory intensive. Specify the maximum number of charts to store in the cache. After the cache is full, if you generate a new chart, ColdFusion discards the oldest chart in the cache. Specify the maximum number of chart requests that can be processed concurrently. The minimum number is 1 and the maximum is 5. Higher numbers are more memory intensive. When caching to disk, specify the directory in which to store the generated charts. Java and JVM Settings page The Java and JVM Settings page lets you specify the following settings, which enable ColdFusion MX to work with Java: Setting Java Virtual Machine Path Initial Memory Size Maximum Memory Size Class Path JVM Arguments Description The absolute file path to the location of the Java virtual machine (JVM): jvm.dll in Windows or jvm.so in Solaris, Linux, and HP-UX. The JVM initial heap size. Default is 8196 MB. The JVM maximum heap size. Default is 512 MB. The file path(s) to the directories that contain the Java classes used by ColdFusion MX. Use a comma-delimited list for multiple entries; for example, c:\foo,d:bar The arguments to the JVM. Use a space to separate multiple entries; for example, -Xint -Xincgc Before ColdFusion saves your changes, it saves a copy of the current jvm.config file as jvm.bak. If you r changes prevent ColdFusion from restarting, use jvm.bak to restore your system. For more information, see the online Help. Server Settings section 15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 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

Server Settings section
15
Charting Settings page
The ColdFusion charting and graphing engine lets you produce highly customizable
business graphics, in a variety of formats, using the
cfchart
tag. You use the Charting
page in the Administrator to control characteristics of the engine.
The following table describes the caching and thread settings for the ColdFusion charting
and graphing engine:
Java and JVM Settings page
The Java and JVM Settings page lets you specify the following settings, which enable
ColdFusion MX to work with Java:
Before ColdFusion saves your changes, it saves a copy of the current jvm.config file as
jvm.bak. If you r changes prevent ColdFusion from restarting, use jvm.bak to restore
your system. For more information, see the online Help.
Setting
Description
Cache Type
Set the cache type. Charts can be cached either in memory or to
disk. In memory caching is faster, but more memory intensive.
Maximum number of
images in cache
Specify the maximum number of charts to store in the cache. After
the cache is full, if you generate a new chart, ColdFusion discards
the oldest chart in the cache.
Max number of
charting threads
Specify the maximum number of chart requests that can be
processed concurrently. The minimum number is 1 and the
maximum is 5. Higher numbers are more memory intensive.
Disk cache location
When caching to disk, specify the directory in which to store the
generated charts.
Setting
Description
Java Virtual Machine Path
The absolute file path to the location of the Java virtual
machine (JVM): jvm.dll in Windows or jvm.so in Solaris,
Linux, and HP-UX.
Initial Memory Size
The JVM initial heap size. Default is 8196 MB.
Maximum Memory Size
The JVM maximum heap size. Default is 512 MB.
Class Path
The file path(s) to the directories that contain the Java
classes used by ColdFusion MX. Use a comma-delimited
list for multiple entries; for example, c:\foo,d:bar
JVM Arguments
The arguments to the JVM. Use a space to separate
multiple entries; for example, -Xint -Xincgc