Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
  • 1.  Attachments on port 9080 Issue

    Posted 12/24/21 10:41 PM
    Hi All,

    I've got attachments working fine on port 80. That is when I type:

    http://maximo/DOCLINKS/ATTACHMENTS/test12.txt - this works fine

    However, when am trying to access it on 9080 it won't work as per below URL . I already define path in system properties mxe.doclink.path01

    http://maximo:9080/DOCLINKS/ATTACHMENTS/test.txt - this does not work and gives me below message

    SRVE0255E: A WebGroup/Virtual Host to handle maximo:9080 has not been defined.

    I am unable to access port 9080.

    Does anybody know how to get attachments working on port 9080?




    ------------------------------
    Faryal Amjad
    ------------------------------

    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: Attachments on port 9080 Issue

    Posted 12/24/21 10:57 PM
    Pretty sure that's a problem with the deployment in Websphere.  

    Steps to fix:
    1.  Log into the Websphere 
    2.  In the Enterprise Applications list, uninstall Maximo.
    3.  Reinstall Maximo.  Make sure you specify the Maximo host in the hosts step.






  • 3.  RE: Attachments on port 9080 Issue

    Posted 12/25/21 04:36 AM
    I am accessing attachments as per the below link which is working properly. the problem is I want to access the below attachments URL on port 9080. by default it is pointing 80

    http://maximo/DOCLINKS/ATTACHMENTS/test12.txt 

    ------------------------------
    Faryal Amjad
    ------------------------------



  • 4.  RE: Attachments on port 9080 Issue

    Posted 12/27/21 08:03 AM
    What you're trying to utilize is unsecured attachments which has the web server (IBM HTTP Server/IIS) render the attachments. 9080 is the WebSphere port which does not expose Maximo attachments as a virtual directory. I'm not sure why you are looking to have WebSphere expose the attachments, but assuming it's to not have it exposed via web server I'd suggest utilizing secured attachments instead (enable mxe.doclink.securedAttachment system property). You would not have a user friendly URL because each request generates a one time URL to access the file. But it's this aspect that improves security. Only authenticated users with access to the attachment would be able to access the attachment with this property enabled. Exposing via virtual directory using the web server means anyone with the URL can access it, whether they're authenticated in Maximo or not and whether they should have access to the document or not.

    ------------------------------
    Steven Shull
    ------------------------------