IBM Support

PK78515: APPLICATION DEPLOYMENT ERROR GENERATING IN CONSOLE WITH ADMA0207E

Fixes are available

7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for AIX
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for IBM i
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for HP-UX
7.0.0.5: Java SDK 1.6 SR5 Cumulative Fix for WebSphere Application Server
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Solaris
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
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
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
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.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

  • An application has an EE5 module and when you try to deploy it
    via the console the error ADMA0207E: is generating in WebSphere
    Application Server v7.0 deployment wizard.
    
    Console Message:
    
    The EAR file could be corrupt and/or incomplete. Make sure that
    the application is at a compatible Java(TM) Platform, Enterprise
    Edition (Java EE) level for the current version of WebSphere(R)
    Application Server.
    com.ibm.websphere.management.application.client.AppDeploymentExc
    eption: ADMA0207E: EE 5 module <WAR MODULE NAME.war> in ear file
    contains unsupported xmi format bindings file.
    
    The error description in WebSphere Application Server v7.0
    information center says, convert the xmi binding files
    to xml file using the conversion tool.
    
    http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?
    topic=/c
    om.ibm.websphere.messages.doc/com.ibm.ws.management.resources.Ap
    pDeploymentMessages.html
    
    
    ADMA0207E:
    EE 5 module {0} in ear file contains unsupported xmi format
    bindings file.
    
    Explanation:
    xmi format bindings files are not supported for EE5 modules. Use
    xml format instead.
    
    Action:
    Convert all the xmi bindings files for EE5 modules in the
    archive to the xml format by using the conversion tool.
    
    That text is not appropriate, and should be fixed (since the
    tool is still under development).
    
    Basically, applications at an EE 5 spec level have a different
    format for IBM bindings and extensions data. Before EE 5, we
    had an XMI format, while at EE 5 (and above) has an XML format.
    
    When moving from before EE 5 to EE 5, the XMI files have to be
    removed, otherwise, you will see that error.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere Application Server   *
    *                  version 7.0.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: The user action for error message       *
    *                      ADMA0207E in the Information Center     *
    *                      refers to a conversion tool which is    *
    *                      not yet available.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The user action message in the Information Center for an error
    in an enterprise application with Java Enterprise Edition
    (Java EE) 5 module containing unsupported xmi bindings file
    refers to a conversion tool to help customer to convert xmi to
    xml bindings format. However, such a conversion tool is not
    yet available. The error is
    
    ADMA0207E:
    EE 5 module {0} in ear file contains unsupported xmi format
    bindings file.
    

Problem conclusion

  • The explanation and user action messages for error ADMA0207E
    were modified to explain the bindings files difference between
    Java EE 5 and pre-Java EE 5 modules.
    
    Explanation
    
    This error occurs when a module has a version that is
    associated with Java Enterprise Edition (Java EE) 5 and the
    module has IBM Bindings and Extensions files in an older XMI
    format. When a module has a Java EE 5-specific version, the
    bindings and extensions files of that module must not use the
    old XMI format. Instead, the bindings and extensions files of
    the module must use the new XML format.
    
    IBM Bindings and Extensions files in the older XMI format have
    a .xmi file extension. IBM Bindings and Extensions files in
    the new XML format have a .xml file extension. If a module has
    a deployment descriptor, then that deployment descriptor
    records the version of the module. IBM WebSphere Application
    Server Version 7.0 assigns a Java EE 5-specific version to a
    module that does not have a deployment descriptor. Module
    versions that are specific to Java EE 5 are 2.5 for Web
    archive (WAR) files and 3.0 for Enterprise JavaBeans (EJB)
    Java archive (JAR) files.
    
    Action
    
    Either revert the module version to a pre-Java EE 5 value or
    remove the bindings and extensions files for the module.
    Important: Do not rename the bindings and extensions files to
    change the file extension from .xmi to .xml.
    
    Note: The error is specific to individual modules. When you
    fix this problem, only update the specific modules that are
    exhibiting the problem.
    
    If you remove the bindings and extensions files, the files can
    be regenerated using the application deployment process. Also,
    you can regenerate the bindings and extensions files using
    application development tools.
    
    
    The fix for this APAR is currently targeted for inclusion in
    fixpack 7.0.0.5.  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

    PK78515

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-01-13

  • Closed date

    2009-03-27

  • Last modified date

    2009-03-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVS22","label":"General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 March 2009