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

KB41308: On a WebLogic Web Server, Mobile Configurations stored in MicroStrategy Mobile server are missing after the Weblogic server is restarted


Community Admin

• Strategy


With MicroStrategy Mobile 9.x and higher installed on a Weblogic web server, administrators must take caution regarding the use of this type of Web Server. Mobile Configurations are stored as XML files and generated by the Mobile Server. When the Weblogic server is restarted, these XML files may be automatically deleted by the server.

SYMPTOM:
With Strategy Mobile 9.x and higher installed on a Weblogic web server, administrators must take caution regarding the use of this type of Web Server. Mobile Configurations are stored as XML files and generated by the Mobile Server. When the Weblogic server is restarted, these XML files may be automatically deleted by the server. Mobile Devices may require reconfiguration when these XML files are deleted.
 
CAUSE:
This is not a Strategy software issue. The Weblogic server may be deleting these files automatically.
 
This can be expected behavior depending on the Weblogic deployment method. Web administrators have two methods of deploying Strategy Web 9.x and higher:

  • Non-exploded directory
    The Strategy Mobile 9.x and higher .WAR file is placed in a deployment directory and automatically unpackaged by the Weblogic server. Strategy refers to this as the "Development" method of deploying Web. This .WAR file is decompressed automatically and deployed by the WebLogic server.
  • Exploded directory
    The Strategy Mobile 9.x and higher is "exploded" by decompressing the .WAR file into its full directory structure. This directory can then used as a backup location for the changes made by the Mobile Server. Weblogic will then deploy this directory to end-users, including all the modified/new files.

If the Weblogic administrators chose the non-exploded / "development" deployment, then the server is behaving expectedly. The .war file, if left unmodified, does not contain the created Configuration XMLs. When the Weblogic server redeploys the .war file on startup, the generated XML files are deleted, since they do not match the "source" .war file. Configurations and other customizations will be lost when the server is restarted or the application is redeployed. 
 
ACTION:
There are two options, depending on your method of deployment:

  1. Redeploy Strategy Mobile 9.x and higher as a "Exploded Directory." Frequently back up the deployed installation to the source exploded directory.
  2. If a Non-expoloded deployment is preferred, frequently backup the deployed directories and recompress the Mobile server into a .war file. This is essentially the same action as above, but recompressed into a .WAR file.

Be sure to backup this directory, when you wish to preserver Mobile Configurations specifically:
\WEB-INF\xml\mobile
 


Comment

0 comments

Details

Knowledge Article

Published:

April 12, 2017

Last Updated:

April 12, 2017