BI 4.

0
Services
 Agenda

1. Overview
2. Common Server Properties
3. Management Services
3.1. Server Intelligent Agent
3.2 Web Application Component Server
3.3. Central Management Server
3.4 Event Server
4. Storage Services
4.1. File Repository Servers
4.2. Cache Servers
5. Processing Services
5.1. Scheduling Job Servers
5.2. Viewing Processing Server
6. Server Management

© SAP AG 2009. All rights reserved. / Page 2

 Overview

These concepts will be used throughout this presentation

© SAP AG 2009. All rights reserved. / Page 3

 Agenda

1. Overview
2. Common Server Properties
3. Management Services
3.1. Server Intelligent Agent
3.2 Web Application Component Server
3.3. Central Management Server
3.4 Event Server
4. Storage Services
4.1. File Repository Servers
4.2. Cache Servers
5. Processing Services
5.1. Scheduling Job Servers
5.2. Viewing Processing Server
6. Server Management
7. Solution Manager Monitoring
© SAP AG 2009. All rights reserved. / Page 4
 Common Server Properties

• Server Name – The name of the server (Default

= Name of the node that the server is on, plus the name of the server)

• ID, CUID – The short ID and cluster unique ID of the server. Read-only
(Default = values are auto generated)

• Node - The name of the node where the server is located and, in brackets, the host name and
the account name used to run the node (Default = Specified during installation)

• Description – The server’s description (Default = Name of the server)

• Command Line Parameters – The command-line parameters for the server (Default
= depends on the type of server)

• Request Port - Specifies the port from which the server receives requests. In an environment
with firewalls, you may want to force the server to only listen to requests on ports that are open
on the firewall. If you are specifying a port for the server, ensure that the port is not already
taking by another process. (Default = Blank)

• Auto assign - Specifies whether the server binds to a dynamically allocated port whenever the
server is restarted (Default = TRUE)

© SAP AG 2009. All rights reserved. / Page 5

 Common Server Properties

Auto-start Properties

• Automatically start this server when the Server Intelligence Agent starts - Specifies
whether the server is automatically started when the Server Intelligence Agent (SIA) starts or
restarts (Default = TRUE)

Host Identifier Properties

• Auto assign - Specifies whether the server binds to a network interface that is automatically
assigned (Default = TRUE)

• Hostname - The hostname of the network interface that the server binds to. If a host name is
specified, the server accepts requests on all IP Addresses associated with the host name
(Default = Blank)

• IP Address - The IP Address of the network interface that the server binds to. Both IPv4 and
IPv6 protocols are supported. If an IP Address is specified, the server accepts requests on the IP
Address only (Default = Blank)

© SAP AG 2009. All rights reserved. / Page 6

 Common Server Properties

Configuration Template Properties

• Use Configuration Template – Specifies whether to use a configuration template (Default

= FALSE)

• Restore System Default – Specifies whether to restore the original default settings for this
server (Default = FALSE)

• Set Configuration Template - Specifies whether to use the current service's settings as a
configuration template for all services of the same type. If set to TRUE, all services of the same
type that you have specified to Use Configuration Template are immediately reconfigured to use
the settings of the current service (Default = FALSE)

TraceLog Service Properties

• Log Level – Specifies the minimum severity of messages that you want to be recorded, and
determines how much information is recorded in the server log file. Possible values include:
Unspecified, None, Low, Medium, High (Default = Unspecified)

© SAP AG 2009. All rights reserved. / Page 7

 Agenda

1. Overview
2. Common Server Properties
3. Management Services
3.1. Server Intelligent Agent
3.2 Web Application Component Server
3.3. Central Management Server
3.4 Event Server
4. Storage Services
4.1. File Repository Servers
4.2. Cache Servers
5. Processing Services
5.1. Scheduling Job Servers
5.2. Viewing Processing Server
6. Server Management
7. Solution Manager Monitoring

© SAP AG 2009. All rights reserved. / Page 8

 Server Intelligence Agent (SIA)

 What is the Server Intelligence Agent?

 Server Intelligence is managed via the SIA.
 It is the component that processes the server management tasks.

 SIA is a Management service

 Starts/ stops all other BOE services
 Monitors BOE services and will issue restart on failure
 Allows for the remote management of the BOE servers from CMC
– Adding/ Deleting, Enabling/ Disabling, cloning servers

 Node
 Is a collection of BI platform servers running on the same host and managed by the same
Server Intelligence Agent (SIA)
 A Node only exists within the CMC. (virtual representation of the SIA)
 Has a 1:1 relationship with the SIA
 BOE servers are associated to the Node, not machine
 Ability to move a Node (and all respective servers) to new machine
 Can have multiple SIA/nodes per machine.

© SAP AG 2009. All rights reserved. / Page 9

 Central Management Server (CMS)

 Responsible for authenticating users and groups, and controls access to the
system files
 It is recommended that you do not mix operating systems for Central
Management Server (CMS) processes
 Keeps track of the availability of other BusinessObjects Enterprise services
 All servers communicate with CMS upon startup
 Maintains the BusinessObjects Enterprise system database
 Information about Users and Groups
 Security Levels
 Business Objects Enterprise Content
 Services
 Maintains Audit database
 Tracks information on user actions and system usage

© SAP AG 2009. All rights reserved. / Page 11

 CMS – breakdown of CMC settings

 The third section cannot be edited manually

 The .pid file will show the process ID for the CMS
 This file is altered each time the CMS starts

■ dbinfo file tells CMS which DB to connect to

on startup
■ It also contains the cluster key, which is
used to encrypt all the cryptographic keys in
the CMS repository
■ Dbinfo file is updated when CMS is pointed
to a new DB in CCM
■ Connection string is encrypted but the db
type is in clear text

© SAP AG 2009. All rights reserved. / Page 12

 CMS – breakdown of CMC settings

■ Textbox above can be edited to

add/change command line parameters

■ The SIA properties in CCM is

synced with command line above

■ If CMS doesn’t start, use CCM

to add –trace or other parameters to
CMS properties to troubleshoot

© SAP AG 2009. All rights reserved. / Page 13

 CMS – Command Line Parameters

-threads <num> - Specifies the number of working threads that the CMS initializes and uses.
The value can be between 12 and 150. Default value is 50

-reinitializedb - Cause the CMS to delete the system database and recreate it with only the
default system objects. All existing data in the database is lost when it is recreated.

-receiverpool <num> Specify the number of threads the CMS creates to receive
client requests. A client may be another Business Objects
server, the Report Publishing Wizard, Crystal Reports, or a
custom client application that you have created. Normally you
will not need to increase the default value, unless you create a
custom application with many clients.
Default value = 5

-maxobjectsincache <num> Specify the maximum number of objects that the CMS stores
in its memory cache. Increasing the number of objects reduces
the number of database calls required and greatly improves
CMS performance. However, placing too many objects in
memory may result in the CMS having too little memory
remaining to process queries.
Maximum Value = 100,000

