eroom Enterprise 7.2 ECM Extensions Workflow Integration Guide

Transcription

1 eroom Enterprise 7.2 ECM Extensions Workflow Integration Guide Documentum, Inc., a division of EMC 6801 Koll Center Parkway, Pleasanton, CA (925)

2 COPYRIGHT Copyright Documentum, Inc., a division of EMC 6801 Koll Center Parkway, Pleasanton, CA (925) Trademarks Documentum Documentum RightSite, Documentum Server, Docbasic, Documentum DocPage Server, Now You Know, Documentum WorkSpace, Documentum SmartSpace, Documentum ViewSpace, AutoRender Pro, Docbase, DocInput, Docobject, DocPage Builder, Documentum 4i, Documentum Administrator, Documentum CADLink, Documentum Commerce Server Integrators, Documentum Application Server Integrators, Documentum Content Authentication Services, Documentum Content Personalization Services, Documentum ContentCaster, Documentum Corrective Action Manager, Documentum Desktop Client, Documentum Developer Studio, Documentum DocControl Manager, Documentum DocLoader, Documentum DocViewer, Documentum Dynamic Content Assembler, Documentum econnector for CAD, Documentum econnector for IBM WebSphere (IBM and WebSphere are trademarks of IBM) Documentum econnector for SAP (SAP is a trademark of SAP AG), Documentum econnector, Documentum econnector for BEA Weblogic (BEA is a registered trademark of BEA Systems Inc) Documentum econnector for JDBC, Documentum econnector for ATG Dynamo (ATG and Dynamo are registered trademarks of Art Technology Group), Documentum econnector for Lotus Notes (Lotus Notes is a registered trademark of Lotus Development Corporation) Documentum econtent Server, Documentum Engagement Services, Document Engagement Server, Documentum ftpintegrator, Documentum Intranet Client, Documentum iteam, Documentum Reporting Gateway, Documentum Site Delivery Services, Documentum Web Development Kit, Documentum Web Gear, Documentum WebCache, Documentum Web Publisher, GMPharma, GXPharma, GDPharma, GSPharma, Momentum, Virtual Document Manager (VDM), Documentum Selfrepair, and eroom are trademarks or registered trademarks of Documentum, Inc. in the United States and throughout the world. All other company and product names are used for identification purposes only and may be trademarks of their respective owners. eroom Enterprise 7.2 ECM Extensions Workflow Integration Guide i

3 What are the eroom Enterprise 7.2 ECM Extensions?... 1 Requirements... 1 Installing the ECM Extensions... 1 eroom Server... 2 Webtop Server... 2 Content Server... 2 What the Extensions Do... 3 Workflow... 3 Quickflow... 4 Inbox... 4 Lifecycle... 5 Versions... 5 Troubleshooting... 5 eroom Enterprise 7.2 ECM Extensions Server Workflow Integration Guide 1

4 What are the eroom Enterprise 7.2 ECM Extensions? What are the eroom Enterprise 7.2 ECM Extensions? Requirements The eroom Enterprise 7.2 ECM Extensions enable you to harness the refined collaboration capabilities of Documentum eroom 7 together with the powerful Workflow capabilities of Documentum Content Server. Once you have installed the ECM (Enterprise Content Management) extensions, you can launch Content Server Workflows from within eroom. By doing this, you create an association between eroom items and Workflows. Then when you need to move between a particular context within eroom and a particular Workflow context, or vice versa, you can easily do so. At present, there are six ECM Extensions: Workflow Quickflow Link to Documentum Inbox Lifecycle Versions Virtual Document Manager The ECM Extensions work together or separately to connect eroom in various ways with Content Server Workflows. To install and configure the ECM Extensions, a distinct group of files must be placed in each of three locations: The eroom 7 server The Docbase server The Webtop server In addition, you must use the eroom 7 Extension Manager to configure the extensions once you have placed them in the proper location on the eroom server. eroom requirements for the ECM Extensions are the same as they are for eroom 7.2. In addition, you must have Content Server 5.1 or later and WDK Web Server 5.2 or later to support the Workflows. Installing the ECM Extensions In order to install the ECM Extensions, you must place and configure files on each of the three main servers involved (eroom Server, Webtop Server, and Documentum Content Server). Accordingly, the ECM Extensions are packaged as a.zip file containing three other.zip files--one for each server. Complete each of the following procedures below to install and configure these files. eroom Enterprise 7.2 ECM Extensions Workflow Integration Guide 1

