Symantec ALTIRIS WORKFLOW 7.0 - INSTALLATION AND CONFIGURATION GUIDE... User manual

Altiris™Workflow from
Symantec Installation and
Configuration Guide
Version 7.0

Workflow 7.0 Installation and Configuration Guide
Legal Notice
Copyright © 2009 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo are trademarks or registered trademarks of Symantec
Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks
of their respective owners.
This Symantec product may contain third party software for which Symantec is required
to provide attribution to the third party (“Third Party Programs”). Some of the Third Party
Programs are available under open source or free software licenses. The License Agreement
accompanying the Software does not alter any rights or obligations you may have under
those open source or free software licenses. Please see the Third Party Legal Notice Appendix
to this Documentation or TPIP ReadMe File accompanying this Symantec product for more
information on the Third Party Programs.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com

Technical Support
Symantec Technical Support maintains support centers globally. Technical
Support’s primary role is to respond to specific queries about product features
and functionality. The Technical Support group also creates content for our online
Knowledge Base. The Technical Support group works collaboratively with the
other functional areas within Symantec to answer your questions in a timely
fashion. For example, the Technical Support group works with Product Engineering
and Symantec Security Response to provide alerting services and virus definition
updates.
Symantec’s maintenance offerings include the following:
■A range of support options that give you the flexibility to select the right
amount of service for any size organization
■Telephone and Web-based support that provides rapid response and
up-to-the-minute information
■Upgrade assurance that delivers automatic software upgrade protection
■Global support that is available 24 hours a day, 7 days a week
■Advanced features, including Account Management Services
For information about Symantec’s Maintenance Programs, you can visit our Web
site at the following URL:
www.symantec.com/techsupp/
Contacting Technical Support
Customers with a current maintenance agreement may access Technical Support
information at the following URL:
www.symantec.com/techsupp/
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
■Product release level
■Hardware information
■Available memory, disk space, and NIC information
■Operating system

■Version and patch level
■Network topology
■Router, gateway, and IP address information
■Problem description:
■Error messages and log files
■Troubleshooting that was performed before contacting Symantec
■Recent software configuration changes and network changes
Licensing and registration
If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
www.symantec.com/techsupp/
Customer service
Customer service information is available at the following URL:
www.symantec.com/techsupp/
Customer Service is available to assist with the following types of issues:
■Questions regarding product licensing or serialization
■Product registration updates, such as address or name changes
■General product information (features, language availability, local dealers)
■Latest information about product updates and upgrades
■Information about upgrade assurance and maintenance contracts
■Information about the Symantec Buying Programs
■Advice about Symantec's technical support options
■Nontechnical presales questions
■Issues that are related to CD-ROMs or manuals

Maintenance agreement resources
If you want to contact Symantec regarding an existing maintenance agreement,
please contact the maintenance agreement administration team for your region
as follows:
[email protected]Asia-Pacific and Japan
[email protected]Europe, Middle-East, and Africa
[email protected]North America and Latin America
Additional enterprise services
Symantec offers a comprehensive set of services that allow you to maximize your
investment in Symantec products and to develop your knowledge, expertise, and
global insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
These solutions provide early warning of cyber attacks, comprehensive threat
analysis, and countermeasures to prevent attacks before they occur.
Symantec Early Warning Solutions
These services remove the burden of managing and monitoring security devices
and events, ensuring rapid response to real threats.
Managed Security Services
Symantec Consulting Services provide on-site technical expertise from
Symantec and its trusted partners. Symantec Consulting Services offer a variety
of prepackaged and customizable options that include assessment, design,
implementation, monitoring, and management capabilities. Each is focused on
establishing and maintaining the integrity and availability of your IT resources.
Consulting Services
Educational Services provide a full array of technical training, security
education, security certification, and awareness communication programs.
Educational Services
To access more information about Enterprise services, please visit our Web site
at the following URL:
www.symantec.com
Select your country or language from the site index.