© SAP AG 2009. All rights reserved. / Page 14

 CMS – Breakdown of CMC settings

 Controls request port used by CMS for receiving communication / request from other BI 4.0
servers
 CMS will pick a random request port if not specified
 Only need to set if the random port could be blocked by a firewall
 Hostname can be set to force communication to a certain NIC

© SAP AG 2009. All rights reserved. / Page 15

 CMS – breakdown of CMC settings

© SAP AG 2009. All rights reserved. / Page 16

 CMS - Properties

- Name Server Port Specifies the port on which the CMS listens to initial name service requests
Default value = 6400

- System Database Connections Requested Specifies the number of CMS system

database connections that the CMS attempts to establish. If the server cannot establish
all of the requested database connection, the CMS continues to function but at
a reduced performance, since fewer concurrent requests can be served
simultaneously. The CMS will attempt to establish additional connections, until
the requested number of connection is established. The CMS's Established
System Database Connections metric shows the current number of
established connections.
Default Value: 14

- Auto Reconnect to System Database Specifies whether the CMS automatically attempts to
reestablish a connection to the CMS database in the event of a service
disruption. If this Value is set to FALSE, you are able to check the integrity of
the CMS database before resuming operations; you must restart the CMS to
reestablish the database connection.
Default Value: TRUE
- Single Sign-On Expiry Specifies the time, in seconds, that an SSO connection to a
datasource is valid before expiring. This applies to Windows AD users running
reports that are configured for Windows AD SSO to the datasource.
Default Value: 86400

© SAP AG 2009. All rights reserved. / Page 17

 CMS – Metrics

© SAP AG 2009. All rights reserved. / Page 18

 CMS - Metrics

© SAP AG 2009. All rights reserved. / Page 19

 CMS - Metrics

© SAP AG 2009. All rights reserved. / Page 20

 CMS - Metrics

© SAP AG 2009. All rights reserved. / Page 21

 CMS - Metrics

© SAP AG 2009. All rights reserved. / Page 22

 CMS - Metrics

© SAP AG 2009. All rights reserved. / Page 23

 CMS - Metrics

© SAP AG 2009. All rights reserved. / Page 24

 CMS - Metrics

© SAP AG 2009. All rights reserved. / Page 25

 CMS - Metrics

© SAP AG 2009. All rights reserved. / Page 26

 Event Server

Monitors the system for events, which can act as a trigger for running a report. When you
set up a event trigger, the Event Server monitors the condition and notifies the CMS that
an event has occurred. The CMS can then start any jobs that are set to run on the event.
The Event Server manages file-based events, which occur in the storage tier.

Services: Event Service

Event Poll Interval (seconds) - Specifies how often the server polls for a file that
triggers an event, in seconds. The range of allowed values is 1 to 1200 seconds
(Default = 10)

Cleanup Interval (minutes) - Specifies how often cleanup utility runs, in minutes
(Default = 20)

© SAP AG 2009. All rights reserved. / Page 27

 Agenda

1. Overview
2. Common Server Properties
3. Management Services
3.1. Server Intelligent Agent
3.2 Web Application Component Server
3.3. Central Management Server
3.4 Event Server
4. Storage Services
4.1. File Repository Servers
4.2. Cache Servers
5. Processing Services
5.1. Scheduling Job Servers
5.2. Viewing Processing Server
6. Server Management
7. Solution Manager Monitoring
© SAP AG 2009. All rights reserved. / Page 28
 Storage Services - File Repository Servers

 Responsible for the creation of file system objects, such as exported reports, and
imported files in non-native formats. An Input FRS stores report and program objects
that have been published to the system by administrators or end users. An Output FRS
stores all of the report instances generated by the Job Server.

 Input File Repository Server

 manages all of the report and program objects that have been published to the
system
 It can store the following files:
– .rpt, .car, .exe, .bat, .js, .xls, .doc, .ppt, .rtf, .txt, .pdf, .wid, .rep, or .unv

 Output File Repository Server

 manages all of the report instances generated by the various Job servers
 It can store the following files:
– .rpt, .csv, .xls, .doc, .rtf, .txt, .pdf, .wid, or .rep

© SAP AG 2009. All rights reserved. / Page 29

 Storage Services - File Repository Servers
Command Line Options

 The default path to the servers on Windows is <INSTALLDIR>\SAP BusinessObjects

Enterprise XI 4.0\win64_x64\fileserver.exe
 The default path to the program that provides both servers on Unix is
<INSTALLDIR>/sap_bobj/enterprise_xi40/<platform>/boe_inputfilesd
<INSTALLDIR>/sap_bobj/enterprise_xi40/<platform>/boe_outputfilesd
 Note: Do not use command-line parameters to set Input and Output File Repository
Server properties. Instead, set the parameters in the CMC as server properties.

© SAP AG 2009. All rights reserved. / Page 30

 Input /Output Filestore Service – CMC Settings
(Default Values)

© SAP AG 2009. All rights reserved. / Page 31

 Input /Output Filestore Service – CMC Settings

Maximum Retries for File Access - The number of retries the Input or Output Server will attempt to access
a file. Default value is 1, recommended value is 10

Maximum Idle Time (minutes) - Specifies the length of time that the server waits before it closes inactive
connections. Setting a Value that is too low can cause a user's request to be closed prematurely. Setting a
value that is too high can cause excessive consumption of system resources such as processing time and
disk space. Default value is 10 minutes

Temporary Directory - Specifies the directory where temporary files are created when necessary.

Note: You may encounter performance issues if this directory does not have adequate disk space. To
ensure better performance, it is recommended that the Temporary Directory is located on the same file
system as the File Store Directory.

File Store Directory - This is the storage directory for the environment. Input & Output must use separate
folders. If you have multiple Input / Output servers in a cluster, make sure all Input servers point to one
location. Likewise, all Output Servers should point to another location.
Note: You may encounter performance issues if this directory does not have adequate disk space.

© SAP AG 2009. All rights reserved. / Page 32

 Crystal Reports Cache Server

The Cache Server stores report pages generated by the Processing Server. By storing report pages in
cache, the Processing Server and/or database server does not need to be accessed each time the report
is requested. The Cache Server is used for viewing of Crystal Reports only, and if viewer’s
preference is set to any viewer other than Interactive DHTML. When a report is requested for viewing, the
system will first check the Cache Server to see if there are any current available cache pages generated
for that report. If there are pages, the Cache Server will send available report pages to the Web
Application Server. If there are no cached pages, the Cache Server will request a Processing Server to
generate these pages.

© SAP AG 2009. All rights reserved. / Page 33

 Crystal Reports Cache Server - Properties

Cache Files Directory - Specifies the location of the cache file directory
(Default = %DefaultDataDir%/CrystalReportsCachingServer/temp)

