Esko Logo Back to Esko Support
Choose your language for a machine translation:


Description

This article contains a checklist that can be used whilst performing a FileStore move.

Important

The FileStore migration procedure has changed since WebCenter version 21.07
Be careful to follow the correct instructions which are mentioned underneath for after 21.07 if you're running that version.

Checklist


Procedure for WebCenter version 21.03 and older
Moving the FileStore...
  1. Create the new share and ensure it meets the requirements concerning naming and location:
    1. Default share is named FileStore and can be renamed using alphanumeric characters only. For example: instead of using default location C:\Artios\WebCenter\FileStore, you may create a new share on D: partition called ESKOFS instead, D:\ESKOFS.
    2. New destination share must be shared with the local or domain BGSYSTEM user running the WebCenter services. There is a default password which can be changed as per your requirement. Ensure that the Password never expires.

    3. It is NOT recommended that the group EVERYONE is given access to the new destination share. If so, please remove this share and security permission.
    4. The BGSYSTEM user running the WebCenter services must have full share and security permissions to the new destination share.
    5. The new destination share must be reachable from the WebCenter’s Application Server.
    6. If you are configuring a production Automation Engine server instead of the OBGE (not recommended), the BGSYSTEM user running the Automation Engine server's Services (BGMD) also requires full permissions to the new destination share via Windows networking.
    7. WebCenter’s Application Server should maintain constant connection to the new destination share and at no point shall lose the connection and if so then all WebCenter services must be restarted.
  2. Test communication to new share from the Application Server.
    1. From Application Server, log in as the BGSYSTEM user which runs the WebCenter Services. Browse to the new share and create a new text file within the new share. Delete test file after successful writing.
  3. Stop IIS and WebCenter Services on both the Web- and the Application Server. This ensures that no files are in use and locked for backup.
    1. On the Web Server: stop IIS Admin, Word Wide Web Publishing, HTTP SSL, and WebCenter Tomcat.
    2. On the Application Server: stop WebCenter JBOSS, and WebCenter CAD-X.
  4. Backup the Web Server, Application Server, Database, and current FileStore share. (see KB328008539: WebCenter - Backup Requirements for more detailed backup requirements)
  5. Uninstall WebCenter completely. Please note that changing configuration files is not supported. A reinstall is always required.
  6. Inspect the old FileStore share's Properties. Record the total size, number of files and folders. Use this information after the reinstall is finished for comparison.
  7. Move entire contents of current FileStore share to its new destination share.

After FileStore move...

  1. After the move is completed, ensure new share is not marked as Read Only. If so, remove attribute on share and all subfolders and files.
  2. Rename the old share (for example: \Artios\WebCenter\FileStoreOLD).
  3. Reinstall WebCenter using the new FileStore share. Make sure to use a UNC path to the FileStore location.
  4.  On WebCenter's Application Server, configure the OBGE to use the new FileStore location:
    1. Use the Automation Engine Pilot to log on as an admin
    2. Delete the old container and add a new container pointing to the newly created share.
    3. Delete the old Hot Folder or Access Point (first convert to regular folder) and add a new Hot Folder / Access Point.
    4. Make sure your new Hot Folder or Access Point is Active.
  5. Restart IIS and WebCenter services on both Web Server and Application Server.
  6. Test WebCenter with the new FileStore location.
    1. Upload a graphics file to WebCenter and make sure Checking and Registering works (you get a thumbnail after a while).
    2. Verify that you can open the graphics file in the Viewer.
    3. Verify that you can download documents.

Procedure for WebCenter version 21.07 and newer

Moving the Filestore...

Note

Since 21.07 parts of the FileStore will be managed by the File Storage Configuration:

  • 21.07 allows managing Documents and Thumbnails

  • 22.03 allows managing Avatars and Icons (Project Status, Task Status, Task Type Icon)

  • 22.07 allows managing view files

For remarks on files not yet managed, per version specified above, see underneath remark.

  1. Create the new share and ensure it meets the requirements concerning naming and location:
    1. Default share is named FileStore and can be renamed using alphanumeric characters only. For example: instead of using default location C:\Artios\WebCenter\FileStore, you may create a new share on D: partition called ESKOFS instead, D:\ESKOFS.
    2. New destination share must be shared with the local or domain BGSYSTEM user running the WebCenter services. There is a default password which can be changed as per your requirement. Ensure that the Password never expires.

    3. It is NOT recommended that the group EVERYONE is given access to the new destination share. If so, please remove this share and security permission.
    4. The BGSYSTEM user running the WebCenter services must have full share and security permissions to the new destination share.
    5. The new destination share must be reachable from the WebCenter’s Application Server.
    6. If you are configuring a production Automation Engine server instead of the OBGE (not recommended), the BGSYSTEM user running the Automation Engine server's Services (BGMD) also requires full permissions to the new destination share via Windows networking.
    7. WebCenter’s Application Server should maintain constant connection to the new destination share and at no point shall lose the connection and if so then all WebCenter services must be restarted.
  2. Test communication to new share from the Application Server.
    1. From Application Server, log in as the BGSYSTEM user which runs the WebCenter Services. Browse to the new share and create a new text file within the new share. Delete test file after successful writing.
  3. Log into WebCenter as the ADMIN user (it must be the user ADMIN, not just any administrator user)
  4. Navigate to Admin > Configuration > File Storage Configuration
  5. Under the Storage Configuration tab, expand the drop down for whichever section to be migrated and click 'Add New Storage Location'
  6. Define a new name for the storage location. Example: 'ServerName Filestore Documents'
    1. Keep in mind, you do have the option to add different locations per data type as well as per document type.
  7. Specify the Drive type this FileStore folder will be stored.
  8. Provide the UNC path to the new location.
  9. Click Save.
  10. Once all needed sections are updated, click save.
  11. Go to the Storage Locations tab and select all locations to be migrated. Then click 'Migrate Files'
    1. This can be done while WebCenter is up and running. No restart required.
  12. To monitor the progress of the Filestore migration go to the Storage Migration tab.

Files not managed by migration tool

Per newer version of WebCenter, more files will be managed by this File Storage Configuration. Files which are not managed yet by this Configuration, need to be copied over manually towards the new FileStore location and the new location needs to be configured manually inside the AppConfig.xml

How to change the location inside the AppConfig.xml :

  1. Locate AppConfig.xml file on C:\Artios\WebCenter\Config
  2. Edit AppConfig.xml and only adapt the UNC path for the location that is not managed by the File Storage Configuration
Article information
Applies to

WebCenter 12 and newer

Created25-Jul-14
Last revised

 

AuthorDEKE
CW Number
Contents