Configuring default settings for a page or block

An administrator needs to configure the default settings for the MicroStrategy page and for both MicroStrategy blocks: the MicroStrategy master block and the basic MicroStrategy block. The default settings for the page object are applied to each new MicroStrategy page instance that is added to your Drupal site, and the default settings for the block objects are applied to each MicroStrategy block instance that is added to a page. An administrator can also modify any of these settings for specific instances of these pages and blocks. These modified settings apply only to the particular page or block whose settings have been changed.

 

 

Some of the default settings can be left unchanged, but you should specify the appropriate values for the four settings listed below. The values you provide for these settings allow your MicroStrategy page or block to connect to MicroStrategy Web. If you leave the default settings unchanged, the MicroStrategy page or block may not be able to communicate with your MicroStrategy Web installation.
 

 

 

Configuring default settings for a MicroStrategy page or block object
 

To configure default settings for the MicroStrategy page and the two MicroStrategy blocks, do the following:

 

  1. Log in to Drupal as an administrator and navigate to Administer -> Site building -> MicroStrategy -> Default Settings -> and choose one of the following:
     

  2. The default settings for a MicroStrategy page, basic block, or master block are grouped in the following categories:
     

Configure the default settings as desired. Use the information provided below for default settings as a guide in making your changes.
 

  1. Click Submit at the bottom of the page to save your changes.
     

The changes are applied to any newly added pages or blocks, as well as non-customized existing pages or blocks.

 

 

Overriding default settings for a MicroStrategy page or block instance
 

To override default settings for instances of the MicroStrategy page and the two MicroStrategy blocks that have already been created, do the following:

 

  1. Log in to Drupal as an administrator and navigate to Administer -> Site building -> MicroStrategy -> and choose one of the following:
     

  2. Choose the MicroStrategy page or block whose default settings you want to modify.
     

  3. The default settings for a MicroStrategy page, basic block, or master block are grouped in the following categories:
     

Make changes to the default settings as desired. Use the information provided below for default settings as a guide in making your changes.
 

  1. Click Submit at the bottom of the page to save your changes.
     

The changes are applied only to the particular page or block whose settings have been modified.

 

 

Default settings

 

The sections below describe the default settings that can be configured or overridden for MicroStrategy pages and blocks in a Drupal environment. The check boxes below each setting indicate whether the setting is applicable to a MicroStrategy page, basic block, master block, or a combination of these.

 

MicroStrategy Content URL
 


checkedBox.gif MicroStrategy page      checkedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
 

 
The MicroStrategy Web Task URL is used by the page or block to invoke tasks on the MicroStrategy Web server. For example, it is used to create a MicroStrategy session. When the task is executed on the MicroStrategy Web server, it makes the necessary calls to the MicroStrategy Intelligence Server.
  

Note: If you have trouble viewing a MicroStrategy page or block using the MicroStrategy Web Task URL in a .NET environment, you may need to take some additional steps related to the taskProc page. See the Troubleshooting topic for an explanation of how to correct this problem.

 
checkedBox.gif MicroStrategy page      checkedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
 

checkedBox.gif MicroStrategy page      checkedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
 

uncheckedBox.gif MicroStrategy page      checkedBox.gif MicroStrategy master block      uncheckedBox.gif MicroStrategy basic block

 

checkedBox.gif MicroStrategy page      checkedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
 

checkedBox.gif MicroStrategy page      checkedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
 

checkedBox.gif MicroStrategy page      checkedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
 

checkedBox.gif MicroStrategy page      uncheckedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
 

checkedBox.gif MicroStrategy page      uncheckedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
 

checkedBox.gif MicroStrategy page      checkedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
  

MicroStrategy Server

checkedBox.gif MicroStrategy page      checkedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
 

 

Note: The authentication mode that use in the page or block must be enabled in MicroStrategy Web.

 

 

Note: The working set is a collection of messages that reference in-memory report instances. Each time that you perform a manipulation, a new message is created. If you perform more manipulations than the number of messages you are saving in memory and attempt to return to a previous message, you may get a "Job Timed Out" message.

 

Choice

Resulting action

Checked

All of the pending requests will be canceled when a user logs out.

Unchecked

None of the pending requests will be canceled when a user logs out.  (default)

 

 

Plug-ins


checkedBox.gif MicroStrategy page      checkedBox.gif MicroStrategy master block      checkedBox.gif MicroStrategy basic block
 

Note: You can customize the credential mapper plug-in, but it requires PHP programming skills. You can either customize  microstrategy.credential.mapper.inc, the credential mapper file provided by MicroStrategy, or you can create your own custom mapper file.

 

To customize microstrategy.credential.mapper.inc, do the following:

  1. Copy the microstrategy.credential.mapper.inc PHP file into the custom_plugin folder of the MicroStrategy module.
  2. If you need to customize the SSO behavior of the portlet, complete the following steps.

        a. Open the microstrategy.credential.mapper.inc file in a text editor.

        b. Find the microstrategy_map_credentials function in the folder. This PHP function controls the SSO behavior for MicroStrategy pages and blocks.

        c. Modify the microstrategy_map_credentials function as needed.

        d. Save and close the file.

  3. To use the microstrategy.credential.mapper.inc file with a MicroStrategy page or block, you must change the plug-in settings of that page or block as indicated below.

        a. On the your Drupal site, log in as an administrator and navigate to Administer -> Site building -> MicroStrategy.

        b. Select the page or block that is to use the microstrategy.credential.mapper.inc file.

        c. Under the plug-ins heading, enter the following parameters.

            - In the Credential Mapper File Name text box, enter microstrategy.credential.mapper.inc.

            - In the Credential Mapper Function Name text box, enter microstrategy_map_credentials.

        d. Click Submit when you are finished.

 

To create your own custom credential mapper file, do the following:

  1. Create  the custom PHP file, either using the default credential mapper function name, microstrategy_map_credentials, or a custom name. (If you use a custom name for the function, the function parameter and the return type must be the same as the sample code.)

  2. Copy your custom credential mapper file into the custom_plugin folder of the MicroStrategy module.

  3. Use the name of your custom credential mapper file as the value of this setting (Credential Mapper File Name).

  4. Use the name of your custom credential mapper function as the value of the setting below (Credential Mapper Function Name).

 

Note: If you want to customize the credential mapper function, see the note above for the Credential Mapper File Name setting.

 

Note: You can customize the URL parameter mapper plug-in, but it requires PHP programming skills. You can either customize  microstrategy.urlparameter.mapper.inc, the URL parameter mapper file provided by MicroStrategy, or you can create your own custom mapper file.

 

To customize microstrategy.urlparameter.mapper.inc, do the following:

  1. Copy the microstrategy.urlparameter.mapper.inc file in the custom_plugin folder of the Microstrategy module.

  2. Change the implementation of the microstrategy_map_url_parameters function if needed.

 

To create your own custom URL parameter mapper file, do the following:

  1. Create  the custom PHP file, either using the default URL parameter mapper function name, microstrategy_map_url_parameters, or a custom name. (If you use a custom name for the function, the function parameter and the return type must be the same as the sample code.)

  2. Copy your custom URL parameter mapper file into the custom_plugin folder of the MicroStrategy module.

  3. Use the name of your custom URL parameter mapper file as the value of this setting (URL Parameter Mapper File Name).

  4. Use the name of your custom URL parameter mapper function as the value of the setting below (URL Parameter Mapper Function Name).

 

Note: If you want to customize the URL parameter mapper function, see the note above for the URL Parameter Mapper File Name setting.

 

User Parameters

 

Default preferences for MicroStrategy page and block instances