![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[z/OS]](../images/ngzos.gif)
Intelligent Management: on demand router system and custom properties
You can use on demand router (ODR) custom properties to change the behavior of your ODR. For example, you can change the error code that the ODR returns when messages are rejected because of processor or memory overload. To set a custom property on the ODR in the administrative console, click
.http.log.history custom property
Use the http.log.history custom property to specify the number of history server log files. The server log files are the ODR custom log files, as well as the proxy.log, local.log, and cache.log files. Without this custom property, you have one history file for the server log files. Setting this custom property does not affect the custom logs that are already initialized.
Value | Description |
---|---|
Scope | ODR or ODR cluster |
Value | Any positive integer greater than 0 |
Default | 1 |
http.log.history.backup.list custom property
By default, existing custom log files from previous runs are not counted towards the maximum number of history files. Set the http.log.history.backup.list proxy custom property to true so that the ODR counts existing custom logs towards the maximum number of history files.
Scope | ODR or ODR Cluster |
---|---|
Value | Any positive integer greater than 0 |
Default | 1 |
http.log.maxSize custom property
Use the http.log.maxSize custom property to specify the maximum log size in megabytes (MB). A value of UNLIMITED indicates unlimited. As with the http.log.history custom property, the http.log.maxSize custom property applies to the ODR custom log files, as well as the proxy.log, local.log, and cache.log files
Value | Description |
---|---|
Scope | ODR or ODR cluster |
Value | Any positive integer greater than 0 |
Default | 500 MB |
CenterCell custom property
When you are configuring multi-cell performance management in your environment, you can use the CenterCell custom property to designate one cell as the center cell. You also set the CenterCell custom property individually for each cell that you want to designate as a point cell.

Value | Description |
---|---|
Scope | Cell |
Valid values | true: Designates one cell as the center
cell false: Designates one cell as a point cell |
ODR.heapUsage.max
Use the ODR.heapUsage.max custom property to configure a percentage value that determines at what amount of heap usage the ODR rejects requests. If heap usage exceeds 90%, the ODR rejects any incoming request and a 503 error code is returned.
Value | Description |
---|---|
Scope | Cell |
Value | Percentage |
Default | 90% |
ODR.heapUsage.algorithm
Use the ODR.heapUsage.algorithm custom property to configure when heap usage is calculated. If you set the value to globalGC, the amount of heap usage is calculated only immediately after a global garbage collection cycle. If you set the value to request, the amount of heap usage is calculated with each request.
Value | Description |
---|---|
Scope | Cell |
Value | Algorithm |
Default | globalGC |
ODR.heapUsage.errorCode
Use the ODR.heapUsage.errorCode custom property to configure the type of error code that is returned when a request is received and the heap usage exceeds the maximum threshold.
Value | Description |
---|---|
Scope | Cell |
Value | Integer |
Default | 503 |
ODR.sslAlias.<cluster_name>
Use the ODR.sslAlias.<cluster_name> custom property to specify the SSL alias name to be used during SSL outbound connections to any of the servers in the specified cluster. Set this custom property at cell level. Restart the ODR in order for this custom property setting to take effect.
http.overload.error
Use the http.overload.error custom property to configure a custom error code for the autonomic request flow manager to return when an HTTP message over TCP or SSL is rejected due to processor or memory overload. If you do not configure this custom property, the default 503 error code is returned.
Value | Description |
---|---|
Scope | On demand router |
Value | Integer |
Default | 503 |
sip.overload.error
Use the sip.overload.error custom property to configure a custom error code for the autonomic request flow manager to return when a Session Initiation Protocol (SIP) message over Transmission Control Protocol (TCP) or Secure Sockets Layer (SSL) is rejected because of processor or memory overload. If you do not configure this custom property, the default 503 error code is returned.
Value | Description |
---|---|
Scope | On demand router |
Value | Integer |
Default | 503 |
sipu.overload.error
Use the sipu.overload.error custom property to configure a custom error code for the autonomic request flow manager to return when a Session Initiation Protocol (SIP) message over User Datagram Protocol (UDP) is rejected due to processor or memory overload. If you do not configure this custom property, the default 503 error code is returned.
Value | Description |
---|---|
Scope | On demand router |
Value | Integer |
Default | 503 |
http.partialResponseBodyBufferSize
Use the http.partialResponseBodyBufferSize custom property to disable the ODR from buffering the size of the response payload when you perform a rollout on an application edition. Set the http.partialResponseBodyBufferSize custom property to a value of 0.
Value | Description |
---|---|
Scope | On demand router |
Value | Integer |
Default | 0 |
System properties
Follow the instructions to set specific system properties for the ODR.
From the administrative console, select
.ODCLeftGroupDelay
Use the ODCLeftGroupDelay =0 system property set to allow no delay for on demand configuration detection of down servers during failover when servers become unavailable.
The ODCLeftGroupDelay is specified in milliseconds. Set the value to no less than 30000 milliseconds so there is enough time to handle any processes that become peer-to-peer (P2P) unresponsive.
When setting the ODCLeftGroupDelay, temporary network issues can starve resources and ODC recovery processing can add stress to the network.
ODR.traceRouteHeader
Use the ODR.traceRouteHeader system property on the ODR, and it will add a response header with the route that the request took.
For example, -DODR.traceRouteHeader=TraceRoute adds a response header with the name TraceRoute to each request. The value of this response header is the path that the request took.
updateWLM
- If set at cell level, it applies to all dynamic clusters in the cell.
- If set at DC level, it applies to that DC only.
Value | Description |
---|---|
Scope | Dynamic cluster or cell |
Valid values | true or false |
Default | true |