IJ45093: IN A UNC PATH CONFIGURATION, DOCLINKS IS NOT WORKING EVEN AFTER UPGRADING TO 7.6.1.2 LATEST IFIX

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION:
  In a UNC Path configuration, Doclinks is not working even after
  upgrading to 7.6.1.2 latest IFIX
  
  PROBLEM:
  In a UNC Path configuration, Doclinks is not working even after
  upgrading to 7.6.1.2 with the newer IFIXes.
  New files can be created and stored but if you try to view
  them(or any existing) they do not display.
  This appears to be a browser issue in that it works if we use on
  older browser such as edge v44 or I.E. however with chrome v96
  or edge v96 they fail to open.
  The documents are stored on a separate server(maxp01) and maximo
  runs on(maxp01-19)
  This setup was being used prior to the upgrade however both
  maximo and the document server were the same server(maxp01)
  
  Here are the main definitions sample:
  
  maximo and file server type: Windows 2019 server
  httpd.conf setup
  DocumentRoot "//MAXP01/DOCLINKS"
  <Directory "\\MAXP01\DOCLINKS">
  
  maximo system properties
  mxe.doclink.doctypes.defpath
  \\MAXP01\DOCLINKS
  
  mxe.doclink.doctypes.topLevelPaths
  \\MAXP01\DOCLINKS
  
  mxe.doclink.path01
  \\MAXP01\DOCLINKS=http://maxp01-19
  
  Document Folders
  Attachments
  \\MAXP01\DOCLINKS\ATTACHMENTS
  
  Diagrams
  \\MAXP01\DOCLINKS\DIAGRAMS
  
  images
  \\MAXP01\DOCLINKS\IMAGES
  
  
  For L3/Dev:
  Story points: 4
  Potential fix is to only remove the "file:" if on weblogic, in
  label.jsp:
  if(app.isdoclinkweblogic() && requestHeader.indexOf("Chrome") >=
  0 && requestHeader.indexOf("Edge") == -1 &&
  newlink.substring(1,4).equalsIgnoreCase("ile")) {
  
  
  STEPS TO REPRODUCE:
  In an environment with UNC path configured for DOCLINKS, go to
  any application (Assets) and
  Try to open any attachment (View Attachment) from records with
  doclinks in a Chrome browser.
  
  CURRENT ERRONEOUS RESULT:
  In a UNC Path configuration, Doclinks are not opening
  
  EXPECTED RESULT:
  In a UNC Path configuration, Doclinks are working fine
  
  ENVIRONMENT VERSION:
  Tivoli's process automation engine 7.6.1.2-IFIX20220216-1819
  Build 20200715-0100 DB Build 17612-284 HFDB Build HF7612-76
  IBM Maximo Asset Management Work Centers 7.6.0.4 Build
  20200715-0100 DB Build 17604-119 HFDB Build HF7680-10
  IBM Maximo Enterprise Adapter for Oracle Applications 7.6.1.0
  Build 20200901-1037 DB Build 17610-02
  IBM Maximo Asset Management Scheduler 7.6.8.0 Build
  20200715-0100 DB Build 17680-148 HFDB Build HF7680-26
  IBM Maximo Anywhere 7.6.4.0 Build 20200117_195427-0500 DB Build
  17640-12
  IBM Tpae Integration Framework 7.6.1.2 Build 20200615-2330 DB
  Build 17612-11
  IBM Maximo Spatial Asset Management 7.6.1.0-20210628-1749 Build
  20200716-1706 DB Build 17610-15 HFDB Build HF7610-06
  IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build
  17611-01
  IoT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build
  17603-32
  TPAE OSLC Object Structure 7.6.4.0 Build 20200219_092917-0500 DB
  Build 17640-04
  

Local fix

• Use a web server on the doclinks server, so that the attachments
  are served up as "http:" and not "file:"
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IN A UNC PATH CONFIGURATION, DOCLINKS IS NOT WORKING EVEN    *
  * AFTER UPGRADING TO 7.6.1.2 LATEST IFIX                       *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR will be included in a future release.
  Even with this fix, Chrome will retrict access to local file
  links. Users may be able to install a Chrome plug-in to
  cirumvent this restriction, however this is not supported by
  Maximo now or in the future.
  

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

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels