Introducing Kaazing's Named Developer Program

Get direct access to expert WebSocket developers

LEARN MORE

Client SDKs

NPM

Copy
npm install kaazing-enterprise-client

Bower

Copy
bower install kaazing-enterprise-client

CDN

Copy
                
                  <script src="//cdn.kaazing.com/releases/enterprise.javascript.client/4.1.0/WebSocket.js"></script>
                  <script src="//cdn.kaazing.com/releases/enterprise.javascript.client/4.1.0/AmqpClient.js"></script>
                  <script src="//cdn.kaazing.com/releases/enterprise.javascript.client/4.1.0/JmsClient.js"></script>
                
              

Maven

Copy
                <dependency>
  <groupId>com.kaazing</groupId>
  <artifactId>enterprise.java.client.all</artifactId>
  <version>4.1.0</version>
</dependency>
                
              

Adding the Maven repository to your settings

Edit your settings.xml or project file to include the following:

Copy
<profiles>
  <profile>
    <id>kaazing</id>
    <repositories>
      <repository>
        <id>kaazing-enterprise-repository</id>
        <name>kaazing-enterprise-repository</name>
        <url>https://repository.kaazing.com/maven/</url>
      </repository>
    </repositories>
    <activation>
      <activeByDefault>true</activeByDefault>
    </activation>
  </profile>
</profiles>

Gradle

Copy
dependencies {
  ...
  compile 'com.kaazing:enterprise.java.client.all:4.1.0'
}

Adding the Maven repository to your settings

Edit your build.gradle file to include the following:

Copy
repositories {
  mavenCentral()
    maven {
      url "https://repository.kaazing.com/maven/"
    }
}

Maven

Copy
                <dependency>
  <groupId>com.kaazing</groupId>
  <artifactId>enterprise.android.client.all</artifactId>
  <version>4.1.0</version>
</dependency>
                
              

Adding the Maven repository to your settings

Edit your settings.xml or project file to include the following:

Copy
<profiles>
  <profile>
    <id>kaazing</id>
    <repositories>
      <repository>
        <id>kaazing-enterprise-repository</id>
        <name>kaazing-enterprise-repository</name>
        <url>https://repository.kaazing.com/maven/</url>
      </repository>
    </repositories>
    <activation>
      <activeByDefault>true</activeByDefault>
    </activation>
  </profile>
</profiles>

Gradle

Copy
dependencies {
  ...
  compile 'com.kaazing:enterprise.android.client.all:4.1.0'
}

Adding the Maven repository to your settings

Edit your build.gradle file to include the following:

Copy
repositories {
  mavenCentral()
    maven {
      url "https://repository.kaazing.com/maven/"
    }
}

NuGet

Copy
Install-Package Kaazing.Enterprise

Kaazing WebSocket Gateway

Enterprise Edition

(Jump to Community Edition instead)

Start the gateway:

Copy
./bin/gateway.start

Then use a browser and open http://localhost:8000


Other start commands

Start the gateway using the pre-packaged AMQP broker:

Copy
./bin/gateway.start --broker amqp

Start the gateway using the pre-packaged JMS broker:

Copy
./bin/gateway.start --broker jms
Copy
docker run --rm --name kwg -h example.com -p 8000:8000 kaazing/enterprise-gateway

The hostname example.com needs to be resolvable from your browser. You can do this by adding an entry to your hosts file for example.com that points to your Docker host's IP address. For example, if you are using Docker Machine, you can get the IP address with this command: docker-machine ip.

You should then be able to connect to ws://example.com:8000/echo using the WebSocket.org echo test.

Kaazing WebSocket Gateway

Community Edition

(Jump to Enterprise Edition instead)

Start the gateway:

./bin/gateway.start

Then use a browser and open http://localhost:8000

docker run --rm --name kwg -h example.com -p 8000:8000 kaazing/gateway

The hostname example.com needs to be resolvable from your browser. You can do this by adding an entry to your hosts file for example.com that points to your Docker host's IP address. For example, if you are using Docker Machine, you can get the IP address with this command: docker-machine ip.

You should then be able to connect to ws://example.com:8000/echo using the WebSocket.org echo test.