EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB47604: How to Modify the FrameProcessor.Xml File Without Making Changes to the Default File


Community Admin

• Strategy


This is a sample of how to modify the timeout property in FrameProcessor.xml file without changing the out of the box FrameProcessor.xml file.

Sometimes changing the out of the box FrameProcessor.xml will corrupt the file causing other issues to Strategy Web.
 
This is a sample of how to modify the timeout property in FrameProcessor.xml file without changing the out of the box FrameProcessor.xml file.
Example:
 
Using the Web Customization Editor to create a plug-in
 
Strategy SDK provides a Web Customization Editor that can be used to create a customization plug-in. The following steps show how to create the plug-in.
 

  1. Launch the Web Customization Editor
  2. Create a new plug-in and give it a meaningful name
  3. Go to your Application Root folder then to the plug-in folder created in step 2
  4. Go to the xml folder inside your plug-in folder
  5. Create a a new folder and name it blocks
  6. Create a new xml file inside this folder
  7. Copy and paste the code below
  8. Save the file as FrameProcessors.xml


<!DOCTYPE block SYSTEM "../dtds/blockLibrary.dtd">

          <!-- Frame processor --> 
             <block>
               <assignments>
                 <property name="timeout">50000</property>
               </assignments>
             </block>

 
Without using the Web Customization Editor

  1. Create a new folder in the plugins folder and give it a meaningful name
  2. Create the folder structure as the screenshots below
  3. Follow steps 6-8 shown above.

 
Inside the plug-in folder created in step 1

ka04W000001MKy7QAG_0EM440000002GUY.png

 
 
 
 
 
 
 
 
Inside WEB-INF                                                                                                                                                                                                                                                                        

ka04W000001MKy7QAG_0EM440000002GUW.png

 
Inside xml
 

ka04W000001MKy7QAG_0EM440000002GUZ.png

 
 
The example provided in this document is provided “as-is” and user has read the following customization warning:
ADDITIONAL INFORMATION:
The Strategy SDK allows you to customize several Strategy products and extend and integrate the Strategy business intelligence functionality into other applications. However, before changing the way Strategy products look or behave, it is helpful to understand how the application is built. For more information regarding the Strategy products or the process of customizing Strategy products, please refer to Strategy Developer Zone (https://developer.microstrategy.com).
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 https://www.microstrategy.com/us/services/support/contact.
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.
 


Comment

0 comments

Details

Knowledge Article

Published:

March 31, 2017

Last Updated:

March 31, 2017