GOAL

How to move the media objects off a Deployment Server to a different server, like the Enterprise or Batch servers or new deployment server. What is the process or procedure to accomplish this?

Overview

EnterpriseOne media object queues allow storage location of media objects to be tracked by reference as opposed to physical network location. This allows for easy administration of the media object queue location. For example, the location for media objects on your server can change, and the change only has to be reflected in one place, P98MOQUE.

If a change is made to the P98MOQUE, the user may have to log out / in to see the changes.

Media objects can be moved to another server as long as the server is Windows based. The OLEQUE has to be on a Windows box because the OLE objects are stored as a .stg format (see note below).  After moving the physical files and directories you have to make sure to go back into P98MOQUE and change the paths to the media object folder so they point to the new place. 

There are different requirements for setting up the web client based on the type of operating system being used. Although we do not recommend other configurations, it is possible for customers to setup their media object files on a non-Windows operating system on a release with tools release 8.97 or later using the Web client only.  See Document 845387.1 for web configuration.  It is up to the customer to setup this configuration and test it. Since all of our upgrade table conversions expect the media objects to be stored on the Windows E1 Deployment server, moving the media object files to the standard configuration may be a requirement during an application upgrade.)  

If the web and MOBJ file server runs on Windows, then Windows file sharing may be used. However, if the web server or file server is running on a non-Windows operating system such as Unix, Linux, AS400 / iSeries, then FTP will have to be used. Please note: Windows users can opt to use FTP if they desire.  
 
However for customers that have upgraded from older releases the restriction with .STG files still applies as they can only be stored on Windows platform. If access to these upgraded files is necessary, the recommendation is to use the Windows platform.

Access the Media Object Queues Application (P98MOQUE).  Within this application, verify that the path for the media object queue is valid. 

\\servername\(E1 Application Release)\mediaobj\oleque 

where server name is the network name of the server and where the E1 Application Release would be B7333, B7334, B9, E810, E811, E812, E900. Verify that the directories exist and that the directory is the share name and not a drive letter path.  

Verify that the appropriate NT permissions exist for the user. Users need CHANGE permissions (on NT) to use media objects.

OLE

You define a media object queue to identify the pointer to the location where the actual attachment files or OLE objects reside.

In EnterpriseOne, the OLE object attached to a row or a form is actually a shortcut to the OLE object that resides in a media object queue.  Therefore, just changing the path where the OLE queue will be pointing will be enough for telling the application where to go now to find those objects.  This is different with OLE linked attachments.  Linked records are stored in the stg file and may have to be deleted and reattached if the linked file needs to be moved, Document 636127.1.

Details Specific to Xe/ERP8

Attempt to view from the fat client first.  Sometimes trying to view the attachments from the fat client will correct the path in the F00165 and thus allow the users to access the attachment via the web.

With Xe/ERP8, the fixed path is actually stored in the F00165 blob field, and does not automatically update with the new queue path.  This is something development changed in later releases.  Also, beginning with the 8.9 release level, there is a separate field in the table which stores the path.  Thus allowing easy viewing/updating if the need arises.

Since Xe/ERP8 does not allow for modifying the file location, the following are some additional options:

  1. Change the name of the server to be the same as the old server name.  (Easiest/recommended solution)
  2. Reattach all media objects
  3. Create a custom BSFN to update the F00165 with the correct path.
  4. Use the upgrade table conversions to change the file location (An idea, do not know if this would work or not.)
  5. Give the new Windows server a second name (old server name) via DNS

8.9 and higher

There is a new field in the F00165 table, GTFILENM, which may need to be updated using SQL in order to correct the new server path. The following is an example SQL statement to update this field.   

update testdta.f00165 set GDGTFILENM = replace(rtrim(GDGTFILENM),'\\old_deployment_server\b9', '\\new_deployment\e812') where GDGTFILENM like 'C:%'

Prior to running any SQL statement over the F00165, first make a working backup of the F00165 table.