Maximum Cache Size (KB) - Specifies the amount of hard disk space (in KB) that is used to cache reports.
A large cache size may be necessary if the server needs to handle large numbers of reports, or reports that
are especially complex. (Default = 256000)

Idle Connection Timeout (minutes) - Specifies the amount of time, in minutes, that the Crystal Reports
Cache Server waits for a request from an idle connection (Default = 20)

Security Cache Timeout (minutes) - Specifies the amount of time, in minutes, that the
server uses cached logon credentials, report parameters, and database connection information to serve
requests before querying the CMS (Default = 20)

Share Report Data Between Clients - Specifies whether report data is shared between different clients
(Default = TRUE)

Viewer Refresh Always Yields Current Data - Specifies whether, when users explicitly refresh a report, all
cached pages are ignored and new data is retrieved directly from the database
(Default = TRUE)

Oldest On-Demand Data Given to Clients (seconds) - Specifies the amount of time, in seconds, that the
server uses cached data to meet requests from on-demand reports (Default = 0)

© SAP AG 2009. All rights reserved. / Page 34

 Crystal Reports Processing Server

Responds to page requests by processing reports and generating encapsulated page

format (EPF) pages. The key benefit of EPF is that it supports page-on-demand access,
so only the requested page is returned, not the entire report. This improves system
performance and reduces unnecessary network traffic for large reports.

Services:

Crystal Reports 2011

Processing Service –
Accepts and processes Crystal Reports
2011 reports; can share data between
reports to reduce the number of database
accesses

Crystal Reports Processing Service -

Accepts and processes Crystal reports;
can share data between reports to reduce
the number of database accesses

© SAP AG 2009. All rights reserved. / Page 35

 Crystal Reports Processing Server - Properties

Temporary Directory - Specifies the directory where temporary files are created when necessary
(Default = %DefaultDataDir%/CrystalReportsProcessingServer/temp)

Maximum Concurrent Jobs (0 for automatic) - Specifies the maximum number of independent
jobs allowed to run concurrently on the Crystal Reports Processing Server (Default = 20)

Maximum Lifetime Jobs Per Child - Specifies the maximum number of jobs that each child
process can manage per lifetime (Default = 1000)

Maximum Number of Prestarted Children - Specifies the maximum number of prestarted child
processes that are allowed by the server. If this value is too low, the server creates child
processes as soon as requests are made, and a user may experience latency. If this value is too
high, system resources may be unnecessary wasted by idle child processes (Default = 1)

Idle Connection Timeout (minutes) - Specifies the amount of time, in minutes, that the Crystal
Reports Cache Server waits for a request from an idle connection (Default = 20)

Idle Job Timeout (minutes) - Specifies the length of time, in minutes, that the server waits
between requests for a given job (Default = 20)

Share Report Data Between Clients - Specifies whether report data is shared between different
clients (Default = TRUE)
© SAP AG 2009. All rights reserved. / Page 36
 Crystal Reports Processing Server - Properties

Viewer Refresh Always Yields Current Data - Specifies whether, when users explicitly refresh a
report, all cached pages are ignored and new data is retrieved directly from the database
(Default = TRUE)

Oldest On-Demand Data Given to Clients (seconds) - Specifies the amount of time, in
seconds, that the server uses cached data to meet requests from on-demand reports (Default = 0)

Java Class Path - The name and path of the Java classes that are required by the server.
(Default = %CommonJavaLibDir%/procCR.jar)

Java Child VM Arguments - Specifies the command-line arguments that are supplied to child
processes that are created by the server
(Default = Dbusinessobjects.connectivity.directory=%CONNECTIONSERVER_DIR%,
Dcom.businessobjects.mds.cs.ImplementationID=csEX)

Any properties that apply to both Crystal Reports Cache Servers and Crystal Reports
Processing Servers should be set to the same value.

© SAP AG 2009. All rights reserved. / Page 37

 Crystal Reports 2011 Processing Server -
Properties
Temporary Directory - Specifies the directory where temporary files are created when necessary
(Default = %DefaultDataDir%/CrystalReports2011ProcessingServer/temp)

Maximum Concurrent Jobs (0 for automatic) - Specifies the maximum number of independent
jobs allowed to run concurrently on the Crystal Reports Processing Server (Default = 0)

Maximum Lifetime Jobs Per Child - Specifies the maximum number of jobs that each child
process can manage per lifetime (Default = 1000)

Maximum Number of Prestarted Children - Specifies the maximum number of prestarted child
processes that are allowed by the server. If this value is too low, the server creates child
processes as soon as requests are made, and a user may experience latency. If this value is too
high, system resources may be unnecessary wasted by idle child processes (Default = 1)

Idle Connection Timeout (minutes) - Specifies the amount of time, in minutes, that the Crystal
Reports Cache Server waits for a request from an idle connection (Default = 20)

Idle Job Timeout (minutes) - Specifies the length of time, in minutes, that the server waits
between requests for a given job (Default = 20)

Share Report Data Between Clients - Specifies whether report data is shared between different
clients (Default = TRUE)
© SAP AG 2009. All rights reserved. / Page 38
 Crystal Reports 2011 Processing Server -
Properties
Viewer Refresh Always Yields Current Data - Specifies whether, when users explicitly refresh
a report, all cached pages are ignored and new data is retrieved directly from the database
(Default = FALSE)

Oldest On-Demand Data Given to Clients (seconds) - Specifies the amount of time, in
seconds, that the server uses cached data to meet requests from on-demand reports (Default =
0)

Allow Report Jobs to Stay Connected to the Database until the Report Job is Closed -
Specifies whether the report job will remain connected to the database until the job is closed
(Default = FALSE)

Database Records Read When Previewing or Refreshing (0 for unlimited) - Specifies the
number of database records that will be read when viewing or refreshing a report. This settings
limits the number of records that the server retrieves from the database when a user runs a
query or report. This setting is useful when you want to prevent users from running on-demand
reports that return excessively large record sets.

You may prefer to schedule such reports, both to make the reports available more quickly to
users and to reduce the load on your database from these large queries. (Default = 20000)

© SAP AG 2009. All rights reserved. / Page 39

 Dashboard Design Cache Server

Intercepts report requests sent from clients to the Dashboard server. If the cache server
cannot fulfill the request with a cached report page, it passes the request on to the
Dashboard server, which runs the report and returns the results. The cache server then
caches the report page for potential future use.

Services: Dashboards Cache Service

© SAP AG 2009. All rights reserved. / Page 40

 Dashboard Design Cache Server - Properties

Maximum Cache Size (KB) - Specifies the amount of hard disk space (in KB) that is used to cache
reports. A large cache size may be necessary if the server needs to handle large numbers of
reports, or reports that are especially complex. (Default = 256000)

Idle Connection Timeout (minutes) - Specifies the amount of time, in minutes, that the
Dashboards Cache Server waits for a request from an idle connection. There is generally no need
to modify the default value. (Default = 15)

