ActiveTransfer Server needs additional hard drive space if you use the hard drive as your virtual file system. The space required depends on the total size of documents ActiveTransfer Server needs to store, upload, and download. ActiveTransfer Server might need additional hard drive space for log files.

See the AgileApps wiki.

Hard drive space, RAM, and core requirements for Apama vary significantly depending on the Apama application you run. You will need to determine processing and memory requirements by measuring the application, since these requirements vary. Contact Software AG Global Support for help.

For Software AG Designer Eclipse platform, 700MB additional free hard drive space is required in the system temp directory(Windows) or temporary (UNIX) directory.

Each product plug-ins you install in Software AG Designer can require from 50K to 150MB of additional free hard drive space.

Hard drive space for the deployment projects you create. When allocating space, allow for the number of projects to increase over time.

The hard disk space for Locate must be in a RAID configuration. The range of hardware requirements in the table is intended to accommodate your needs up to the largest dataset you could install.

The RAM requirement correlates with the amount of data processed and might need to be increased based on use case. You might need to increase cores based on the number of simultaneous users.

You will need additional hard drive space to accommodate the SDKs for the mobile devices for which you want to develop applications.

OneData needs additional hard drive space for temp, import, and export files in the Software AG_directory \OneData\config directory.

The Analytic Engine needs 1GB virtual swap space and a disk subsystem with 10GB available free space. In a production environment, the disk subsystem must have a redundant array of independent disks (RAID 5), an UltraWide SCSI, and 10K to 15K RPM drives.

Also in a production environment, the Analytic Engine needs additional hard drive space for log files. The recommended amount is 100MB; the engine needs 50MB of space for each log file.

Each Web Service Data Collector needs 128MB of virtual swap space. In a production environment, each Web Service Data Collector needs additional hard drive space for log files. The recommended amount is 75MB; each Web Service Data Collector needs 5MB of hard drive space for each log file. More hard drive space might be needed if you use debug level or higher logging.

To use large document handling, Trading Networks Server needs additional hard drive space on which to temporarily save documents (instead of storing them in memory). For detailed information, see webMethods Trading Networks User’s Guide.

If you use persistent topics or queues, or persistent messages, Universal Messaging needs additional hard drive space to persist the published data. The amount of space required would be loosely based on this equation: messages per second x message size x message time to live. If you store messages in memory only, Universal Messaging needs additional heap within the JVM to hold references to these messages. The heap size required is based on the same equation.

Universal Messaging realm servers support high-performance spin locks. If you enable spin locking for a realm server, and then add the realm server to a cluster, the realm server needs two additional cores to handle high-performance cluster event processing.

If you enable a Universal Messaging realm server to use shared memory, the realm server needs two additional cores for each client that connects to it with shared memory.

Additional storage may be required for working and temporary space. The amount of the total required disk space depends on the size of files (models, data, etc.) expected to be uploaded to and processed by Zementis Predictive Analytics.