Chapter 1 About Workflow 7.0 and installation ................................ 9
About Workflow 7.0 ....................................................................... 9
Prerequisites for Workflow 7.0 ....................................................... 11
Operating system compatibility ...................................................... 12
Where to get more information about Symantec Workflow 7.0 ............. 12
About installing Workflow 7.0 ........................................................ 13
Installing Workflow for the first time ........................................ 14
Upgrading from Workflow 6.5 .................................................. 15
Chapter 2 Installing Workflow 7.0 ...................................................... 21
Installing Workflow Solution through Symantec Installation
Manager ............................................................................... 21
Downloading the Workflow installer through the Symantec
Management Console ............................................................. 22
Possible installation configurations ................................................. 23
Installing with separate background processing ........................... 24
Installing Workflow Server ............................................................ 27
Installing Workflow Designer ......................................................... 29
Installing Process Manager ............................................................ 31
Configuring Workflow 7.0 .............................................................. 34
Migrating links from Notification Server 6.5 to Symantec
Management Platform 7.0 ................................................. 35
Licensing Workflow Server, Workflow Designer, and Process
Manager ......................................................................... 37
Technical Support ............................................................................................... 4
Index .................................................................................................................... 41
Contents

Contents8

About Workflow 7.0 and
installation
This chapter includes the following topics:
■About Workflow 7.0
■Prerequisites for Workflow 7.0
■Operating system compatibility
■Where to get more information about Symantec Workflow 7.0
■About installing Workflow 7.0
About Workflow 7.0
Symantec Workflow 7.0 provides the Workflow 7.0 capability of advanced logic
and workflow to Symantec Management Console and the Symantec solutions.
For more information on Workflow 7.0, see the Workflow 7.0 User's Guide.
See “Where to get more information about Symantec Workflow 7.0”on page 12.
Workflow 7.0 is not a single piece of software. It has five main pieces—Workflow
Solution, Workflow Designer, Workflow Server, client tools, and Process Manager.
The following table describes each piece:
1
Chapter

Table 1-1 Pieces of Workflow 7.0
DescriptionSoftware piece
Workflow Solution is the piece of Workflow 7.0 that is
installed as an integrated solution on the Symantec
Management Platform and is accessible through the
Symantec Management Console. It facilitates licensing and
reports with the platform. It also integrates Workflow
Designer and Workflow Server with Symantec Management
Platform. This integration lets Workflow interact with other
solutions, such as creating tasks that other solutions can
use. The solution piece also lets you distribute components
through the Symantec Management Console.
Workflow Solution
Workflow Designer is the tool used to design processes. It
contains components that you can arrange into processes
and then publish to a Workflow Server. It should be installed
on computers other than the Symantec Management
Platform host. Installation of Workflow Designer is not
required. Workflow Designer is dependent on Workflow
Server to be able to publish workflows.
For more information about Workflow Designer, see the
Workflow 7.0 User's Guide.
Workflow Designer
Workflow Server runs and manages published workflow
projects. It should be installed on any computer to which
you want to publish: a designated server or your local
computer. It is installed automatically when you install
Workflow 7.0. Typically, you should designate a server as
the production Workflow server and install Workflow Server
on that server so there is a central location for all
production-ready workflows.
For more information, see the Workflow Solution User's
Guide.
Workflow Server
Process Manager is a Web portal used to manage published
processes that include human interaction. It should be
installed on a central Process Manager server. Installation
of Process Manager is not required. For a development and
testing environment, install Process Manager on a design
computer. For a production environment, install it on a
central server.
For more information, see the Workflow 7.0 User's Guide.
Process Manager
About Workflow 7.0 and installation
About Workflow 7.0
10

Table 1-1 Pieces of Workflow 7.0 (continued)
DescriptionSoftware piece
Workflow client tools are a tool set that supports Workflow
7.0.
The tools are as follows:
■Business TimeSpan Editor
■Composer Theme Editor
■Configuration and Logging Tool
■Local Machine Info Editor
■Messaging Console
■Notification Server Credentials Tool
■Profiler Tool, Scheduler Tool
■Server Extensions Configurator
■Task Tray Tool
■Tool Preferences Editor
Client tools
Prerequisites for Workflow 7.0
Workflow 7.0 includes a number of pieces that can be installed on the same or
different computers. If you install all of them on one computer, that computer
must meet all the prerequisites listed in the table below. If you install only one
piece listed below, the host computer must meet the prerequisites for that piece.
Table 1-2 Workflow prerequisites
PrerequisitesWorkflow piece
Here are the prerequisites for Workflow Solution:
■Symantec Management Platform 7.0 SP1, HotFix
1 or greater
■Microsoft .NET Framework 3.5
■Symantec Management Platform Webservice 7.0
Workflow Solution
Workflow Server has one prerequisite:
■Microsoft IIS 5.x or 6.x
Workflow Server
11About Workflow 7.0 and installation
Prerequisites for Workflow 7.0

