Symantec Workflow 7.1 System Requirements
| Article:HOWTO66292 | | | Created: 2012-02-04 | | | Updated: 2012-02-04 | | | Article URL http://www.symantec.com/docs/HOWTO66292 |
Notice the date of this article. You should also check the Symantec Workflow 7.1 Release Notes for updated information, at http://www.symantec.com/docs/DOC4796.
Refer to the following guides for additional information:
- Symantec Management Platform (SMP) Installation Guide:http://www.symantec.com/docs/DOC4798
- ITMS Implementation Guide: http://www.symantec.com/docs/DOC4827
The information in this article assumes that you are using Symantec Management Platform in conjunction with Workflow, although most features of Workflow can be run independently of the platform.
The information in this article reflects the recommended configuration when the Workflow system’s utilization load is not well defined. Utilization load is proportionate to the frequency of process execution multiplied by the number of components in the process. Processing speed is affected by the number of active simultaneous processes and by the length of time it takes an external system to respond to the Workflow system.
In nearly all scenarios, it is appropriate to use the following recommendations:
- One or more developer workstations
- One lab environment specification
- One medium environment specification
Customers who plan to leverage Symantec Management Platform for additional purposes (such as client management, server management, or asset management) should observe the following recommendations:
- Increase the hardware capacity of the platform server to reflect additional SQL load requirements.
- Install Workflow Server on a separate production server.
Symantec Workflow recommendations are shown below in the following categories:
- Developer workstation
- Small or lab environment
- Medium environment
- Large environment
- Advanced setup
In the remainder of this article, items that are marked with an asterisk (*) are automatically installed by the Symantec Installation Manager (SIM) when the platform is selected within SIM. Required items are underlined.
 |
2 GHZ CPU 3 GB memory 1 GB available disk space |
|
Windows XP SP3 x86 or x64 |
|
| Workflow Designer (Install after platform + Symantec Workflow) |
|
| Access to a test SMTP server |
 |
All in one box |
|
Windows Server 2008 R2 (SP1 optional) (64-bit) |
|
|
SQL 2005 SP4 or SQL 2008 R2 SP1 |
|
|
Symantec Management Platform 7.1 SP2 |
|
| Access to a test SMTP server |
 |
Platform + SQL box |
|
Windows Server 2008 R2 (SP1 optional) (64-bit) |
|
|
SQL 2005 SP4 or SQL 2008 R2 SP1 |
|
|
Symantec Management Platform 7.1 SP2 |
|
| * Symantec Administrator SDK v7.1.83 * Symantec NS Web Services v7.0.60 |
|
|
Workflow Server box |
|
|
Windows Server 2003 SP2 R2 x64 |
|
|
Workflow Server |
|
| Access to a production SMTP server |
 |
Platform box |
|
Windows Server 2008 R2 (SP1 optional) (64-bit) |
|
|
Symantec Management Platform 7.1 SP2 |
|
|
* Symantec Administrator SDK v7.1.83 |
|
|
SQL box |
|
|
Windows Server 2003 SP2 R2 x64 or |
|
|
SQL 2008 R2 SP1 Standard Edition |
|
|
Workflow Server box |
|
|
Windows Server 2008 R2 (64-bit) |
|
|
Workflow Server |
|
| Access to a production SMTP server |
 |
Platform box |
|
Clustered SQL servers (2 boxes) |
|
|
Windows Server 2003 SP2 R2 x64 or |
|
|
SQL 2008 R2 SP1 Standard Edition Note: Some customers utilize SQL Reporting Services within their Workflow processes. SQL Reporting is not compatible with clustering, but it can be load balanced with additional hardware. |
|
|
Workflow Server boxes 4 to 8x CPU |
|
|
Process load can be distributed by deploying different Workflow projects to different Workflow Servers. |
|
| Windows Server 2008 R2 (64-bit) | |
| Availability and process load can be improved by deploying the same Workflow projects to multiple Workflow Servers and placing them behind a load-balancing switch. | |
|
Microsoft .NET Framework 3.5 SP1 |
|
|
Workflow Server |
|
| Portal availability can be improved by configuring multiple Workflow Process Manager (WPM) servers to share a common SQL (ProcessManager) database. All WPM servers are then placed behind a load-balancing switch. |
|
|
Article URL http://www.symantec.com/docs/HOWTO66292
Terms of use for this information are found in Legal Notices
Thank you.