You can configure an agent that resides on an on-premises Cognos Command Center
server.
Tip: We recommend that you use an on-premises agent instead of an in-cloud agent. This
setting allows you to automate TM1, Email, FTP, SFTP and Oracle tasks in just a few clicks.
Restriction: If you use an on-premises agent in the planning analytics cloud
environment, you cannot perform these tasks:
- run an executable or a batch file
- monitor networking ports
- manage files
The following diagram shows a Cognos Command Center agent that is configured on an on-premises
Cognos Command Center server.
Before you begin
The TM1 9.5.2 plugin is loaded by default. However, only the TM1 10.2.2.2 plugin is
compatible with Planning Analytics in the cloud. Therefore, you must load the TM1 10.2.2.2 plugin
before you configure the agent.
- In Cognos Command Center, select .
- Select the IBM Cognos TM1 10.2.2.2 plugin zip file.
- Click Open.
Procedure
-
Create an agent. See Setting up an agent in the Cognos Command Center server.
-
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.
