Java HTML Shell
Clone or download
Permalink
Failed to load latest commit information.
.github feat(build): Add semantic-release integration (#958) Jul 2, 2018
.utility fix(utility): Fix shebang and script filepath when generating API diff Jun 4, 2018
assistant docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
conversation docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
core test(auth): Add test for converting username and password to IAM Jul 11, 2018
discovery docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
examples docs(examples): Fix compilation errors Jul 9, 2018
gradle/wrapper πŸš’ cherry pick develop commits Aug 27, 2017
java-sdk fix(assistant): Add missing dependency line for Assistant Mar 19, 2018
language-translator docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
natural-language-classifier docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
natural-language-understanding docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
personality-insights docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
speech-to-text docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
text-to-speech docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
tone-analyzer docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
visual-recognition docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
.bumpversion.cfg docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
.gitattributes switch to OkHttp #72 Nov 7, 2015
.gitignore chore(gitignore): Ignore .rej files Jun 12, 2018
.releaserc ci: Add repositoryUrl Jul 12, 2018
.travis.yml ci: Remove use of deployment script Aug 8, 2018
CHANGELOG.md πŸš’ cherry pick develop commits Aug 27, 2017
LICENSE More improvements - fold arbitrary JSON objs into referencing properties Mar 11, 2017
MIGRATION.md merge master into develop Jun 24, 2017
README.md docs: Update version numbers from 6.3.1 β†’ 6.4.0 Aug 14, 2018
RELEASE.md docs(release): Update release documentation Aug 8, 2018
build.gradle feat(build): Add semantic-release integration (#958) Jul 2, 2018
checkstyle.xml test(discovery): Add integration tests for credentials method Jul 12, 2018
config.properties.enc build(credentials): Update credentials for LT Jun 12, 2018
gradle.properties [Gradle Release Plugin] - new version commit: 'java-sdk-6.4.1'. Aug 14, 2018
gradlew πŸš’ cherry pick develop commits Aug 27, 2017
gradlew.bat πŸš’ cherry pick develop commits Aug 27, 2017
settings.gradle Merge branch 'develop' into codegen/assistant Mar 15, 2018
utils.gradle Restructuring tests for Gradle Jan 9, 2017

README.md

Watson APIs Java SDK

Build Status Slack Maven Central CLA assistant

Java client library to use the Watson APIs.

Table of Contents

Before you begin

Installation

Maven

All the services:

<dependency>
	<groupId>com.ibm.watson.developer_cloud</groupId>
	<artifactId>java-sdk</artifactId>
	<version>6.4.0</version>
</dependency>

Only Discovery:

<dependency>
	<groupId>com.ibm.watson.developer_cloud</groupId>
	<artifactId>discovery</artifactId>
	<version>6.4.0</version>
</dependency>
Gradle

All the services:

'com.ibm.watson.developer_cloud:java-sdk:6.4.0'

Only Assistant:

'com.ibm.watson.developer_cloud:assistant:6.4.0'
Development snapshots

Snapshots of the development version are available in Sonatype's snapshots repository.

Gradle

Add repository to your project Gradle file

allprojects {
    repositories {
        maven { url "https://oss.sonatype.org/content/repositories/snapshots" }
    }
}

And then reference the snapshot version on your app module gradle Only Speech to Text:

'com.ibm.watson.developer_cloud:speech-to-text:6.4.1-SNAPSHOT'
JAR

Download the jar with dependencies here.

Now, you are ready to see some examples.

Usage

The examples within each service assume that you already have service credentials. If not, you will have to create a service in IBM Cloud.

If you are running your application in IBM Cloud (or other platforms based on Cloud Foundry), you don't need to specify the credentials; the library will get them for you by looking at the VCAP_SERVICES environment variable.

Running in IBM Cloud

When running in IBM Cloud (or other platforms based on Cloud Foundry), the library will automatically get the credentials from VCAP_SERVICES. If you have more than one plan, you can use CredentialUtils to get the service credentials for an specific plan.

Authentication

Watson services are migrating to token-based Identity and Access Management (IAM) authentication.

  • With some service instances, you authenticate to the API by using IAM.
  • In other instances, you authenticate by providing the username and password for the service instance.
  • Visual Recognition uses a form of API key only with instances created before May 23, 2018. Newer instances of Visual Recognition use IAM.

Note: Previously, it was possible to authenticate using a token in a header called X-Watson-Authorization-Token. This method is deprecated. The token continues to work with Cloud Foundry services, but is not supported for services that use Identity and Access Management (IAM) authentication. See here for details.

Getting credentials

To find out which authentication to use, view the service credentials. You find the service credentials for authentication the same way for all Watson services:

  1. Go to the IBM Cloud Dashboard page.
  2. Either click an existing Watson service instance or click Create resource > AI and create a service instance.
  3. Copy the url and either apikey or username and password. Click Show if the credentials are masked.

In your code, you can use these values in the service constructor or with a method call after instantiating your service.

IAM

Some services use token-based Identity and Access Management (IAM) authentication. IAM authentication uses a service API key to get an access token that is passed with the call. Access tokens are valid for approximately one hour and must be regenerated.

You supply either an IAM service API key or an access token:

  • Use the API key to have the SDK manage the lifecycle of the access token. The SDK requests an access token, ensures that the access token is valid, and refreshes it if necessary.
  • Use the access token if you want to manage the lifecycle yourself. For details, see Authenticating with IAM tokens. If you want to switch to API key, override your stored IAM credentials with an IAM API key. Then call the setIamCredentials() method again.

Supplying the IAM API key

// in the constructor, letting the SDK manage the IAM token
IamOptions options = new IamOptions.Builder()
  .apiKey("<iam_api_key>")
  .url("<iam_url>") // optional - the default value is https://iam.bluemix.net/identity/token
  .build();
Discovery service = new Discovery("2017-11-07", options);
// after instantiation, letting the SDK manage the IAM token
Discovery service = new Discovery("2017-11-07");
IamOptions options = new IamOptions.Builder()
  .apiKey("<iam_api_key>")
  .build();
service.setIamCredentials(options);

Supplying the access token

// in the constructor, assuming control of managing IAM token
IamOptions options = new IamOptions.Builder()
  .accessToken("<access_token>")
  .build();
Discovery service = new Discovery("2017-11-07", options);
// after instantiation, assuming control of managing IAM token
Discovery service = new Discovery("2017-11-07");
IamOptions options = new IamOptions.Builder()
  .accessToken("<access_token>")
  .build();
service.setIamCredentials(options);

Username and password

// in the constructor
Discovery service = new Discovery("2017-11-07", "<username>", "<password>");
// after instantiation
Discovery service = new Discovery("2017-11-07");
service.setUsernameAndPassword("<username>", "<password>");

API key

Important: This type of authentication works only with Visual Recognition instances created before May 23, 2018. Newer instances of Visual Recognition use IAM.

// in the constructor
VisualRecognition service = new VisualRecognition("2016-05-20", "<api_key>");
// after instantiation
VisualRecognition service = new VisualRecognition("2016-05-20");
service.setApiKey("<api_key>");

Android

The Android SDK utilizes the Java SDK while making some Android-specific additions. This repository can be found here. It depends on OkHttp and gson.

Using a proxy

Override the configureHttpClient() method and add the proxy using the OkHttpClient.Builder object.

For example:

Assistant service = new Assistant("2018-02-16") {
  @Override
  protected OkHttpClient configureHttpClient() {
    Proxy proxy = new Proxy(Proxy.Type.HTTP, new InetSocketAddress("proxyHost", 8080));
    return super.configureHttpClient().newBuilder().proxy(proxy).build();
  }
};

service.setUsernameAndPassword("<username>", "<password>");

WorkspaceCollection workspaces = service.listWorkspaces().execute();
System.out.println(workspaces);

For more information see: OkHTTPClient Proxy authentication how to?

PersonalityInsights service = new PersonalityInsights("2016-10-19");
String apiKey = CredentialUtils.getAPIKey(service.getName(), CredentialUtils.PLAN_STANDARD);
service.setApiKey(apiKey);

Sending request headers

Custom headers can be passed with any request. To do so, add the header to the ServiceCall object before executing the request. For example, this is what it looks like to send the header Custom-Header along with a call to the Watson Assistant service:

WorkspaceCollection workspaces = service.listWorkspaces()
  .addHeader("Custom-Header", "custom_value")
  .execute();

Parsing HTTP response info

The basic execute(), enqueue(), and rx() methods make HTTP requests to your Watson service and return models based on the requested endpoint. If you would like access to some HTTP response information along with the response model, you can use the more detailed versions of those three methods: executeWithDetails(), enqueueWithDetails(), and rxWithDetails(). To capture the responses, use the new Response<T> class, with T being the expected response model.

Here is an example of calling the Watson Assistant listWorkspaces() method and parsing its response model as well as the response headers:

Response<WorkspaceCollection> response = service.listWorkspaces().executeWithDetails();

// getting result equivalent to execute()
WorkspaceCollection workspaces = response.getResult();

// getting returned HTTP headers
Headers responseHeaders = response.getHeaders();

Note that when using enqueueWithDetails(), you must also implement the new ServiceCallbackWithDetails interface. For example:

service.listWorkspaces().enqueueWithDetails(new ServiceCallbackWithDetails<WorkspaceCollection>() {
  @Override
  public void onResponse(Response<WorkspaceCollection> response) {
    WorkspaceCollection workspaces = response.getResult();
    Headers responseHeaders = response.getHeaders();
  }

  @Override
  public void onFailure(Exception e) { }
});

Default headers

Default headers can be specified at any time by using the setDefaultHeaders(Map<String, String> headers) method.

The example below sends the X-Watson-Learning-Opt-Out header in every request preventing Watson from using the payload to improve the service.

PersonalityInsights service = new PersonalityInsights("2016-10-19");

Map<String, String> headers = new HashMap<String, String>();
headers.put(HttpHeaders.X_WATSON_LEARNING_OPT_OUT, "true");

service.setDefaultHeaders(headers);

// All the api calls from now on will send the default headers

Specifying a service URL

You can set the correct API endpoint for your service calling setEndPoint().

For example, if you have the Discovery service in Germany, the endpoint may be https://gateway-fra.watsonplatform.net/discovery/api.

You will need to call

Discovery service = new Discovery("2017-11-07");
service.sentEndPoint("https://gateway-fra.watsonplatform.net/discovery/api")

401 unauthorized error

Make sure you are using the service credentials and not your IBM Cloud account/password. Check the API endpoint, you may need to update the default using setEndPoint().

Changes for v4.0

Version 4.0 focuses on the move to programmatically-generated code for many of the services. See the changelog for the details. This version also includes many breaking changes as a result of standardizing behavior across the new generated services. Full details on migration from previous versions can be found here.

Debug

HTTP requests can be logged by adding a logging.properties file to your classpath.

handlers=java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level=FINE
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
java.util.logging.SimpleFormatter.format=%1$tb %1$td, %1$tY %1$tl:%1$tM:%1$tS %1$Tp %2$s %4$s: %5$s%n
.level=SEVERE
# HTTP Logging - Basic
com.ibm.watson.developer_cloud.util.HttpLogging.level=INFO

The configuration above will log only the URL and query parameters for each request.

For example:

Mar 30, 2017 7:31:22 PM okhttp3.internal.platform.Platform log
INFO: --> POST https://gateway.watsonplatform.net/tradeoff-analytics/api/v1/dilemmas?generate_visualization=false http/1.1 (923-byte body)
Mar 30, 2017 7:31:22 PM okhttp3.internal.platform.Platform log
INFO: <-- 200 OK https://gateway.watsonplatform.net/tradeoff-analytics/api/v1/dilemmas?generate_visualization=false (104ms, unknown-length body)
Mar 30, 2017 7:31:23 PM okhttp3.internal.platform.Platform log
INFO: --> POST https://gateway.watsonplatform.net/tradeoff-analytics/api/v1/dilemmas?generate_visualization=true http/1.1 (12398-byte body)
Mar 30, 2017 7:31:35 PM okhttp3.internal.platform.Platform log
INFO: <-- 200 OK https://gateway.watsonplatform.net/tradeoff-analytics/api/v1/dilemmas?generate_visualization=true (12311ms, unknown-length body)

Warning: The logs generated by this logger when using the level FINE or ALL has the potential to leak sensitive information such as "Authorization" or "Cookie" headers and the contents of request and response bodies. This data should only be logged in a controlled way or in a non-production environment.

Build + test

To build and test the project you can use Gradle (version 1.x).

Gradle:

cd java-sdk
gradle jar  # build jar file (build/libs/watson-developer-cloud-6.4.0.jar)
gradle test # run tests
gradle check # performs quality checks on source files and generates reports
gradle testReport # run tests and generate the aggregated test report (build/reports/allTests)
gradle codeCoverageReport # run tests and generate the code coverage report (build/reports/jacoco)

Working with Eclipse and Intellij IDEA

If you want to work on the code in an IDE instead of a text editor you can easily create project files with gradle:

gradle idea     # Intellij IDEA
gradle eclipse  # Eclipse

Open source @ IBM

Find more open source projects on the IBM Github Page

License

This library is licensed under Apache 2.0. Full license text is available in LICENSE.

Contributing

See CONTRIBUTING.md.

Code of conduct

See CODE_OF_CONDUCT.md.

Other

If you are having difficulties using the APIs or you have a question about the IBM Watson Services, please ask a question on dW Answers or Stack Overflow.