The desktop client export dialog allows you to export files from Elvis to Enterprise, with the possibility to create Dossiers on the fly and select the Enterprise Brand, Category, Issue, etc.
Configuration
Copy or reference files on export
For Elvis 1.0 - 3.x the export always creates a copy of the file in Enterprise when exporting files from Elvis to Enterprise.
This is changed with Elvis 4.0, which introduces a new method that only creates a reference in Enterprise to the file in Elvis. You can find more information about this new method in Elvis Content Source plug-in for Enterprise.
While this new method is enabled by default, the existing copy method is also still available. The behavior can be modified with the following server config options:
#
# Set to true to export assets as shadow objects by default, set to false to create
# a copy of the asset in enterprise by default.
#
# The default setting can be overruled in the AIR-client by setting
# enableExportShadowObjets to true
#
# Exporting shadow objects is supported by Enterprise 8 or higher, this option has
# no effect on exporting to Enterprise 7 or lower.
#
defaultExportShadowObjects=true
#
# Enables a checkbox in the export to Enterprise dialog to allow a choice between
# exporting a copy or a shadow object to Enterprise.
#
# Exporting shadow objects is supported by Enterprise 8 or higher, this option has
# no effect on exporting to Enterprise 7 or lower.
#
enableExportShadowObjects=trueSet up a connection to the Enterprise Server
You can setup a connection to the Enterprise Server on the client machine or on the server. Elvis uses the WWSettings.xml file to retrieve information on the available Enterprise Server(s). Inside the export dialog, a user can select an available Enterprise server and login using their Enterprise credentials.
If both the server and client have a WWSettings.xml file, the files will be merged. On duplicate entries the client setup is preferred over the server setup.
Setup WWSettings.xml server side
To set up the export correctly you will need the WWSettings.xml file from your Enterprise installation. For more information about this file and it's configuration please refer to the Enterprise documentation. The WWSettings.xml file might be serving several Enterprise servers, all of those servers will show up in Elvis when you're exporting.
Setup WWSettings.xml client side
The desktop client detects if the settings file is available locally on the client machine. The file must be present on it's default location:
- Windows: C:\Program Data\WoodWing\WWSettings.xml
- OSX: /Library/Application Support/WoodWing/WWSettings.xml
Configure the export
- Open the Elvis server configuration from the Windows Start menu or from your Elvis server console on Mac OS X.
- Open the sce_export folder.
- Either copy your existing WWSettings.xml file here or...
- Modify the empty WWSettings.xml file provided by the Elvis installer. Typically you will want to add one or more server entries:
<?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://demo.woodwing.net/SCEnterprise/index.php"/>
</SCEnt:Servers>
</Settings>- For the moment only the ServerInfo entries are used by the Elvis sce-export, any other configuration settings are ignored.
- Restart the server to enable the config settings.
Comments
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 here.
3 comments
Suppose the URL changes from HTTP to HTTPS, will that then not work, as by default, <SCEnt:SSL enable="true"/> is disabled in WWSettings.xml? Should <SCEnt:SSL enable="true"/> maybe be enabled by default, as it doesn't has in default cases, and provides actual benefits?
I've created a support ticket for this: https://helpcenter.woodwing.com/hc/en-us/requests/30519
Enabling <SCEnt:SSL enable="true"/> is not required for the Elvis Export to Enterprise feature to work
Please sign in to leave a comment.