IBM Maximo: Migration from NFS to S3 Storage

From Wiki
Revision as of 21:30, 25 February 2024 by Ebasso (talk | contribs) (Created page with "You can configure IBM Maximo and MAS so that it stores attachments in a Simple Storage Service (S3) cloud object storage. This is the best option when migrate from EAM to MAS. To enable this configuration in your Maximo environment by using S3 Storage, it is necessary to: 1) create a bucket in a service cloud in order to store your data. 2) setup Maximo application to use S3 : a. Login into Maximo : b. Go to System Properties Application : c. Change configurations...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

You can configure IBM Maximo and MAS so that it stores attachments in a Simple Storage Service (S3) cloud object storage.

This is the best option when migrate from EAM to MAS.

To enable this configuration in your Maximo environment by using S3 Storage, it is necessary to:

1) create a bucket in a service cloud in order to store your data.

2) setup Maximo application to use S3

a. Login into Maximo
b. Go to System Properties Application
c. Change configurations
Caption text
Header text Header text
mxe.cosaccesskey This value is the access_key_id described in the bucket.
mxe.cosendpointuri This value is the use-geo endpoint address: https://s3.us.cloud-object-storage.appdomain.cloud
mxe.cosbucketname This value is the name defined in the bucket.
mxe.cossecretkey This value is the secret_access_key described in the bucket.
mxe.attachmentstorage

com.ibm.tivoli.maximo.oslc.provider.COSAttachmentStorage

Once this value is set, traditional doclinks will no longer work. To revert, this property must be removed and the server restarted.

mxe.doclink.doctypes.defpath cos:doclinks\default
mxe.doclink.doctypes.topLevelPaths cos:doclinks
mxe.doclink.path01 cos:doclinks=hostname/DOCLINKS
mxe.doclink.securedAttachment True

3) restart Maximo