Ibm®cognos®business FDI is a multi-tier architecture product that can be divided into three tiers: Web servers, business tiers, and data tiers. These three layers can be isolated through a network firewall. The Cognos BI User Interface (browser and Fat client) is located on the three floor. As shown in Figure 1:
Figure 1. Ibm®cognos®business FDI Architecture
The IBM Cognos BI Gateway runs on the WEB server layer, primarily to receive client requests and to be forwarded to Dispatcher. Dispatcher,application RS and Contentmanager are located at the business level, primarily dealing with business logic, such as storing user settings, running reports, and working. Data tier is mainly responsible for storage and query, content inventory put metadata, reports, etc., query database can be a relational database containing business data, files, OLAP cubes and other physical storage sources.
Deploying Cognos BI 10 under IBM http://www.aliyun.com/zixun/aggregation/13387.html ">websphere"
1 Prerequisites
1.1 Before installing Cognos BI 10, you can visit the IBM website http://www-01.ibm.com/support/docview.wss?uid=swg27027080 to view software support information. After you have installed Cognos, make sure that the Cognos Content Library is configured correctly:
Installation directory:/ibm/softwares/cognos/c10_64
Gateway software: Apache Http Server
Gateway Port: 80
Host Name: Fpru
Java_home:/opt/ibm/websphere/appserver/java
As shown in Figure 2:
Figure 2. Cognos Content Library Configuration validation
If you plan to deploy with a distributed server, you will need to install different components of Cognos CM,ACT,GW on separate paths. For example Content Manager:/ibm/softwares/cognos/c10_64/cm, creator Tier Component:/ibm/softwares/cognos/c10_64/act, Gateway:/IBM/SOFTWARES/COGNOS/C10_64/GW
1.2 Install IBM WebSphere, install IBM WebSphere 7.0 and the necessary patches on Linux.
2 modifying URI configuration in Cognos revisit
2.1 Open Cognos revisit, under Linux can execute $Cognos _install/bin64/cogconfig.sh, (note: need to set Java_home). After opening, click Environnement in the left navigation tree to modify the port in the Dispather and Content Manager URI, as shown in Figure 3:
Figure 3. Modify URL configuration information
3 Creating WebSphere and Configuration Profile
3.1 Advanced into the $WAS _installation/appserver/bin directory, execute the following command to create the profile. The profile filename COG102 to deploy the P2pd.war. Run the command./manageprofiles.sh-create-profilename cog102-profilepath/opt/ibm/websphere/appserver/profiles/cog102- Templatepath/opt/ibm/websphere/appserver/profiletemplates/default-enableadminsecurity False–validateports when appearing was When the profile creates a successful message, it indicates that the profile was created successfully, as shown in Figure 4:
Figure 4. Creating an IBM WebSphere profile