The previous article introduced the installation and deployment of the IBM Cognos Business Intelligence Development edition. However, studies have found that ESRI maps for COGNOS cannot be installed on the Development edition, therefore, the Enterprise Edition installation and deployment were reorganized.
Software deployment is divided into several steps to install media preparation
Install Oracle 11g Release 2 (11.2) for Microsoft Windows x64 (64-bit)
This step is skipped directly, note that the character set is set to UTF-8 in installation options during installation.
Install Oracle 11g R2 Client
You can install the database by default. After the database is installed, the client can connect to the database server.
Note: The Oracle database server and Cognos can be deployed separately. However, the Cognos client must be a 32-bit client that corresponds to the Oracle version and cannot be installed with 64-bit.
Install IBM Cognos businessintelligence server v10.1.1 (32-bit)
The issetup.exe under the double-hitting installation media directory is basically one way to next:
Click Finish to exit the installation process. You can directly start IBM Cognos configuration, or start IBM Cognos configuration in the Start Menu.
Keep default parameters and start the service directly. Click Start in the upper left corner.
Error
The reason is that the connection to the Content Manager database is not configured. Here we select Oracle database for configuration, delete the original content store, right-click Content Manager, and choose "New Resource"> "Database ".
Enter the name as needed. Select Oracle database as the type.
Click "OK" and enter the parameters for Oracle database connection: Server Name, port number, user name, password, and Oracle database instance name.
Click OK and then right-click Oracle ----- Test
If the preceding error occurs, Cognos cannot find the Oracle database driver. We need to install the Oracle database client corresponding to the database server in the client directory ...... Under \ product \ 11.2.0 \ client_1 \ JDBC \ Lib, copy the ojdbc5.jar and ojdbc6.jar files to the Cognos installation directory .... \ IBM \ Cognos \ C10 \ webapps \ p2pd \ WEB-INF \ Lib, open IBM cognosconfiguration in the Start menu, and save
Then perform the connection test. The result is:
Click Start in the upper left corner of IBM cognosconfiguration to start the service.
So far, the Cognos service has been started successfully.
Note: if an error occurs in this step, click details to indicate that the Content Manager configuration is incorrect because the database configuration is incorrect. Here, we emphasize the requirements for configuring the Content Manager Database: create a user on the database server and grant the DBA permission to create its default tablespace. For example:
Create tablespace Cognos datafile 'd: \ app \ yuyouxiang \ oradata \ orcl \ Cognos. dbf' size 100 m autoextend on;
Create user Cognos identified by cognosdefault tablespace Cognos;
Grant connect, resource, DBA to Cognos;
Installation lessons: Before starting the service, configure the above database requirements. The content store connection test is successful, but the service cannot be started successfully, because the service is started to create n tables in the database.
In addition, if Cognos contentdatabase is selected during installation
You do not need to configure the above databases.
After the service is successfully started, enter http: // localhost: 9300/p2pd/servlet/dispatch in the browser.
The first time we enter the Cognos web interface, many styles on the Web page do not exist, because we use the Tomcat that comes with Cognos to start the web application, we need to set C: all content in the \ Program Files \ IBM \ Cognos \ C10 \ webcontent directory is copied to the C: \ Program Files \ IBM \ Cognos \ C10 \ webapps \ p2pd directory, then refresh the browser address, and then the Cognos development interface will be fully displayed.
Finally, a welcome page is provided.
Install ibm_cognos framework Manager
Framework is used to develop report model release packages. As a model developer, you only need to install the framework installer on the local machine, configure the gateway information, and direct it to the address of the Cognos Report Server. In this way, you can publish the model developed on the framework to the specified server.
In the installation media folder, select Win32 ---- issetup.
Next until the process is completed.
Install IBM Cognos samples_10.1.1
The installation process is mainly to obtain the Oracle database backup files of samples data, and finally restore these backup files to the Oracle database.
In the installation media folder, select Win32
Run issetup
All the way to next until the installation is complete
Installation is complete. The installation sample is located:
C: \ Program Files (x86) \ IBM \ Cognos \ C10 \ webcontent \ Samples
The datasource \ oracle in this path contains the DMP data file of sample data. In the subsequent configuration, the DMP data backup file will be imported to Oracle.
Post install ---- sample data import after installation and Cognos database connection and configuration sample database recovery
The data to be imported includes
Database or schema description |
Oracle |
Cstatd |
Cstatd. dmp |
Great Outdoors sales |
Gosales. dmp |
Great Outdoors Retailers |
Gosalesrt. dmp |
Great Outdoors sales data warehouse |
Gosalesdw. dmp |
Great Outdoors market research |
Gosalesmr. dmp |
Great Outdoors Human Resources |
Gosaleshr. dmp |
Cstatd is located in c: \ Program Files (x86) \ IBM \ Cognos \ C10 \ webcontent \ samples \ datasources \ oracle
The remaining four DMPS are stored in the data folder decompressed by gs_db_ora.tar.
Make the following preparations before importing data:
· Create a database with the same name as DMP, which is sensitive to size.
· Create a user with select permission
· Use UTF-8 encoding on the database server.
· Modify the client environment variables. Run set nls_lang = american_america.utf8 in windows.
Log on to the database as an administrator and execute the following database scripts:
Create tablespace cstatd datafile 'd: \ app \ yuyouxiang \ oradata \ orcl \ cstatd. dbf' size 50 m autoextend on;
Create tablespace gosales datafile 'd: \ app \ yuyouxiang \ oradata \ orcl \ gosales. dbf' size 100 m autoextend on;
Create tablespace gosalesrt datafile 'd: \ app \ yuyouxiang \ oradata \ orcl \ gosalesrt. dbf' size 5 m autoextend on;
Create tablespace gosalesdw datafile 'd: \ app \ yuyouxiang \ oradata \ orcl \ gosalesdw. dbf' size 200 m autoextend on;
Create tablespace gosalesmr datafile 'd: \ app \ yuyouxiang \ oradata \ orcl \ gosalesmr. dbf' size 25 m autoextend on;
Create tablespace gosaleshr datafile 'd: \ app \ yuyouxiang \ oradata \ orcl \ gosaleshr. dbf' size 25 m autoextend on;
Create user cstatd identified by cstatddefault tablespace cstatd;
Grant connect, resource, DBA to cstatd;
Create user gosales identified by gosalesdefault tablespace gosales;
Grant connect, resource, DBA to gosales;
Create user gosalesrt identified bygosalesrt default tablespace gosalesrt;
Grant connect, resource, DBA to gosalesrt;
Create user gosalesdw identified bygosalesdw default tablespace gosalesdw;
Grant connect, resource, DBA to gosalesdw;
Create user gosalesmr identified bygosalesmr default tablespace gosalesmr;
Grant connect, resource, DBA to gosalesmr;
Create user gosaleshr identified bygosaleshr default tablespace gosaleshr;
Grant connect, resource, DBA to gosaleshr;
Open CMD and execute Database Import:
IMP cstatd/cstatd @ orclfile = D: \ DMP \ cstatd. dmp log = D: \ imp_cstatd.log full = y
IMP gosales/gosales @ orclfile = D: \ DMP \ gosales. dmp log = D: \ imp_gosales.log full = y
IMP gosalesrt/gosalesrt @ orclfile = D: \ DMP \ gosalesrt. dmp log = D: \ imp_gosalesrt.log full = y
IMP gosalesdw/gosalesdw @ orclfile = D: \ DMP \ gosalesdw. dmp log = D: \ imp_gosalesdw.log full = y
IMP gosalesmr/gosalesmr @ orclfile = D: \ DMP \ gosalesmr. dmp log = D: \ imp_gosalesmr.log full = y
IMP gosaleshr/gosaleshr @ orclfile = D: \ DMP \ gosaleshr. dmp log = D: \ imp_gosaleshr.log full = y
Execute the gs_or_modify.sqlscript to adjust the relationship between users, under the data folder decompressed by gs_db_ora.tar
So far, the sample data import is complete.
Create a data source connection for the sample database
Open BM Cognos Administration
Select Configuration
Click create data source in the upper right corner.
Enter the name great_outdoors_sales, and then select the data source type.
Enter the Oracle database instance name, user name, and password (gosales), and click test connection.
The test is successful.
In this way, the data source great_outdoors_sales is created successfully. Repeat the preceding operation to create a database connection named great_outdoors_warehouse. Select "gosalesdw" as the data source"
Create a cube data source
Enter sales_and_marketing_zh.
Select IBM Cognos powercube as the data source
In the new data source wizard, enter
C: \ ProgramFiles (x86) \ IBM \ Cognos \ C10 \ webcontent \ samples \ datasources \ cubes \ powercubes \ ZH \ sales_and_marketing_zh.mdc
Click "test"
Test successful
Click Finish.
Repeat the preceding steps to create the other five data sources. MDC is in the same folder.
Import sample content
Include the sample content in the c: \ Program Files (x86) \ IBM \ Cognos \ C10 \ webcontent \ samples \ content
Here we only import ibm_cognos_samples.zipw.ibm_cognos_powercube.zip
First copy it to c: \ Program Files (x86) \ IBM \ Cognos \ C10 \ deployment
Choose create import in the upper-right corner of configuration> content management.
Select one of them, such as ibm_cognos_samples.
All the way to "Next" to complete and run.
At this point, we have completed importing ibm_cognos_samples.zip.
The same formula can be used to import ibm_cognos_powercube.zip backup.
View the imported report file
Import images
The reports developed in simple use other images.
\ IBM \ Cognos \ C10 \ webcontent \ samples \ images folder copy
Under \ IBM \ Cognos \ C10 \ webapps \ p2pd \ Samples
Running example