This topic covers the procedure steps of installing TeamSite version 6.7.1 SP1. TeamSite (TS) can be installed on a server that supports either OS platform:
MS Windows
Solaris
Linux
However this blog will only cover installing TS on a Windows environment.
Installation Path
The required steps in order for TS installation are as follows below. Basically there are 5 package installation software that needs to be installed:
Install TeamSite base server release v.6.7.1
Install TeamSite search server release
Install TeamSite v6.7.1 Service Pack 1
Install TeamSite search server Service Pack 1
Install Workflow Modeler
Pre-requistie
Get appropriate license keys for TeamSite from support.interwoven.com.au
Download all the five TeamSite package installation software from Interwoven support
Temporary turn off all services runnign Anti-Virus software prior to installing TeamSite. Then enable the virus software after TeamSite installation is complete.
IIS v6 has been installed on the server machine that will run TeamSite
Install SQL 2000/2005 on the TeamSite server. Create a database (named tsevents). Create a database admin account (sa account for SQL)
Install Java RunTime (minimum v1.5 or later)
.NET Framework 2 has been installed (if the server is hosting .NET applications)
Install SQL 2000/2005 (If TS server is using SQL 2005 then prefer to install JBDC 2000 driver first as TeamSite Installation only picks up 2000 JBDC driver. Then later install 2005 driver) JDBC driver has been installed in the TeamSite server
Appropriate users and groups has been added to Active Directory
Domain name has been created and shared in TeamSite server box
Installing TeamSite
1. Login into the server with system domain administrator. Then follow and read the instruction here on how to install TemSite 6.7.1 Service Pack 1. Accept all default value in the installation instructions except for the directory lcoation of TS should be at c:\interwoven\teamsite folder. You should also obtain the following license key from Interwoven support before you start installing. There will be errors found if user skip getting a license key and install TS.
TeamSite license key (TS.lic file)
ContentServices SOAP server license key
ReportCenter license key (optional)
Provide Interwoven support with the following information about the server:
Hostname
Domain
Product version
Platform OS
Number of CPUs
2. After installing Teamsite base release v6.7.1 with the license key, reboot the server and during the loading of window, Interwoven TS dialog bow will pop up with status message saying to wait awhile while TS configures IIS and adds a default TS user and group to AD.
3. After rebooting the server for the first time after installing TS, ensure that virtual Y drive has been created and ensure that the following 6 TS services are running (Control panel->administrative tool->services):
Interwoven Event Subsystem
Interwoven Proxy
Interwoven servlet Engine
Interwoven TeamSite
Interwoven TeamSite Utility Daemon
Interwoven Web Daemon
If any of the TS service is not running and/or Y drive has not been created, type "iwreset -a" in command prompt.
5. Ensure that TS login screen is loaded in the internet browser by going to URL: http://localhost/iw-cc/command/iw.ui and that you are able to log into TS using the administrator's windows authnetication account.
6. After succesfully logging into TS, add all the approiate AD users into TS, including IIS anonymous user TSIMP_. Add all AD users to TeamSite Preview AD group. Note: The list of all available users displayed in TeamSite are retreieve from Active Directory or LDAP. So if you want to add a user in TeamSite but is not displayed in TS, you need to add that new user in AD/LDAP first. Always reset TS or reboot the server everytime you have added a new AD/LDAP user so that TS will be updated with the list of new users from AD/LDAP.
7. Add a new TS group. Add existing members (created from step 6) and managers to the TS group.
8. Add appropriate roles to the TS group (created from step 7) to the selected branch.
Note: Before installing TeamSite Search server base release v2, you must ensure that all TS services is running, y drive created and can log into TS.
9. Install TS search server base release v2.0 See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/02_installing19.html for instructions and install it at c:\interwoven\search folder. Then reboot server after installation is complete.
10. Install Teamsite v6.7.1 SP 1 and reboot the server after installation.
11. Install TS search server SP 1 and reboot the server after installation.
This topic covers the procedure steps of installing TeamSite version 6.7.1 SP1. TeamSite (TS) can be installed on a server that supports either OS platform:
MS Windows
Solaris
Linux
However this blog will only cover installing TS on a Windows environment.
Installation Path
The required steps in order for TS installation are as follows below. Basically there are 5 package installation software that needs to be installed:
Install TeamSite base server release v.6.7.1
Install TeamSite search server release
Install TeamSite v6.7.1 Service Pack 1
Install TeamSite search server Service Pack 1
Install Workflow Modeler
Pre-requistie
Get appropriate license keys for TeamSite from support.interwoven.com.au
Download all the five TeamSite package installation software from Interwoven support
Temporary turn off all services runnign Anti-Virus software prior to installing TeamSite. Then enable the virus software after TeamSite installation is complete.
IIS v6 has been installed on the server machine that will run TeamSite
Install SQL 2000/2005 on the TeamSite server. Create a database (named tsevents). Create a database admin account (sa account for SQL)
Install Java RunTime (minimum v1.5 or later)
.NET Framework 2 has been installed (if the server is hosting .NET applications)
Install SQL 2000/2005 (If TS server is using SQL 2005 then prefer to install JBDC 2000 driver first as TeamSite Installation only picks up 2000 JBDC driver. Then later install 2005 driver) JDBC driver has been installed in the TeamSite server
Appropriate users and groups has been added to Active Directory
Domain name has been created and shared in TeamSite server box
Installing TeamSite
1. Login into the server with system domain administrator. Then follow and read the instruction here on how to install TemSite 6.7.1 Service Pack 1. Accept all default value in the installation instructions except for the directory lcoation of TS should be at c:\interwoven\teamsite folder. You should also obtain the following license key from Interwoven support before you start installing. There will be errors found if user skip getting a license key and install TS.
TeamSite license key (TS.lic file)
ContentServices SOAP server license key
ReportCenter license key (optional)
Provide Interwoven support with the following information about the server:
Hostname
Domain
Product version
Platform OS
Number of CPUs
2. After installing Teamsite base release v6.7.1 with the license key, reboot the server and during the loading of window, Interwoven TS dialog bow will pop up with status message saying to wait awhile while TS configures IIS and adds a default TS user and group to AD.
3. After rebooting the server for the first time after installing TS, ensure that virtual Y drive has been created and ensure that the following 6 TS services are running (Control panel->administrative tool->services):
Interwoven Event Subsystem
Interwoven Proxy
Interwoven servlet Engine
Interwoven TeamSite
Interwoven TeamSite Utility Daemon
Interwoven Web Daemon
If any of the TS service is not running and/or Y drive has not been created, type "iwreset -a" in command prompt.
5. Ensure that TS login screen is loaded in the internet browser by going to URL: http://localhost/iw-cc/command/iw.ui and that you are able to log into TS using the administrator's windows authnetication account.
6. After succesfully logging into TS, add all the approiate AD users into TS, including IIS anonymous user TSIMP_. Add all AD users to TeamSite Preview AD group. Note: The list of all available users displayed in TeamSite are retreieve from Active Directory or LDAP. So if you want to add a user in TeamSite but is not displayed in TS, you need to add that new user in AD/LDAP first. Always reset TS or reboot the server everytime you have added a new AD/LDAP user so that TS will be updated with the list of new users from AD/LDAP.
7. Add a new TS group. Add existing members (created from step 6) and managers to the TS group.
8. Add appropriate roles to the TS group (created from step 7) to the selected branch.
Note: Before installing TeamSite Search server base release v2, you must ensure that all TS services is running, y drive created and can log into TS.
9. Install TS search server base release v2.0 See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/02_installing19.html for instructions and install it at c:\interwoven\search folder. Then reboot server after installation is complete.
10. Install Teamsite v6.7.1 SP 1 and reboot the server after installation.
11. Install TS search server SP 1 and reboot the server after installation.
11. Install TS search server SP 1 and reboot the server after installation.
12. Install Redirector module for IIS - See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/03_webServer7.html#wp1170385
13. Redirect NSAPI HTTPS request. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/03_webServer11.html#wp718293
14. Install lcoal file manager. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/04_clients3.html#wp1126238
15. Mount the TS server file system (i.e. Y drive on the server) as a shared network drive. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/04_clients6.html#wp1123940
16. Create the branches and the workarea for each branch. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/05_content6.html#wp482158
17. Give TS group and users access permission to the newly created branches.
18. Publish all files located at /iwadmin/main/workflowModels/WORKAREA/iw-wa/Internal to staging.
19. Configure event sub-system to use SQL 2005 JDBC driver. See:
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=56631
http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/config.server21.html
Note the following: i) Download SQL JDBC driver version 1.1. (version 1.2 does NOT work well) ii) Firstly create a new database and a SQL Server authenication user that is reflected in the jmsconfignew.xml file. iii)Run the create_sqlserver.sql script for the new database created in step ii.
20. Configure SQL 2005 to allow remote connection by the SQL JDBC driver. See: http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277 . Note the following:
Change the port number of url element tag to 1434 in jmsconfignew.xml file. Then change the TCP/IP port number to 1434 (defaulted to 1433) for "Protocols for MSSQLSERVER" in SQL Server Configuration Manager, because SQL "Native Client Protocols" is already using port 1433. Test it by restarting the "Interwoven Event Subsystem" service and checking to see that there is no error in the log file iw-home\local\logs\eventsubd_err.log.
Change the Authentication Mode of the SQL server from "Windows Authentication Mode (Windows Authentication)" to "Mixed Mode (Windows Authentication and SQL Server Authentication)". Restart SQL Server service.
Start the following services: SQL server, agent, browser, Full text and VSS writer.
21. Configure the iw.cfg file and edit it as required for each section. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/iw.cfg4.html for more detail instructions on how to do it.
22. Implement a backup strategy plan for TeamSite. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/backups.html for more details.
23. Configure the Search server - See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/search.html#wp999146 for more details.
24. Install Workflow Modeller
Online e-Book:
TeamSite Installation Guide
HTML version
PDF version
TeamSite Administration Guide:
HTML version
PDF version
Posted by David at 11:42 PM 2 comments:
Labels: Administration
16 October 2008
TeamSite Skill Set
To learn the skills of TeamSite CMS, knowledge of with experience in usingTeamSite must be obtained. These knowledges are categories
and rated into four skill levels below. So for example, basic low skill levels for beginners will require basic fundamental knowledge of TeamSite. The higher the skill levels, the more tecnhnical knowledge of TeamSite is required to understand.
The skill levels are as follows:
Level 0: The Developer has no knowledge of or experience in the skill/knowledge area whatsoever.
Level 1: The Developer has a conceptual knowledge of the skill/knowledge area and has some limited commercial experience or may have experimented with the related concepts and/or supporting technologies in a non-commercial sense. The developer cannot apply this skill/knowledge area without direct supervision.
Level 2: The Developer is proficient in the skill/knowledge area with recent commercial experience in its application, can apply the skill/knowledge without direct supervision, but has insufficient experience/knowledge
to provide direction to others in the given area.
Level 3: The Developer can be considered an expert in the skill/knowledge area with considerable recent commercial experience in its application, with experience providing mentoring/guidance to others. The Developer has a detailed and broad understanding of the skill/knowledge area.
Note that each level described above subsumes all levels below it. Thus, in order for a TeamSite Developer to rate at Level 3, he or she must meet the criteria for Levels 1, 2 and 3.
The following area of TeamSite knowledge a TeamSite Developer need to obtain are broken down into each levels below:
Level 0
Introduction to Content Management System (CMS)
Can describe the definition of TeamSite
Can describe the features of TeamSite
Can describe the definition of CMS
Can describe the purpose of CMS
Can describe the content development life cycle
Cam describe the definition of an asset
Introduction to TeamSite Concept
Can define TeamSite server architecture
Can define TeamSite terminology like for example: i)
Content stores ii) Branches ii)Workareas iv) Edition and Versionin v)Can describe the definition and what are the roles in TeamSite vi)Metadata vii)Can log in to a TeamSite server
Can describe and demonstrate and use the features in each version of ContentCenter User Interface
Level 1
Editing files
Can do simple and advance search for assets
Can describe and use TeamSite VisualPrevew tool
Can describe and use Local File Manager to edit files
Can describe and perform basic file operations like copy, rename, delete, create, move/rename, import/export and modifying properties of a file
Can view and set metadata
Can describe and demonstrate checking in/out a file and able to perform merges
Introduction to Workflows
Can describe the workflow terminology use in TeamSite, like for example understand the following:
Workflow
Job specification
Workflow Moder
Workflow template
Task
Activation
Transition
Links
Understand the difference between serial and parallel task
Workflow events
Introduction to Forms Publisher
Can describe the forms publisher terminology use in TeamSite, like for example understand the following:
Data Capture Templates (DCTs) / Data Capture Forms
Data Content Records (DCRs)
Presentation Template (PTs)
Level 2
Workflow Development
Can describe and demonstrate how to configure and set up out of the box workflows templates and workflow models
Can describe and demonstrate how to design, implement and deploy a workflow using the Workflow Modeler Tool
Can describe and demonstrate how to design, implement and deploy a customise workflow template using XML and Perl script
Form Publisher Development
Can describe and demonstrate how to develop Data Catpure Forms
Can describe and demonstrate how to develop Presentation Templates
Can describe and demonstrate how to use APIs and Command Line with Data Capture Forms
OpenDeploy
Can describe and demonstrate how to configure Open Deploy tool to deploy files to production server
Level 3
Advanced Workflow and Form Publisher Development
Can describe and demonstrate executing external programs
Can describe and demonstrate creating custom data source
Can describe and demonstrate using external database with Data Catpure Forms
TeamSite Administration
Can describe and install or upgrade TeamSite CMS, TeamSite Search, MetaTagger and Open Deploy
Can describe and demonstrate the process of configuring and reindexing TeamSite Search
Can demonstrate the maintenance process of creating, deleting, updating users, groups and roles in TeamSite
Can describe and demonstrate the process of backing and restoring content store
Can describe and demonstrate diagnosing error message with log files
Can configure file virtualisation in TeamSite
Posted by David at 1:21 AM 1 comment:
Labels: TeamSite Basic
09 April 2008
Part 4 - Installing TeamSite Front-Office
Overview
TeamSite Front-Office (FO) is a interface tool that allow users access to their workarea & TS functionality within Windows explorer or Microsoft Office applications (e.g. MS Word) . FO consists of 2 components:
TeamSite Front-Office Server: Works with your TeamSite server to provide a framework for contributing content from development applications directly to TeamSite.
TeamSite Front-Office Client: A client-side application that enables content contributors to access TeamSite features directly from their development applications. This component includes the application plug-ins, the TeamSite Briefcase, and the TeamSite Front-Office Configuration Wizard.
Both of these 2 components will need to be installed individually, i.e. FO server is to be installed on the server that runs and host TS. The other is to be installed on the client's machine.
Installing & Configuring Front Office Server
The instruction below will be installign the latest version of FO version 5.6.6 at the time of writing this blog.
Before you install FO server, ensure that all workarea branches and users with their roles has been added into TeamSite and that the users/group has been appropriate permission to access the workarea.
Before you install the FO Windows server, you must have local Administrator
privileges because the installation process needs to start and stop the iwwebd
service.
Download the FO server and client software from Interwoven support website. TFO_server566Buildxxx.exe & FTO_client566Buildxxx.exe
Install Front -Office server (v5.6.6) on the server that had TeamSite install, by running TFO_server566Buildxxx.exe. Installation path shall be c:\interwoven\TeamSite Front-Office\ folder
Configure users and workarea in iw-home\conf\iwwa.cfg file to give FO user(s)/group access to a workarea.
Configure iw-home\etc\iw.cfg file under "[FrontOffice]" section.
Configure iw-home\local\config\wft\available_templates.cfg file to add out of the box FO workflows (see availiable_templates.cfg.tfo.example) if submit operations from FO triggers a worflow, i.e. iw.cfg had "wf_submit=yes"
Configure index_template.htx if FO auto-index is enabled in iw.cfg. Then copy the index_template.htx file to each directory within a workarea that you want to index.
Reset Teamsite server with "iwreset -a" command in DOS prompt.
Installing and configuring Front-Office Client
Run FTO_client566Buildxx.exe software on each client's machine that will be using FO.
Follow the instruction on the setup screen.
Further reading
1. Front-Office Admin Guide (PDF version)
Posted by David at 5:46 PM No comments:
Labels: Administration
10 March 2008
TeamSite Roles
A role is a set of allowed permission (e.g. copy, delete, create, etc) that is assigned to each user. Teamsite has 5 "out of the box" default rows, i.e.
Administrator
Master
Editor
Author
Reviewer
Administrator
Content development managers or team leaders. Owners of a branch but not Teamsite admin.
Responsible for managing a project that is stored in a branch by creating new workareas for Editors and groups and by creating subbranches of their own branch to explore separate paths of development.
Capbilities of an author, editor and reviewer.
Editor
Roles include: submitting completed work to staging, assign work to authors, edit and create files
Approve/rejects work and create new versions by sbubmitting files, merging and reverting.
Purose: Editors are generally "deveoper” users, who primarily supervise the work of Authors, or self-managing “power users", who need extended TeamSite functionality to manage their own content.
Author
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 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.
Purpose: 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.
Reviewer
Review content changes and either reject or apporve changes.
Browse workareas and review files and forms, search for content, and work with tasks.
Purpose:Reviewer role is a typical manager who's role is to review and check other people's work.
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 system-wide basis.
Users with the Master role have access to the Administration tab 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.
Posted by David at 5:44 AM No comments:
Labels: TeamSite Basic
17 April 2008
TeamSite Upgrades
TeamSite Upgrades Overiew
The overall plan for TeamSite (TS) upgrades are as follows:
Day 1
Perform back up procedures
Perform prerequisite requirements
Upgrade TeamSite and OpenDeploy (OD) with latest patch for TS and OD
Apply new licenses
Day 2
Upgrade TeamSite Search
Configure TeamSite Search
Fix any upgrade issues
Re-run toolkit.ipl for any UI customization
Day 3
Check accounts and permissions
Check basic functionalities works in the new upgrade of TS
Perform system testing
Test form publishing (DCT, DCR and PTs)
Test workflows
Test OpenDeploy and Data Deploy
Test View->My local files
Fix any issues found in testing
Day 4
Reserve day for fixing any upgrade issues
Bug upgrade report for TS v6.7.1 with SP1
There is a bug report with using VisualFormat editor in TS v6.7.1 Service Pack 1. When a user previews a Data Capture Form that has a text area field using Visual editor, an error pop up page will appear. Use TinyMce instead of using VF as a work around solution.
Latest patch installer for TS v6.7.1 SP1 has glitches with previewing a Presentation Template on the TS server that runs with a Semantic Anti-virus. Skip the step for installing the latest TS patch.
Prerequisite
Back up the entire hard drive of where TS server and Search server was installed (e.g. if TS was installed at c:\interwoven, then backup the entire c drive).
Back up the entire iw-store. If iw-store was stored in a separate partition drive, then back up that entire drive.
Get Administrator login account details from the client.
Get Interwoven support login account from the client.
Notify TS users of outage.
Disable all antivirus software/services temporary on the TS and search server (if any), particularly if server has a Semantic virus running, as it will cause problem with new TS installations or upgrades (See knowledge article xx)
Check and confirm what current version of TeamSite is installed on all the server boxes that will be upgraded. This is done either by:
Control panel->add/remove program; or
Check iw-home\iwinstall\iwov-inventory.xml file
Download the relevant TS installation package software from Interwoven support website.
Upgrade instructions
The existing TS.lic license key used for TS v6.5 file would still be valid and useable after the upgrade. So there is no need to generate a new TS license key.
The upgrade path for various TS version on Windows OS is as follows whether the upgrade was on the same or on a different server box:
TS v6.5 upgrade path
Upgrade from v6.5 to v6.5 SP 2 (if haven’t done so)
Upgrade from v6.5 SP2 to v6.7.1
Upgrade from v6.7.1 to v6.7.1 SP1
Install only latest patch for v6.7.1 SP1
TS search v6.5 upgrade path
Upgrade from Upgrade from v6.5 to v6.5 SP 2 (if haven’t done so)
Upgrade from v6.5 SP2 to v6.7.1
Upgrade from v6.7.1 to v6.7.1 SP1
OD upgrade path
Install OD Base Server v6.1.1
Install OD Admin Server v6.1.1
Apply latest patch to OD server
Install OD receiver v6.1.1
Apply latest patch to OD receiver
*Note: OD v6.1.1 is more stable to install than v6.2
TeamSite Upgrade steps
1. Download the following installer from Interwoven support site:
TS v6.7.1 installer
TS search v6.7.1 installer
TS v6.7.1 SP1 installer
TS search v6.7.1 installer
Patch update for v6.7.1 SP1
2. Login as Administrator on the TeamSite server machine
3. Backup all configuration files (*.cfg and xml files)
4. Manually stop all TS services and set them to manual on start up
5. Confirm step 4 by going to DOS prompt and type “netstart amore” and look for Interwoven port number
6. Manually stop all IIS
7. Install TS v6.7.1
Select “mssql” checkbox and select the SQL JDBC driver file (*.jar) from iw-home\TeamSite\eventsubsystem\lib folder
Select “No” for don’t overwrite existing jmsconfignew.xml file
8. Reboot server
9. Log into TeamSite via the internet browser and make sure that you can successfully login in
10. Run iwaccessmigrate with –m & -bg –n parameter
11. Run “iwreset –a”
12. Login into TS to ensure that TS is running after performing step 10
13. Manually stop all the TS services
14. Install TS v6.7.1 SP 1
15. Install the latest patch
Manually stop all TS services
Run the patch installer
16. Reboot server and login to TS to ensure that it is running
17. Check that event subsystem service is running
18. Decide whether the client will be using either TinyMCE or VisualFormat editor for published form.
If using VisualFormat (VF) editor, there is a required additional step to install client visual format on the entire client’s machine that will be using published forms. Location of visualformatclient.exe installer is found at C:\Interwoven\TeamSite\httpd\iw\ewebeditpro20\clientinstall folder. You can customize the VisualFormat toolbar by editing the visualformatconfig.xml file at iw-home\httpd\iw\ folder. (for more information read Form Publisher Developer Guide 6.7.1 release PDF doc)
If using TinyMCE, the advantage is that it is already installed with TS because it’s a Java app. However VF is more powerful than TinyMCE. The toolbar can be customized by editing custom_config.js
19. Run script (toolkit.ipl) to migrate any customize UI (if there are any UI customization)
Note:
Read the installation log file at c:\iwinstall\log folder for any unsuccessful installation
Read TS server log file iwtrace.log at iw-home\teamsite\local\logs folder
Read iwutid_cmdout.log file for any PT error message provide iwutild.cfg file debug mode enabled
TS search server upgrade steps
Note: If the search v6.5 was installed on a separate server box, then upgrading the TS server can be done independently without needing to wait for TS upgrades. So to save time TS Search upgrades can be simultaneously run in parallel with TS upgrade.
Run TS search v6.7.1 installer on the search server box and install it at c:\interwoven\search folder
Locate and enter the TS server host. Ensure that you can firstly ping the TS server host name to confirm that both search server and TS server box can communicate and ping each other
Locate the shared file system. Usually at iw-home\new folder (create a new folder)
Check that the search service are running
Install the search v6.7.1 SP 1
* Manually stop the search service
* Run the installer
Reboot the server
Check that all search services (i.e. Interwoven TS Search & Index) are both running
Configure the search
* Edit iw-home\cssdk\cssdk.cfg file: Uncomment
# search.server.host: localhost
# search.server.port: 6720
# search.server.maxConnectionLimit: 10
* Edit iwseach-home\etc\branch.cfg file and add the branches that you want to index
* Restart search and index services (Stop in order search and index. Start index and then search service)
* Run CTL:
iwndxlistbr - Display the list of branches that are index
iwndxrefreshbr -b /default/brachname…
iwndxrefreshbr –I /default/branchname.. (Incremental update on real time)
OD upgrades steps
Upgrade the following OD v6.1.1 in this order below.
OD base server
OD admin server
OD receiver server
1. Get a OD license key
Go to DOS command
Run java -cp od-home/lib/odng.jar com.interwoven.license.LicInfo
-f output-file -p OD
Login the Interwoven support site and go to the OD generate license key webpage
Enter the server information generated into the form and submit it
2. Back up a copy of all files from iw-ODhome\config and etc folder.
3. Download v6.1.1 of OD base, admin server and OD receiver installer from Interwoven support site.
4. Stop all previous version of OD services
5. Run the OD base installer. Install it at c:\interwoven\ folder
6. Choose “upgrade” select box from the installation dialog screen
7. Follow the installation instruction on the screen to install it
8. Check the email that will receive the OD license key file
9. Copy OD.lic to iw-ODhome\etc folder
10. Reboot server
11. Check that OD base service is running (i.e. 62 services). If not, then restart it and set to automatic startup
12. Run the OD admin installer on the same server box that had OD base installed in step 5 and follow its instructions
13. Reboot the server
14. Ensure that OD admin server is running
15. Apply latest patch for OD server. Read the README.txt for further instructions on installing the patch. Basically the instruction will instruct you to:
* Stop all OD services
* Run the patch installer
* Update the registry
16. Reboot the server
17. Check that all OD services are running. If not then set OD services to automatic and start the OD Interwoven services (i.e. AccessService, UI admin and 62 services)
18. Run the OD receiver installer on the other receiver server box
19. Choose “upgrade” option box from the installation dialog box
20. Apply latest patch to OD receiver
21. Get OD receiver license key
Post installation
Enable the Symantec antivirus is back up and running after the whole TS installation package have been installed. Set the antivirus services back to automatic start up.
Posted by David at 9:24 AM 2 comments:
Labels: Administration
29 April 2008
Configuring .NET ASPX File Virtualization for TeamSite
The following configurations are necessary to successfully virtualize content from aspx files on a TeamSite Server where the .NET Framework is also installed on the same server.
Prerequisite
Add the ASPNET user to the "TeamSite Web Preview" Group.
Ensure that .NET framework version 2 is already installed in the same server box that runs TeamSite.
Details
If you are using Windows 2003 the following must also be done (until Bug 57146 has been fixed):
If IIS was installed before you installed TeamSite then you need to delete the default website. Rename the current default website (e.g. “default website bkup”) and click the “Stop” button for the backup default website to stop IIS from running. Then create a new one (also name it “Default Web Site”), using port 81, set path to c:\inetpub\wwwroot and configure it for anonymous access using the IIS IUSR_ user. Click the “Start” button on the new created default website.
Go to Default Web Site properties->ASP.NET tab and check the the .NET version. If there are two version of the .NET framework in the selected drop down box, select version 2.0.xxxx
Go to Default Web Site and Add the SSI ISAPI filter as follows
Right click Default Web Site > Properties > ISAPI Filters > Add, give a filter name like "iwrewrite" and point to \lib\iwproxy_isapi.dll
Within the IIS Management console, under “default website” create a new virtual directory called "iw-mount" which points to the Y:\ drive directory. Anonymous access to this directory should be the TSIMP_ user.
For the root directory (iw-mount), click the “Configuration” button and check the configuration of the defined application to ensure that at least the extensions ".aspx" points to the version 2 .NET framework of aspnet_isapi.dll. Further extensions pointing to this are asax, ascx, ashx, asmx & axd.
Check in the Web Service Extensions that Active Server Pages and ASP.NET are enabled.
Do step A to C **
Set full permission to everyone on the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files folder
Restart IIS and run “iwreset –a”
You should now be able to run a simple ASPX. (just take a simple HTML page and rename it .asp/.aspx.
Log into TeamSite and view a ASPX page.
If you receive and error like "Access denied to 'Y:\default\main\WORKAREA\test, Failed to start monitoring file changes" then you need to check that all necessary parts of ASP.Net have the correct permissions as per Microsoft Knowledgebase articles 317955 & 316721. Interwoven KB article 53298 may also help to identify the problem.
If all the steps are successful, then delete the old default web site that was renamed in step 1 (optional).
The "C:\Inetpub\wwwroot\aspnet_client" directory contains JavaScript files used by .NET, and is automatically installed with the framework.
To enable the virtual system to locate this directory you may need to add a virtual directory at the root of the Workarea:
From within the IIS console, navigate to the Workarea (i.e. "\iw-mount")
Right-click on the Workarea; Select New > Virtual DirectoryEnter "aspnet_client" as the Alias
Enter "C:\Inetpub\wwwroot\aspnet_client" for the Directory
Use the default permissions
* *Ref:
A. From within the IIS console, navigate to the Workarea (e.g. "\iw-mount\default\main\uam\WORKAREA\load")
B. Right-click on the Workarea and click on "Properties", Under "Application Settings" click on "Create" button.
C. Restart IIS.
Further reading:
See knowledge article # 49749
Posted by David at 8:39 PM No comments:
Labels: Administration
17 March 2008
Part 2.2 - Configuring availiable_templates.cfg
The available_templates.cfg file is an XML configuration file that lists all of the workflow templates that are available for use on the TeamSite server. For each workflow, this file indicates the name of workflow, the location of the workflow template file, and the conditions under which the workflow is available.
By default, the available_templates.cfg file is located in:
C:\Program Files\Interwoven\TeamSite\local\config\wft (Windows)
/Interwoven/TeamSite/local/config/wft (UNIX)
Note: If available_templates.cfg is edited and contains non-ASCII text, it must be saved in UTF-8 encoding.
The available_templates element is the container element for the file. This element contains the following attribute:
require_workarea — specify whether (true) or not (false) workflow templates selection screen will include a branch/workarea chooser if workarea context is not present. Most of the out of the box workflow template examples require this to be enabled (require_workarea="true") to work properly. Default value is false.
Within the available_templates element is the template_file element:
<available_templates require_workarea="true">
<template_file name="Author Submit Workflow"
path="solutions/configurable_author_submit.wft">
...
</template_file>
</available_templates>
The template_file element has the following attributes:
name — specify the title of the workflow, for example:
name="Author Submit Workflow"
active — indicate whether (yes) or not (no) the workflow template is enabled. Default value is yes.
path — specify the path where the template file resides. Template files must reside in one of the following locations:
iw‑home/local/config/wft/default
iw‑home/local/config/wft/examples
iw‑home/local/config/wft/solutions
The value you specify is relative to the iw‑home/local/config/wft directory, so if the template file resided in the following absolute path:
iw‑home/local/config/wft/default/author_submit.wft
then you would specify the value:
path="default/author_submit.wft"
Specifying Template Access
You can configure access to each template listed in the available_templates.cfg file by using any combination of the following categories:
Command
Role
Group
User
Branch
The categories can be combined using boolean terms such as AND, OR, and NOT to include and exclude those that meet the inclusion or exclusion criteria you configure. Template access is configured within the allowed element, which is a subelement of template_file:
Within the template_file element is the allowed element, where you can configure user access by matching workflow commands with user roles:
<template_file ...>
<allowed>
...
</allowed>
</template_file>
Command Access
Workflow commands are specified by the command element. The command element specifies the user-activity that starts the corresponding workflow. For example, the following configuration:
<command name="submit"/>
specifies that the associated workflow is started when performing a Submit and that it cannot be invoked by other means.
The valid command values that you can associate with a workflow are:
submit (submitting files)
assign (assign button or menu item)
new_job (new job)
new_TFO_job (new job, in TeamSite FrontOffice)
tt_data (saving FormsPublisher data records)
tt_deletedcr (deleting FormsPublisher data records in ContentCenter Standard only)
all (all possible values from this list)
Note: The tt_data command is valid in ContentCenter Standard and can be configured in ContentCenter Professional; see the User Interface Customization Guide. The tt_deletedcr command is only valid when users are using the ContentCenter Standard interface; in ContentCenter Professional, this command is not valid and data records are treated like any other assets.
Role Access
Access based on TeamSite roles is specified by the role element’s name attribute. For example, the following configuration:
<role name="author"/>
specifies that if the user is logged in as an Author.
Group Access
Access based on user groups is specified by the group element:
<group name="marketing"/>
User Access
Access based on individual user name is specified by the user element:
<user name="jdoe"/>
Branch Access
Access based on TeamSite branch is specified by the branch element:
<branch="/default/products"/>
Combining Access Categories
Pairings of individual or multiple access elements can be included or excluded using the and, or, and not elements within the allowed element. You can use boolean logic to create combinations of categories that can either have access to a specific template, or be excluded from it.
In the following example:
<template_file name="Author Submit" path="default/author_submit.wft">
<allowed>
<and>
<command name="submit"/>
<or>
<role name="author"/>
<role name="editor"/>
<group name="marketing"/>
<and>
<role name="admin"/>
<not>
<user name="jdoe"/>
</not>
</and>
</or>
</and>
</allowed>
</template_file>
the following individuals have access to the Author Submit workflow:
Those who are authorized to perform submit commands.
Those who have the author or editor role.
Those who are members of the marketing group.
Those who have the admin role, with the exception of the user jdoe.
If no access category is specified, it is assumed that category has full access to the workflow template.
Regular Expression Support
You can use regular expressions when specifying branch element constraints within available_templates.cfg to search for a specified pattern and specify what to do when matching patterns are found. Using regular expressions allows a greater level of flexibility when adding items.
For example, if you want only the users in the three administration_1 branches (a1, a2, and a3) to access a workflow template, you can set the following constraint:
<allowed>
<or>
<branch name="/default/main/administrator_1/a1"/>
<branch name="/default/main/administrator_1/a2"/>
<branch name="/default/main/administrator_1/a3"/>
</or>
...
</allowed>
If a new branch called a4 is added to /default/main/administrator_1 you could manually update the available_templates.cfg file to allow access for users in the new branch by adding the branch element to the existing ones:
<branch name="/default/main/administrator_1/a4"/>
Or you could modify the available templates.cfg file to use the following regular expression and, thus, automate the constraints placed on the a4 branch:
<allowed>
<and>
<branch name="/deault/main/administrator_1/.*"/>
</and>
...
</allowed>
This regular expression allows users from any branch under /deault/main/administrator_1 to have access to the template.
Path Separators
When using regular expressions, the path-separators (“\”, “\\”, “/”) are all translated to “/” in both the pattern and the string to match against before attempting the match.
In the following example:
<branch name="foo"/>
any branch path that includes the string foo will be matched. Here the following examples match:
/default/main/food/...
/default/main/barfoo/...
In the next example:
<branch name="^/default/main/foo"/>
any branch path that begins with the value-string will be matched. Here the following example matches:
/default/main/food/...
while this one does not:
/default/main/barfoo/...
The following examples are all treated as identical on both Windows and UNIX.
<branch name="^/default/main/foo" include="yes"/>
<branch name="^\default\main\foo" include="yes"/>
<branch name="^\\default\\main\\foo" include="yes"/>
<branch name="^/default\main\\foo" include="yes"/>
Posted by David at 5:48 AM No comments:
Labels: Workflow
16 March 2008
Part 2.1 - Enabling & Configuring Workflow
The optional (non-default) workflows can be activated by completing the following procedure:
Verify that you have satisfied the following two requirements:
Install and license TeamSite (which now includes FormsPublisher)—Workflow email notifications use the presentation template compiler installed with FormsPublisher.
The permissions on the iw-home/tmp and the iw-home/tmp/cci directories must be readable and writable to all TeamSite users (the email notifications are temporarily placed in these directories while being created).
And consider the following compatibility issues:
Install MetaTagger 3.6 or later (optional)—MetaTagger 3.5 and earlier are not supported. If you are integrating with MetaTagger, TeamSite must be installed before MetaTagger or the MetaTagger GUI will not work.
Install OpenDeploy 5.5.1 or later (optional)—You must have a base server on the TeamSite server.
Open the iw‑home/local/config/wft/available_templates.cfg file (see available_templates.cfg).
Add an entry for each new workflow.
For example, to add the Author Submit Workflow workflow, add the following entry:
<template_file name='Author Submit Workflow'
path='solutions/configurable_author_submit.wft'>
<allowed>
<and>
<command name="submit"/>
<role name="author"/>
</and>
</allowed>
</template_file>
For your convenience, a file containing entries for each new workflow is provided. It is called available_templates.cfg.fragment and is located in the iw‑home/local/config/wft/solutions directory. You can copy any or all of the workflow entries from this file into your available_templates.cfg file.
If you are replacing another workflow, you can deactivate it by any of these methods:
Delete the entry
Comment out the entry using <!-- -->
Add the attribute active=“no”
Save and close the available_templates.cfg file.
For each configurable workflow that you added to your available_templates.cfg file, edit the corresponding .cfg file to activate the desired functionality.
The .cfg file contains question and answer pairings for each configurable option. For example, in the Email Notification section:
# Should a email notification be sent if a deploy task fails? email_no_deploy=no
Change the default from no to yes on any feature you want to activate. For a detailed description of the configurable features available in each workflow, refer to Configurable Workflow Settings.
If you are using the Email Notification functionality:
Ensure that your iw.cfg file contains entries for maildomain and mailserver in the [iwsend_mail] section.
If it does not, add the appropriate entries. For example:
[iwsend_mail]
maildomain=yourcompany.com
mailserver=mail.yourcompany.com
Edit the solutions/email_map.cfg file to specify the mapping from user names to email addresses if adding @yourcompany.com to the username is not adequate.
If you are using Metadata Capture functionality:
Ensure that the metadata_capture_ui properties in the workflow-specific .cfg files have the desired setting for either MetaTagger or TeamSite Metadata
Ensure that iw‑home/local/config/ contains datacapture.cfg and metadata‑rules.cfg files, and that these files contain the desired settings.
Ensure the mt‑home/conf/metatagger.cfg file contains the desired entries. See MetaTagger Administration Guide “Configuring MetaTagger to Work with TeamSite” for integration instructions.
Ensure that the category tag values in the metatagger.cfg file match corresponding item name values in the datacapture.cfg file.
Optionally, test your metadata capture configuration from a custom menu item before you try it from a workflow.
If you are using Deployment functionality:
Copy the deployment configuration file (solutions/wft_opendeploy.xml) to the od‑home/conf directory.
Edit solutions/wft_opendeploy.cfg file to specify the mapping from branch names to the corresponding destination nodes and paths.
See Integrating with OpenDeploy for detailed information about these entries.
10. Ensure that yo have add appropriate TS groups and users in LDAP or AD. Then in TS, add all the groups and users. Then add the appropriate user to a group. Then assign roles to each added users.
Posted by David at 8:10 PM No comments:
15 March 2008
Part 1 - Introduction to Workflow
Objective
Define workflow terms
Define task types
Understand types of workflow
Workflow terms
A workflow consist of a set of steps/procedures that are interconnected in predeccessor-successor relationship. It is represented by a flowchart. In Teamsite workflows implements business workflow and also a *package of files and instructions.
A bussiness workflow is a real world process used by an organistaion to produce a result.
**Job: A new workflow instance started by an execuation of a workflow model. This job is identified by a numeric job ID. A job is a collection of tasks and links but all the variables have been filled in. Job has one or more files attached to it. Many jobs can be started from one workflow model.
Job specifications are XML files that describe a specific job instance. You can create these files either by invoking the instantiation of a workflow template or a workflow modeler only through a TeamSite v6.7.1 GUI.
However previous version of TS v6.5 uses the workflow template to create the job specification
Instantiation: Means that the workflow model is being filled in with values to gnerate a true job specification. If any variables are user supplied, then instantiator display a form to gather information from user.
Workflow modeler (new feature in v6.7.1) is a TS authoring tool for defining a workflow model that will implement a recurring and approving business process for content management. Think of a workflow model like an automated flowchart use to i)manage content developement life cycle ii)automate development tasks iii)customise procedures. It saves the workflow model as a XML file with *.ipm extension.
Workflow template: (old feature in v6.5 but still supported in v6.7.1) Workflow templates are XML files with a .wft extension (known as wofty files) that describes the job specifications for a particular workflow. These files are created dynamically with embedded Perl script to dynamically generate the output job specification. Then it is transfer to the TeamSite server where they can be instantiated by users, as needed, to become specific jobs. The configuration file available_templates.cfg lists all the workflow templates available to users to be instantiated.
The server-side workflow subsystem resides on the TeamSite server and contains all the executable files that provide workflow functionality.
Task: A single step in a workflow process which can be perform by a perseon or program & the task status is either inactive or active and identified by a task ID. More than one task can be active at a time. Active means user has not yet completed the task's work.
Activation: User or program for that task has not yet completed the task's work
Transition: Occurs when one task is finished, which cases the current task to become inactive and activate the current task's successor (according to the workflow model) which may be one or more other task.
Transition options: There are two or more possible ways to transition, usually depending on the outcome of the task.
Links is a connection between two or more tasks and present the oder in which tasks are performed. Links can activate more than one tasks at a time. Links can also re-activate task that have already completed (i.e. activate an inactive task), creating loops.When a task is completed, the next task starts automatically. Links create predecessor/successor relationship between tasks. When a predecessor task is completed, it activates its successors. Links can have multiple predecessor/successor.
Start and end event - Workflow model has one or more start and end event. All successors of start evetns become active as soon as workflow job is started. WHen any end event activates, the workflow is terminated. Start event has no predecessor. End event has no successor.
Serial task activation - A workflow model in which no more than 1 task is active at one time.
Parallel task activation - A workflow model in which more than 1 task active at a time.
Parell Transitions - If a user task has 2 or more successor, the user selects one of them to be the next task
The package is routed from one user to the next:
Each user reads instructions to see what they need to do to the files
Afer doing their work, the user addes comments to hte package what they did and pass the package to the next person in sequence.
**When a workflow job is started, the following occurs
Workflow job is instantiated
Workflow job becomes active
Task in workflow becomes active if they are successors of a start event.
Workflow users
Business users define the workflow requirements
Developers implement workflows
Content Managers/Contributor initiate and maintain the jobs and automate and perform the tasks.
Task Types
Most workflows are automated by the program. Those tasks that can't be performed automatically must be assigned to a user to manually perform a interactive task (e.g. review/approve or reject, content creation, etc). So there are two types of task:
1. Automated task: Perform operations on the worflows flikes like copy, lock, submit, etc..
2. User-interactive tasks comes in 3 types:
User task - Standardise TeamSite (TS) workflow task types designed to give user the tools needed to work on the workflow inside their "to-do" windows. Example include: create/edit files, fill in forms/metadata, review and approve/reject, compare and merge.
Group task - Assign to a list of people and will show up in all their "to-do" windows, until one of the user takes ownership (i.e. starts the work), which assigns the task to that person. After that the group task becomes a standard user task. Example include lock/unlock, email notification, copy/move files, submit, deploy, execute program.
Custom user task - Known as CGI task because the task is created by system adminstartors from common gateway interface task, which can provide customise task.
Workflow types
TS has two "out of the box" common workflows, but any number of other workflows can be created during TS installation. Workflow is dependent on busines needs and operations.
Assign workflow: Where a person asign work to another team member. Some examples include:
A team member (Assigner) assign a set of files and instructions to another person
Assignee completes the work
The Assigner who assigned the work then reviews it, and either approves/rejects the work
After approval, the files are automatically submitted.
Email is sent to the Assigner and Assignee.
2. Submit worfklow - Runs a job to submit a workflow using the default_submit workflow template.
Workflow Events
Workflow events are the initiation of starting a job when a user selects the following event:
Action->new job
Submit
Assign
Create/delete a DCR
Resources
For further details, read: Workflow Developers Guid v6.7.1 SP1
Posted by David at 2:00 AM No comments:
Labels: Workflow
08 April 2008
TeamSite Search Overview
Overview
The primary use of TeamSite Search is to find a file for:
view, editing, copying & reuse
removing outdated file
reporting purposes
recovery purposes
There are other reasons why a user would want to use the search facility in TS but the above points are the common reasons for using a search.
Architecture
Search facility is made up of 2 parts:
Index manager/server :- Controls indexing of content. Also uses a document cracker that looks into the content of a file or data record and provide metadata and full search content on it.
Search manager/server :- Performs queries on indices and returns the search result to queries. TS interface communicate with the search manager to request searches and to view the search results.
Both index and search server uses query agent, which is a processor use to perform indexing or querying documents.
So for example if you search for a content (case sensitive search), you send a query to the search manager. The search manager scans a search index for files that match your query, and returns a results page. The results page lists matching files in order of relevance.
There are two types of search methods in TS that user can do:
Simple searches :- Before you can initiate a simple search, you must first navigate into an area on a branch
that is indexed for search. A simple search query returns documents that contain any of your keywords. Phrase matching, wild cards, and Boolean logic—the use of “and”, “+”, “not”, “-”, and other operators in a search query—are not supported by simple search but is supported in advance search
Advance searches
Configuring search
Search engine can be configured by editing either of the 4 files located in iwsearch-home/etc folder
branches.cfg - Config file to tell the index manager which branch is to be index during startup time
search.properties - Config file to tell the index and search server/manager which set of files is to be index when a user submits a set of fiels through TS.
FieldMapping.xml - Allows additional attribute fields that will be indexed by the index manager.
search.xml (located at: iwhome\httpd\webapps\conten_centerweb-inf\conf\search)
NOTE: Any update of the 4 search configuration fiels above will require a server reboot to take affect.
branches.cfg
Provide search feature to control which branches will be index - See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/search4.html
search.properties
Provide search feature such as:
Partial index
Controls how many files are submitted to be indexed at a time
Controls which files will not be index
Control size of file that will be index
Enable/disable index update whenever a file is submitted
See - http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/search7.html
Posted by David at 9:23 PM No comments:
Labels: Administration
11 March 2008
What is TeamSite?
TeamSite is a content management software (CMS) for enterprise business that was developed by a vendor called Interwoven, that started off from in the USA head office in 1993 and now a company global organisation in many countries providing content management solutions to business clients.
At the heart of any CMS is the ability to control, manage, store, find, share, change, track, test, move and back up a large number of the organisation's asset (a file that contains important data), such as web pages, document files, database, program source codes, scripts.
That's what Teamsite CMS does with ability to cover the content development life cycle. The basic development cycle includes:
Assign: a new task involving content creation and assigning that task to a person.
Edit: Content is edited and tested by a content contributor.
Review: Content is reviewed by a reviewer with possible rejection and recycle the process.
Deploy: Content that is approved by the reviewer is then transferred to production site.
The diagram above can equivalently look more like the diagram below.
Note:
TS integrates with OpenDeploy and MetaTagger. OpenDeploy is a software that allows contents, documents, files to in TS be deploy and published to the production server. MetaTagger is a software that automates the process of tagging enterprise business content with descriptive metadata to help transform a loosely content to a organise library catalog.
TeamSite can be used for a wide range of applications:
Public web sites
Intranet and internal portals
Extranet portals
Colloborative document and digital asset management
Workflow management
MS Windows
Solaris
Linux
However this blog will only cover installing TS on a Windows environment.
Installation Path
The required steps in order for TS installation are as follows below. Basically there are 5 package installation software that needs to be installed:
Install TeamSite base server release v.6.7.1
Install TeamSite search server release
Install TeamSite v6.7.1 Service Pack 1
Install TeamSite search server Service Pack 1
Install Workflow Modeler
Pre-requistie
Get appropriate license keys for TeamSite from support.interwoven.com.au
Download all the five TeamSite package installation software from Interwoven support
Temporary turn off all services runnign Anti-Virus software prior to installing TeamSite. Then enable the virus software after TeamSite installation is complete.
IIS v6 has been installed on the server machine that will run TeamSite
Install SQL 2000/2005 on the TeamSite server. Create a database (named tsevents). Create a database admin account (sa account for SQL)
Install Java RunTime (minimum v1.5 or later)
.NET Framework 2 has been installed (if the server is hosting .NET applications)
Install SQL 2000/2005 (If TS server is using SQL 2005 then prefer to install JBDC 2000 driver first as TeamSite Installation only picks up 2000 JBDC driver. Then later install 2005 driver) JDBC driver has been installed in the TeamSite server
Appropriate users and groups has been added to Active Directory
Domain name has been created and shared in TeamSite server box
Installing TeamSite
1. Login into the server with system domain administrator. Then follow and read the instruction here on how to install TemSite 6.7.1 Service Pack 1. Accept all default value in the installation instructions except for the directory lcoation of TS should be at c:\interwoven\teamsite folder. You should also obtain the following license key from Interwoven support before you start installing. There will be errors found if user skip getting a license key and install TS.
TeamSite license key (TS.lic file)
ContentServices SOAP server license key
ReportCenter license key (optional)
Provide Interwoven support with the following information about the server:
Hostname
Domain
Product version
Platform OS
Number of CPUs
2. After installing Teamsite base release v6.7.1 with the license key, reboot the server and during the loading of window, Interwoven TS dialog bow will pop up with status message saying to wait awhile while TS configures IIS and adds a default TS user and group to AD.
3. After rebooting the server for the first time after installing TS, ensure that virtual Y drive has been created and ensure that the following 6 TS services are running (Control panel->administrative tool->services):
Interwoven Event Subsystem
Interwoven Proxy
Interwoven servlet Engine
Interwoven TeamSite
Interwoven TeamSite Utility Daemon
Interwoven Web Daemon
If any of the TS service is not running and/or Y drive has not been created, type "iwreset -a" in command prompt.
5. Ensure that TS login screen is loaded in the internet browser by going to URL: http://localhost/iw-cc/command/iw.ui and that you are able to log into TS using the administrator's windows authnetication account.
6. After succesfully logging into TS, add all the approiate AD users into TS, including IIS anonymous user TSIMP_. Add all AD users to TeamSite Preview AD group. Note: The list of all available users displayed in TeamSite are retreieve from Active Directory or LDAP. So if you want to add a user in TeamSite but is not displayed in TS, you need to add that new user in AD/LDAP first. Always reset TS or reboot the server everytime you have added a new AD/LDAP user so that TS will be updated with the list of new users from AD/LDAP.
7. Add a new TS group. Add existing members (created from step 6) and managers to the TS group.
8. Add appropriate roles to the TS group (created from step 7) to the selected branch.
Note: Before installing TeamSite Search server base release v2, you must ensure that all TS services is running, y drive created and can log into TS.
9. Install TS search server base release v2.0 See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/02_installing19.html for instructions and install it at c:\interwoven\search folder. Then reboot server after installation is complete.
10. Install Teamsite v6.7.1 SP 1 and reboot the server after installation.
11. Install TS search server SP 1 and reboot the server after installation.
This topic covers the procedure steps of installing TeamSite version 6.7.1 SP1. TeamSite (TS) can be installed on a server that supports either OS platform:
MS Windows
Solaris
Linux
However this blog will only cover installing TS on a Windows environment.
Installation Path
The required steps in order for TS installation are as follows below. Basically there are 5 package installation software that needs to be installed:
Install TeamSite base server release v.6.7.1
Install TeamSite search server release
Install TeamSite v6.7.1 Service Pack 1
Install TeamSite search server Service Pack 1
Install Workflow Modeler
Pre-requistie
Get appropriate license keys for TeamSite from support.interwoven.com.au
Download all the five TeamSite package installation software from Interwoven support
Temporary turn off all services runnign Anti-Virus software prior to installing TeamSite. Then enable the virus software after TeamSite installation is complete.
IIS v6 has been installed on the server machine that will run TeamSite
Install SQL 2000/2005 on the TeamSite server. Create a database (named tsevents). Create a database admin account (sa account for SQL)
Install Java RunTime (minimum v1.5 or later)
.NET Framework 2 has been installed (if the server is hosting .NET applications)
Install SQL 2000/2005 (If TS server is using SQL 2005 then prefer to install JBDC 2000 driver first as TeamSite Installation only picks up 2000 JBDC driver. Then later install 2005 driver) JDBC driver has been installed in the TeamSite server
Appropriate users and groups has been added to Active Directory
Domain name has been created and shared in TeamSite server box
Installing TeamSite
1. Login into the server with system domain administrator. Then follow and read the instruction here on how to install TemSite 6.7.1 Service Pack 1. Accept all default value in the installation instructions except for the directory lcoation of TS should be at c:\interwoven\teamsite folder. You should also obtain the following license key from Interwoven support before you start installing. There will be errors found if user skip getting a license key and install TS.
TeamSite license key (TS.lic file)
ContentServices SOAP server license key
ReportCenter license key (optional)
Provide Interwoven support with the following information about the server:
Hostname
Domain
Product version
Platform OS
Number of CPUs
2. After installing Teamsite base release v6.7.1 with the license key, reboot the server and during the loading of window, Interwoven TS dialog bow will pop up with status message saying to wait awhile while TS configures IIS and adds a default TS user and group to AD.
3. After rebooting the server for the first time after installing TS, ensure that virtual Y drive has been created and ensure that the following 6 TS services are running (Control panel->administrative tool->services):
Interwoven Event Subsystem
Interwoven Proxy
Interwoven servlet Engine
Interwoven TeamSite
Interwoven TeamSite Utility Daemon
Interwoven Web Daemon
If any of the TS service is not running and/or Y drive has not been created, type "iwreset -a" in command prompt.
5. Ensure that TS login screen is loaded in the internet browser by going to URL: http://localhost/iw-cc/command/iw.ui and that you are able to log into TS using the administrator's windows authnetication account.
6. After succesfully logging into TS, add all the approiate AD users into TS, including IIS anonymous user TSIMP_. Add all AD users to TeamSite Preview AD group. Note: The list of all available users displayed in TeamSite are retreieve from Active Directory or LDAP. So if you want to add a user in TeamSite but is not displayed in TS, you need to add that new user in AD/LDAP first. Always reset TS or reboot the server everytime you have added a new AD/LDAP user so that TS will be updated with the list of new users from AD/LDAP.
7. Add a new TS group. Add existing members (created from step 6) and managers to the TS group.
8. Add appropriate roles to the TS group (created from step 7) to the selected branch.
Note: Before installing TeamSite Search server base release v2, you must ensure that all TS services is running, y drive created and can log into TS.
9. Install TS search server base release v2.0 See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/02_installing19.html for instructions and install it at c:\interwoven\search folder. Then reboot server after installation is complete.
10. Install Teamsite v6.7.1 SP 1 and reboot the server after installation.
11. Install TS search server SP 1 and reboot the server after installation.
11. Install TS search server SP 1 and reboot the server after installation.
12. Install Redirector module for IIS - See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/03_webServer7.html#wp1170385
13. Redirect NSAPI HTTPS request. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/03_webServer11.html#wp718293
14. Install lcoal file manager. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/04_clients3.html#wp1126238
15. Mount the TS server file system (i.e. Y drive on the server) as a shared network drive. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/04_clients6.html#wp1123940
16. Create the branches and the workarea for each branch. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.installwin/05_content6.html#wp482158
17. Give TS group and users access permission to the newly created branches.
18. Publish all files located at /iwadmin/main/workflowModels/WORKAREA/iw-wa/Internal to staging.
19. Configure event sub-system to use SQL 2005 JDBC driver. See:
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=56631
http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/config.server21.html
Note the following: i) Download SQL JDBC driver version 1.1. (version 1.2 does NOT work well) ii) Firstly create a new database and a SQL Server authenication user that is reflected in the jmsconfignew.xml file. iii)Run the create_sqlserver.sql script for the new database created in step ii.
20. Configure SQL 2005 to allow remote connection by the SQL JDBC driver. See: http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277 . Note the following:
Change the port number of url element tag to 1434 in jmsconfignew.xml file. Then change the TCP/IP port number to 1434 (defaulted to 1433) for "Protocols for MSSQLSERVER" in SQL Server Configuration Manager, because SQL "Native Client Protocols" is already using port 1433. Test it by restarting the "Interwoven Event Subsystem" service and checking to see that there is no error in the log file iw-home\local\logs\eventsubd_err.log.
Change the Authentication Mode of the SQL server from "Windows Authentication Mode (Windows Authentication)" to "Mixed Mode (Windows Authentication and SQL Server Authentication)". Restart SQL Server service.
Start the following services: SQL server, agent, browser, Full text and VSS writer.
21. Configure the iw.cfg file and edit it as required for each section. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/iw.cfg4.html for more detail instructions on how to do it.
22. Implement a backup strategy plan for TeamSite. See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/backups.html for more details.
23. Configure the Search server - See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/search.html#wp999146 for more details.
24. Install Workflow Modeller
Online e-Book:
TeamSite Installation Guide
HTML version
PDF version
TeamSite Administration Guide:
HTML version
PDF version
Posted by David at 11:42 PM 2 comments:
Labels: Administration
16 October 2008
TeamSite Skill Set
To learn the skills of TeamSite CMS, knowledge of with experience in usingTeamSite must be obtained. These knowledges are categories
and rated into four skill levels below. So for example, basic low skill levels for beginners will require basic fundamental knowledge of TeamSite. The higher the skill levels, the more tecnhnical knowledge of TeamSite is required to understand.
The skill levels are as follows:
Level 0: The Developer has no knowledge of or experience in the skill/knowledge area whatsoever.
Level 1: The Developer has a conceptual knowledge of the skill/knowledge area and has some limited commercial experience or may have experimented with the related concepts and/or supporting technologies in a non-commercial sense. The developer cannot apply this skill/knowledge area without direct supervision.
Level 2: The Developer is proficient in the skill/knowledge area with recent commercial experience in its application, can apply the skill/knowledge without direct supervision, but has insufficient experience/knowledge
to provide direction to others in the given area.
Level 3: The Developer can be considered an expert in the skill/knowledge area with considerable recent commercial experience in its application, with experience providing mentoring/guidance to others. The Developer has a detailed and broad understanding of the skill/knowledge area.
Note that each level described above subsumes all levels below it. Thus, in order for a TeamSite Developer to rate at Level 3, he or she must meet the criteria for Levels 1, 2 and 3.
The following area of TeamSite knowledge a TeamSite Developer need to obtain are broken down into each levels below:
Level 0
Introduction to Content Management System (CMS)
Can describe the definition of TeamSite
Can describe the features of TeamSite
Can describe the definition of CMS
Can describe the purpose of CMS
Can describe the content development life cycle
Cam describe the definition of an asset
Introduction to TeamSite Concept
Can define TeamSite server architecture
Can define TeamSite terminology like for example: i)
Content stores ii) Branches ii)Workareas iv) Edition and Versionin v)Can describe the definition and what are the roles in TeamSite vi)Metadata vii)Can log in to a TeamSite server
Can describe and demonstrate and use the features in each version of ContentCenter User Interface
Level 1
Editing files
Can do simple and advance search for assets
Can describe and use TeamSite VisualPrevew tool
Can describe and use Local File Manager to edit files
Can describe and perform basic file operations like copy, rename, delete, create, move/rename, import/export and modifying properties of a file
Can view and set metadata
Can describe and demonstrate checking in/out a file and able to perform merges
Introduction to Workflows
Can describe the workflow terminology use in TeamSite, like for example understand the following:
Workflow
Job specification
Workflow Moder
Workflow template
Task
Activation
Transition
Links
Understand the difference between serial and parallel task
Workflow events
Introduction to Forms Publisher
Can describe the forms publisher terminology use in TeamSite, like for example understand the following:
Data Capture Templates (DCTs) / Data Capture Forms
Data Content Records (DCRs)
Presentation Template (PTs)
Level 2
Workflow Development
Can describe and demonstrate how to configure and set up out of the box workflows templates and workflow models
Can describe and demonstrate how to design, implement and deploy a workflow using the Workflow Modeler Tool
Can describe and demonstrate how to design, implement and deploy a customise workflow template using XML and Perl script
Form Publisher Development
Can describe and demonstrate how to develop Data Catpure Forms
Can describe and demonstrate how to develop Presentation Templates
Can describe and demonstrate how to use APIs and Command Line with Data Capture Forms
OpenDeploy
Can describe and demonstrate how to configure Open Deploy tool to deploy files to production server
Level 3
Advanced Workflow and Form Publisher Development
Can describe and demonstrate executing external programs
Can describe and demonstrate creating custom data source
Can describe and demonstrate using external database with Data Catpure Forms
TeamSite Administration
Can describe and install or upgrade TeamSite CMS, TeamSite Search, MetaTagger and Open Deploy
Can describe and demonstrate the process of configuring and reindexing TeamSite Search
Can demonstrate the maintenance process of creating, deleting, updating users, groups and roles in TeamSite
Can describe and demonstrate the process of backing and restoring content store
Can describe and demonstrate diagnosing error message with log files
Can configure file virtualisation in TeamSite
Posted by David at 1:21 AM 1 comment:
Labels: TeamSite Basic
09 April 2008
Part 4 - Installing TeamSite Front-Office
Overview
TeamSite Front-Office (FO) is a interface tool that allow users access to their workarea & TS functionality within Windows explorer or Microsoft Office applications (e.g. MS Word) . FO consists of 2 components:
TeamSite Front-Office Server: Works with your TeamSite server to provide a framework for contributing content from development applications directly to TeamSite.
TeamSite Front-Office Client: A client-side application that enables content contributors to access TeamSite features directly from their development applications. This component includes the application plug-ins, the TeamSite Briefcase, and the TeamSite Front-Office Configuration Wizard.
Both of these 2 components will need to be installed individually, i.e. FO server is to be installed on the server that runs and host TS. The other is to be installed on the client's machine.
Installing & Configuring Front Office Server
The instruction below will be installign the latest version of FO version 5.6.6 at the time of writing this blog.
Before you install FO server, ensure that all workarea branches and users with their roles has been added into TeamSite and that the users/group has been appropriate permission to access the workarea.
Before you install the FO Windows server, you must have local Administrator
privileges because the installation process needs to start and stop the iwwebd
service.
Download the FO server and client software from Interwoven support website. TFO_server566Buildxxx.exe & FTO_client566Buildxxx.exe
Install Front -Office server (v5.6.6) on the server that had TeamSite install, by running TFO_server566Buildxxx.exe. Installation path shall be c:\interwoven\TeamSite Front-Office\ folder
Configure users and workarea in iw-home\conf\iwwa.cfg file to give FO user(s)/group access to a workarea.
Configure iw-home\etc\iw.cfg file under "[FrontOffice]" section.
Configure iw-home\local\config\wft\available_templates.cfg file to add out of the box FO workflows (see availiable_templates.cfg.tfo.example) if submit operations from FO triggers a worflow, i.e. iw.cfg had "wf_submit=yes"
Configure index_template.htx if FO auto-index is enabled in iw.cfg. Then copy the index_template.htx file to each directory within a workarea that you want to index.
Reset Teamsite server with "iwreset -a" command in DOS prompt.
Installing and configuring Front-Office Client
Run FTO_client566Buildxx.exe software on each client's machine that will be using FO.
Follow the instruction on the setup screen.
Further reading
1. Front-Office Admin Guide (PDF version)
Posted by David at 5:46 PM No comments:
Labels: Administration
10 March 2008
TeamSite Roles
A role is a set of allowed permission (e.g. copy, delete, create, etc) that is assigned to each user. Teamsite has 5 "out of the box" default rows, i.e.
Administrator
Master
Editor
Author
Reviewer
Administrator
Content development managers or team leaders. Owners of a branch but not Teamsite admin.
Responsible for managing a project that is stored in a branch by creating new workareas for Editors and groups and by creating subbranches of their own branch to explore separate paths of development.
Capbilities of an author, editor and reviewer.
Editor
Roles include: submitting completed work to staging, assign work to authors, edit and create files
Approve/rejects work and create new versions by sbubmitting files, merging and reverting.
Purose: Editors are generally "deveoper” users, who primarily supervise the work of Authors, or self-managing “power users", who need extended TeamSite functionality to manage their own content.
Author
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 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.
Purpose: 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.
Reviewer
Review content changes and either reject or apporve changes.
Browse workareas and review files and forms, search for content, and work with tasks.
Purpose:Reviewer role is a typical manager who's role is to review and check other people's work.
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 system-wide basis.
Users with the Master role have access to the Administration tab 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.
Posted by David at 5:44 AM No comments:
Labels: TeamSite Basic
17 April 2008
TeamSite Upgrades
TeamSite Upgrades Overiew
The overall plan for TeamSite (TS) upgrades are as follows:
Day 1
Perform back up procedures
Perform prerequisite requirements
Upgrade TeamSite and OpenDeploy (OD) with latest patch for TS and OD
Apply new licenses
Day 2
Upgrade TeamSite Search
Configure TeamSite Search
Fix any upgrade issues
Re-run toolkit.ipl for any UI customization
Day 3
Check accounts and permissions
Check basic functionalities works in the new upgrade of TS
Perform system testing
Test form publishing (DCT, DCR and PTs)
Test workflows
Test OpenDeploy and Data Deploy
Test View->My local files
Fix any issues found in testing
Day 4
Reserve day for fixing any upgrade issues
Bug upgrade report for TS v6.7.1 with SP1
There is a bug report with using VisualFormat editor in TS v6.7.1 Service Pack 1. When a user previews a Data Capture Form that has a text area field using Visual editor, an error pop up page will appear. Use TinyMce instead of using VF as a work around solution.
Latest patch installer for TS v6.7.1 SP1 has glitches with previewing a Presentation Template on the TS server that runs with a Semantic Anti-virus. Skip the step for installing the latest TS patch.
Prerequisite
Back up the entire hard drive of where TS server and Search server was installed (e.g. if TS was installed at c:\interwoven, then backup the entire c drive).
Back up the entire iw-store. If iw-store was stored in a separate partition drive, then back up that entire drive.
Get Administrator login account details from the client.
Get Interwoven support login account from the client.
Notify TS users of outage.
Disable all antivirus software/services temporary on the TS and search server (if any), particularly if server has a Semantic virus running, as it will cause problem with new TS installations or upgrades (See knowledge article xx)
Check and confirm what current version of TeamSite is installed on all the server boxes that will be upgraded. This is done either by:
Control panel->add/remove program; or
Check iw-home\iwinstall\iwov-inventory.xml file
Download the relevant TS installation package software from Interwoven support website.
Upgrade instructions
The existing TS.lic license key used for TS v6.5 file would still be valid and useable after the upgrade. So there is no need to generate a new TS license key.
The upgrade path for various TS version on Windows OS is as follows whether the upgrade was on the same or on a different server box:
TS v6.5 upgrade path
Upgrade from v6.5 to v6.5 SP 2 (if haven’t done so)
Upgrade from v6.5 SP2 to v6.7.1
Upgrade from v6.7.1 to v6.7.1 SP1
Install only latest patch for v6.7.1 SP1
TS search v6.5 upgrade path
Upgrade from Upgrade from v6.5 to v6.5 SP 2 (if haven’t done so)
Upgrade from v6.5 SP2 to v6.7.1
Upgrade from v6.7.1 to v6.7.1 SP1
OD upgrade path
Install OD Base Server v6.1.1
Install OD Admin Server v6.1.1
Apply latest patch to OD server
Install OD receiver v6.1.1
Apply latest patch to OD receiver
*Note: OD v6.1.1 is more stable to install than v6.2
TeamSite Upgrade steps
1. Download the following installer from Interwoven support site:
TS v6.7.1 installer
TS search v6.7.1 installer
TS v6.7.1 SP1 installer
TS search v6.7.1 installer
Patch update for v6.7.1 SP1
2. Login as Administrator on the TeamSite server machine
3. Backup all configuration files (*.cfg and xml files)
4. Manually stop all TS services and set them to manual on start up
5. Confirm step 4 by going to DOS prompt and type “netstart amore” and look for Interwoven port number
6. Manually stop all IIS
7. Install TS v6.7.1
Select “mssql” checkbox and select the SQL JDBC driver file (*.jar) from iw-home\TeamSite\eventsubsystem\lib folder
Select “No” for don’t overwrite existing jmsconfignew.xml file
8. Reboot server
9. Log into TeamSite via the internet browser and make sure that you can successfully login in
10. Run iwaccessmigrate with –m & -bg –n parameter
11. Run “iwreset –a”
12. Login into TS to ensure that TS is running after performing step 10
13. Manually stop all the TS services
14. Install TS v6.7.1 SP 1
15. Install the latest patch
Manually stop all TS services
Run the patch installer
16. Reboot server and login to TS to ensure that it is running
17. Check that event subsystem service is running
18. Decide whether the client will be using either TinyMCE or VisualFormat editor for published form.
If using VisualFormat (VF) editor, there is a required additional step to install client visual format on the entire client’s machine that will be using published forms. Location of visualformatclient.exe installer is found at C:\Interwoven\TeamSite\httpd\iw\ewebeditpro20\clientinstall folder. You can customize the VisualFormat toolbar by editing the visualformatconfig.xml file at iw-home\httpd\iw\ folder. (for more information read Form Publisher Developer Guide 6.7.1 release PDF doc)
If using TinyMCE, the advantage is that it is already installed with TS because it’s a Java app. However VF is more powerful than TinyMCE. The toolbar can be customized by editing custom_config.js
19. Run script (toolkit.ipl) to migrate any customize UI (if there are any UI customization)
Note:
Read the installation log file at c:\iwinstall\log folder for any unsuccessful installation
Read TS server log file iwtrace.log at iw-home\teamsite\local\logs folder
Read iwutid_cmdout.log file for any PT error message provide iwutild.cfg file debug mode enabled
TS search server upgrade steps
Note: If the search v6.5 was installed on a separate server box, then upgrading the TS server can be done independently without needing to wait for TS upgrades. So to save time TS Search upgrades can be simultaneously run in parallel with TS upgrade.
Run TS search v6.7.1 installer on the search server box and install it at c:\interwoven\search folder
Locate and enter the TS server host. Ensure that you can firstly ping the TS server host name to confirm that both search server and TS server box can communicate and ping each other
Locate the shared file system. Usually at iw-home\new folder (create a new folder)
Check that the search service are running
Install the search v6.7.1 SP 1
* Manually stop the search service
* Run the installer
Reboot the server
Check that all search services (i.e. Interwoven TS Search & Index) are both running
Configure the search
* Edit iw-home\cssdk\cssdk.cfg file: Uncomment
# search.server.host: localhost
# search.server.port: 6720
# search.server.maxConnectionLimit: 10
* Edit iwseach-home\etc\branch.cfg file and add the branches that you want to index
* Restart search and index services (Stop in order search and index. Start index and then search service)
* Run CTL:
iwndxlistbr - Display the list of branches that are index
iwndxrefreshbr -b /default/brachname…
iwndxrefreshbr –I /default/branchname.. (Incremental update on real time)
OD upgrades steps
Upgrade the following OD v6.1.1 in this order below.
OD base server
OD admin server
OD receiver server
1. Get a OD license key
Go to DOS command
Run java -cp od-home/lib/odng.jar com.interwoven.license.LicInfo
-f output-file -p OD
Login the Interwoven support site and go to the OD generate license key webpage
Enter the server information generated into the form and submit it
2. Back up a copy of all files from iw-ODhome\config and etc folder.
3. Download v6.1.1 of OD base, admin server and OD receiver installer from Interwoven support site.
4. Stop all previous version of OD services
5. Run the OD base installer. Install it at c:\interwoven\ folder
6. Choose “upgrade” select box from the installation dialog screen
7. Follow the installation instruction on the screen to install it
8. Check the email that will receive the OD license key file
9. Copy OD.lic to iw-ODhome\etc folder
10. Reboot server
11. Check that OD base service is running (i.e. 62 services). If not, then restart it and set to automatic startup
12. Run the OD admin installer on the same server box that had OD base installed in step 5 and follow its instructions
13. Reboot the server
14. Ensure that OD admin server is running
15. Apply latest patch for OD server. Read the README.txt for further instructions on installing the patch. Basically the instruction will instruct you to:
* Stop all OD services
* Run the patch installer
* Update the registry
16. Reboot the server
17. Check that all OD services are running. If not then set OD services to automatic and start the OD Interwoven services (i.e. AccessService, UI admin and 62 services)
18. Run the OD receiver installer on the other receiver server box
19. Choose “upgrade” option box from the installation dialog box
20. Apply latest patch to OD receiver
21. Get OD receiver license key
Post installation
Enable the Symantec antivirus is back up and running after the whole TS installation package have been installed. Set the antivirus services back to automatic start up.
Posted by David at 9:24 AM 2 comments:
Labels: Administration
29 April 2008
Configuring .NET ASPX File Virtualization for TeamSite
The following configurations are necessary to successfully virtualize content from aspx files on a TeamSite Server where the .NET Framework is also installed on the same server.
Prerequisite
Add the ASPNET user to the "TeamSite Web Preview" Group.
Ensure that .NET framework version 2 is already installed in the same server box that runs TeamSite.
Details
If you are using Windows 2003 the following must also be done (until Bug 57146 has been fixed):
If IIS was installed before you installed TeamSite then you need to delete the default website. Rename the current default website (e.g. “default website bkup”) and click the “Stop” button for the backup default website to stop IIS from running. Then create a new one (also name it “Default Web Site”), using port 81, set path to c:\inetpub\wwwroot and configure it for anonymous access using the IIS IUSR_ user. Click the “Start” button on the new created default website.
Go to Default Web Site properties->ASP.NET tab and check the the .NET version. If there are two version of the .NET framework in the selected drop down box, select version 2.0.xxxx
Go to Default Web Site and Add the SSI ISAPI filter as follows
Right click Default Web Site > Properties > ISAPI Filters > Add, give a filter name like "iwrewrite" and point to \lib\iwproxy_isapi.dll
Within the IIS Management console, under “default website” create a new virtual directory called "iw-mount" which points to the Y:\ drive directory. Anonymous access to this directory should be the TSIMP_ user.
For the root directory (iw-mount), click the “Configuration” button and check the configuration of the defined application to ensure that at least the extensions ".aspx" points to the version 2 .NET framework of aspnet_isapi.dll. Further extensions pointing to this are asax, ascx, ashx, asmx & axd.
Check in the Web Service Extensions that Active Server Pages and ASP.NET are enabled.
Do step A to C **
Set full permission to everyone on the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files folder
Restart IIS and run “iwreset –a”
You should now be able to run a simple ASPX. (just take a simple HTML page and rename it .asp/.aspx.
Log into TeamSite and view a ASPX page.
If you receive and error like "Access denied to 'Y:\default\main\WORKAREA\test, Failed to start monitoring file changes" then you need to check that all necessary parts of ASP.Net have the correct permissions as per Microsoft Knowledgebase articles 317955 & 316721. Interwoven KB article 53298 may also help to identify the problem.
If all the steps are successful, then delete the old default web site that was renamed in step 1 (optional).
The "C:\Inetpub\wwwroot\aspnet_client" directory contains JavaScript files used by .NET, and is automatically installed with the framework.
To enable the virtual system to locate this directory you may need to add a virtual directory at the root of the Workarea:
From within the IIS console, navigate to the Workarea (i.e. "\iw-mount")
Right-click on the Workarea; Select New > Virtual DirectoryEnter "aspnet_client" as the Alias
Enter "C:\Inetpub\wwwroot\aspnet_client" for the Directory
Use the default permissions
* *Ref:
A. From within the IIS console, navigate to the Workarea (e.g. "\iw-mount\default\main\uam\WORKAREA\load")
B. Right-click on the Workarea and click on "Properties", Under "Application Settings" click on "Create" button.
C. Restart IIS.
Further reading:
See knowledge article # 49749
Posted by David at 8:39 PM No comments:
Labels: Administration
17 March 2008
Part 2.2 - Configuring availiable_templates.cfg
The available_templates.cfg file is an XML configuration file that lists all of the workflow templates that are available for use on the TeamSite server. For each workflow, this file indicates the name of workflow, the location of the workflow template file, and the conditions under which the workflow is available.
By default, the available_templates.cfg file is located in:
C:\Program Files\Interwoven\TeamSite\local\config\wft (Windows)
/Interwoven/TeamSite/local/config/wft (UNIX)
Note: If available_templates.cfg is edited and contains non-ASCII text, it must be saved in UTF-8 encoding.
The available_templates element is the container element for the file. This element contains the following attribute:
require_workarea — specify whether (true) or not (false) workflow templates selection screen will include a branch/workarea chooser if workarea context is not present. Most of the out of the box workflow template examples require this to be enabled (require_workarea="true") to work properly. Default value is false.
Within the available_templates element is the template_file element:
<available_templates require_workarea="true">
<template_file name="Author Submit Workflow"
path="solutions/configurable_author_submit.wft">
...
</template_file>
</available_templates>
The template_file element has the following attributes:
name — specify the title of the workflow, for example:
name="Author Submit Workflow"
active — indicate whether (yes) or not (no) the workflow template is enabled. Default value is yes.
path — specify the path where the template file resides. Template files must reside in one of the following locations:
iw‑home/local/config/wft/default
iw‑home/local/config/wft/examples
iw‑home/local/config/wft/solutions
The value you specify is relative to the iw‑home/local/config/wft directory, so if the template file resided in the following absolute path:
iw‑home/local/config/wft/default/author_submit.wft
then you would specify the value:
path="default/author_submit.wft"
Specifying Template Access
You can configure access to each template listed in the available_templates.cfg file by using any combination of the following categories:
Command
Role
Group
User
Branch
The categories can be combined using boolean terms such as AND, OR, and NOT to include and exclude those that meet the inclusion or exclusion criteria you configure. Template access is configured within the allowed element, which is a subelement of template_file:
Within the template_file element is the allowed element, where you can configure user access by matching workflow commands with user roles:
<template_file ...>
<allowed>
...
</allowed>
</template_file>
Command Access
Workflow commands are specified by the command element. The command element specifies the user-activity that starts the corresponding workflow. For example, the following configuration:
<command name="submit"/>
specifies that the associated workflow is started when performing a Submit and that it cannot be invoked by other means.
The valid command values that you can associate with a workflow are:
submit (submitting files)
assign (assign button or menu item)
new_job (new job)
new_TFO_job (new job, in TeamSite FrontOffice)
tt_data (saving FormsPublisher data records)
tt_deletedcr (deleting FormsPublisher data records in ContentCenter Standard only)
all (all possible values from this list)
Note: The tt_data command is valid in ContentCenter Standard and can be configured in ContentCenter Professional; see the User Interface Customization Guide. The tt_deletedcr command is only valid when users are using the ContentCenter Standard interface; in ContentCenter Professional, this command is not valid and data records are treated like any other assets.
Role Access
Access based on TeamSite roles is specified by the role element’s name attribute. For example, the following configuration:
<role name="author"/>
specifies that if the user is logged in as an Author.
Group Access
Access based on user groups is specified by the group element:
<group name="marketing"/>
User Access
Access based on individual user name is specified by the user element:
<user name="jdoe"/>
Branch Access
Access based on TeamSite branch is specified by the branch element:
<branch="/default/products"/>
Combining Access Categories
Pairings of individual or multiple access elements can be included or excluded using the and, or, and not elements within the allowed element. You can use boolean logic to create combinations of categories that can either have access to a specific template, or be excluded from it.
In the following example:
<template_file name="Author Submit" path="default/author_submit.wft">
<allowed>
<and>
<command name="submit"/>
<or>
<role name="author"/>
<role name="editor"/>
<group name="marketing"/>
<and>
<role name="admin"/>
<not>
<user name="jdoe"/>
</not>
</and>
</or>
</and>
</allowed>
</template_file>
the following individuals have access to the Author Submit workflow:
Those who are authorized to perform submit commands.
Those who have the author or editor role.
Those who are members of the marketing group.
Those who have the admin role, with the exception of the user jdoe.
If no access category is specified, it is assumed that category has full access to the workflow template.
Regular Expression Support
You can use regular expressions when specifying branch element constraints within available_templates.cfg to search for a specified pattern and specify what to do when matching patterns are found. Using regular expressions allows a greater level of flexibility when adding items.
For example, if you want only the users in the three administration_1 branches (a1, a2, and a3) to access a workflow template, you can set the following constraint:
<allowed>
<or>
<branch name="/default/main/administrator_1/a1"/>
<branch name="/default/main/administrator_1/a2"/>
<branch name="/default/main/administrator_1/a3"/>
</or>
...
</allowed>
If a new branch called a4 is added to /default/main/administrator_1 you could manually update the available_templates.cfg file to allow access for users in the new branch by adding the branch element to the existing ones:
<branch name="/default/main/administrator_1/a4"/>
Or you could modify the available templates.cfg file to use the following regular expression and, thus, automate the constraints placed on the a4 branch:
<allowed>
<and>
<branch name="/deault/main/administrator_1/.*"/>
</and>
...
</allowed>
This regular expression allows users from any branch under /deault/main/administrator_1 to have access to the template.
Path Separators
When using regular expressions, the path-separators (“\”, “\\”, “/”) are all translated to “/” in both the pattern and the string to match against before attempting the match.
In the following example:
<branch name="foo"/>
any branch path that includes the string foo will be matched. Here the following examples match:
/default/main/food/...
/default/main/barfoo/...
In the next example:
<branch name="^/default/main/foo"/>
any branch path that begins with the value-string will be matched. Here the following example matches:
/default/main/food/...
while this one does not:
/default/main/barfoo/...
The following examples are all treated as identical on both Windows and UNIX.
<branch name="^/default/main/foo" include="yes"/>
<branch name="^\default\main\foo" include="yes"/>
<branch name="^\\default\\main\\foo" include="yes"/>
<branch name="^/default\main\\foo" include="yes"/>
Posted by David at 5:48 AM No comments:
Labels: Workflow
16 March 2008
Part 2.1 - Enabling & Configuring Workflow
The optional (non-default) workflows can be activated by completing the following procedure:
Verify that you have satisfied the following two requirements:
Install and license TeamSite (which now includes FormsPublisher)—Workflow email notifications use the presentation template compiler installed with FormsPublisher.
The permissions on the iw-home/tmp and the iw-home/tmp/cci directories must be readable and writable to all TeamSite users (the email notifications are temporarily placed in these directories while being created).
And consider the following compatibility issues:
Install MetaTagger 3.6 or later (optional)—MetaTagger 3.5 and earlier are not supported. If you are integrating with MetaTagger, TeamSite must be installed before MetaTagger or the MetaTagger GUI will not work.
Install OpenDeploy 5.5.1 or later (optional)—You must have a base server on the TeamSite server.
Open the iw‑home/local/config/wft/available_templates.cfg file (see available_templates.cfg).
Add an entry for each new workflow.
For example, to add the Author Submit Workflow workflow, add the following entry:
<template_file name='Author Submit Workflow'
path='solutions/configurable_author_submit.wft'>
<allowed>
<and>
<command name="submit"/>
<role name="author"/>
</and>
</allowed>
</template_file>
For your convenience, a file containing entries for each new workflow is provided. It is called available_templates.cfg.fragment and is located in the iw‑home/local/config/wft/solutions directory. You can copy any or all of the workflow entries from this file into your available_templates.cfg file.
If you are replacing another workflow, you can deactivate it by any of these methods:
Delete the entry
Comment out the entry using <!-- -->
Add the attribute active=“no”
Save and close the available_templates.cfg file.
For each configurable workflow that you added to your available_templates.cfg file, edit the corresponding .cfg file to activate the desired functionality.
The .cfg file contains question and answer pairings for each configurable option. For example, in the Email Notification section:
# Should a email notification be sent if a deploy task fails? email_no_deploy=no
Change the default from no to yes on any feature you want to activate. For a detailed description of the configurable features available in each workflow, refer to Configurable Workflow Settings.
If you are using the Email Notification functionality:
Ensure that your iw.cfg file contains entries for maildomain and mailserver in the [iwsend_mail] section.
If it does not, add the appropriate entries. For example:
[iwsend_mail]
maildomain=yourcompany.com
mailserver=mail.yourcompany.com
Edit the solutions/email_map.cfg file to specify the mapping from user names to email addresses if adding @yourcompany.com to the username is not adequate.
If you are using Metadata Capture functionality:
Ensure that the metadata_capture_ui properties in the workflow-specific .cfg files have the desired setting for either MetaTagger or TeamSite Metadata
Ensure that iw‑home/local/config/ contains datacapture.cfg and metadata‑rules.cfg files, and that these files contain the desired settings.
Ensure the mt‑home/conf/metatagger.cfg file contains the desired entries. See MetaTagger Administration Guide “Configuring MetaTagger to Work with TeamSite” for integration instructions.
Ensure that the category tag values in the metatagger.cfg file match corresponding item name values in the datacapture.cfg file.
Optionally, test your metadata capture configuration from a custom menu item before you try it from a workflow.
If you are using Deployment functionality:
Copy the deployment configuration file (solutions/wft_opendeploy.xml) to the od‑home/conf directory.
Edit solutions/wft_opendeploy.cfg file to specify the mapping from branch names to the corresponding destination nodes and paths.
See Integrating with OpenDeploy for detailed information about these entries.
10. Ensure that yo have add appropriate TS groups and users in LDAP or AD. Then in TS, add all the groups and users. Then add the appropriate user to a group. Then assign roles to each added users.
Posted by David at 8:10 PM No comments:
15 March 2008
Part 1 - Introduction to Workflow
Objective
Define workflow terms
Define task types
Understand types of workflow
Workflow terms
A workflow consist of a set of steps/procedures that are interconnected in predeccessor-successor relationship. It is represented by a flowchart. In Teamsite workflows implements business workflow and also a *package of files and instructions.
A bussiness workflow is a real world process used by an organistaion to produce a result.
**Job: A new workflow instance started by an execuation of a workflow model. This job is identified by a numeric job ID. A job is a collection of tasks and links but all the variables have been filled in. Job has one or more files attached to it. Many jobs can be started from one workflow model.
Job specifications are XML files that describe a specific job instance. You can create these files either by invoking the instantiation of a workflow template or a workflow modeler only through a TeamSite v6.7.1 GUI.
However previous version of TS v6.5 uses the workflow template to create the job specification
Instantiation: Means that the workflow model is being filled in with values to gnerate a true job specification. If any variables are user supplied, then instantiator display a form to gather information from user.
Workflow modeler (new feature in v6.7.1) is a TS authoring tool for defining a workflow model that will implement a recurring and approving business process for content management. Think of a workflow model like an automated flowchart use to i)manage content developement life cycle ii)automate development tasks iii)customise procedures. It saves the workflow model as a XML file with *.ipm extension.
Workflow template: (old feature in v6.5 but still supported in v6.7.1) Workflow templates are XML files with a .wft extension (known as wofty files) that describes the job specifications for a particular workflow. These files are created dynamically with embedded Perl script to dynamically generate the output job specification. Then it is transfer to the TeamSite server where they can be instantiated by users, as needed, to become specific jobs. The configuration file available_templates.cfg lists all the workflow templates available to users to be instantiated.
The server-side workflow subsystem resides on the TeamSite server and contains all the executable files that provide workflow functionality.
Task: A single step in a workflow process which can be perform by a perseon or program & the task status is either inactive or active and identified by a task ID. More than one task can be active at a time. Active means user has not yet completed the task's work.
Activation: User or program for that task has not yet completed the task's work
Transition: Occurs when one task is finished, which cases the current task to become inactive and activate the current task's successor (according to the workflow model) which may be one or more other task.
Transition options: There are two or more possible ways to transition, usually depending on the outcome of the task.
Links is a connection between two or more tasks and present the oder in which tasks are performed. Links can activate more than one tasks at a time. Links can also re-activate task that have already completed (i.e. activate an inactive task), creating loops.When a task is completed, the next task starts automatically. Links create predecessor/successor relationship between tasks. When a predecessor task is completed, it activates its successors. Links can have multiple predecessor/successor.
Start and end event - Workflow model has one or more start and end event. All successors of start evetns become active as soon as workflow job is started. WHen any end event activates, the workflow is terminated. Start event has no predecessor. End event has no successor.
Serial task activation - A workflow model in which no more than 1 task is active at one time.
Parallel task activation - A workflow model in which more than 1 task active at a time.
Parell Transitions - If a user task has 2 or more successor, the user selects one of them to be the next task
The package is routed from one user to the next:
Each user reads instructions to see what they need to do to the files
Afer doing their work, the user addes comments to hte package what they did and pass the package to the next person in sequence.
**When a workflow job is started, the following occurs
Workflow job is instantiated
Workflow job becomes active
Task in workflow becomes active if they are successors of a start event.
Workflow users
Business users define the workflow requirements
Developers implement workflows
Content Managers/Contributor initiate and maintain the jobs and automate and perform the tasks.
Task Types
Most workflows are automated by the program. Those tasks that can't be performed automatically must be assigned to a user to manually perform a interactive task (e.g. review/approve or reject, content creation, etc). So there are two types of task:
1. Automated task: Perform operations on the worflows flikes like copy, lock, submit, etc..
2. User-interactive tasks comes in 3 types:
User task - Standardise TeamSite (TS) workflow task types designed to give user the tools needed to work on the workflow inside their "to-do" windows. Example include: create/edit files, fill in forms/metadata, review and approve/reject, compare and merge.
Group task - Assign to a list of people and will show up in all their "to-do" windows, until one of the user takes ownership (i.e. starts the work), which assigns the task to that person. After that the group task becomes a standard user task. Example include lock/unlock, email notification, copy/move files, submit, deploy, execute program.
Custom user task - Known as CGI task because the task is created by system adminstartors from common gateway interface task, which can provide customise task.
Workflow types
TS has two "out of the box" common workflows, but any number of other workflows can be created during TS installation. Workflow is dependent on busines needs and operations.
Assign workflow: Where a person asign work to another team member. Some examples include:
A team member (Assigner) assign a set of files and instructions to another person
Assignee completes the work
The Assigner who assigned the work then reviews it, and either approves/rejects the work
After approval, the files are automatically submitted.
Email is sent to the Assigner and Assignee.
2. Submit worfklow - Runs a job to submit a workflow using the default_submit workflow template.
Workflow Events
Workflow events are the initiation of starting a job when a user selects the following event:
Action->new job
Submit
Assign
Create/delete a DCR
Resources
For further details, read: Workflow Developers Guid v6.7.1 SP1
Posted by David at 2:00 AM No comments:
Labels: Workflow
08 April 2008
TeamSite Search Overview
Overview
The primary use of TeamSite Search is to find a file for:
view, editing, copying & reuse
removing outdated file
reporting purposes
recovery purposes
There are other reasons why a user would want to use the search facility in TS but the above points are the common reasons for using a search.
Architecture
Search facility is made up of 2 parts:
Index manager/server :- Controls indexing of content. Also uses a document cracker that looks into the content of a file or data record and provide metadata and full search content on it.
Search manager/server :- Performs queries on indices and returns the search result to queries. TS interface communicate with the search manager to request searches and to view the search results.
Both index and search server uses query agent, which is a processor use to perform indexing or querying documents.
So for example if you search for a content (case sensitive search), you send a query to the search manager. The search manager scans a search index for files that match your query, and returns a results page. The results page lists matching files in order of relevance.
There are two types of search methods in TS that user can do:
Simple searches :- Before you can initiate a simple search, you must first navigate into an area on a branch
that is indexed for search. A simple search query returns documents that contain any of your keywords. Phrase matching, wild cards, and Boolean logic—the use of “and”, “+”, “not”, “-”, and other operators in a search query—are not supported by simple search but is supported in advance search
Advance searches
Configuring search
Search engine can be configured by editing either of the 4 files located in iwsearch-home/etc folder
branches.cfg - Config file to tell the index manager which branch is to be index during startup time
search.properties - Config file to tell the index and search server/manager which set of files is to be index when a user submits a set of fiels through TS.
FieldMapping.xml - Allows additional attribute fields that will be indexed by the index manager.
search.xml (located at: iwhome\httpd\webapps\conten_centerweb-inf\conf\search)
NOTE: Any update of the 4 search configuration fiels above will require a server reboot to take affect.
branches.cfg
Provide search feature to control which branches will be index - See http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/search4.html
search.properties
Provide search feature such as:
Partial index
Controls how many files are submitted to be indexed at a time
Controls which files will not be index
Control size of file that will be index
Enable/disable index update whenever a file is submitted
See - http://support.interwoven.com/library/manuals/teamsite/html/671/ts.adminwin/search7.html
Posted by David at 9:23 PM No comments:
Labels: Administration
11 March 2008
What is TeamSite?
TeamSite is a content management software (CMS) for enterprise business that was developed by a vendor called Interwoven, that started off from in the USA head office in 1993 and now a company global organisation in many countries providing content management solutions to business clients.
At the heart of any CMS is the ability to control, manage, store, find, share, change, track, test, move and back up a large number of the organisation's asset (a file that contains important data), such as web pages, document files, database, program source codes, scripts.
That's what Teamsite CMS does with ability to cover the content development life cycle. The basic development cycle includes:
Assign: a new task involving content creation and assigning that task to a person.
Edit: Content is edited and tested by a content contributor.
Review: Content is reviewed by a reviewer with possible rejection and recycle the process.
Deploy: Content that is approved by the reviewer is then transferred to production site.
The diagram above can equivalently look more like the diagram below.
Note:
TS integrates with OpenDeploy and MetaTagger. OpenDeploy is a software that allows contents, documents, files to in TS be deploy and published to the production server. MetaTagger is a software that automates the process of tagging enterprise business content with descriptive metadata to help transform a loosely content to a organise library catalog.
TeamSite can be used for a wide range of applications:
Public web sites
Intranet and internal portals
Extranet portals
Colloborative document and digital asset management
Workflow management