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:
The BusinessObjects Intercompany installation guide contains the following:
•The components to be installed and configured before installing
•A summary of the steps involved in installing the product.
•Detailed instructions on installing BusinessObjects Intercompany
•Detailed instructions on configuring the product.
Intended audience
This document is intended for system administrators who are in charge of the
installation, configuration and administration of BusinessObjects
Intercompany. Architects should be experienced in systems and networks
and be familiar with the BusinessObjects Intercompany environment.
This document will provide you with the information you need to set up all of
the installation tasks.
To find out more about using the product, please consult the BusinessObjects
Intercompany user guide. The user guide is available in PDF format on the
installation CD or in HTML format in the Help menu after installation.
BusinessObjects Intercompany.
components.
Document conventions
Typefaces
The table below presents the different typefaces used in the guide:
TypefaceMeaningExample
BoldNames of windows,
dialog boxes, menus,
menu commands and
buttons
Menu > Command Menu commandSelect New > Data source.
CodeCommand line
Code on gray
background
6Installation guide
All or part of a
configuration file to be
checked or changed
The Installation Directory dialog box will
appear.
CtStopServer.vbe_SrvBroker_Magnitude_""
<add key="CompressionLevel"
value="Normal" />
Page 7
TypefaceMeaningExample
Numbered listProcedure or series of
steps to be performed
< >Value to be set
_ Compulsory space
between settings
" "To be inserted if spaces
are used in a setting
[ ]Optional setting
1.Right-click to select New > Virtual
Directory.
2.The following dialog box will appear:
3.Click Next.
4.Open a Command Prompt dialog box.
5.Run the
command line.
<datasource_name>_
CtStartServer.vbe_<datasource_manager>
<"datasource_password">
<"datasource_password">_[<server>]
Introduction
About this guide
C:\>iisreset /restart
1
Installation guide7
Page 8
Introduction
1
Business Objects technical support
Business Objects technical support
If you encounter difficulties during the installation, configuration or
administration of the product, please consult the Troubleshooting chapter in
the Administration guide first.
If this does not provide an answer to your problem, you should contact the
person within your workgroup who is in charge of centralizing queries. He/she
will then liaise with your IT team and if required, with the Business Objects
Software Support team.
You should provide the following information when reporting the problem:
•the version number of the product installed on your computer
•the environment used e.g. Web, Citrix, Windows, etc.
•the type of database (e.g. Oracle, Microsoft SQL Server, etc.) and its
version
•the operating systems of the servers and clients
•the network connection, e.g. RNIS, WAN, LAN, etc. and other software
components such as Internet Explorer, IIS, etc.
•the exact text of the messages that appear when a problem occurs
•a clear problem statement
•the action plan implemented to try to solve the problem
You should also provide the corresponding screen shots, log files, error
messages and any other tools to identify the problem.
8Installation guide
Page 9
New features 5.1
Authentication
New configuration panel supports the following authentication modes:
•LDAP
•ActiveDirectory
•Business Objects security
Platforms
The following platforms are now supported or obsolete:
•Microsoft SQL 2005 support in native mode.
•Oracle 10g.
•ActivePDF Server 3.8 is no longer required because it is replaced by an
internal component.
•Microsoft Excel 2003 is no longer required because it is replaced by an
internal component.
•Microsoft SQL 2000 and Oracle 9i are no longer supported.
Note: If you use either of these databases, you should migrate to one of the
new databases supported.
Introduction
New features 5.1
1
Installation guide9
Page 10
Introduction
1
New features 5.1
10Installation guide
Page 11
Checklist for installing
BusinessObjects
Intercompany
chapter
Page 12
Checklist for installing BusinessObjects Intercompany
2
Single server installation
Single server installation
Step 1 - Back up the databases in useFor more information, see...
If an earlier version of BusinessObjects Intercompany is already installed on the
application server, save the database(s) in use. Perform the backup using SQL Server
Enterprise Manager or Oracle Export Utility).
The default database is generally called "IntercompanyDB"
Step 2 - Migrate the database engineFor more information, see...
If using SQL Server, install SQL Server 2005
If using Oracle, install Oracle 10g
Step 3 - Uninstall BusinessObjects
Intercompany
1.If an earlier version of BusinessObjects Intercompany is already installed on the
application server, uninstall it.
2.Restart the server and check that the uninstall operation has been successfully
completed in the Windows Control Panel.
Step 4- Install BusinessObjects IntercompanyFor more information, see...
1.For SQL Server 2005 database:
- Install SQL Server 2005 SP2 US (Client
Tools Only)
“Databases” on page 18
For more information, see...
“Installing the SQL Server 2005 client”
on page 18
For Oracle10g database:
- Install Oracle Database Server 10g Release
2 Client with Oracle Services for Microsoft
Transaction Server component installation
- Install Oracle10g Release 2 ODAC (Oracle
Data Access Component)
3.Install the BusinessObjects Intercompany
Services
Step 5 - Create or migrate the databaseFor more information, see...
1.If you are installing BusinessObjects
Intercompany for the first time, you must
create a database using the SQL Database Generator program or Oracle DB Manager.
12Installation guide
“Installing the Oracle 10g Release 2
client” on page 18
Intercompany” on page 28
“Installing the BusinessObjects
Intercompany Services” on page 38
“Creating a SQL database” on page 45
or “Creating an Oracle database” on
page 47
Page 13
Checklist for installing BusinessObjects Intercompany
Single server installation
2
2.If an earlier version of BusinessObjects
Intercompany is already installed, you must
migrate your database via the SQL Database
Upgrade program or the Oracle DB
Manager.
3.Copy the Cartesis.ICS.license.lic file
provided by Business Objects to the root of
the BusinessObjects Intercompany
installation folder created during the
installation on the application server.
Step 5 - Connect to BusinessObjects
Intercompany
Open your browser and connect to http://
<server_name>/ICS5
“Migrating a SQL database” on page 54
or “Using the BusinessObjects
Intercompany Oracle DB Manager” on
page 47
“Installing the license” on page 44
For more information, see...
“Logging in to BusinessObjects
Intercompany” on page 61
Installation guide13
Page 14
Checklist for installing BusinessObjects Intercompany
2
Multi servers installation
Multi servers installation
Installing the server hosting the servicesFor more information, see...
1.For SQL Server 2005 database:
- Install SQL Server 2005 SP2 US (Client
Tools Only)
For Oracle10g database:
- Install Oracle Database Server 10g
Release 2 Client with Oracle Services for
Microsoft Transaction Server component
installation
- Install Oracle10g Release 2 ODAC
(Oracle Data Access Component)
2.Check that the Microsoft .NET Framework
2.0 is installed
3.Install BusinessObjects Intercompany
- Check the Clustered option
- Check the ASP.NET State Service
4.Install the BusinessObjects Intercompany
Services
Installing the standard serversFor more information, see...
1.Check that Excel 2003 is installed
2.For SQL Server 2005 database:
- Install SQL Server 2005 SP2 US (Client
Tools Only)
“Installing the SQL Server 2005 client” on
page 18
“Installing the Oracle 10g Release 2 client”
on page 18
“Installing the server hosting the ASP.NET
State Service” on page 65
“Installing the server hosting the ASP.NET
State Service” on page 65
“Installing the SQL Server 2005 client” on
page 18
For Oracle10g database:
- Install Oracle Database Server 10g
Release 2 Client with Oracle Services for
Microsoft Transaction Server component
installation
- Install Oracle10g Release 2 ODAC
(Oracle Data Access Component)
3.Check that the Microsoft .NET Framework
2.0 is installed
14Installation guide
“Installing the Oracle 10g Release 2 client”
on page 18
Page 15
Checklist for installing BusinessObjects Intercompany
Multi servers installation
2
5.Install BusinessObjects Intercompany
Server
- Check the Clustered option
- Do not forget to enter the File Service’s
Machine Name
On all serversFor more information, see...
1.Configure loadbalancing (for example
through the Microsoft NLB cluster)
“Installing the standard servers” on
page 68
Installation guide15
Page 16
Checklist for installing BusinessObjects Intercompany
2
Multi servers installation
16Installation guide
Page 17
Installation requirements
chapter
Page 18
Installation requirements
3
Databases
Databases
Installing the SQL Server 2005 client
We recommend that you install the client version (with the latest service pack)
provided with your database engine on the BusinessObjects Intercompany
application servers.
Note: If you have problems connecting to the database, you may have to
perform the full SQL Server client installation so that you can use the
application's configuration and analysis tools. The setup is available on the
SQL Server installation CD. The optimal setup for BusinessObjects
Intercompany is an SQL Server client configured in TCP/IP mode.
Warning: If an SQL client is already installed, you should check that it is
configured to function in English.
Installing the Oracle 10g Release 2 client
Warning: Only one Oracle client should be installed per BusinessObjects
Intercompany application server. The value of the
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES\HOME_CO
UNTER\ key must be 1.
Do not forget to uninstall other oracle client versions you might have installed
before installing the Oracle client 10g.
You must install the Oracle client version corresponding to your database
engine on the BusinessObjects Intercompany application servers:
•Oracle 10g Release 2 client (10.2.0.3) Patch Set 2 or higher Standard
Edition
•Oracle Services for Microsoft Transaction Server component
•Oracle10g Release 2 ODAC (Oracle Data Access Component)
Warning: Make sure that the Read and Execute permissions are checked
for the Authenticated Users group in the Oracle client directory.
18Installation guide
Page 19
Installation requirements
Databases
Oracle 10g client with Oracle Services for Microsoft Transaction Server
component installation
1.During the Oracle client setup, you must select the Oracle Services for
Microsoft Transaction Server.
3
Oracle10g Release 2 ODAC (Oracle Data Access Component) 10.2.0.2.21
installation
1.Download the ODAC setup from http://www.oracle.com/technology/
software/tech/windows/odpnet/index.html.
Installation guide19
Page 20
Installation requirements
3
Databases
2.Execute the setup and select the Oracle Data Provider for .NET 2.0.
20Installation guide
Page 21
SQL 2005 engine settings
When you install Microsoft SQL Server 2005, you can use the default settings
proposed by the setup.
The Intercompany database must use the following settings:
Installation requirements
Databases
3
In the Recovery modeldrop-down menu of the Options window, select the
following option.
•Fullif you want to activate the log.
•Simpleif you do not want to activate the log.
Warning: If you activate the log, you must regularly back up your database
logs. If you do not do so, the database log will be completely filled.
In the Automaticgroupbox, we recommend that you select the following
options:
•Auto create statistics
•Auto update statistics
The other choices are optional.
Installation guide21
Page 22
Installation requirements
3
Databases
Warning: You should not select the Auto shrink and Auto close options on
a server so as not to decrease its performance.
The BusinessObjects Intercompany database can be accessed via a
connection string. This string contains login information needed to connect to
the database. The default login is sa. However, we strongly recommend
locking access to the SQL login and creating other logins.
The SQL login created to connect to BusinessObjects Intercompany should
belong to the database owner (dbo) for every database you want to access.
Warning: You cannot log in using a login with the same rights as the dbo.
The database collation should be one that uses the 125X code page, e.g. the
Latin1_General collation with the 1252 code page. You should select a caseinsensitive (CI) and accent-sensitive (AS) sort order.
Example: Latin1_General_CI_AS.
Recommendations for improving performance
We recommend that you install two configurations for the physical storage of
the data files to improve performance and data protection.
Firstly, you should store the following files on separate disks:
•the log files and tempdb table files.
•the .mdb data and index files.
Choosing between RAID 0 and RAID 1 is the equivalent of choosing between
performance and data protection.
•RAID 0 splits the data across several disks. It does not offer any
protection in case of hardware failure but does improve read/write
performance.
•RAID 1 writes data to two disks, creating two identical disks. In this way, if
either one is damaged, the data is still stored on the other disk. RAID 1
therefore enables you to protect data but does not help improve
performance.
Other methods for improving performances and security are available
(RAID 5, SAN systems, etc.).
This section outlines a data storage method. However, we strongly
recommend that you consult the SQL Server 2005 documentation.
Disk spanning
As mentioned above, we recommend that the data and indexes be stored on
different disks in order to improve performance. This is only possible if the
server contains more than one disk. This is not the standard configuration of
the database provided.
22Installation guide
Page 23
Installation requirements
Databases
Ideally, the BusinessObjects Intercompany database is made up of the
following three filegroups.
•Filegroup for storing the balances.
•Filegroup for storing the indexes to the balances.
•Filegroup for storing other data.
The clustered index of the balances table (tblIntercoTxn) must be stored
with the data itself.
However, the non-clustered indexes can be stored in another filegroup.
3
Installation guide23
Page 24
Installation requirements
3
Oracle 10g engine settings
Oracle 10g engine settings
Oracle installation requirements
The required components for installing the Oracle database engine are:
•the Oracle server on the DBMS server.
•the Oracle Net client on the application servers with Oracle Services for
MTS and ODAC.
All the other components are optional. Oracle Corporation recommends that
you upgrade your client software to match the current server software and
use the latest patch releases.
Warning: You must install the client layer delivered with your database
engine on the application server.
Note: To find out more about the operating systems supported,
recommended patches and installation procedures, you can consult the
Oracle website at http://www.oracle.com.
When you install the Oracle engine, you can use the default settings
proposed during setup.
Database requirements
In order to function properly, the BusinessObjects Intercompany database
requires a standard instance.
The options available with the Oracle engine are not mandatory (such as
Oracle Spatial, Oracle Ultra Search, Oracle Data Mining, etc.)
With regard to the database Connection Options, BusinessObjects
Intercompany supports the shared server mode (formerly known as multithreaded server mode).
The character set recommended for a BusinessObjects Intercompany
database is WE8MSWIN1252. The national character set recommended is
AL16UTF16.
If you are planning to install BusinessObjects Intercompany in Japanese, the
national character set recommended is
When the database is configured in archive log mode, you should ensure that
sufficient disk space is available for the archived redo logs and that the
system is sized appropriately to support the system overhead associated with
archiving.
For the memory settings, the default Oracle settings are sufficient.
24Installation guide
AL32UTF8.
Page 25
Installation requirements
Oracle 10g engine settings
BusinessObjects Intercompany uses a single Oracle account to store all its
database objects and manage all its connections to the Oracle server.
Typically, multiple simultaneous connections to the server are established
with this single user account at any given time. Different schemas to separate
development and production environments can coexist in the same database.
You can create schema using the BusinessObjects Intercompany Oracle DB
Manager. It is possible to create schema without the assistant; however, you
must use the BusinessObjects Intercompany Oracle DB Manager for
database initialization (tables, stored procedures, functions…).
If you choose to create the schema without the BusinessObjects
Intercompany Oracle DB Manager, the Oracle user must have:
•a dedicated tablespace for its objects
•a temporary tablespace for temporary objects
The Oracle user account requires the following privileges:
•CONNECT, RESOURCE
3
Installation guide25
Page 26
Installation requirements
3
Web components
Web components
Before installing BusinessObjects Intercompany, you must install the following
components:
•Windows Server 2003 operating system
•Internet Information Services (IIS) 6
•Microsoft .NET framework 2.0
IIS configuration
activation of ASP.NET 2.0
In the IIS management console, check that the extension of the Web service
associated with ASP.NET 2.0 is authorized as indicated below:
Security recommendations
To take advantage of the full set of security settings, it is important to make
sure that virtual directories are located on drives formatted for the NTFS file
system.
Recommendations for the IIS log
Because users can change their IP address during a session, reading IIS logs
is complicated. In order to facilitate user workflow, you can configure the IIS
log so that it includes a cookie. This enables you to monitor Web sessions
easily and does not increase the size of the log.
To activate the IIS log
1.Access the IIS management console.
2.In the Web Sites Properties window, select the Web Site tab.
3.Check the Enable Logging option.
4.Click the Properties button.
5.In the Extended Properties tab, check the Cookie option.
Note: Log activation is optional.
26Installation guide
Page 27
Single server installation
chapter
Page 28
Single server installation
4
Installing BusinessObjects Intercompany
Installing BusinessObjects Intercompany
To install BusinessObjects Intercompany
1.Double-click Setup.exelocated in the BusinessObjects Intercompany
Web Application folder of the installation CD.
The BusinessObjects Intercompany 5.1 - InstallShield Wizard dialog
box appears.
2.Click Next.
28Installation guide
The following dialog box appears.
Page 29
Single server installation
Installing BusinessObjects Intercompany
3.Specify a User Name and your Organization.
4.Click Next.
The following dialog box appears.
5.Check the I accept the terms in the license agreement and click Next.
The following dialog box appears.
4
6.In the ASP.NET State Service’s Machine Name field, enter the name of
the application server that will host the ASP.NET State Service.
Installation guide29
Page 30
Single server installation
4
Installing BusinessObjects Intercompany
7.In the ASP.NET State Service’s Port Number field, enter the 42424
value.
8.In the File Service’s Machine Name field, enter the name of the server
that hosts the file service.
9.In the File Service’s Machine Port Number field, enter the 11111 value.
10. Select the Standalone running environment.
11. Click Next.
The following dialog box appears.
12. Select the Complete option and click Next.
30Installation guide
Page 31
Single server installation
Installing BusinessObjects Intercompany
13. The following dialog box appears.
14. Select the Completeoption and click Next.
15. Select the folder in which you want to install the application and click
Next.
The following dialog box appears.
4
16. Select the folder in which you want to store the files generated by
BusinessObjects Intercompany and click Next.
Installation guide31
Page 32
Single server installation
4
Installing BusinessObjects Intercompany
The following dialog box appears.
17. Click OK.
The following dialog box appears.
18. If the settings are correct, click Install.
32Installation guide
Page 33
Single server installation
Installing BusinessObjects Intercompany
The following dialog box enables you to check on the progress of the
installation.
Once the installation is complete, the following dialog box appears.
4
19. Click Finish.
20. Open the folder you defined at step 16 to store the files generated by
Intercompany and give Full control access to the ASP.NET account.
21. Then set the DTC service called Distributed Transaction Coordinator
to Automatic Start up type.
Installation guide33
Page 34
Single server installation
4
Installing BusinessObjects Intercompany
Warning: This operation is mandatory. If you do not set the DTC service
to automatic, you may encounter errors when when trying to write to the
ICS database.
22. Restart the machine.
Warning: We recommend that you restart your machine immediately
after the installation is complete.
Importing heavy files
IIS 6.0 sets a maximum size for files on the application server. You can
change the maximum by following these instructions:
1.Select the <BusinessObjects Intercompany 5.0 Installed
Folder>\aspnet\ics5folder.
2.Make the changes in the web.config file.
3.Search for the maxRequestLengthstring.
The default value is: 24576. Any files containing more kilobytes than this
cannot be imported into BusinessObjects Intercompany.
4.Add zeros to change this value (e.g. 245760).
5.Save the file.
Authorizing log, txt and html extensions
BusinessObjects Intercompany generates files with the following extensions:
•.log
•.txt
•.html
Note: To find out how to authorize the extensions, see the Microsoft
documentation.
You may encounter errors when opening files with .log extensions.
To avoid these errors, proceed as follows:
1.Access the IIS management console.
2.Right-click the ICS5 virtual directory and select its Properties.
3.In the Web Sites Properties window, select the HTTP Headers tab.
4.Click the File Types button.
5.Click New Type.
6.In the Associated extension field, enter .log.
34Installation guide
Page 35
Single server installation
Installing BusinessObjects Intercompany
7.In the Content type field, enter the description of your choice.
8.Click OK.
Activating Microsoft DTC
If the database is installed on another machine or if you have performed an
installation on a multi server NLB cluster environment, you need to manually
configure MSDTC on the application and database servers. To configure
MSDTC, follow the procedure:
STEP 1 - CHECK THAT THE WINDOWS 2003 COMPONENTS HAVE BEEN INSTALLED
1.Select Add/Remove Programs > Add/Remove Windows Components
> Application Server.
2.Click Details.
3.Check that the following objects have been checked: Enable network
DTC access.
STEP 2 - CONFIGURE MSDTC
1.Run MSDTC –uninstall from command prompt to uninstall MSDTC.
2.Launch the Registry Editor by running regedit.exe.
3.Remove the MSDTC keys in HKLM/Software/Microsoft/MSDTC and
HKLM/System/CurrentControlSet/Services/MSDTC
4.Reboot the server.
5.Run the following DOS command:
6.Run the dcomcnfg command.
7.Select Component Services > My Computer and right-click it to open
My Computer Properties.
8.Select the MS DTC tab.
MSDTC -install
4
Installation guide35
Page 36
Single server installation
4
Installing BusinessObjects Intercompany
The following dialog box appears.
9.Click Security Configuration.
The following dialog box appears.
10. Check that the following options are selected:
36Installation guide
Page 37
Single server installation
Installing BusinessObjects Intercompany
•Network DTC Access
•Allow remote clients
•Allow remote Administration
•Allow Inbound
•Allow Outbound
•No Authentication Required
•Enable Transaction Internet Protocol (TIP) Transactions
•Enable XA transactions
4
Installation guide37
Page 38
Single server installation
4
Installing the BusinessObjects Intercompany Services
Installing the BusinessObjects Intercompany
Services
To in
stall the BusinessObjects Intercompany Services
1.Double-click Setup.exe located in the BusinessObjects Intercompany
Note: SMTP is the protocol used to send emails in BusinessObjects
Intercompany. When the application is installed in a multi-server environment,
SMTP needs to be configured on all the application servers.
4
Installation guide43
Page 44
Single server installation
4
Installing the license
Installing the license
To be able to use the application, you must copy the license file provided by
Business Objects to the root of the folder in which BusinessObjects
Intercompany is installed on the application server.
For example, copy the
Cartesis.ICS.LicenseManagement.CartesisLicensedClass.lic license file
into the installation folder C:\Program Files\Cartesis\Intercompany
5.1\ics5\licenses\.
44Installation guide
Page 45
Creating a SQL database
When you have finished installing BusinessObjects Intercompany for the first
time, you must create a database.
Note: The procedure below can be performed in the case of a multi-server
installation or in the case of a single server installation.
To create a database
1.In the Windows Start menu on the application server, select Programs >
2.In the Server dropdown menu, select the server on which you want to
create the database.
Note: In the case of a single server installation, i.e. the database server
is on the same machine as the application server, select (local).
3.In the User Name field, enter the SQL Server login.
4.In the Password field, enter the SQL server password.
5.Click the Connect button.
The connection to the specified SQL server is established when the DB
Name field, Location field and Create button are activated.
Note: An error message will appear if you did not enter the correct SQL
Server connection information. If this occurs, check with your system
administrator.
6.In the DB Name field, enter "IntercompanyDB".
Installation guide45
Page 46
Single server installation
4
Creating a SQL database
7.Click the button to the right of Location.
The Dialog Caption dialog box will appear. It lists all the disks available
on the specified server.
8.Select where you want to create the database.
9.Click OK.
10. Click the Create button.
Once you have created the database, the following message will appear:
Database Generation has been completed.
Note: The database you have just created is automatically linked to SQL
Server. You do not have to do it manually in SQL Enterprise Manager. To
check that the database is correctly linked in SQL Enterprise Manager,
you may have to refresh the screen.
Note: By default, the BusinessObjects Intercompany database created
contains one user: ADMIN. Its password is set to "123456". On the first
login attempt, this user will be forced to change its password.
46Installation guide
Page 47
Single server installation
Using the BusinessObjects Intercompany Oracle DB Manager
Using the BusinessObjects Intercompany
Oracle DB Manager
Oracle DB Manager allows you to create table spaces, users, objects and
schema for BusinessObjects Intercompany with Oracle.
Two tabs compose the BusinessObjects Intercompany Oracle DB Manager:
•One tab allows you to create an Oracle schema and its tablespaces.
Note: If you do not want to use this tool to create a schema, you can also
create it manually, following the recommendations contained in the
chapter “Oracle 10g engine settings” on page 24.
•One tab allows you to initialize an empty existing Oracle schema.
Note: This operation must be performed with the BusinessObjects
Intercompany Oracle DB Manager.
Creating an Oracle database
Connecting to BusinessObjects Intercompany Oracle DB Manager
You can create table spaces, users and schema for the BusinessObjects
Intercompany application by using the Oracle Database Configuration
Assistant.
1.Start the BusinessObjects Intercompany Oracle DB Manager from
Start > All Programs > BusinessObjects EPM > Programs >
BusinessObjects EPM Tools > Intercompany > Oracle DB Manager.
Note: To perform any operation you must log in to the database as a
user with SYSDBA privileges.
4
Installation guide47
Page 48
Single server installation
4
Using the BusinessObjects Intercompany Oracle DB Manager
The BusinessObjects Intercompany Oracle DB Manager dialog box
appears.
2.In the Connect as SYSDBA groupbox, enter the Sys User Name,
Password and TNS Name of the database you want to connect to and
click Connect.
If the information you specified is correct, the message Connected to
database successfully should appear.
3.Once you are connected, you can create table spaces and users.
Creating a Table Space
1.In the Create New Tablespace groupbox, enter the Tablespace Name
and the Size of the table space in MB.
2.If you want to create a temporary table, check the Temporary
Tablespace box.
48Installation guide
Page 49
Using the BusinessObjects Intercompany Oracle DB Manager
3.Click Create Tablespace.
Single server installation
4
Once the table space is created, the message Tablespace created
successfully will appear.
Warning: If you are creating a tablespace in a Unix environment, do not
forget to enter the correct syntax in the Location field (with /).
Warning: IThe Location field must always be completed with a / or \
depending of your environment, but not with a letter.
Tip: It is recommended to create a tablespace for data and one for
temporary tables.
Installation guide49
Page 50
Single server installation
4
Using the BusinessObjects Intercompany Oracle DB Manager
Creating a User
1.In the Create New User groupbox, enter the user name you want to
create and its password.
2.In the Tablespace Name dropdown list, select the default table space
you want to use.
3.In the Temp Tablespace dropdown list, select the temporary table space
you want to use.
4.Click Create User.
Once the table space is created, the message User created
successfully will appear.
Creating the BusinessObjects Intercompany schema
manually
If you do not want to use the Oracle DB Manager tool or if you are running
Oracle on a Unix system, you can create the schema manually.
50Installation guide
Page 51
Using the BusinessObjects Intercompany Oracle DB Manager
1.Create an Oracle user with a dedicated table space for data and a
temporary table space.
2.The minimum recommended size is 100 Mo for both table spaces.
3.This Oracle user account requires the following privileges: CONNECT,
RESOURCE.
Note: You must not assign the SELECT ANY TABLE privilege or assign
a role including this privilege (e.g. DBA) to this user.
Intializing an Oracle database
Once you have created the empty Oracle schema, you need to use the
Initialize tab in order to create the BusinessObjects Intercompany objects
(tables, indexes, stored procedures, etc.)
1.Connect to the BusinessObjects Intercompany Oracle DB Manager.
2.Select the Intialize Database tab.
The following dialog box appears.
Single server installation
4
Installation guide51
Page 52
Single server installation
4
Using the BusinessObjects Intercompany Oracle DB Manager
3.In the Initialize / Update Database groupbox, select the user who will be
the schema owner of the BusinessObjects Intercompany database
schema.
4.Enter the password this user will use to connect to the database.
5.Click Initialize DB.
Note: This operation can take several minutes.
Once the user is created, the message Database created successfully
appears.
Note: By default, the BusinessObjects Intercompany database created
contains one user: ADMIN. Its password is set to "123456". On the first
login attempt, this user will be forced to change its password.
52Installation guide
Page 53
Migrating an existing BusinessObjects Intercompany version
Migrating an existing BusinessObjects
Intercompany version
This version of Intercompany only supports SQL Server 2005 and Oracle 10g.
You must therefore migrate your database engine before migrating
Intercompany.
There is no specific migration procedure concerning the BusinessObjects
Intercompany setup. You must uninstall the BusinessObjects Intercompany
4.2 or 5.0 versions and then install the BusinessObjects Intercompany 5
version.
Single server installation
4
Installation guide53
Page 54
Single server installation
4
Migrating a SQL database
Migrating a SQL database
If you are upgrading your version of BusinessObjects Intercompany and you
already have a database, you should migrate it.
First check that the database has the correct collation type: the database
collation should be one that uses the 125X code page, e.g. the
Latin1_General collation with the 1252 code page. You should select a casesensitive (CS) and accent-sensitive (AS) sort order.
if you are upgrading from BusinessObjects Intercompany 4.x, your database
has probably the CI_AS sort order. This has to be changed. Contact the
Business Objects Support to get the procedure.
Note: The procedure below can be performed in the case of a multi-server
installation or in the case of a single server installation.
Warning: The upgrade tool can not migrate a SQL Server database to an
Oracle database.
Tip: Before starting the migration process, please take a complete back up of
the database you wish to upgrade. If the migration fails for any reason,
restore the backup and then try migrating the database again. Do not try to
migrate a database on which migration has already failed.
Procedure for a SQL 2000 database migration
1.Back up your BusinessObjects Intercompany database.
2.Uninstall SQL Server 2000.
3.Install SQL Server 2005 SP2.
4.Load the BusinessObjects Intercompany database you have backed up.
5.Modify the compatibility mode of your database to the 2005 mode (by
default, the dump will be loaded with the 2000 compatibility mode).
6.Continue with the standard procedure.
Standard procedure
1.Modify the compatibility mode of your database to the 2005 mode (by
default, the dump will be loaded with the 2000 compatibility mode).
2.In the Windows Start menu on the application server, select Start > All
6.In the Initialize / Update Database groupbox, select the Oracle TNS
7.Select the user of the BusinessObjects Intercompany database schema.
56Installation guide
Name of your Oracle instance.
Page 57
Single server installation
Migrating an Oracle database
8.Enter the password of this user.
The following warning message appears.
9.Click Yes .
Once the database has been migrated, a message appears indicating
that the migration has been completed.
10. Compile manually the stored procedures.
Warning: You should check that all procedures are compiled. It may be
not the case, you will therefore have to perform this task several times.
4
Installation guide57
Page 58
Single server installation
4
Connecting to the database
Connecting to the database
To connect to BusinessObjects Intercompany, you first need to create a
connection to the database. To create a connection to your database, you will
use the BusinessObjects Intercompany Control Panel.
You can access the BusinessObjects Intercompany Control Panel by clicking
on: Start > All Programs > BusinessObjects EPM > Programs >
BusinessObjects EPM Tools > Intercompany > Control Panel.
The Connections tab appears as shown below:
1.Click the Add button.
58Installation guide
To add a SQL Server connection
Page 59
Single server installation
Connecting to the database
The Add connection dialog box appears.
2.In the Connection Name field, enter a description to identify the
connection.
3.Select the SQL Server connection type.
Note: This description will appear in the BusinessObjects Intercompany
Administration tab.
4.In the Server Name dropdown menu, select the server on which the
database is stored. This menu lists the servers on which SQL Server is
installed.
5.In the Username field, enter the user name belonging to the SQL Server
database admin user.
6.In the Password field, enter the user's password.
7.In the Database Name dropdown menu, select the database you want to
add. The menu lists all the SQL databases stored on the selected server
appear.
8.Click OK.
4
To add an Oracle connection
1.Click the Add button.
Installation guide59
Page 60
Single server installation
4
Connecting to the database
The Add connection dialog box appears.
2.In the Connection Name field, enter a description to identify the
database.
3.Select the Oracle connection type.
Note: This description will appear in the BusinessObjects Intercompany
Administration tab.
4.In the Server Name dropdown menu, select the server on which the
database is stored.
5.In the Username field, enter the user name belonging to the Oracle
database admin user.
6.In the Password field, enter the user's password.
7.In the Databases field, enter the instance of the Oracle database you
want to add.
8.Click OK.
60Installation guide
Page 61
Single server installation
Logging in to BusinessObjects Intercompany
Logging in to BusinessObjects Intercompany
The application, the web server and the database server must be started
before you can log in to BusinessObjects Intercompany.
1.Open your browser.
2.Select Start > All Programs > BusinessObjects EPM >
BusinessObjects Intercompany.
3.Enter the user name and password.
4
4.Click the Login button.
The installation of BusinessObjects Intercompany is now complete.
Note: By default, the BusinessObjects Intercompany database contains
one user: ADMIN.
Warning: An error message may appear. If so, follow the procedure
below.
Installation guide61
Page 62
Single server installation
4
Logging in to BusinessObjects Intercompany
The following error message may appear:
5.In this case, restart the OracleMTSRecoveryService service on all the
62Installation guide
BusinessObjects Intercompany servers.
Page 63
Multiserver installation
chapter
Page 64
Multiserver installation
5
Overview
Overview
The multi server configuration allows the use of load balancing. With
BusinessObjects Intercompany, it is possible to use the Microsoft NLB cluster
solution, as it will load balance the connection between the different servers.
BusinessObjects Intercompany does not use session affinity as sessions are
directly managed in the database.
NLB is only one solution concerning multi-server. You can also use other load
balancing technology, like load balancing devices.
The multi-server installation consists in:
Installing the server hosting the ASP.NET state service
1.Install BusinessObiects Intercompany.
•Check the Clustered option.
•Check the ASP.NET State Service
2.Install the BusinessObiects Intercompany Services.
Installing the standard servers
1.Install BusinessObiects Intercompany.
•Check the Clustered option.
•During the setup, do not forget to indicate the ASP.NET state service
machine name.
•Configure loadbalancing (for example through the Microsoft NLB cluster).
64Installation guide
On all servers
Define a common shared folder that can be accessed from all servers
Page 65
Multiserver installation
Installing the server hosting the ASP.NET State Service
Installing the server hosting the ASP.NET
State Service
Warning: If you are performing a multi-server installation, we strongly
recommend against installing the different servers using the same disk image
(e.g. using a tool like Ghost). If you use the same image, the registry keys for
MS DTC (Microsoft Distributed Transaction Coordinator) remain unchanged
on the different servers even though they should be different on each one. As
a result, the servers cannot communicate with each other. To find out more,
see http://support.microsoft.com/kb/306843/en-us or http://
3.In the ASP.NET State Service’s Machine Name field, enter the name of
4.In the ASP.NET State Service’s Port Number field, enter the 42424
5.In the File Service’s Machine Name field, enter the name of the current
6.In the File Service’s Machine Port Number field, enter the 11111 value.
7.Check the ASP.NET State Service is running on this machine box.
8.Select the Clustered option.
9.Click Next.
66Installation guide
the current machine.
value.
machine.
Page 67
Multiserver installation
Installing the server hosting the ASP.NET State Service
The following dialog box appears.
10. Specify the shared folder name you previously configured to be accessed
from all Intercompany servers.
11. Continue the setup as indicated in “Installing BusinessObjects
Intercompany” on page 28.
12. Install the services by running the BusinessObjects Intercompany
Services setup as indicated in the chapter “Installing the
BusinessObjects Intercompany Services” on page 38.
5
Installation guide67
Page 68
Multiserver installation
5
Installing the standard servers
Installing the standard servers
Warning: If you are performing a multi-server installation, we strongly
recommend against installing the different servers using the same disk image
(e.g. using a tool like Ghost). If you use the same image, the registry keys for
MS DTC (Microsoft Distributed Transaction Coordinator) remain unchanged
on the different servers even though they should be different on each one. As
a result, the servers cannot communicate with each other. To find out more,
see http://support.microsoft.com/kb/306843/en-us or http://