TeamSite_16.3_Admin_Guide_en_rev1.pdf - TeamSite Administration Guide Release 16.3 TM OpenText TeamSite TeamSite Administration Guide Rev October 2017

TeamSite_16.3_Admin_Guide_en_rev1.pdf - TeamSite...

This preview shows page 1 out of 236 pages.

Unformatted text preview: TeamSite Administration Guide Release 16.3 TM OpenText TeamSite TeamSite Administration Guide Rev.: October 2017 This documentation has been created for software version 16.3. It is also valid for subsequent software versions as long as no new document version is shipped with the product or is published at . Open Text Corporation 275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1 Tel: +1-519-888-7111 Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440 Fax: +1-519-888-0677 Support: For more information, visit Copyright © 2017 Open Text. All Rights Reserved. Trademarks owned by Open Text. Disclaimer No Warranties and Limitation of Liability Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication. Administration Guide Table of Contents Part I: Introduction 11 Chapter 1: TeamSite Overview TeamSite Elements Content Stores Branches Workareas Staging Areas Editions User Roles Reviewer Author Editor Administrator Master WorkflowUser WorkflowAdmin Campaign Manager TeamSite Workflow Jobs Tasks TeamSite Architecture Understanding the TeamSite File System NFS Exports Specify VPaths Related Documentation 12 12 12 12 13 13 13 14 15 15 15 15 15 16 16 16 16 17 17 18 19 20 21 22 Chapter 2: Configuration File Overview The iw.cfg File Location of iw.cfg The iw.cfg File Options Additional Configuration Files 23 24 24 25 30 Part II: Administrative Tasks Chapter 3: Configure the TeamSite Server Configure User Interface Functionality Enable and Disable VisualPreview Configure Domain Lists in the Login Screen Configure Email Settings Specify Valid Domains Configure Server Functionality Control Modification Times Modify Extended Attributes Specify the Encoding of the iw.cfg File Configure the Web Daemon Change the Servlet Engine TeamSite (16.3) 32 33 33 33 34 34 35 35 35 36 36 37 37 Page 3 of 236 Administration Guide Set Locking Models Compare Files Submit and Update Logs Autoprivate Feature Working with the Utility Service Run as Non-Root User Run Teamsite Processes as a Non-Root User Authoring Processes Runtime Processes OpenDeploy Processes Run iwauthend as Non-Root User, iwts Start/Stop the iwutild Server Enable the Event Subsystem Verify that the Event Subsystem is Enabled Ensure that the Event Subsystem Servlet is Started Enable DAS Publishing Configure Server Performance Cache Size External Task Impersonation Throughput Monitors Detect Low Disk Space and Inode Count Configure the TeamSite Server Locale Configure An Example Templating Environment Set up the Example Environment Content Template-Related Settings in iw.cfg TeamSite Embedded Failsafe Fetch the Datasource for a Workflow Using HTTPS urlPrefix Chapter 4: Manage the TeamSite Server Verify Server Operation Start and Stop the TeamSite Server Check for Multiple Servers Check Request Handling Verify the Server Mount Locate the Installation Directory Review TeamSite Log Files WFS Log Installation Log Server Log Trace Log Events Log Workflow Log Windows Event Viewer Monitor the Server Load Reconfigure iwwebd to Recognize a New IP Address Configure iwwebd to Generate Media Managment Thumbnails Manage Disk Space TeamSite (16.3) 37 39 39 39 41 45 45 46 49 52 55 55 55 56 57 57 58 58 58 59 59 60 61 61 62 63 63 64 64 65 66 66 66 67 68 68 68 68 68 68 70 70 70 71 72 72 Page 4 of 236 Administration Guide File Locations Enhance File System Performance on the TeamSite Server Monitor Disk Space Usage Delete Editions Metadata Forking Move the Content Store and Removing Old Versions Chapter 5: Work with Branches Overview Control Branch Ownership and Administration Create Branches Integrate Content From Different Branches Manage Branches Work with Branch Properties View Branch Users and Roles Chapter 6: Manage TeamSite Access Access Considerations Working with Permissions Workarea Access Branch and Workarea Security Default Permissions View File Permissions Share TeamSite Assets using Windows Groups Group Usage with Native Mode Active Directory Group Usage for Larger AD Networks Manage Windows Groups for Best Performance Enable the User/Group/Role Disk Cache Disable Group Nesting Enable the ADSI Debug Flag Additional Tools for Debugging Operate System Group Membership Change Group Ownership of Workareas Web Server Group/UID Group Remapping Maintain the GID Authentication Store TeamSite Users The user_databases.xml File Create a Certificate Authority Database in the cert7.db Format (Windows) Synchronize LDAP Users Configure TeamSite to Work Without an Anonymous Bind LDAP Synchronization Impact of Using Non-OS Users in TeamSite User Authentication TeamSite and PAM Configuration File Interaction The Authentication Daemon Domains to Use for Group Authentication TeamSite (16.3) 72 74 75 76 77 77 78 78 79 79 81 81 82 83 85 85 86 92 92 92 93 94 94 95 96 97 97 98 98 98 99 100 100 101 101 102 102 106 107 109 109 110 110 111 112 113 Page 5 of 236 Administration Guide Log Users and Groups Configure Submit Filtering The submit.cfg File Submit Filtering Sequence Sample submit.cfg file Test and Debug Submit Filtering RCS Macro Expansion 113 114 114 116 116 119 120 Chapter 7: Set Up TagUI TagUI Features Using TagUI Rulesets TagUI Form Design Configure TagUI Map to Rulesets Adjust Server Timeout Tag Large Numbers of Files Control the Search Function Revert to MetaData Capture Tagging Create Rulesets Requirements for Designing Rulesets Best Practices for Designing Rulesets Merge Rulesets Dynamic Addition of Select Box Entries Use FormAPI Best Practices for using JavaScript Troubleshooting JavaScript Integrate IDOL Taxonomy Solution Installation Requirements Configure The Collaborative Classifier Create a Ruleset Configure IDOL Eduction Edit the Mapping File Use the IDOL Taxonomy Solution in the User Interface 123 123 124 124 126 126 129 129 129 129 130 137 138 138 140 141 141 141 142 142 142 143 145 146 147 Chapter 8: Configure the TeamSite Web Daemon and Proxy Server About the TeamSite Web Daemon About the Proxy Server Apply Changes to Proxy Configuration Configure TeamSite Web Daemon and Proxy Server Operation Support for a Cloud-Based MediaBin Installation Add Proxy JVM Parameters to jBoss Startup Scripts Resolve Relative and Absolute Paths Document Roots Resolve Fully Qualified URLs Redirect Fully Qualified URLs Configure the Proxy Server to Redirect Fully Qualified URLs Configure your Web browsers to Use the TeamSite Web Daemon Redirect TeamSite Views to Different Areas 148 148 149 150 150 151 151 151 152 154 154 155 155 156 TeamSite (16.3) Page 6 of 236 Administration Guide Using iwproxy_preconnect_remap Using iwproxy_preconnect_redirect Configure TeamSite to Use Different Web Servers Configure External Remappings Using iwproxy_preconnect_remap Using iwproxy_external_remap Host Header Remappings Enable iwproxy Access Control Configure SSI Remapping Configure Proxy Failover Debug Your Proxy Server Configuration Configure webd to Run TeamSite over HTTPS 157 158 158 159 159 159 160 160 161 161 163 163 Chapter 9: Manage Search Overview Index Branches Search Branches Delete Branches Types of Files Being Indexed Search CLTs Search Examples Troubleshooting Files Not Found Password Syntax Using the CustomDate Extended Attribute Deleted Edition Deleted Branches Changes to Content Store IDs Bringing Down Servers Configuration Issues Using CLTs Error Messages 165 165 165 167 167 167 168 169 174 174 175 175 176 176 176 176 177 178 178 Chapter 10: Connectors Overview Optimost Connections Access Reports for a Site Troubleshooting Enable Debugging MediaBin Connections Content Template-Related Configuration Files datacapture.cfg Presentation Template Files MetaData XML Record attribute Metadata Elements Representation of Data Types Dublin Core Metadata Elements Custom Metadata MediaBin Configuration 180 180 180 181 181 182 182 182 185 185 186 187 187 188 188 TeamSite (16.3) Page 7 of 236 Administration Guide Setting Anonymous Access Configuring MediaBin Trusted Client and LDAP Authentication Troubleshooting Running MediaBin Connector 1.1 and 2.0 Toolkits Simultaneously Import from MediaBin Requires Anonymous Access to the Transfer Directory Chapter 11: Back Up TeamSite Integrate with Third-Party Backup Solutions Suggested Strategies for Incremental Backups Appendixes 189 189 189 189 190 191 191 192 194 Appendix A: Migrate SitePublisher Sites to Experience Studio Revert a SitePublisher Migration 195 195 Appendix B: Internationalization Overview Supported Client and Server Platforms Supported Content Limitations and Assumptions Content Stores and Character Encoding About UTF-8 URL Commands with Multibyte Characters Interface with Localized Operating Systems Access the Localized Interface Language of the VisualPreview Tool Bar Run TeamSite CLTs in DOS Console Mode Specify File Encoding of Text Files Text Editor Encodings Behavior of Netscape Navigator Configure Netscape for Multibyte Characters Usage Scenarios 197 197 198 198 198 199 199 199 199 200 200 201 201 202 202 203 203 Appendix C: Specify Content Encoding regex_map Defined Simple regex_map Example The regex_map Format Rule Syntax Regular Expression Syntax Variables Application Variables Intermediate Variables Interpolation of Variables and Captured Subexpressions Quoting Strategies for Effective regex_maps Internationalization and regex_maps VisualPreview and file_encoding.cfg Source Differencing and Merging and file_encoding.cfg 205 205 206 207 207 207 208 208 208 208 211 212 214 214 214 TeamSite (16.3) Page 8 of 236 Administration Guide Sample file_encoding.cfg 215 Appendix D: Single Sign-On Overview Integrate SiteMinder and TeamSite with an Active Response Prerequisites Overview Integration Procedure Integrate SiteMinder and TeamSite Without an Active Response Prerequisites Overview Integration Procedure Integrate an SSO Product Other than SiteMinder with TeamSite Prerequisites Overview Integration Procedure Troubleshooting Troubleshooting the SiteMinder Web Agent Troubleshooting the Active Response 217 217 218 218 218 219 223 223 223 224 229 229 229 230 232 232 233 Appendix E: Troubleshooting 234 TeamSite (16.3) Page 9 of 236 Administration Guide TeamSite (16.3) Page 10 of 236 Part I: Introduction This section introduces important TeamSite administration concepts. l "TeamSite Overview" on page 12 l "Configuration File Overview" on page 23 TeamSite (16.3) Page 11 of 236 Administration Guide Chapter 1: TeamSite Overview Chapter 1: TeamSite Overview This chapter introduces three major TeamSite concepts and concludes with a description of the TeamSite system architecture. It includes the following topics: l "TeamSite Elements" below l "User Roles" on page 14 l "TeamSite Workflow" on page 16 l "TeamSite Architecture" on page 18 TeamSite Elements The following sections describe some common TeamSite concepts that you should be familiar with before beginning to configure TeamSite. Content Stores The Content Store is a large directory created by the TeamSite installation program that contains TeamSite files and metadata. By default, the Content Store is located in Unix:/iw-store; Windows:C:\iw-store. TeamSite supports as many as eight Content Stores per TeamSite server (the first is created automatically by the installation program, and the others are created as needed by the TeamSite system administrator. Branches TeamSite provides branches for different paths of development for content. Branches can be related to each other (for example, alternate language versions of the same Web site) or they may be completely independent. Typically, each branch contains all the content for a Web site or a major section of it (such as a department), or a collection of related content (such as the program files for a software application or the image and text files for a book). Branches can be indexed and searched. A single branch contains archived copies of its content as editions, a staging area for content integration, and individual workareas where users may develop content without disturbing one another. Branches can also contain subbranches, so that teams may keep alternate paths of development separate from each other. Content can be easily shared and synchronized across branches and subbranches. Users may work on one branch or on several, and the number of branches on a system is not limited. Branches facilitate distributed workflow because they allow separate teams to work independently on different projects. Because all branches are located on the same TeamSite server, it is easy for one team to incorporate the work of another into their project. TeamSite (16.3) Page 12 of 236 Administration Guide Chapter 1: TeamSite Overview Workareas Each workarea contains a virtual copy of all related content, which may be modified in any way without affecting the work of other contributors. Users who have access to a workarea may modify files within that workarea and view their changes within the context of all related content before integrating their work with that of other contributors. Users can lock files in each workarea, eliminating the possibility of conflicting edits. All changes made to files in a workarea are kept completely separate from other workareas and the staging area until the user chooses to submit his changes to the staging area. Within a workarea, users may add, edit, or delete files, or revert to older versions of files without affecting other users. Staging Areas Each branch contains one staging area where contributors incorporate their changes with the work of others. Users submit files from their workareas to the staging area to integrate their work with other contributions, and test the integrity of the resulting content. Because the staging area is an integrated component of the system, conflicts are easily identified and different versions of the same file can be merged, rather than overwritten. Editions Editions are read-only snapshots of a branch, taken at sequential points in its development. Contributors with appropriate permissions can create new editions any time they feel their work is well integrated, or any time they want to create an updated snapshot of all content for reference or deployment to a production server. For Web site content development, each edition is a fully functional version of the Web site, so that users can see the development of the Web site over time and compare it with current work. TeamSite branches contain private workareas, which contain complete virtual copies of the Web site; staging areas, where contributors integrate their work; and editions, which are read-only snapshots of the Web site at various points in its development. Each area contains a virtual copy of the entire Web site. Content is submitted from workareas to the staging area, and the staging area is then published as an edition. Older editions are available for reference. The following figure illustrates the use of TeamSite for Web site development. TeamSite (16.3) Page 13 of 236 Administration Guide Chapter 1: TeamSite Overview User Roles TeamSite ships with out-of-the-box user types, each with specific access permissions and optimized user interfaces. These user types are known as roles. The roles are: l Administrator l Author l Editor l Master l Reviewer l Site Manager l WorkflowUser l WorkflowAdmin l Campaign Manager These default roles are summarized in the following sections. Each installation can create or modify roles to meet the needs of your organization. Note: A user must be a member of the group owning the Project to have the full permissions of the assigned role. TeamSite (16.3) Page 14 of 236 Administration Guide Chapter 1: TeamSite Overview Reviewer Reviewers generally review work done by others. They may have approval authority. They can browse workareas and review files and forms, search for content, and work with tasks. Reviewers usually access TeamSite from the browser-based ContentCenter Professional interface. Author Authors are primary content creators. All work done by Authors goes through an explicit approval step. They can receive assignments from Editors, which are displayed in task lists when Authors log in to TeamSite. Authors usually access TeamSite from the browser-based ContentCenter Professional interface and do not need to be sophisticated computer users. In order to test their work, Authors have full access to the content in their Editors’ workareas, but do not need to concern themselves with the larger structure and functionality of TeamSite. The Author role is appropriate for non-technical users or for more technical contributors who do not need access to extended TeamSite functionality, such as advanced version management features. Editor Editors own workareas. They create and edit content, just as Authors do, but they are primarily responsible for managing the development taking place within their workareas. This includes assigning files to Authors and submitting completed content to the staging area, and it may include creating editions. Editors have access to specialized TeamSite content and workflow management functions. Editors are generally “managerial” users, who primarily supervise the work of Authors, or self-managing “power” users, who need extended TeamSite functionality to manage their own content. Administrator Administrators own branches. They have all the abilities of Editors, but they are primarily responsible for the content and functioning of their branch. Administrators can manage project workflow by creating new workareas for Editors and groups and by creating subbranches of their own branch to explore separate paths of development. They can assign TeamSite users to groups and assign users to roles on the branch. An Administrator is the supervisor of the project being developed on his branch. Master Master users own the entire TeamSite Content Server. They can create new stores and perform all the functions of Editors and Administrators on any branch. They can create or modify roles. The Master user is generally involved in the installation of TeamSite and can reconfigure TeamSite on a systemwide basis. TeamSite (16.3) Page 15 of 236 Administration Guide Chapter 1: TeamSite Overview Users with the Master role have access to the Administration Console within ContentCenter Professional. This allows them to add operating system users to TeamSite, assign groups, create and edit roles, and perform other TeamSite tasks. Most installations only have a few Master users. WorkflowUser By default, all TeamSite users should be able to use workflow models. To achieve this, the workflowModels branch of the iwadmin store is shared for iwEveryone with role as WorkflowUser. This role has the minimum privileges required to instantiate a workflow. WorkflowAdmin The WorkflowAdmin role has privileges to design workflows using Workflow Modeler and upload them to TeamSite. They have privileges to manage, configure, and debug the workflow models. Users who can perform these operations include workflow developers or TeamSite administrators. Campaign Manager The Campaign Manager manages e-mail and social media campaigns and the lists of leads that are used as audiences for the campaigns. TeamSite Workflow A workflow model is a general workflow configuration that can be used repeatedly. Each workflow model describes a process that may include user tasks and a wide variety of automated tasks. Workflow models are configured by the system administrator or by the Client Services organization. The following figure is a diagram of a very simple assign-edit-approve workflow model. Email is sent to the participants at every stage of the process, and some automated tasks are performed at the end. TeamSite (16.3) Page 16 of 236 Administration Guide Chapter 1: TeamSite Overview Jobs A job is a set...
View Full Document

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture