SUP Dev Blog

First off:  it was an amazing week @TechEd Vegas.  It was great to meet all the customers, partners, and individuals involved in SUP projects, great to be able to share the features and apps coming with and on SUP 2.1, and to get feedback on our roadmap strategy for the upcoming year.  It’s an exciting time to be in mobile apps in the SAP ecosystem.  I’m looking forward to Madrid in November to share with the community in EMEA.

Second:  now that I can set TechEd prep aside, there are a bunch of SUP development posts that have been stacking up that I want to get out.  To start off, I’ll deal with a most basic question recently posted to the Why Are We So Excited About 2.0.. post:  “When I am deploying application in SUP workspace, an error is generating while connecting to ‘My Unwired Server’.  The error is: ‘ Could not connect to My Unwired Server’. Ping also failed.”

If you cannot connect to the SUP Server, this typically means one of two things:  the server isn’t started, or you have a domain configuration which is incorrect.

Check the SUP Server is running

1. In the Services directory, look for: SybaseUnwiredPlatform<hostname>Server1
2. If it is not started, click the ‘Start Sybase Unwired Platform Services’ batch file icon installed on the desktop.  The batch will run, and attempt to start the set of SUP services.  This includes the internal databases, the OpenDS service, etc.  When it comes to the SUPServer1 service, it will check some properties against the license/admin service.  This happens regardless of whether you are using a licensed or evaluation environment.
3. Refresh the Services directory.  If the SUPServer1 failed to start, that means one of two things:  the license settings are inaccurate, and/or the admin services are improperly configured.
4. If the SUP Server is running, skip to:  Check the Connection Profile Settings

Check that the License settings are correct

1. Make sure your license is for the version you selected @ install.  This process is documented here:  Sybase Unwired Platform Licenses
2. Key Points:  make sure that you have the correct version of the license (Locating Information in a License File)
3. Troubleshooting guide is here:  Troubleshooting SySAM

Check the Admin Tool Domain settings

1. Sometimes if you installed SUP while on a corporate domain, that domain setting will be hard-coded to the Admin service-config file.  To check this, go to: <Install dir>/SCC-3_0/Services/RMI/, and open service-config in Notepad.
2. In the <properties> tag, make sure that the “address” value is set to “localhost” or an appropriate IP for when the administration service is running locally.
3. Example:

<?xml version="1.0" encoding="ISO-8859-1"?>
<service-config id="RMIService" version="3.0.0" name="RMI Service" class="com.sybase.ua.services.rmi.RMIService" provider-name="Sybase, Inc." register-on-startup="true" mbean-type="Model MBean" mbean-descriptor="mbean-descriptor.xml" arl-config="arl.xml">
  <dependencies />
  <properties>
    <set-property property="address" value="localhost" />
    <set-property property="addressType" value="dynamic" />
    <set-property property="port" value="9999" />
    <set-property property="timeout" value="43200" />
  </properties>
</service-config>

Save.  If you changed this setting, you should re-boot your machine so that the SCC service can capture the new value and take effect.  Once you’ve confirmed in the Services window that the Sybase Unified Agent 3.0 is ‘Started’ (not just ‘Starting), run the ‘Start Sybase Unwired Platform Services’ bat file on the desktop.  The server should get running.

Check the Connection Profile Settings

Now, the server is running, but you can’t connect from the Eclipse tool.  This has to do with the same domain issue as in the RMI service, and is a much easier fix because you can do it right in Eclipse.

1. Right-click on the ‘My Unwired Server’ connection profile in the Enterprise Explorer window, and select ‘Properties’.
2. Switch from ‘Common’ view to ‘Unwired Server Connection Properties’.
3. If you are running SUP on a local machine, delete the value in the ‘IP domain’ field.  Leave it empty.
4. Click ‘Test Connection’ to get a ping.  You should be able to ping successfully.

Special Case:  TechEd 2011 images: If you are using a TechEd 2011 image, you must also change the ‘Port’ value to 20000 from the default 2000.  This was modified during the image creation to eliminate a conflict, and was not propagated to the WorkSpace configurations.