R98MODAT File ConversionRegarding storage of documents/objects in the database - what about existing media objects? Is there a conversion?
It would be nice if JDE would support FILESTEAM for MS SQL blob data types (and equivalent on other DBs if it exists). Then you could have the best of both worlds.Good advice Russell. We have approximately 1/2 Terabyte of MO Files that I'm not looking forward to moving into expensive RAID 10 storage.
We can place the new tables on a separate tablespace that maps to a RAID 1 drive but I like the idea of using URL links for some of these files (all our scanned documents are stored as PDFs for example).
Except that a lot of environments don't present tiered storage to their enterprise database servers so it may take some reconfiguration or even the acquisition of new storage solutions to support this. The other curiosity is whether the Oracle Cloud Provisioning of JDE will give you the flexibility to deploy a tiered database architecture for E1.No way would I include these tables in the primary database. OCM for the win...
Exactly ! From TR 184.108.40.206, we will be able to store the media object in File system or Database. Jas.ini setting will decide whether media object needs to be stored in Database or File System.Except that a lot of environments don't present tiered storage to their enterprise database servers so it may take some reconfiguration or even the acquisition of new storage solutions to support this. The other curiosity is whether the Oracle Cloud Provisioning of JDE will give you the flexibility to deploy a tiered database architecture for E1.
Obviously this is just an option at the moment but you would expect at some future tools release will become the only option.
Refer the document E1: MOBJ: Understanding Advanced Media Object (MOBJ) functionality available in 9.2.1 and newer (Doc ID 2199562.1)Hey E1Tips, my read of Document 2212744.1 doesn't indicate that we will still have a option of choosing File System or Database.
We either batch convert or it will automatically move MO files to the database as they are opened by users (terrible approach IMO).
Anyway 2212744.1 says:
"With Tools Release 9.2.1, media objects are now written to and read from the database instead of the file system. All new media objects are automatically inserted into the database table F98MODAT. All existing media objects need to be migrated from the file system to the database so they can be accessed by users going forward. This can be done on-demand or by batch process. "
. . .
"With 9.2.1, all media object files will be stored in the database. There is no option to choose between file and database."