IBM Support

IV63269: DISABLE HTTP AND HTTPS PORTS TO DURING SILENT CONFIGURATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • It can be difficult to disable HTTP and HTTPS port settings for
    Tivoli Monitoring agents during local and remote deploy
    installation. This requires multiple steps to correctly
    override the Monitoring server connection settings for each
    agent and then the agent may need to be reconfigured as well as
    recycled.
    

Local fix

  • On Windows:
    
    --
    For each agent or Tivoli Monitoring component installed,
    <PP> or <pp> represents the 2 character component code.
    In the %candle_home%\TMAITM6 and %candle_home%\TMAITM6_X64
    directories, locate the K<PP>*CMA.ini, K<PP>*CMA_*.ini,
    K<pp>*cma.ini, K<pp>*cma_*.ini files.
    
    If the *.ini file contains the following string:
    http_server:n
    then this file does not need to be modified.  Skip the following
    two steps and check the *.ini file for the next agent.
    
    If the *.ini file does not contain the following string:
    [Override Local Settings]
    then append the following 2 lines to the end of the *.ini file:
    [Override Local Settings]
    http_server:n
    
    If the *.ini file does contain the following string:
    [Override Local Settings]
    then append the following line to the end of the *.ini:
    http_server:n
    
    --
    For each agent or Tivoli Monitoring component installed,
    <PP> or <pp> represents the 2 character component code.
    In the %candle_home%\TMAITM6 and %candle_home%\TMAITM6_X64
    directories, locate K<PP>*ENV* files.
    
    If the *ENV* file contains the following string:
    http_server:n
    or the *ENV* file does NOT contain the following string:
    KDC_FAMILIES=
    then this file does not need to be modified.  Skip the following
    step and check the *ENV* file for the next agent.
    
    If the *ENV* file does NOT contain the following string:
    http_server:n
    and the *ENV* file contains the following string:
    KDC_FAMILIES=
    then locate and replace any KDC_FAMILIES= lines as follows,
    where <REST> represents everything following KDC_FAMILIES= on
    the original line:
    KDC_FAMILIES=http_server:n <REST>
    
    --
    If either the *.ini or *ENV* files were modified for an agent,
    then the agent and any agent instances need to be reconfigured
    and then recycled.
    
    
    On UNIX or Linux:
    
    --
    For each agent or Tivoli Monitoring component installed,
    <pp> represents the 2 character component code.
    In the $CANDLEHOME/config directory, locate the <pp>.environment
    file .
    
    If the *.environment file exists and contains the following
    string:
    http_server:n
    then this file does not need to be modified.  Skip the following
    three steps and check the *.environment file for the next agent.
    
    If the *.environment file exists and contains the following
    string:
    KDC_FAMILIES=
    then replace any KDC_FAMILIES= lines as follows, where
    <REST> represents everything following KDC_FAMILIES= on the
    original line:
    KDC_FAMILIES=http_server:n <REST>
    
    If the *.environment file exists and does NOT contains the
    following string:
    KDC_FAMILIES=
    then append the following line to the end of the
    *.environment file:
    KDC_FAMILIES=http_server:n ${KDC_FAMILIES}
    
    If the *.environment file does NOT exist, then create the
    <pp>.environment file and append the following line to the end
    of the *.environment file:
    KDC_FAMILIES=http_server:n ${KDC_FAMILIES}
    
    --
    If the *.environment file was created or modified, then the
    agent and any agent instances need to be recycled.
    

Problem summary

  • Disabling the HTTP and HTTPS port settings for Tivoli Monitoring
     agents during remote deploy and local installation and
    configuration requires multiple steps for each agent and agent
    instance.  The Monitoring server connection settings must be
    overridden for each agent and agent instance and then that agent
     needs to be reconfigured and recycled.
    
    
    Turning off the integrated HTTP server for Tivoli Monitoring
    agents so that additional ports are not opened on an endpoint is
    difficult to perform during remote deploy and local installation
    and configuration.  This must be performed separately for each
    agent and agent instance.  If not performed correctly, the
    configuration settings may be over-written during an upgrade
    causing the integrated HTTP server to be started and additional
    ports opened.
    

