cancel
Showing results for 
Search instead for 
Did you mean: 

Smart phone mobiliser 5.1 issue

Former Member
0 Kudos

Hello,

We have downloaded Mobiliser 5.1 from SMP.

Able to test web portal and it is working fine.

But while trying to test smart phone mobile client for Android we are getting issues as below log and attached the screen shot of the error coming on the Android console.

Mobiliser.log

2013-05-28 08:43:09,631 [jetty-54] DEBUG com.sybase365.mobiliser.money.security.token.CookiePolicyPersistentTokenBasedRememberMeServices - Remember-me login not requested.

2013-05-28 08:43:09,653 [jetty-204] DEBUG com.sybase365.mobiliser.money.security.umgr.impl.UmgrUserDetailsService - Loaded customer Customer #100 by identification type 5

2013-05-28 08:43:09,715 [jetty-204] DEBUG com.sybase365.mobiliser.money.security.token.CookiePolicyPersistentTokenBasedRememberMeServices - Did not send remember-me cookie (principal did not set parameter 'create_mobiliser_remember_me')

2013-05-28 08:43:09,715 [jetty-204] DEBUG com.sybase365.mobiliser.money.security.token.CookiePolicyPersistentTokenBasedRememberMeServices - Remember-me login not requested.

2013-05-28 08:43:10,550 [channelmgr-jmspickup-defaultQ-1] WARN  org.springframework.jms.listener.DefaultMessageListenerContainer - Could not refresh JMS Connection for destination 'defaultQ' - retrying in 5000 ms. Cause: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused

2013-05-28 08:43:12,222 [jetty-57] DEBUG com.sybase365.mobiliser.money.security.token.CookiePolicyPersistentTokenBasedRememberMeServices - Remember-me cookie detected

2013-05-28 08:43:12,254 [jetty-57] DEBUG com.sybase365.mobiliser.money.security.token.CookiePolicyPersistentTokenBasedRememberMeServices - Note: Cookie will not be marked as HttpOnly because you are not using Servlet 3.0 (Cookie#setHttpOnly(boolean) was not found).

2013-05-28 08:43:12,259 [jetty-57] DEBUG com.sybase365.mobiliser.money.security.umgr.impl.UmgrUserDetailsService - Loaded customer Customer #500000450 by identification type 1

2013-05-28 08:43:12,263 [jetty-57] DEBUG com.sybase365.mobiliser.money.security.token.CookiePolicyPersistentTokenBasedRememberMeServices - Remember-me cookie accepted

2013-05-28 08:43:14,713 [db-audit-dispatcher-2] DEBUG com.sybase365.mobiliser.money.auditmgr.DatabaseAuditManager - Writing batch of 8 audit(s) to the database

2013-05-28 08:43:14,715 [db-audit-dispatcher-2] DEBUG com.sybase365.mobiliser.money.businesslogic.audit.impl.AuditLogLogic - # Creating auditLog of type [LogoutRequest] for Customer = null.

2013-05-28 08:43:14,722 [db-audit-dispatcher-2] DEBUG com.sybase365.mobiliser.money.auditmgr.AuditDispatcher - Submitting audit dispatcher com.sybase365.mobiliser.money.auditmgr.DatabaseAuditManager@17d5c6 with delay 3000ms

2013-05-28 08:43:15,565 [channelmgr-jmspickup-defaultQ-1] WARN  org.springframework.jms.listener.DefaultMessageListenerContainer - Could not refresh JMS Connection for destination 'defaultQ' - retrying in 5000 ms. Cause: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused

2013-05-28 08:43:17,723 [db-audit-dispatcher-1] DEBUG com.sybase365.mobiliser.money.auditmgr.DatabaseAuditManager - No audits to process

2013-05-28 08:43:17,724 [db-audit-dispatcher-1] DEBUG com.sybase365.mobiliser.money.auditmgr.AuditDispatcher - Submitting audit dispatcher com.sybase365.mobiliser.money.auditmgr.DatabaseAuditManager@17d5c6 with delay 3000ms

Please guide us to overcome this issue.

with regards

Shankar.K

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Shankar,

See the above information, I am eager to learn where did you download the below JAR files?

from SAP's website or Sybase website's?

Sybase Mobiliser Reporting Module 5.1 (Available at Sybase Product Download Center)

- Download and copy into {MOBILISER_HOME}/bundles/17-crystalreports directory:

com.businessobjects.cvom_12.2.212.1346-1.0.1.jar

com.businessobjects.foundation.logging_12.2.212.1346-1.0.1.jar

com.businessobjects.reports.jdbinterface_12.2.212.1346-1.0.1.jar

com.businessobjects.visualization.pfjgraphics_12.2.212.1346-1.0.1.jar

com.crystaldecisions.common.keycode_12.2.212.1346-1.0.1.jar

com.crystaldecisions.reports.runtime_12.2.212.1346-1.0.1.jar

Sybase Mobiliser Reporting Module 5.1 (Available at Sybase Product Download Center)

- Download and copy into {MOBILISER_HOME}/bundles/20-mobiliser-reports-services
directory:

com.sybase365.mobiliser.util.report.crystalreports.impl-5.1.0.RELEASE.jar

com.sybase365.mobiliser.util.report.crystalreports.util-5.1.0.RELEASE.jar

com.sybase365.mobiliser.util.report.crystalreports.web-5.1.0.RELEASE.war

com.sybase365.mobiliser.util.report.watcher-5.1.0.RELEASE.jar

Sybase Mobiliser Reporting Module 5.1 (Available at Sybase Product Download Center)

- Download and copy into {MOBILSER_HOME}/bundles/18-report-fragments directory:

com.azalea.ufl.barcode_1.0-1.0.1.jar

-- Javed

aschlosser
Employee
Employee
0 Kudos

Javed,

You can find "Reporting Mobiliser" in SAP Market Place (if you go to Products A-Z, you'll find it under 'R')


Andreas

Former Member
0 Kudos
Hi Andreas,

Still we are not able to run the SMP application from the device/emulator.

Do we need to configure for reverse proxy/cross origin access.

Please advice.

with regards
Shankar.K

aschlosser
Employee
Employee
0 Kudos

can you please check the mobiliser.log.smartphone log file for any errors in there? you wouldn't need any special reverse proxy setup for local testing with Mobiliser and Android simulator set up on the same machine.

Andreas