This page may be out of date for versions after CQ 5.5. It has not been tested.
Making your Vignette repository JCR compliant consists of the following steps:
- Installing and configuring the CRX repository used as framework for the Vignette V7 connector
- Installing the Vignette V7 connector and the included remote access extension
- Configuring the Vignette V7 connector
The CRX Connector for Vignette V7 includes the following functionality:
- Read from the Vignette repository via the Vignette CMS API
- Execute queries on the Vignette repository
- Use the user accounts and access controls (ACLs) specified in the Vignette repository
- Observe user and content changes that occur in the Vignette repository
The connector runs on the following operation systems:
- Windows Server 2000, 2003
- Red Hat Enterprise Linux Advanced Server 3 and 4
- Solaris 9 and 10
The connector can be used for the following main purposes:
- Read users, groups, group memberships, and content (incl. ACLs) stored in the Vignette repository.
- Search content stored in the Vignette repository
- Repository Full scan: the whole content and all users, groups and group memberships can be extracted and processed by the application using the connector.
- Incremental updates: registered applications receive a notification on available content, user and permission updates. The notification frequency is configurable.
The connector maps any Vignette ObjectType, including custom types, to the JCR API according to the following rules:
- The NodeType name is the Vignette ObjectType name qualified by a default namespace. Example: “Article” maps to vgn:article.
- The JCR properties are Vignette’s attribute definitions qualified by a default namespace. Example: “title” maps to vgn:title.
- Any autogenerated attributes are mapped as JCR autocreated and are mandatory.
- If the ObjectType has any relations, they are mapped as children of the JCR nodes including the name and type of relation.
In addition to the mapping rules, a JCR connector includes the following add-ons:
- All mapped NodeTypes are based on the NodeType vgn:record, which defines the jcr:creationDate and jcr:modificationDate properties. These properties are mapped to Vignette’s creationTime and lastModTime meta-data attributes respectively. The vgn:record NodeType extends JCR nt:hierarchyItem and can be used in nt:file/folder structures.
- StaticFiles are converted into a NodeType that inherits the JCR nt:file. The actual binary file content is mapped to a child of the node, such as nt:file/jcr:content/jcr:data. The child NodeType vgn:ContentNode is based on nt:resources. The file’s binary content is accessible as a JCR value of jcr:data attribute. The filename and extension determines the JCR:mimeType attribute.
- Each NodeType includes the following additional properties:
- vgn:sites, a multivalued string property, contains a value for each site where the node is published. The value is the name of the site.
- vgn:channels, a multivalued string property, contains a value for each channel to which a node belongs to. The value is the name of the channel.
- vgn:status. If Vignette’s ManagedObject contains status information, a property called vgn:status is also added. vgn:status is a string value that reflects the approved status of the object.
The connector requires the following:
- Day Content Repository Extreme 1.2 (CRX 1.2) or later
- Vignette API jar files (vgn-appsvcs-cda.jar and thirdparty-combined.jar)
- Vignette V7 connector 1.2
Note: <crx install> referenced in the documentation is the home of the CRX Installation. The home can be selected during the CRX Installation.
To install the connector, you need to unpack the CRX Web archive, so you can access its contents individually. Proceed as follows:
- Go to the /server/webapps directory
- Rename the archive file crx.war to crx_ori.war
- Create a new folder named crx.war
- Extract the archive crx_ori.war to the folder crx.war
The remote access extension webapp crx2vignette.war does not contain the Vignette libraries it needs to access the Vignette V7 repository. You need to make the vgn-appsvcs-cda.jar and thirdparty-combined.jar files available to the webapp either via the shared classpath of the servlet container or by embedding the jar files into the WEB-INF/lib folder of the webapp. The latter is described in steps 1-3 of the following instructions.
- Unpack crx2vignette.war (this file is contained in crx2vignette-1.2.zip, see 3.3.2) to a temporary directory preserving the directory structure of the files contained in crx2vignette.war.
- Copy the following files to /WEB-INF/lib of the extracted file structure: vgn-appsvcs-cda.jar and thirdparty-combined.jar. Please take these files from your Vignette V7 installation.
- Package the modified file structure into a new crx2vignette.war file.
- Sign in to the Vignette Runtime Services Administration Console
- Select “Deployments / Web Application Modules” within the VgnCluster. The crx2vignette.war must be deployed on the VgnCluster and not on VgnAdminServer.
- Select “Deploy a new Web Application Module...”
- Upload and install the modified crx2vignette.war file.
1. Extract the file crx2vignette-1.2.zip to a temporary directory. The distribution contains the following files and folders:
- README.txt: This file contains the latest information on the Vignette V7 connector.
- LICENSE.txt: The license files provide you with the terms and conditions of the use of this product. The same information is also available in the online documentation.
- /lib:This folder contains the Vignette V7 connector library and the required remote access extension as well as other libraries that the adapter requires.
- /docs: This folder contains this documentation.
- /etc: This folder contains configuration files for the Vignette V7 connector.
Note:The workspace directory now contains a Vignette folder. When you start CRX, CRX creates the workspace based on the information in the workspace.xml file. The first time you log into the workspace, CRX creates the required workspace files.
In the pre-configured vignette_login.conf file set the synchronization interval parameter defining how often the connector gets updates on user, group, and group memberships from the Vignette V7 repository.
- sync_interval (in seconds, default is 3’600 seconds)
If you cannot login to the crx.vignette workspace, and there is a log message "Authentication error: <the Vignette username configured in vignette.properties>".
- Verify that the username and password configured in vignette.properties are correct and that you can use them to login normally to the Vignette Administration Console.
- Check that the administration console host and port settings in WEB-INF/web.xml inside the deployed crx2vignette.war are correct.
CRX Content Repository Extreme (r) Connector for Vignette ("the Software"). By installing the Software you agree to the following terms and conditions. This Software is protected by copyright law and international treaties. This Software is licensed (not sold), and its use is subject to a separate license agreement between you and Day or Day's authorized resellers. By installing the Software you confirm to be an authorized user of the software in accordance with such license agreement. The unauthorized use, copying or distribution of this Software may result in severe criminal or civil penalties, and will be prosecuted to the maximum extent allowed by law. Remote Verification. You acknowledge and agree that the Software may contain verification and reporting functionality that allows the remote reporting of your usage of the Software for the purpose of verifying your compliance with these terms and conditions. If remote verification reveals that you are using the Software in violation of these terms and conditions, you agree to cease such unauthorized use and to pay Day's reasonable expenses and a penalty fee associated with such remote verification and your unauthorized use. DAY, the DAY logo, Communique, ContentBus and CRX Content Repository Extreme are registered trademarks and service marks, or are trademarks and service marks, of Day Management AG, Switzerland, in various countries around the world. All other product names and company logos mentioned in the information, documents or other items provided or available herein may be the trademarks of their respective owners.