MicroStrategy ONE
Managing Subscriptions
This section contains the following information:
- Tasks for Managing Subscriptions
- Administering Subscriptions
- Result Caches and Subscriptions
- Subscriptions in a Clustered System
Tasks for Managing Subscriptions
The table below lists common subscription and delivery-related tasks that users or administrators can perform, and where to perform those tasks, in both MicroStrategy Web and Developer. Note that some tasks can be performed only in MicroStrategy Web.
The steps in the table take you to the main interface to complete the task. For detailed steps, click Help once you are in the main interface.
User task |
Where to perform the task |
Define preferences for a report/document to be delivered to a user's History List folder, mobile device, or system cache. |
|
Define preferences for a report/document to be delivered to an email address, network storage location, FTP location, or printer (Distribution Services only). |
|
Define personal subscription preferences to all reports or documents, in one location. |
|
Set up alert-based subscriptions. |
|
Schedule a report/document to be sent to another user. |
|
Unsubscribe from a report or document. |
|
Change subscription details for a report or document. |
|
Configure who can subscribe to each report. |
|
Configure who can subscribe to each document. |
|
Administering Subscriptions
You can create, remove, or modify subscriptions through the Subscription Manager.
You can set the maximum number of subscriptions of each type that each user can have for each project. This can prevent excessive load on the system when subscriptions are executed. By default, there is no limit to the number of subscriptions. You set these limits in the Project Configuration Editor, in the Governing Rules: Default: Subscriptions category.
To Manage Your Subscriptions in the Subscription Manager
- In Developer, log in to a project source.
- Expand Administration, then expand Configuration Managers, and then select Subscriptions.
- To manage your subscriptions, select from the tasks below:
- To create a subscription, right-click in the Subscription Manager and select Subscription Creation Wizard. . Follow the instructions in Creating Subscriptions.
- To modify a subscription, right-click the subscription and select Edit. Make any changes and click OK.
- To delete a subscription, right-click the subscription and select Delete.
- To filter the subscriptions that are listed, right-click in the Subscription Manager and select Filter. Specify the filtering criteria and click OK.
Result Caches and Subscriptions
By default, if a cache is present for a subscribed report or document, the report or document uses the cache instead of re-executing the report or document. If no cache is present, one is created when the report or document is executed. For information about how result (report or document) caches are used in MicroStrategy, see Result Caches.
When you create a subscription, you can force the report or document to re-execute against the warehouse even if a cache is present, by selecting the Re-run against the warehouse check box in the Subscription Wizard. You can also prevent the subscription from creating a new cache by selecting the Do not create or update matching caches check box.
You can change the default values for these check boxes in the Project Configuration Editor, in the Caching: Subscription Execution category.
Subscriptions in a Clustered System
When you set up several Intelligence Server machines in a cluster, you can distribute projects across those clustered machines (or nodes) in any configuration. Each node can host a different subset of projects. For more information, including instructions, on clustering Intelligence Servers, see Cluster Multiple MicroStrategy Servers.
Subscriptions in a clustered system are load-balanced across all nodes of the cluster that host the project containing the subscribed report or document. Subscriptions are load-balanced by the number of subscription jobs created. One subscription job is created for each user or user group in the subscription. For example, if User A and User Group B are subscribed to a dashboard, the subscription creates one job for User A, and a second job for User Group B. In a two-node cluster, the subscription for User A would execute on one node, and the subscription for User Group B would execute on the other node.