IBM Support

IJ09116: BMXAA4191E - THE VALUE MXASSET IS NOT VALID FOR APPLICATION WHEN USING MIGRATION MANAGER WITH OBJECT STRUCTURE SECURITY

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • STEPS TO REPRODUCE:
    1) Go To Object Structures
    2) Select the MXASSET object structure
    3) More Actions -> Configure Object Structure Security
    4) Select the Use Object Structure for Authorization Name?
    checkbox
    5) Receive message
    BMXAA9299W - Authorization enablement is configured using the
    Object Structure name.
    6) Click OK
    7) Click OK
    
    8) Go To Security Groups
    9) Select the maxadmin group
    10) Click on the Object Structures Tab
    11) Filter for and select MXASSET
    12) Grant Listed Options for This Object Structure
    13) Save Group
    
    14) Go To Migration Manager
    15) Common Actions -> New Package Definition
    Name = Test
    Type = Snapshot
    Processing Action = Replace
    
    16) In the Migration Groups Section, click New Row
    17) On the Detail Menu, Click Go To Migration Groups
    18) Click New Migration Group
    19) Name = TEST_MG
    
    20) In Migration Objects for, click New Row
    21) Select Object Structure DMMAXGROUP
    22) Save Migration Group
    23) Return with value
    
    24) In the Migration Groups Section of the Package Definition
    Tab, Click on Set Where Clause
    25) Type groupname = 'MAXADMIN'
    26) Click OK
    
    27) Change Status to Approved
    
    28) On the Package Tab, click Create
    29) Click Continue
    30) Wait for successful creation, then click OK
    
    31) On the Package Tab, click Distribute
    32) Select any target
    33) Click OK
    34) After successful distribution, click OK
    
    35) In the packages section, click download
    36) Save the .zip file to a location of your choice
    
    37) More Actions -> Delete Package Definition
    38) Click Yes
    
    39) Use the Security Groups Application to revoke all
    permissions on the MXASSET Object Structure for group maxadmin
    and save the changes
    
    40) Go To Migration Manager
    41) Common Actions -> Upload Package
    42) Select the file that was downloaded above
    43) Click OK
    
    44) Common Actions -> Deploy Package
    45) Make sure you have a current database backup and then
    select Do you have a current backup
    46) Click on Deploy
    
    RESULTS:
    Messages in Browser
    
    BMXAA6163I - [8/8/18 6:41 AM] Could not import configuration
    records for package <packagename>
    
    BMXAA5259E - Could not deploy package <packagename> Please
    check log entries for more information.
    
    On the Messages tab, messages include
    
    Please review log file for more detail.
    psdi.util.MXApplicationException: BMXAA4191E - The value
    MXASSET is not valid for Application. Specify a valid value for
    Application.
    at psdi.mbo.MAXTableDomain.validate(MAXTableDomain.java:167)
    at psdi.mbo.MboValue.validate(MboValue.java:1713)
    at psdi.mbo.MboValue.validate(MboValue.java:1616)
    at psdi.mbo.Mbo.validateAttributes(Mbo.java:5002)
    at psdi.mbo.Mbo.validate(Mbo.java:4575)
    at
    psdi.iface.mos.MosProcessImpl.checkValidateErrors(MosProcessImpl
    .java:2336)
    at
    psdi.iface.mos.MosProcessImpl.setAdditionalTableData(MosProcessI
    mpl.java:1710)
    at
    psdi.iface.mos.MosProcessImpl.createChildrens(MosProcessImpl.jav
    a:969)
    at
    psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessImpl.ja
    va:810)
    at
    psdi.iface.mos.MosProcessImpl.processExternalData(MosProcessImpl
    .java:344)
    at
    psdi.iface.mos.MosProcessImpl.processObjectStructureService(MosP
    rocessImpl.java:239)
    at
    psdi.iface.mic.MicService.processObjectStructureData(MicService.
    java:859)
    at psdi.iface.mic.MicService.loadData(MicService.java:698)
    at psdi.dm.pkg.DMPackage.deployStagingData(DMPackage.java:1516)
    at psdi.dm.pkg.DMPackage.deployPackage(DMPackage.java:1026)
    at
    psdi.webclient.beans.dm.DMAppBean.deployPackage(DMAppBean.java:3
    51)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:90)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:55)
    at java.lang.reflect.Method.invoke(Method.java:508)
    at
    psdi.webclient.system.session.AsyncProcess.run(AsyncProcess.java
    :172)
    at java.lang.Thread.run(Thread.java:811)
    
    EXPECTED RESULTS:
    Package should be imported without error
    
    PRODUCT VERSION:
    Tivoli's process automation engine 7.6.0.9-IFIX20180522-0831
    Build 20171127-0100 DB Build V7609-45 HFDB Build HF7609-04
    IBM TPAE Integration Framework
    7.6.0.9-MIF_7609_IFIX.20180510-0926 Build 20171127-2230 DB
    Build V7609-32
    TPAE OSLC Object Structure 7.6.2.1 Build 20180516_140928-0500
    DB Build V7621-06
    IBM Maximo Linear Management 7.6.0.2 Build 20171127-0100 DB
    Build V7602-03
    IBM Maximo Asset Management Scheduler 7.6.7.0 Build
    20171127-0100 DB Build V7670-56 HFDB Build HF7670-17
    IBM Maximo Anywhere 7.6.2.1 Build 20180516_141011-0500 DB Build
    V7621-03
    IBM Maximo Asset Management Work Centers 7.6.0.3 Build
    20171121-0723 DB Build V7603-175
    IBM Maximo Asset Management 7.6.0.9 Build 20171127-0100 DB
    Build V7604-01
    

Local fix

  • Temporarily remove Java class APPLICATIONAUTH.APP before a
    migration and put it back afterwards.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Administrators migrating a security configuration from one   *
    * environment to another.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When migrating applicationauth records, a generic error may  *
    * be encountered, even if the correct MAXAPPS record(s) exist: *
    * "BMXAA4191E - The value {app} is not valid for Application.  *
    * Specify a valid value for Application."                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is included in the following package:
                             | Release 7.6.1.1 of Base Services.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ09116

  • Reported component name

    MIGRATION MANAG

  • Reported component ID

    5724R46MI

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-09-13

  • Closed date

    2018-10-01

  • Last modified date

    2018-10-01

  • 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

    MIGRATION MANAG

  • Fixed component ID

    5724R46MI

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management
Migration Manager

Software version: 760

Reference #: IJ09116

Modified date: 01 October 2018