KB42886: Custom Changes are not Being Applied when Redeploying MicroStrategy War File with Custom Plugins when Using WebLogic Application Server

When deploying a Strategy War file on a WebLogic application server, certain temporary files are also extracted to be used later on with WebLogic. Because of these temporary files, users may not see any changes take place if an altered WAR file is deployed.
 
In order to clean the temporary files and see the reflected changes in the new WAR file, perform the following steps:

1. Clean the temp files under /var/tmp/MicroStrategy/. This will ensure that the Strategy temporary files are no longer present in the application server.
2. Clean the config.xml under /usr0/webapp/bea/user_projects/<domain>/config/. After each deployment a node will be created in this file. A node has the following structure:
   <app-deployment>
                   <name>_appsdir_”WAR FILE NAME”_war</name>
                   <target>AdminServer</target>
                   <module-type>war</module-type>
                   <source-path>war</ source-path >
                   <security-dd-model>DDOnly</ security-dd-model >
                   <staging-mode>stage</ staging-mode >
   <app-deployment>
3. In  WebLogic 9.x and newer,  removal of cache requires deleting each server instance's tmp folder.

General locations of the tmp folder for WebLogic 9.x and higher versions
WIN: C:\bea\user_projects\domains\yourdomain\servers\yourserver\tmp
UNIX: /bea/user_projects/domains/yourdomain/servers/yourserver/tmp
The following commands may be used to clear the cache:
WIN: rd C:\bea\user_projects\domains\yourdomain\servers\yourserver\tmp \s
UNIX: rm -rf /bea/user_projects/domains/yourdomain/servers\yourserver/tmp
 
The example provided in this document is provided “as-is” to the user and assumes that the user:

• Can program, compile (e.g. javac, jikes, etc.), and execute Java programs
• Can configure environment variables (e.g. JAR files, property files, etc.)
• Have all the necessary tools to create Java applications (JDK, IDE, etc.)
• Has access to the Strategy SDK documentation.
• Has read the customization warning at the bottom of this document

 
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:

• Strategy Web Universal (JSP): {web_root}/WEB-INF/lib directory.
• Strategy Web (.NET): Program Files\Common Files\Strategy directory.

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://community.strategy.com/topic/0TO44000000FliLGAS/sdk).
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/en/support/contact-support.
 
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.