Developing SMP 3 Mobile App using Appbuilder, Kapsel and SMP 3 Trial – Part 3
Part 1 | Part 2 |
Part 3 |
Update: SAP’s recommended tool to develop SAPUI5 app is using SAP Web IDE. So I would suggest you to start with Web IDE instead of Appbuilder. More info: SAP Web IDE – Enablement
Deploying Kapsel on SMP server
A cordova project can be created from Appbuilder and can deploy the kapsel on SMP 3 server without using a command line interface (Kapsel plugins can be added to a cordova project through commands too ex. Get your hands dirty and try Kapsel with SMP Cloud).
1. From Appbuilder> click on “Deployment“> Select “Create Cordova Project“> In the new dialog window check the option “for Android” and leave the remaining field as by default.
2. Click on “Native Plugins“> Kapsel> Check “Logon Manager“. Leave remaining fields as by default and click on “Confirm“.
Note: Path to the Kapsel plugins has to be provided under Cordova Path. I am using only Logon plugin in this example.
3. After successful creation of Cordova Project click on “Deployment“> Kapsel on SMP server> Start. SMP details has to be provided in this window as given below:
4. Import the project to Android Developer Tools (Eclipse IDE) and run the app. By default the project created will be in the path C:\kapsel.
Midhun VP
@midhunvptwit
Hi Midhun,
My SMP is in cloud.
When I try to Deploy to Kapsel on SMP server I gor response error:undefined.
Everything was fine untill this part.
So, i need some help.....
Regards,
Vladimir
Are you using SMP 3 on cloud or SMP on cloud ? The example I given is based on SMP 3 on cloud. Make sure you are able to ping the SMP 3 server IP. Also make sure you created the cordova project without any errors.
Midhun VP
I can't ping smp server.
Find the cloud SMP's public IP as I mentioned here, Developing SMP 3 Mobile App using Appbuilder, Kapsel and SMP 3 Trial - Part 2 and use that in the appbuilder.
Midhun VP
Hi Midhun ,
Have a question regarding importing of the package in the eclipse (android sdk ) , get two work space to import , and also when i import both of the them , the main have some problem with the .java (activity file).then i have to manually set the src packages, to get the cordova code working.
Can you guide over this.
I haven't faced a problem with importing the project to eclipse.
Steps to be followed:
From Eclipse File>New>Project>Android>Android Project from Existing Code>Next, give root directory>browse>finish.
Midhun VP
Ok thanks for that info., what version of cordova are you using ?
It was mentioned in the first part of blog,Cordova version 3.1.0-0.2.0.
Hi Midhun,
After running app in simulator blank screen is coming,
only home screen without any data visible
and in Admin portal two registrations are visible
Please guide
Regards,
Lekhak Patil
Are you getting the registration screen ?
Midhun VP
After running app in simulator blank screen is coming,
only home screen without any data visible.
Increase ADB Connection timeout(ms) to 10000 or more, by default 5000
If you are in Eclipse, you can do this by going through
Window-> Preferences -> Android -> DDMS -> ADB Connection Timeout (ms)
Hi Midhun,
Your blog is awesome.. I did exactly as per your blog and all steps are working as expected for me..
Thank a lot..
Vishnu
Hi Midhun,
I tried Deploy to Kapsel on SMP Server. I am getting "Deploy Successful". But in the terminal I am getting some command not found messages. Also how to check whether the app is deployed in my SMP server management cockpit?
I have attached the terminal screenshot for command not found error.
Could you give the steps you followed? Make sure you installed appbuilder correctly, Apache ANT is installed, Cordova and NPM installed. Are you able to create Cordova project manually and add the kapsel plugins to it.
Midhun VP
Hi Midhun,
It was an issue with NPM installation. I reinstalled it and it is getting deployed successfully.
Thanks,
Dhani.
Hi Midhun,
Thank you for sharing this tutorial. It's awesome..
I am facing a problem to create a cordova project for Android in AppBuilder.
It's said the generation successful. However the project is not under my workplace.
Below, you can see I can create cordova project with command line.
Is there any steps I missed? Thanks!
Make sure you installed NPM, Cordova and Android.
NPM
Cordova
Android
Download Android SDK> Run SDK manager and install all packages.
Finally, create cordova project.
Thanks for quick reply. I did install all of them.
I can create cordova project and add andorid platform with Cordova command in CMD. But cannot do it in AppBuilder..
You mean to say that you are not able to find the project created in the path ? You can find the path from Deployment>Workspace setting.
Are you able to import the project created to Android workspace (Eclipse) and run ?
Regards,
Midhun VP
No I mean, when I created project from Deployment->Create Cordova Project in Appbuilder, nothing was created in my workspace.
My workspace setting.
It's said successfully when create cordova project.
But my workspace is empty.
The issue looks new to me. When happens with a new workspace ? Have you tried without any network connectivity.
Ming Kho , could you have a look at this issue.
Regards,
Midhun VP
it still doesn't work with a new workspace 'C:\Apps\Kapsel'..
I saw when create cordova project in AppBuilder, it actually run a script project.bat
But, it looks like the command in project.bat file is invalid.
Hi, Cai,
Have you received any feedback yet? I'm having the exact same issue.
thanks
not yet..
My issue is solved.
My problem was that the foldername where i installed appbuilder, contained a space. After removal, everything went fine. So please check the same, probably you have the same issue.
rg
Peter
Hello Peter,
What folder did you remove. can you please let me know i am not able to find out android project.
BR,
Saurabh
Maybe i was not clear enough...
In the folderpath where i've installed appbuilder, there were spaces in the foldername of the directory, so after removal of the spaces in the foldername (ie. sap soft\appbuilder -> sapsoft\appbuilder), the issue was solved.
rg
Peter
Thanks Peter your answer is helpful to me. 🙂
Hi Mithun,
After deploying the project in Android simulator only white screen is coming (blank).
i can see in error that :- Iab ui undefined error .could you help me in that ?
BR,
Saurabh
Hi Midhun,
Your tutorial is very nice, i understood all the things upto part 2 but
After importing the project in eclipse, while i executed the project it gives me the following error ,
"Uncaught TypeError: Cannot read property 'IabUi' of undefined at file:///android_asset/www/index.html:48"
can you please help me ??
is anyone else had this kind of error?
anyone know the solution for this then please help me with this, thank you.
One more thing though i am new to SAP i don't know what is use of deploying Kapsel on SMP server,
i mean what is the use of it, for what purpose we are doing that?
I am also stuck with this error. Please let me know what is the solution for this.
When a Kapsel application registers with the SMP server, the SMP server can assist with security. It provides the ability to work with different authentication providers. The SMP server can provide native push capabilities for your application, it can provide updates to the HTML content that make up your application using the appupdate plugin, it can provide the ability to upload a device log to the SMP server with the Logger plugin, statistics for your application such as the number of registrations, and as of SP05, it can enable your application to work with offline OData. For additional details see Getting Started with Kapsel - Part 1
I am assuming the deploy shown above to the SMP server relates to the AppUpdate plugin. The following document provides more details on this.
Getting Started with Kapsel - Part 3 -- AppUpdate
For the error mentioned above, I would double check the version of the inAppBrowser plugin being used in your project. Kapsel requires the version that is included at C:\SAP\MobileSDK3\KapselSDK\plugins\inappbrowser.
The version details can be seen by examining the plugin.xml
C:\SAP\MobileSDK3\KapselSDK\plugins\inappbrowser\plugin.xml
When a Kapsel project is created, it is recommended that the searchpath parameter be used. That way when a plugin is added, it first checks the searchpath and if it finds the plugin there, it is added.
An example would be
cordova -d create C:\Kapsel_Projects\LogonDemo com.mycompany.logon LogonDemo "{\"plugin_search_path\":\"C:/SAP/MobileSDK3/KapselSDK/plugins/\"}"
This will create the following file
C:\Kapsel_Projects\LogonDemo\.cordova\config.json that contains the searchpath for the project
{
"plugin_search_path": "C:/SAP/MobileSDK3/KapselSDK/plugins/"
}
Hope that helps,
Dan van Leeuwen
Hi Midhun,
I've created this demo a while ago, and everything works nice on my android device.
However after some time (some hours, ...), the app doesn't show the data anymore.
If I then redeploy the app on the device, everything runs fine again.
When i check the app during the failures, i see that my user/psw are correctly retrieved from the application context. So I don't think it has anything to do with the kapsel plugin.
When i check the logging on the server, I notice the following:
<html><head><title>Logon Error Message</title><META http-equiv="Content-Type" content="text/html;charset=UTF-8"><style type="text/css">body { font-family:tahoma,helvetica,sans-serif;color:#333333;background-color:#FFFFFF; }td { font-family:tahoma,helvetica,sans-serif;font-size:70%;color:#333333; }h1 { font-family:tahoma,helvetica,sans-serif;font-size:160%;font-weight:bold;margin-top:15px;margin-bottom:3px;color:#003366; }h2 { font-family:verdana,helvetica,sans-serif;font-size:120%;font-style:italic;font-weight:bold;margin-top:6px;margin-bottom:6px;color:#999900; }p { font-family:tahoma,helvetica,sans-serif;color:#333333;margin-top:4px;margin-bottom:4px; }ul { font-family:tahoma,helvetica,sans-serif;color:#333333;list-style-type:square;margin-top:8px;margin-bottom:8px; }li { font-family:tahoma,helvetica,sans-serif;color:#33333;margin-top:4px; }.emphasize { color:#333333;background-color:#C8E3FF;padding:5px;}.note { color:#CC6600; }a { font-family:tahoma,helvetica,sans-serif;text-decoration:underline;color:#336699; }a:visited { color:#001166; }a:hover { text-decoration:none; }</style></head><body><table cellpadding="0" cellspacing="0" border="0" width="100%"><tr><td><h1>Aanmelding mislukt</h1><br><h2>Wat is er gebeurd?</h2><p>Oproepen van URL https://smp-s0003439903trial.hanatrial.ondemand.com/com.list.test/BusinessPartnerCollection is afgebroken op grond van foutieve aanmeldgegevens</p></td></tr><tr><td> </td></tr><tr><td class="emphasize"><strong>SAPNote</strong><br><ul><li> Aanmelding is in systeem ES1 uitgevoerd </li><li> Aanmelding is uitgevoerd voor mandant 520 en taal NL </li></ul></td></tr><tr><td> </td></tr><tr><td><p> </p><h2>Wat **** u doen?</h2><ul><li> Controleer de geldigheid van uw SSO-ticket voor dit systeem </li> <li> Wend u tot de systeembeheerder als u nog geen gebruiker-ID hebt </li></ul></br><p class="note">Foutcode: ICF-LE-http-c:520-l:N-T:21-C:5-U:5-P:5-L:7-X:0050568474FA1EE49DC6A0218138E840_0050568474FA1EE49DC6A028F788E840_1-x:5475CB51A1D0567FE1000000AC140C37</p></br><p> HTTP 401 - Unauthorized</br><p> Uw SAP Internet Communication Framework Team</p></td></tr></table></body></html>
I get an unauthorized failure between SMP & gateway, also it mentions the validity of an SSO ticket(even though it is http). What could be the problem? And what could be the reason that after redeployment everything goes fine again? Can we see in some log the call between smp and gateway?
Maybe the trace file can also help:
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Retrieve appHandler=[proxy], application=[com.list.test] and backendURL=[/BusinessPartnerCollection?&$top=200].
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "host"=[smp-s0003439903trial.hanatrial.ondemand.com:443]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "connection"=[keep-alive]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "x-csrf-token"=[Fetch]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request header Authorization passed
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "x-sup-appcid"=[9bcf7d41-8a63-4bc7-a105-b808ca212dd9]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "maxdataserviceversion"=[3.0]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "accept"=[application/atomsvc+xml;q=0.8, application/json;odata=fullmetadata;q=0.7, application/json;q=0.5, */*;q=0.1]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "x-sup-sc"=[]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "user-agent"=[Mozilla/5.0 (Linux; U; Android 4.0.3; nl-be; HTC One V Build/IML74K) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "accept-encoding"=[gzip,deflate]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "accept-language"=[nl-BE, en-US]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "accept-charset"=[utf-8, iso-8859-1, utf-16, *;q=0.7]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "cookie"=[MYSAPSSO2=U01QX0VOQ3tBalF4TURNQkFCaFRBREFBTUFBd0FETUFOQUF6QURrQU9RQXdBRE1BSUFBQ0FBWTFBRElBTUFBREFCQkZBRk1BTVFBZ0FDQUFJQUFnQUNBQUJBQVlNZ0F3QURFQU5BQXhBREVBTWdBMkFERUFOZ0F4QURrQUJRQUVBQUFBQ0FZQUFsZ0FDUUFDVGdEJTJmQVZVd2dnRlJCZ2txaGtpRzl3MEJCd0tnZ2dGQ01JSUJQZ0lCQVRFTE1Ba0dCU3NPQXdJYUJRQXdDd1lKS29aSWh2Y05BUWNCTVlJQkhUQ0NBUmtDQVFFd2J6QmtNUXN3Q1FZRFZRUUdFd0pFUlRFY01Cb0dBMVVFQ2hNVFUwRlFJRlJ5ZFhOMElFTnZiVzExYm1sMGVURVRNQkVHQTFVRUN4TUtVMEZRSUZkbFlpQkJVekVVTUJJR0ExVUVDeE1MU1RBeE1qQXdNRE0wTVRFeEREQUtCZ05WQkFNVEEwVTJOQUlISUJFQ0ZBZ2pVVEFKQmdVckRnTUNHZ1VBb0Ywd0dBWUpLb1pJaHZjTkFRa0RNUXNHQ1NxR1NJYjNEUUVIQVRBY0Jna3Foa2lHOXcwQkNRVXhEeGNOTVRReE1USTJNVFl4T1RJeldqQWpCZ2txaGtpRzl3MEJDUVF4RmdRVUg3cklCbCUyZmVKRkRUa1RWWGFxNGVMSzJKZzB3d0NRWUhLb1pJempnRUF3UXVNQ3dDRkJ5NGhXeDJ1TUJkQSUyZmVvd1NidkpDUU9oaDV0QWhRczZOJTIxcGVneDlGJTJmVDcwVUZ5aHElMjFOZXQ0c0l3JTNkJTNkOy99; SAP_SESSIONID_ES1_520=U01QX0VOQ3tLekIxaVNIQXNDWE01VTktOUEyTUJmdnZrMTExaHhIa25FWUFVRmFFZFBvJTNkOy99; sap-XSRF_ES1_520=U01QX0VOQ3t0QTl0X2JoV2lyaktydnNZaDlGRXVRJTNkJTNkMjAxNDExMjYxNjE5MjNiT2FPTEFkSUV0WW9PTXQ0NnJvQ3Utb0RvWGU1UzJNUGk5OVQ2WFVCVzJzJTNkOy99; X-SUP-APPCID=9bcf7d41-8a63-4bc7-a105-b808ca212dd9; BIGipServer~jpaas_folder~smp.hanatrial.ondemand.com=2047636746.26911.0000]
2014-11-27 13:04:58.693#DEBUG#com.sybase.sup.server.http.DispatcherServlet#null#Request Header "x-forwarded-for"=[109.130.25.255]
2014-11-27 13:04:58.694#DEBUG#com.sybase.sup.server.http.ApplicationCIDProcessor#null#Process application connection id.
2014-11-27 13:04:58.694#DEBUG#com.sybase.sup.server.http.ApplicationCIDProcessor#null#Request Header "X-SUP-APPCID"=[9bcf7d41-8a63-4bc7-a105-b808ca212dd9]
2014-11-27 13:04:58.694#DEBUG#com.sybase.sup.server.http.ApplicationCIDProcessor#null#Add Cookie: javax.servlet.http.Cookie@36fc25b0
2014-11-27 13:04:58.706#DEBUG#com.sybase.sup.server.http.ODPSecurityFactory#null#Retrieved securityConfiguration=[http].
2014-11-27 13:04:58.706#DEBUG#com.sybase.sup.server.http.AuthenticationProcessor#null#Process authentication information.
2014-11-27 13:04:58.718#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#Dispatch request to proxy handler.
2014-11-27 13:04:58.718#DEBUG#com.sybase.sup.odp.handler.ODPHTTPDelegatehandler#null#ODPHTTPDelegatehandler :Received a request to fire to Gateway
2014-11-27 13:04:58.718#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#----------In DirectProxy handle()---------com.list.test
2014-11-27 13:04:58.719#INFO#com.sybase.sup.odp.handler.DirectProxy#null#URL rewrite enabled?: true
2014-11-27 13:04:58.719#INFO#com.sybase.sup.odp.handler.DirectProxy#null#after truncating endpoint ishttp://sapes1.sapdevcenter.com:8080/sap/opu/odata/iwbep/gwdemo
2014-11-27 13:04:58.719#INFO#com.sybase.sup.odp.handler.DirectProxy#null#Final endpoint URL ishttp://sapes1.sapdevcenter.com:8080/sap/opu/odata/iwbep/gwdemo/BusinessPartnerCollection?&$top=200
2014-11-27 13:04:58.719#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#----Application Id sent from client is--------com.list.test
2014-11-27 13:04:58.719#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#--------------About to fire the request to the backend-----------
2014-11-27 13:04:58.72#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#----------In DirectProxy fireRequest()----------
2014-11-27 13:04:58.72#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#header: key=x-csrf-token value=Fetch
2014-11-27 13:04:58.72#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#header: key=authorization value= *****
2014-11-27 13:04:58.72#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#header: key=maxdataserviceversion value=3.0
2014-11-27 13:04:58.72#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#header: key=accept value=application/atomsvc+xml;q=0.8, application/json;odata=fullmetadata;q=0.7, application/json;q=0.5, */*;q=0.1
2014-11-27 13:04:58.72#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#header: key=x-sup-sc value=
2014-11-27 13:04:58.72#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#header: key=accept-encoding value=gzip,deflate
2014-11-27 13:04:58.72#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#header: key=accept-language value=nl-BE, en-US
2014-11-27 13:04:58.72#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#header: key=accept-charset value=utf-8, iso-8859-1, utf-16, *;q=0.7
2014-11-27 13:04:58.72#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#header: key=x-forwarded-for value=109.130.25.255
2014-11-27 13:04:59.796#DEBUG#com.sybase.sup.common.connectivity.BackendConnectivity#null#Response code of the request ::: 401
2014-11-27 13:04:59.796#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#--------------Finished firing the request to backend-----------
2014-11-27 13:04:59.799#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#ODP:Recieved the response from the backend server
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#Response code is HTTP/1.0 401 Unauthorized
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#Response header key:Proxy-Connection Response header value:close
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#Response header key:server Response header value:SAP NetWeaver Application Server / ABAP 702
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#Response header key:www-authenticate Response header value:Basic realm="SAP NetWeaver Application Server [ES1/520]"
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#Response header key:sap-system Response header value:ES1
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#Response header key:cteonnt-length Response header value:2153
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#Response header key:content-type Response header value:text/html; charset=utf-8
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#Response header key:set-cookie Response header value:sap-ssolist=0; expires=Tue, 01-Jan-1980 00:00:01 GMT; path=/
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#Response header key:set-cookie Response header value:MYSAPSSO2=0; expires=Tue, 01-Jan-1980 00:00:01 GMT; path=/; domain=.sapdevcenter.com
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#------------content type:|encoding|length--------text/html; charset=utf-8--------0----
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#-------Response code from GW is not 2XX--------
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#ODP:Read response body from Gateway
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#prepareResponse finally block
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null# text/html/xml/json
2014-11-27 13:04:59.8#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#Inside getURLRewriteTable()
2014-11-27 13:04:59.803#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#response before re-write:<html><head><title>Logon Error Message</title><META http-equiv="Content-Type" content="text/html;charset=UTF-8"><style type="text/css">body { font-family:tahoma,helvetica,sans-serif;color:#333333;background-color:#FFFFFF; }td { font-family:tahoma,helvetica,sans-serif;font-size:70%;color:#333333; }h1 { font-family:tahoma,helvetica,sans-serif;font-size:160%;font-weight:bold;margin-top:15px;margin-bottom:3px;color:#003366; }h2 { font-family:verdana,helvetica,sans-serif;font-size:120%;font-style:italic;font-weight:bold;margin-top:6px;margin-bottom:6px;color:#999900; }p { font-family:tahoma,helvetica,sans-serif;color:#333333;margin-top:4px;margin-bottom:4px; }ul { font-family:tahoma,helvetica,sans-serif;color:#333333;list-style-type:square;margin-top:8px;margin-bottom:8px; }li { font-family:tahoma,helvetica,sans-serif;color:#33333;margin-top:4px; }.emphasize { color:#333333;background-color:#C8E3FF;padding:5px;}.note { color:#CC6600; }a { font-family:tahoma,helvetica,sans-serif;text-decoration:underline;color:#336699; }a:visited { color:#001166; }a:hover { text-decoration:none; }</style></head><body><table cellpadding="0" cellspacing="0" border="0" width="100%"><tr><td><h1>Aanmelding mislukt</h1><br><h2>Wat is er gebeurd?</h2><p>Oproepen van URL http://sapes1.sapdevcenter.com:8080/sap/opu/odata/iwbep/gwdemo/BusinessPartnerCollection is afgebroken op grond van foutieve aanmeldgegevens</p></td></tr><tr><td> </td></tr><tr><td class="emphasize"><strong>SAPNote</strong><br><ul><li> Aanmelding is in systeem ES1 uitgevoerd </li><li> Aanmelding is uitgevoerd voor mandant 520 en taal NL </li></ul></td></tr><tr><td> </td></tr><tr><td><p> </p><h2>Wat **** u doen?</h2><ul><li> Controleer de geldigheid van uw SSO-ticket voor dit systeem </li> <li> Wend u tot de systeembeheerder als u nog geen gebruiker-ID hebt </li></ul></br><p class="note">Foutcode: ICF-LE-http-c:520-l:N-T:21-C:5-U:5-P:5-L:7-X:0050568474FA1EE49DC6A0218138E840_0050568474FA1EE49DC6A028F788E840_1-x:5475CB51A1D0567FE1000000AC140C37</p></br><p> HTTP 401 - Unauthorized</br><p> Uw SAP Internet Communication Framework Team</p></td></tr></table></body></html>
2014-11-27 13:04:59.803#DEBUG#com.sybase.sup.common.logging.SMPLogger#null#response after re-write<html><head><title>Logon Error Message</title><META http-equiv="Content-Type" content="text/html;charset=UTF-8"><style type="text/css">body { font-family:tahoma,helvetica,sans-serif;color:#333333;background-color:#FFFFFF; }td { font-family:tahoma,helvetica,sans-serif;font-size:70%;color:#333333; }h1 { font-family:tahoma,helvetica,sans-serif;font-size:160%;font-weight:bold;margin-top:15px;margin-bottom:3px;color:#003366; }h2 { font-family:verdana,helvetica,sans-serif;font-size:120%;font-style:italic;font-weight:bold;margin-top:6px;margin-bottom:6px;color:#999900; }p { font-family:tahoma,helvetica,sans-serif;color:#333333;margin-top:4px;margin-bottom:4px; }ul { font-family:tahoma,helvetica,sans-serif;color:#333333;list-style-type:square;margin-top:8px;margin-bottom:8px; }li { font-family:tahoma,helvetica,sans-serif;color:#33333;margin-top:4px; }.emphasize { color:#333333;background-color:#C8E3FF;padding:5px;}.note { color:#CC6600; }a { font-family:tahoma,helvetica,sans-serif;text-decoration:underline;color:#336699; }a:visited { color:#001166; }a:hover { text-decoration:none; }</style></head><body><table cellpadding="0" cellspacing="0" border="0" width="100%"><tr><td><h1>Aanmelding mislukt</h1><br><h2>Wat is er gebeurd?</h2><p>Oproepen van URL https://smp-s0003439903trial.hanatrial.ondemand.com/com.list.test/BusinessPartnerCollection is afgebroken op grond van foutieve aanmeldgegevens</p></td></tr><tr><td> </td></tr><tr><td class="emphasize"><strong>SAPNote</strong><br><ul><li> Aanmelding is in systeem ES1 uitgevoerd </li><li> Aanmelding is uitgevoerd voor mandant 520 en taal NL </li></ul></td></tr><tr><td> </td></tr><tr><td><p> </p><h2>Wat **** u doen?</h2><ul><li> Controleer de geldigheid van uw SSO-ticket voor dit systeem </li> <li> Wend u tot de systeembeheerder als u nog geen gebruiker-ID hebt </li></ul></br><p class="note">Foutcode: ICF-LE-http-c:520-l:N-T:21-C:5-U:5-P:5-L:7-X:0050568474FA1EE49DC6A0218138E840_0050568474FA1EE49DC6A028F788E840_1-x:5475CB51A1D0567FE1000000AC140C37</p></br><p> HTTP 401 - Unauthorized</br><p> Uw SAP Internet Communication Framework Team</p></td></tr></table></body></html>
2014-11-27 13:04:59.803#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null#URL rewrite : response is sent
2014-11-27 13:04:59.803#DEBUG#com.sybase.sup.odp.handler.DirectProxy#null# prepareResponse() method ends
2014-11-27 13:04:59.803#INFO#com.sybase.sup.odp.handler.ODPHTTPDelegatehandler#null#ODPHTTPDelegatehandler :Sending response to the dispatcher
Thanks for feedback,
regards
Peter
Hi Peter,
The application developed is a demo on how to use Appbuilder, Kapsel plugins and SMP. I don't know why it is failing when using the app after keeping the app idle for few hours (I didn't test this either), you may have to look at the android app lifecycle and manage it accordingly or use updated SDKs.
Update: SAP's recommended tool to develop SAPUI5 apps is using SAP Web IDE. So I would suggest you to start with Web IDE instead of Appbuilder. More info: SAP Web IDE - Enablement
Hi Midhun,
do you have any idea how to transport smp3.0 from dev to production. do we use sap solution manager for that ?
we are working on RFP for a client but not sure about smp3.0 transport.
BR,
Saurabh
saurabh shrivastava
Have a look at
Hi Jitendra,
Thanks a lot it solved my query .
Br,
Saurabh