DAM Operational Verification - Precisely_EnterWorks - EnterWorks - 11.0

EnterWorks Guide
Product type
Software
Portfolio
Verify
Product family
EnterWorks
Product
Precisely EnterWorks
Precisely EnterWorks > EnterWorks
Version
11.0
Language
English
Product name
Precisely EnterWorks
Title
EnterWorks Guide
Copyright
2024
First publish date
2007
Last updated
2025-01-07
Published on
2025-01-07T07:44:20.997000

DAM Verification Procedures

Test asset upload

  1. Perform this test for each of the following methods of uploading an asset:

    • In the New UI, upload a digital asset using the Upload Digital Assets widget.

    • In the New UI, upload a digital asset by opening the DamMaster repository in a Repository View and clicking the Upload button on the Repository View's Activity bar.

    • In the Classic UI, upload a digital asset using the Upload Digital Assets widget.

    • In the Classic UI, upload a digital asset by opening the DamMaster repository in a Repository View and click the Upload Image icon on the Repository View's Action bar.

    • If EnterWorks has been configured for Bulk Import, place an asset into the DamDrop folder.

    For each of the tests:

    1. Upload an asset.
    2. Check that the asset's record appears in DamMaster.
    3. Check that the asset appears in the DAMRoot folder.
    4. If the asset is an image, check that the image's variants have been created correctly.
    5. Download the file and any variants that were created. Examine them to ensure they were correctly uploaded, generated, and downloaded.
    6. If you are using non-local DAM storage, use a non-EnterWorks application to view the storage and verify that the asset and all of its variants were uploaded.

  2. Test uploading an image from a linked record:

    This test exercises core DAM functionality and it also exercises other major EnterWorks components. Therefore, a failure of this test does not necessarily indicate a failure of DAM processes.

    Perform the following in both the New and Classic UIs:

    1. Open a record for editing in the Detail Editor.
    2. Import and link an asset.
    3. Verify the following:

      • Verify that the asset has been linked properly.

      • If the asset is an image, verify that the image's thumbnail appears when the record is displayed in a Repository View.

Test variant generation

  • Test automatic image variant generation:

    1. Remove one of the variants of an image.
    2. Re-upload the image.

      • The variant should have been re-created.

      • Check that the variant appears in DamMaster.

      • Check that the variant appears in the DAMRoot folder.

  • Test the image regeneration:

    In both the New and Classic UIs, test the Regenerate Variants function:

    1. Trigger the regenerate variants function:

      • In the New UI:

        1. Open DamMaster in a Repository View.
        2. Select one or more images.
        3. Open the More dropdown by clicking the button on the Repository View's Activity Bar and select Regenerate.

      • In the Classic UI:

        1. Open DamMaster in a Repository View.
        2. Select one or more images.
        3. Open the Action dropdown menu and select Generate Variants.
    2. Ensure that the variants were generated correctly.

  • Other Variant Tests:

    • Ensure that variants of each type can be displayed.

    • Ensure that variants of each type can be downloaded.

Test the Image Report and DAM Cleanup

  • Test the case of an existing asset that is not in DamMaster

    1. Choose an existing asset that is in both DamMaster and the DAMRoot folder.
    2. Delete the asset's record from DamMaster.
    3. Run the Image Report.
    4. Check the Image Report job's log file to verify that it recognizes that the asset's record is missing from DamMaster.
    5. Run a DAM Cleanup job.
    6. Check the Image Report job's log file to verify that the asset has been removed from the DAMRoot folder.

  • Test the case of DamMaster linking to an asset that does not exist:

    1. Choose an existing asset that appears in both DamMaster and the DAMRoot folder.
    2. Delete the asset from the DAMRoot folder.
    3. Run the Image Report.
    4. Check the Image Report job's log file to verify that it recognizes that the asset is missing from the DAMRoot folder.
    5. Run a DAM Cleanup job.
    6. Check the Image Report job's log file to verify that the asset's record has been removed from DamMaster.

Rebuild EPIM Database Indexes

The database indexes used by EnterWorks may become fragmented over time, which can significantly impact query performance. To address this, the indexes should be rebuilt on a regular basis, such as weekly. You may also want to rebuild them if many changes have been made to the EPIM database.

In the process of rebuilding the indexes, you will be directed to run theIndexFragmentation script. To determine how frequently indexes should be rebuilt, rebuild the indexes, then immediately afterward create a baseline report by running the IndexFragmentation script again. Save the baseline report, then at periodic intervals, (daily or weekly), run the script again and compare the new report to the baseline report. Specifically, look for tables with a large page count and a high increase in fragmentation. If the fragmentation is increasing dramatically, consider rebuilding your indexes more frequently.

Note: Some tables are transient in nature. Rebuilding the indexes for these tables may not result in a significant improvement in performance. Tables most likely to be transient have names that contain the text "TMP" or "BATCH".

To rebuild the EPIM database indexes:

  1. Connect to the EPIM database using SQL Server Management Studio.
  2. Copy the IndexFragmentation script and run it in SQL Server Management Studio.
  3. In the Results, select the Table column for the rows that have an avg_fragmentation_in_percent column value of 20 or higher. Right-click the selected rows and click Copy with Headers.
  4. Paste the rows to an empty Excel spreadsheet.
  5. Sort the spreadsheet on the Table column.
  6. Select the rows you just pasted and click the Remove Duplicates button.
  7. Check the My data has headers and the Table checkboxes, then click OK.
  8. Copy the text: =CONCATENATE("ALTER INDEX ALL ON ", A2, " REBUILD") to the B2 cell of the spreadsheet:
  9. Copy the value of the B2 cell and paste it to the B column cell for all the other rows except the header. This will result in all the B column values changing to ALTER INDEX ALL ON <table-name> REBUILD.
  10. Copy the contents of the B column and paste it in the SQL Server Management Studio's Query window.
  11. Run the commands. Depending upon the total number of records, this operation may take some time.

indexfragmentation Script

See: indexfragmentation Script.