Tuning runtime application parameters and tracing specifications

To manually tune selected runtime application parameters and tracing specifications, use the Runtime Parameters management page.

Procedure

  1. From the top menu, select Secure Mobile Settings > Manage > Runtime Parameters. This page contains three panels: Runtime Status, Runtime Tuning Parameters, and Runtime Tracing.
  2. Perform one or more of the following actions to tune your run time.
    Note: Certain changes might require a restart of the run time before they can take effect.
    View the status of and restart the run time
    1. Select the Runtime Status panel. The status of local and clustered run times are displayed.
      • Under Local Runtime Status, you can view the run time operational status, when it was last started, and whether a restart is outstanding. If the value of the Restart Required field is True, it means that the run time must be restarted for some changes to take effect.
      • Under Clustered Runtime Status, all nodes in the cluster are listed.
        • The Master column indicates whether a node is the cluster master.
        • The Runtime Status column indicates whether a node is running or stopped.
        • The Changes Active column indicates whether changes made to the cluster configuration are active on this node. Having a green indicator in this column means that all changes made are already active. Having a yellow indicator in this column means that this node must be restarted before some changes can take effect.
    2. Depending on which run time you want to restart, click Restart Local Runtime or Restart All Clustered Runtimes.
    Modify the maximum or initial heap size

    These parameters indicate the maximum and initial heap size in megabytes for the run time Java virtual machine.

    1. On the Runtime Tuning Parameters panel, select Max Heap Size or Initial Heap Size.
    2. Click Edit.
    3. In the Max Heap Size or Initial Heap Size window, enter the heap size value as needed.
    4. Click OK.
    Modify whether to suppress sensitive trace

    Enabling this parameter prevents sensitive information from being exposed in log and trace files. Examples of such sensitive information include bytes received over a network connection.

    1. On the Runtime Tuning Parameters panel, select Suppress Sensitive Trace.
    2. Click Edit.
    3. In the Suppress Sensitive Trace window, select or clear the check box as needed.
    4. Click OK.
    Modify console log level

    Console log level controls the granularity of messages that go to the console.log file.

    1. On the Runtime Tuning Parameters panel, select Console Log Level.
    2. Click Edit.
    3. In the Console Log Level window, select the new value from the list.
    4. Click OK.
    Set whether to accept client certificates
    This parameter controls whether the server accepts client certificates as a form of authentication.
    1. On the Runtime Tuning Parameters panel, select Accept Client Certificates.
    2. Click Edit.
    3. In the Accept Client Certificates window, select or clear the check box as needed.
    4. Click OK.
    Set session invalidation timeout

    This parameter defines the amount of time a session can remain unused before it is no longer valid.

    1. On the Runtime Tuning Parameters panel, select Session Invalidation Timeout.
    2. Click Edit.
    3. In the Session Invalidation Timeout window, define the value in seconds.
    4. Click OK.
    Set session reaper poll interval

    This parameter defines the wake-up interval in seconds for the process that removes invalid sessions. The minimum value is 30 seconds. If a value less than the minimum is entered, an appropriate value is automatically determined and used. This value overrides the default installation value, which is 30 - 360 seconds, based on the session timeout value. Because the default session timeout is 120 minutes, the reaper interval is usually 2 - 3 minutes.

    1. On the Runtime Tuning Parameters panel, select Session Reaper Poll Interval.
    2. Click Edit.
    3. In the Session Reaper Poll Interval window, define the value in seconds.
    4. Click OK.
    Set the key store that is used by the run time server

    This parameter defines the key database that contains the run time server's private key.

    1. On the Runtime Tuning Parameters panel, select Keystore.
    2. Click Edit.
    3. In the Keystore window, select the key database from the list.
    4. Click OK.
    Set the trust store that is used by the run time server

    This parameter defines the key database that contains keys that are trusted by the run time server

    1. On the Runtime Tuning Parameters panel, select Truststore.
    2. Click Edit.
    3. In the Truststore window, select the key database from the list.
    4. Click OK.
    Delete the value of a parameter
    Use this button to delete the existing value of a parameter.
    1. Select the parameter to reset the value for.
    2. Click Delete. The value of the parameter is then changed to Unset.
    Manage the application interface on which the run time listens
    1. On the Runtime Tuning Parameters panel, under Runtime Listening Interfaces, you can add, edit, or delete a listening interface.
      To add a listening interface
      1. Click Add.
      2. In the Runtime Listening Interfaces window, select the listening interface from the list.
      3. Specify the listening port.
      4. Select the SSL check box if security is required.
      5. Click OK.
      To modify a listening interface
      1. Select the listening interface to edit.
      2. Click Edit.
      3. In the Runtime Listening Interfaces window, edit the values as needed.
      4. Click OK to save the changes.
      To delete a listening interface
      1. Select the listening interface to delete.
      2. Select Delete.
      3. Confirm the deletion.
    Manage tracing specification
    1. Select the Runtime Tracing link from the top of this page. You can also access this panel from the top menu by selecting Monitor Analysis and Diagnostics > Logs > Runtime Tracing.
    2. Use one of the following ways to edit the trace level of a component.
      • Select the component name from the Component list. Select the ideal trace level for this component from the Trace Level list. Then, click Add. Repeat this process to modify trace levels for other components if needed. To clear all of the tracing levels, click Clear.
        To log all events, select ALL as the trace level.
        Note: This setting increases the amount of data in logs, so use this level when necessary.
        com.ibm.tscc.rtss.*=ALL:com.ibm.sec.authz.*=ALL
com.tivoli.am.fim.trustserver.sts.modules.*=ALL:com.tivoli.am.fim.otp.*=ALL
com.tivoli.am.rba.*=ALL
      • Enter the name and value of the trace component in the Trace Specification field. To modify multiple components, separate two strings with a colon (:). Here is an example.
        com.x.y.*=WARNING:com.a.b.*=WARNING:com.ibm.isam.*=INFO
    3. Click Save.
  3. When you make changes, the appliance displays a message that there are undeployed changes. If you have finished making changes, deploy them.
Parent topic: Configuring Access Manager for Mobile