Install and configure IBM®
WebSphere® Application Server Network Deployment on the
computer hosting IBM
Cognos® Business Intelligence and also configure a new
profile for Cognos, so that the server can be managed by the Deployment Manager used with IBM Connections.
About this task
The WebSphere node
hosting the Cognos BI server
will be federated to the same dedicated Deployment Manager as your IBM Connections deployment. Do not
use a WebSphere node that
has already been federated to a different Deployment Manager.
Note: For
IBM i, install IBM WebSphere Application Server Base on AIX to host
IBM Cognos Business Intelligence.
Procedure
- Install WebSphere Application
Server Network Deployment as described in the WebSphere Application
Server Version 8.5.5 knowledge center.
Use WebSphere Customization Toolbox
to create an Application server type profile. It will be federated
to the Deployment Manager by the Cognos Installation
wizard.
If you will use a server where the appropriate version
of WebSphere Application
Server Network Deployment is already deployed, you do not have to
install it again; just create a new Application server profile for Cognos Business Intelligence
with WebSphere Customization
Toolbox, or run the WAS command as follows:
IBM AIX®, Linuxmanageprofiles.sh -create -templatepath WAS_install_root/profileTemplates/default -adminUserName was_admin_name -adminPassword was_admin_password -profileName cognosProfile -nodeName CognosNode01
Microsoft Windowsmanageprofiles.bat -create -templatepath WAS_install_root\profileTemplates\default -adminUserName was_admin_name -adminPassword was_admin_password -profileName cognosProfile -nodeName CognosNode01
You can verify that the installation was successful
by reviewing the WebSphere Application
Server log stored in:
Cognos_WAS_node_profile/logs/Cognos_server_name/SystemOut.log;
for example on Windows:
C:\Program Files\IBM\WebSphere\AppServer\profiles\cognosProfile\logs\cognos_server\SystemOut.log
- On the newly installed server, set the system clock to
match the time (and time zone) on the Deployment Manager's computer.
Attention: The node's clock must be synced to within
1 minute of the Deployment Manager's clock to ensure that federation
does not fail in a later task.