Strategy Web ASP is not available in the Strategy Cloud Environment (MCE) platform. Therefore, customers using Strategy Web ASP need to transition to either Strategy Web JSP or Strategy Library. While Strategy Web JSP offers a smooth, ‘like-for-like’ replacement to Strategy web ASP, we highly recommend moving from Strategy Web to Strategy Library for a modernized analytics experience with enhanced functionality and an improved user interface.
Strategy Web JSP vs Strategy Web ASP
Simplified Customization:
- With JSP, users can perform customization tasks more easily. The architecture separates the presentation layer from business logic, allowing for easier upgrades and maintenance. Customizations can be made without modifying default configuration files directly.
Strategy Custom Tags:
- Users can utilize a variety of custom tags in JSP to simplify code and enhance functionality. These tags allow for:
- Dynamic content generation.
- Layout changes for static and dynamic content.
- Conditional logic for displaying content based on specific criteria.
- Easy access to properties and values from Strategy objects.
Enhanced Task Infrastructure:
- Tasks are published through the Strategy SDK, enabling features like hierarchy browsing, prompt answer manipulation, and full metadata search.
Monitoring and Administrative Tasks:
- APIs are available for monitoring jobs, users, and database connections, which can enhance administrative capabilities.
If your application uses customizations written for Strategy Web ASP and you need guidance to migrate them to Strategy Web JSP, or you are interested in moving from Strategy Web to Strategy Library, please contact your account team or MicroStrategy Support.
