Run a Java Client with OAuth Bearer Token Login | Generic Events (Legacy) | Streaming API Developer Guide

Run a Java client that uses EMP Connector to subscribe to the channel with OAuth authentication.

Obtain an OAuth bearer access token for your Salesforce user. You supply this access token in the connector example.

See Set Up Authorization with OAuth 2.0. Also see Authorize Apps with OAuth.

Let’s run an example that uses OAuth bearer token login.

Get the EMP Connector project from GitHub. See Step 3: Download and Build the Project.
In the /src/main/java/com/salesforce/emp/connector/example folder, open the BearerTokenExample.java Java source file.
Run the BearerTokenExample class, and provide the following argument values.

Argument Value
username Username of the logged-in user.
password Password for the username (or logged-in user).
channel /u/notifications/ExampleUserChannel

Optionally, to receive different events, you can include a replay ID as the last argument. Valid values are:
- –1 — Get all new events sent after subscription. This option is the default.
- –2 — Get all new events sent after subscription and all past events within the retention window. Use -2 sparingly. If a large volume of event messages is stored, retrieving all event messages can slow performance.
- Specific number — Get all events that occurred after the event with the specified replay ID.

Argument	Value
username	Username of the logged-in user.
password	Password for the username (or logged-in user).
channel	`/u/notifications/ExampleUserChannel`

When you run this client app and generate notifications using the REST resource, the output will look something like:

1Subscribed: Subscription [/u/notifications/ExampleUserChannel:-1]
2Received:
3{payload=Broadcast message to all subscribers, event={createdDate=2016-12-13T00:57:36.020Z, replayId=1}}
4Received:
5{payload=Another message, event={createdDate=2016-12-13T00:58:16.591Z, replayId=2}}

In the next step, you learn how to generate notifications using REST.