When WoodWing Enterprise is integrated with Elvis 5, assets that are stored in Elvis can be exported to Enterprise for use in a production workflow.
To make this work, several configuration steps are necessary:
- Making Enterprise Server instances available to the Desktop client
- (Optional) Configuring Elvis Server
1. Making Enterprise Server instances available to the Desktop client
When a user wants to export assets to Enterprise, the Enterprise Server to export to needs to be chosen first.
The names and locations of these Enterprise Server instances are stored in the WWSettings.xml file, a file that is used by Enterprise Server and its clients to communicate with each other.
Elvis Server retrieves this information from this file and makes it available as options to choose from in the Export window in the Desktop client.
Figure: Choosing the Enterprise Server instance to export to in the Desktop client.
It is assumed here that you have such a file available or at least have the URLs of the Enterprise Server instances.
- Mac OS X: /Library/Application Support/WoodWing
- Windows: c:\ProgramData\WoodWing
Note: This folder is hidden by default. To display this folder, change the folder options. (See the Windows Help file.)
Making the WWSettings.xml file available can be done on Elvis Server or on the system where the Desktop client is installed.
|
Note:
|
Step 1. In the Config folder of your Elvis installation, open the folder named sce_export.
Step 2. Do one of the following:
- Replace the empty WWSettings.xml file by a fully configured version.
- Open the emtpy WWSettings.xml file and add the URLs to Enterprise Server between the <SCEnt:Servers> </SCEnt:Servers> tags.
<?xml version="1.0" encoding="utf-8"?>
<Settings xmlns:SCEnt="urn:Smart Connection Enterprise" xmlns:WoodWing="urn:WoodWing Software">
<SCEnt:Servers>
<SCEnt:ServerInfo name="WoodWing" url="http://www.woodwing.com/Enterprise/index.php"/>
</SCEnt:Servers>
</Settings>Important: Make sure to validate the WWSettings.xml file for correct content. See Validating the WWSettings.xml file.
Step 3. Restart Elvis Server.
Make sure that the WWSettings.xml file is available in the following location:
- Mac OS X: /Library/Application Support/WoodWing
- Windows: c:\ProgramData\WoodWing
Note: This folder is hidden by default. To display this folder, change the folder options. (See the Windows Help file.)
Important: Make sure to validate the WWSettings.xml file for correct content. See Validating the WWSettings.xml file.
2. Configuring Elvis Server
The following options can be configured on Elvis Server:
- Exporting the asset as a copy instead of as a reference
- Options for routing the exported asset to an Enterprise user
Exporting the asset as a copy instead of as a reference
When an asset is exported from Elvis to Enterprise, a reference to that asset is created in Enterprise that links to the original asset in Elvis (such references are also known as 'shadow objects'). This makes sure that:
- Any changes to the asset in Elvis are reflected in all locations in Enterprise where the asset is used
- Any metadata modifications that are made in Enterprise are also implemented in the asset in Elvis
In case a copy of the asset should be created instead (which is not linked to the original asset in Elvis), set the following option in the cluster-config.properties.txt file:
defaultExportShadowObjects=false
Letting the user control this setting
When the user should also be given the choice to export the asset as a copy or as a reference, a check box can be shown in the Export window. Do this by setting the following option in the cluster-config.properties.txt file:
enableExportShadowObjects=true
Automatically routing the exported file to an Enterprise user
The first step of the export process is to log in to Enterprise Server. The user credentials that are used for logging in are also used for automatically routing the exported assets to that user. This behavior can be controlled through the following option in the cluster-config.properties.txt file:
sceRouteToUser=true
The following settings can be used:
- true (default). The exported assets are routed to the user which credentials were used for logging in to Enterprise.
- false. The exported assets are not routed to a user.
- auto (requires Elvis 5.24 or higher). The assets are routed to a user or user group, based on the Route To rules set up in Enterprise Server.
Document history
- 3 May 2017: Added info about automatically routing the exported file to an Enterprise user.
Comment
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
2 comments
When will it be possible to export from Web Pro Client to Enterprise?
Hi,
We dont have an exact time line when this will be added, for now the user would need to drag & drop the files to Content Station or to the Layout. Smart Connection will add the images to Enterprise when they are placed on the Layout.
Small note, it is better to use the product feedback fora to discuss functionality.
Best regards,
Tom
Please sign in to leave a comment.