Share Report Data Between Clients - Specifies whether report data is shared between different
clients (Default = TRUE)

Oldest On-Demand Data Given to Clients (seconds) - Specifies the amount of time, in seconds,
that the server uses cached data to meet requests from on-demand reports (Default = 0)

Security Cache Timeout (minutes) - Specifies the amount of time, in minutes, that the
server uses cached logon credentials, report parameters, and database connection information to
serve requests before querying the CMS (Default = 20)

Java VM Arguments - Specifies the command-line arguments that can be supplied to the JVM
(Default = Xmx858M)

© SAP AG 2009. All rights reserved. / Page 41

 Agenda

1. Overview
2. Common Server Properties
3. Management Services
3.1. Server Intelligent Agent
3.2 Web Application Component Server
3.3. Central Management Server
3.4 Event Server
4. Storage Services
4.1. File Repository Servers
4.2. Cache Servers
5. Processing Services
5.1. Scheduling Job Servers
5.2. Viewing Processing Server
6. Server Management
7. Solution Manager Monitoring
© SAP AG 2009. All rights reserved. / Page 42
 Adaptive Job Server

General server that processes scheduled jobs. When you add a Job server to the SAP
BusinessObjects Business Intelligence platform system, you can configure the Job server to
process reports, documents, programs, or publications and send the results to different
destinations.

Services:

• Authentication Update Scheduling Service - Provides synchronization of updates for third-

party security plug-ins

• Crystal Reports 2011 Scheduling Service - Accepts and processes Crystal Reports 2011
reports; can share data between reports to reduce the number of database accesses

• Crystal Reports Scheduling Service - Runs scheduled legacy Crystal Reports jobs and
publishes the results to an output location

• Destination Delivery Scheduling Service - Limits the number of database accesses

generated from Dashboards reports, and speeds up reporting by managing a cache of reports

• Lifecycle Management Service – LCM Core service

© SAP AG 2009. All rights reserved. / Page 43

 Adaptive Job Server – Services

• Platform Search Scheduling Service - Runs scheduled search to index all content in the
Central Management Server (CMS) repository

• Probe Scheduling Service - Provides scheduled Probe jobs and publishes the results to an
output location

• Program Scheduling Service - Runs programs that have been scheduled to run at a given
time

• Publication Scheduling Service - Runs scheduled publishing jobs and publishes the results
to an output location

• Replication Service - Runs scheduled federation jobs to replicate content between federated
sites

• Security Query Scheduling Service – Runs scheduled Sign-On support

• Visual Difference Scheduling Service - Runs scheduled Visual Difference (Lifecycle

Management) jobs and publishes the results to an output location

• Web Intelligence Scheduling Service - Enables support for scheduled Web Intelligence jobs

© SAP AG 2009. All rights reserved. / Page 44

 Adaptive Job Server – General Properties

Temporary Directory - Specifies the directory where temporary files are created on when
necessary. You may encounter performance issues if this directory does not have adequate
disk space. For better performance, ensure that this directory is located on a local disk.
(Default - %DefaultDataDir%)

Each service hosted on the Adaptive Job Server contains the following two parameters:

Maximum Concurrent Jobs - Specifies the number of concurrent independent processes (child
processes) that the server allows. You can adjust the maximum number of jobs to suit your
reporting environment (Default = 5)

Maximum Child Requests - Specifies the number of jobs the child will process before restarting
(Default = 100)

© SAP AG 2009. All rights reserved. / Page 45

 Connection Server

Provides database access to source data. It supports relational databases, as well as

OLAP and other formats. The Connection Server is responsible for handling connection
and interaction with the various data sources and providing a common feature set to
clients.

Services: Native Connectivity Service (32 or 64 bit)

