IBM Support

PM24073: IHS COLLOCATED WITH THE DEPLOYMENT MANAGER DOES NOT SUPPORT PLUGIN PROPAGATION VIA IHS ADMIN SERVICE OR NODE AGENT

Fixes are available

7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When an IBM HTTP Server web server is collocated on the
    Deployment Manager the propagation method for the
    plugin-cfg.xml file is a local file copy to the location
    specified in console under Web Servers>webservername>Plug-in
    Properties:
    *Plug-in Configuration directory and file name
    (defined in the webserver defintion's Server.xml)
    
    Deployment Manager makes a determination to see if the IBM
    HTTP Server host/ip is the same as the Deployment Manager and
    sets a flag as either 'Local' or 'Remote". If the flag is
    local the OS file copy process is called.
    
    This method also supports plugin-cfg.xml propagation for
    non_IBM HTTP Server web servers that are collocated with the
    Deployment Manager and is considered superior to using IBM
    HTTP Server Admin Service or Node Sync. This also means that
    the permissions are with the WebSphere username that logged
    into WebSphere and not those granted under IBM HTTP Server
    Admin Service.  Some environments will not allow usernames
    with permissions to manage WebSphere to have permissions over
    WebServer files due to security policies. This causes localcopy
    propagation of plugin files to fail and currently we have no
    method to alternate to the other propagation methods via IBM
    HTTP Server Admin or Node Agent in this senario.
    
    WebSphere Application Server needs a fix to allow localcopy of
    plugin files (cfg,kdb,sth) to be done thru the IBM HTTP Server
    Admin Service port or Node Agent port (depending on IBM HTTP
    Server being defined as managed or unmanaged) instead of
    localcopy. using the OS copy feature.. This is needed to
    correctly interact with all security policies.
    
    LOCAL FIX:
    Manual propagation of the plugin-cfg.xml
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.1 and V7.0                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Propagation of the plugin doesn't       *
    *                      work with co-located web server.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Propagation of the plugin may fail for a web server that is
    co-located with the Dmgr due to stringent file system
    security.  Web servers that reside on the same box as the Dmgr
    use a straight file system copy method instead of the Node
    Sync.
    

Problem conclusion

  • A new system property has been added
    "localWebServerUseNodeSync".  This new property takes the
    node name associated to the web server.  When set, plug-in
    propagation will use the node sync process instead of the file
    system copy method.
    
    This new property is set within the Dmgr at:
    System Admin>Deployment Mgr>Java and Process
    Management/Process Definition>Java Virtual Machine>Custom
    Properties.  This property can take multiple values (node
    names) which need to be separated with a semi colon ";".
    
    Since this is set as a system property, this is not available
    when using the GenPluginCfg script.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.37 and  7.0.0.15.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM24073

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-10-07

  • Closed date

    2010-10-20

  • Last modified date

    2016-10-11

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM24073

Modified date: 11 October 2016