Connecting to server components and data sources

Whether you are installing DB2 OLAP Integration Server for the first time or upgrading from a previous release, after you start the console, the OLAP Metadata Catalog Setup dialog box is displayed. Using this dialog box, you can either create a catalog or upgrade an existing catalog.

An OLAP Metadata Catalog must be created and configured before you can connect to it:

After the process of creating or upgrading an OLAP Metadata Catalog is complete, you can begin to create OLAP models and metaoutlines. You must connect to Integration Server to an external data source and to the OLAP Metadata Catalog where you want to store the OLAP models and metaoutlines that you create.

To use Integration Services Console to perform data loads, member loads, or member and data loads, you must connect the client software to the server component of DB2 OLAP Server, which is called the Analytic Server.

You are prompted by the Login dialog box to connect to an Integration Server and an OLAP Metadata Catalog. Optionally, in the Login dialog box, you can also connect to an instance of Analytic Server and create default connection settings for both server components.

For information on troubleshooting connections to server components, see the Integration Services Administrator's Guide

Connecting to Integration Server

The Integration Server (which is the server component of DB2 OLAP Integration Server) manages access to OLAP Metadata Catalogs and to data sources. A catalog stores information that defines the external data source and the structure of OLAP model and metaoutline elements. To create an OLAP model or a metaoutline, you must connect to Integration Server.

The Integration Server system administrator must provide a user name and password to an OLAP Metadata Catalog before you can connect to the server.

To connect to Integration Server:

  1. To display the Login dialog box, from the OLAP Model main window or the Integration Services Console, select Connections > OLAP Metadata Catalog > Connect.

    The Login dialog box is displayed automatically when you start Integration Services Console. You can redisplay the Login dialog box by using the procedures described in this topic.

  2. In the Server drop-down list under Essbase Integration Services, type or select the name of an Integration Server computer; for example, cypress.

    If the port number on which DB2 OLAP Integration Server communicates with the console has been set to a value other than the default, you must type the server name or IP address and type the nonstandard port number, separated by a colon; for example:

    cypress:3390 
  3. In the OLAP Metadata Catalog drop-down list, select the name of an OLAP Metadata Catalog; for example, TBC_MD for the sample TBC (The Beverage Company) database.

    Oracle OCI: If you are using Oracle Call Interface (OCI) direct connection, you must specify the data source name in the format, Oracle:sid; for example: Oracle:TBC.

  4. In the Code Page drop-down list box, select the code page of the language you want to use during the current Integration Services Console session.

    The code page is a portion of the locale which identifies the local language and cultural conventions such as the formatting of currency and dates and the sort order of data.

  5. In the User Name drop-down list box under Essbase Integration Services, type or select your user name.

    It is necessary to type a user name the first time it is used. After a user is successfully connected to Integration Services, the user name is then displayed in the User Name drop-down list.

  6. In the Password text box under Essbase Integration Services, type your password.

    Use the same user name and password that you use to connect directly to the database server and to access the database that contains the OLAP Metadata Catalog.

  7. Click OK or enter information for connecting to an instance of Analytic Server; see Connecting to Analytic Server.

Connecting to Analytic Server

Analytic Server (which is the server component of DB2 OLAP Server) creates and manages OLAP databases. You do not have to connect Integration Services Console to Analytic Server to create an OLAP model or metaoutline, but you must connect to Analytic Server to view a sample OLAP outline or to load members or data into an OLAP database.

In the Login dialog box, you can specify the information for connecting to Analytic Server, but Integration Services Console does not connect to Analytic Server until you attempt to view a sample outline or to load members or data.

If you plan to use the Integration Services Console on a client computer that is outside the firewall for your network, and the console requires that Integration Server and Analytic Server be located inside the firewall for your network, you must log on to Analytic Server with a name or an IP address that connects from both sides of the firewall. The system administrator provides you with this name or IP address.

The system administrator for Analytic Server must provide you with a user name and password before you can connect.

To set connection information for an instance of Analytic Server:

  1. In the OLAP Metaoutline main window, select Connections > OLAP Metadata Catalog > Connect to display the Login dialog box.

    The Login dialog box is displayed automatically when you start Integration Services Console. You can redisplay the Login dialog box at any time while working in the OLAP Metaoutline main window by using the procedures described in this topic.

  2. In the Server text box under Essbase Analytic Server, type or select the name of a computer that is running Analytic Server; for example, sequoia.

    If you are using Integration Services Console on a client computer that is outside the firewall for your network, and you require access to instances of Integration Server and Analytic Server located inside the firewall for your network, be sure to use a name or an IP address for the instance of Analytic Server that is accessible from both sides of the firewall.

  3. In the User Name drop-down list box under Essbase Analytic Server, type or select your DB2 OLAP Server user name. It is necessary to type a user name the first time it is used. After a user is successfully connected to Analytic Server, the user name is then displayed in the User Name drop-down list.
  4. In the Password text box under Essbase Analytic Server, type your DB2 OLAP Server password.
  5. Click OK.

Setting connection defaults

If you typically use a specific instance of Integration Server, OLAP Metadata Catalog, and Analytic Server, you can save the settings as the default. After you set default connection information, you can reuse these settings without reentering the information.

If you use multiple instances of Integration Server and OLAP Metadata Catalogs, you can also set multiple relationships and select the appropriate one to use so that you do not need to reenter the information.