Activate Data Source - Allows you to select the data sources for which you
want connections (Default = Not Selected

Network Layer - Specifies the network layer used by the connection

(Default = ODBC for native CORBA servers)

Database - Specifies the database used by the connection (Default = Blank)

Note: Only the non-localized name is considered for Network Layer and Database properties

© SAP AG 2009. All rights reserved. / Page 46

 Connection Server - Properties

Connection Pooling - Either enables

or disables the connection pool.
Possible values are:
• Enabled - With Timeout (default)
• Enabled
• Disabled

Connection Pool Timeout (minutes) - Specifies the maximum idle time for connections in
the pool in minutes (Default = 60)

Transient Object Inactivity Timeout (minutes) - Specifies how many minutes to keep an
unused temporary object in the server. The object is removed afterwards and its resources are
reclaimed (Default = 60)

Transient Object Timer Interval (minutes) - Specifies the time between activity checks in
minutes. At regular intervals, the server searches for candidate objects for removal (Default = 5)

Enable HTTP Chunking - Either enables or disables the HTTP chunking (Default = Enabled)

HTTP Chunk Size (kilobytes) - Specifies the size of the HTTP responses emitted by the server
in kilobytes (Default = 64)
© SAP AG 2009. All rights reserved. / Page 47
 Dashboards Processing Server

A new data processing layer is available for enterprise data connectivity and is designed to
address the scalability and performance requirements of large scale Dashboard deployments. It
includes two new servers: a Dashboard Design Cache Server and a Dashboard Processing
Server. The Dashboard Design Cache Server provides data caching and sharing on consistent
data models (Relational Universe queries) off the Semantic Layer, and the Dashboard
Processing Server manages query processing requests. Both servers are integrated into
standard BI Platform services including auditing and monitoring

© SAP AG 2009. All rights reserved. / Page 48

 Dashboards Processing Server - Properties

Maximum Concurrent Jobs (0 for automatic) - Specifies the maximum number of independent
jobs allowed to run concurrently on the Crystal Reports Processing Server (Default = 0)

Maximum Lifetime Jobs Per Child - Specifies the maximum number of jobs that each child
process can manage per lifetime (Default = 10000)

Maximum Number of Prestarted Children - Specifies the maximum number of prestarted child
processes that are allowed by the server. If this value is too low, the server creates child
processes as soon as requests are made, and a user may experience latency. If this value is too
high, system resources may be unnecessary wasted by idle child processes (Default = 1)

Idle Connection Timeout (minutes) - Specifies the amount of time, in minutes, that the Crystal
Reports Cache Server waits for a request from an idle connection (Default = 15)

Idle Job Timeout (minutes) - Specifies the length of time, in minutes, that the server waits
between requests for a given job (Default = 15)

Java Child VM Arguments - Specifies the command-line arguments that are supplied to child
processes that are created by the server.
(Default = Xmx858M,Dswfinjection.lang.directory=%CommonJavaLibDir%,
Dbusinessobjects.connectivity.directory=%CONNECTIONSERVER_DIR%)

© SAP AG 2009. All rights reserved. / Page 49

 Adaptive Processing Server

A generic server that hosts services responsible for processing requests from a variety of
sources.

Note:
The installation program installs one Adaptive Processing Server (APS) per host system.
Depending on the features that you've installed, this APS may host a large number of
services, such as the Monitoring Service, Lifecycle Management Service,
Multi-Dimensional Analysis Service (MDAS), Publishing Service, and others.

If you are installing a production environment, do not use the default APS. Instead, it is
highly recommended that once the installation process is complete, you perform a
system sizing to determine:

• The type and number of APS services.

• The distribution of services across multiple APS servers.
• The optimal number of APS servers. Multiple APS servers provide redundancy, better
performance, and higher reliability.
• The distribution of APS servers across multiple nodes.

Create new APS server instances as determined by the sizing process.

© SAP AG 2009. All rights reserved. / Page 51

 Adaptive Processing Server - Services

• Adaptive Connectivity Service - Provides connectivity services (replaces Connection Server)

• BEx Web Application Service - Provides integration of SAP Business Warehouse (BW)
Business Explorer (BEx) web applications with BI launch pad

• Client Auditing Proxy Service - Collects auditing events sent from clients and forwards them
to the CMS server

• Custom Data Access Service - Provides dynamic connections to data sources that do not
require a Connection Server

• Data Federation Service - ???

• Document Recovery Service - Web Intelligence document auto-save and recovery

• DSL Bridge Service - Dual Semantic Layer(DSL) session support

• Excel Data Access Service - Supports Excel files uploaded to Business Intelligence platform
as data sources

• Insight to Action Service - Enables actions to be invoked and provides support for RRI

© SAP AG 2009. All rights reserved. / Page 52

 Adaptive Processing Server - Services

• Lifecycle Management ClearCase Service – Provides ClearCase support for LCM

• Lifecycle Management Service – LCM Core service

• Multi Dimensional Analysis Service - Provides access to multi-dimensional Online Analytical

Processing (OLAP) data; converts the raw data into XML, which can be rendered into Excel,
PDF, or Analysis

• Platform Search Service - Runs scheduled search to index all content in the Central
Management Server (CMS) repository

• Publishing Post Processing Service - Performs actions on reports after they have
completed, such as sending a report to an output location

• Publishing Service - Coordinates with the Publishing Post Processing Service and
Destination Job Service to publish reports to an output location, such as a file system, FTP
server, email, or a user's inbox

• Rebean Service - SDK used by Web Intelligence and Explorer

• Security Token Service – SAP Single Sign-On support

© SAP AG 2009. All rights reserved. / Page 53

 Adaptive Processing Server - Services

• Translation Service - Translates InfoObjects with input from the Translation Manager client

• Visual Difference Service - Runs scheduled Visual Difference (Lifecycle Management) jobs
and publishes the results to an output location

• Visualization Service - A common Visualization Object Model Service used by Web

Intelligence

© SAP AG 2009. All rights reserved. / Page 54

 Adaptive Processing Server – Properties

Service Startup Timeout (seconds) - Specifies the amount of time, in seconds, that the server
will wait for services to start (Default = 1200)

There are no additional configuration properties for the following services:

• Adaptive Connectivity Service

• Client Auditing Proxy Service
• Document Recovery Service
• Lifecycle Management ClearCase Service
• Platform Search Service
• Publishing Post Processing Service
• Publishing Service
• Rebean Service
• Visual Difference Service

© SAP AG 2009. All rights reserved. / Page 55

 Adaptive Processing Server –
Bex Web Application Service Properties
Maximum Client Sessions - The maximum number of client sessions allowed on the service
(Default = 15)

SAP BW Master System - The name of the OLAP connection to the BW system that you created
in SAP BusinessObjects Business Intelligence platform (Default = SAP_BW)

JCo Server RFC Destination - The name of the JCo Server RFS Destination that you entered in
the BW system (Default = Blank)

JCo Server Gateway Host - The name of the JCo Server Gateway Host that you defined in the
BW system (Default = Blank)

JCo Server Gateway Service - The name of the JCo Server Gateway Service that you defined in
the BW system (Default = Blank)

JCo Server Connection Count - Specifies the number of automatically created programs that
can
be used to handle calls from ABAP to Java for the service (Default = 3)

© SAP AG 2009. All rights reserved. / Page 56

 Adaptive Processing Server –
Custom Data Access Service Properties
Custom Data Access Cleanup Timeout (in seconds) - Specifies the amount of time, in
seconds, that the service waits for an inactive client before performing a cleanup of the client's
session (Default = 1200)

Custom Data Access Swap Timeout (in seconds) - Specifies the amount of time, in seconds,
that the service waits for an inactive client before swapping the client's session onto the hard disk.
It is recommended that you specify a value that is lower than the value for the Custom Data
Access
Cleanup Timeout (in seconds) property (Default = 600)

© SAP AG 2009. All rights reserved. / Page 57

 Adaptive Processing Server –
Data Federation Service Properties
Max Connections – Specifies the maximum number of connections allowed on the server
(Default = 32767)

Execution Thread Pool Size - Specifies the maximum number of queries that can be executed in
parallel at a given moment (Default = 10)

Connection Inactivity Timeout (seconds) - Specifies the amount of time in seconds after which
an inactive connection is closed (Default = 10800)

Statement Inactivity Timeout (seconds) - Specifies the amount of time in seconds after which
an inactive query statement is closed (Default = 600)

© SAP AG 2009. All rights reserved. / Page 58

 Adaptive Processing Server –
DSL Bridge Service Properties
DSL Bridge Engine Cleanup Timeout (in seconds) - Specifies the amount of time, in seconds,
that the service waits for an inactive client before performing a cleanup of the client's session
(Default = 1200)

DSL Bridge Engine Swap Timeout (in seconds) - Specifies the amount of time, in seconds, that
the service waits for an inactive client before swapping the client's session onto the hard disk. It is
recommended that you specify a value that is lower than the value for the DSL Bridge Engine
Cleanup Timeout (in seconds) property (Default = 600)

© SAP AG 2009. All rights reserved. / Page 59

 Adaptive Processing Server –
Excel Data Access Service Properties
Excel Data Access Cleanup Timeout (in seconds) - Specifies the amount of time, in seconds,
that the service waits for an inactive client before performing a cleanup of the client's session
(Default = 1200)

Excel Data Access Swap Timeout (in seconds) - Specifies the amount of time, in seconds, that
the service waits for an inactive client before swapping the client's session onto the hard disk. It is
recommended that you specify a value that is lower than the value for the Excel Data Access
Cleanup Timeout (in seconds) property (Default = 600)

© SAP AG 2009. All rights reserved. / Page 60

 Adaptive Processing Server –
Insight to Action Service Properties
Maximum Number of Active Connections Per User Session - The maximum number of
connections with the SAP server available for a user for a given time (Default = 20)

Maximum Number of Idle Connections Per User Session - The number of idle connections to
keep open and reuse for subsequent RRI requests (Default = 20)

Maximum Connection Wait Time (in seconds) - The amount of time the Insight to Action
framework should wait for a response from the SAP Server before timing out (Default = 30)

© SAP AG 2009. All rights reserved. / Page 61

 Adaptive Processing Server –
Lifecycle Management Service Properties
Adaptive Job Server - Specifies the number of concurrent independent processes (child
processes) that the server allows. You can adjust the maximum number of jobs to suit your
reporting environment. The default setting is acceptable for most reporting scenarios. The ideal
setting for your reporting environment depends on your hardware configuration, database
software, and reporting requirements (Default = 5)

Adaptive Processing Server - Specifies the number of jobs the child will process before
restarting
(Default = 100)

Note: The Adaptive Processing Server has a Lifecycle Management Service and a Lifecycle
Management ClearCase Service. These services have no configurable properties in the CMC

© SAP AG 2009. All rights reserved. / Page 62

 Adaptive Processing Server –
Monitoring Service Properties
Enable Monitoring - Specifies whether monitoring enabled for the service (Default = TRUE)

Monitoring Thread Loop Delay (seconds) - Specifies the amount of time, in seconds, between
attempts that the service makes to ping clients (Default = 300)

Default Monitored Resource Cleanup Timeout (in seconds) - Specifies the amount of time, in
seconds, that the service waits for an inactive client before performing a cleanup of the client's
session (Default = 1200)

Default Monitored Resource Swap Timeout (in seconds) - Specifies the amount of time, in
seconds, that the service waits for an inactive client before swapping the client's session onto the
hard disk. It is recommended that you specify a value that is lower than the value for the Default
Monitored Resource Cleanup Timeout (in seconds) property (Default = 600)

© SAP AG 2009. All rights reserved. / Page 63

 Adaptive Processing Server –
Multi Dimensional Analysis Service Properties
Maximum Client Sessions - Specifies the maximum number of MDAS sessions that can
simultaneously be open on the server. When the number of open sessions reaches this number,
any additional attempts to start MDAS sessions result in a server unavailable error message. You
can change this value to optimize MDAS performance, depending on your needs and available
hardware, but increasing the value may result in performance issues for both the MDAS and the
database. The default value of 15 sessions is a conservative estimate. For installations where
user queries are small, you can increase this value significantly, whereas installations where user
queries are large would require a lower value (Default = 15, valid range is 1 to 100)

Maximum number of cells returned by a query - Specifies the number of cells that are returned
to a user in a single query. The user is prevented from executing a query that returns an extremely
large number of cells, consuming a large amount of memory. If the user's query exceeds this cell
limit, the user receives an error message (Default = 100000)

Maximum number of members returned when filtering - Specifies the number of members
retrieved when filtering by member. A very large number of retrieved members can consume a
large amount of memory (Default = 100000)

© SAP AG 2009. All rights reserved. / Page 64

 Adaptive Processing Server –
Visualization Service Properties
Visualization Engine Cleanup Timeout in seconds) - Specifies the amount of time, in seconds,
that the service waits for an inactive client before performing a cleanup of the client's session
(Default = 1200)

