MicroStrategy ONE

Modifying Properties of a Bean

This topic provides step-by-step instructions on modifying the general properties of a bean instance, such as the name of the system bean and event handler, its persistence mode, and its web features, as well as its initialization and request properties.

  1. Launch the Web Customization Editor. 

  2. Click on MicroStrategy Web Configuration inside the Application Settings view to expand the hierarchical tree. The expanded list comprises the different settings that can be modified to perform customizations. 

  3. Click on Pages to expand the list of pages used in MicroStrategy Web. 

  4. Expand the appropriate page to display the Beans and CSS folders. 

  5. Click on Beans to display the list of beans used on that page. 

  6. Double-click the bean for which you wish to modify the properties. The Bean Properties tab of the page is displayed. 

  7. Modify general properties such as name of the system bean and event handler used by the bean by modifying values in the System Bean and Event Handler text fields respectively. Select the persistence mode from the Persistance Mode drop-down menu and web features by clicking Modify. 

  8. Select either the Initialization Properties or the Request Properties tab to view the initialization and request properties respectively for the bean. 

  9. Click the entries in the Type, Source, and Value fields to modify the properties. Available sources include the following.

    • default: The default source is request.

    • request: The value is returned by an HTTP request.

    • enum: The value specifies the ID of a Java enumeration. Consult the API documentation for a list of available enumerations.

    • const: This source setting uses a constant value.

    • preferences: The value is the ID of a MicroStrategy Web preference.

    • browserSetting: This source uses a browser cookie.

    • feature: This source setting uses a MicroStrategy Web feature.

  10. Save your changes.

After you have completed this task, you must restart the application server for changes to take effect, unless the reloadConfigurationFiles property in microstrategy.xml is set to true. See Applying Customization Changes for information on changing the value of the reloadConfigurationFiles property.