Importing Mobile Web Studio objects protected by custom J2EE roles  Chapter 13: Changing the Portal’s Look and Feel

Chapter 12: Importing and Exporting Portal Objects

Restrictions

Files used by applications or templates You cannot export or import any files used by applications or templates. For example, a document type of application does not work in export/import because it involves installing document files from one deployment to another.

XML validation XML validation must be turned off for the import and export functionality to work:

  1. Open global.properties.xml in a text editor. The default location of this file if you are using Tomcat is x:\UnwiredAccelerator70\tomcat\webapps\onepage\config, where “x” is the drive on which the product is installed. If you are using EAServer, the location of this file is %JAGUAR%\EAServer\Repository\WebApplication\onepage\config.

  2. Find <Property name=“XmlValidation”> and verify that the value is set to “off.” If it is not, change it.

  3. Save the file and close the text editor.

  4. Restart the application server.

Multiple element applications To export an application to the Mobile Web Studio, which is used with M-Business Server to form the Unwired Accelerator product, the application can have only one element. Multiple-element applications are not compatible as mobile applications.

Templates The JSP template is the only valid template that can be used for exporting an application to M-Business Server.





Copyright © 2005. Sybase Inc. All rights reserved. Chapter 13: Changing the Portal’s Look and Feel

View this book as PDF