Visualization Engine Swap Timeout (in seconds) - Specifies the amount of time, in seconds,
that the service waits for an inactive client before swapping the client's session onto the hard disk.
It is recommended that you specify a value that is lower than the value for the Visualization
Engine Cleanup Timeout (in seconds) property (Default = 600)

© SAP AG 2009. All rights reserved. / Page 65

 Web Intelligence Processing Server

■ The processing server “processes” Web Intelligence requests such as opening,

rendering, refreshing, creating and editing WebI documents

■ Server Responsibilities

■ Creates, edits, views, and analyzes WI Documents

■ Maintains a cache of previously viewed instances and requests

■ Processes scheduled WI documents

■ Creates XML pages of the documents to send back to the SDK

■ Retrieves documents from the Input/Output FRS

■ Notifies WI Job Server when jobs are completed

■ Connects to universes and reporting databases

■ Exports documents to Excel and PDF formats

■ Viewing and scheduling Web Intelligence reports and List of Values (LOV) prompts
© SAP AG 2009. All rights reserved. / Page 66
 WebI Processing Server – Command Line Options

- ConnectionTimeoutMinutes <mins> Specify the number of minutes before the server will
timeout.

- MaxConnections <num> Specify the maximum number of simultaneous connections that the
server allows at one time.

- DocExpressEnable Enables caching of Web Intelligence documents when the

document is being viewed.

- DocExpressRealTimeCachingEnable Enables real time caching of Web Intelligence documents.

- DocExpressCacheDurationMinutes <mins> Specify the amount of time (in minutes) that

content is stored in cache.

- DocExpressMaxCacheSizeKB <kbs> Specify the size of the document cache.

- EnableListOfValuesCache Enables the caching per user sessions of lists of values

- ListOfValuesBatchSize <num> Specify the maximum number of values that can be returned
per list of values batch.

- UniverseMaxCacheSize <num> Specify the number of universes to be cached.

- WIDMaxCacheSize <num> Specify the maximum number of Web Intelligence documents that can
be stored in cache.
© SAP AG 2009. All rights reserved. / Page 67
 Web Intelligence Processing Server - Services

■ Information Engine Service

■ Web Intelligence Common Service

■ Web Intelligence Core Service

■ Web Intelligence Processing Service

© SAP AG 2009. All rights reserved. / Page 68

 Information Engine Service - Properties

- Enable List of Values Cache Specifies whether caching is enabled for List of Values on the Web
Intelligence Processing Server.
Default Value: TRUE

- List of Values Batch Size (entries) Specifies the maximum number of entries (or values) for each
List of Values batch.
Default Value: 1000

- Maximum Custom Sort Size (entries) Specifies the maximum number of entries in the custom sort.
Default Value: 100

-Universe Cache MaximumSize (Universes)Specifies the number of universes to be cached on the Web
Intelligence Processing Server.
Default Value: 20

- Maximum List of Values Size (entries) Specifies the maximum number of entries (or values) for each
List of Values.
© SAP AG 2009. All rights reserved. / Page 69
Default Value: 50000
 Web Intelligence Common Service - Properties

© SAP AG 2009. All rights reserved. / Page 70

 Web Intelligence Common Service - Properties

- Cache Timeout (minutes) Specifies the amount of time, in minutes, before the contents of the
document cache will be cleared. The timeout depends on the most recent
access date per document.
Default Value: 4370

- Document Cache Clean-up Interval (minutes) Specifies the time interval, in minutes, that the
document cache is scanned and is checked
against the Maximum Document Cache Size,
Maximum Document Cache Reduction Space,
and Maximum Document in Cache settings.
Default Value: 120

- Disable Cache Sharing Specifies whether cache sharing is disabled. By default cache sharing is
enabled; which means that all Web Intelligence Processing Server
instances will share the same cache. However, if you prefer to have one
cache per instance of Web Intelligence Processing Server then you
should enable this property.
Default Value: FALSE

