API tools faq
paste
Advertisement
Guest User

my_cognos_tm1_cfg_file

a guest
Jul 9th, 2014
761
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 36.51 KB | None | 0 0
raw download clone embed print report
  1. ## Licensed Materials - Property of IBM
  2. ##
  3. ## IBM Cognos Products: TM1
  4. ##
  5. ## (C) Copyright IBM Corp. 2007, 2012
  6. ##
  7. ## US Government Users Restricted Rights - Use, duplication or
  8. ## disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
  9.  
  10. [TM1S]
  11. # ServerLogging
  12. # Generates a log with the security activity details on the TM1 server that are associated with Integrated Login. The log file, named Tm1server.log, is saved to the TM1 server data directory. The ServerLogging parameter is useful only if your TM1 server is configured to use Integrated Login.
  13. # Type: Optional, Static
  14. #
  15. # Set ServerLogging to T in Tm1s.cfg. Note also that if ServerLogging=T is set, you must rename the TM1 server message logfile tm1server.log by editing the corresponding parameter in the logger configuration file tm1s-log.properties file.
  16. ServerLogging=F
  17.  
  18.  
  19. # Security package name
  20. # If you configure the TM1 server to use Integrated Login, the SecurityPackageName parameter defines the security package that authenticates your user name and password in Windows.
  21. # Type: Optional, Static
  22. #
  23. # Valid values are:
  24. # * Kerberos (default) - Windows 2000 or later.
  25. # * NTLM - Older Windows installations, such as Windows NT.
  26. #SecurityPackageName=Kerberos
  27.  
  28.  
  29. # Security mode
  30. # Type: optional, static
  31. #
  32. #
  33. # If IntegratedSecurityMode is set to 1. All clients must provide a database
  34. # username and password. This is traditionally done through a login screen.
  35. #
  36. # If IntegratedSecurityMode is set to 2. The clients will have the choice
  37. # to connect provide a database username and password or use the single-login
  38. # mechanism for authentication.
  39. #
  40. # If IntegratedSecurityMode is set to 3. All clients must use the single-login
  41. # mechanism for authentication.
  42. #
  43. # If IntegratedSecurityMode is set to 4. The server uses IBM Cognos 8 security authentication.
  44. #
  45. # If IntegratedSecurityMode is set to 5. The server uses IBM Cognos 8 security authentication and supports user groups from both TM1 and Cognos 8.
  46. #
  47. # If this is not set the parameter will be set to 1 by default.
  48. IntegratedSecurityMode=4
  49.  
  50.  
  51. # UseSSL
  52. # Enables or disables SSL on the TM1 server.
  53. # Type: Optional/Required to use SSL, Static
  54. # Set UseSSL=T to enable SSL. With this setting, only TM1 9.1 and later clients will be able to securely connect to the server.
  55. # Set UseSSL=F to disable SSL. With this setting, all TM1 clients, including older clients that do not support SSL, will be able to connect to the server in insecure mode.
  56. # When UseSSL=T, you must set several other Tm1s.cfg parameters that manage SSL implementation. For details on these parameters, see Running TM1 in Secure Mode Using SSL.
  57. # Default is UseSSL=T
  58. #UseSSL=F
  59.  
  60.  
  61. # Server name to register with the Admin Server. If you do not supply this parameter, TM1 names the server Local and treats it as a local server.
  62. # Type: Optional, Static
  63. ServerName=CubeServer
  64.  
  65.  
  66. # Location of TM1 database
  67. # Type: Required, static
  68. # Specifies the data directory from which the server loads cubes, dimensions, and other objects. You can list multiple data directories by separating them with semicolons.
  69. #
  70. # Example:
  71. # DataBaseDirectory=C:\Program Files\Cognos\TM1\Custom\TM1Data\PlanSamp\
  72. DataBaseDirectory=C:\tm1_data\CubeServer
  73.  
  74.  
  75. # AdminHost
  76. # Specifies the computer name or IP address of the Admin Host on which an Admin Server is running
  77. # Type: Required, Static
  78. # You can specify multiple Admin Hosts by separating each host name with a semicolon on a Windows TM1 server, or a colon on a UNIX TM1 server. For example:
  79. # * Use the format AdminHost=hostname1;hostname2 on a Windows TM1 server.
  80. # * Use the format AdminHost=hostname1:hostname2 on a UNIX TM1 server.
  81. #
  82. # Some examples include:
  83. # * AdminHost=boston;newyork
  84. # * AdminHost=192.168.1.17;192.168.1.22
  85. # * AdminHost=boston;192.168.1.17;192.168.1.22;myserver;192.168.1.40
  86. #
  87. #Note: The string specifying the admin host(s) is limited to 1020 characters or bytes.
  88. # If set to empty than use localhost
  89. AdminHost=
  90.  
  91.  
  92. # TM1 Server Port
  93. # Sets the server port number used to distinguish between multiple servers running on the same computer. When multiple TM1 servers are installed on a single computer, each server must use a unique port number.
  94. # Type: Optional, Static
  95. # When you install a TM1 server, the default port number is 12345. Valid port values are between 5000 and 49151
  96. #
  97. # If the Tm1s.cfg file does not contain the PortNumber parameter, the TM1 server uses port 5000. Local TM1 servers use port 5000. The port used for Client Messages must also be a unique port number and is set to 5001 by default when the ClientMessagePortNumberparameter is used.
  98. PortNumber=35516
  99.  
  100.  
  101. # ClientMessagePortNumber
  102. # Identifies a secondary port used to accept client messages concerning the progress and ultimate cancellation of a lengthy operation without tying up thread reserves.
  103. # Type: optional, dynamically set/Sstatic for changes
  104. # This additional port ensures that other server requests can continue to process while waiting for a cancellation from the user.
  105. #
  106. # By default, this port number is automatically and dynamically assigned when the TM1 server starts. You do not have to set ClientMessagePortNumber to a specific number unless firewalls or other network issues require the listener port to be a well-known number.
  107. #
  108. # Note: Be sure to assign unique port numbers for the server and client message ports. If you have two servers running on the same machine with the same port number, the message activity may cause a system failure.
  109. ClientMessagePortNumber=
  110.  
  111.  
  112. # Sets the language used in the TM1 interface. You can use this to override the current locale settings
  113. # Type: Optional, Static
  114. #
  115. # Valid values are:
  116. # * ENG - English
  117. # * FRA - French
  118. # * DEU - German
  119. # * JPN - Japanese
  120. # * SCH - Simplified Chinese
  121. # * ITA - Italian
  122. # * ESP - Spanish
  123. #Language=ENG
  124.  
  125.  
  126. # Savetime
  127. # Sets the time of day to execute an automatic save of server data; saves the cubes every succeeding day at the same time. As with a regular shutdown, SaveTime renames the log file, opens a new log file, and continues to run after the save.
  128. # The Savetime parameter is not available when running the TM1 server as a Windows service.
  129. # The format of the SaveTime parameter is dd:hh:mm where:
  130. # * dd is the number of days from today that the system will start automatically saving data. For example, 00 is today, 01 is tomorrow.
  131. # * hh:mm is the time of day in 24-hour format.
  132. # Type: optional, dynamic
  133. Savetime=
  134.  
  135.  
  136. # Downtime
  137. # Specifies a time when the server will come down automatically.
  138. # The Downtime parameter is not available when running the TM1 server as a Windows service.
  139. # The format of the Downtime parameter is dd:hh:mm where:
  140. # * dd is the number of days from today that the system will start automatically saving data. For example, 00 is today, 01 is tomorrow.
  141. # * hh:mm is the time of day in 24-hour format.
  142. # When you use the DownTime parameter on the UNIX TM1 server, you must set the RunningInBackground parameter to T. If RunningInBackground=F, the server prompts for confirmation before shutting down and cannot shut down without manual confirmation from an administrator.
  143. # Type: optional, dynamic
  144. Downtime=
  145.  
  146.  
  147. # ProgressMessage
  148. # This parameter determines whether users have the option to cancel lengthy view calculations. When a user opens a view that takes a significant amount of time to calculate (usually a view with high levels of consolidation or complex rules), TM1 monitors the progress of the process. When ProgressMessage=T a dialog box opens that allows the user to Stop Building View.
  149. # Type: Optional, Static
  150. #
  151. # If the user clicks Stop Building View, the view is discarded on the client, but view calculation continues on the server. In some instances, this can tie up the server.
  152. # If ProgressMessage=F, the Stop Building View option is not offered and the user cannot cancel lengthy operations. This setting helps avoid potential server tie ups in versions 9.1 SP3 through 9.4.
  153. # When ProgressMessage=T or is not present in the Tm1s.cfg file, the Stop Building View option opens during lengthy view calculations so the user can cancel the process if necessary. For versions 9.4 or later, the user can assign a unique Port Number using ClientMessagePortNumber. This additional port allows these progress messages to travel via a secondary port so that server processing can continue without tying up thread reserves.
  154. # Note: To avoid potentially tying up servers, TM1 9.1 SP3 through 9.4 have ProgressMessage=F inserted into the Tm1s.cfg file during server installation. As of TM1 9.4, progress messages can travel via the secondary port assigned by ClientMessagePortNumber so TM1 9.4 and later have ProgressMessage=T set by default. This parameter has been tested with Citrix when this feature was redesigned.
  155. ProgressMessage=True
  156.  
  157.  
  158. # AuditLogOn
  159. # Turns audit logging on (T) or off (F).
  160. # Type: Optional, Static
  161. AuditLogOn=F
  162.  
  163.  
  164. # AuditLogMaxFileSize
  165. # Indicates the maximum file size that an audit log file can grow to before it is closed and a new file is created.
  166. # Type: Optional, Dynamic
  167. # This value must include units of KB (kilobytes), MB (megabytes), or GB (gigabytes).
  168. # Default value: 100 MB
  169. # Minimum value: 1 KB
  170. # Maximum value: 2 GB
  171. AuditLogMaxFileSize= 100 MB
  172.  
  173.  
  174. # AuditLogUpdateInterval
  175. # Indicates the maximum amount of time, in minutes, that TM1 waits before moving the events from the temporary audit file into the final audit log.
  176. # Type: Optional, Dynamic
  177. # This value must include units of KB (kilobytes), MB (megabytes), or GB (gigabytes).
  178. # Default value: 60 (sixty minutes)
  179. # Minimum value: 1 (one minute)
  180. AuditLogUpdateInterval=60
  181.  
  182.  
  183. #PersistentFeeders
  184. # Turn on Persistent Feeders to make TM1 models load faster
  185. # Type: Optional, Static
  186. PersistentFeeders=F
  187.  
  188.  
  189. # ParallelInteraction
  190. # Enables Cube Versioning AKA MVCC
  191. ParallelInteraction=T
  192.  
  193.  
  194. # ServerCAMURI
  195. # Specifies the URI for the internal dispatcher that the TM1 server should use to connect to CAM. The URI is specified in the form http[s]://host IP address:port/p2pd/servlet/dispatch.
  196. # Type: Optional, Static
  197. # No default
  198. # For example,
  199. #
  200. # http://10.121.25.121:9300/p2pd/servlet/dispatch
  201. # or
  202. # https://10.121.25.121:9300/p2pd/servlet/dispatch
  203. ServerCAMURI=http://myserver.mycompany.com:9300/p2pd/servlet/dispatch
  204.  
  205.  
  206. # ClientCAMURI
  207. # The URI for the IBM Cognos Server IBM Cognos Connection used to authenticate TM1 clients. The URI is specified in the form http[s]://host/cognos8/cgi-bin/cognos.cgi.
  208. # Type: Optional, Static
  209. # No default
  210. # Example: http://10.121.25.121/cognos8/cgi-bin/cognos.cgi
  211. ClientCAMURI=https://myserver.mycompany.com:443/ibmcognos/cgi-bin/cognos.cgi
  212.  
  213.  
  214. # ClientPingCAMPassport
  215. # Indicates the interval, in seconds, that a client should ping the CAM server to keep their passport alive.
  216. # Type: Optional, Static
  217. # If an error occurs or the passport expires the user will be disconnected from the TM1 server.
  218. ClientPingCAMPassport=900
  219.  
  220.  
  221. ## Optional CAM parameters
  222.  
  223. # CAMSSLCertificate
  224. # Type: Optional/Required only when CAM server is configured with SSL, Static
  225. # The full path and name of the SSL certificate to be used when connecting to the internal dispatcher. For example, C:\AxTM1\Install_Dir\ssl\CognosCert.cer.
  226. #CAMSSLCertificate=
  227.  
  228.  
  229. # CAMSSLCertRevList
  230. # CAM SSL Certificate Rev List
  231. #CAMSSLCertRevList=
  232.  
  233.  
  234. # Skip SSL CAM Host Check
  235. # Indicates whether the SSL certificate ID confirmation process can be skipped. The default is FALSE.
  236. # Type: Optional, Static
  237. # Important: This parameter should be set to TRUE only if using a generic certificate for demonstration purposes.
  238. SkipSSLCAMHostCheck=TRUE
  239.  
  240.  
  241. ## Optional LDAP Settings
  242.  
  243. # PasswordSource
  244. # Determines the source of authentication
  245. # Type: Optional, Static
  246. # Two options:
  247. # * TM1 (default) - Compares the user-entered password to the password in the TM1 database.
  248. # * LDAP - Compares the user-entered password to the password stored in on the LDAP server.
  249. #PasswordSource=LDAP
  250.  
  251.  
  252. # LDAPPort
  253. # TM1 attempts to bind to an LDAP server on the specified secure port. If you do not enter an LDAPPort value, TM1 uses the default value, port 636
  254. # Type: Optional, Static
  255. # This must be a secure (SSL) port.
  256. #LDAPPort=636
  257.  
  258.  
  259. # LDAPHost
  260. # Uses the domain name or dotted string representation of the IP address of the LDAP server host. If you do enter a value for LDAPHost, TM1 uses the default value, localhost.
  261. # Type: Optional, Static
  262. #LDAPHost=localhost
  263.  
  264.  
  265. # LDAPUseServerAccount
  266. # Determines if a password is required to connect to the server when using LDAP authentication.
  267. # Type: Optional
  268. # To connect directly to the LDAP server using integrated authentication, set this parameter to T. Set this parameter to T whenever the IBM Cognos TM1 server and LDAP server exist on the same domain.
  269. # To use a password before connecting, set this parameter to F. When LDAPUseServerAccount is set to F, you must also set the LDAPPasswordFile and LDAPPasswordKeyFile to successfully connect to the LDAP server using SSL.
  270. #LDAPUseServerAccount=T
  271.  
  272.  
  273. # LDAPSearchBase
  274. # A base distinguished name (DN) in the LDAP directory. For example:
  275. # ou=people,o=company.com
  276. # Specifies the node in the LDAP tree at which the search for the TM1 user being validated begins. For example, if the distinguished names are of the form:
  277. # uid-bjensen, ou-people, o=company.com
  278. #
  279. # then the search base would be:
  280. # ou-people, o=company.com
  281. # This is a required field if using LDAP Authentication.
  282. #LDAPSearchBase=cn=users,dc=company,dc=com
  283.  
  284.  
  285. # LDAPSearchField
  286. # cn
  287. # The name of the LDAP attribute that is expected to contain the name of the TM1 user being validated. If you do not enter an LDAPSearchField value, the default value is cn, which is also the default value for Microsoft Active Directory.
  288. #LDAPSearchField=cn=user
  289.  
  290.  
  291. # IPVersion
  292. # Select IPv4 or IPv6
  293. # Sets IP protocol.
  294. # Type: Optional, Static
  295. #
  296. # Three options:
  297. # * ipv4 - use ipv4 (default)
  298. # * ipv6 - use ipv6
  299. # * dual - use ipv6 with support for ipv4
  300. IPVersion=ipv4
  301.  
  302.  
  303. # AllowSeparateNandCRules
  304. # Specifies expressions for N: and C: levels on separate lines using identical AREA definitions, maintaining the rules conventions of TM1.
  305. # Type: Optional, Static
  306. #
  307. # For example,
  308. #
  309. # ['Budget','Argentina']=N:Expression;
  310. #
  311. # ['Budget','Argentina']=C:Expression;
  312. #
  313. # are both valid rules statements when you include the AllowSeparateNandCRules parameter in the Tm1s.cfg file and set to T.
  314. #
  315. # This parameter also effects how numeric and string rules are applied to cells. Without this parameter, the first rule statement that is encountered for a given AREA definition is applied to the cells within the scope of that definition. If any cell within the AREA definition is numeric and the rule is a string rule, then the cell is considered not rule-derived because there was a match that did not apply to the cell.
  316. #
  317. # For example, consider the statements:
  318. #
  319. # ['1 Quarter']=s:'str_value';Not following.
  320. #
  321. # ['1 Quarter']=n:77;
  322. #
  323. # If the AllowSeparateNandCRules parameter is not set (or is set to F), then the first rule statement will match any cell that uses ‘1 Quarter’ as one of its elements. If the cell is a string cell, the value of the cell will be set to “str_value”. If the cell is a numeric cell, the cell will not be considered rule derived, since a match was found (the first rule) but the rule itself did not apply.
  324. #
  325. # If the AllowSeparateNandCRules parameter is set to T, then string cells which use ‘1 Quarter’ will be set to “str_value” and numeric cells which use ‘1 Quarter’ will be set to 77.
  326. AllowSeparateNandCRules=T
  327.  
  328. # DistributedPlanningOutputDir
  329. # Type: Optional, Static
  330. # This parameter defines the directory to which 'TUnits' are written when an application is 'deployed'. This call is made as part of Cognos Deskop deploying an application which will allow a client to open a distributed client.
  331. #DistributedPlanningOutputDir=.\tunit
  332.  
  333. # CalculationThresholdForStorage
  334. # Defines a minimum number of rule calculations required for a single cell or Stargate view, beyond which the TM1® server stores the calculations for use during the current server session.
  335. # Type: Optional, Dynamic
  336. # For example, when a user requests rule-derived values from the TM1 server, either from a single cell or a Stargate view, the server usually has to perform multiple rule calculations to arrive at the requested rule-derived values.
  337. #
  338. # CalculationThresholdForStorage has a direct effect on memory consumption and performance. A high parameter value results in decreased memory consumption and slower performance. A low parameter value results in increased memory consumption and faster performance.
  339. #
  340. # If you do not include CalculationThresholdForStorage in Tm1s.cfg, the default calculation threshold is 50.
  341. #CalculationThresholdForStorage=50
  342.  
  343. # GroupsCreationLimit
  344. # Sets the maximum number of groups that can be created in one TM1® server session.
  345. # Type: Optional, Static
  346. # Note: The GroupsCreationLimit server configuration parameter pre-allocates
  347. # memory and should not be set higher than needed. Please see TM1 technical
  348. # bulletin: GroupsCreationLimit Recommendations for more information on
  349. # how this parameter works.
  350. # The GroupsCreationLimit parameter accepts a value of any positive integer. The maximum number of groups for GroupsCreationLimit is 65535. The maximum number of groups that can exist on a server is 65535. If you do not use the parameter, the default number of groups is 20.
  351. #
  352. # For example, to create 50 groups per server session, enter the following line:
  353. #
  354. # GroupsCreationLimit=50
  355. #
  356. # Note: When TM1 allocates memory to store security information, the server calculates the amount of memory required based in part on the value of GroupsCreationLimit. In some circumstances when your TM1model is large and the GroupsCreationLimit parameter is set to an exceptionally high value, the server will attempt to allocate memory beyond the available capacity on the server. The TM1 server will fail to load and will issue a Server Out of Memory message. To avoid this situation, set GroupsCreationLimit to a value that accurately reflects the maximum number of user groups you may need to create during a server session.
  357. #
  358. # The GroupsCreationLimit value is not enforced when you create groups with the AddGroup function in TurboIntegrator.
  359. GroupsCreationLimit=600
  360.  
  361. # ping cam
  362. ClientPintCAMPassport=43200
  363. ## Licensed Materials - Property of IBM
  364. ##
  365. ## IBM Cognos Products: TM1
  366. ##
  367. ## (C) Copyright IBM Corp. 2007, 2012
  368. ##
  369. ## US Government Users Restricted Rights - Use, duplication or
  370. ## disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
  371.  
  372. [TM1S]
  373. # ServerLogging
  374. # Generates a log with the security activity details on the TM1 server that are associated with Integrated Login. The log file, named Tm1server.log, is saved to the TM1 server data directory. The ServerLogging parameter is useful only if your TM1 server is configured to use Integrated Login.
  375. # Type: Optional, Static
  376. #
  377. # Set ServerLogging to T in Tm1s.cfg. Note also that if ServerLogging=T is set, you must rename the TM1 server message logfile tm1server.log by editing the corresponding parameter in the logger configuration file tm1s-log.properties file.
  378. ServerLogging=F
  379.  
  380.  
  381. # Security package name
  382. # If you configure the TM1 server to use Integrated Login, the SecurityPackageName parameter defines the security package that authenticates your user name and password in Windows.
  383. # Type: Optional, Static
  384. #
  385. # Valid values are:
  386. # * Kerberos (default) - Windows 2000 or later.
  387. # * NTLM - Older Windows installations, such as Windows NT.
  388. #SecurityPackageName=Kerberos
  389.  
  390.  
  391. # Security mode
  392. # Type: optional, static
  393. #
  394. #
  395. # If IntegratedSecurityMode is set to 1. All clients must provide a database
  396. # username and password. This is traditionally done through a login screen.
  397. #
  398. # If IntegratedSecurityMode is set to 2. The clients will have the choice
  399. # to connect provide a database username and password or use the single-login
  400. # mechanism for authentication.
  401. #
  402. # If IntegratedSecurityMode is set to 3. All clients must use the single-login
  403. # mechanism for authentication.
  404. #
  405. # If IntegratedSecurityMode is set to 4. The server uses IBM Cognos 8 security authentication.
  406. #
  407. # If IntegratedSecurityMode is set to 5. The server uses IBM Cognos 8 security authentication and supports user groups from both TM1 and Cognos 8.
  408. #
  409. # If this is not set the parameter will be set to 1 by default.
  410. IntegratedSecurityMode=4
  411.  
  412.  
  413. # UseSSL
  414. # Enables or disables SSL on the TM1 server.
  415. # Type: Optional/Required to use SSL, Static
  416. # Set UseSSL=T to enable SSL. With this setting, only TM1 9.1 and later clients will be able to securely connect to the server.
  417. # Set UseSSL=F to disable SSL. With this setting, all TM1 clients, including older clients that do not support SSL, will be able to connect to the server in insecure mode.
  418. # When UseSSL=T, you must set several other Tm1s.cfg parameters that manage SSL implementation. For details on these parameters, see Running TM1 in Secure Mode Using SSL.
  419. # Default is UseSSL=T
  420. #UseSSL=F
  421.  
  422.  
  423. # Server name to register with the Admin Server. If you do not supply this parameter, TM1 names the server Local and treats it as a local server.
  424. # Type: Optional, Static
  425. ServerName=CubeServer
  426.  
  427.  
  428. # Location of TM1 database
  429. # Type: Required, static
  430. # Specifies the data directory from which the server loads cubes, dimensions, and other objects. You can list multiple data directories by separating them with semicolons.
  431. #
  432. # Example:
  433. # DataBaseDirectory=C:\Program Files\Cognos\TM1\Custom\TM1Data\PlanSamp\
  434. DataBaseDirectory=C:\tm1_data\CubeServer
  435.  
  436.  
  437. # AdminHost
  438. # Specifies the computer name or IP address of the Admin Host on which an Admin Server is running
  439. # Type: Required, Static
  440. # You can specify multiple Admin Hosts by separating each host name with a semicolon on a Windows TM1 server, or a colon on a UNIX TM1 server. For example:
  441. # * Use the format AdminHost=hostname1;hostname2 on a Windows TM1 server.
  442. # * Use the format AdminHost=hostname1:hostname2 on a UNIX TM1 server.
  443. #
  444. # Some examples include:
  445. # * AdminHost=boston;newyork
  446. # * AdminHost=192.168.1.17;192.168.1.22
  447. # * AdminHost=boston;192.168.1.17;192.168.1.22;myserver;192.168.1.40
  448. #
  449. #Note: The string specifying the admin host(s) is limited to 1020 characters or bytes.
  450. # If set to empty than use localhost
  451. AdminHost=
  452.  
  453.  
  454. # TM1 Server Port
  455. # Sets the server port number used to distinguish between multiple servers running on the same computer. When multiple TM1 servers are installed on a single computer, each server must use a unique port number.
  456. # Type: Optional, Static
  457. # When you install a TM1 server, the default port number is 12345. Valid port values are between 5000 and 49151
  458. #
  459. # If the Tm1s.cfg file does not contain the PortNumber parameter, the TM1 server uses port 5000. Local TM1 servers use port 5000. The port used for Client Messages must also be a unique port number and is set to 5001 by default when the ClientMessagePortNumberparameter is used.
  460. PortNumber=35516
  461.  
  462.  
  463. # ClientMessagePortNumber
  464. # Identifies a secondary port used to accept client messages concerning the progress and ultimate cancellation of a lengthy operation without tying up thread reserves.
  465. # Type: optional, dynamically set/Sstatic for changes
  466. # This additional port ensures that other server requests can continue to process while waiting for a cancellation from the user.
  467. #
  468. # By default, this port number is automatically and dynamically assigned when the TM1 server starts. You do not have to set ClientMessagePortNumber to a specific number unless firewalls or other network issues require the listener port to be a well-known number.
  469. #
  470. # Note: Be sure to assign unique port numbers for the server and client message ports. If you have two servers running on the same machine with the same port number, the message activity may cause a system failure.
  471. ClientMessagePortNumber=
  472.  
  473.  
  474. # Sets the language used in the TM1 interface. You can use this to override the current locale settings
  475. # Type: Optional, Static
  476. #
  477. # Valid values are:
  478. # * ENG - English
  479. # * FRA - French
  480. # * DEU - German
  481. # * JPN - Japanese
  482. # * SCH - Simplified Chinese
  483. # * ITA - Italian
  484. # * ESP - Spanish
  485. #Language=ENG
  486.  
  487.  
  488. # Savetime
  489. # Sets the time of day to execute an automatic save of server data; saves the cubes every succeeding day at the same time. As with a regular shutdown, SaveTime renames the log file, opens a new log file, and continues to run after the save.
  490. # The Savetime parameter is not available when running the TM1 server as a Windows service.
  491. # The format of the SaveTime parameter is dd:hh:mm where:
  492. # * dd is the number of days from today that the system will start automatically saving data. For example, 00 is today, 01 is tomorrow.
  493. # * hh:mm is the time of day in 24-hour format.
  494. # Type: optional, dynamic
  495. Savetime=
  496.  
  497.  
  498. # Downtime
  499. # Specifies a time when the server will come down automatically.
  500. # The Downtime parameter is not available when running the TM1 server as a Windows service.
  501. # The format of the Downtime parameter is dd:hh:mm where:
  502. # * dd is the number of days from today that the system will start automatically saving data. For example, 00 is today, 01 is tomorrow.
  503. # * hh:mm is the time of day in 24-hour format.
  504. # When you use the DownTime parameter on the UNIX TM1 server, you must set the RunningInBackground parameter to T. If RunningInBackground=F, the server prompts for confirmation before shutting down and cannot shut down without manual confirmation from an administrator.
  505. # Type: optional, dynamic
  506. Downtime=
  507.  
  508.  
  509. # ProgressMessage
  510. # This parameter determines whether users have the option to cancel lengthy view calculations. When a user opens a view that takes a significant amount of time to calculate (usually a view with high levels of consolidation or complex rules), TM1 monitors the progress of the process. When ProgressMessage=T a dialog box opens that allows the user to Stop Building View.
  511. # Type: Optional, Static
  512. #
  513. # If the user clicks Stop Building View, the view is discarded on the client, but view calculation continues on the server. In some instances, this can tie up the server.
  514. # If ProgressMessage=F, the Stop Building View option is not offered and the user cannot cancel lengthy operations. This setting helps avoid potential server tie ups in versions 9.1 SP3 through 9.4.
  515. # When ProgressMessage=T or is not present in the Tm1s.cfg file, the Stop Building View option opens during lengthy view calculations so the user can cancel the process if necessary. For versions 9.4 or later, the user can assign a unique Port Number using ClientMessagePortNumber. This additional port allows these progress messages to travel via a secondary port so that server processing can continue without tying up thread reserves.
  516. # Note: To avoid potentially tying up servers, TM1 9.1 SP3 through 9.4 have ProgressMessage=F inserted into the Tm1s.cfg file during server installation. As of TM1 9.4, progress messages can travel via the secondary port assigned by ClientMessagePortNumber so TM1 9.4 and later have ProgressMessage=T set by default. This parameter has been tested with Citrix when this feature was redesigned.
  517. ProgressMessage=True
  518.  
  519.  
  520. # AuditLogOn
  521. # Turns audit logging on (T) or off (F).
  522. # Type: Optional, Static
  523. AuditLogOn=F
  524.  
  525.  
  526. # AuditLogMaxFileSize
  527. # Indicates the maximum file size that an audit log file can grow to before it is closed and a new file is created.
  528. # Type: Optional, Dynamic
  529. # This value must include units of KB (kilobytes), MB (megabytes), or GB (gigabytes).
  530. # Default value: 100 MB
  531. # Minimum value: 1 KB
  532. # Maximum value: 2 GB
  533. AuditLogMaxFileSize= 100 MB
  534.  
  535.  
  536. # AuditLogUpdateInterval
  537. # Indicates the maximum amount of time, in minutes, that TM1 waits before moving the events from the temporary audit file into the final audit log.
  538. # Type: Optional, Dynamic
  539. # This value must include units of KB (kilobytes), MB (megabytes), or GB (gigabytes).
  540. # Default value: 60 (sixty minutes)
  541. # Minimum value: 1 (one minute)
  542. AuditLogUpdateInterval=60
  543.  
  544.  
  545. #PersistentFeeders
  546. # Turn on Persistent Feeders to make TM1 models load faster
  547. # Type: Optional, Static
  548. PersistentFeeders=F
  549.  
  550.  
  551. # ParallelInteraction
  552. # Enables Cube Versioning AKA MVCC
  553. ParallelInteraction=T
  554.  
  555.  
  556. # ServerCAMURI
  557. # Specifies the URI for the internal dispatcher that the TM1 server should use to connect to CAM. The URI is specified in the form http[s]://host IP address:port/p2pd/servlet/dispatch.
  558. # Type: Optional, Static
  559. # No default
  560. # For example,
  561. #
  562. # http://10.121.25.121:9300/p2pd/servlet/dispatch
  563. # or
  564. # https://10.121.25.121:9300/p2pd/servlet/dispatch
  565. ServerCAMURI=http://myserver.mycompany.com:9300/p2pd/servlet/dispatch
  566.  
  567.  
  568. # ClientCAMURI
  569. # The URI for the IBM Cognos Server IBM Cognos Connection used to authenticate TM1 clients. The URI is specified in the form http[s]://host/cognos8/cgi-bin/cognos.cgi.
  570. # Type: Optional, Static
  571. # No default
  572. # Example: http://10.121.25.121/cognos8/cgi-bin/cognos.cgi
  573. ClientCAMURI=https://myserver.mycompany.com:443/ibmcognos/cgi-bin/cognos.cgi
  574.  
  575.  
  576. # ClientPingCAMPassport
  577. # Indicates the interval, in seconds, that a client should ping the CAM server to keep their passport alive.
  578. # Type: Optional, Static
  579. # If an error occurs or the passport expires the user will be disconnected from the TM1 server.
  580. ClientPingCAMPassport=900
  581.  
  582.  
  583. ## Optional CAM parameters
  584.  
  585. # CAMSSLCertificate
  586. # Type: Optional/Required only when CAM server is configured with SSL, Static
  587. # The full path and name of the SSL certificate to be used when connecting to the internal dispatcher. For example, C:\AxTM1\Install_Dir\ssl\CognosCert.cer.
  588. #CAMSSLCertificate=
  589.  
  590.  
  591. # CAMSSLCertRevList
  592. # CAM SSL Certificate Rev List
  593. #CAMSSLCertRevList=
  594.  
  595.  
  596. # Skip SSL CAM Host Check
  597. # Indicates whether the SSL certificate ID confirmation process can be skipped. The default is FALSE.
  598. # Type: Optional, Static
  599. # Important: This parameter should be set to TRUE only if using a generic certificate for demonstration purposes.
  600. SkipSSLCAMHostCheck=TRUE
  601.  
  602.  
  603. ## Optional LDAP Settings
  604.  
  605. # PasswordSource
  606. # Determines the source of authentication
  607. # Type: Optional, Static
  608. # Two options:
  609. # * TM1 (default) - Compares the user-entered password to the password in the TM1 database.
  610. # * LDAP - Compares the user-entered password to the password stored in on the LDAP server.
  611. #PasswordSource=LDAP
  612.  
  613.  
  614. # LDAPPort
  615. # TM1 attempts to bind to an LDAP server on the specified secure port. If you do not enter an LDAPPort value, TM1 uses the default value, port 636
  616. # Type: Optional, Static
  617. # This must be a secure (SSL) port.
  618. #LDAPPort=636
  619.  
  620.  
  621. # LDAPHost
  622. # Uses the domain name or dotted string representation of the IP address of the LDAP server host. If you do enter a value for LDAPHost, TM1 uses the default value, localhost.
  623. # Type: Optional, Static
  624. #LDAPHost=localhost
  625.  
  626.  
  627. # LDAPUseServerAccount
  628. # Determines if a password is required to connect to the server when using LDAP authentication.
  629. # Type: Optional
  630. # To connect directly to the LDAP server using integrated authentication, set this parameter to T. Set this parameter to T whenever the IBM Cognos TM1 server and LDAP server exist on the same domain.
  631. # To use a password before connecting, set this parameter to F. When LDAPUseServerAccount is set to F, you must also set the LDAPPasswordFile and LDAPPasswordKeyFile to successfully connect to the LDAP server using SSL.
  632. #LDAPUseServerAccount=T
  633.  
  634.  
  635. # LDAPSearchBase
  636. # A base distinguished name (DN) in the LDAP directory. For example:
  637. # ou=people,o=company.com
  638. # Specifies the node in the LDAP tree at which the search for the TM1 user being validated begins. For example, if the distinguished names are of the form:
  639. # uid-bjensen, ou-people, o=company.com
  640. #
  641. # then the search base would be:
  642. # ou-people, o=company.com
  643. # This is a required field if using LDAP Authentication.
  644. #LDAPSearchBase=cn=users,dc=company,dc=com
  645.  
  646.  
  647. # LDAPSearchField
  648. # cn
  649. # The name of the LDAP attribute that is expected to contain the name of the TM1 user being validated. If you do not enter an LDAPSearchField value, the default value is cn, which is also the default value for Microsoft Active Directory.
  650. #LDAPSearchField=cn=user
  651.  
  652.  
  653. # IPVersion
  654. # Select IPv4 or IPv6
  655. # Sets IP protocol.
  656. # Type: Optional, Static
  657. #
  658. # Three options:
  659. # * ipv4 - use ipv4 (default)
  660. # * ipv6 - use ipv6
  661. # * dual - use ipv6 with support for ipv4
  662. IPVersion=ipv4
  663.  
  664.  
  665. # AllowSeparateNandCRules
  666. # Specifies expressions for N: and C: levels on separate lines using identical AREA definitions, maintaining the rules conventions of TM1.
  667. # Type: Optional, Static
  668. #
  669. # For example,
  670. #
  671. # ['Budget','Argentina']=N:Expression;
  672. #
  673. # ['Budget','Argentina']=C:Expression;
  674. #
  675. # are both valid rules statements when you include the AllowSeparateNandCRules parameter in the Tm1s.cfg file and set to T.
  676. #
  677. # This parameter also effects how numeric and string rules are applied to cells. Without this parameter, the first rule statement that is encountered for a given AREA definition is applied to the cells within the scope of that definition. If any cell within the AREA definition is numeric and the rule is a string rule, then the cell is considered not rule-derived because there was a match that did not apply to the cell.
  678. #
  679. # For example, consider the statements:
  680. #
  681. # ['1 Quarter']=s:'str_value';Not following.
  682. #
  683. # ['1 Quarter']=n:77;
  684. #
  685. # If the AllowSeparateNandCRules parameter is not set (or is set to F), then the first rule statement will match any cell that uses ‘1 Quarter’ as one of its elements. If the cell is a string cell, the value of the cell will be set to “str_value”. If the cell is a numeric cell, the cell will not be considered rule derived, since a match was found (the first rule) but the rule itself did not apply.
  686. #
  687. # If the AllowSeparateNandCRules parameter is set to T, then string cells which use ‘1 Quarter’ will be set to “str_value” and numeric cells which use ‘1 Quarter’ will be set to 77.
  688. AllowSeparateNandCRules=T
  689.  
  690. # DistributedPlanningOutputDir
  691. # Type: Optional, Static
  692. # This parameter defines the directory to which 'TUnits' are written when an application is 'deployed'. This call is made as part of Cognos Deskop deploying an application which will allow a client to open a distributed client.
  693. #DistributedPlanningOutputDir=.\tunit
  694.  
  695. # CalculationThresholdForStorage
  696. # Defines a minimum number of rule calculations required for a single cell or Stargate view, beyond which the TM1® server stores the calculations for use during the current server session.
  697. # Type: Optional, Dynamic
  698. # For example, when a user requests rule-derived values from the TM1 server, either from a single cell or a Stargate view, the server usually has to perform multiple rule calculations to arrive at the requested rule-derived values.
  699. #
  700. # CalculationThresholdForStorage has a direct effect on memory consumption and performance. A high parameter value results in decreased memory consumption and slower performance. A low parameter value results in increased memory consumption and faster performance.
  701. #
  702. # If you do not include CalculationThresholdForStorage in Tm1s.cfg, the default calculation threshold is 50.
  703. #CalculationThresholdForStorage=50
  704.  
  705. # GroupsCreationLimit
  706. # Sets the maximum number of groups that can be created in one TM1® server session.
  707. # Type: Optional, Static
  708. # Note: The GroupsCreationLimit server configuration parameter pre-allocates
  709. # memory and should not be set higher than needed. Please see TM1 technical
  710. # bulletin: GroupsCreationLimit Recommendations for more information on
  711. # how this parameter works.
  712. # The GroupsCreationLimit parameter accepts a value of any positive integer. The maximum number of groups for GroupsCreationLimit is 65535. The maximum number of groups that can exist on a server is 65535. If you do not use the parameter, the default number of groups is 20.
  713. #
  714. # For example, to create 50 groups per server session, enter the following line:
  715. #
  716. # GroupsCreationLimit=50
  717. #
  718. # Note: When TM1 allocates memory to store security information, the server calculates the amount of memory required based in part on the value of GroupsCreationLimit. In some circumstances when your TM1model is large and the GroupsCreationLimit parameter is set to an exceptionally high value, the server will attempt to allocate memory beyond the available capacity on the server. The TM1 server will fail to load and will issue a Server Out of Memory message. To avoid this situation, set GroupsCreationLimit to a value that accurately reflects the maximum number of user groups you may need to create during a server session.
  719. #
  720. # The GroupsCreationLimit value is not enforced when you create groups with the AddGroup function in TurboIntegrator.
  721. GroupsCreationLimit=600
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!