Problem conclusion

  • Silent install/configuration:
    For Windows and UNIX/Linux, the new silent response file items
    "DISABLE_HTTP=YES" and "DISABLE_HTTP=NO" were added.
    
    GUI install/configuration:
    For Windows, the new check-box labeled "Disable HTTP" was added
    on the "TEMS connection panel".
    For UNIX/Linux, the new check-box labeled "Disable HTTP
    capability" was added on the "TEMS connection panel".
    
    CLI configuration:
    For UNIX/Linux, the new prompt "Disable HTTP capability" was
    added at the end of the agent configuration dialog.
    
    Remote Deploy:
    The new "-p" command line option "DISABLE_HTTP" was added to the
    following tacmd commands:
    setagentconnection, creategroup, editgroup, addgroupmember,
    editgroupmember
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
      | fix pack | 6.3.0-TIV-ITM-FP0004
    

Temporary fix

  • ============
    On Windows:
    -----------
    For each agent or Tivoli Monitoring component installed, <PP> or
    <pp> represents the 2 character component code.
    In the %candle_home%\TMAITM6 and %candle_home%\TMAITM6_X64
    directories, locate the K<PP>CMA.ini, K<PP>CMA_*.ini,
    K<pp>cma.ini, K<pp>*cma_*.ini files.
    The *.ini file may or may not contain the string
    "http_server:n".  If it does, then this file does not need to be
    modified.  Skip the following two steps and check the *.ini file
    for the next agent.
    If the *.ini file does NOT contain the string "[Override Local
    Settings]" then append the following 2 lines to the end of the
    *.ini file:
    [Override Local Settings]
    KDC_FAMILIES=http_server:n @PROTOCOL@
    If the *.ini file contains the string "[Override Local
    Settings]" then append the following line to the end of the
    *.ini:
    KDC_FAMILIES=http_server:n @PROTOCOL@
    --
    If the *.ini file were modified for an agent, then the agent and
    any agent instances need to be reconfigured and then recycled.
    
    
    ============
    On UNIX or Linux:
    ----------------
    For each agent or Tivoli Monitoring component installed, <pp>
    represents the 2 character component code.
    In the $CANDLEHOME/config directory, locate the <pp>.environment
    file.
    If the *.environment file exists and contains the string
    "HTTP_SERVER:N" then this file does not need to be modified.
    Skip the following three steps and check the *.environment file
    for the next agent.
    If the *.environment file exists and contains the string
    "KDC_FAMILIES=" then replace any "KDC_FAMILIES=" lines as
    follows, where <REST> represents everything following
    "KDC_FAMILIES=" on the original line:
    KDC_FAMILIES=HTTP_SERVER:n <REST>
    If the *.environment file exists and does NOT contains the
    string "KDC_FAMILIES=" then append the following line to the end
    of the *.environment file:
    KDC_FAMILIES=http_server:n ${KDC_FAMILIES}
    If the *.environment file does NOT exist, then create the
    <pp>.environment file and append the following line to the end
    of the <pp>.environment file:
    KDC_FAMILIES=http_server:n ${KDC_FAMILIES}
    --
    If the *.environment file was created or modified, then the
    agent and any agent instances need to be recycled.
    ============
    

Comments

APAR Information

  • APAR number

    IV63269

  • Reported component name

    OMEG DIST INSTA

  • Reported component ID

    5608A41CI

  • Reported release

    630

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-06

  • Closed date

    2014-10-23

  • Last modified date

    2014-12-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    OMEG DIST INSTA

  • Fixed component ID

    5608A41CI

Applicable component levels

  • R630 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 November 2022