mattcobb 5a014bb30c Remove config specific change 4 years ago
Validation move validation taks list 5 years ago
sdk Remove config specific change 4 years ago
.gitattributes fix possible typo 5 years ago
.gitignore second part of bug #81 5 years ago be more explicit about requiring an older version of jsduck 5 years ago



The AT&T HTML5 SDK provides an HTML5 framework for calling the AT&T API Platform.

SDK Contents

Each release consists of two ZIP files: one containing the SDK source code, and the other with the SDK documentation. Please refer to the SDK Filename Format section below for more details on the ZIP filenames. Please refer to the Building The SDK section below for instructions describing how you can build the SDK yourself.

  • SDK Documentation Located at doc folder
  • JavaScript client library att-api-client.js
  • Java Server Code Java server side including:
    • Source code: server/java/src
    • Distributable war and jar files: server/java/dist
    • Documentation: server/java/docs
  • PHP Server code
    • Source: server/php/public_html
    • Documentation: server/php/docs
  • Ruby Server code
    • Source: server/ruby
    • Documentation: server/ruby/docs
  • Standalone Sample Apps Located at webcontent
  • License

Consuming the SDK

If you want to use the SDK, please unpack the associated ZIP files and read the documentation in the doc ZIP. The remainder of the instructions below are intended for developers who are modifying or updating the SDK.

The SDK Developer's Quick-Start

The checked-in source tree represents a working deployment of the SDK. After installing the prerequisite Ruby software described below, you can run the samples app server:

sdk/server/ruby/att> ruby app.rb


sdk/server/ruby/att> ruby listener.rb

And then you can view the samples by navigating a Chrome browser to:


You can also alternatively run the Java or PHP server, after setting up their associated prerequisites.

Installing Ruby 1.9.3 on Mac OSX

  1. It is wise to install rvm first. Start by opening up terminal and running this command:

    curl -L | bash -s stable

  2. After the installation of rvm run the following command:

    rvm install ruby-1.9.3-p484

  3. Make Ruby 1.9.3 default by running 'rvm --default ruby-1.9.3

Installing the Sinatra Web Server

The following instructions apply to both the Virtual Box Environment and any Windows environment you are using to test the SDK code.

  1. You will need the 1.9.3 or later version of Ruby.

  2. To install any rubyGem, the syntax is:

    gem install gemNameHere

  3. So installing sinatra is almost as simple as:

    gem install sinatra

    except that you may need to look at any error messages to install missing components or dependent gems. The messages are not exactly friendly.

    Please note that in order to use jsduck on Java and PHP, we require an older version of the tool, which can be installed with:

    gem install -v 3.11.2 jsduck

    Common gems that will be used to run this project are:

    • jsduck version 3.11.2
    • yard
    • thin
    • crack
    • mechanize
    • uuid
    • immutable_struct
    • rest-client

    One thing that helps is that if you get the rubyGem name approximately right, the gem install will often suggest an alternative after a long pause, which usually is correct.

SDK Filename Format

The name convention we are using, as per AT&T request, is the following:

SDK source code: SDK documentation:


  • MAJOR is the SDK major version.
  • MINOR is the SDK minor version.
  • DATE is the formatted date (yyyyMMddHHmm) to identify the build.

The sdk.version values are configured in the file.

Packaging The SDK

The SDK is produced by executing the following script on sdk folder:

sdk# ./

Although the packaging process should not place any unnecessary generated files in the release ZIP files, you may find it useful to run git clean -fdx before packaging, just to be sure.

This script will compile and package all server side languages and samples. The generated files will be placed on the root folder of the project. One ZIP file will be created for the SDK development material, and a second ZIP file will be created for the SDK documentation.

Troubleshooting tip: If the script doesn't run, check the file's execution settings; you can enable the execute bit with:

chmod +x

The packaging process has a number of dependencies you will need to set up in advance, as described below:

Setting up a Build Environment

Note that the build process for this project was originally set up to run in a Linux environment; for best results we recommend doing the same. The free product VirtualBox can be used to set up a Linux virtual machine.

  1. Install the java, including the JDK. Either the Oracle JDK or OpenJDK will work just fine.

  2. You must have the JAVA_HOME environment variable pointing to the correct location for the scripts to work. Type echo $JAVA_HOME at the Bash Terminal prompt, and if nothing happens, the variable has not been set. It should be set to the root of your Java installation, and $JAVA_HOME/bin should be in your $PATH.

  3. Install Ruby; the latest version in the 1.9.x series currently is the most likely not to cause problems. (The dependent Ruby libraries are all present and reliable for 1.9.3.) Please refer to the documentation packaged with the SDK; it contains detailed instructions for installing the required Ruby components. This documentation is checked in at sdk/doc_src/guides/server_ruby_env/, but the HTML version included in the SDK is more legible.

  4. Install the Ant build tool, using Ant web site instructions.

  5. Install the JSDuck documentation tool. This is a Ruby gem that can be installed using the command below. If Ruby is installed as admin, you may need to prefix that command with 'sudo'. NOTE You must install the older version of JSDuck listed below - the tool removed support for documenting non-JavaScript source code in more recent versions.

    • gem install -v 3.11.2 jsduck