Table 1-2 Workflow prerequisites (continued)
PrerequisitesWorkflow piece
Here are the prerequisites for Workflow Designer:
■Microsoft .NET Framework 3.5
■Workflow Server—Gets installed automatically
during Workflow Designer installation.
■Optional: Microsoft IIS 5.x or 6.x —An internal Web
server is delivered with Workflow Designer that
can be used with the debugger.
Workflow Designer
Here are the prerequisites for Process Manager:
■Microsoft .NET Framework 3.5
■Microsoft IIS 5.x or 6.x
■Microsoft SQL Server 2005 or SQL Express
■Workflow Server - Gets installed automatically
during Workflow Designer installation.
Process Manager
Operating system compatibility
Workflow 7.0 is compatible with several operating systems. Although you can
run Workflow Designer, Server, Process Manager, and Solution on many operating
systems, run them only on the operating systems listed below in a production
environment.
Table 1-3 Operating system compatibility
SolutionProcess ManagerServerDesigner
Workflow Solution supports
all operating systems
supported by Symantec
Management Console.
■Windows Server 2003
R2 SP2 32-bit
■Windows Server 2003
R2 SP2 64-bit
■Windows Server 2003
R2 SP2 32-bit
■Windows Server 2003
R2 SP2 64-bit
■Windows XP SP3 32-bit
■Windows Vista SP2
32-bit
Where to get more information about Symantec
Workflow 7.0
For more information, refer to the information sources in the following table.
About Workflow 7.0 and installation
Operating system compatibility
12

Table 1-4 Where to get more information
LocationInformation source
www.workflowswat.comWorkflow SWAT
https://.kb.altiris.comSymantec Management Platform 7.0 Release
Notes
https://.kb.altiris.comAltiris 7.0 Planning and Implementation
Guide
https://.kb.altiris.comInstalling the Symantec Management
Platform 7.0 products
https://.kb.altiris.comKnowledge Base
http://www.symantec.com/connect/Symantec Connect
About installing Workflow 7.0
Depending on whether you are installing Workflow for the first time, the
installation process has three main steps: installing through Symantec Installation
Manager, downloading the installer through Symantec Management Console, and
running the installer.
See “Installing Workflow for the first time”on page 14.
Workflow 7.0 has only one installer for numerous pieces. While installing you
can click which pieces of Workflow 7.0 you want to install.
See “About Workflow 7.0”on page 9.
Although you have a lot of flexibility with how you install Workflow 7.0, every
installation must conform to the following parameters:
■Workflow Solution must be installed in Symantec Installation Manager.
■Workflow Server must be installed on every computer running Workflow 7.0
(this is done automatically with every Workflow install).
Although Workflow Server always gets installed with Workflow Designer or
Process Manager, you should designate a server as the production Workflow
server and install Workflow Server on that server. This creates one central location
for all production-ready workflows.
You do not have to install either Workflow Designer or Process Manager when
you install Workflow Server. For a typical production environment, install Process
Manager only on a central server, and install Workflow Designer only on design
13About Workflow 7.0 and installation
About installing Workflow 7.0

computers. For a development and testing environment, install these two pieces
of Workflow on a design computer.
Installing Workflow for the first time
Refer to the following steps if you are installing Workflow for the first time. If
you are upgrading from Workflow 6.5, see the following section:
See “Upgrading from Workflow 6.5”on page 15.
Installing Workflow has three main steps: installing through Symantec Installation
Manager, downloading the installer through Symantec Management Console, and
running the installer.
Table 1-5 Process for installing Workflow 7.0
DescriptionActionStep
Installing Workflow through the
Symantec Installation Manager makes
Workflow available in Symantec
Management Console. Once you have
installed Workflow through the
Symantec Installation Manager you can
download the installer through the
Symantec Management Console.
See “Installing Workflow Solution
through Symantec Installation
Manager”on page 21.
Install Workflow through the
Symantec Installation Manager
Step 1
A link to the Workflow installer is
available in Symantec Management
Console. Clicking this link downloads
the Workflow installer to your local
computer.
See “Downloading the Workflow
installer through the Symantec
Management Console ”on page 22.
Download the Workflow installer
through Symantec Management
Console
Step 2
About Workflow 7.0 and installation
About installing Workflow 7.0
14