5 What are the eroom Enterprise 7.2 ECM Extensions? eroom Server Webtop Server Content Server 1. Extract the contents of the eroomserver.zip file into the ~Extensions folder within the same eroom 7 File Server directory that contains facility templates. (For example, c:\program Files\eRoom File Server\~Extensions) 2. Use the ERSAdmin program to configure and deploy the ECM Extensions you extracted in Step 1. For detailed instructions on configuring and deploying Extensions, refer to the Site Administration topic within eroom 7 s online help. 3. In the Options area of the General page of eroom s Site Settings, make sure the Allow XML queries and commands from external applications option is checked. 4. In the Content Server Connection area of the General page of eroom s Site Settings, make sure your Webtop/DAM URL is properly configured. 5. Make sure the accept login credentials setting is enabled in eroom s Site Settings. 1. Extract the contents of the webtopserver.zip file into the...\webapps\webtop directory in your Webtop install path on the Webtop server. (For example, c:\program Files\Apache Tomcat 4.0\webapps\webtop) 2. Make sure that the jar file xercesimpl.jar is in the classpath for your web server. 3. To make Webtop aware of the eroom server, you must edit the following file:.../webapps/webtop/custom/config/com/documentum/eroom/workflow/ eroomitemlocator_component.xml Open the file and locate the following line: <deferoomserverurl> </deferoomserverurl> Edit the line by adding the URL of the eroom server up to, but not including, the eroom virtual root. For example: <deferoomserverurl> 1. Extract the contents of the contentserver.zip file to a temporary directory on the Content Server machine. 2. Open the extracted file with a text editor. 3. Using Interactive DQL, execute the eroom_reference.dql script, which you extracted in Step 1: For Windows: idql32 <docbase_name> -U<Documentum_superuser> -P<superuser_password> -Reroom_reference.dql -E For UNIX: idql <docbase_name> -U<Documentum_superuser> -P<superuser_password> -Reroom_reference.dql -E 2 eroom Enterprise 7.2 ECM Extensions Workflow Integration Guide

6 What the Extensions Do Note: This script creates a sub-type of dm_sysobject named eroom_reference. Consequently, if you are upgrading from a previous version of the ECM Extensions, this step is unecessary. 4. Alternatively, you can use any tool that executes DQL to cpy the CREATE TYPE command from the eroom)reference.dql file and execute it with go, making sure you are logged in as a super user. 5. Using the Webtop client, add a folder named eroom_references to the system cabinet on the content server. This folder will be used to store reference objects. 6. Set up the desired access privileges for this folder. (Generally, world write permission.) What the Extensions Do Each of the ECM extensions opens a different connection between eroom and your Content Server Workflows. These connections are accessed through a series of buttons that are added to erooms when you install the Workflow extensions. Workflow The following sections describe and illustrate the various connections available now that you have installed the Workflow extensions. The Start Workflow button enables you to connect an eroom item with a Workflow. When you click the Start Workflow button, the Webtop Start Workflow screen appears. This screen enables you to choose the Workflow you want to attach the eroom item to. After you have selected a Workflow and its options, you will be prompted to choose an item to attach to the Workflow. The dialog will feature an eroom Items tab from which you can specify the eroom item you want to attach. eroom Enterprise 7.2 ECM Extensions Workflow Integration Guide 3

7 What the Extensions Do Quickflow Quickflows offer a more streamlined approach to Workflow-like functionality. Unlike with Workflows, you must first select a file in eroom before you click the Quickflow button. (Consequently, there is no subsequent screen for choosing an eroom object.) Once you click the Quickflow button, you can rapidly configure a Quickflow by setting a few options on the Quickflow dialog that appears. Inbox In addition to the buttons that are added to the eroom, a tool button that enables you to access your Content Server inbox is added to the eroom s control bar. This tool button opens the Workflow s task screen, which in turn links back to the eroom when an eroom item is part of a task. 4 eroom Enterprise 7.2 ECM Extensions Workflow Integration Guide

8 Troubleshooting Lifecycle The Lifecycle extension enables you to attach an eroom object to (or detach it from) a Lifecycle. You can also Demote or Promote the object within the Lifecycle or suspend the Lifecycle. Versions The Versions extension enables you to connect to the Version Manager and to display major and minor version history of eroom items that are linked to Content Server. Troubleshooting This section contains a brief list of things to double-check if you are having trouble with your extensions. Make sure the extensions are installed correctly. If so, you should see the Content Server Inbox icon in the eroom s control bar. Make sure the eroom Site Settings that enable the Workflow Extensions are set properly. (See the eroom Server section in this document.) Make sure you can launch a Quickflow. If you can, then the Workflow Extensions should be correctly installed and configured. eroom Enterprise 7.2 ECM Extensions Workflow Integration Guide 5

9 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United State and other countries. All other trademarks used herein are the property of their respective owners.