Starting Integration Server

Before starting Integration Server, verify all required components are running. These components need not be on your local computer. Also, verify that these components are running:

The relational database management system (RDBMS) with the relational data source containing the OLAP Metadata Catalog where the metadata is stored
One or more RDBMSs containing the relational data sources you want to use to create or modify an OLAP model or metaoutline

Essbase Server must be running if you create, change, or load data into an Essbase database or if you want to preview an Essbase database outline.

You can start Integration Server using several methods:

From a DOS command prompt
From a UNIX command prompt
From the Windows Desktop Start menu

As a Windows service

Note:

To start Integration Server as a Windows service, you must have configured it as a Windows service during the configuration process. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

To start Integration Server from DOS:

At the command line, type the startup.bat command.
The startup.bat command ensures the environment is set correctly and that proper PATH and CLASSPATH settings are used when starting Integration Server.
If you want to change a default startup switch, add the switch to the ais.cfg file or the startup.bat file.
If you want to change a default configuration parameter, add the parameter to the ais.cfg file.

See Storing Startup Information in the Configuration File and Storing Startup Information in the Startup File (Windows Only) for information on adding startup switches and configuration parameters to files.

To start Integration Server from UNIX:

Type is.sh .

Type the executable name on the command line, for example, type

olapisvr

Note:

If Integration Server does not start when olapisvr is executed from the command line, the operating system path may not be updated correctly. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

If you want to change a default startup switch, type the command syntax after the olapisvr command or add the switches to the ais.cfg file.
See Storing Startup Information in the Configuration File and Storing Startup Information in the Startup File (Windows Only) for information on adding startup switches to these files.
Values for startup switches entered at the command line override startup switch values stored in the ais.cfg file.
When entering parameters for startup switches at the command line, enclose path names that contain spaces in quotation marks (" "). The following example illustrates the syntax for passing the -E and -M options:
```
olapisvr -E"c:\my logs\eislog" -M"c:\ess\bin\essbase.mdb"
```

To start Integration Server from the Windows Desktop Start menu:

Click Start.
Select All Programs, then Oracle EPM System, then Essbase, then Integration Services, then Server.
If startup switch settings are stored in startup.bat or ais.cfg, the settings in startup.bat override the settings in ais.cfg when Integration Server is started from the Windows Desktop Start menu.

To start Integration Server as a Windows service:

Access the Services dialog box in Windows.
Double-click Essbase Integration Server to start the service.
The Service Control message box is displayed. After a few seconds it is removed, and the Status field entry for Integration Server is changed to Started.
If you want to change any default startup switches or configuration parameters, add the switches to the ais.cfg file or the startup.bat file.