Table 1-5 Process for installing Workflow 7.0 (continued)
DescriptionActionStep
Run the Workflow installer to install
Workflow on your local computer.
There is only one installer for all the
pieces of Workflow.
See “Installing Workflow Server”
on page 27.
See “Installing Workflow Designer”
on page 29.
Install WorkflowStep 3
Upgrading from Workflow 6.5
Refer to the following steps if you are upgrading Workflow 6.5 to Workflow 7.0.
If you are installing Workflow for the first time, see the following section:
See “Installing Workflow for the first time”on page 14.
You can disrupt currently-running Workflow 6.5 processes by installing Workflow
7.0 if you do not keep the same persistence settings. Ideally, you should use the
same persistence settings for Workflow 7.0 that you used for Workflow 6.5. During
installation you can set the persistence setting for Workflow 7.0. If the persistence
setting in Workflow 6.5 is not supported in Workflow 7.0, version your projects
so you do not overwrite the currently-running processes.
See “Versioning a process”on page 19.
If you do not know what persistence settings your current version of Workflow
is using, refer to the following section:
See “Determining a project's persistence setting”on page 17.
Symantec recommends using the following steps to upgrade your
currently-running processes from Workflow 6.5 to Workflow 7.0:
Table 1-6 Process for upgrading currently-running processes
DescriptionActionStep
Create packages for all your projects, and store these packages
on a safe directory.
For more information on creating a project package, see the
Workflow 7.0 User's Guide.
www.alitis.com/support/documentation.aspx
Backup your projectsStep 1
15About Workflow 7.0 and installation
About installing Workflow 7.0

Table 1-6 Process for upgrading currently-running processes (continued)
DescriptionActionStep
Create a backup of your Ensemble database. Store the database
backup on a safe directory.
Backup the Ensemble databaseStep 2
Install Workflow 7.0 on a testing computer.
See “Installing Workflow for the first time”on page 14.
If you already have a testing computer setup up with Workflow
7.0, you do not need to set up another one.
While you are installing on your testing computer, make sure
you do the following:
■Use the same Workflow persistence settings as your Workflow
6.5 configuration.
If you do not know what persistence setting you are using in
Workflow 6.5, see the following section:
See “Determining a project's persistence setting”on page 17.
If you are using a persistence setting that is not supported by
Workflow 7.0, see the following section:
See “Versioning a process”on page 19.
■Set Workflow 7.0 to have access to a Symantec Management
Platform 7.0 server (NS 7).
Install Workflow 7.0 on a testing
computer
Step 3
Open each project and make the necessary changes for it to be
compatible with Workflow 7.0 and Symantec Management
Platform 7.0. Change any old Notification Server components
and settings.
If you can use the same persistence setting for your Workflow
7.0 projects as you used for your Workflow 6.5 projects.
See “Determining a project's persistence setting”on page 17.
Revise your projectsStep 4
Publish the revised projects to the Workflow 7.0 computer. For
more information on publishing projects, see the Workflow 7.0
User's Guide.
Publish revised projects to
Workflow 7.0 computer
Step 5
Conduct thorough tests to ensure that your projects are working
properly in a Workflow 7.0 and Symantec Management Platform
7.0 environment. If you encounter any problems, fix the project
and republish.
Test revised projectsStep 6
About Workflow 7.0 and installation
About installing Workflow 7.0
16

Table 1-6 Process for upgrading currently-running processes (continued)
DescriptionActionStep
Install Workflow 7.0 on your production computer. When you
install, make sure you use the same persistence setting as you
6.5 configuration.
See “Installing Workflow Server”on page 27.
See “Installing Workflow Designer”on page 29.
Install Workflow 7.0 on
production computer
Step 7
Publish all of your revised projects to the Workflow 7.0
production computer. For more information on publishing
projects, see the Workflow 7.0 User's Guide.
Publish revised projects to
production computer
Step 8
Determining a project's persistence setting
Persistence refers to how a running process is stored in memory to improve the
performance of Workflow 7.0. Persistence is set at the project level, but most
projects use the default setting that was set when Workflow was installed (almost
always file-based). For Workflow 6.5 projects, the persistence setting is configured
under the project's Publishing data tab in the WorkQueueServiceName property.
The best way to determine a project's persistence setting is to open the project
and look at its Work Queue Service Name property under the Publishing data
tab.
For more information on data tabs, see the Workflow 7.0 User's Guide.
The following table describes persistence options:
Table 1-7 Persistence options
DescriptionPersistence option
Uses Ensemble SQL database settings. The workflow
project uses the Ensemble database for persistence.
There is no Workflow 7.0 equivalent of this setting.
LogicBase.Components.Ensemble.WSWorkQueue
17About Workflow 7.0 and installation
About installing Workflow 7.0

