on 06-03-2009 9:52 AM
Hi,
I am having a problem with the DSD application on a mobile device.
I have loaded the:
JVM
DB2e
MI
MDSD 2.1
onto the mobile device (the mobile has been restarted after each application has been loaded)- the backend has been confiereged using the configeration guide.
When I start the application in MI by selecting the MDSD button the mobile device shows a processing icon (like egg timer) but progresses no further and does not exit this state.
In addittion I cannot locate any error logs that identify why the application has appeared to stop.
Help on this would very much be apprechiated!
Thanks James
Hello James,
You said on the click of the MDSD button on the MI Home screen the app shows the wait cursor and does not move. Please set the trace level to "All" in the the MI Home menu Settings -> Trace and then click on the MDSD button. And send the trace. Based on the logs I will be able to exactly tell you what needs to be done.
Regards
Anup
http://www.indience.com/index.php/products/mobile-direct-store-delivery.html
/people/sridhar.dilip/blog/2009/05/04/sap-mdsd-integration-with-sap-crm-survey-suite
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
The log reads:
[20090608 11:08:45:254] W [MI/CCMS ] File not found during Config Info collection: /Windows/Start Menu/MIServer.lnk
[20090608 11:13:47:325] W [MI/Core ] The SSL support feature is not properly configured. Https is not available.
[20090608 11:14:50:644] W [MI/Security ] Error while creating MIAUTH sync bo (no SyncBoDescriptor for MIAUTH available); contact SAP support
[20090608 11:14:50:660] W [MI/Security ] Cannot start authority query for user because SyncBoDescriptor for MIAUTH is not available
[20090608 11:19:33:672] W [MI/Core ] The SSL support feature is not properly configured. Https is not available.
[20090608 11:20:51:723] W [MI/Security ] Error while creating MIAUTH sync bo (no SyncBoDescriptor for MIAUTH available); contact SAP support
[20090608 11:20:51:743] W [MI/Security ] Cannot start authority query for user because SyncBoDescriptor for MIAUTH is not available
Thanks James
hi
The trace file;
[20090608 11:05:39:917] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON
[20090608 11:05:39:917] I [MI/API/Logging ] ***** Mobile Infrastructure version: MI 70 SP 15 Patch 3 Build 200903191315
[20090608 11:05:39:917] I [MI/API/Logging ] ***** Current timezone: GMT[20090608 11:05:39:917] I [MI/API/Logging ] ***** Current Trace Level: 50
[20090608 11:08:45:260] E [MI/CCMS ] Config Info: /Windows/Start Menu/MIServer.lnk
[20090608 11:08:45:263] E [MI/CCMS ] java.io.FileNotFoundException: /Windows/Start Menu/MIServer.lnk
java.io.FileNotFoundException: /Windows/Start Menu/MIServer.lnk
at java.io.FileInputStream.<init>()
at java.io.FileInputStream.<init>()
at java.io.FileReader.<init>()
at com.sap.ip.me.ccms.configinfo.ConfigInfoCollector.addMobileEngineLnk()
at com.sap.ip.me.ccms.configinfo.ConfigInfoCollector.addConfigInfoToContainer()
at com.sap.ip.me.ccms.configinfo.ConfigInfoCollector.createConfigInfoContainer()
at com.sap.ip.me.ccms.configinfo.ConfigInfoCheckerInboundProcessor.process()
at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()
at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()
at com.sap.ip.me.awtapps.home.Home.doSync()
at com.sap.ip.me.awtapps.home.HomeFrame.doUserActionSync()
at com.sap.ip.me.awtapps.home.HomeFrame.userActionSync()
at com.sap.ip.me.awtapps.home.HomeFrame.access$000()
at com.sap.ip.me.awtapps.home.HomeFrame$SyncThread.run()
at java.lang.Thread.run()
Hello Richard,
The issue is you are not using IBM DBe2 persistence in this installation, The file IO option is enabled by default and does not work with SAP MDSD.
So you have to redo the complete MI install except the Crème installation.
Install:
1. MI cab
2. Assign and Download DB2e add-on 8.2.4 or 9.0 from the NetWeaver Admin console to the MI installation. This installs asks you to restarts the MI etc .
3. Assign and Download MDSD component to the MI install.
Regards
Anup
Hello James,
If you talking about installing the DB2e cab provided by IBM, The MI cannot know that such thing is available and will not use it. It can only identify add-ons which are deployed via SAP MI and loads them accordingly.
These addons also come with some preoperty settigns etc which also important for the MI during runtime.
You have to get a copy of this db2e add-on from SAP again.
Regards
Anup
.
Hi Akil
MI 7.0 (Latest patch)
DB2e 9.1.2
and the maifest on the device is:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.4
Created-By: 1.4.2_12-b03 (Sun Microsystems Inc.)
Implementation-Version: official
Specification-Title: Mobile Direct Store Delivery
Specification-Version: 2.1
Implementation-Title: com.sap.dsd.appctrl.DSDMain
Main-Class: com.sap.dsd.appctrl.DSDMain
Implementation-Vendor-Id: sap.com
ApplicationClass: com.sap.dsd.appctrl.DSDMain
Implementation-Vendor: SAP
Description: Mobile Direct Store Delivery
Specification-Vendor: SAP AG
Build-ID: 2.1.00.112755
Thanks James
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear James,
You are on what Sp levels at both server and mobile client.
What is WM version u use.
1 creme( Which version )
2 MAP70.....core.core.cab
3 DB2e
4 MDSD2.1 application
Regards,
Akhil
Edited by: Akhil Rastogi on Jun 3, 2009 11:00 AM
Edited by: Akhil Rastogi on Jun 3, 2009 11:02 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.