IJ40259: -DFILE.ENCODING=UTF8 IS MISSING FROM JVM.OPTIONS

APAR status

• Closed as program error.

Error description

• Maximo Integration Framework request that include Swedish
  characters i.e. "åäö" are processing the characters replaced
  with "???" when using Automation Script End Point Handler.
  
  
  In order to support Swedish characters in the script and avoid
  this issue,  WebSphere Liberty requires adding the
  
  -Durl.encoding=UTF8'  JVM argument.
  
  The following documentation was followed:
  
  Configuring JVM options (IBM Maximo Manage 8.2.0)
  https://www.ibm.com/docs/en/maximo-manage/8.2.0?topic=applicati
  on-configuring-jvm-options
  
  However, adding client.encoding.override=UTF-8 to server has no
  impact.
  
  After the change, run a test from a End point with the Test
  Data, for example:
  
  "för tompallsbana"
  
  If you then print out the RequestData as string it looks like
  this instead:
  
  "f?r tompallsbana"
  
  When testing to send the message through a simple outbound
  transaction via Publish Channel and using handler XMLFILE, the
  data containing Swedish characters file looks good.
  
  But if you then take this message and copy the message to the
  End Point that is based on an Automation Script the åäö is
  changed to ???.
  
  The SQL data is correct based on queries in database. This seems
  to be a issue in the sending into Endpoint where there is a
  mis-match between formats resulting in "+" changed to "?"
  
  
  STEPS TO REPRODUCE:
  
  1- Go to Automation Scripts application and select Create Script
  from More Actions menu:
  
  Script: MASHANDLER
  Script Language: Python - test handler
  Log Level: ERROR
  
  2- Copy the following for the script:
  
  from java.lang import String
  xml=String(requestData)
  service.error("debug",xml)
  
  3- Save record & close System Message dialog
  
  System Message
  BMXAA7990I - The automation script was created successfully.
  
  4- Go to Integrations -> End Points application & use Common
  Actions menu to Create New End Point
  
  End Point: MASHANDLER
  Handler: SCRIPT
  Consumed By: INTEGRATION
  
  Properties For End Point: MASHANDLER
  ------------------------------------
  Property: SCRIPT
  Value: MASHANDLER
  
  5- Save record
  
  BMXAA4205I - Record has been saved.
  
  6- Click Test button
  
  The Test End Point window opens
  
  7- In the Test Data window panel enter some English only
  characters:
  
  abcd
  
  8- Click on Test and check the Response window panel
  
  Reponse: psdi.util.MXApplicationException: debug#abcd
  
  Now enter Swedish characters:
  
  åäö
  
  UNEXPECTED RESULTS:
  
  After clicking test, the Response window panel replaces these
  with question marks:
  
  psdi.util.MXApplicationException: debug#???
  
  EXPECTED RESULTS:
  
  Response should be: psdi.util.MXApplicationException: debug#åäö
  
  
  Environment: IBM Maximo Manage 8.2.0
  

Local fix

• Dev to provide fix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Customers/users using MIF and scripting functions that       *
  * depend on Java file encoding.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In some instances certain characters are corrupted.          *
  ****************************************************************
  

Problem conclusion

• _The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 7.6.1.3 Product_
  

Temporary fix

Comments

APAR Information

• 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 SYSTEMS

• Fixed component ID

  5724R46AV

Applicable component levels