Decisions
Enable you to better control the order in which processes execute by comparing exit codes, parameters, and other values.
They can also check if a file or folder exists and use this information to determine subsequent actions.
They can also check if a file or folder exists and use this information to determine subsequent actions.
Enterprise Manager Best Practices (performance and system health)
• The process for data loads adds extra overhead to the Intelligence Server process. For that reason, schedule the data load process at off-peak hours.
• Configure the data load maintenance tasks according to your needs
• Purge unused data: depending on how many objects (such as reports, users and projects) you are collecting statistics for, Enterprise Manager could be gathering a great deal of data. Having too much data could affect warehouse performance. MicroStrategy recommends that you purge outdated and no longer relevant data to optimize for database performance. This keeps the database to a manageable size, making it easier to maintain and faster to query.
• Keep only up to 3 months (one quarter) of live statistics. If statistics must be retained for longer periods, store it elsewhere.
• Configure the data load maintenance tasks according to your needs
• Purge unused data: depending on how many objects (such as reports, users and projects) you are collecting statistics for, Enterprise Manager could be gathering a great deal of data. Having too much data could affect warehouse performance. MicroStrategy recommends that you purge outdated and no longer relevant data to optimize for database performance. This keeps the database to a manageable size, making it easier to maintain and faster to query.
• Keep only up to 3 months (one quarter) of live statistics. If statistics must be retained for longer periods, store it elsewhere.
Entry (green flag) and Exit Processes (gray circle with red line)
Entry processes may be any processes that have been designated as potential starting points in a workflow.
By default, the first process you add to a workflow is marked as an entry process, but you can add other processes as entry points as well.
Every workflow should have at least one exit process to ensure consistent results.
To add an exit process to a workflow, on the Connectors and Processes pane, on the toolbar, click the Exit Workflow process and place the process in the workflow canvas.
By default, the first process you add to a workflow is marked as an entry process, but you can add other processes as entry points as well.
Every workflow should have at least one exit process to ensure consistent results.
To add an exit process to a workflow, on the Connectors and Processes pane, on the toolbar, click the Exit Workflow process and place the process in the workflow canvas.
Operations Analysis folder
Contains reports which provide information on system resource usage, concurrency, and report and subscription processing time.
In addition to the reports in this folder, the following dashboards provide a visual overview of usage and performance in the monitored projects:
Document Processing Analysis Dashboard
This interactive dashboard provides insight into how document execution affects the BI System, and how each document is requested and executed, including average wait times and number of execution errors encountered.
In addition to the reports in this folder, the following dashboards provide a visual overview of usage and performance in the monitored projects:
Document Processing Analysis Dashboard
This interactive dashboard provides insight into how document execution affects the BI System, and how each document is requested and executed, including average wait times and number of execution errors encountered.
Performance Analysis folder
Contains reports, which support analysis
related to usage patterns, Intelligence Server governing settings, and
Intelligent Cube analysis.
In addition to the reports in the Performance Analysis folder, the following dashboards provide information that can guide you when optimizing the performance of your data warehouse and towards optimal caching strategies based on historical usage data.
Data Warehouse Optimization Advisor - is a data warehouse optimization wizard that helps you locate the worst-performing reports in your projects. It provides a set of recommendations for each database table accessed by these reports.
Server Caching Optimization Advisor - is an Intelligence Server workload optimization wizard that provides guidance on optimal caching strategies based on historical usage monitoring.
In addition to the reports in the Performance Analysis folder, the following dashboards provide information that can guide you when optimizing the performance of your data warehouse and towards optimal caching strategies based on historical usage data.
Data Warehouse Optimization Advisor - is a data warehouse optimization wizard that helps you locate the worst-performing reports in your projects. It provides a set of recommendations for each database table accessed by these reports.
Server Caching Optimization Advisor - is an Intelligence Server workload optimization wizard that provides guidance on optimal caching strategies based on historical usage monitoring.
Project Analysis folder
Contains reports that provide information
about MicroStrategy project growth and the usage patterns of
configuration and project objects.
In addition to the reports in the Project Analysis folder, the following dashboards provide a comprehensive overview of usage and activity on your projects, over the time frame that you specify:
Project Analysis Dashboard -provides you with project-level statistics on load distribution, usage, and job performance across all monitored projects.
Project Analysis Interactive Dashboard - provides different views of a given project. It looks at overall project size, object storage patterns, usage of the project and its objects, as well as growth patterns.
In addition to the reports in the Project Analysis folder, the following dashboards provide a comprehensive overview of usage and activity on your projects, over the time frame that you specify:
Project Analysis Dashboard -provides you with project-level statistics on load distribution, usage, and job performance across all monitored projects.
Project Analysis Interactive Dashboard - provides different views of a given project. It looks at overall project size, object storage patterns, usage of the project and its objects, as well as growth patterns.
Real-Time Analysis foler
Contains reports with information related to current response times and schedule results.
This information can be useful for troubleshooting and for optimizing your database configuration.
In addition to the reports in the Real-Time analysis folder, the following dashboard provides an overview of recent system activity.
Real-Time Server Usage Dashboard - provides you with a comprehensive, real-time overview of report job activity.
This information can be useful for troubleshooting and for optimizing your database configuration.
In addition to the reports in the Real-Time analysis folder, the following dashboard provides an overview of recent system activity.
Real-Time Server Usage Dashboard - provides you with a comprehensive, real-time overview of report job activity.
Split and merge processes enable workflows to run processes in parallel and rejoin parallel paths into a linear workflow.
You can connect parallel processes to a Merge Execution process to ensure different paths reconvene.
The Merge Execution process waits until all source processes are executed or a user-defined period of
time that starts after the completion of the fastest process.
If not all processes execute in time, you can use a failure connector to determine subsequent behavior. Otherwise, a success connector can continue the workflow.
The Merge Execution process waits until all source processes are executed or a user-defined period of
time that starts after the completion of the fastest process.
If not all processes execute in time, you can use a failure connector to determine subsequent behavior. Otherwise, a success connector can continue the workflow.
System Objects you CANNOT delete
• Administration icon
• Monitors
• Managers
• Administration directory
• Administrator user
• Data Explorer
• My Personal Objects folder
• My Reports folder
• My Favorites folder
• My Answers folder
• My Objects folder
• Schema Objects folder and all subfolders
• Everyone user group
• Public user group
• System Administrators user group
• Monitors
• Managers
• Administration directory
• Administrator user
• Data Explorer
• My Personal Objects folder
• My Reports folder
• My Favorites folder
• My Answers folder
• My Objects folder
• Schema Objects folder and all subfolders
• Everyone user group
• Public user group
• System Administrators user group
User Analysis folder
Contain the User attribute as their primary attribute for analysis and analyzes user activity and preferences.
In addition to the reports in the User Analysis folder, the following dashboard provides an overview of user activity on an Intelligence Server or project, including statistics for report and document execution and user session information.
You can also examine inactive users to find out how long they have been inactive to determine whether they should be deleted.
User Analysis Dashboard - provides insights into how users are using the system with regards to report and document execution, and session information.
In addition to the reports in the User Analysis folder, the following dashboard provides an overview of user activity on an Intelligence Server or project, including statistics for report and document execution and user session information.
You can also examine inactive users to find out how long they have been inactive to determine whether they should be deleted.
User Analysis Dashboard - provides insights into how users are using the system with regards to report and document execution, and session information.
A workflow may consist of [PCD]
- Processes
- Connectors
- Decisions
- Connectors
- Decisions
Analyzing/comparing reports and documents in Integrity Manager
For reports, you can analyze and compare the following types of output:
• SQL / MDX
• Data
• Graph
• Excel
• PDF
For documents, you can test document execution and analyze and compare the following types of output:
• Excel
• PDF
• SQL / MDX
• Data
• Graph
• Excel
For documents, you can test document execution and analyze and compare the following types of output:
• Excel
Application Life Cycle Management
The process of moving objects across development, test, production
Asynchronous Execution
Command Manager uses asynchronous
execution, which means that while a script is executing, you can create
additional scripts and execute them without needing to wait until
execution of the original script is complete.
Auto-complete feature
Assists you in editing and developing scripts.
This feature helps users complete words in a Command Manager command and can eliminate the need to browse through the Outlines form.
This feature can be enabled or disabled from the Options window. Invoke auto-complete by typing CTRL + SPACEBAR at any time during the editing of a Command Manager script.
This feature helps users complete words in a Command Manager command and can eliminate the need to browse through the Outlines form.
This feature can be enabled or disabled from the Options window. Invoke auto-complete by typing CTRL + SPACEBAR at any time during the editing of a Command Manager script.
Automated Package Creation from a Command Line
You can create update packages without opening Object Manager.
You must first create an XML file that contains a list of the objects to be migrated and conflict resolution rules for those objects.
Then you execute the instructions in that XML file using the Project Merge executable to create the update package file (.mmp).
The main advantages of creating packages through XML files:
• The user does not need access to Object Manager.
• The user does not need access to the source project.
You must first create an XML file that contains a list of the objects to be migrated and conflict resolution rules for those objects.
Then you execute the instructions in that XML file using the Project Merge executable to create the update package file (.mmp).
The main advantages of creating packages through XML files:
• The user does not need access to Object Manager.
• The user does not need access to the source project.
Baseline File
Every time an Integrity Manager test is executed, the results of the test are saved as a baseline.xml file.
By default, a Single Project test creates one baseline.xml file based on the results of the base project used in the test.
A Project vs. Project test creates two baseline.xml files; one for the base project and one for the target project.
A Baseline vs. Project test also creates two baseline.xml files; one for the baseline file and one for the target project.
An Integrity Manager test has an extension of .mtc. By default, it is stored in the C:\Program Files (x86)\MicroStrategy\Integrity Manager folder.
By default, a Single Project test creates one baseline.xml file based on the results of the base project used in the test.
A Project vs. Project test creates two baseline.xml files; one for the base project and one for the target project.
A Baseline vs. Project test also creates two baseline.xml files; one for the baseline file and one for the target project.
An Integrity Manager test has an extension of .mtc. By default, it is stored in the C:\Program Files (x86)\MicroStrategy\Integrity Manager folder.
Before copying and pasting objects
You should back up your metadata as you cannot "undo" the paste action.
Benefits of the Administrative Tools
• Ability to maintain object integrity
> Object Manager and Project Merge Wizard
• Ability to maintain data integrity
> Integrity Manager
• Ability to automate administrative tasks
> Command Manager and System Manager
• Ability to report on your project
> Enterprise Manager
• Ability to audit changes to the metadata
> MicroStrategy Change Journaling
> Object Manager and Project Merge Wizard
• Ability to maintain data integrity
> Integrity Manager
• Ability to automate administrative tasks
> Command Manager and System Manager
• Ability to report on your project
> Enterprise Manager
• Ability to audit changes to the metadata
> MicroStrategy Change Journaling
Besides duplicating projects, you can do the following with Object Manager
• Copy objects across projects
• Delete objects
• Rename objects
• Move objects
• Search for objects
• View object dependencies
• Compare objects across projects
• Delete objects
• Rename objects
• Move objects
• Search for objects
• View object dependencies
• Compare objects across projects
By default, objects with parent dependencies cannot be deleted
For example, if a metric is part of a
report definition, you will not be able to delete the metric before
deleting the parent report first.
By default, Integrity Manager only answers required prompts, and ignores optional prompts that do not have default answers
To answer optional prompts using the same logic as required prompts that do not have default answers, select the Answer optional prompts check box.
Change Journal Monitor Filter
You can filter transactions based on the object type, project, transaction type, and transaction source.
You can also limit the search to a specific time period.
You can also limit the search to a specific time period.
Change Journal Transactions Monitor
You can monitor change journal transactions logged for any object in any project using the Change Journal Transactions monitor.
The monitor is located in the project source Administration section, under System Monitors.
The monitor is located in the project source Administration section, under System Monitors.
Change Journaling
Refers to tracking information about changes made to application, schema, and configuration objects in a MicroStrategy environment.
Whenever any of these objects are created, modified, or deleted, a corresponding transaction is recorded in the change journal.
Change journaling enables administrators to better control and audit their MicroStrategy environment, quickly detect irregular activity, and promote best practices among architects and report developers.
Whenever any of these objects are created, modified, or deleted, a corresponding transaction is recorded in the change journal.
Change journaling enables administrators to better control and audit their MicroStrategy environment, quickly detect irregular activity, and promote best practices among architects and report developers.
Change journaling can be enabed at two levels
• Server level—Enables you to track changes made to the configuration objects
• Project level—Enables you to track changes made to the schema and application objects
• Project level—Enables you to track changes made to the schema and application objects
CLE Interface Modes
• Console mode - enables you to connect to a server, load a script, and change environment settings.
• Edit mode - enables you to create, save, and execute scripts.
• Edit mode - enables you to create, save, and execute scripts.
Command Manager
Enables administrators to complete many of their routine tasks more quickly and easily.
It is an interface that enables you to create scripts to perform various administrative functions such as the following:
• Creating, modifying, and deleting configuration objects (schedules, users, groups, and so forth)
• Managing caches
• Modifying Intelligence Server and project configuration settings
• Triggering event-based schedules
• Assigning privileges to users and groups
• Creating, modifying, and deleting attributes, facts, filters, and metrics
• Publishing, listing, and deleting Intelligent Cubes
• Managing Distribution Services subscriptions
It is an interface that enables you to create scripts to perform various administrative functions such as the following:
• Creating, modifying, and deleting configuration objects (schedules, users, groups, and so forth)
• Managing caches
• Modifying Intelligence Server and project configuration settings
• Triggering event-based schedules
• Assigning privileges to users and groups
• Creating, modifying, and deleting attributes, facts, filters, and metrics
• Publishing, listing, and deleting Intelligent Cubes
• Managing Distribution Services subscriptions
Command Manager - Supported Operating System
Command Manager was developed in Java on top of the MicroStrategy Java/XML infrastructure.
It is an operating system-independent application and can be run on all Intelligence Server-supported environments, including Windows and the 64-bit UNIX (Solaris, AIX, HP-UX) and Linux platforms.
It is an operating system-independent application and can be run on all Intelligence Server-supported environments, including Windows and the 64-bit UNIX (Solaris, AIX, HP-UX) and Linux platforms.
Command Manager also enables
You to create Java programs that combine
Command Manager commands and Java programming concepts, such as loops
and if-then-else logic, to create procedures.
Command Manager can be opened using the following interfaces, each supported in both Windows and UNIX:
• Graphical user interface (GUI) —
Provides users with a toolbar, a script window, and a results window for
users to interactively view outlines, create scripts, validate syntax,
execute scripts, and view execution results.
• Command line interface (using CmdMgr.exe) — Enables you to execute existing Command Manager scripts using parameters in the command line mode.
• Command Line Editor interface (CLE) — Provides the same interactivity as the graphical interface but enables you to run the Command Manager application from the command line in all supported operating systems.
> The CLE interface allows script creation and execution in situations where no graphical user interface is available.
• Command line interface (using CmdMgr.exe) — Enables you to execute existing Command Manager scripts using parameters in the command line mode.
• Command Line Editor interface (CLE) — Provides the same interactivity as the graphical interface but enables you to run the Command Manager application from the command line in all supported operating systems.
> The CLE interface allows script creation and execution in situations where no graphical user interface is available.
Command Manager Connection Modes
Command Manager supports three-tier connectivity to the metadata through Intelligence Server.
However, it does NOT support direct two-tier connectivity between Command Manager and the metadata.
You can also access Command Manager in connection-less session login mode, which allows you to edit Command Manager scripts without first connecting to an Intelligence Server repository.
Using the connection-less session login mode, you can execute certain commands and perform operations on multiple Intelligence Server machines in one script. You can also execute, connect, and disconnect commands in a single script.
Certain commands, such as LIST SERVERS or START/STOP SERVER statements, can be executed without a connection.
However, it does NOT support direct two-tier connectivity between Command Manager and the metadata.
You can also access Command Manager in connection-less session login mode, which allows you to edit Command Manager scripts without first connecting to an Intelligence Server repository.
Using the connection-less session login mode, you can execute certain commands and perform operations on multiple Intelligence Server machines in one script. You can also execute, connect, and disconnect commands in a single script.
Certain commands, such as LIST SERVERS or START/STOP SERVER statements, can be executed without a connection.
Command Manager list of management areas that are available only in the Windows environment
• Schema management (facts, attributes, hierarchies)
• Application management (filters, folders, metrics)
• Database management (tables)
• Schedule relation management (schedules and subscriptions)
• Application management (filters, folders, metrics)
• Database management (tables)
• Schedule relation management (schedules and subscriptions)
Comparing Objects across Projects
Within Object Manager you can compare objects between two projects using the Project Comparison tool.
Conflict Explanations
Exists identically - The object ID, object version, and path are the same in the source and destination projects.
Exists differently - The object ID is the same in the source and destination projects, but the object versions are different. The path may be the same or different.
Exists identically except for path - The object ID and object version are the same in the source and destination projects, but the paths are different. This occurs when one of the objects exists in a different folder. If you resolve the conflict with the Replace action, the destination object is updated to reflect the path of the source object.
Exists identically except for Distribution Services objects - (User only) The object ID and object version of the user are the same in the source and destination projects, but at least one associated Distribution Services contact or contact group is different. This may occur if you modified a contact or contact group linked to this user in the source project. If you resolve the conflict with the Replace action, the destination user is updated to reflect the contacts and contact groups of the source user.
Does not exist - The object exists in the source project but not in the destination project. Note: If you clear the Show new objects that exist only in the source check box in the Migration category of the Object Manager Preferences dialog box, objects that do not exist in the destination project are copied automatically with no need for conflict resolution.
Exists differently - The object ID is the same in the source and destination projects, but the object versions are different. The path may be the same or different.
Exists identically except for path - The object ID and object version are the same in the source and destination projects, but the paths are different. This occurs when one of the objects exists in a different folder. If you resolve the conflict with the Replace action, the destination object is updated to reflect the path of the source object.
Exists identically except for Distribution Services objects - (User only) The object ID and object version of the user are the same in the source and destination projects, but at least one associated Distribution Services contact or contact group is different. This may occur if you modified a contact or contact group linked to this user in the source project. If you resolve the conflict with the Replace action, the destination user is updated to reflect the contacts and contact groups of the source user.
Does not exist - The object exists in the source project but not in the destination project. Note: If you clear the Show new objects that exist only in the source check box in the Migration category of the Object Manager Preferences dialog box, objects that do not exist in the destination project are copied automatically with no need for conflict resolution.
A conflict occurs when
Object Manager finds that the source object already exists in the target project.
This object may exist with the same Version ID, which means it exists identically as the source, or with a different Version ID, which means the definition has been changed.
This object may exist with the same Version ID, which means it exists identically as the source, or with a different Version ID, which means the definition has been changed.
Connectors
Appear as arrows and link processes together to control the order in which processes execute.
There are three types of connectors: Success, Failure, and Continue.
As you learned, processes output success or failure exit codes. Continue connectors move the workflow from a source process to the next process regardless of the exit code of the first process.
If a source process outputs a success exit code, a success connector determines the target process, while failure connectors do the same for failure exit codes.
There are three types of connectors: Success, Failure, and Continue.
As you learned, processes output success or failure exit codes. Continue connectors move the workflow from a source process to the next process regardless of the exit code of the first process.
If a source process outputs a success exit code, a success connector determines the target process, while failure connectors do the same for failure exit codes.
Connectors
Link processes together and determine the order and logic of a workflow.
Copying objects across Projects
To copy objects across projects, the projects must be related.
In other words, the projects must be duplicates of each other or duplicates of a common project.
In other words, the projects must be duplicates of each other or duplicates of a common project.
Copying Objects across Unrelated Projects
You can copy objects across unrelated projects using the update package feature.
For example, if you want to copy the Cost fact from the MicroStrategy Tutorial project to the Human Resources Analysis Module project, you can create a package with the Cost fact and all of its dependents, and then import that package into the target project.
When importing the package, ensure that the dependent object for the object you are importing exist either in the package or in the target project.
In this example, if the system finds that the Cost fact is missing a dependent component, the fact is not created in the destination project.
For example, if you want to copy the Cost fact from the MicroStrategy Tutorial project to the Human Resources Analysis Module project, you can create a package with the Cost fact and all of its dependents, and then import that package into the target project.
When importing the package, ensure that the dependent object for the object you are importing exist either in the package or in the target project.
In this example, if the system finds that the Cost fact is missing a dependent component, the fact is not created in the destination project.
Creating Project Security Packages
The project access information for users
and groups included in the package, such as privileges, security roles,
and security filters, is not included in the configuration update package, because this information can be different for each project.
Project security packages adds project access information for users and groups included in the configuration package, such as privileges, security roles, and security filters.
Project security packages adds project access information for users and groups included in the configuration package, such as privileges, security roles, and security filters.
Data Load Maintenance Tasks
Update database statistics -- Hourly
Close orphan sessions -- Daily (>= every 24 hours)
Update object deletions -- Weekly
Data migration -- Hourly
Update folder paths -- Weekly
Repopulate Relate Tables -- Weekly
Close orphan sessions -- Daily (>= every 24 hours)
Update object deletions -- Weekly
Data migration -- Hourly
Update folder paths -- Weekly
Repopulate Relate Tables -- Weekly
Data Load Process
Populates lookup tables and fact tables in
the Enterprise Manager data warehouse, and verifies that the
information is synchronized with the projects being monitored.
Data loads can be run on a schedule (such as during an off-peak hour), or run manually.
In addition, you can set the data load to load statistics logged since the last successful data load, or you can specify the data load to load data between specified dates by using a custom time window.
Data loads can be run on a schedule (such as during an off-peak hour), or run manually.
In addition, you can set the data load to load statistics logged since the last successful data load, or you can specify the data load to load data between specified dates by using a custom time window.
Data Load Process Steps
1. Enterprise Manager uses a set of SQL
scripts to read the metadata of the projects for which the Intelligence
Server is logging statistics. It then populates the lookup tables of the
data warehouse with that information.
2. Enterprise Manager then converts and migrates data from the statistics tables into the data warehouse fact tables, also using a set of SQL scripts.
3. In addition to loading data from the statistics tables and project metadata, the data load process can perform certain system maintenance tasks, such as updating folder paths, updating object deletions, and repopulating relate tables. These keep your Enterprise Manager project and data loads performing efficiently. They can be performed during each data load, or run immediately.
2. Enterprise Manager then converts and migrates data from the statistics tables into the data warehouse fact tables, also using a set of SQL scripts.
3. In addition to loading data from the statistics tables and project metadata, the data load process can perform certain system maintenance tasks, such as updating folder paths, updating object deletions, and repopulating relate tables. These keep your Enterprise Manager project and data loads performing efficiently. They can be performed during each data load, or run immediately.
Decisions
Enable you to determine the next process
in a workflow based on specific outcomes of previous processes, rather
than just the simple success or failure of a process.
Dependent Objects Deletion feature in Desktop
You can use the to force the deletion of objects with parent dependencies.
This feature allows you to recursively delete dependent objects of application objects.
This means that all objects that use the object in question are deleted, and all objects that use those objects are also removed.
For example, if a metric is used in a filter that is used
in a report, all three objects will be deleted if you delete the metric.
This feature allows you to recursively delete dependent objects of application objects.
This means that all objects that use the object in question are deleted, and all objects that use those objects are also removed.
For example, if a metric is used in a filter that is used
in a report, all three objects will be deleted if you delete the metric.
Enterprise Manager
Is designed to help administrators monitor
project environments for the purpose of observing performance and
diagnosing problems.
It enables you to build a project that reports on statistics collected by Intelligence Server. This project comes with a variety of predefined reports and dashboards for analyzing report performance, user activity, and job queues and execution.
It also includes informational reports that display MicroStrategy object data, such as the number of metrics in a project or a list of all of the reports in a project.
It enables you to build a project that reports on statistics collected by Intelligence Server. This project comes with a variety of predefined reports and dashboards for analyzing report performance, user activity, and job queues and execution.
It also includes informational reports that display MicroStrategy object data, such as the number of metrics in a project or a list of all of the reports in a project.
Enterprise Manager Dashboards
Enterprise Manager offers a variety of dashboards, including the Enterprise Manager Overview Dashboard,
which provides an intuitive and interactive overview of collected
document, report, and user activity data, as well as a quick guide to
the other dashboards available in Enterprise Manager.
This dashboard gives an introduction to the capabilities of Enterprise Manager and explores Intelligence Server, Report Services, Distribution Services, and OLAP Services usage. It is prompted on time.
You must have a MicroStrategy Report Services license to view or work with a Report Services document.
In addition, dashboards must be viewed in MicroStrategy Web to take full advantage of their interactivity.
This dashboard gives an introduction to the capabilities of Enterprise Manager and explores Intelligence Server, Report Services, Distribution Services, and OLAP Services usage. It is prompted on time.
You must have a MicroStrategy Report Services license to view or work with a Report Services document.
In addition, dashboards must be viewed in MicroStrategy Web to take full advantage of their interactivity.
Enterprise Manager Data Warehouse
Contains all of the tables necessary for the Enterprise Manager project, such as lookup tables and fact tables.
The statistics tables must also be created in the Enterprise Manager data warehouse database.
The statistics tables must also be created in the Enterprise Manager data warehouse database.
Exit Codes
Describe the outcome of a process. Every process produces an exit code.
There are two types of exit codes, success and failure, though there may be unique codes for different types of successes and failures.
For example, the Find and Replace File Content process can output the exit codes 0, 1, -1, or -2.
0 represents a successful execution and 1 represents a qualified success. -1 and -2 are failure exit codes, with -1 signifying a problem while reading the source file and -2 signifying a file manipulation problem.
To view descriptions of exit codes, in a workflow canvas, click on a process. At the bottom of the Properties and Parameters pane click Show Descriptions.
There are two types of exit codes, success and failure, though there may be unique codes for different types of successes and failures.
For example, the Find and Replace File Content process can output the exit codes 0, 1, -1, or -2.
0 represents a successful execution and 1 represents a qualified success. -1 and -2 are failure exit codes, with -1 signifying a problem while reading the source file and -2 signifying a file manipulation problem.
To view descriptions of exit codes, in a workflow canvas, click on a process. At the bottom of the Properties and Parameters pane click Show Descriptions.
Folder organization of Enterprise Manager
Enterprise Manager comes with a predefined
metadata that includes a variety of dashboards and reports for
analyzing projects, along with all of their supporting objects.
They are organized into the following folders, each corresponding to a particular area of analysis:
- Dashboards
- Operations Analysis
- Performance Analysis
- Project Analysis
- Real-Time Analysis
- User Analysis
They are organized into the following folders, each corresponding to a particular area of analysis:
- Dashboards
- Operations Analysis
- Performance Analysis
- Project Analysis
- Real-Time Analysis
- User Analysis
The following process is used to produce Enterprise Manager reports
1. As users log in to 3-tier projects and
run reports against the Intelligence Server, statistics about this
activity are logged into a statistics database. The administrator can
configure how much detail the Intelligence Server logs.
2. Enterprise Manager loads the data from the statistics database into tables in the Enterprise Manager warehouse. This warehouse resides in the same database as the statistics database. Administrators use the Enterprise Manager Console to configure the data load process and all other Enterprise Manager parameters.
3. The administrator logs in to the Enterprise Manager project, which is housed in the Enterprise Manager metadata, and runs an Enterprise Manager report.
4. The Enterprise Manager report or dashboard runs against the Enterprise Manager warehouse, retrieving the result set from the stored statistics.
2. Enterprise Manager loads the data from the statistics database into tables in the Enterprise Manager warehouse. This warehouse resides in the same database as the statistics database. Administrators use the Enterprise Manager Console to configure the data load process and all other Enterprise Manager parameters.
3. The administrator logs in to the Enterprise Manager project, which is housed in the Enterprise Manager metadata, and runs an Enterprise Manager report.
4. The Enterprise Manager report or dashboard runs against the Enterprise Manager warehouse, retrieving the result set from the stored statistics.
High-level steps to create the workflow process
1. Open a new workflow canvas
2. Add processes and decisions
3. Update process properties and create parameters
4. Add connectors and split and merge connectors
5. Designate entry processes and add exit workflow processes
2. Add processes and decisions
3. Update process properties and create parameters
4. Add connectors and split and merge connectors
5. Designate entry processes and add exit workflow processes
If you disable the request for comments by selecting the Do not show this screen in the future option
You can re-enable it in the Desktop Preferences, under the Optional Actions category.
Important features of an update package are:
• You do not need a connection to the source project during migration.
• The package is a text file and can be shared over email or over a network.
• You can automate package import using a Command Manager script or System Manager.
• You can roll back the changes made by an update package by using an undo package.
• The package is a text file and can be shared over email or over a network.
• You can automate package import using a Command Manager script or System Manager.
• You can roll back the changes made by an update package by using an undo package.
In the Change Journal Manager
You can enable change journaling for all projects by selecting the Apply to all projects check box.
However, it is recommended that you enable change journaling on a project-by-project basis, as necessary.
Apply to all projects check box is not available when enabling change journaling in the MicroStrategy Intelligence Server Configuration Editor.
However, it is recommended that you enable change journaling on a project-by-project basis, as necessary.
Apply to all projects check box is not available when enabling change journaling in the MicroStrategy Intelligence Server Configuration Editor.
Integrity Manager
Creates a ResultsSummary.html output file
that can be viewed outside of Integrity Manager's interface, so you can
easily share the data.
Integrity Manager Prompt Resolution Features
• Ability to provide personal answers
• Ability to run a report using multiple prompt answers
• Ability to enable or disable prompt answers from different sources (for example, personal answers, default prompt answers saved with the report or document, user-defined prompt answers, and Integrity Manager's internal logic)
• Ability to select the order of the prompt answer sources.
• Ability to run a report using multiple prompt answers
• Ability to enable or disable prompt answers from different sources (for example, personal answers, default prompt answers saved with the report or document, user-defined prompt answers, and Integrity Manager's internal logic)
• Ability to select the order of the prompt answer sources.
Integrity Manager has four operational modes
1. Project versus Project—Select and execute reports to compare two live projects
2. Baseline versus Project—Select previously generated output and use as a baseline in comparison with a live project
3. Baseline versus Baseline—Compare two previously generated outputs
4. Single Project—Select and execute reports from one project to confirm they are operational and generate baseline output files
2. Baseline versus Project—Select previously generated output and use as a baseline in comparison with a live project
3. Baseline versus Baseline—Compare two previously generated outputs
4. Single Project—Select and execute reports from one project to confirm they are operational and generate baseline output files
Integrity Manager Prompt Resolution Issues
If Integrity Manager cannot resolve a prompt according to its prompt resolution strategy, the report fails, and its status displays as "Not Supported".
Some examples of prompts that Integrity Manager cannot resolve are listed below:
• Prompts that cannot be answered (for example, an element list prompt that does not have any elements in the list)
• Level prompts that use the results of a search object to generate a list of possible levels
• Prompts in metric qualifications (for example, to define filters or custom group elements)
• Prompts in an MDX expression
Some examples of prompts that Integrity Manager cannot resolve are listed below:
• Prompts that cannot be answered (for example, an element list prompt that does not have any elements in the list)
• Level prompts that use the results of a search object to generate a list of possible levels
• Prompts in metric qualifications (for example, to define filters or custom group elements)
• Prompts in an MDX expression
Locking/Unlocking Projects
Only the user who locked a project, or another user with the "Bypass All Security Access Checks" and "Create Configuration Objects" privileges, can unlock a project.
MicroStrategy Object Manager
Is a stand-alone product, requiring its own license. It includes the following components:
• Object Manager
• Project Merge Wizard
• Repository Translation Wizard
• User Merge Wizard
• Object Manager
• Project Merge Wizard
• Repository Translation Wizard
• User Merge Wizard
MicroStrategy recommends the following best practices for application life cycle management
• Use at least three environments—Development, Test, and Production
• Allow only one-way migration of objects
• Create and change objects only in development
• Keep track of all the changes that have been made to objects
• Test all objects before publishing them in production
• Allow only one-way migration of objects
• Create and change objects only in development
• Keep track of all the changes that have been made to objects
• Test all objects before publishing them in production
Migrating from Test to Production
MicroStrategy Project Merge is recommended for migrating a project from the test system to the production system.
Mobile Usage and Adoption Dashboard
Measures the MicroStrategy Mobile usage and its contribution to the MicroStrategy system.
This information provides insights into Mobile interactive jobs, Mobile Subscriptions, and the most popular Mobile reports and documents.
This information provides insights into Mobile interactive jobs, Mobile Subscriptions, and the most popular Mobile reports and documents.
Object Manager and Project Merge
Are both designed for migrating objects between projects.
Both tools involve copying objects between projects in a definite order according to object types.
While Object Manager is sufficient for incremental changes to your project like migrating selected reports, Project Merge is more efficient for large-scale migration.
Both tools involve copying objects between projects in a definite order according to object types.
While Object Manager is sufficient for incremental changes to your project like migrating selected reports, Project Merge is more efficient for large-scale migration.
Object Manager functions
• copying objects across projects
• duplicating projects
• comparing objects across projects
• viewing object dependencies
• duplicating projects
• comparing objects across projects
• viewing object dependencies
Object Manager supports two kinds of update packages:
• Project update packages — contain application and schema objects from a single project.
• Configuration update packages — contain configuration objects from a single project source.
• Undo packages — are automatically created and consist of all the objects in an update package as they are currently configured in the destination project.
• Configuration update packages — contain configuration objects from a single project source.
• Undo packages — are automatically created and consist of all the objects in an update package as they are currently configured in the destination project.
Objects you CANNOT Rename
• Administration icon
• Monitors
• Managers
• Data Explorer
• My Personal Objects folder
• My Reports folder
• My Favorites folder
• My Answers folder
• My Objects folder
• Everyone user group
• Monitors
• Managers
• Data Explorer
• My Personal Objects folder
• My Reports folder
• My Favorites folder
• My Answers folder
• My Objects folder
• Everyone user group
Parameters
Are variables that you can reuse across a workflow to define process properties.
Parameters can be provided as part of a workflow, as part of an independent file to execute the workflow, or as input from a user when executing the workflow.
Parameters can also be used as part of a workflow to create controlled loops of processes.
Parameters are very useful in defining property values that are repeatedly used within a workflow or across different workflows.
Parameters can be provided as part of a workflow, as part of an independent file to execute the workflow, or as input from a user when executing the workflow.
Parameters can also be used as part of a workflow to create controlled loops of processes.
Parameters are very useful in defining property values that are repeatedly used within a workflow or across different workflows.
Parent Dependency
When an object is used by the definition of other objects
Processes
Are tasks that your workflow may execute.
They represent either MicroStrategy functions or external actions.
MicroStrategy-specific processes support a wide variety of operations, including importing an Object Manager configuration package, executing a Command Manager script, retrieving Intelligence Server status, or even running other System Manager workflows.
They represent either MicroStrategy functions or external actions.
MicroStrategy-specific processes support a wide variety of operations, including importing an Object Manager configuration package, executing a Command Manager script, retrieving Intelligence Server status, or even running other System Manager workflows.
Project Locking
When you open a project in Object Manager,
you place a lock on the project, which prevents other MicroStrategy
users from modifying any objects in the project in Desktop or
MicroStrategy Web.
Project Merge Wizard
With Project Merge Wizard, there is a
source project, the project from which you are migrating information,
and a destination project, the project to which you are migrating
information.
Purging Change Journal features
You can purge change journal transactions based on a selected date.
All entries older than the selected date are purged from the change journal.
You can purge the change journal for an individual project, or for all projects in the metadata.
All entries older than the selected date are purged from the change journal.
You can purge the change journal for an individual project, or for all projects in the metadata.
Rules of the Project Merge Wizard
The wizard automatically determines the objects that should be migrated.
It looks at every object in the source project and determines whether to copy the object as follows:
• If the object exists identically (same version) in both projects, it does not copy the object
• If the object exists only in the source project (that is, a new object), it copies the object to the destination project
• If the object exists in both projects but its definitions are slightly different, it will copy or not copy the object to the destination project based on rules you define
It looks at every object in the source project and determines whether to copy the object as follows:
• If the object exists identically (same version) in both projects, it does not copy the object
• If the object exists only in the source project (that is, a new object), it copies the object to the destination project
• If the object exists in both projects but its definitions are slightly different, it will copy or not copy the object to the destination project based on rules you define
Script Outline
Is a script template provided by Command
Manager that you customize with your enterprise-specific information,
and then execute against the metadata.
Script Outline Syntax - Brackets [ ]
• —Denotes optional tokens.
For example, in the following script outline syntax, the LOGIN and PASSWORD tokens are optional. You can retain them and replace the respective placeholders with literal text, or you can delete them. If you delete them, when the script is executed, only the database login will be created. *CREATE DBLOGIN "<dblogin_name>" [LOGIN
"<database_login>"] [PASSWORD "<database_pwd>"];*
>Brackets are included as a flag to denote optional syntax only. You must delete them prior to executing the script.
For example, in the following script outline syntax, the LOGIN and PASSWORD tokens are optional. You can retain them and replace the respective placeholders with literal text, or you can delete them. If you delete them, when the script is executed, only the database login will be created. *CREATE DBLOGIN "<dblogin_name>" [LOGIN
"<database_login>"] [PASSWORD "<database_pwd>"];*
>Brackets are included as a flag to denote optional syntax only. You must delete them prior to executing the script.
Script Outline Syntax - Pipes ( | )
Denotes user choice between the tokens
listed in the script outline. For example, in the following script
outline syntax, the APPLY SECURITY FILTER token can apply to either the
USER token or GROUP token. Therefore you must delete the token to which
the security filter doesn't apply. APPLY SECURITY FILTER
"<sec_filter_name>" [FOLDER "<location_path>"] TO ([USER]
"<login_name>" | [USER] GROUP "<group_name>") ON [PROJECT]
"<project_name>";
>Pipes are included as a flag to denote a selection between tokens only. You must delete them prior to executing the script.
>Pipes are included as a flag to denote a selection between tokens only. You must delete them prior to executing the script.
Script Outline Syntax - Placeholders
Enclosed in quotes and denoted with the
characters < >. You replace a placeholder with literal text, but
retain the quotes.
For example, the Create_DBLogin_Outline script contains the placeholder "<dblogin_name>"
For example, the Create_DBLogin_Outline script contains the placeholder "<dblogin_name>"
Script Outline Syntax - Semi-colon
Are placed at the end of the script that denotes completion of the script.
Script Outline Syntax - Tokens
Reserved words that have specific meaning
to the SQL parser. For example, the Create_DBLogin_Outline script
contains the token CREATE DBLOGIN, which, when executed, creates
database logins.
Tokens are displayed in a script outline in all capital letters and by default, are displayed in color.
Tokens are displayed in a script outline in all capital letters and by default, are displayed in color.
The Search for Objects tool in Object Manager
Is very similar to the tool you have in Desktop.
However, in Object Manager, at the project level you can only search for application and schema objects.
You can only search for configuration objects from the Create Configuration Packaged window, accessible at the project source level.
However, in Object Manager, at the project level you can only search for application and schema objects.
You can only search for configuration objects from the Create Configuration Packaged window, accessible at the project source level.
Statistics Tables
You use the MicroStrategy Configuration Wizard to create statistics tables.
Intelligence Server then populates the statistics tables with data it records based on your specifications.
Intelligence Server then populates the statistics tables with data it records based on your specifications.
System Manager
Is a cross-platform product that eases end-to-end deployment, administration, and migration processes that typically involve multiple MicroStrategy products and multiple system processes.
You can use the intuitive System Manager graphical interface to define workflows that combine and automate many system tasks.
These include checking for server status, backing up projects, sending alert emails after system status changes, rebooting servers, and so forth.
Besides automation, System Manager enables you to standardize common processes into set workflows to ensure consistency and enforce best practices.
You can use the intuitive System Manager graphical interface to define workflows that combine and automate many system tasks.
These include checking for server status, backing up projects, sending alert emails after system status changes, rebooting servers, and so forth.
Besides automation, System Manager enables you to standardize common processes into set workflows to ensure consistency and enforce best practices.
To disable temporary locking of Projects in Object Manager
• Open configuration in read-only mode — Enables MicroStrategy users to make changes to configuration objects such as users and groups.
• Open project in read-only mode —Enables MicroStrategy users to modify application and schema objects in projects.
• Open project in read-only mode —Enables MicroStrategy users to modify application and schema objects in projects.
To enable change journaling at the Project Level
In the Project monitor, right-click the appropriate project, point to Monitor Historical Activity, and select Manage Change Journal.
OR
In the Project Configuration Editor, under Project definition, select Change Journaling
OR
In the Project Configuration Editor, under Project definition, select Change Journaling
To enable change journaling at the Server Level
In Desktop, on the Administration menu, select Manage Change Journal.
OR
In the Intelligence Server Configuration Editor, under the Server Definition category, select Change Journaling.
OR
Under the Administration icon, expand System Monitors, right-click Change Journal Transactions, and select Manage Change Journal.
OR
In the Intelligence Server Configuration Editor, under the Server Definition category, select Change Journaling.
OR
Under the Administration icon, expand System Monitors, right-click Change Journal Transactions, and select Manage Change Journal.
Transactions not added as part of change journaling
- subscriptions
- addresses
- contacts
- history list
- addresses
- contacts
- history list
Types of Processes
• MicroStrategy Products—These
processes enable you to perform MicroStrategy functions related to
object migration, BI environment creation and maintenance, and other
administrative tasks. Examples include Import Package, Get Server
Status, and Intelligence Server, which enables you to execute Command
Manager scripts, among others.
• System Tools—These processes enable you to perform tasks external to MicroStrategy. Examples include Execute SQL, Send Email, Wait, and Download Using FTP, among others.
• Cloud Computing—These processes enable you to launch and manage Amazon Cloud instances and VMware virtual machines.
• System Tools—These processes enable you to perform tasks external to MicroStrategy. Examples include Execute SQL, Send Email, Wait, and Download Using FTP, among others.
• Cloud Computing—These processes enable you to launch and manage Amazon Cloud instances and VMware virtual machines.
Update Package
Is saved in a file, and can be freely copied and moved between computer systems.
You can import an update package into a project or project source from within Object Manager, using a Command Manager script, using the command line, or using a System Manager workflow.
This feature is useful in situations where you may need to update the objects in several folders at once, or you may need to update the objects during the time when the source project is offline.
You can import an update package into a project or project source from within Object Manager, using a Command Manager script, using the command line, or using a System Manager workflow.
This feature is useful in situations where you may need to update the objects in several folders at once, or you may need to update the objects during the time when the source project is offline.
Validate a Workflow
Before you execute a workflow, you should
validate it to make sure there are no missing components and there will
be no unexpected behavior.
You should manually review your workflow for the following:
• All non-exit processes are sources for connectors that handle all possible exit codes.
• There is at least one exit process.
• The workflow paths make logical sense. In particular, you should eliminate the possibility of unregulated loops of processes.
You should manually review your workflow for the following:
• All non-exit processes are sources for connectors that handle all possible exit codes.
• There is at least one exit process.
• The workflow paths make logical sense. In particular, you should eliminate the possibility of unregulated loops of processes.
When to use Baseline vs. Baseline
• Neither source nor target projects are available for testing
When to use Baseline vs. Project
• Having only one test server
• Modifying the results of a single report
• Modifying the results of a single report
When to use Project vs. Project
• Moving a project from one environment to another, for example, out of development and into production
• Modifying the data warehouse ODBC information (executing against a different warehouse)
• Migrating Intelligence Server to a different operating system
• Upgrading to a new version of MicroStrategy
• Modifying the data warehouse ODBC information (executing against a different warehouse)
• Migrating Intelligence Server to a different operating system
• Upgrading to a new version of MicroStrategy
When to use Single Project
• Maintaining the warehouse (deleting tables)
• Altering the project schema
• Changing user ACLs or privileges
• Changing VLDB settings
• Changing ODBC information
• Migrating Intelligence Server to a different operating system
• Upgrading to a new MicroStrategy version
• Altering the project schema
• Changing user ACLs or privileges
• Changing VLDB settings
• Changing ODBC information
• Migrating Intelligence Server to a different operating system
• Upgrading to a new MicroStrategy version
When you purge the Change Journal from within the Change Journal Manager
You can only purge transactions for the configuration objects or for all projects at one time.
You cannot purge transactions for a specific project.
You cannot purge transactions for a specific project.
When you copy an attribute or fact from one project to another
Object Manager copies and updates any tables on which the attribute or fact definition is based.
This includes warehouse tables, MDX tables, and XDA tables.
If a table already exists in the destination project, you need to resolve the conflict.
This includes warehouse tables, MDX tables, and XDA tables.
If a table already exists in the destination project, you need to resolve the conflict.
When you copy an object
Object Manager searches for that object's child dependencies and copies those objects too.
For example, when you copy a folder, Object Manager copies all child objects and subfolders of that folder.
For example, when you copy a folder, Object Manager copies all child objects and subfolders of that folder.
You can duplicate a project
Using the Project Duplication Wizard in MicroStrategy Object Manager or MicroStrategy Desktop
You can import an Update Package into a project or project source using any of the following methods:
• From within Object Manager
• Using a Command Manager script
• From the Command Line, using the stand-alone Import Package utility
• Using a System Manager workflow
• Using a Command Manager script
• From the Command Line, using the stand-alone Import Package utility
• Using a System Manager workflow
You can copy the following configuration objects within a project source or across project sources:
• Database Instances
• Database Connections
• Database Logins
• DBMS
• Devices
• Transmitters
• Events
• Languages
• Schedules
• Groups and Users
• Security Roles
• Database Connections
• Database Logins
• DBMS
• Devices
• Transmitters
• Events
• Languages
• Schedules
• Groups and Users
• Security Roles
Comments
Micro Strategy Online Training
Micro Strategy Courses
ui path training