Tidal Enterprise Scheduler: Configure Memory on a Service Adapter

Available Languages

Updated:August 19, 2011
Document ID:113194

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This document describes how to configure memory allocation for the Tidal Service Adapters running on either Windows or UNIX platforms.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The components described in this document are the various Tidal Service Adapters.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Configure Service Adapter Memory

By default, the adapters have these amounts configured for their memory:

Adapter Min (MB) Max (MB)
Email 16 64
Horizon 16 256
MSSQL 16 256
Oracle Apps 16 256
Oracle DB 16 256
PeopleSoft 16 256
SAP 16 512
TA 32 32
Webservice 16 256

In order to adjust the memory for any of these adapters, a service.props file needs to be created and configured to specify the amount of memory required. In this file, add these parameters:

  • JvmMinMemory=xxx (where xxx is the amount of memory in MB)

  • JvmMaxMemory=xxx (where xxx is the amount of memory in MB)

Note: These parameters are case sensitive.

The service.props file needs to be located at:

${TIDAL_HOME}/services{service GUID}/config directory)

The config directory needs to be created as it does not exist by default. The different service GUID folders are:

  • Email: Scheduler\master\services\{65C600D1-4316-41bd-8ED0-AB8E5F470838}

  • Horizon: Scheduler\master\services\{84E41389-A7FA-4834-9A63-3808C7B7D799}

  • MSSQL: Scheduler\master\services\{CAFA6E81-E29F-4263-8E80-4928FFF416A2}

  • Oracle Apps: Scheduler\master\services\{DB7FB8C2-96AF-4790-9512-AFC8ECFE784D}

  • Oracle DB: Scheduler\master\services\{3EC69AA3-C8C3-4a19-8F66-F36CFDDA5BB1}

  • PeopleSoft: Scheduler\master\services\{B20EC120-2EB5-4d5f-8133-73FA37225667}

  • SAP: Scheduler\master\services\{51C57049-3215-44b7-ABE1-C012FF786010}

  • TA: Scheduler\master\services\{A2277702-9011-49e9-991D-F2E7E7055C0E}

  • Webservice: Scheduler\master\services\{2C290052-71BA-47BC-85BB-D65E06459001}

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco