Manage Mobile Pages problems

Refer to the following information for help with common Manage Mobile Pages problems.

The right-hand pane in Manage Mobile Pages is empty

The problem is caused by missing unique IDs in the file wp_profile_root/PortalServer/config/AdminUniqueNamesMappingService.properties. Check that the following IDs are defined in the file:

MWP_EXTENDED_ATTRS=mwp.extattr
MWP_PRELOAD_NOTICE=mwp.preloadnotice
MWP_MANAGE_MOBILE_PAGES=mwp.managemobilepages

If the IDs are not defined, you can add them to the list of Resource Environment Providers used by WebSphere® Portal in the WebSphere Application Server Integrated Solutions Console.

Note: After you make changes to AdminUniqueNamesMappingService.properties, you must restart WebSphere Portal.

The Extended Properties portlet and Preload Notice portlet display a "Not Available" message

Check the logs for errors. Ensure that the WebSphere Portal database is available. Verify that the properties within the wp_profile_root/PortalServer/wp.mobile/wp.mobile.mwp/shared/app/config/attr-descriptor.xml file are correct and the file is well-formed. Restart WebSphere Portal after any changes to the attr-descriptor.xml file.

Empty Icon Resource drop-down list within the Extended Properties portlet

Check the logs for errors. Ensure that the Multi-Channel Server (MCS) database is available. Check the wp_profile_root/ConfigEngine/log/ConfigTrace.log for any errors after importing policies during the MCS installation. If you are manually importing image asset policies, ensure that they were imported successfully into the default MCS project (mobile-portal).

Cannot save properties in the Extended Properties portlet or the Preload Notice portlet

Check the logs for errors. Ensure that the WebSphere Portal database is available.

Problems with the preload notice database

You may encounter the following errors when there is an exception containing or related to the Preload Notice table:

Error message:

"SystemErr R javax.naming.NameNotFoundException: Context: ../nodes/../servers/WebSphere_Portal, name: jdbc/mpaplnDS: First component in name mpaplnDS not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
at com.ibm.ws.naming.jndicos.CNContextImpl.mapNotFoundException(CNContextImpl.java:4365)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1794)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1749)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1500)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:637)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:165)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:455)
at com.ibm.mwp.db.MWPDataStoreContext.init"

To resolve this issue, make sure that the datasource name in the mwp.pln.datasource property (in the mwp.properties file (located in the wp_profile_root/PortalServer/wp.mobile/wp.mobile.mwp/shared/app/config directory)) that connects to Preload Notice tables is correct. By default, the entry will be jdbc/mpaplnDS. Make sure to update the same in the mwp.properties file in case you changed the data source name by any chance.

Error message:

MWPDataStoreC E com.ibm.mwp.db.MWPDataStoreContext handleException CWMPU0200E: Error occurred during database access. Last SQL statement is [SELECT NAME,VALUE FROM db2admi.MWP_PLN_RULES WHERE NODE_ID = ? AND USER_ID = ? AND INT_ID = ? ].
java.sql.SQLSyntaxErrorException: Schema 'DB2ADMI' does not exist
at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(Unknown Source)
at org.apache.derby.jdbc.Driver40.newEmbedPreparedStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source

To resolve this issue, make sure that the schema name in the mwp.pln.datasource property (in the mwp.properties file (located in the wp_profile_root/PortalServer/wp.mobile/wp.mobile.mwp/shared/app/config directory)) for Preload Notice tables is correct. By default, the schema will be the same as db_username_of customization_database. Make sure to update the same in the mwp.properties file in case you have changed the schema name by any chance.