If you are on the receiving side of an exported archive file from a different Mobile Web Studio installation, use the Mobile Web Studio–Export/Import dialog box to import entities into your Mobile Web Studio installation. You must place the archived XML file that you want to import on the same server as your Mobile Web Studio installation.
If you are importing applications from a previous release,
or are upgrading a UA server from 7.0 to 8.0, you might end up with
templates associated with the application that are not appropriate
for 8.0 or cause execution failures. For example, the BlackBerry
Online template has changed with 8.0, the Nokia Online template
is new, and applications created in 7.0 may use XSL templates that
no longer work with 8.0.
To fix this, either edit the application so that each device type points to the correct template; or edit the template itself so that it is correct. If you edit the template, there is no need to edit the application. Decide which to do based on whether the problems is with the template definition, or with the application pointing to the wrong template.
Importing a file into Mobile Web Studio
Log in to the Mobile Web Studio as a user that has the StudioAdmin and PortalAdmin role.
Select Build | Applications from the Mobile Web Studio left pane.
Click Import/Export on the Application Manager toolbar.
When the Export/Import window displays, click the Import tab.
Complete these fields:
File Name – enter the name of the XML file to import, or click Browse to locate the file using the Choose File dialog box.
Click Upload to upload the file to Mobile Web Studio. When a prompt confirms that the upload was successful, click OK.
Do not import and export documents from the \tmp\upload\ directory
if the client browser and the UA server are running on the same
machine, as this truncates the XML file.
Click View to view the XML file contents.
Import Catalog As Active – make the imported catalog the default display catalog. The imported XML document can contain more than one catalog, but only one catalog is marked as the default display catalog—approved and active. If you import this catalog as active, it deactivates the current default catalog and replaces it with the new catalog. You can export more than one catalog at a time because agents can refer to catalogs that are inactive or not approved.
Override Existing Entities – have imported entities (pages, page groups, applications, and agents) replace an equivalent entity with the same name; for example, replace a page with an imported page with the same name. These entities do not use versioning.
If you are importing applications from a previous version,
such as UA 7.0, do not check the Override Existing Entities box.
If you do, older templates will override new templates, causing
problems with your applications.
Import Entities As Active – import the new entities as active but the catalog as inactive, which makes the imported entities (but not the catalog) available to Portal Interface users.
Set Deferred Update For All Portal Users – indicates whether to notify all portal users of a change in the portal content so that they can refresh their view the next time they log in to the portal.
During the import process, if you do not select Set
Deferred Update For All Portal Users, the Portal Interface user
must perform an Update for each guest page or guest page group.
Click Upload to move the file to the UA server.
Click Import. When a prompt confirms that the import was successful, click OK.
Click View Log to review the import operation’s activities.
Click Close to exit the Mobile Web Studio–Export/Import window.
Select Build | Catalogs from the Mobile Web Studio left pane.
Select Approved from the Catalog Manager Status menu. If you chose to import a new catalog as active, you should see the catalog in the detail view with a check mark in the Active column.
If you chose to import the catalog as active, click Update on the Catalog Manager toolbar to update Portal Interface on the same application server with the new default display catalog.
When you see confirmation that the operation was successful, click OK.
If you are importing mobile applications from a previous version of UA, test out the applications. You may need to repair them or redeploy them in the new version of UA for them to work. For example, you may need to:
Modify fixup JSP.
Modify templates.
Redeploy applications to MobiLink.
Recapture applications.
Optionally, you can add applications to Portal Interface:
Log in to Portal Interface.
You can add applications only to your personal page and page group.
If the page.group global property is turned on, create a page group, then add a new page to that page group.
If the page.group property is turned off, create a new page.
See the Unwired Accelerator Administration
Guide for more information about setting the page.group
property.
Click Add Application. When the Add Application window appears, it should display the contents of the new default display catalog.
When you import portal objects (templates, catalogs,
and so on) they maintain their original owner; that is, the Owner
column in the detail view for objects lists the person who originally
created the object, not the person performing the import.
