If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Should my backup CM act as a dispatcher while in passive mode?

Started by mpflug, 11 Mar 2010 10:45:33 AM

Previous topic - Next topic

mpflug

Hi All,
  I thought I read somewhere that backup CMs in passive mode will act as dispatchers until they become the active CM.  Am I making this up?  I've installed a backup CM on my stack and am never seeing it used as a dispatcher.  I have it in the dispatcher URI list on the gateway but i don't see it listed as a dispatcher in cognos administration.  If i access the dispatcher directly:  http://<dispatcher>:9300/p2pd/servlet/dispatch it works fine.  Any ideas?

Thanks,
Mike 

mpflug

Answering my own question:  The appropriate services are disabled by default.  You can do this by changing cogstartup.xml to enable the services you're looking for:


 <!-- CBS: Defines a group of properties for the IBM Cognos 8 service.  -->
 <!-- Use these properties to specify the amount of resources that the IBM Cognos 8 service
      uses.  -->
 <crn:parameter name="CBS" opaque="true">
   <crn:value>
     <!-- asvIsEnabled: Specifies whether the agent service is enabled.  -->
     <!-- Use this property to enable or disable the agent service on the local computer. The
          agent service executes agents. If the conditions for an agent are met, the agent
          service signals the monitor service to execute the tasks. By default the agent service
          is enabled.  -->
     <crn:parameter name="asvIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- brsIsEnabled: Specifies whether the batch report service is enabled.  -->
     <!-- Use this property to enable or disable the batch report service on the local computer.
          The batch report service handles background requests for report executions and provides
          output, on behalf of the monitor service. The batch report service works the same
          as the report service, except it handles only background executions. By default the
          batch report service is enabled.  -->
     <crn:parameter name="brsIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- cmIsEnabled: Specifies whether the Content Manager service is enabled.  -->
     <!-- Use this property to enable or disable the Content Manager service on the local computer.
          The Content Manager service is a service used by other services to store, organize,
          and retrieve application data such as system configuration, models, report specifications,
          report outputs, schedules, user accounts, groups, contacts, distribution lists and
          data sources. A distributed installation may have one active Content Manager service,
          and one or more standby Content Manager services. By default the Content Manager
          service is enabled.  -->
     <crn:parameter name="cmIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- disIsEnabled: Specifies whether the data integration service is enabled.  -->
     <!-- Use this property to enable or disable the data integration service on the local
          computer. The data integration service manages the tasks that obtain data from data
          sources, extract information from data stores, recalculate and transform data, and
          load content for use by Metrics Manager in the portal. By default the data integration
          service is enabled.  -->
     <crn:parameter name="disIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- dssoapIsEnabled: Specifies whether the Data Manager SOAP service is enabled.  -->
     <!-- Use this property to enable or disable Data Manager SOAP service on the local computer.
          By default Data Manager SOAP service is enabled.  -->
     <crn:parameter name="dssoapIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- dmsIsEnabled: Specifies whether the data movement service is enabled.  -->
     <!-- Use this property to enable or disable the data movement service on the local computer.
          The data movement service is used for CEBA-based requests for data movement tasks.
          By default, the data movement service is enabled.  -->
     <crn:parameter name="dmsIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- dlsIsEnabled: Specifies whether the delivery service is enabled.  -->
     <!-- Use this property to enable or disable the delivery service on the local computer.
          The delivery service sends emails on behalf of other services, such as the report
          service, job service or agent service. By default the delivery service is enabled.  -->
     <crn:parameter name="dlsIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- dispIsEnabled: Specifies whether the dispatcher related services are enabled.  -->
     <!-- Use this property to enable or disable a number of services on the local computer.
          Currently these are the batch report service, report service, data movement service,
          metadata service and presentation service. By default these services are disabled
          on computers where Content Manager is the only component that is installed. Please
          note that the dispatcher itself will not be disabled.  -->
     <crn:parameter name="dispIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- emIsEnabled: Specifies whether the event management service is enabled.  -->
     <!-- Use this property to enable or disable the event management service on the local
          computer. The event management service manages scheduled task executions. When a
          scheduled task execution begins, the event management service signals the monitor
          service to begin the execution of the task. By default the event management service
          is enabled.  -->
     <crn:parameter name="emIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- csnidIsEnabled: Specifies whether the index data service is enabled.  -->
     <!-- Use this property to enable or disable the index data service on the local computer.
          The index data service stores the contents of the index. A distributed installation
          should have only one enabled index data service instance. By default the index data
          service is enabled.  -->
     <crn:parameter name="csnidIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- csnisIsEnabled: Specifies whether the index search service is enabled.  -->
     <!-- Use this property to enable or disable the index search service on the local computer.
          The index search service is used to search based on the contents of the index. By
          default the index search service is enabled.  -->
     <crn:parameter name="csnisIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- csniuIsEnabled: Specifies whether the index update service is enabled.  -->
     <!-- Use this property to enable or disable the index update service on the local computer.
          The index update service indexes information that has been stored using the Content
          Manager service. By default the index update service is enabled.  -->
     <crn:parameter name="csniuIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- jsIsEnabled: Specifies whether the job service is enabled.  -->
     <!-- Use this property to enable or disable the job service on the local computer. The
          job service executes jobs and signals the monitor service to execute job steps in
          the background. By default the job service is enabled.  -->
     <crn:parameter name="jsIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- mdsIsEnabled: Specifies whether the metadata service is enabled.  -->
     <!-- Use this property to enable or disable the metadata service on the local computer.
          The metadata service handles metadata requests including lineage, queryMetadata,
          updateMetadata and testDataSourceConnection. By default, the metadata service is
          enabled.  -->
     <crn:parameter name="mdsIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- cmmIsEnabled: Specifies whether Metrics Manager service is enabled.  -->
     <!-- Use this property to enable or disable Metrics Manager service on the local computer.
          The Metrics Manager service manages application requests, such as requests for Web
          pages or application configuration information. By default the Metrics Manager service
          is enabled.  -->
     <crn:parameter name="cmmIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- migsrvIsEnabled: Specifies whether the migration service is enabled.  -->
     <!-- Use this property to enable or disable the migration service on the local computer.
          The migration service is used to migrate PowerPlay content. By default the migration
          service is enabled.  -->
     <crn:parameter name="migsrvIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- mobIsEnabled: Specifies whether the mobile service is enabled.  -->
     <!-- Use this property to enable or disable the mobile service on the local computer.
          The mobile service allows content to be sent to mobile devices, and handles requests
          from mobile devices. By default the mobile service is enabled.  -->
     <crn:parameter name="mobIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- msIsEnabled: Specifies whether the monitor service is enabled.  -->
     <!-- Use this property to enable or disable the monitor service on the local computer.
          The monitor service signals a target service to handle a task, then monitors the
          execution of the task and collects and saves history information for the execution
          of the task. The monitor service can also take control of asynchronous service conversations
          on behalf of the client. By default the monitor service is enabled.  -->
     <crn:parameter name="msIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- pasIsEnabled: Specifies whether the planning administration console service is enabled.  -->
     <!-- Use this property to enable or disable the planning administration console service
          on the local computer. By default the planning administration console service is
          enabled.  -->
     <crn:parameter name="pasIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- pdsIsEnabled: Specifies whether the planning data service is enabled.  -->
     <!-- Use this property to enable or disable the planning data service on the local computer.
          The planning data service manages report queries against IBM Cognos Planning - Contributor
          data sources. By default, the planning data service is enabled.  -->
     <crn:parameter name="pdsIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- pjsIsEnabled: Specifies whether the planning job Data Manager service is enabled.  -->
     <!-- Use this property to enable or disable the planning job service on the local computer.
          By default the planning job service is enabled.  -->
     <crn:parameter name="pjsIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- pwsIsEnabled: Specifies whether the planning Web service is enabled.  -->
     <!-- Use this property to enable or disable the planning Web service on the local computer.
          By default the planning Web service is enabled.  -->
     <crn:parameter name="pwsIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- ppesIsEnabled: Specifies whether the PowerPlay service is enabled.  -->
     <!-- Use this property to enable or disable the PowerPlay service on the local computer.
          By default the PowerPlay service is enabled.  -->
     <crn:parameter name="ppesIsEnabled" disabled="true">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- xtscrnIsEnabled: Specifies whether the presentation service is enabled.  -->
     <!-- Use this property to enable or disable the presentation service on the local computer.
          The presentation service handles requests for IBM Cognos Connection, Query Studio,
          and Event Studio. By default the presentation service is disabled on computers where
          Content Manager is the only component that is installed.  -->
     <crn:parameter name="xtscrnIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- ccsIsEnabled: Specifies whether the report data service is enabled.  -->
     <!-- Use this property to enable or disable the report data service on the local computer.
          The report data service manages external client requests such as IBM Cognos 8 Go!
          Office. By default the report data service is enabled.  -->
     <crn:parameter name="ccsIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- warpIsEnabled: Specifies whether the report service is enabled.  -->
     <!-- Use this property to enable or disable the report service on the local computer.
          The report service handles interactive requests for report executions and generates
          output for a user in IBM Cognos Connection or one of the studios. By default the
          report service is enabled.  -->
     <crn:parameter name="warpIsEnabled">
       <crn:value xsi:type="xsd:boolean">true</crn:value>
     </crn:parameter>
     <!-- cbs: Specifies the template used to configure the IBM Cognos 8 service.  -->
     <!-- This property is automatically set when you select a template for the IBM Cognos
          8 service. You cannot change the value of this property in this window. If you want
          to use another template, in the Explorer window, right-click the service and click
          Delete. Right-click IBM Cognos 8 service, click New resource, Configuration. Enter
          a resource name and then select a template from the list.  -->
     <crn:instances name="cbs">
       <!-- IBM Cognos 8: Defines a group of properties for a configuration template used for
            small installations.  -->
       <!-- Use this type of configuration for proof of concept, demonstration or development
            environments where all of the product components are installed on one computer, memory
            resources are limited, and the startup time is more important than performance or
            processing a large number of simultaneous requests.  -->
       <crn:instance name="IBM Cognos 8" class="Small">
         <!-- dispatcherPingTimeout: Specifies the maximum number of seconds to wait for a response
              to a ping.  -->
         <!-- If the ping is not responded to within the specified time interval, the process is
              automatically restarted.  -->
         <crn:parameter name="dispatcherPingTimeout">
           <crn:value xsi:type="xsd:unsignedShort">240</crn:value>
         </crn:parameter>
         <!-- dispatcherStopWaitTime: Specifies the maximum number of seconds that the IBM Cognos
              8 service waits for the process to stop.  -->
         <!-- After this amount of time, the process is automatically stopped.  -->
         <crn:parameter name="dispatcherStopWaitTime">
           <crn:value xsi:type="xsd:unsignedShort">60</crn:value>
         </crn:parameter>
         <!-- dispatcherMaxMemory: Specifies the maximum amount of memory in MB that can be used
              by the process.  -->
         <!-- This value determines the amount of memory used by the Java Virtual Machine and depends
              on how much memory is available. If this value is too high, the process will fail
              to start and no log information will be generated. Invoke the test action to determine
              if this value is valid.  -->
         <crn:parameter name="dispatcherMaxMemory">
           <crn:value xsi:type="xsd:unsignedInt">768</crn:value>
         </crn:parameter>
         <!-- shutdownPort: Specifies the port the product uses to listen for a shutdown command.  -->
         <!-- The port number is used by Tomcat. When you change the port, it is automatically
              updated in the server.xml file located in the c8_location/tomcat4.1.27/conf directory.  -->
         <crn:parameter name="shutdownPort">
           <crn:value xsi:type="xsd:unsignedShort">9399</crn:value>
         </crn:parameter>
       </crn:instance>
     </crn:instances>
   </crn:value>
 </crn:parameter>