ASE On VMWare Vshpere
ASE On VMWare Vshpere
on VMware vSphere®
Essential Deployment Tips
Bob Goldsand
Partner Architect,
Global Strategic Alliances VMware
Chris Brown
Solution Advisor Expert SAP
White paper
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
With the trend towards large logical CPU and high memory
2 Introduction
systems at cost-effective prices, more and more SAP
3 VMware vSphere
4 VMware vMotion and Storage vMotion customers are looking to deploy their production databases
9 Virtual Machine Guest Operating System VMware, in cooperation with SAP, conducted several
10 CPU Considerations extensive tests to compare the performance of SAP®
12 Resource Management Sybase® Adaptive Server® Enterprise (SAP Sybase ASE),
13 Networking
version 15.7 running on VMware vSphere 5.0®, versus
14 Storage
directly on native hardware. The results showed that
15 Multiple Virtual SCSI Controllers
throughput on the high-transaction OLTP database
15 Sybase Direct I/O Parameter
SAP Sybase ASE, running in a virtual machine,
16 EMC VMAX FAST VP
often matched that of an identical physical system.
16 FAST VP Performance Measurement and Data Movement
16 FASTVP and VMware Storage DRS Once the performance myths are dispelled, the next
17 Storage DRS Manual Mode and I/O Metric Inclusion questions are typically centered around support, such
18 Deployment Tips/Guidelines Summary
as “Is the database supported once it is virtualized?”
19 Conclusion and “Do I have to reproduce issues on physical hardware?”
20 Appendix A: Test Results − ASE Native versus vSphere SAP fully supports and certifies SAP Sybase ASE running
21 Resources
on VMware vSphere, and customers will not be required
22 Acknowledgements
to reproduce issues on native hardware.
2
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
for architects and engineers who are responsible for Figure 1. VMware vSphere
virtualization platform.
VMware vSphere
VMware vSphere is an optimal virtualization platform and enabler
for cloud computing architectures. vSphere enables IT to meet
service-level agreements (SLAs) for the most demanding business-
critical applications at the lowest total cost of ownership (TCO).
VMware vSphere delivers control over all IT resources with the
highest efficiency and choice in the industry, as shown in Figure 1.
3
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
• Automation. VMware automated load balancing takes advantage In addition, VMware vSphere 5.1 enables a virtual machine to
of vMotion and Storage vMotion to migrate virtual machines change its datastore and host simultaneously, even when the hosts
among a set of VMware® ESXi™ hosts. VMware vSphere® do not have a shared storage environment. It allows virtual machine
Distributed Resource Scheduler (DRS) and VMware vSphere
™ ®
migration between clusters in a larger datacenter that might not
Storage DRS™ enable automatic resource relocation and have a common set of datastores between them. vSphere also
optimization decisions for virtual machines and storage. allows virtual machine migration in small environments without
• Availability. High availability can be enabled to reduce requiring access to expensive, shared storage equipment, as
unplanned downtime and support higher service levels for shown below.
applications. VMware vSphere® High Availability (HA) ensures Figure 2. VMware vMotion and Storage vMotion
that, in the event of an unplanned hardware failure, the
affected virtual machines are automatically restarted on
another host in a VMware cluster.
4
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
5
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
VMware Storage vMotion • Migrates virtual machines running any supported operating
Storage vMotion enables the live migration of virtual machine system on any supported server hardware based on usage
disk files within and across storage arrays, and it provides for and priority policies for tiered storage.
automated storage management. Storage vMotion relocates • Performs live migration of virtual machine disk files across
disk files of virtual machines running on SAP Sybase ASE,
any Fibre Channel, Internet Small Computer System Interface
while maintaining continuous service availability and complete
(iSCSI), Fibre Channel over Ethernet (FCoE), and Network File
transaction integrity, as shown below.
System (NFS) storage system supported by vSphere.
6
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
Each of these vSphere advanced features is described in the VMware Storage DRS
sections below. Storage DRS aggregates the resources of several datastores into
a single datastore cluster to simplify storage management at scale.
VMware Distributed Resource Scheduler
During virtual machine provisioning, Storage DRS ensures that
DRS is an automated load-balancing technology that takes
virtual machine data is assigned the optimal storage location
advantage of vMotion to migrate virtual machines among a set
initially, and it provides intelligent virtual machine placement
of ESXi™ hosts. DRS continuously monitors utilization across
based on the I/O load and available storage capacity. Storage
vSphere servers and intelligently allocates available resources
DRS performs ongoing load balancing between datastores to
among virtual machines according to business needs. DRS
align the storage resources with predefined rules in order to
dynamically aligns resources with business priorities, balances
meet business objectives, as shown below.
computing capacity, and reduces power consumption in the
datacenter, as shown below. Figure 6. VMware Storage DRS
7
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
• Empowers business units to build and manage virtual architectures. With the advent of cores and threads, the industry
machines within their storage, while giving central IT has reached a point to where it’s no longer a “chip clock-speed”
control over storage resources. race, but a “core and thread” race.
• Is
Suite on Sybase ASE.
the first version of SAP Sybase ASE to be certified with
SAP Business Suite software.
8
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
processes and peripherals, and the compilation of a monolithic later releases. Plan the operating system installation to ensure
kernel to direct the critical compute resources (CPU, memory, that it takes advantage of virtualization and creates an optimized
network, and I/O) to the databases. computing environment.
Each of these items is described in the sections below. Simply disabling the peripheral components in the BIOS does
not guarantee that these components are fully disabled. It is
also important to ensure that the peripheral components are not
Virtual Machine BIOS Settings
re-enabled during the operating system installation. In addition,
Servers with Intel® micro-architecture (Nehalem class) including
do not install office productivity suites, graphics, sound, video
the Intel® Xeon® 5500 series and later CPUs, offers two other
programs, and so on.
power management options: C-states and Intel Turbo Boost.
Leaving C-states enabled can increase memory latency. This
After the installation, disable unnecessary foreground and back-
option is therefore not recommended for low-latency workloads.
ground processes.
9
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
• Change the I/O scheduler: for the virtual machines running on the system do not exceed the
• To ‘noop’ from the default of ‘cfq’. Sybase ASE performs better CPU capacity of the host. It is good practice to under-commit
in a virtual environment. CPU resources on the host. If the host CPU capacity is overloaded,
the performance of the virtual database might degrade.
• Use a 4K page size, since the Linux operating system utilizes
a 4k block size for I/O operations by default.
Do not over commit CPU resources in a production environment.
For additional operating system and version settings and A reasonable ceiling should be 80 percent of consumption; set
dependencies, go to the Sybase ASE release notes at: 90 percent consumption as the limit for generating an alert to
http://www.sybase.com/support/techdocs the virtual infrastructure administrator.
See the “Resources” section later in this paper for more information. A multithreaded application such as Sybase ASE can benefit from
using multiple CPUs. However, for latency-sensitive applications,
do not over commit virtual CPUs compared with the number of
CPU Considerations
physical CPUs. In order to ensure that the physical CPUs are
For the best performance of latency-sensitive applications in
not oversubscribed, limit the total number of vCPUs to the total
guest operating systems, schedule all virtual CPUs (vCPUs) on
number of physical CPUs, minus 1.
the same Non-Uniform Memory Access (NUMA) node. Fit and
allocate all virtual machine memory from the local physical
Configuring virtual Sybase ASE database with excess vCPUs
memory attached to the NUMA node. Set processor and
can impose a small resource requirement on vSphere because
memory affinity as described below.
unused vCPUs continue to consume timer interrupts. vSphere
co-schedules virtual machine vCPUs and attempts to run the
When the processor affinity for vCPUs is scheduled on a specific
vCPUs in parallel to the extent possible. Unused vCPUs impose
NUMA node, set the processor affinity using the vSphere client
scheduling constraints on the vCPU being used and can
as shown in the table below.
degrade its performance.
Processor Affinity Memory Affinity
Workload CPU Optimization - CPU Scheduling
For the virtual machine For the virtual machine
settings, go to : settings, go to : In some use cases, the application owner may want to ensure
•• Resources tab •• Resources tab that the VMkernel does not de-schedule the virtual machine
•• Advanced CPU •• Advanced CPU when the vCPU is idle. In order to determine that there is opti-
•• Check the Scheduling •• Check the NUMA Memory
Affinity box Affinity box mal database performance, add the configuration below:
10
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
• Go to Virtual Machine Settings in vCenter Server, Options tab, • %RDY – The percentage of time the world was ready to run,
Advanced General, Configuration Parameters, and add: but is not scheduled to a core. A world in a run queue is wait-
• monitor_control.halt_desched (with the value of False) ing for the CPU scheduler to let it run on a PCPU. When
%RDY is greater than 10 percent, it could be an indication of
Performance is normally monitored through vSphere vCenter.
resource contention.
However, it is a best practice to periodically collect additional
• %CSTP – The percentage of time the world is stopped from
statistical measures of the host CPU usage. This can be done
running to allow other vCPUs in the virtual machine to catch
through the vSphere Client, or by using esxtop or resxtop. CPU
up, co-deschedule state. If %CSTP is greater than 5 percent,
usage tips are listed below.
this usually means the virtual machine workload is not using
Work with your VMware administrator to interpret esxtop data: VCPUs in a balanced fashion.
• The usage percentage of physical CPUs on the PCPU line can Memory Considerations
be another indication of a possibly overloaded condition. For memory, the best practice is to configure memory reservations
equal to the size of the Sybase ASE max memory setting. Do not
In general, 80 percent usage is a reasonable ceiling in production
over commit memory in a production environment. When con-
environments. 90 percent usage should be used as an alert to
solidating Sybase ASE database instances, vSphere presents
the VMware administrator that the CPUs are approaching an
the opportunity for sharing memory across all virtual machines
overloaded condition that needs to be addressed. However,
that may be running the same operating systems, applications,
decisions concerning usage levels are typically made based
or components. In this case, vSphere uses a proprietary, trans-
on the criticality of the Sybase database being virtualized,
parent page-sharing technique to reclaim memory that allows
regarding the desired load percentage.
databases to run with less memory than physical. Transparent
When using esxtop, three critical statistics to interpret are: page sharing can also be used to over- commit memory, without
any performance degradation.
• %RUN – The percentage of total time the “world”1 is running
on the processor. If %RUN is high, it does not necessarily Hardware-Assisted Memory Virtualization
mean that the virtual machine is resource-constrained. (See Some recent processors include a feature that addresses over-
description of %RDY below.) head due to memory management unit (MMU) virtualization by
providing hardware support to virtualize the MMU. Without
1 Esxtop uses “worlds” and “groups” as the entities to show CPU usage.
A “world” is an ESX VMkernel schedulable entity, similar to a process
or thread in other operating systems. A “group” contains multiple worlds.
11
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
hardware-assisted MMU virtualization, VMware ESXi™ maintains Large (Huge) Memory Pages
“shadow page tables” that directly map guest virtual memory to Large (huge) pages can potentially increase TLB access efficiency,
host physical memory addresses. thereby improving database performance. The use of large pages
can significantly improve the performance of SAP Sybase ASE
These shadow page tables are maintained for use by the processor
databases on vSphere, compared to running the workload using
and are kept consistent with the guest page tables. This allows
small pages. Large-page support is enabled by default in
ordinary memory references to execute without additional overhead,
VMware ESX versions 3.5 and later. The use of Large Pages
since the hardware translation lookaside buffer (TLB) caches
is supported for SAP Sybase ASE version 15.0.3 and greater.
direct guest virtual memory to host physical memory address
translations that are read from the shadow page tables. However, Using HugePages at the operating system level enables SAP
extra work is required to maintain the shadow page tables. Sybase ASE to achieve approximately a 10 percent performance
improvement. It is recommended for any 64-bit production system.
Hardware assistance eliminates software memory virtualization
Furthermore, in larger memory configurations (that is, configurations
overhead. In particular, hardware assistance eliminates the
where SAP Sybase ASE utilizes more than 256 GB of RAM,
overhead required to keep shadow page tables in synchronization
HugePages are required in order for SAP Sybase ASE to boot.
with guest page tables, although the TLB miss latency is significantly
higher. This means that hardware assistance provides workload
benefits depending primarily on the memory virtualization overhead Resource Management
that is caused when using software memory virtualization. When using vSphere advanced workload management features
such as VMware vMotion and VMware DRS, the database is freed
If a workload involves a small amount of page table activity, from the resource limitations of a single host. With vMotion, virtual
such as process creation, mapping the memory, or context machines running SAP Sybase ASE can be moved from one
switches, software virtualization does not cause significant physical vSphere to another to balance the available resources.
overhead. However, workloads having a large amount of page DRS can dynamically allocate and balance computing resources
table activity, such as workloads from a database, are likely to by continually monitoring the utilization of resource pools associated
benefit from hardware assistance. with virtual machines in a VMware cluster.
For these reasons, enable vSphere to Choose the Best Virtual Over-commitment is perfectly acceptable for SAP Sybase ASE in
Machine Monitor based on the CPU and Guest Operating nonproduction environments such as Dev, Test, QA, and others,
System Combination. where predictable and consistent performance is not as critical.
12
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
In addition to supporting Private VLANs (PVLANs), the vDS also # esxcli system module parameters list -m <driver>
13
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
In order to determine if disabling LRO benefits application stack applications and is analogous to provisioning dedicated LUNs
requirements, reload the vmxnet3 driver in the Linux guest: in the physical world. However virtualized customers can use
# modprobe -r vmxnet3
vSphere features such as VMware vSphere® Storage I/O Control,
Storage vMotion, and Storage DRS to prioritize and manage
Add the following line in /etc/modprobe.conf data store workloads. For production SAP Sybase ASE data-
(Linux-version dependent): bases, use dedicated data stores. For nonproduction or less
demanding environments, use consolidated data stores.
options vmxnet3 disable_lro=1
14
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
data and log devices. PVSCSI adapters are high performance SAP Sybase ASE – Direct I/O Parameter
storage adapters that can result in greater throughput and lower In Sybase ASE version 15, the directI/O parameter is used to
CPU utilization. PVSCSI adapters are best suited for high configure Sybase ASE to transfer data directly to disk, bypassing
performance storage environments . 2
the operating system buffer cache. This directI/O parameter acts
similar to a “raw device” in legacy UNIX. In fact, raw partitions
Multiple Virtual SCSI Controllers in Linux are simply direct I/O to a file. Direct I/O performs I/O
VMware recommends creating multiple virtual SCSI controllers in the same manner as raw devices and provides the same
to distribute the I/O associated with database workloads. When performance benefit as raw devices (significantly better than
creating multiple SCSI controllers, map these controllers to the dsync), but it has the ease of use and manageability of file
database or operating system workload profile. Ensure that the system devices.
The primary purpose for using multiple virtual SCSI controllers are mutually exclusive. If a device has dsync set to true, you
is to parallelize the units of work in a database transaction. In cannot set DirectI/O to true for this device. In order to enable
this case, consider the implications when using multiple SCSI DirectI/O for a device, first reset dsync to false.
15
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
VMware Storage DRS In doing so, it combines the advantages of virtual provisioning
Historically, virtual machine storage provisioning has imposed with automatic storage tiering at the sub-LUN level to optimize
operational challenges. Monitoring datastore capacity and I/O performance and cost, while radically simplifying storage
load has proven to be very difficult, and as a result it is often management and increasing storage efficiency. Data movement
neglected. The Storage DRS is a feature introduced in VMware between tiers is based on performance measurement and user-
vSphere 5.0 provides smart virtual machine placement and
®
defined policies, and it is executed automatically and
load balancing mechanisms based on I/O and space capacity. nondisruptively using FAST VP.
It helps decrease the operational effort associated with the
provisioning of virtual machines and the monitoring of the
FAST VP Performance Measurement and Data Movement
storage environment.
With FAST VP, entire devices are promoted or demoted between
tiers based on overall device performance. FAST VP works at the
EMC VMAX FAST VP
sub-LUN level, introducing finer granularities of both performance
EMC® Fully Automated Storage Tiering for Virtual Pools (FAST VP)
measurement and data movement, and can spread the data
challenges the conventional wisdom associated with data
from a single thin device across multiple tiers.
placement and layout. In the past, the database architect
needed to work closely with storage administrators to make sure
The metrics collected at the sub-LUN level for thin devices under
data and log files were placed on the highest-performing drives,
FAST VP control contain measurements that enable FAST VP to
and to closely monitor the tracks on which data was placed.
make separate data movement requests for every 7,680 KB unit
of storage that makes up the thin device. This unit of storage
With FAST VP data placement is not static. FAST VP
is called an extent group and it consists of 10 contiguous thin
provides support for sub-LUN data movement in thin
device extents.
provisioning environments. FAST VP continuously analyzes
devices at the sub-LUN level. This enables it to identify and
relocate the specific parts of a LUN that are the most active and FASTVP and VMware Storage DRS
would benefit the most from being moved to higher-performing Auto-tiering technologies such as FAST VP migrate LUN segments
storage such as EFD. It also identifies the least active parts of (chunks) to different disk types, based on the use pattern. Hot
a LUN and relocates that data to higher-capacity, more cost- (frequently accessed) segments typically move to faster disks,
effective storage such as SATA, without altering performance. whereas cold segments move to slower disks. Depending on the
array type and vendor, there are different policies and thresholds
for these migrations.
16
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
Storage DRS generates migration recommendations that prevent user by automating the selection of an individual datastore, leaving
out-of-space situations or resolve imbalances in performance. In the user with the much smaller scale decision of selecting a
order to prevent hot spots in the datastore cluster and decrease datastore cluster.
the overall latency imbalance, Storage DRS I/O load balancing
By default, Storage DRS is invoked every eight hours and requires
uses device modeling and virtual machine workload modeling:
performance data over more than 16 hours to generate I/O load
• Device modeling helps Storage DRS analyze the performance balancing decisions. FAST VP uses different time cycles to collect
characteristics of the devices backing the datastores. and analyze the workload before moving LUN segments than
Storage DRS. The misalignment of Storage DRS invocation and
• Virtual machine workload modeling analyzes workloads
FAST VP algorithm cycles makes it unpredictable when LUN
of virtual machines running inside the datastore cluster.
segments might be moved, potentially conflicting with Storage
Both device and workload modeling help Storage DRS
DRS recommendations.
assess improvement in I/O latency achieved after a virtual
machine migration. For these reasons, the best practice is either to turn off Storage DRS
or configure Storage DRS in manual mode with I/O Metric disabled.
In order to characterize the datastore, device modeling opens
and reads random blocks. Storage DRS does not detect active
Storage DRS Manual Mode and I/O Metric Inclusion
FAST VP structures and might open blocks located on disks of
In manual mode, Storage DRS makes recommendations when
similar speed, either slow or fast. The datastore can be distributed
the configured thresholds for latency or space utilization have
throughout multiple tiers of disk types, thereby leading to an
been exceeded. It also provides recommendations for placement
incorrect performance characterization. Therefore, the assessment
during the provisioning process of a virtual machine or a virtual
of migrating the workload can be incorrect. This can generate a
disk. In other words, when Storage DRS is set to manual mode,
recommendation to move into an underperforming datastore. It
it monitors the environment and makes recommendations on
also can cause a recommendation to be withheld while there is
destinations for virtual disk migrations. Manual mode is the default
sufficient performance available in other datastores.
setting when configuring a Storage DRS datastore cluster.
By aggregating datastores backed by FAST VP technology into
In order to disable I/O Metric inclusion, go to Advanced Options,
a datastore cluster, Storage DRS provides simplified storage
and uncheck the I/O Metric box in the Storage DRS Runtime
management on the datastore cluster level, rather than on the
Rules configuration window.
datastore level. Initial placement speeds up the process for the
17
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
Operating system •• XFS file system vSphere •• Scale vCPUs for each ASE engine
•• NOOP I/O Scheduler (Example: 4 ASE engines = 4 vCPUs).
•• Hyperthreading enabled – •• Allow vSphere to Choose the Best
workload dependent Virtual Machine Monitor based on
the CPU and Guest Operating
Server BIOS •• Enable: System Combination.
•• Virtualization Technology •• Set memory reservations to equal
•• Turbo mode to the size of the Sybase ASE max
•• Hardware based virtualization support memory setting.
•• Hyperthreading •• Use VMXNET 3 virtual NICs.
•• Wake on LAN (Required for DPS) •• Hardware Assisted Memory Virtualization
- CPU/MMU Virtualization Option =
•• Execute Disable Automatic
(Required for vMotion/DRS
•• Use Virtual Distributed Switch for ease
•• Static high performance/balanced of management and to isolate database,
•• Disable: application, vMotion traffic on separate
•• Node interleaving VLANS.
•• C1E Halt state •• Determine if disabling interrupt
•• Power saving coalescing is optimal.
•• Unused features: Video BIOS •• Determine if disabling LRO is optimal.
Shadowable, Video RAM Cacheable, •• VMFS 5.0:
on-board audio, on-board modem, •• Paravirtualized SCSI driver for
on-board serial ports, on-board SAP Sybase ASE devices.
parallel ports, on-board game port, •• LSI Logic SCSI driver for operating
floppy drive, CD-ROM, USB system – SAP Sybase ASE binaries.
Sybase ASE •• Use large (huge)pages •• Align file system offset – Ex: VNX
(supported for 15.0.3 and greater). 128K offset.
•• Use direct I/O = true for data devices, •• Use dedicated datastores for SAP
set to false for temp devices: Sybase ASE production databases.
•• DSYNC turned off •• Use multiple Virtual SCSI Controllers.
•• AIO Lib loaded •• Leverage New Storage Architectures
•• Tabular Data Stream (TDS) packet (EX: EMC FASY VP).
size 16K (LOBs)
Table 4. Sybase ASE on vSphere: General Guidelines for Settings
•• Page Size 4K typical – 16K for SAP
18
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
Conclusion
As shown by our joint testing, even the most demanding
SAP Sybase ASE database workloads can be virtualized using
VMware vSphere. This is an important data point for customers
who are considering running not only their existing SAP Sybase
ASE database on VMware vSphere, but SAP Business Suite on
SAP Sybase ASE as well. These results were achieved for the
most part out-of-the-box. There is minimal tuning or specialized
configurations needed to run SAP Sybase ASE on VMware
vSphere. This paper is a guideline database administrators
can use to easily virtualize their environments, without having
to learn or relearn their duties.
19
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
Appendix A: Test Results − ASE Native versus vSphere Figure A-2 results show that this configuration exceeded
Appendix A provides summarized, sample validation test results for physical performance.
Sybase ASE running on native physical hardware versus running
on the VMware vSphere virtualization platform. These tests were Figure A-2. 4 SAP-Sybase ASE engine threads 6 vCPUs
run on standard x86 hardware using an OLTP transactional
benchmark. The results below show consistently less than
5 percent transactional overhead as the number of users
are increased.
20
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
21
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
Acknowledgements
The following individuals contributed to the creation of this
technical paper:
22
SAP Sybase Adaptive Server Enterprise on VMware vSphere®
23
© 2013 VMware, Inc. All rights reserved. © 2013 SAP AG. All rights reserved.
This product is protected by U.S. and international SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
copyright and intellectual property laws. VMware StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as
products are covered by one or more patents listed at their respective logos are trademarks or registered trademarks of SAP AG in Germany and
http://www.vmware.com/go/patents. other countries.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
other jurisdictions. All other marks and names mentioned herein may be trademarks of their Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
respective companies. mentioned herein as well as their respective logos are trademarks or registered trademarks of
Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks
of Crossgate AG in Germany and other countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only.
National product specifications may vary.
These materials are subject to change without notice. These materials are provided by
SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying
such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
3/13