Customizing EnterMedia App
Click on the Manager tab when logged in as an Adminstrator. If the default catalog doesn't open automatically, select the catalog where you want to create your application. Select the "Create New Application" option.Fill out the fields in the "App Wizard" and then click Save. When setting up a DEV, QA or staging environment it is best to use as many aspects of the production site as possible. The closer the resemblance between the two areas, the more relevant the testing and experimentation will be. EnterMedia allows DAM administrators to export applications or workspaces for backup and testing purposes. There are a number of items that are included and excluded in an application export. Many of the items that are excluded can be exported separately. The application export should not be considered a backup by itself. The assets, users, groups, roles and modules must be backed up, exported or recreated if attempting a full restoration. To export an application, select the application that you wish to export from the initial manager screen. Next, select the application itself from the list of currently installed applications. From the final menu, select export and choose a storage location for the zipped file to reside. The file can then be unpacked and edited locally.
The theme or custom skin. Custom permissions. Special list tables. Scheduled events. Custom data views.
Roles. Modules. Users and Groups. Assets.
Compress your application back into a ZIP file. Make sure that the WEB-INF and other child folders are exposed within the ZIP directory and not buried in multiple folders. Navigate to the Catalog that you want to Import and Application into. Click on "Import Application". On the next screen, select "Choose File" to bring up a file selection dialog and find your Zip file and click "Open". Specify the application path by following the example and finally click "Submit" to import. When the application is imported into a new catalog, make sure that there is not already an existing application with the same name or the asset table and other key files will be over-written. Now that you've imported your application, the changes and customizations that you've made should be applied.
Assets are not included in a standard application export because they could increase the investment time and size of an export exponentially. In order to transfer uploaded assets to the new application the data directory must be copied from the WEB-INF folder. If the application was populated using hot folders then the hot folders themselves will need to be remapped in order to access the original files. In most cases it is sufficient to populate a test environment with only a handful of assets that belong to different groups, libraries and modules to test access and permissions.
If desired, users and groups can be exported in the user import/export area. It is not necessary to import an entire list of users and groups into a dev, qa or staging environment. These environments are best kept simple with a single user in each role or group for testing custom permissions, privacy settings, module access or any other special features.