IBM Cognos Dynamic Cubes

92 IBM Cognos Dynamic Cubes

Although a number of steps are required to manually deploy your cube, this approach might

be the correct approach to use if you are publishing to an environment other than a

development or test environment. Acceptance testing or production environments are tightly

controlled by administrators, so using the quick-deploy options might not be permitted.

The first required step is to publish the cube from Cognos Cube Designer without the

additional options selected. This approach creates a cube data source in Cognos Connection

and publishes your cube model to the Cognos content store. The Publish dialog contains an

option that must be set if your environment has security defined. Most environments, other

than a sandbox environment, have defined some kind of security. The cube you publish to

Cognos Connection requires an account to be specified if security is defined. If you do not set

it, the cube will not start. You can have Cognos Cube Designer associate your account with

the cube by clicking the Associate my account and signon with the cube datasource

check box. You must do an additional step of generating credentials. You do that by clicking

the First, you must create the credentials link in the Personal tab of the preferences dialog

in IBM Cognos Connection.

If a cube of the same name exists in the portal, you are prompted to confirm that you want to

continue to deploy the cube and overwrite the existing cube.

The remaining steps to deploy your dynamic cube are done in the IBM Cognos Administration

in Cognos Connection, so you might need to work with your system administrator. Detailed

steps to add your cube to a query service and start the cube are in Chapter 5, “Administering

dynamic cubes” on page 115.

After the cube is started, you then create a package in IBM Cognos Framework Manager to

publish to the content store to make the cube available for reporting and analysis. To do this,

create a new Framework Manager project and when prompted for a data source to use, select

the dynamic cube data source that was created during the publish step in Cognos Cube

Designer. The data source will inherit the name of the cube you published. The cube will be

imported into Framework Manager as a cube object, so you cannot expand the cube to see

the dimensions and levels in the cube. Create a package and add the cube object and then

publish the cube to the location of your choice in Cognos Connection. This process is

identical to creating a Framework Manager package using any other supported OLAP source

such as IBM Cognos TM1 or IBM Cognos Transformer PowerCubes.

4.12 Troubleshooting

This section provides information for troubleshooting metadata, publishing errors, and

members.

4.12.1 Importing metadata

Cognos Cube Designer models consist of a model file plus one or more metadata files. For

each schema that is imported into the model and used, a metadata file is created in the data

directory. The data directory is located in the directory where Cognos Framework Manager

and Cognos Cube Designer are installed.

When you open a model, Cognos Cube Designer attempts to load the metadata that is

specified in the data sources that have been used in the model. If it cannot load, it displays

the following message in the metadata viewer:

Select sources to include in the package