Configuring an in-cloud agent
You can configure an agent that resides in the Planning Analytics cloud.
However, with an in-cloud agent, you can perform the following tasks that an on-premises agent cannot run:
- Run an executable or a batch file.
- Monitor networking ports.
- Manage files.
The following diagram shows a Cognos Command Center agent that resides in the Planning Analytics cloud.
Before you begin
- In Cognos Command Center, select .
- Select the IBM Cognos TM1 10.2.2.2 plugin zip file.
- Click Open.
Configure the corporate firewall of
Forward inbound traffic TCP port 61617 to
192.168.1.200 port 61617
Tip: In this example, 192.168.1.200 is the internal ip address of CCC server.
- Submit a ticket to the cloud ops team to find out the IP address of the Planning Analytics data computer.
Block all inbound traffic except traffic that comes from the Planning Analytics cloud computer
for port 61617.
Note: Port 61617 is used by CCC Queue in this document. You specify this port number when you install Cognos Command Center.
- Forward inbound traffic TCP port 61617 to 192.168.1.200 port 61617
Configure the Cognos Command Center Queue.
- In the Cognos Command Center client, select .
- Click the Queue subsystem.
- For the External URI property, update the value of subdomain.domain.com
Modify the file activemq.xml.
- Open the file activemq.xml, which is located in installation_directory\IBM\Cognos Command Center\Common\apache-activemq-5.8.0\conf\
In the object
transportConnector, replace the value of the
uriattribute with the following text:
- Save the file activemq.xml.
- Restart both the IBM Cognos Command Center Queue and the IBM Cognos Command Center Server Windows services.
Create an agent. See Setting up an agent in the Cognos Command Center server.
Tip: If you receive the following error, revisit Step 1.
Failed to receive reply event from agent through the message queue. Timeout while waiting on event from agent.
Add a computing resource. See Setting up a computing resource in the Cognos Command Center server.
In the Server endpoint field, enter a value with this format:
https://hostname.planning-analytics.cloud.ibm.com/tm1/api/tm1_server_name/api/v1/Note: If your TM1 server name includes a space, Planning Analytics creates two endpoints that you can use to connect to the server; one with a space in the server name and one without a space in the server name. For example, if you have a server named Planning Sample, both of these server endpoints are available:
Some third-party applications might not be able to connect to a TM1 server with spaces in the name. If you encounter difficulty connecting to a server with spaces in the name, try using the endpoint without spaces in the server name.