A simple Android Native Application Development

Dear All,
OBJECTIVE:
This document illustrates the procedure to create a simple android based sup native application.
I am sure you must have checked the same at infocenter. My objective of writing this document is to bring all the points altogether at same place.
REQUIREMENT:

Tools used in developing the application are:
SUP version: 2.2 SP04,
Android Development Tool Kit 22.0.1,

Android SDK

PROCEDURE:
1. Download SUP101 MBO project (with complete files) from http://scn.sap.com/docs/DOC-8803
1.PNG
2. Import the same project in mobile sdk and deploy to SUP server. (make sure you are connected to My sample database and sup server)
3. Generate the Java Object API code.
  •      Under third party jar file, select .jar file from SDK path
               D:\xxxxx\adt-bundle-windows-x86-20130522\sdk\platforms\android-17\android.jar
1.PNG
4. After step 3, there are two apporaches to develop android application. Either you can add ADT plugin in sybase mobile sdk itself OR you can use Eclipse Junos to build the application seperately. Here i am preferring first apporach because running two eclipses on same machine eat more RAM.
Installing ADT in Sybase mobile SDK
  • Open sybase mobile SDK. Go to Help Menu>Install New Software
1.PNG
  • If you have ADT plugin setup on your machine, then you can do following:
    • Click on Add
    • Name: ADT
    • Location: click on Archive go to the ADT Zip file location.
                    1.PNG
    •     Select both Developer tools and NDK plugins
              1.PNG
  • If you don’t have the setup file, it can be downloaded through internet.
5. Go to Window>preferences
    •    browse to the SDK path in SDK location.
1.PNG
6.  Creating the Android Project:

1.PNG

    

  • Select File>New>Project
  • then select Android>Android Application Project and then click Next

               1.PNG

  • give the package name as metioned below. then click next.

         

          1.PNG

  • At the last screen, Blank Activity mention below details and click on Finish.

    

1.PNG

7. Next task is to add compiler and library resources

  • go to SUP_HOME\UnwiredPlatform\MobileSDK22\ObjectAPI\Android
  • Copy armeabi folder, AfariaSLL.jar, ClientLib.jar, sup-client.jar, UltraLiteJN12.jar

    

     1.PNG

  • Paste above all files and folder to the SUP101Android>libs in sybase workspace

1.PNG            

  • Right click SUP101Android project in workspace, select properties>Jave Build Path>Libraries>Add JARs
  • In the JAR Selection window, expand the SUP101Android\libs folder and select AfariaSSL.jar, ClientLib.jar, sup-client.jar, and UltraLiteJNI12.jar.

        1.PNG

8.  Copying Generated code Object API files:

  • From the workspace navigator, under SUP101 project…. copy com folder in \Generated Code\Android\src\

1.PNG

  • Paste this folder in the src directory of SUP101Android Project.

    

     1.PNG

9. UI Creation:

  • You must have downloaded SUP101 Android project from above mentioned link. Go to that path copy these jave files:

         CustomerListAdapter.java, DetailActivity.java, and SUP101SampleActivity.java

  • Expand SUP101Android, paste the copied java files, copying over any existing files to src\com\mycorp\sup101\android\app in WorkSpace navigator

          1.PNG

  • Open SUP101SampleActivity.java file and modify the host ip address (sup server machine address) and verify sup username and password.
  • Again go to the Android project path (downloaded one), copy layout XML files: customer.xml, detail.xml, and main.xml
  • Expand SUP101Android project in workspace navigator, go to res/layout, paste the copied XML files, copying over any existing files.

          1.PNG

10. Launch the emulator by right clicking SUP101Android>Run As>Android Application

The application activation (on boarding) image indicates that the application is registering data from Unwired Server

1.PNG

  • When the synchronization is done, this application shows the SUP101Android application with a list of customer data in a ListView control. You can scroll through the customer list to see more data and to make changes. The data loads from the database on demand.

1.PNG

1.PNG

1.PNG

References:  http://scn.sap.com/docs/DOC-8803

                     http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01734.0222/doc/html/lly1325724225650.html

I hope it will help you to understand basic flow of SUP native app on Android.

Your comments and suggestions are most welcome.

Regards,

Jitendra

To report this post you need to login first.

35 Comments

You must be Logged on to comment or reply to a post.

  1. Dmitriy Prokofiev

    hi All

    • When the synchronization is done, this application shows the SUP101Android application with a list of customer data in a ListView control. You can scroll through the customer list to see more data and to make changes. The data loads from the database on demand.

    my progress bar never dissapear, i only see white screen after ~ 20 mintues of waiting…

    where is the problem ?

    (0) 
    1. jitendra kansal Post author

      Hi Dmitriy,

      my progress bar never dissapear,

      are you talking about on boarding Please wait while downloading initial data

      is data not getting downloaded your device? i couldnt understand your query completely.

      Please provide more inputs.

      Regards,

      Jitendra

      (0) 
      1. Dmitriy Prokofiev

        11-20 18:10:54.565: E/SMP101(627): Cannot register Error: 558 Message: ‘Could not connect to server. Verify Relay Server URL Template’

        11-20 18:10:54.565: I/SMP101(627): Application REGISTERED

        11-20 18:10:54.576: D/UpgradeUtil(627): upgrade takes : 0ms

        11-20 18:10:54.748: D/dalvikvm(627): Trying to load lib /data/data/com.mycorp.smp101.android.app/lib/libultralitej12.so 0x40ffa8a8

        11-20 18:10:54.806: I/Choreographer(627): Skipped 41 frames!  The application may be doing too much work on its main thread.

        11-20 18:10:54.945: D/dalvikvm(627): Added shared lib /data/data/com.mycorp.smp101.android.app/lib/libultralitej12.so 0x40ffa8a8

        11-20 18:10:54.945: D/dalvikvm(627): No JNI_OnLoad found in /data/data/com.mycorp.smp101.android.app/lib/libultralitej12.so 0x40ffa8a8, skipping init

        11-20 18:10:55.215: I/SMP101(627): Starting Initial Sync

        11-20 18:10:55.466: I/MocaLog(627): 20T181055, T2, MessagingClientLib: getConfigProperty: 7

        11-20 18:10:55.585: I/MocaLog(627): 20T181055, T2, MessagingClientLib: getDeviceID

        11-20 18:10:55.585: I/SMP101(627): OnSynchronize() called with STATUS 1

        11-20 18:10:55.685: W/System.err(627): com.sybase.mobile.ApplicationRuntimeException: Application settings are not available

        11-20 18:10:55.685: W/System.err(627):           at com.sybase.mobile.ApplicationSettings.checkApplicationSettingsAvailable(ApplicationSettings.java:94)

        11-20 18:10:55.715: W/System.err(627):           at com.sybase.sup.client.persistence.RbsDatabaseDelegate.internalSynchronize(RbsDatabaseDelegate.java:477)

        11-20 18:10:55.715: W/System.err(627):           at com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronizeWithCallback(RbsDatabaseDelegate.java:427)

        11-20 18:10:55.745: W/System.err(627):           at com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronize(RbsDatabaseDelegate.java:1439)

        11-20 18:10:55.745: W/System.err(627):           at com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronize(RbsDatabaseDelegate.java:1430)

        11-20 18:10:55.766: W/System.err(627):           at com.mycorp.smp101.android.mbo.SMP101DB.synchronize(SMP101DB.java:199)

        11-20 18:10:55.785: W/System.err(627):           at com.mycorp.smp101.android.app.SMP101SampleActivity$2.run(SMP101SampleActivity.java:151)

        11-20 18:10:56.055: W/System.err(627):           at java.lang.Thread.run(Thread.java:856)

        (0) 
        1. jitendra kansal Post author

          your app is not even connecting to smp server.

          did you pass sup server ip address in SMP101SampleActivity.java file as mentioned in step#9?

          please double check all the steps mentioned above with what you have done.

          (0) 
  2. Dmitriy Prokofiev

    are there additional steps – to configure RelayServe or may be register application via Sap control cebter ?

    i tried

    private static String HOST = “127.0.0.1”;

    and this one –

    private static String HOST = “localhost”;

    (0) 
    1. jitendra kansal Post author

      are there additional steps – to configure RelayServe or may be register application via Sap control cebter ?

      is this requirement with above android app development? are you using relay server in your android app development?

      Regards,

      Jitendra

      (0) 
          1. Dmitriy Prokofiev

            my platform is 2.3, sample project files 2.3 too, instruction for 2.3 android sample project and your ( for 2.2) are the same, the same steps. but my application couldnot register to server, and couldnot synchronizy with DB. could you see my error logs above?

            (0) 
            1. jitendra kansal Post author

              . but my application couldnot register to server

              but in the log it says..Application REGISTERED

              what is user status in SCC?

              can you run app once again ….. check server.log file

              (0) 
  3. Dmitriy Prokofiev

    there is an instruction for registration an application if we use iOS tutorial –

    SAP Mobile Platform 2.3 > Tutorial: iOS Object API Application Development 2.3 > Developing an iOS Application

    Registering the Application Connection in SAP Control Center

    but in case of android – it is not necessary to do registraion, isnt it ?

    here is a sample code from  activity :

    public void onRegistrationStatusChanged(int registrationStatus, int errorCode, String errorMessage)

                  {

                switch (registrationStatus)

                {

                    case RegistrationStatus.REGISTERED:

                              System.out.println(“Device is REGISTERED”);

                        break;

                    case RegistrationStatus.REGISTERING:

                              System.out.println(“Device is REGISTERING”);

                        break;

                    case RegistrationStatus.REGISTRATION_ERROR:

                              System.out.println(“Registration Error: ” + errorMessage);

                        break;

                    case RegistrationStatus.UNREGISTERED:

                              System.out.println(“Device is UNREGISTERED”);

                        break;

                    case RegistrationStatus.UNREGISTERING:

                              System.out.println(“Device is UNREGISTERING”);

                        break;

                }   

                  }

    wneh debugging, a have only

    case RegistrationStatus.REGISTERING:

                    System.out.println(“Device is REGISTERING”);

                        break;

                    case RegistrationStatus.REGISTRATION_ERROR:

                    System.out.println(“Registration Error: ” + errorMessage);

                        break;

    cases , and then – after an error – this line of code

    Log.i(“SMP101″,”Application REGISTERED”);, so as you right noriced, it seems that application really registered.

    (0) 
  4. Dmitriy Prokofiev

    i didnt set any options to use an relay server but here is a log file :

    11-20 22:40:13.237: W/ActivityThread(671): Application com.mycorp.smp101.android.app can be debugged on port 8100…

    11-20 22:40:14.097: I/MocaLog(671): 20T224014, T1, ThreadID = Thread[main,5,main] maps to short thread id 1

    11-20 22:40:14.107: I/MocaLog(671): 20T224014, T1, Starting Log. Platform Android. Current time: 20131120T224014

    11-20 22:40:14.128: I/MocaLog(671): 20T224014, T1, MocaLog Logging Level: 5

    11-20 22:40:14.147: I/MocaLog(671): 20T224014, T1, AppId: null

    11-20 22:40:14.167: I/MocaLog(671): 20T224014, T1, iMo Version Number: 2.3.0.6690

    11-20 22:40:14.178: I/MocaLog(671): 20T224014, T1, Creating DATA_CONNECTION_STATE listener

    11-20 22:40:14.297: I/MocaLog(671): 20T224014, T1, MessagingClientLib: initInstance. App ID: SMP101, Log Level 4

    11-20 22:40:14.327: I/MocaLog(671): 20T224014, T1, Starting CmoBinary::cleanOldFiles

    11-20 22:40:14.337: I/MocaLog(671): 20T224014, T1, Searching file pattern: /data/data/com.mycorp.smp101.android.app/app_mobinary/mobinary_cookie_*

    11-20 22:40:14.367: I/MocaLog(671): 20T224014, T1, Finished CmoBinary::cleanOldFiles

    11-20 22:40:14.497: I/MocaLog(671): 20T224014, T1, MessagingClientLib: getConfigProperty: 7

    11-20 22:40:14.607: I/MocaLog(671): 20T224014, T1, MessagingClientLib: addPushNotificationListener

    11-20 22:40:14.647: I/MocaLog(671): 20T224014, T1, GCM Disabled, running without GCM

    11-20 22:40:14.678: I/MocaLog(671): 20T224014, T1, MessagingClientLib: getDeviceID

    11-20 22:40:14.697: I/MocaLog(671): 20T224014, T1, getEmulatorDeviceId: Simulator37a84b0b-a72f-4db2-8155-c9db06cac708

    11-20 22:40:14.767: D/dalvikvm(671): GC_CONCURRENT freed 227K, 5% free 6239K/6535K, paused 54ms+16ms, total 269ms

    11-20 22:40:14.787: I/MocaLog(671): 20T224014, T1, Cookies – setClientCookies count: 0

    11-20 22:40:14.897: I/Choreographer(671): Skipped 762 frames!  The application may be doing too much work on its main thread.

    11-20 22:40:15.327: I/Choreographer(671): Skipped 270 frames!  The application may be doing too much work on its main thread.

    11-20 22:40:15.397: D/gralloc_goldfish(671): Emulator without GPU emulation detected.

    11-20 22:40:15.757: I/MocaLog(671): 20T224015, T2, ThreadID = Thread[Thread-85,5,main] maps to short thread id 2

    11-20 22:40:15.917: I/MocaLog(671): 20T224015, T2, MessagingClientLib: getDeviceID

    11-20 22:40:16.017: I/System.out(671): CONSOLE TRACE: setListener

    11-20 22:40:16.057: I/System.out(671): CONSOLE TRACE: addConnection for Connection key: smp101:1.0

    11-20 22:40:16.057: I/System.out(671): CONSOLE TRACE: leave setListener

    11-20 22:40:16.137: I/Choreographer(671): Skipped 165 frames!  The application may be doing too much work on its main thread.

    11-20 22:40:16.202: I/SMP101(671): Starting Application Registration

    11-20 22:40:16.718: I/MocaLog(671): 20T224016, T2, MessagingClientLib: setConfigProperty

    11-20 22:40:16.737: I/MocaLog(671): 20T224016, T2, MessagingClientLib: propertyDisplayOnly

    11-20 22:40:16.837: I/MocaLog(671): 20T224016, T2, MessagingClientLib: setConfigProperty (1305):

    11-20 22:40:16.867: I/MocaLog(671): 20T224016, T2, MessagingClientLib: setConfigProperty

    11-20 22:40:17.037: I/MocaLog(671): 20T224017, T2, MessagingClientLib: propertyDisplayOnly

    11-20 22:40:17.087: I/MocaLog(671): 20T224017, T2, MessagingClientLib: setConfigProperty (20): false

    11-20 22:40:17.137: I/MocaLog(671): 20T224017, T2, MessagingClientLib: setConnectionProperties: localhost, 5001, 0, supAdmin, null, false,

    11-20 22:40:17.197: I/MocaLog(671): 20T224017, T2, Property 10002 is changed, saved: 123, new: null

    11-20 22:40:17.267: I/MocaLog(671): 20T224017, T2, Property 10002 is changed, saved: 123, new:

    11-20 22:40:17.697: I/MocaLog(671): 20T224017, T2, MessagingClientLib: setConnectionProperties – server configuration changes detected!

    11-20 22:40:17.987: I/System.out(671): Device is REGISTERING

    11-20 22:40:18.038: I/MocaLog(671): 20T224018, T3, ThreadID = Thread[register,5,main] maps to short thread id 3

    11-20 22:40:18.057: I/MocaLog(671): 20T224018, T3, MessagingClientLib: getConfigProperty: 1

    11-20 22:40:18.077: I/MocaLog(671): 20T224018, T3, MessagingClientLib: getConfigProperty: 2

    11-20 22:40:18.096: I/MocaLog(671): 20T224018, T3, MessagingClientLib: getConfigProperty: 3

    11-20 22:40:18.117: I/MocaLog(671): 20T224018, T3, MessagingClientLib: getConfigProperty: 10001

    11-20 22:40:18.187: I/MocaLog(671): 20T224018, T3, Starting URL Template discovery

    11-20 22:40:18.207: I/MocaLog(671): 20T224018, T3, Testing Relay Server URL Template:/

    11-20 22:40:18.265: I/MocaLog(671): 20T224018, T3, Called startTmMessage with URL Template:/

    11-20 22:40:18.277: I/MocaLog(671): 20T224018, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:18.497: I/MocaLog(671): 20T224018, T3, Cookies – setRequest:

    11-20 22:40:18.647: I/MocaLog(671): 20T224018, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:18.667: I/MocaLog(671): 20T224018, T3, Testing Relay Server URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:18.707: I/MocaLog(671): 20T224018, T3, Called startTmMessage with URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:18.777: I/MocaLog(671): 20T224018, T3, Connect to: http://localhost:5001/ias_relay_server/client/rs_client.dll/0/tm

    11-20 22:40:18.837: I/MocaLog(671): 20T224018, T3, Cookies – setRequest:

    11-20 22:40:18.967: I/MocaLog(671): 20T224018, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:19.037: I/MocaLog(671): 20T224019, T3, Testing Relay Server URL Template:/cli/iarelayserver/0/

    11-20 22:40:19.087: I/MocaLog(671): 20T224019, T3, Called startTmMessage with URL Template:/cli/iarelayserver/0/

    11-20 22:40:19.117: I/MocaLog(671): 20T224019, T3, Connect to: http://localhost:5001/cli/iarelayserver/0/tm

    11-20 22:40:19.187: I/MocaLog(671): 20T224019, T3, Cookies – setRequest:

    11-20 22:40:19.297: I/MocaLog(671): 20T224019, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:19.416: D/dalvikvm(671): GC_CONCURRENT freed 328K, 6% free 6407K/6791K, paused 50ms+40ms, total 658ms

    11-20 22:40:19.437: I/MocaLog(671): 20T224019, T3, Testing Relay Server URL Template:/

    11-20 22:40:19.597: I/MocaLog(671): 20T224019, T3, Called startTmMessage with URL Template:/

    11-20 22:40:19.667: I/MocaLog(671): 20T224019, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:19.687: I/MocaLog(671): 20T224019, T3, Cookies – setRequest:

    11-20 22:40:19.727: I/MocaLog(671): 20T224019, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:19.767: I/MocaLog(671): 20T224019, T3, Did NOT find good Relay Server URL Template

    11-20 22:40:19.878: I/MocaLog(671): 20T224019, T3, Error:isServerCapableOf:

    11-20 22:40:19.878: I/MocaLog(671): com.sybase.messaging.traveler.TmException: Could not connect to server. Verify Relay Server URL Template

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.messaging.traveler.TmSession.getUrlTemplate(TmSession.java:439)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.messaging.traveler.TmSession.startTmMessage(TmSession.java:574)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.messaging.traveler.TmSession.sendTmMessage(TmSession.java:515)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.messaging.traveler.TmSession.sendSimpleMessage(TmSession.java:465)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.mo.ServerVersionInfo.refreshVersionInfo(ServerVersionInfo.java:127)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.mo.ServerVersionInfo.isServerCapableOf(ServerVersionInfo.java:280)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.mo.MoObject.isServerCapableOf(MoObject.java:1269)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.mo.MoObject.execute(MoObject.java:459)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.messaging.MclServerRmiCalls.addDeviceRegistration(MclServerRmiCalls.java:103)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.messaging.MclServerRmiCalls.addDeviceRegistration(MclServerRmiCalls.java:234)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.mobile.Application.register(Application.java:430)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.mobile.Application.access$000(Application.java:61)

    11-20 22:40:19.878: I/MocaLog(671):           at com.sybase.mobile.Application$1.run(Application.java:385)

    11-20 22:40:19.898: I/MocaLog(671): 20T224019, T3, execute:  objectName=’monet:DeviceManagement.dll:DeviceManagement’ methodName=’AddDeviceRegistration’ param count(false)=9

    11-20 22:40:19.967: I/MocaLog(671): 20T224019, T3, execute:  refreshing stale ServerVersionInfo

    11-20 22:40:19.997: I/MocaLog(671): 20T224019, T3, Starting URL Template discovery

    11-20 22:40:20.030: I/Choreographer(671): Skipped 81 frames!  The application may be doing too much work on its main thread.

    11-20 22:40:20.077: I/MocaLog(671): 20T224020, T3, Testing Relay Server URL Template:/

    11-20 22:40:20.107: I/MocaLog(671): 20T224020, T3, Called startTmMessage with URL Template:/

    11-20 22:40:20.207: I/MocaLog(671): 20T224020, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:20.239: I/MocaLog(671): 20T224020, T3, Cookies – setRequest:

    11-20 22:40:20.329: I/MocaLog(671): 20T224020, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:20.367: I/MocaLog(671): 20T224020, T3, Testing Relay Server URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:20.546: I/MocaLog(671): 20T224020, T3, Called startTmMessage with URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:20.607: I/MocaLog(671): 20T224020, T3, Connect to: http://localhost:5001/ias_relay_server/client/rs_client.dll/0/tm

    11-20 22:40:20.626: I/MocaLog(671): 20T224020, T3, Cookies – setRequest:

    11-20 22:40:20.697: I/MocaLog(671): 20T224020, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:20.717: I/MocaLog(671): 20T224020, T3, Testing Relay Server URL Template:/cli/iarelayserver/0/

    11-20 22:40:20.756: I/MocaLog(671): 20T224020, T3, Called startTmMessage with URL Template:/cli/iarelayserver/0/

    11-20 22:40:20.777: I/MocaLog(671): 20T224020, T3, Connect to: http://localhost:5001/cli/iarelayserver/0/tm

    11-20 22:40:20.917: I/MocaLog(671): 20T224020, T3, Cookies – setRequest:

    11-20 22:40:21.038: I/MocaLog(671): 20T224021, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:21.117: I/MocaLog(671): 20T224021, T3, Testing Relay Server URL Template:/

    11-20 22:40:21.136: I/MocaLog(671): 20T224021, T3, Called startTmMessage with URL Template:/

    11-20 22:40:21.156: I/MocaLog(671): 20T224021, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:21.276: I/MocaLog(671): 20T224021, T3, Cookies – setRequest:

    11-20 22:40:21.347: I/MocaLog(671): 20T224021, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:21.356: I/MocaLog(671): 20T224021, T3, Did NOT find good Relay Server URL Template

    11-20 22:40:21.386: I/MocaLog(671): 20T224021, T3, error retrieving ServerVersionInfo: Could not connect to server. Verify Relay Server URL Template

    11-20 22:40:21.556: I/MocaLog(671): 20T224021, T3, current ServerVersionInfo: null,11

    11-20 22:40:21.586: I/MocaLog(671): 20T224021, T3, tm uri:  ‘tm://mo/rmi?cid=0&devid=Simulator37a84b0b-a72f-4db2-8155-c9db06cac708__SMP101&devtype=android&connid=1&noauth=true’

    11-20 22:40:21.646: I/MocaLog(671): 20T224021, T3, Starting URL Template discovery

    11-20 22:40:21.727: I/MocaLog(671): 20T224021, T3, Testing Relay Server URL Template:/

    11-20 22:40:21.746: I/MocaLog(671): 20T224021, T3, Called startTmMessage with URL Template:/

    11-20 22:40:21.776: I/MocaLog(671): 20T224021, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:21.806: I/MocaLog(671): 20T224021, T3, Cookies – setRequest:

    11-20 22:40:21.846: I/MocaLog(671): 20T224021, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:21.856: I/MocaLog(671): 20T224021, T3, Testing Relay Server URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:21.896: I/MocaLog(671): 20T224021, T3, Called startTmMessage with URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:21.949: I/MocaLog(671): 20T224021, T3, Connect to: http://localhost:5001/ias_relay_server/client/rs_client.dll/0/tm

    11-20 22:40:22.011: I/MocaLog(671): 20T224021, T3, Cookies – setRequest:

    11-20 22:40:22.046: I/MocaLog(671): 20T224022, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:22.066: I/MocaLog(671): 20T224022, T3, Testing Relay Server URL Template:/cli/iarelayserver/0/

    11-20 22:40:22.149: I/MocaLog(671): 20T224022, T3, Called startTmMessage with URL Template:/cli/iarelayserver/0/

    11-20 22:40:22.168: I/MocaLog(671): 20T224022, T3, Connect to: http://localhost:5001/cli/iarelayserver/0/tm

    11-20 22:40:22.246: I/MocaLog(671): 20T224022, T3, Cookies – setRequest:

    11-20 22:40:22.276: I/MocaLog(671): 20T224022, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:22.286: I/MocaLog(671): 20T224022, T3, Testing Relay Server URL Template:/

    11-20 22:40:22.338: I/MocaLog(671): 20T224022, T3, Called startTmMessage with URL Template:/

    11-20 22:40:22.356: I/MocaLog(671): 20T224022, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:22.376: I/MocaLog(671): 20T224022, T3, Cookies – setRequest:

    11-20 22:40:22.406: I/MocaLog(671): 20T224022, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:22.440: I/MocaLog(671): 20T224022, T3, Did NOT find good Relay Server URL Template

    11-20 22:40:22.458: I/MocaLog(671): 20T224022, T3, MoObject.execute — caught TM exception – 15:com.sybase.messaging.traveler.TmException: Could not connect to server. Verify Relay Server URL Template

    11-20 22:40:22.545: I/MocaLog(671): 20T224022, T3, MclServerRmiCalls.addDeviceRegistration failed.  Ex: Error: 558 Message: ‘Could not connect to server. Verify Relay Server URL Template’

    11-20 22:40:22.566: I/MocaLog(671): 20T224022, T3, MessagingClientLib: getConfigProperty: 1

    11-20 22:40:22.667: I/MocaLog(671): 20T224022, T3, MessagingClientLib: getConfigProperty: 2

    11-20 22:40:22.687: I/MocaLog(671): 20T224022, T3, MessagingClientLib: getConfigProperty: 3

    11-20 22:40:22.737: I/MocaLog(671): 20T224022, T3, MessagingClientLib: getConfigProperty: 10001

    11-20 22:40:22.776: I/MocaLog(671): 20T224022, T3, Starting URL Template discovery

    11-20 22:40:22.826: I/MocaLog(671): 20T224022, T3, Testing Relay Server URL Template:/

    11-20 22:40:22.907: I/MocaLog(671): 20T224022, T3, Called startTmMessage with URL Template:/

    11-20 22:40:22.996: I/MocaLog(671): 20T224022, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:23.077: I/MocaLog(671): 20T224023, T3, Cookies – setRequest:

    11-20 22:40:23.197: D/dalvikvm(671): GC_CONCURRENT freed 427K, 8% free 6417K/6919K, paused 52ms+66ms, total 487ms

    11-20 22:40:23.257: I/MocaLog(671): 20T224023, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:23.277: I/MocaLog(671): 20T224023, T3, Testing Relay Server URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:23.337: I/MocaLog(671): 20T224023, T3, Called startTmMessage with URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:23.357: I/MocaLog(671): 20T224023, T3, Connect to: http://localhost:5001/ias_relay_server/client/rs_client.dll/0/tm

    11-20 22:40:23.407: I/MocaLog(671): 20T224023, T3, Cookies – setRequest:

    11-20 22:40:23.537: I/Choreographer(671): Skipped 33 frames!  The application may be doing too much work on its main thread.

    11-20 22:40:23.617: I/MocaLog(671): 20T224023, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:23.687: I/MocaLog(671): 20T224023, T3, Testing Relay Server URL Template:/cli/iarelayserver/0/

    11-20 22:40:23.757: I/MocaLog(671): 20T224023, T3, Called startTmMessage with URL Template:/cli/iarelayserver/0/

    11-20 22:40:23.807: I/MocaLog(671): 20T224023, T3, Connect to: http://localhost:5001/cli/iarelayserver/0/tm

    11-20 22:40:23.827: I/MocaLog(671): 20T224023, T3, Cookies – setRequest:

    11-20 22:40:23.997: I/MocaLog(671): 20T224023, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:24.027: I/MocaLog(671): 20T224024, T3, Testing Relay Server URL Template:/

    11-20 22:40:24.097: I/MocaLog(671): 20T224024, T3, Called startTmMessage with URL Template:/

    11-20 22:40:24.127: I/MocaLog(671): 20T224024, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:24.147: I/MocaLog(671): 20T224024, T3, Cookies – setRequest:

    11-20 22:40:24.177: I/MocaLog(671): 20T224024, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:24.207: I/MocaLog(671): 20T224024, T3, Did NOT find good Relay Server URL Template

    11-20 22:40:24.307: I/MocaLog(671): 20T224024, T3, Error:isServerCapableOf:

    11-20 22:40:24.307: I/MocaLog(671): com.sybase.messaging.traveler.TmException: Could not connect to server. Verify Relay Server URL Template

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.messaging.traveler.TmSession.getUrlTemplate(TmSession.java:439)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.messaging.traveler.TmSession.startTmMessage(TmSession.java:574)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.messaging.traveler.TmSession.sendTmMessage(TmSession.java:515)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.messaging.traveler.TmSession.sendSimpleMessage(TmSession.java:465)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.mo.ServerVersionInfo.refreshVersionInfo(ServerVersionInfo.java:127)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.mo.ServerVersionInfo.isServerCapableOf(ServerVersionInfo.java:280)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.mo.MoObject.isServerCapableOf(MoObject.java:1269)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.mo.MoObject.execute(MoObject.java:459)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.messaging.MclServerRmiCalls.addDeviceRegistration(MclServerRmiCalls.java:103)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.messaging.MclServerRmiCalls.addDeviceRegistration(MclServerRmiCalls.java:234)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.mobile.Application.register(Application.java:435)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.mobile.Application.access$000(Application.java:61)

    11-20 22:40:24.307: I/MocaLog(671):           at com.sybase.mobile.Application$1.run(Application.java:385)

    11-20 22:40:24.327: I/MocaLog(671): 20T224024, T3, execute:  objectName=’monet:DeviceManagement.dll:DeviceManagement’ methodName=’AddDeviceRegistration’ param count(false)=9

    11-20 22:40:24.397: I/MocaLog(671): 20T224024, T3, execute:  refreshing stale ServerVersionInfo

    11-20 22:40:24.417: I/MocaLog(671): 20T224024, T3, Starting URL Template discovery

    11-20 22:40:24.507: I/MocaLog(671): 20T224024, T3, Testing Relay Server URL Template:/

    11-20 22:40:24.577: I/MocaLog(671): 20T224024, T3, Called startTmMessage with URL Template:/

    11-20 22:40:24.677: I/MocaLog(671): 20T224024, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:24.697: I/MocaLog(671): 20T224024, T3, Cookies – setRequest:

    11-20 22:40:24.757: I/MocaLog(671): 20T224024, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:24.777: I/MocaLog(671): 20T224024, T3, Testing Relay Server URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:24.787: I/MocaLog(671): 20T224024, T3, Called startTmMessage with URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:24.847: I/MocaLog(671): 20T224024, T3, Connect to: http://localhost:5001/ias_relay_server/client/rs_client.dll/0/tm

    11-20 22:40:24.877: I/MocaLog(671): 20T224024, T3, Cookies – setRequest:

    11-20 22:40:24.947: I/MocaLog(671): 20T224024, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:24.987: I/MocaLog(671): 20T224024, T3, Testing Relay Server URL Template:/cli/iarelayserver/0/

    11-20 22:40:25.017: I/MocaLog(671): 20T224025, T3, Called startTmMessage with URL Template:/cli/iarelayserver/0/

    11-20 22:40:25.057: I/MocaLog(671): 20T224025, T3, Connect to: http://localhost:5001/cli/iarelayserver/0/tm

    11-20 22:40:25.107: I/MocaLog(671): 20T224025, T3, Cookies – setRequest:

    11-20 22:40:25.157: I/MocaLog(671): 20T224025, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:25.237: I/MocaLog(671): 20T224025, T3, Testing Relay Server URL Template:/

    11-20 22:40:25.248: I/MocaLog(671): 20T224025, T3, Called startTmMessage with URL Template:/

    11-20 22:40:25.267: I/MocaLog(671): 20T224025, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:25.287: I/MocaLog(671): 20T224025, T3, Cookies – setRequest:

    11-20 22:40:25.337: I/MocaLog(671): 20T224025, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:25.437: I/MocaLog(671): 20T224025, T3, Did NOT find good Relay Server URL Template

    11-20 22:40:25.457: I/MocaLog(671): 20T224025, T3, error retrieving ServerVersionInfo: Could not connect to server. Verify Relay Server URL Template

    11-20 22:40:25.577: I/MocaLog(671): 20T224025, T3, current ServerVersionInfo: null,11

    11-20 22:40:25.629: I/MocaLog(671): 20T224025, T3, tm uri:  ‘tm://mo/rmi?cid=0&devid=Simulator37a84b0b-a72f-4db2-8155-c9db06cac708__SMP101&devtype=android&connid=1&noauth=true’

    11-20 22:40:25.637: I/Choreographer(671): Skipped 77 frames!  The application may be doing too much work on its main thread.

    11-20 22:40:25.677: I/MocaLog(671): 20T224025, T3, Starting URL Template discovery

    11-20 22:40:25.767: I/MocaLog(671): 20T224025, T3, Testing Relay Server URL Template:/

    11-20 22:40:25.778: I/MocaLog(671): 20T224025, T3, Called startTmMessage with URL Template:/

    11-20 22:40:25.797: I/MocaLog(671): 20T224025, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:25.817: I/MocaLog(671): 20T224025, T3, Cookies – setRequest:

    11-20 22:40:25.867: I/MocaLog(671): 20T224025, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:25.900: I/MocaLog(671): 20T224025, T3, Testing Relay Server URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:25.947: I/MocaLog(671): 20T224025, T3, Called startTmMessage with URL Template:/ias_relay_server/client/rs_client.dll/0/

    11-20 22:40:25.967: I/MocaLog(671): 20T224025, T3, Connect to: http://localhost:5001/ias_relay_server/client/rs_client.dll/0/tm

    11-20 22:40:25.997: I/MocaLog(671): 20T224025, T3, Cookies – setRequest:

    11-20 22:40:26.077: I/MocaLog(671): 20T224026, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:26.097: I/MocaLog(671): 20T224026, T3, Testing Relay Server URL Template:/cli/iarelayserver/0/

    11-20 22:40:26.207: I/MocaLog(671): 20T224026, T3, Called startTmMessage with URL Template:/cli/iarelayserver/0/

    11-20 22:40:26.257: I/MocaLog(671): 20T224026, T3, Connect to: http://localhost:5001/cli/iarelayserver/0/tm

    11-20 22:40:26.347: I/MocaLog(671): 20T224026, T3, Cookies – setRequest:

    11-20 22:40:26.427: I/MocaLog(671): 20T224026, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:26.447: I/MocaLog(671): 20T224026, T3, Testing Relay Server URL Template:/

    11-20 22:40:26.457: I/MocaLog(671): 20T224026, T3, Called startTmMessage with URL Template:/

    11-20 22:40:26.577: I/MocaLog(671): 20T224026, T3, Connect to: http://localhost:5001/tm

    11-20 22:40:26.625: D/dalvikvm(671): GC_CONCURRENT freed 428K, 8% free 6417K/6919K, paused 57ms+71ms, total 403ms

    11-20 22:40:26.637: I/MocaLog(671): 20T224026, T3, Cookies – setRequest:

    11-20 22:40:26.727: I/Choreographer(671): Skipped 120 frames!  The application may be doing too much work on its main thread.

    11-20 22:40:26.767: I/MocaLog(671): 20T224026, T3, URL discovery exception error code: 6 http error:0

    11-20 22:40:26.817: I/MocaLog(671): 20T224026, T3, Did NOT find good Relay Server URL Template

    11-20 22:40:26.907: I/MocaLog(671): 20T224026, T3, MoObject.execute — caught TM exception – 15:com.sybase.messaging.traveler.TmException: Could not connect to server. Verify Relay Server URL Template

    11-20 22:40:26.980: I/MocaLog(671): 20T224026, T3, MclServerRmiCalls.addDeviceRegistration failed.  Ex: Error: 558 Message: ‘Could not connect to server. Verify Relay Server URL Template’

    11-20 22:40:26.987: D/com.sybase.mobile.Application(671): register

    11-20 22:40:26.987: D/com.sybase.mobile.Application(671): Error: 558 Message: Error: 558 Message: ‘Could not connect to server. Verify Relay Server URL Template’

    11-20 22:40:26.987: D/com.sybase.mobile.Application(671):           at com.sybase.messaging.MclServerRmiCalls.addDeviceRegistration(MclServerRmiCalls.java:247)

    11-20 22:40:26.987: D/com.sybase.mobile.Application(671):           at com.sybase.mobile.Application.register(Application.java:435)

    11-20 22:40:26.987: D/com.sybase.mobile.Application(671):           at com.sybase.mobile.Application.access$000(Application.java:61)

    11-20 22:40:26.987: D/com.sybase.mobile.Application(671):           at com.sybase.mobile.Application$1.run(Application.java:385)

    11-20 22:40:26.987: I/System.out(671): Registration Error: Error: 558 Message: ‘Could not connect to server. Verify Relay Server URL Template’

    11-20 22:40:27.023: E/SMP101(671): Cannot register Error: 558 Message: ‘Could not connect to server. Verify Relay Server URL Template’

    11-20 22:40:27.027: I/SMP101(671): Application REGISTERED

    11-20 22:40:27.027: D/UpgradeUtil(671): upgrade takes : 0ms

    11-20 22:40:27.267: D/dalvikvm(671): Trying to load lib /data/data/com.mycorp.smp101.android.app/lib/libultralitej12.so 0x40ff3be8

    11-20 22:40:27.287: D/dalvikvm(671): Added shared lib /data/data/com.mycorp.smp101.android.app/lib/libultralitej12.so 0x40ff3be8

    11-20 22:40:27.287: D/dalvikvm(671): No JNI_OnLoad found in /data/data/com.mycorp.smp101.android.app/lib/libultralitej12.so 0x40ff3be8, skipping init

    11-20 22:40:27.617: I/SMP101(671): Starting Initial Sync

    11-20 22:40:27.827: I/MocaLog(671): 20T224027, T2, MessagingClientLib: getConfigProperty: 7

    11-20 22:40:27.918: I/MocaLog(671): 20T224027, T2, MessagingClientLib: getDeviceID

    11-20 22:40:27.927: I/SMP101(671): OnSynchronize() called with STATUS 1

    11-20 22:40:28.003: W/System.err(671): com.sybase.mobile.ApplicationRuntimeException: Application settings are not available

    11-20 22:40:28.081: W/System.err(671):           at com.sybase.mobile.ApplicationSettings.checkApplicationSettingsAvailable(ApplicationSettings.java:94)

    11-20 22:40:28.098: W/System.err(671):           at com.sybase.sup.client.persistence.RbsDatabaseDelegate.internalSynchronize(RbsDatabaseDelegate.java:477)

    11-20 22:40:28.098: W/System.err(671):           at com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronizeWithCallback(RbsDatabaseDelegate.java:427)

    11-20 22:40:28.098: W/System.err(671):           at com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronize(RbsDatabaseDelegate.java:1439)

    11-20 22:40:28.098: W/System.err(671):           at com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronize(RbsDatabaseDelegate.java:1430)

    11-20 22:40:28.107: W/System.err(671):           at com.mycorp.smp101.android.mbo.SMP101DB.synchronize(SMP101DB.java:199)

    11-20 22:40:28.127: W/System.err(671):           at com.mycorp.smp101.android.app.SMP101SampleActivity$2.run(SMP101SampleActivity.java:151)

    11-20 22:40:28.127: W/System.err(671):           at java.lang.Thread.run(Thread.java:856)

    (0) 
    1. jitendra kansal Post author

      Dmitriy Prokofiev

      Sorry for late response.  Has this issue been resolved?

      from the logs i can see clearly that

      Message: ‘Could not connect to server. Verify Relay Server URL Template’

      what do you user status in SCC? Is it showing as online?

      Rgrds,

      Jitendra

      (0) 
      1. Dmitriy Prokofiev

        hi, my problem is still actual.

        in case of Sybase Unwired platform 2.1.3 with 03 sp it works!

        but i am trying to do the same with SAP Mobile Platform 2.3, with default installation settings.

        program can’t do the registeration of application, and all errors are about RelayServer.

        (0) 
        1. Midhun VP

          Can you create a new discussion with the steps you followed and issue in detail so we can help you better. According to logs, it says that your mobile is not reaching SUP server. Make sure the Port 5001 is open in your SUP server and your mobile is inside your private network and check.

          – Midhun VP

          (0) 
  5. Suseelan Hari

    Hi Jitendra,

    You rock as usual. No second thought! Fantabulous blog about SUP and I am learning SUP. Trying to learn about SMP too. 🙂

    Thank you so much for sharing golden information.

    Regards,

    Hari Suseelan

    (0) 
  6. Nham Duc Long

    Dear Kansal,

    How can i download the SUP 2.2, i don’t find it on Sap Market Place. I download the SMP 3.0 SP01 on there, but i can not install. Message is “SAP Mobile Platform SDK 3.0 is not installed on the system. Cannot upgrade to 3.0 SP01”. But i cannot find down the 3.0. Can you help me?

    Longnd.

    (0) 
    1. jitendra kansal Post author

      Hi Nham Duc Long

      Request you to post a new thread since this thread doesnt relevant with this document content.

      http://scn.sap.com/community/developer-center/post!input.jspa?containerType=14&container=2408&contentType=1

      You must search with “M” for SUP 2.2. I am able to see it in service marketplace.

      SMP 3.0 runtime hasnt release in the market, it is still in Ramp-up process. So there is no use of SDK alone.

      Rgrds,

      Jitendra

      (0) 

Leave a Reply