IBM Support

IJ02087: WHEN USED THE CONTENT TYPE APPLICATION/JSON IN THE END POINT THE MESSAGE IS CREATED WITH TEXT/XML.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When used the content type application/json in the End Point
    the message is created with text/xml (The default content type
    for MIF).
    
    ENVIRONMENT:
    App Server IBM WebSphere Application Server 8.5.5.0
    
    Version IBM Maximo Asset Management 7.5.0.8 Build 201504071004
    DB Build
    V7508-00
    Tivoli's process automation engine 7.5.0.8 Build 20150401-2000
    DB Build
    V7508-33
    IBM Maximo for Utilities 7.5.0.1-20150624-1038 Build
    20120710-0136 DB
    Build V7501-14 HFDB Build HF7501-11
    IBM Maximo Spatial Asset Management 7.5.0.1-20130410-0901 Build
    
    20120714-2208 DB Build V7501-13 HFDB Build HF7501-01
    IBM TPAE Integration Framework 7.5.1.3 Build 20150403-1800 DB
    Build V7513-02
    
    Server OS AIX 7.1
    
    Server DB Oracle 11.2 (Oracle Database 11g Enterprise Edition
    Release
    11.2.0.3.0 - 64bit Production With the Automatic Storage
    Management
    option)
    .
    
    
    STEPS TO REPRODUCE:
    The steps below use MAXDEMO as example:
    
    Prerequisites:
    
    1) Web Server must have JMS queues
    2) Maximo Server must have access to internet
    
    STEPS:
    
    1) Go to End Point application. Create a new record as below:
    End Point: HTTPPF
    Handler: HTTP
    HEADERS: Content-Type:application/json
    HTTPMETHOD: POST
    URL: http://posttestserver.com/post.php?dir=PFTEST
    
    Save.
    
    2)Go to External Systems. Create a new record as below:
    
    System: HTTPPF
    End Point: HTTPPF
    Outbound Sequential Queue: jms/maximo/int/queues/sqout
    Inbound Sequential Queue: jms/maximo/int/queues/sqin
    Inbound Continuous Queue: jms/maximo/int/queues/cqin
    
    Check Enabled.
    
    Publish Channels: MXPERSONInterface
    Check Enabled.
    
    Save.
    
    3)Go to Publish Channels. Search for MXPERSONInterface.
    Click on Select Action => Enable Event Listener.
    Save.
    
    4) Go to People. Create a new record as below:
    Person: PFTEST.
    Save.
    
    5)Open the URL:
    http://posttestserver.com/data/2017/09/27/PFTEST/
    
    Replace the date 2017/09/27 for the data of the test.
    
    A file will be created with all the information sent by Maximo.
    Open
    the file.
    
    Like the example below, the content type is text/xml. Should be
    
    application/json.
    
    Time: Wed, 27 Sep 17 13:07:29 +0000
    Source ip: 199.246.40.54
    
    Headers (Some may be inserted by server)
    CONTENT_TYPE = text/xml
    HTTP_CACHE_CONTROL = no-cache
    HTTP_PRAGMA = no-cache
    HTTP_USER_AGENT = Java/1.6.0
    HTTP_HOST = posttestserver.com
    HTTP_ACCEPT = text/html, image/gif, image/jpeg, *; q=.2, */*;
    q=.2
    HTTP_CONNECTION = keep-alive
    CONTENT_LENGTH = 2218
    REMOTE_ADDR = 199.246.40.54
    DOCUMENT_ROOT = /var/www/html
    REQUEST_SCHEME = http
    CONTEXT_PREFIX =
    CONTEXT_DOCUMENT_ROOT = /var/www/html
    REMOTE_PORT = 57394
    GATEWAY_INTERFACE = CGI/1.1
    REQUEST_METHOD = POST
    QUERY_STRING = dir=PFTEST
    REQUEST_URI = /post.php?dir=PFTEST
    PHP_SELF = /post.php
    REQUEST_TIME_FLOAT = 1506517649.785
    REQUEST_TIME = 1506517649
    
    No Post Params.
    Empty post body.
    
    Upload contains PUT data:
    <?xml version="1.0" encoding="UTF-8"?><PublishMXPERSON
    xmlns="http://www.ibm.com/maximo"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    creationDateTime="2017-09-27T09:06:47-04:00" transLanguage="EN"
    
    baseLanguage="EN" messageID="1506517607385870810"
    maximoVersion="7 5
    20150403-1800 V7513--1" event="1"><MXPERSONSet><PERSON
    action="Add"><ACCEPTINGWFMAIL>1</ACCEPTINGWFMAIL><ADDRESSLINE1><
    /ADDRESS
    LINE1><ADDRESSLINE2></ADDRESSLINE2><ADDRESSLINE3></ADDRESSLINE3>
    <BILLTOA
    DDRESS></BILLTOADDRESS><BIRTHDATE
    xsi:nil="true"></BIRTHDATE><CALTYPE></CALTYPE><CITY></CITY><COUN
    TRY></CO
    UNTRY><COUNTY></COUNTY><DELEGATE></DELEGATE><DELEGATEFROMDATE
    xsi:nil="true"></DELEGATEFROMDATE><DELEGATETODATE
    xsi:nil="true"></DELEGATETODATE><DEPARTMENT></DEPARTMENT><DEVICE
    CLASS>2<
    /DEVICECLASS><DFLTAPP></DFLTAPP><DISPLAYNAME></DISPLAYNAME><DROP
    POINT></
    DROPPOINT><EMPLOYEETYPE></EMPLOYEETYPE><EXTERNALREFID></EXTERNAL
    REFID><F
    IRSTNAME></FIRSTNAME><HIREDATE
    xsi:nil="true"></HIREDATE><IM_ID></IM_ID><JOBCODE></JOBCODE><LAN
    GUAGE></
    LANGUAGE><LASTEVALDATE
    xsi:nil="true"></LASTEVALDATE><LASTNAME></LASTNAME><LOCALE></LOC
    ALE><LOC
    ATION></LOCATION><LOCATIONORG></LOCATIONORG><LOCATIONSITE></LOCA
    TIONSITE
    ><LOCTOSERVREQ>1</LOCTOSERVREQ><NEXTEVALDATE
    xsi:nil="true"></NEXTEVALDATE><NP_STATUSMEMO></NP_STATUSMEMO><OW
    NERGROUP
    ></OWNERGROUP><OWNERSYSID></OWNERSYSID><PCARDEXPDATE></PCARDEXPD
    ATE><PCA
    RDNUM></PCARDNUM><PCARDTYPE></PCARDTYPE><PCARDVERIFICATION></PCA
    RDVERIFI
    CATION><PERSONID>PFTEST</PERSONID><PERSONUID>153</PERSONUID><POS
    TALCODE>
    </POSTALCODE><PRIMARYEMAIL></PRIMARYEMAIL><PRIMARYPHONE></PRIMAR
    YPHONE><
    PRIMARYSMS></PRIMARYSMS><REGIONDISTRICT></REGIONDISTRICT><SENDER
    SYSID>MX
    </SENDERSYSID><SHIPTOADDRESS></SHIPTOADDRESS><SOURCESYSID></SOUR
    CESYSID>
    <STATEPROVINCE></STATEPROVINCE><STATUS
    maxvalue="ACTIVE">ACTIVE</STATUS><STATUSDATE>2017-09-27T09:06:38
    -04:00</
    STATUSDATE><STATUSIFACE>0</STATUSIFACE><SUPERVISOR></SUPERVISOR>
    <TERMINA
    TIONDATE
    xsi:nil="true"></TERMINATIONDATE><TIMEZONE></TIMEZONE><TITLE></T
    ITLE><TR
    ANSEMAILELECTION
    maxvalue="NEVER">NEVER</TRANSEMAILELECTION><VIP
    xsi:nil="true"></VIP><WFMAILELECTION
    maxvalue="PROCESS">PROCESS</WFMAILELECTION><WOPRIORITY
    xsi:nil="true"></WOPRIORITY></PERSON></MXPERSONSet></PublishMXPE
    RSON>
    
    
    CURRENT ERRONEOUS RESULT: Maximo do a POST with the content
    type
    text/xml
    
    EXPECTED RESULT: Maximo should do a POST with the content type
    application/json
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When the content type application/json is used in an End     *
    * Point, the message is created with text/xml (The default     *
    * content type                                                 *
    * for MIF).  Header parameters are not properly set, resulting *
    * in the incorrect message type.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ02087

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-24

  • Closed date

    2017-12-01

  • Last modified date

    2017-12-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

    INTEGRATION

  • Fixed component ID

    5724R46I1

Applicable component levels

  • R760 PSN

       UP

  • R750 PSY

       UP

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

Document Information

Modified date:
01 December 2017