IBM Support

JR34084: SCADMGRCREATEALIAS SCRIPT FAILURE WHILE WBI AUGMENTING WAS DEPLOYMENT MANAGER

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Environment :
    
    - WAS 6.1 Deployment Manager and  federated node with few server
    - Installing WPS 6.1.2 and augment the deployment manage.
    - Ref PMR 15008,004,000
    ----------------
    
    Problem:
    
    - Customer was able successfully to install WPS6.1.2 binary
    - Failed to augment WAS deployment manager
    
      Failed during scaDmgrCreateAlias
    
      apps/WebSphere/AppServer/profiles/Dmgr/bin/wsadmin.sh
      -conntype NONE
       -f
    /apps/WebSphere/AppServer/profileTemplates/dmgr.wbicore/actions/
      scripts/scaDmgrCreateAlias.
    
    WASX7017E: Exception received while running file
    "/apps/WebSphere/AppServer/profileTemplates/dmgr.wbicore/actions
    /scripts
    /scaDmgrCreateAlias.jacl"; exception information:
    com.ibm.ws.scripting.ScriptingException: WASX7025E: Error found
    in
    String
    "{_Websphere_Config_Data_Display_Name=(cells/dawss01cell/nodes/i
    nternaln
    ode/servers/ECMA2|security.xml#Security_1243540770946)
    
    (cells/dawss01cell/nodes/internalnode/servers/GSD21|security.xml
    #Securit
    y_1243544256623)
    
    (cells/dawss01cell/nodes/internalnode/servers/JEMS|security.xml#
    Security
    _1243544285410)
    
    (cells/dawss01cell/nodes/internalnode/servers/MQWF-DAWSS01|secur
    ity.xml#
    Security_1243544316458)
    
    ,
    _Websphere_Config_Data_Id=cells/dawss01cell|security.xml#Securit
    y_1}";
    cannot create ObjectName.
    
    Please see more failure information on Page15
    
    -------------------------------
    
    Analysis:
    
    - Experimenting with the scaDmgrCreateAlias to create
      Authentication Alias
    - The script fails to create object if the security is
      configured at multiple SCOPE.
    - This script only works if the security is configured at the
      cell level
    
    -----------------
    
    How to recreate :
    
    - Use ND environment with Dmgr and a Node ( with minimum one
    server)
    - Enable the global security using the AdminConsole
    - Enable the sever level security
      server--> application server--><servername> --> server
      security
      click on "security setting for this server overrides the cell
      setting"
      Make sure "Enable application security" and  "use java 2
      security to
      restrict application access to local resources" is checked.
    - Save and check <dmgr>Config to make sure you have security.xml
      file at the cell level and another one created at the server
      scope
    - Sync the node
    
    - I have uploaded instrumented script saved under
      Ecrup/"support" for testing purpose.  use the script to
       create a new authentication alias.
    
    -  run the  CreateAliasTest1.jacl  script
       wsadmin -conntype NONE  -trace -f CreateAliasTest1.jacl 1
           <AnyName> <anyPassword> dummy_test_alias
    
      You will see the failure to create the object.
    
      --------Code snippet ----
      ...
      ...
    
     set jaasAttrs   [list $authenticationAlias $description $userid
       $password]
       $AdminConfig create JAASAuthData [$AdminConfig list Security]
       $jaasAttrs
    
      ...
      ...
      --------------------------
    
    Probelm is that [$AdminConfig list Security] returns multiple
    security file when security is configured at multiple scope.
    
    scaDmgrCreateAlias.jacl script has to be changed to list only
    cell level Secirity.xml file so that the code will work when
    security is configured at multiple level.
    
    Let me know if you have any questions
    
    -----------------------
    

Local fix

  • Work around:
    - Susing AdminConsole disable application security from the
      Application server level.
    - Make sure security.xml file is deleted under
     <DMgr>/config/<cells>/<nodes><appropriateServer>
    - Complete the Sync operation
    - Stop the deployment manager and all the other JVMs
    - Start  PMT and augment the Deployment Manager
    - After completing the augmentation , you can re-enable the
      security for the Application server level as needed
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Process Server 6.1.x and 6.2.x    *
    *                  users having Network Deployment topologies  *
    *                  with security configuration at multiple     *
    *                  scopes.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: If security is configured at multiple   *
    *                      scopes then scaDmgrCreateAlias jacl     *
    *                      script fails to create SCA_Auth_Alias.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    scaDmgrCreateAlias script fails to create
    SCA_Auth_Alias if security is configured
    at multiple scopes. User might see the
    error error like "Cannot create
    ObjectName".
    
    Failed during scaDmgrCreateAlias
    
    apps/WebSphere/AppServer/profiles/Dmgr/bin/w
    sadmin.sh
    -conntype NONE
    -f
    /apps/WebSphere/AppServer/profileTemplates/d
    mgr.wbicore/actions/
    scripts/scaDmgrCreateAlias.
    
    WASX7017E: Exception received while
    running file
    "/apps/WebSphere/AppServer/profileTemplates/
    dmgr.wbicore/actions
    /scripts
    /scaDmgrCreateAlias.jacl"; exception
    information:
    com.ibm.ws.scripting.ScriptingException:
    WASX7025E: Error found
    in
    String
    "{_Websphere_Config_Data_Display_Name=(cells
    /dawss01cell/nodes/i
    nternaln
    ode/servers/ECMA2|security.xml#Security_1243
    540770946)
    
    (cells/dawss01cell/nodes/internalnode/server
    s/GSD21|security.xml
    #Securit
    y_1243544256623)
    
    (cells/dawss01cell/nodes/internalnode/server
    s/JEMS|security.xml#
    Security
    _1243544285410)
    
    (cells/dawss01cell/nodes/internalnode/server
    s/MQWF-DAWSS01|secur
    ity.xml#
    Security_1243544316458)
    
    ,
    _Websphere_Config_Data_Id=cells/dawss01cell|
    security.xml#Securit
    y_1}";
    cannot create ObjectName.
    

Problem conclusion

  • Problem is fixed in the next fixpack of WebSphere Process
    Server v6.1.2 and v6.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR34084

  • Reported component name

    WEB PROC SERVER

  • Reported component ID

    5724L0100

  • Reported release

    612

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-24

  • Closed date

    2009-10-23

  • Last modified date

    2009-10-27

  • 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

    WEB PROC SERVER

  • Fixed component ID

    5724L0100

Applicable component levels

  • R612 PSY

       UP

  • R620 PSY

       UP



Document information

More support for: WebSphere Process Server

Software version: 6.1.2

Reference #: JR34084

Modified date: 27 October 2009


Translate this page: