In service-oriented architecture, discrete chunks of functionality are built as services that can be accessed by many applications in many different ways. In Strategy Web, these services are called tasks. Once an operation has been defined as a task in Strategy Web, it can be called as a service from anywhere using any protocol. What this means is that you need to build a task only once, and it can then be used everywhere. Regardless of whether a task is called from HTTP, URL, Web Services, COM, .NET, or Java, the underlying implementation is the same.
The ability to discovery and use tasks in Strategy Web is based on the role of the user. This role-based security mechanism ensures that tasks are exposed only to users with proper privileges. Task-related roles include Task Invokers, Task Developers, and Web Server Administrators. The user's role determines whether available tasks can be viewed in a GUI application, which tasks that can be viewed and executed, and which servlet is used to execute a task.
Task Viewer
The Task Viewer application is available to users with the role of Task Developer. It provides the names, descriptions, and parameters for all non-administrative public tasks that are currently registered. The topics in this section describe how developers can use this application to build and test URLs that invoke non-administrative tasks—both out-of-the-box tasks and custom-built tasks that have been registered.
Task Administrator
The Task Administrator application is available to users with the role of Web Server Administrator. It provides the names, descriptions, and parameters for all of the currently registered public tasks, both administrative and non-administrative tasks. The topics in this section describe how administrators can use this application to build and test URLs that invoke tasks—both out-of-the-box tasks and custom-built tasks that have been registered.
Private Tasks
By default there is a large group of tasks automatically hidden from the user in both the Task Administrator and Task Viewer application. These private tasks are typically used by other tasks and are not usually intended for development. However, in certain cases it may be necessary to use one of these tasks. The following steps will make these tasks public:
Alternatively, if it is not required to show the entire list of private tasks in the taskAdmin page, it is possible to show private tasks individually by scrolling through the list of private tasks and remove the <privateTask> entry from the list.
PREREQUISITES:
For the sample to work, the Strategy Web JAR files must be accessible by the Java Runtime
Environment. The Strategy Web JAR files can be found under:
ADDITIONAL INFORMATION:
The Strategy SDK allows you to customize the standard Strategy Web interface, and extend and integrate the Strategy business intelligence functionality into other applications. However, before changing the way Strategy Web products look or behave, it is helpful to understand how the application is built. For more information regarding the Strategy Web architecture or the process of customizing Strategy Web, please refer to Strategy Developer Zone (https://resource.microstrategy.com/msdz/).
To access the Strategy Developer Zone, you must have access to the Strategy Knowledge Base, you must have purchased the Strategy SDK, and you must be current on your Strategy maintenance agreement. If you are a US-based business and believe that you satisfy all three of these conditions but you do not have access to the Strategy Developer Zone, please contact Strategy Technical Support at support@microstrategy.com or at (703) 848-8700. If you are an international business, please contact Strategy Technical Support at the appropriate email address or phone number found at http://www.microstrategy.com/Support/ContactUs.asp.
CUSTOMIZATION WARNING:
This customization is provided as a convenience to Strategy users and is only directly applicable to the version stated. While this code may apply to other releases directly, Strategy Technical Support makes no guarantees that the code provided will apply to any future or previous builds. In the event of a code change in future builds, Strategy Technical Support makes no guarantee that an updated version of this particular customization will be provided. In the event of a code change in future builds, Strategy may not be able to provide additional code on this matter even though this customization is provided at this time for this specific build. For enhancements to this customization or to incorporate similar functionality into other versions, contact your Account Executive to inquire about Strategy Consulting assistance.
