This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
We have thousands of documents on a shared network drive which are structured with a basic Hierarchy of folders.
We have many situations where a specific pump is installed in 100 locations within a large plant.
The intent is to have the Pump Manual linked to all these Assets within Maximo.
Instead of attaching the document to 100 Assets, we want to use a URL path to the original document so we can maintain just one version....instead of 100.
You can put in a URL to any place on the web and it will work but a URL path to a file that is in a folder structure on a shared drive will not.
IBM says they never had that design in mind and don't support that approach.
Anyone have any suggestions ? Is this really just a security or access issue ? a Websphere issue ? or what ?
Anyone have this working ?
Regards,
Eric Klemenok 254 230 5399
Check out Launch in Context, I just got it working for a file share that was unreachable from the Maximo server.
-W
________________________________
From: "Klemenok, Eric" <eric.klemenok@mallinckrodt.com>
To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
Sent: Tuesday, April 15, 2014 10:44 AM
Subject: [MAXIMO List] Using URL to link document to multiple assets
We have thousands of documents on a shared network drive which are structured with a basic Hierarchy of folders.
We have many situations where a specific pump is installed in 100 locations within a large plant.
The intent is to have the Pump Manual linked to all these Assets within Maximo.
Instead of attaching the document to 100 Assets, we want to use a URL path to the original document so we can maintain just one version….instead of 100.
You can put in a URL to any place on the web and it will work but a URL path to a file that is in a folder structure on a shared drive will not.
IBM says they never had that design in mind and don’t support that approach.
Anyone have any suggestions ? Is this really just a security or access issue ? a Websphere issue ? or what ?
Anyone have this working ?
Regards,
Eric Klemenok 254 230 5399