-Enable Document Cache Specifies whether the document cache is enabled. If the property is
enabled, then the cache can be pre-loaded with scheduled Web
Intelligence documents.
Default Value: TRUE

© SAP AG 2009. All rights reserved. / Page 71

 Web Intelligence Common Service - Properties

- Enable Real-Time Cache Specifies whether the real-time cache is enabled. If the property
is enabled, then the cache can be loaded dynamically. Therefore, the
Web Intelligence Processing Server caches Web Intelligence documents when
they are viewed. The server also caches the documents when they run
as a scheduled job, if the pre-cache was enabled in the document.
Default Value: TRUE

- Maximum Document Cache Size (KB) Specifies the maximum size of the document cache. Once
this limit is reached the document cache will be cleared based
on the Maximum Document Cache Reduction Space property.
Default Value: 1000000

- Maximum Document Cache Reduction Space (percent) Specifies the percentage of cache that
is emptied to allow newer actions and
results to be stored in the cache.
Documents with the oldest “last
access time” are purged.
Default Value: 70

- Maximum Character Stream Size (MB) Specifies the maximum character stream size sent to the
Web Intelligence client. If this property is exceeded, then the
Web Intelligence document will not be created and the client
will receive an error message. Range: 1 - 65535
Default Value: 5

© SAP AG 2009. All rights reserved. / Page 72

 Web Intelligence Common Service - Properties

- Binary Stream Maximum Size (MB) Specifies the maximum size, in MB, of a binary stream sent to
the Web Intelligence client. If this value is exceeded, the Web
Intelligence document will not be created and an error
message appears on the client computer. Range: 1 - 65535
Default Value: 50

- Maximum Documents in Cache The maximum number of Web Intelligence documents that
can be stored in the cache. There is never more than this
many documents in the cache; the total size of the cache is
never greater than the value specified with the Maximum
Document Cache Reduction Space (MB)
setting. To improve system performance, set this value to 0
when Enable Real-Time Cache is selected, but you should
enter a value when Enable Real-Time Cache is cleared.
Range: 0 - 65535
Default Value: 0

- Images Directory Specifies the location of the images directory.

Default Value: Blank

- Output Cache Directory Specifies the location of the cache.

Default Value: Blank

© SAP AG 2009. All rights reserved. / Page 73

 Web Intelligence Core Service - Properties

© SAP AG 2009. All rights reserved. / Page 74

 Web Intelligence Core Service - Properties

- Timeout Before Recycling (seconds) Specifies the time, in seconds, the server is idle before the
Server Intelligence Agent (SIA) stops and restarts the server
when the total number of documents processed is above the
value specified with the Maximum Documents Before
Recycling property.
Default Value: 1200

- Idle Document Timeout (seconds) Specifies the amount of time, before the Web Intelligence
Processing Server session will be swapped.
Therefore, when the client is not generating requests during this
period of time, the session will be swapped onto the hard disk, freeing
up resources for an active session. Range: 100 - 1000
Default Value: 300

- Server Polling Interval (seconds) Specifies the interval, in seconds, that must pass before the
server polls for new thread requests. When the server is in
the polling phase, it performs cleanup actions like swapping
unused documents to keep the server memory under the
upper memory threshold.
Default Value: 120

-Maximum Documents per User Specifies the maximum number of active sessions (Web
Intelligence documents) that can be associated with a user at
any given time. Therefore, if the default value is 5, then the
user can use up to 5 active sessions at once. Range: 1 - 20
Default Value: 5
© SAP AG 2009. All rights reserved. / Page 75
 Web Intelligence Core Service - Properties

- Maximum Documents Before Recycling Specifies the number of Web Intelligence documents that can
be processed before the server will be considered for
recycling. If the number of processed documents has been
reached, and the server is idle, then the server is closed and
the Server Intelligence Agent (SIA) starts a new instance of
the server. However, there will be a time delay before a new
instance of the server is started. The time delay is defined by
the Timeout Before Recycling property.
Default Value: 50

- Allow Document Map Maximum Size Errors Specifies whether the Maximum Connections
property is restricted. If this property is enabled,
then the value set for the Maximum Connections
property is recognized by the server; otherwise
the property is disregarded.
Default Value: TRUE

- Idle Connection Timeout (minutes) Specifies the amount of time, in minutes, that the server waits
for a request from an idle connection. Setting a value that is
too low can cause a request to close prematurely. Setting a
value that is too high can caused requests to be queued while
the server waits for idle requests to be closed.
Default Value: 20

© SAP AG 2009. All rights reserved. / Page 76

 Web Intelligence Core Service - Properties

- Maximum Connections Specifies the maximum number of simultaneous sessions that can be
opened at one time. This is an approximate number; this setting does not
count the inactive sessions that are swapped, or the session that is
created to analyze the number of sessions. If this limit is reached and no
other server is available to handle the request, the user will receive an
error message. The Allow Document Map Maximum Size Errors property
must be enabled for this property to be recognized by the server.
Default Value: 50 Range: 5 - 65535

- Enable Memory Analysis Specifies whether memory analysis is enabled. If this property is enabled
then the following properties will be active and recognized by the server:
• Memory Maximum Threshold
• Memory Upper Threshold
• Memory Lower Threshold
When the server's process memory is above the Memory Upper
Threshold, the only operation that is allowed is saving documents. When
the process memory is above the Memory Maximum Threshold, all
operations stop and fail.
Default Value: TRUE

- Memory Maximum Threshold (MB) Specifies the maximum threshold for memory consumption.
Default Value: 6000

- Memory Upper Threshold (MB) Specifies the maximum threshold for memory consumption.
Default Value: 4500
© SAP AG 2009. All rights reserved. / Page 77
 Web Intelligence Core Service - Properties

- Memory Lower Threshold (MB) Specifies the lower threshold for memory consumption.
Default Value: 3500

- Enable APS Service Monitoring Enables monitoring of the server by the APS
service, hosted on the Adaptive processing server.
Default Value: TRUE

- Retry Count on APS Service ping failure Specifies the number of times the server will try to reach the
APS Service before deciding that it is unable to reach it.
Default Value: 3

- APS Service Monitoring Thread Period Specifies the period of delay between attempts to reach the
APS Service.
Default Value: 300

- Enable Current Activity Logs Specifies whether complete traces are generated in the server's log files.
This property should be enabled only for debugging purposes when
troubleshooting issues. Set to FALSE during normal operations.
Default Value: FALSE

© SAP AG 2009. All rights reserved. / Page 78

 Web Intelligence Processing Service - Properties

- Enable use of HTTP URL Specifies whether the server is able to access files that are stored
remotely.
Default Value: TRUE

- Proxy value Specifies the address of your network's proxy server. It is only necessary to specify a
value if your network has a proxy server and you attempting to access files that are
stored remotely.
Default Value: Blank