Table 1-7 Persistence options (continued)
DescriptionPersistence option
Uses Exchange for persistence. This is the most common
persistence setting. This setting uses either file-based or
SQL-based persistence over Exchange.
For information on determining whether this setting uses
file-based or SQL-based persistence, see the following
section:
See “To determine the default persistence setting in the
Configuration and Logging Tool”on page 18.
The Workflow 7.0 equivalent of this is Exchange
(file-based) or SQL-based persistence. You can set this
when you install Workflow 7.0.
LogicBase.Components.Default.ExchangeAdapters.
LogicBaseExchangeWorkQueue
Uses direct file-based persistence.
There is no Workflow 7.0 equivalent of this setting.
LogicBase.Core.Workflow.FileSystemAdapters.
FileSystemWorkQueue
Uses internal Workflow memory.
There is no Workflow 7.0 equivalent of this setting.
LogicBase.Core.Models.Workflow.InMemoryWorkQueue
Uses direct SQL-based persistence.
There is no Workflow 7.0 equivalent of this setting.
LogicBase.Core.Workflow.SQLServerAdapters.
SQLServerWorkQueue
Your projects are probably set to use
LogicBase.Components.Default.ExchangeAdapters.LogicBaseExchangeWorkQueue.
If this is the case, you can determine whether the exchange is set to file-based or
SQL-based persistence in the Configuration and Logging Tool.
See “To determine the default persistence setting in the Configuration and Logging
Tool”on page 18.
If any of your projects use a persistence setting other than
LogicBase.Components.Default.ExchangeAdapters.LogicBaseExchangeWorkQueue,
you should version them to avoid losing process data.
See “Versioning a process”on page 19.
To determine the default persistence setting in the Configuration and Logging Tool
1Open the Configuration and Logging Tool.
Start >Programs >Altiris >Workflow Designer >Tools >Configuration
and Logging Tool.
2Click the Exchange Configuration tab.
About Workflow 7.0 and installation
About installing Workflow 7.0
18

3In the left pane, click local.config : LBQ_Local_Defaults.
4In the right pane, double-click local.workflow-.
If the Deliver To Queue property is set to LBME.Workflow (with a prefix),
the default persistence setting is file-based.
If the Deliver To Queue property is set to workflowsqlexchange (with a
prefix), the default persistence setting is SQL-based.
Versioning a process
If you have a Workflow 6.5 project that uses a persistence setting that is not
supported in Workflow 7.0, version the project so you do not lose any process
data (such as tasks).Process versioning is handled in IIS. When you publish a
workflow project, a new virtual directory is created in IIS, unless one of the same
name already exists. If an identical one exists, the new process overwrites the
process already published there. A new virtual directory must be created to contain
the updated process while the old process is allowed to run in its virtual directory.
The following steps assume that you have a currently running process you are
replacing with an updated version.
Versioning works only with the “Publish Application to Server”publishing option.
Because the other publishing options do not let you set the virtual directory name,
you cannot use versioning with them.
To version a process
1In Workflow Designer, when you are ready to publish your updated process,
click File >Publish Project >Publish Application to Server.
2In the Virtual Directory field, add the updated version number to the end of
the name of the virtual directory.
For example, if the old process is in a virtual directory called “PurchaseOrder,”
call the new virtual directory “PurchaseOrder2.0.”If you publish without
changing the name of the virtual directory, your new process will completely
replace the old one and break any of its current instances.
3Complete the publishing process as normal.
4Repoint the invocation links to the virtual directory of the updated process.
In other words, whatever invoked the old process (such as Process Manager
service catalog item or external link) must be repointed to the new virtual
directory that contains the process.
5After the old process has finished all activity, delete its virtual directory.
19About Workflow 7.0 and installation
About installing Workflow 7.0

About Workflow 7.0 and installation
About installing Workflow 7.0
20