Cisco Cisco Process Orchestrator 3.0 Guida Informativa
Microsoft® SQL Server 2012
Y
Y
—
—
—
—
—
—
—
Microsoft® SQL Server 2008 R2
Y
Y
Y
Y
Y
Y
Y
Y
Y
Microsoft® SQL Server 2008
Y
Y
Y
Y
Y
Y
Y
Y
Y
Microsoft® SQL Server 2005
Standard or Enterprise Edition
—
—
Y
Y
Y
Y
Y
Y
Y
Oracle® Database Enterprise Edition 11g R2
(requires Oracle Partitioning)
(requires Oracle Partitioning)
Y
Y
Y
Y
Y
Y
Y
Y
Y
Oracle® Database Enterprise Edition 11g R2
Real Application Clusters (RAC). (requires
Oracle Partitioning)
Real Application Clusters (RAC). (requires
Oracle Partitioning)
Y
Y
Y
Y
Y
Y
Y
Y
Y
Microsoft® SQL Server 2012
Y
Y
—
—
—
—
—
—
—
Microsoft® SQL Server 2008 R2
Y
Y
Y
Y
Y
Y
Y
Y
Y
Microsoft® SQL Server 2008
Y
Y
Y
Y
Y
Y
Y
Y
Y
Microsoft® SQL Server 2005
Standard or Enterprise Edition
—
—
Y
Y
Y
Y
Y
Y
Y
Oracle® Database Enterprise Edition 11g R2
Y
Y
Y
Y
Y
Y
Y
Y
Y
Oracle® Database Enterprise Edition 11g R2
Real Application Clusters (RAC)
Real Application Clusters (RAC)
Y
Y
—
—
—
—
—
—
—
3.1 SP2 and SP3
Y
Y
Y
Y
Y
Y
Y
Y
—
3.1 SP1
—
—
—
—
—
—
—
—
Y
2012
Y
Y
—
—
—
—
—
—
—
2008 R2
Y
Y
Y
Y
Y
Y
Y
Y
Y
2008
Y
Y
Y
Y
Y
Y
Y
Y
Y
2005
—
—
Y
Y
Y
Y
Y
Y
Y
Both 32‐bit and 64‐bit are supported
Specific versions of operating systems are
limited to the versions Oracle supports.
It is strongly recommended that the database
settings should be case‐insensitive. See the
Cisco Process Orchestrator Installation and
Administration Guide .
Oracle DB Standard Edition is not supported
Specific versions of operating systems are
limited to the versions Oracle supports.
It is strongly recommended that the database
settings should be case‐insensitive. See the
Cisco Process Orchestrator Installation and
Administration Guide .
Oracle DB Standard Edition is not supported
Soft
Soft
Upstream
Upstream
Reporting is an optional Process Orchestrator element. Process Orchestrator automation will work without them. If there
is an outage in reporting, only the reporting function will be impacted, and Process Orchestrator overall will continue to
operate.
is an outage in reporting, only the reporting function will be impacted, and Process Orchestrator overall will continue to
operate.
Reporting is an optional Process Orchestrator element. Process Orchestrator automation will work without them. If there
is an outage in reporting, only the reporting function will be impacted, and Process Orchestrator overall will continue to
operate.
is an outage in reporting, only the reporting function will be impacted, and Process Orchestrator overall will continue to
operate.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
www.cisco.com/go/trademarks. Third‐party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (1110R)
www.cisco.com/go/trademarks. Third‐party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (1110R)
Business Objects
Enterprise XI
Enterprise XI
Only one reporting tools is required.
Microsoft® SQL Server
Reporting Services
Reporting Services
Upstream
Reporting Tools
(Both 32‐bit and 64‐bit are supported) Specific
versions of operating systems are limited to the
Oracle versions that are supported on them.
It is strongly recommended that the database
settings should be case‐insensitive. See
Modifying Oracle DB Instance Case‐Sensitive
Settings in the Cisco Process Orchestrator
Installation and Administration Guide .
Oracle DB Standard Edition is not supported.
versions of operating systems are limited to the
Oracle versions that are supported on them.
It is strongly recommended that the database
settings should be case‐insensitive. See
Modifying Oracle DB Instance Case‐Sensitive
Settings in the Cisco Process Orchestrator
Installation and Administration Guide .
Oracle DB Standard Edition is not supported.
Soft
Standard or Enterprise Edition (Including
Failover Clusters)
Failover Clusters)
Hard
An outage of this database will imply that reporting data cannot be written. To improve performance, reporting data is
held in queues and is occasionally written to the database in bulk rather than an item at a time. Should the Reporting
Database fail, data will be queued to be written when database service is restored. Should the reporting database be
down for an extended period of time, the queue will fill and data will be lost. Regardless, Process Orchestrator
automation will continue to function so that only reporting functionality is impacted.
held in queues and is occasionally written to the database in bulk rather than an item at a time. Should the Reporting
Database fail, data will be queued to be written when database service is restored. Should the reporting database be
down for an extended period of time, the queue will fill and data will be lost. Regardless, Process Orchestrator
automation will continue to function so that only reporting functionality is impacted.
During a friendly shutdown, the Process Orchestrator service flushes the queue. In the event of a Process Orchestrator
failure, the data in the queue will be present on restart and will be sent whenever the Process Orchestrator Server starts
up; no data will be lost. However, if an unexpected failure occurs for which there is a need to reinstall the Process
Orchestrator server on a different computer or restore the computer hosting the Process Orchestrator server from a
backup, reporting data from these queues is lost.
failure, the data in the queue will be present on restart and will be sent whenever the Process Orchestrator Server starts
up; no data will be lost. However, if an unexpected failure occurs for which there is a need to reinstall the Process
Orchestrator server on a different computer or restore the computer hosting the Process Orchestrator server from a
backup, reporting data from these queues is lost.
The reporting database can use vendor‐standard high‐availability configurations such as Oracle RAC or Microsoft SQL
Server Failover Clusters. These options are recommended for highly available environments.
Server Failover Clusters. These options are recommended for highly available environments.
Reporting Database
Databases
Upstream
Standard or Enterprise Edition (Including
Failover Clusters)
Failover Clusters)
Processes Database
Process Orchestrator Compatibility Matrix
© 2012 Cisco Systems, Inc. All rights reserved.
2