Configuring an in-cloud agent

You can configure an agent that resides in the Planning Analytics cloud.

Note: We recommend that you use an on-premises agent instead of an in-cloud agent.

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.

A diagram that shows a Cognos Command Center agent that resides in the Planning Analytics cloud.

Before you begin

You must load the Planning Analytics plugin before you configure the agent.
  1. In Cognos Command Center, select Tools > Manage Plugin Tasks.
  2. Select the IBM Cognos TM1 10.2.2.2 plugin zip file.
  3. Click Open.

Procedure

  1. Configure the corporate firewall of subdomain.domain.com.
    1. 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.
    2. Submit a ticket to the cloud ops team to find out the IP address of the Planning Analytics data computer.
    3. 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.
  2. Configure the Cognos Command Center Queue.
    1. In the Cognos Command Center client, select Tools > System Configuration.
    2. Click the Queue subsystem.
    3. For the External URI property, update the value of subdomain.domain.com
  3. Modify the file activemq.xml.
    1. Open the file activemq.xml, which is located in installation_directory\IBM\Cognos Command Center\Common\apache-activemq-5.8.0\conf\
    2. In the object transportConnector, replace the value of the uri attribute with the following text: "ssl://0.0.0.0:61617?transport.enabledProtocols=TLSv1,TLSv1.1,TLSv1.2"
    3. Save the file activemq.xml.
    4. Restart both the IBM Cognos Command Center Queue and the IBM Cognos Command Center Server Windows services.
  4. 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.

  5. 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: 
    • https://<environmentname>.planning-analytics.cloud.ibm.com/tm1/api/Planning Analytics/api/vi
    • https://<environmentname>.planning-analytics.cloud.ibm.com/tm1/api/PlanningAnalytics/api/vi

    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.