Topic
  • 6 replies
  • Latest Post - ‏2012-10-02T16:14:49Z by gsander
lcrivas
lcrivas
9 Posts

Pinned topic [Solved] Need steps for Manually Configuring Security of App Center

‏2012-09-28T19:32:33Z |
We are running the WL V5 FP3 Server on Linux. Application Center is starting. It appears that the default Security is not configured as is required. WL is running on an existing Linux WAS8 ND install. Worklight components are being manually configured. The Admin guide had instructions for this for the WL Server, but not much for the manual configuration of the App Center. Can instructions for manually configuring the WLAC security, after the WAR is installed, be provided?

The current error is:

Caused by: org.apache.wink.json4j.JSONException: com.ibm.puremeap.resources.exceptions.AccessControlException: MOBILEMGMT0401W: No user appears to be logged, check the Application Center security configuration.

After you launch the ./wlappcenter url, you get the error:

"MOBILEMGMT0401W No user appears to be logged, check the
Application Center security configuration"
  • Tissandier
    Tissandier
    2 Posts

    Re: Need steps for Manually Configuring Security of App Center

    ‏2012-10-01T09:48:31Z  
    You should be able to find how to manually install Application Center for Websphere in the documentation at : http://public.dhe.ibm.com/ibmdl/export/pub/software/mobile-solutions/worklight/docs/wl_5_0_app_center.pdf

    Application Center requires that you configure the security for the web application, when this is not done, you are getting this message.

    Hope this helps.

    -Emmanuel
  • Tissandier
    Tissandier
    2 Posts

    Re: Need steps for Manually Configuring Security of App Center

    ‏2012-10-01T09:48:36Z  
    You should be able to find how to manually install Application Center for Websphere in the documentation at : http://public.dhe.ibm.com/ibmdl/export/pub/software/mobile-solutions/worklight/docs/wl_5_0_app_center.pdf

    Application Center requires that you configure the security for the web application, when this is not done, you are getting this message.

    Hope this helps.

    -Emmanuel
  • lcrivas
    lcrivas
    9 Posts

    Re: Need steps for Manually Configuring Security of App Center

    ‏2012-10-01T23:10:09Z  
    The links were helpful, but we are still getting errors during login... They appear to be DB related. After entering login credentials on the login screen, we get :

    MOBILEMGMT0400W Error while processing access control "com.ibm.urmeap.resources, exceptions.SystemException: PUREMAP.PRINCIPALS is an undefined name.SQLCODE=-204, SQLSTATE=42704, DRIVER=3.64.82"

    It looks like there needs to be some updates to the WRKLGHT database to support the Application Center.... our target install is WAS V8 ND cell with DB2 UDB.
    There is a DERBY sql (create-appcenter-derby.sql) file, but is there one specific for DB2 UDB? I assume DB2 UDB is fully supported, right?

    Thanks!!
  • slowhand
    slowhand
    35 Posts

    Re: Need steps for Manually Configuring Security of App Center

    ‏2012-10-02T01:45:36Z  
    • lcrivas
    • ‏2012-10-01T23:10:09Z
    The links were helpful, but we are still getting errors during login... They appear to be DB related. After entering login credentials on the login screen, we get :

    MOBILEMGMT0400W Error while processing access control "com.ibm.urmeap.resources, exceptions.SystemException: PUREMAP.PRINCIPALS is an undefined name.SQLCODE=-204, SQLSTATE=42704, DRIVER=3.64.82"

    It looks like there needs to be some updates to the WRKLGHT database to support the Application Center.... our target install is WAS V8 ND cell with DB2 UDB.
    There is a DERBY sql (create-appcenter-derby.sql) file, but is there one specific for DB2 UDB? I assume DB2 UDB is fully supported, right?

    Thanks!!
    > PUREMAP.PRINCIPALS is an undefined name.SQLCODE=-204, SQLSTATE=42704, DRIVER=3.64.82

    This means that you are accessing the Application Center's database through an unsupported database driver.

    In Worklight 5.0.0.x, the Application Center's database supports only Derby and has the database name MOBILE
    and the schema PUREMEAP. You are trying to use a DB2 driver for it. DB2 is supported for the WRKLGHT and
    WLREPORT databases, but not for MOBILE.

    --slowhand
  • lcrivas
    lcrivas
    9 Posts

    Re: Need steps for Manually Configuring Security of App Center

    ‏2012-10-02T15:08:29Z  
    • slowhand
    • ‏2012-10-02T01:45:36Z
    > PUREMAP.PRINCIPALS is an undefined name.SQLCODE=-204, SQLSTATE=42704, DRIVER=3.64.82

    This means that you are accessing the Application Center's database through an unsupported database driver.

    In Worklight 5.0.0.x, the Application Center's database supports only Derby and has the database name MOBILE
    and the schema PUREMEAP. You are trying to use a DB2 driver for it. DB2 is supported for the WRKLGHT and
    WLREPORT databases, but not for MOBILE.

    --slowhand
    Hi,

    If we are able to modify the Derby sql file to be IBM UDB friendly, are there any known issues with using a current version of IBM UDB with the App Center? We are able to get beyond the errors seen before using IBM UDB.

    Thanks!
  • gsander
    gsander
    1 Post

    Re: Need steps for Manually Configuring Security of App Center

    ‏2012-10-02T16:14:49Z  
    • lcrivas
    • ‏2012-10-02T15:08:29Z
    Hi,

    If we are able to modify the Derby sql file to be IBM UDB friendly, are there any known issues with using a current version of IBM UDB with the App Center? We are able to get beyond the errors seen before using IBM UDB.

    Thanks!
    Up to IBM Worklight 5.0.0.3, only Derby is supported for the Application Center. DB2 is not supported for Application Center, and we currently do not recommend using DB2 with Application Center for the data base MOBILE.

    IBM Worklight 5.0.0.x uses various data bases: WRKLGHT, WLREPORT, MOBILE. The former two support DB2, the last one, which is used by Application Center, does not support DB2.

    Extending the range of supported platforms and data bases is under consideration for future versions.