To set connection defaults:

  1. To display the Login dialog box, in the OLAP Model main window or OLAP Metaoutline main window, select Connections > OLAP Metadata Catalog > Connect.
  2. In the Login dialog box, click Set Login Defaults The Set Login Defaults dialog box is displayed.
  3. In the Server text box, type or select the name of an Integration Server computer; for example, cypress.
  4. In the OLAP Metadata Catalog text box, type or select the name of an OLAP Metadata Catalog; for example, TBC_MD for the sample TBC database.
  5. In the Code Page drop-down list box, select the code page of the language you want to use for this Integration Services Console session. The code page is a portion of the locale which identifies the local language and cultural conventions such as the formatting of currency and dates and the sort order of data.
  6. In the User Name text box, type or select a user name for the OLAP Metadata Catalog.
  7. Take one of the following actions:
  8. In the Default Server text box, type or select the name of an Analytic Server computer; for example, cypress.
  9. In the Default User Name text box, type or select a user name for the instance of Analytic Server; for example, TBC.
  10. Click OK to return to the Login dialog box.

Connecting to data sources

A data source is an external data repository, such as large database, whose data you want to analyze by using DB2 OLAP Server. You must connect DB2 OLAP Integration Server to all data sources that you plan to use in creating OLAP models and metaoutlines and in loading data into an OLAP database.

You can connect to more than one relational data source to create OLAP models.

To connect to a data source:

  1. In the Integration Services Console Welcome dialog box, click the appropriate icon to create a new OLAP model or metaoutline. Alternatively, select the Existing or Recent tab and double-click an OLAP model or metaoutline to open it for editing. The Data Source dialog box is displayed.
  2. In the Data Source drop-down list, select the data source to be used; for example, TBC in the sample application.

    An ODBC data source must be created on the computer that is running Integration Server for any external data sources that you want to use. With the exception of Oracle Call Interface (OCI) direct connection, if the data source that you need is not visible in the scroll list, contact the Integration Services system administrator.

    For more information about troubleshooting server and data source connections, see the Integration Services System Administrator's Guide.

    Oracle OCI: If you are using Oracle OCI direct connection, be sure to prefix the Net Service Name (found in the tnsnames.ora file) or the Schema Name (if you are using onames) with Oracle (by typing: Oracle:) and then the Net Service Name or Schema Name.

    The following example is a Net Service Name stanza that defines TBC in the tnsnames.ora file:

    TBC =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = labmachine2)(PORT = 1521))
    )
    (CONNECT_DATA =
    (SERVICE_NAME = orasid)
    )
    )

    For Oracle using onames, in the example above, TBC is the Schema Name used to connect to an Oracle database. This is the database identifier that you use when you are using SQL *Plus to connect to a database.

    DataDirect Drivers: If you are using DataDirect drivers with Oracle, pick a data source name from the Data Source drop-down list.

  3. In the Code Page drop-down list box, select the code page of the language you want to use during the current Integration Services Console session, and click OK. The code page is a portion of the locale which identifies the local language and cultural conventions such as the formatting of currency and dates and the sort order of data.
  4. In the User Name drop-down list box, type or select your user name.
  5. In the Password text box, type your password.
  6. Click OK.
  7. The left frame of the OLAP Model main window initially displays information about the first data source to which you connected. Data source information is displayed hierarchically by data source name and owner name.
  8. For each owner name, data is further sorted and organized by tables, views, and synonyms. You can use the listed source tables to create an OLAP model or use additional source tables by connecting to other data sources.
  9. Information about subsequent data sources to which you connect is displayed in the same manner as information about the first connected data source was displayed; that is, by data source name and owner name, then tables, views, and synonyms.
  10. Expand the plus sign, +, to display tables, views, and synonyms contained in the data source.

If you want to connect to additional data sources, complete the steps in the following procedure:

  1. Select Connections > Add Data Sources. The Data Source dialog box is displayed. You can connect to any number of available data sources without closing this dialog box.
  2. In the Data Source drop-down list, select the additional data source to which you want to connect.

    Oracle OCI: If you are using OCI direct connection, be sure to prefix the Net Service Name or the Schema Name with Oracle by typing Oracle: and then the data source name.

    If you are using DataDirect drivers with Oracle, pick a data source name from the Data Source drop-down list.

  3. In the Code Page drop-down list box, select the code page of the language you want to use during the current Integration Services Console session, and click OK.
  4. In the User Name drop-down list box, type or select your user name. It is necessary to type a user name the first time it is used. After a user is successfully connected to a data source, the user name is then displayed in the User Name drop-down list.
  5. In the Password text box, type your password and click Connect. The left frame of the OLAP Model main window displays information about the data source to which you just connected along with information about the first data source to which you connected.
  6. Repeat step 2 through step 3 for each data source to which you want to connect. As you connect to additional data sources, the left frame of the OLAP Model main window displays information about all data sources to which you are connected.
  7. When you finish connecting to all appropriate data sources, click Close.

Reconnecting when connections are lost

If a connection is lost to Integration Server and OLAP Metadata Catalog, you can reconnect without losing any unsaved work on the OLAP models or metaoutlines.

To reconnect to Integration Server and OLAP Metadata Catalog:

  1. Start Integration Server using one of the methods described in Starting the Integration Server on Windows or Starting Integration Server on UNIX.
  2. In the Integration Services Console, select Connections > OLAP Metadata Catalog > Reconnect.

The connection is made automatically. No messages are displayed, and you do not need to reenter information in the Login dialog box.