IBM Support

IJ39072: UNABLE TO CREATE/SYNC A GRAPHICAL SCHEDULE FROM SOAP WEBSERVICE CALLS.

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

  • DESCRIPTION:
    A Graphical Schedule cannot be created when using the SOAP Web
    Services call.
    
    SOAP Response received is-  "BMXAA7136E - Validation failed
    when the database default values were set".
    
    STEPS TO REPRODUCE:
    1) Go to Integration; Object Structures; Create a new Object
    Structure: MXGSKDPROJECT; Consumed By: Integration;
    
    (i) Under Source Objects for MXGSKDPROJECT; Add new Objects;
    
    (a) Object: SKDPROJECT; Object Location Path: SKDPROJECT
    (b) Object: SKDQUERY; Parent Object: SKDPROJECT; Object Location
    Path: SKDPROJECT/SKDQUERY; Relationship: SKDQUERY
    (c) Object: COMMITGROUP; Parent Object: SKDPROJECT; Object
    Location Path: SKDPROJECT/COMMITGROUP; Relationship: COMMITGROUP
    
    
    2) Go to Integration; Web Services Library;
    
    (i) From More Actions; Create Web Service; Create Web Service
    from Object Structure; Select: MXGSKDPROJECT;
    
    (ii) From More Actions; Deploy Web Service.
    
    3) (i) Verify if the Web Service is accessible by accessing the
    URL in the browser
    http://localhost/meaweb/wsdl/MXGSKDPROJECT.wsdl
    (ii) Go to SOAPUI, import the wsdl by accessing the above URL
    
    4) Send a WebService request to the URL after adding header in
    the SOAPUI
    (i) Header: maxauth; Value: bWF4YWRtaW46bWF4YWRtaW4= (base64
    format for maxadmin:maxadmin)
    (ii) SOAP URL: http://localhost/meaweb/services/MXGSKDPROJECT
    (iii) SOAP Body:
    ------
    <soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:max="http://www.ibm.com/maximo">
    <soapenv:Header/>
    <soapenv:Body>
    <max:CreateMXGSKDPROJECT>  <max:MXGSKDPROJECTSet>
       <max:SKDPROJECT action="AddChange">
         	<NAME>TEST001</NAME>
    		<SCENARIONAME>TEST001</SCENARIONAME>
    		<ORGID>EAGLENA</ORGID>
    		<CALNUM>DAY</CALNUM>
    		<STARTDATEACM>2021-10-05T21:00:00+00:00</STARTDATEACM>
    		<ENDDATEACM>2021-10-19T21:00:00+00:00</ENDDATEACM>
    		<SHIFTNUM>COMP1</SHIFTNUM>
    		<INCLUDWONODATES>1</INCLUDWONODATES>
    
       </max:SKDPROJECT>
     </max:MXGSKDPROJECTSet>
    </max:CreateMXGSKDPROJECT>
    </soapenv:Body>
    </soapenv:Envelope>
    
    
    (iv) Result (SOAP Response):
    ------
    <soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
      <soapenv:Body>
         <soapenv:Fault>
            <faultcode>soapenv:Server</faultcode>
            <faultstring>BMXAA7136E - Validation failed when the
    database default values were set. See the associated message for
    more information.
    	null</faultstring>      </soapenv:Fault>
      </soapenv:Body>
    </soapenv:Envelope>
    
    
    (v) Errors similar to below can be see in the logs:
    -----------
    0000011f LocalExceptio E   CNTR0020E: EJB threw an unexpected
    (non-declared) exception during invocation of method
    "secureProcessMOS" on bean "BeanId(MAXIMO#mboejb.jar#mosservice,
    null)". Exception data: javax.ejb.EJBException: nested exception
    is: psdi.util.MXApplicationException: BMXAA7136E - Validation
    failed when the database default values were set. See the
    associated message for more information.
           null
           at psdi.iface.mos.MOSServiceBean.secureProcessMOS(MOSSer
    viceBean.java:126)
    ...
    Caused by: psdi.util.MXApplicationException: BMXAA7136E -
    Validation failed when the database default values were set. See
    the associated message for more information.
           null
           at psdi.mbo.Mbo.setDatabaseDefaultValues(Mbo.java:5345)
    ...
    Caused by: java.lang.NullPointerException
           at com.ibm.tivoli.maximo.skd.app.FldSKDProjectIncludeWOn
    odates.action(FldSKDProjectIncludeWOnodates.java:53)
           at psdi.mbo.MboValue.validate(MboValue.java:1768)
           at psdi.mbo.MboValue.validate(MboValue.java:1645)
           at psdi.mbo.Mbo.validateAttributes(Mbo.java:5126)
           at psdi.mbo.Mbo.setDatabaseDefaultValues(Mbo.java:5339)
           ... 43 more
    
    
    
    RESULT:
    
    Graphical Schedule is not created and an error is thrown-
    "BMXAA7136E - Validation failed when the database default values
    were set".
    
    
    EXPECTED RESULT:
    
    Graphical Schedule should be created.
    
    
    REPORTED IN VERSION:
    IBM Maximo Asset Management Scheduler 7.6.8.0
    Tivoli's process automation engine 7.6.1.2
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Scheduler users                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following
    maintenancepackage:
    Release 7.6.1.3 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ39072

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-03-29

  • Closed date

    2022-09-12

  • Last modified date

    2022-09-12

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
13 September 2022