|The computer hosting the IBM® Cognos® Business Intelligence server must be federated to the same dedicated Deployment Manager used by IBM Connections.
Before you begin
Before attempting to federate the Cognos
node to the Deployment Manager, make sure that:
- The Deployment Manager is running.
- The Cognos server is stopped (if you started it after installation, stop it now by stopping the IBM WebSphere Application Server hosting it).
- The system clock on the Cognos server is set to within 1 minute of the time (and time zone) of the system clock on the Deployment Manager.
- The Deployment Manager and the Cognos server are either both registered in the DNS or are referenced in each other’s etc/hosts file.
About this task
This task involves working on the newly installed Cognos
Business Intelligence server to add the node to the Deployment Manager, and then working on the Deployment Manager to create virtual ports for the new node.
- On the Deployment Manager, disable Java 2 security:
- Log into the Integrated Solutions Console as the WebSphere® administrator.
- Click Security -> Global Security
- Look under Java 2 security and clear the selection for Use Java 2 security to restrict application access to local resources.
- Click Apply.
- Click OK.
- Use the computer hosting the Cognos components to federate the new node to the Deployment Manager:
- On the computer hosting Cognos, open a command window and navigate to the /bin directory in the WebSphere Application Server installation root; for example:
Run the addNode command to federate the node to the Deployment Manager as in the following example:
- IBM AIX®, Linux™: /opt/IBM/WebSphere/AppServer/bin
- Microsoft Windows™: C:\Program Files\IBM\WebSphere\AppServer\bin
Now start the node agent by running the startNode command (from within the same directory); for example:
addNode.bat|sh DM_host_name DM_port -profileName Cognos_profile_name -includeapps -username DM_admin_user_name -password DM_admin_password
- DM_host_name is the fully qualified host name of the Deployment Manager.
- DM_port is the SOAP_CONNECTOR port that the Deployment Manager is listening on; the default port is 8879.
You can determine the port by checking the SOAP_CONNECTOR_ADDRESS
value in the following file on the computer hosting the Deployment Manager:
; for example on Windows
- Cognos_profile_name is the profile name where Cognos Business Intelligence is installed (in case multiple profiles are installed on the same server).
If you only installed one WebSphere profile on the server, you can omit this parameter.
If you are not sure of the Cognos profile name, you can determine it by looking at the directory name where it was installed; for example on Linux
- DM_admin_user_name is the user name of the WebSphere administrator account on the Deployment Manager, and DM_admin_password is the associated password.
Make sure you specify the -includeapps
parameter as shown in the example.
addNode.bat lc40.example.com 8879 -profileName AppSrv01 -includeapps -username wasadmin -password my_WASadmin_pwd
Synchronize the new node to the Deployment Manager:
- AIX or Linux: startNode.sh
- Windows: startNode.bat
Check the virtual host settings on the Deployment Manager and verify that the Cognos server port is included. For more information and a workaround, see the technote: SRVE0255E: A WebGroup/Virtual Host to handle /p2pd/servlet/dispatch
Start the Cognos server.
- On the navigation tree, click System Administration -> Nodes.
- In the nodes table, click the checkbox that precedes the new node (the Cognos server).
- Click the Synchronize button in the table and wait for the operation to finish before proceeding to the next step.
Synchronization might take several minutes to complete; be sure to allow sufficient time before restarting the Cognos server in the next task.
Parent topic: Installing Cognos Business Intelligence for Metrics reporting
Previous topic: Configuring Cognos Business Intelligence after installation
Next topic: Validating the Cognos BI server installation