Page 1
Planning Application Server Installation Guide
Planning Application Server 10.8
Page 2
Patents
Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects:
5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352.
Trademarks
Copyright
Third-party
contributors
Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered
trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names
mentioned herein may be trademarks of their respective owners.
Copyright © 2002-2006 Business Objects. All rights reserved.
Business Objects products in this release may contain redistributions of software licensed from third-party contributors.
Some of these individual components may also be available under alternative licenses. A partial listing of third-party
contributors that have requested or permitted acknowledgments, as well as required notices, can be found at:
http://www.businessobjects.com/thirdparty
Page 3
Contents
Introduction
Required Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Document Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Chapter 1: Before You Install
Technical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Prerequisite Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Server and System Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Defining a Service Account for Application Server . . . . . . . . . . . . . . . . . . . . .7
Configuring Application Server with a Remote Business Objects Planning User
Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Installing Microsoft .NET Framework 1.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Installing Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Installing Professional Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Uninstalling Prior Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Chapter 2: Installing Application Server
Installing Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Upgrading Existing Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Repairing or Removing Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Remove. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Chapter 3: Configuring Application Server
Configuring Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Unused Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Editing Configuration Manager Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Stopping and Starting Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Appendix A: Service Account Permissions
Business Objects Planning Service Account Permissions . . . . . . . . . . . . . . . . . . . . . . . .31
Planning Application Server Installation Guide 3
Page 4
Contents
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4 Planning Application Server Installation Guide
Page 5
Introduction
This guide discusses the installation and configuration of Planning Application Server.
Application Server controls back-end services and scheduled tasks for the Planning
Professional Edition.
This document assumes that you have already read and performed the steps in the
following Business Objects Planning installation guides:
z If this is a Microsoft® SQL Server deployment, the SQL Server Administration
Guide for Business Objects Planning.
z If this is an Oracle® deployment, the Oracle Administration Guide for Business
Objects Planning.
z For all deployments, the Planning Professional Edition Installation and Admin-
istration Guide.
Many of the steps in this document refer to databases, files and directories established
when performing the steps in the above documents.
Required Installations
Application Server is a component of Planning Enterprise Services. Application Server is
required to enable the following Professional Edition features:
consult the Planning Enterprise Services Installation and Administration Guide, which
can be found in the DOCUMENTS folder of your Business Objects Planning product
distribution, or on www.mysrc.com
Intended Audience
Installation of Application Server is typically handled by the organization’s Information
Technology department. The person handling the installation should have appropriate
permissions on the target server(s), and be familiar with installing and configuring
systems for use in a web environment.
Configuration and administration of the Application Server components usually requires a
collaboration of the IT administrator and the Business Objects Planning System
Administrator (Master System User). Business Objects Planning Support and the
Professional Services department are also available to help you through this process.
z Automated email capabilities of Process Control (Lite or Standard deployments)
z Use of the Scheduler automated task utility (Standard deployments only)
Important: This document discusses the steps involved with installing Application Server to enable the above functionality only. If you will be utilizing any
web access options, do not follow the instructions in this document. Instead,
.
Planning Application Server Installation Guide 5
Page 6
Introduction
Document Structure
This manual is organized in the following structure:
Chapter 1, “Before You Install”, discusses the prerequisites for installing Application
Server and planning your installation.
Chapter 2, “Installing Application Server”, discusses installing Application Server
using the Enterprise Services Installer.
Chapter 3, “Configuring Application Server”, discusses configuration information for
Application Server.
Appendix A, “Service Account Permissions”, details the specific permissions
required for the Business Objects Planning Service Account.
Notes
Installations of Enterprise Services include software covered by the GNU Public License
(specifically, #ZipLib and GNU GhostScript). Source code for these components may be
obtained at no charge by contacting Business Objects.
6 Planning Application Server Installation Guide
Page 7
Before You Install
This chapter discusses the prerequisites for installing Application Server. This chapter
applies to every deployment and should be read carefully before proceeding with the
installation.
Technical Requirements
Prior to installation, you should make sure your system meets the recommended technical
requirements for Business Objects Planning. Please contact the Support department or
visit www.mysrc.com
Technical Requirements document.
Planning Your Installation
Before taking any installation steps, it is important to have a well-considered plan for the
implementation environment. This section discusses some of the issues to be considered
when deciding upon your system and server configuration.
for the most recent version of the Business Objects Planning
Server and System Architecture
The server configuration options vary slightly depending on whether you are a Lite
Edition (Microsoft Jet) or Standard Edition (SQL Server or Oracle) installation.
Lite Edition:
Application Server and the Professional Edition shared Program directory must be
installed to the same server. We strongly recommend that the shared User directory
(including the Microsoft Jet database) be placed on this server as well.
Standard Edition:
Application Server and the Professional Edition shared Program directory must be
installed to the same server. We recommend that the shared User directory be placed on
this server as well, although it can reside elsewhere if desired.
We recommend that the SQL Server or Oracle database be hosted on a separate database
server that could also be shared across the enterprise.
Defining a Service Account for Application Server
Application Server requires a local account on the server under which the respective
services are run. If you are hosting your Business Objects Planning User directory on a
separate network location, then you should configure this service account as a domain
Planning Application Server Installation Guide 7
Page 8
Before You Install
1
Planning Your Installation
account. See “Configuring Application Server with a Remote Business Objects Planning
User Directory” on page 8.
It is easiest to initially setup this account (i.e. Business Objects Planning Service
Account) as a part of the local administrator group for installation and configuration, but
permissions can later be reduced to specific directory/file access if necessary. For more
information on permissions requirements for the Business Objects Planning Service
Account, see “Business Objects Planning Service Account Permissions” on page 31.
Note that you will be prompted for this service account identity as part of the installation
process for Application Server.
Some scheduled tasks require output to be sent to the printer during execution. The output
will be sent to the default printer of the Business Objects Planning Service Account.
Please ensure that the Business Objects Planning Service Account has a default printer
established for its workstation.
Configuring Application Server with a Remote Business Objects Planning User Directory
Note: The following section applies only if you plan on hosting Application
Server in an environment where the Business Objects Planning User directory
is located remote to the application server.
Network file access to the Business Objects Planning User directory is required by
Application Server as well as users running the desktop Professional Edition. If the
application server is hosted on a server separate from the User directory, then it is
necessary to create a network account that has access to the remote file system.
It is easiest to configure a domain group that contains the identities of all Professional
Edition users as well as the service account under which Application Server is running.
An example of creating a network group and necessary service account is described
below:
1. Create a Domain Global Group, for example DomainName/Business Objects
Planning Users Group, on which you will grant Read/Write privileges to the
network location where the User directory is located. In a native Active
Directory Environment this group may be actually created as a Domain Local
Group.
2. Create an account to be used by the Application Server for network access, for
example Business Objects Planning Service Account.
3. Add the Business Objects Planning Service Account as a Member of the domain
group above. Also add the network identities of Professional Edition users.
4. Assign file read/write privileges to the domain group to the User directory
location on the network.
8 Planning Application Server Installation Guide
Page 9
Note: If you intend to deploy the Business Objects Planning User directory on
a non-Windows file system such as Novell, please contact Support for further
information. Application Server requires read/write access to the User
directory.
Prerequisite Components
The following components are required for operation of Application Server. All of these
components need to be on the server you are installing to before you attempt installation
of Application Server. If a prerequisite component is not found, the installer will abort the
installation with a message prompting you to install the missing component.
Both Business Objects Planning Lite and Standard installations require the following
components:
z Excel XP or 2003
z Microsoft .NET Framework 1.1
z Planning Professional Edition
Before You Install
Prerequisite Components
1
The following sections describe installation of each of the above prerequisite components.
Installing Microsoft .NET Framework 1.1
Microsoft .NET Framework is required to be installed on the server. Note that the .NET
Framework 1.1 comes pre-installed on Windows Server 2003.
There are two approaches you can use to install .NET Framework:
z Download the .NET Framework Runtime from Microsoft, along with any ser-
vice packs. To do so, you can select Windows Update from the server’s Start
menu, or you can select the following URL: http://windowsup-
date.microsoft.com/.
z When you run the Application Server installer, the install program will check to
see if the appropriate version of .NET Framework is installed. If it is not, the
installer will abort the install and launch Windows Explorer to where the .NET
install files are in your Business Objects Planning product distribution. You can
then launch the .NET install manually. When the .NET install is complete, restart the Application Server install.
If for some reason the .NET files are not available to the Application Server
installer program, the installer will attempt to launch the designated Microsoft
web site where you can download and install the .NET files manually.
You may choose the default options when installing the Framework. You may get a
prompt to restart your computer after the installation of the Framework and service packs.
Please do so before proceeding.
Planning Application Server Installation Guide 9
Page 10
Before You Install
1
Prerequisite Components
Installing Excel
Note: Before continuing, make sure you are logged onto the server you are
configuring as the Business Objects Planning Service Account user. This
environment will assure that each component will have the proper permissions,
and registry hives will be built out properly as you go along.
Excel XP or 2003 must be installed on the server. A default Excel installation is adequate.
After installing, go to http://office.microsoft.com/productupdates/
install any updates.
After installing, open Excel while logged in using the Business Objects Planning Service
Account and perform the following two verifications:
1. Verify that there are no prompts at startup, like “Enter name and initials” or any
Office activation prompts.
2. Go to Tools > Macro > Security and click on the Trusted Sources tab. Verify
that both Trust all installed add-ins and templates and Trust Access to Visual
Basic Project are checked.
and check for and
Installing Professional Edition
Planning Professional Edition is required to be installed on the server. To install
Professional Edition, follow the instructions contained in the Planning Professional
Edition Installation and Administration Guide. The Program directory must be installed
locally, and we recommend that the User directory also be installed locally. If the User
directory is not installed to the application server, see “Configuring Application Server
with a Remote Business Objects Planning User Directory” on page 8.
When installing the Professional Edition on the server, ensure that you are using the local
drive letters for the Program directory (for example: C:\PROGRAM FILES\SRC
SOFTWARE\CORE) and the User Directory (for example. C:\PROGRAM FILES\SRC
SOFTWARE\USER) where prompted. The Program and User directories should then be
shared appropriately for use by other Business Objects Planning users on the network.
Subsequent client network and node installations can then access the shared Business
Objects Planning Program and User directories by using mapped network drive letters
(for example: J:\PLANNING) or Universal Naming Convention (UNC) paths (for
example: \\SERVER\PLANNING).
Uninstalling Prior Versions
If you have installed a prior version (pre-Version 10) of SRC Scheduler Service, it must
be manually deleted before proceeding with the Application Server installation.
To remove this component, go to Start > Settings > Control Panel > Add/Remove
Programs. Choose to Remove SRC Scheduler Service and follow the prompts. This
legacy code must be cleared from your system before proceeding with the Version 10
installation of Application Server.
10 Planning Application Server Installation Guide
Page 11
Installing Application Server
This chapter discusses installing Application Server for both Standard (Microsoft SQL
Server or Oracle) and Lite (Microsoft Jet) deployments. The steps in this chapter assume
that you have already reviewed and performed the prerequisite installation steps detailed
in Chapter 1.
The installation program used for this purpose is labeled Enterprise Services, however,
the only option enabled for you to install is Application Server. Installation of Application
Server includes two sub-components, Planning Scheduler Services and Planning
Configuration Manager.
Note: The installation program performs checks for required components
during the installation. If a required component is not found, the installation
program will abort and you will receive an error message identifying the
necessary component. If this occurs, install the necessary component and restart the
installation program.
Note: You must be an administrator-level user on the server in order to run the
installation program. If you are not, the installation program will abort with a
message asking you to logon as the administrator and re-start the installation.
Installing Application Server
Important: If you are upgrading an existing Business Objects Planning instal-
lation, special considerations apply. Please see “Upgrading Existing
Installations” on page 15 for more details.
To install Application Server, perform the following steps:
1. Within the ENTERPRISE SERVICES folder of your Business Objects Planning
product distribution (either a CD or downloaded via the web), double-click on
setup.exe.
2. The installation performs several checks for minimum requirements, and then brings
up the Welcome screen. Click Next to continue.
3. The License Key screen appears. Enter the 25-character license key listed on the
cover letter with your installation package. Click Next to continue.
4. The Features screen appears:
Planning Application Server Installation Guide 11
Page 12
Installing Application Server
2
Installing Application Server
This screen indicates that Application Server will be installed, along with its two
subcomponents, Scheduler Services and Configuration Manager. You cannot unselect these two subcomponents – they are required for an Application Server
installation. Click Next to continue.
5. The Application Server Location screen appears:
12 Planning Application Server Installation Guide
Page 13
Installing Application Server
Installing Application Server
2
The default location is C:\PROGRAM FILES\SRC SOFTWARE. The path must be a
local directory on the machine you are installing to. If you wish to designate a
different path, click the Browse button. Click Next to continue.
6. The NT Service Log On screen appears. Type in the domain\user name and password
for Application Server to run under. Note that the user name must have a password
defined – the installer will not accept a blank password.
Planning Application Server Installation Guide 13
Page 14
Installing Application Server
2
Installing Application Server
If you wish, you can uncheck the box at the top of the dialog to have the Application
Server run under the Local System account. This allows you to continue with the
installation. However, before the system enters production you need to designate a
domain\user name and password other than the Local System account. The install
program gives you a warning to this effect if you proceed with the Local System
account.
Click Next to continue.
7. The Start Copying Files screen appears. This screen lists a summary of the installation choices made. Review this information and click Next to continue if you are
satisfied with the settings. If you wish to make any changes to the settings, click
Back.
8. The Setup Status screen appears. A progress bar displays the progress of the
installation.
9. The Installation Complete screen appears. Click Finish to exit the installation
program.
The Planning Configuration Manager automatically launches upon successful completion
of the install. See Chapter 3 for details on the Configuration Manager. If you are not
prepared to make the configuration settings for your system at this time, exit the
Configuration Manager. You can enter it later by choosing Start > Programs > Business
Objects > Planning > Configuration Manager. (Note: Upgrades of systems originally
14 Planning Application Server Installation Guide
Page 15
installed prior to 10.71 are located at Start > Programs > SRC Software > Enterprise
Services > SRC Configuration Manager.)
Upgrading Existing Installations
If you are upgrading an existing installation of Application Server, special considerations
apply. The Business Objects Planning components must be upgraded in a particular order
to ensure that all components are upgraded appropriately and compatible.
In almost all cases, both the Professional Edition and Application Server must be
upgraded to the same version. The following describes the order for upgrading all
components:
1. Stop Application Server. Before proceeding with either upgrade, stop the Application Server (the service name in the Services console is SRC Application Server).
The Professional Edition installation program will attempt to shut down the service if
it is not already stopped.
2. Upgrade the Professional Edition. Consult the Planning Professional Edition
Installation and Administration Guide for specifics.
Installing Application Server
Upgrading Existing Installations
2
3. Login to the Professional Edition. To complete the necessary database upgrades,
log in to the Professional Edition as the administrator, then log out. You must perform
this step for each Business Objects Planning system (each separate Business Objects
Planning database) installed in your environment.
4. Upgrade Application Server. Follow the installation steps as detailed in this chapter
to perform the upgrade. Most of your installation choices will be remembered from
the prior installation.
5. Upgrade the Configuration File. To upgrade the configuration file, launch the
Configuration Manager and save the configuration file. If the configuration file is not
upgraded, the system will not operate properly. See Chapter 3 for details on the
Planning Configuration Manager.
6. Start Application Server. After all the installation steps are complete, restart Application Server.
Repairing or Removing Application Server
Once Application Server has been installed, you can repair or remove the program by
choosing Start > Settings > Control Panel > Add or Remove Programs > Enterprise
Services, or by running the install program in your Business Objects Planning product
distribution.
A dialog box appears with the following options. See below for more information on any
of these options.
Planning Application Server Installation Guide 15
Page 16
Installing Application Server
2
Repairing or Removing Application Server
z Modify allows you to selectively install or uninstall Enterprise Services compo-
nents. (NOTE: This option is inapplicable to Application Server-only installations, see below.)
z Repair reinstalls missing or older files, registry entries and shortcuts.
z Remove removes the entire installation of Application Server from this com-
puter.
Modify
The Modify capability is intended to allow you to selectively install or uninstall certain
Enterprise Services components. However, this option is inapplicable in the context of an
Application Server-only installation, as the only two sub-components are required and
cannot be selectively installed. To uninstall Application Server, use the Remove option.
Repair
Selecting Repair restores files and registry entries to your system. The Repair process
compares the files on your machine to its installation files and re-installs any files that are
missing, or that have older dates. It also rewrites all required registry entries and restores
your shortcuts (i.e. Start menu).
You would perform a Repair as a diagnostic step if you are experiencing unknown system
issues, or if you know that certain files have been deleted or corrupted.
16 Planning Application Server Installation Guide
Page 17
Installing Application Server
Repairing or Removing Application Server
Remove
Selecting Remove allows you to uninstall Application Server for this computer.
Note that the files associated with the Configuration Manager settings,
SRCCONFIG.XML and SRCCONFIG.XML.SIG, are not deleted as part of an uninstall.
They will remain in the application directory created when you installed Application
Server (default of C:\PROGRAM FILES\SRC SOFTWARE). These files are not deleted
in the event you are re-installing Application Server either to the same machine or another
machine, and wish to keep your current Configuration Manager settings. If you are
installing Application Server on another machine, copy these files to the new directory
created on the new machine.
If you do not need these Configuration Manager files any longer, you will need to
manually delete them and the application directory from your machine.
2
Planning Application Server Installation Guide 17
Page 18
Installing Application Server
2
Repairing or Removing Application Server
18 Planning Application Server Installation Guide
Page 19
Configuring Application Server
Planning Configuration Manager is the tool used to configure Application Server. You
must configure your system using Configuration Manager before operating Application
Server.
As mentioned in the previous chapter, the Configuration Manager launches upon the
successful completion of an Application Server installation. If you need to launch it
manually, choose Start > Programs > Business Objects > Planning > Configuration
Manager. (Note: Systems originally installed prior to 10.71 are located at Start >
Programs > SRC Software > Enterprise Services > SRC Configuration Manager.)
The primary goal of the Configuration Manager is to define systems for use with
Application Server. The Configuration Manager points to User directories to define
systems. For example, if you have implemented BusinessObjects Budgeting and
BusinessObjects Forecasting, and they each have a separate User directory, then you must
define both as systems in the Configuration Manager.
However, if you have licensed BusinessObjects Budgeting and BusinessObjects Payroll
Planning, but both application modules utilize the same User directory, then you only
have to define one system in the Configuration Manager.
Additionally, there are several global parameters that can be set in the Configuration
Manager.
Note: The Configuration Manager contains several settings and options that
are inapplicable to an Application Server-only installation. For a discussion of
these settings, see “Unused Settings” on page 29. If you are getting validation
errors that do not seem to make sense, it may be that you have inadvertently changed an
inapplicable setting. Please be sure to review this section to make sure you understand
which areas of the Configuration Manager are inapplicable and should not be changed.
Configuring Application Server
To configure your system for use with Application Server, perform the following steps:
1. If the Configuration Manager is not already open, choose Start > Programs >
Business Objects > Planning > Configuration Manager to start the application.
(Note: Systems originally installed prior to 10.71 are located at Start > Programs >
SRC Software > Enterprise Services > SRC Configuration Manager.)
When you first open the Configuration Manager, it will appear similar to the
following:
Planning Application Server Installation Guide 19
Page 20
Configuring Application Server
3
Configuring Application Server
The Configuration Manager validates settings on entry. Because you have not yet
entered any settings, several error messages appear. These can be ignored until you
have completed all the configuration steps discussed in this chapter and perform a
validation on the finished file.
Defining Systems for Use with Application Server
2. The next step is to define systems for use with Application Server. Expand the
Systems node in the treeview. If this is the first time you have entered the Configuration Manager, you will see an entry named NewSystem.
If you have previously defined a system and want to define additional systems, rightclick the Systems node and select Add System. A new entry will appear named
NewSystem.
3. Select the NewSystem node and complete the following settings:
System Name
Type in a name for your system. We recommend selecting a name that you will
intuitively associate with this application, for example, BusinessObjects Budgeting.
20 Planning Application Server Installation Guide
Page 21
Configuring Application Server
Configuring Application Server
User Directory
Click the Browse button and navigate to the folder on your server or network that
contains the Business Objects Planning User directory for the application module you
are defining. By default, this location is C:\PROGRAM FILES\SRC
SOFTWARE\USER. Do not use mapped drive letters. If this location is on a network
share, use the UNC naming convention, such as \\SERVERNAME\SHARENAME.
Database Type
Select the database type for the Business Objects Planning system that you have
licensed – either Jet, SQL Server or Oracle.
Note: The Configuration Manager does not validate the accuracy of these
settings on Validation, so type carefully and check your entries when
finished.
Once you have typed in your selections, the node adopts the System Name you
defined for it. The following screenshot shows an example of a completed System
node:
3
4. If the Database Type you selected in Step 3 was SQL Server or Oracle, expand the
new node you created and highlight the Connection Parameters node. Complete the
following settings for either SQL Server or Oracle.
For SQL Server, specify the Data Source (server name) and Initial Catalog
(database name) that relates to this system.
For Oracle, specify the Data Source. In Oracle, this is either:
Planning Application Server Installation Guide 21
Page 22
Configuring Application Server
3
Configuring Application Server
z A defined service name. This is the name of a locally configured entry made
using the Oracle configuration tool, or a globally configured entry looked up
from Oracle Internet Directory or an Oracle Names Server.
z A TNS descriptor. You can obtain the TNS descriptor for the database from Ora-
cle Enterprise Manager.
This step does not apply if you are defining a Lite (Microsoft Jet) system.
Note: The Configuration Manager does not validate the accuracy of these
settings on Validation, so type carefully and check your entries when
finished.
The following screenshot shows an example of completed Connection Parameters
settings for an SQL Server system:
5. Repeat steps 2-4 for each system you wish to define. Remember, each defined system
must point to a unique User directory.
Defining Global Parameters
6. Expand the Global Parameters node. Several system-wide parameters are set here,
as discussed in the following steps.
7. Underneath Global Parameters, select the Email node. Certain conditions in Application Server generate an automated email message to users and/or to the System
Administrator, using the email addresses as defined in the Security Settings of the
Professional Edition. To enable the system to send these messages, you must define
an SMTP-compliant server and a “From” identity. Complete the following settings:
22 Planning Application Server Installation Guide
Page 23
Configuring Application Server
Configuring Application Server
Mail Server (SMTP-Compliant)
Type in the name of the mail server for Application Server to use when generating
email messages. Application Server generates these messages in an SMTP format, so
the mail server must be SMTP-compliant. Most email servers support this protocol
(including Microsoft Exchange).
Email From
Type in an email address for Application Server to use as the “From” address. This
address should follow the convention of name@company.com. Other alias formats
may not work properly. The address must be a valid user defined in the Mail Server.
Note: The Configuration Manager does not validate the accuracy of these
settings on Validation, so type carefully and check your entries when
finished.
The following screenshot shows an example completed Email screen:
3
8. Under Global Parameters, select the ExcelPool node. Application Server utilizes a
pool of Excel instances for various functions. Each instance of Excel runs asynchronously, and the pool contains automatic recovery functions in case of failure. You can
control various aspects of the pool by editing the ExcelPool settings.
Important: If you are planning to implement a configuration of the Application Server that includes more than 4 instances of Excel, you should
contact Support for an important registry key modification necessary to
ensure the proper heap size necessary.
Review and complete the following settings as necessary:
Planning Application Server Installation Guide 23
Page 24
Configuring Application Server
3
Configuring Application Server
Start Up Excel Instances
This parameter defines how many instances of Excel to launch on services startup. It
should be unnecessary to adjust the default instances except in extremely high server
load situations. Please contact Support for assistance.
Maximum Excel Instances
This parameter indicates the maximum number of Excel instances to support your
services requests. The suggested number of maximum Excel instances is 1.5 times
the number of processors on the server hosting Application Server. For example, if
the server has 2 processors, then Maximum Excel Instances should be set to 3.
Idle Instance Life (minutes)
This parameter describes how long an Excel instance will remain without any
activity. After this time has elapsed without any requests, the instance will be
terminated, except for the minimum default instances as defined above.
The following screenshot shows an example completed ExcelPool screen:
9. Under Global Parameters, select the Log node. Application Server maintains a log
file (SRCSERVERLOG.TXT) that can be used to diagnose problems that may arise.
It is a rolling log file that archives a copy of itself daily (archived as
SRCSERVERLOG.TXTdate.TXT). If problems arise in your system, you may be
asked to send this file to your support representative for assistance in debugging
issues.
Review and complete the following settings as necessary:
Location
Type in the path that you want the log file saved to, or click the Browse button to
browse to a location. A UNC path is recommended. However, you can use a physical
24 Planning Application Server Installation Guide
Page 25
Configuring Application Server
Configuring Application Server
local machine drive letter if desired. Mapped drives should never be used, as those
mappings will not be available to the service.
If this directory does not exist, Application Server will create it when started.
Detail Level
This field specifies the amount of logging that will occur. The default setting is
Warn. Your support representative may ask you to subsequently adjust this setting.
The following screenshot shows an example completed Logs screen:
3
10. Under Global Parameters, select the Paths node. The Paths setting allows you to
define a location on the application server for temporary files.
Type in a valid location for temporary files used by Enterprise Services in the Server
Temporary File Location field. A local physical drive can be used. If you use a local
physical drive, you will receive a warning during validation, advising you to use a
UNC path. However, as long as the local path is valid and does not use mapped
drives, you can ignore the warning.
If this directory does not exist, Application Server will create it when started. The
following screenshot shows an example completed Paths screen:
Planning Application Server Installation Guide 25
Page 26
Configuring Application Server
3
Configuring Application Server
11. Under Global Parameters, select the Scheduler Service node. This setting relates to
the number of systems to perform concurrently executed tasks.
Within any single Business Objects Planning system, scheduled tasks execute
sequentially. Scheduler Service can execute tasks from different systems
concurrently. The Maximum Concurrent Executing Systems item limits the
number of systems that can have concurrently executing scheduler tasks. The default
setting is 3. Setting this number too high could result in excessive computer resources
being devoted to background processing, potentially impacting performance from an
end user perspective. Please contact Support for more assistance.
The following screenshot shows an example completed Scheduler Service screen:
26 Planning Application Server Installation Guide
Page 27
Configuring Application Server
Configuring Application Server
3
12. The remaining option under Global Parameters is Security. This setting does not
apply to Application Server-only installations. However, if you do not complete this
setting, you will receive a validation error when you validate the configuration
settings. You can choose to either ignore the validation error, or fill in the Security
setting to avoid receiving the error. Neither choice has an impact on your Application
Server.
If you decide to complete the setting, click on the Security node. Select a defined
system from the Primary Authentication System drop-down box. Again, this setting
will have no impact on the Application Server – it defines a primary authentication
system for login to Enterprise Desktop, which is inapplicable to an Application
Server-only installation.
Validating Your Settings
13. The final step is to perform a validation of your settings. To do this, choose
Validation > Validate Document.
14. You may see a number of messages in the Validation pane. Double-click on each
message to be automatically navigated to the entry requiring attention. The following
example shows an error message related to a missing Server Temporary File Location
setting:
Planning Application Server Installation Guide 27
Page 28
Configuring Application Server
3
Configuring Application Server
Note that in most cases, the Validation routine is only checking whether a required
setting has been completed, and whether it is in an appropriate format. For example,
it will check to make sure you have made an entry in the User directory field under a
System Name, but it will not validate the existence of that User directory. Please be
sure to check all your entries to make sure no typing errors occurred.
Remember, if you chose not to fill in the Global Parameters > Security setting (as
discussed in step 12), you will receive an error stating “Error Security Primary
Authentication System is missing.” You can either ignore this error, or fill in the
setting to remove the error.
15. When all validation errors have been resolved, select File > Save to save your
settings, then File > Exit to close the Configuration Manager. Although it is possible
to save configuration settings with errors, we highly recommend fixing all configuration errors prior to exiting the Configuration Manager (except the Security setting
validation error as discussed above).
The Configuration Manager automatically performs a validation upon Save, and also
when a configuration file is opened.
When you are done configuring your systems, you need to start Application Server. See
“Stopping and Starting Application Server” on page 29.
28 Planning Application Server Installation Guide
Page 29
Unused Settings
There are several settings in the Configuration Manager that do not apply to Application
Server-only installations. These include the Suites node and subnodes, and the Global
Parameters > Security node.
Additionally, if you right-click on a defined System Name, you will see the option to add
various access options. These do not apply to an Application Server-only installation. If
you add these options to your defined system, it will not add the functionality.
If you do edit these settings or add an access option, it will not impact your Application
Server functionality. However, it may generate validation errors when you validate the
document as described earlier. With the exception of the Security setting as discussed in
the configuration steps, we strongly recommend leaving these areas alone, so that you do
not have to sort through inapplicable validation errors. Please contact Support if you have
any questions about validation errors or the unused settings.
Editing Configuration Manager Settings
At any time you can enter the Configuration Manager and edit your settings.
Configuring Application Server
Editing Configuration Manager Settings
3
z New systems can be added by following the steps outlined in this chapter.
z Existing systems can be deleted by right-clicking the node name and selecting
Delete. Note that if only one system is defined, the Configuration Manager will
not allow you to delete that system.
Be sure to Save after making any changes.
If changes are made within the Configuration Manager, you need to stop and restart
Application Server, as discussed in the following section.
Stopping and Starting Application Server
The service name for Application Server is SRC Application Server. Stopping SRC
Application Server stops all service tasks. To stop the service, go to Start > Settings >
Control Panel > Administrative Tools > Services, scroll down to SRC Application
Server, right-click and then choose Stop.
To start Application Server, simply re-start the service from the Services Console.
You should stop and restart the service in the following instances:
z Before upgrading the Business Objects Planning system. See “Upgrading Exist-
ing Installations” on page 15.
z After you change any settings via the Configuration Manager.
z If you receive a new SU.XLS file from your support representative, you must
login to the Professional Edition as Administrator. Then, stop and restart the service, so that the new system parameters are recognized.
Planning Application Server Installation Guide 29
Page 30
Configuring Application Server
3
Stopping and Starting Application Server
z If you are experiencing unknown system issues, you may stop and restart as a
diagnostic step.
z If instructed to do so by a support representative as a diagnostic step.
Important: Application Server must be running to support the Business
Objects Planning functionality as described in the Introduction to this
document. You should only stop the service if necessary as described above,
and the service should be immediately restarted.
30 Planning Application Server Installation Guide
Page 31
Service Account Permissions
Business Objects Planning Service Account Permissions
As discussed in Chapter 1, Application Server requires a local account on the server under
which the respective services are run. It is easiest to initially setup this account (i.e.
Business Objects Planning Service Account) as a part of the local administrator group for
installation and configuration, but permissions can later be reduced to specific directory/
file access if necessary.
The following enumerates the specific rights that the Business Objects Planning Service
Account must have in order to operate Application Server:
z File system read/write privileges to the Business Objects Planning User direc-
tory.
z File system read privileges to the Business Objects Planning Program directory.
z File system read/write privileges to the Server Home directory (the directory
where Application Server was installed).
z The right to run Excel (and a properly configured profile for Excel – to ensure
this, log in as the user and run Excel once).
z Read registry access to HKLM\Software\SRC Software and all subkeys.
z The right to install drivers.
Planning Application Server Installation Guide 31
Page 32
Service Account Permissions
A
Business Objects Planning Service Account Permissions
32 Planning Application Server Installation Guide
Page 33
Index
Symbols
#ZipLib, 6
.NET, installing
, 9
a
Active Directory Environment, 8
Add System
, 20
b
Business Objects Planning Service Account, see service
account
c
Configuration Manager, 12, 14, 17-29
defining Global Parameters
defining systems
defining the connection parameters for the database
21
editing existing settings
saving settings
starting
, 19
unused settings
validating settings
validation errors
configuring Application Server
configuring for use with a remote User directory
Connection Parameters
, 20, 22
, 28
, 29
, 27-28
, 20, 27
, 21
, 22-27
, 29
, 19-29
, 8
g
Global Parameters, defining, 22-27
GNU GhostScript
GNU Public License
, 6
, 6
i
Idle Instance Life, 24
Initial Catalog
installation steps
intended audience
, 21
, 11-14
, 5
l
license key, 11
Lite Edition, server configuration
local system account
Location (Log setting)
Log settings
, 24-25
, 14
, 24
,
m
mail server, 23
Maximum Concurrent Executing Systems
Maximum Excel Instances
Microsoft .NET Framework, installing
Microsoft Excel, installing
Microsoft Jet
Microsoft SQL Server
Microsoft Windows Server 2003
modifying the Application Server installation
, 7, 21-22
, 24
, 10
, 5, 7, 21
, 7
, 26
, 9
, 9
, 15-17
d
Data Source, 21
defining systems for use with Application Server
Detail Level
domain account
Domain Global Group
Domain Local Group
, 25
, 7
, 8
, 8
e
editing configuration settings, 29
email settings
Enterprise Services
Excel, see Microsoft Excel
ExcelPool settings
, 22
, 11
, 23-24
, 20, 22
n
NewSystem, 20
Novell
, 9
NT service logon
, 13
o
Oracle, 5, 7, 21
p
Paths settings, 25
Planning Configuration Manager, see Configuration
Manager
Planning Enterprise Services, see Enterprise Services
Planning Professional Edition, see Professional Edition
Planning Application Server Installation Guide 33
Page 34
Index
prerequisite documents, 5
prerequisite software components
prerequisites to installation
Primary Authentication System
Process Control
Professional Edition
installing
Program directory
, 5
, 5, 8-9
, 10
, 7, 31
, 9-10
, 7-10
, 27
r
repairing the Application Server installation, 15-17
required installations
restarting Application Server, events necessitating a
restart
, 29
, 5
s
saving configuration settings, 28
Scheduler
Scheduler Service (legacy version), uninstalling
Scheduler Service settings
Scheduler Services
Security settings
server configurations
Server Temporary File Location
service account
SMTP
SQL Server, see Microsoft SQL Server
SRC Application Server
SRCCONFIG.XML
SRCCONFIG.XML.SIG
SRCSERVERLOG.TXT
Standard Edition, server configuration
Start Up Excel Instances
starting and stopping the Application Server
SU.XLS
System Name
Systems
, 5
, 11-12
, 27
, 7
, 8, 10
defining
permissions
printer requirements
, 7
, 31
, 22
, 17
, 29
, 20
, 20
, 10
, 26
, 25
, 8
, 29
, 17
, 24
, 7
, 24
, 29
Application Server
prior versions
upgrading existing installations
User directory
, 7-8, 19, 31
, 15-17
, 10
v
Validation, 27
Visual Basic Project
, 10
w
web access options, 5
Windows Server 2003
, 9
, 15
t
technical requirements, 7
temporary files location
, 25
u
uninstalling
34 Planning Application Server Installation Guide
Loading...