© SAP AG 2009. All rights reserved. / Page 79

 Web Intelligence Processing Server – General
Properties

- Single Sign-On Expiry (seconds) Specifies the time, in seconds, that an SSO connection is
valid before expiring.
Default Value: 86400

© SAP AG 2009. All rights reserved. / Page 80

 Report Application Server (RAS)

 Provides ad-hoc reporting capabilities that allow users to create and modify Crystal
reports via the SAP Crystal Reports Server Embedded Software Development Kit
(SDK).
 Resolves dynamic recipient lists for a publication
 See Report Application Server .NET SDK Developer Guide for more info on report
viewing
 The default path to the server on Windows is <INSTALLDIR>\SAP BusinessObjects
Enterprise XI 4.0\win32_x86\crystalras.exe.
 The default path to the server on Unix is
<INSTALLDIR>/sap_bobj/enterprise_xi40/<PLATFORM32>/ras/boe_crystalras.

© SAP AG 2009. All rights reserved. / Page 81

 RAS – Crystal Reports 2011 Viewing and
Modification Service - Command Line Options

 -ipport – Specify the port number for receiving TCP/IP requests when running in stand-
alone mode (outside of Business Intelligence platform).
 -report_ProcessExtPath - Specify the default directory for processing extensions. For
details, see the SAP BusinessObjects Business Intelligence Platform Administrator
Guide. Specify the default directory for processing extensions. For details, see the
SAP BusinessObjects Business Intelligence Platform Administrator Guide.
 -ProcessAffinityMask - Use a mask to specify exactly which CPUs that RAS will use
when it runs on a multi-processor computer. The mask is in the format 0xffffffff, where
each f represents a processor, and the list of processors reads from right to left (that is,
the last f represents the first processor). For each f, substitute either 0 (use of CPU not
permitted) or 1 (use of CPU is permitted). For example, if you run the RAS on a four-
processor computer and want it to use the third and fourth processor, use the mask
0x1100. To use the second and third processor, use 0x0110.
 Note:
– RAS uses the first permitted processors in the string, up to the maximum
specified by your license. If you have a two processor license, 0x1110 has the
same effect as 0x0110.
– The default value of the mask is -1, which has the same meaning as 0x1111.

© SAP AG 2009. All rights reserved. / Page 82

 RAS – Crystal Reports 2011 Viewing and
Modification Service - CMC Settings

© SAP AG 2009. All rights reserved. / Page 83

 RAS – Crystal Reports 2011 Viewing and
Modification Service - CMC Settings
Allow Report Jobs to Stay Connected… = Specifies whether the report job will remain
connected to the database until the process has been executed.
Default Value: FALSE

Browse Data Size = Specifies the number of distinct records returned from
the database when browsing through a particular field's values. The data is retrieved first
from the client's cache - if it is available - and then from the server's cache. If the data is not
in either cache, it is retrieved from the database.
Default Value: 100

Idle Connection Timeout = Specifies the amount of time, in minutes, that the Report
Application Server (RAS) waits for requests from an idle client before timing out. Setting a
value too low can cause a user's request to be closed prematurely, and setting a value that
is too high can affect the server's scalability (for instance, if the ReportClient Document
object is not closed explicitly, the server will be waiting unnecessarily for an idle job to lose).
Default Value: 30

Batch Size = Specifies how many rows from the result set are returned by the database
during each data transfer. For example, if 500 records are requested, and the Batch Size
property is set to 100 records, the data will be returned in 5 separate batches of 100 rows.
To improve the performance of your RAS, you must understand your network environment,
database, and the type of requests in order to set the appropriate batch size.
Default Value: 100
© SAP AG 2009. All rights reserved. / Page 84
 RAS – Crystal Reports 2011 Viewing and
Modification Service - CMC Settings

Num of database records… = Specifies the number of database records that will be read when
viewing or refreshing a report. This settings limits the number of records that the server retrieves
from the database when a user runs a query or report. This setting is useful when you want to
prevent users from running on-demand reports that return excessively large record sets. You may
prefer to schedule such reports, both to make the reports available more quickly to users and to
reduce the load on your database from these large queries.
Default Value: 20000

Maximum Concurrent Report Jobs (0 for unlimited) = Specifies the maximum number of
independent jobs allowed to run concurrently on the RAS.
Default Value: 75

Oldest On-Demand Data Given to Clients (secs) = Specifies the amount of time, in minutes, an
on-demand report will serve cached report data.
Default Value: 20

Temporary Directory = Specifies the directory where temporary files are created when necessary.
You may encounter performance issues if this directory does not have adequate disk space.
Default Value: %DefaultDataDir%/CrystalReportsRasServer/temp

Single Sign-On Expiry (secs) = Specifies the time, in seconds, that an SSO connection is valid
before expiring.
Default Value: 86400
© SAP AG 2009. All rights reserved. / Page 85
 Agenda

1. Overview
2. Common Server Properties
3. Management Services
3.1. Server Intelligent Agent
3.2 Web Application Component Server
3.3. Central Management Server
3.4 Event Server
4. Storage Services
4.1. File Repository Servers
4.2. Cache Servers
5. Processing Services
5.1. Scheduling Job Servers
5.2. Viewing Processing Server
6. Server Management
7. Solution Manager Monitoring
© SAP AG 2009. All rights reserved. / Page 86
 Server Groups

Server Groups

 Provides a way of grouping servers (Regionally, by Type,

etc)

 Allows for delegated administration

 Use subgroups for further organization/ administration

 Separate server groups to control data flow for Scheduling

or Viewing

For instance, force your EMEA reports pull data from

EMEA database servers for optimal efficiency

© SAP AG 2009. All rights reserved. / Page 87

 Server Cloning

 Cloning allows for easy movement between nodes and/or machines

 Can create a new server using another server’s settings
 Cloning a server from one node to another
 Server credentials will be inherited by the new node’s settings.
 Use placeholders where possible, otherwise the cloned server will use the hardcoded
values for both servers. For instance, server temp folder path.

 Available placeholders are listed for each server within the CMC.
Server properties > Placeholders

© SAP AG 2009. All rights reserved. / Page 88

 Server Configuration Templates

 A template stores a list of settings for a server type.

 Assign one server to be used as the template.
 Assign the other like servers to use the configuration template
 Useful when creating multiple servers of same type

© SAP AG 2009. All rights reserved. / Page 89

 Agenda

1. Overview
2. Common Server Properties
3. Management Services
3.1. Server Intelligent Agent
3.2 Web Application Component Server
3.3. Central Management Server
3.4 Event Server
4. Storage Services
4.1. File Repository Servers
4.2. Cache Servers
5. Processing Services
5.1. Scheduling Job Servers
5.2. Viewing Processing Server
6. Server Management
7. Solution Manager Monitoring
© SAP AG 2009. All rights reserved. / Page 90
 Thank you!

© SAP AG 2009. All rights reserved. / Page 91