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.3</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.3'
}

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.2</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.2'
}

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 Gateway

Download

Consider using a template instead. Read why.

kaazing-enterprise-gateway-5.7.4.tar.gz (Linux/Unix/Mac)

kaazing-enterprise-gateway-5.7.4.zip (Windows)

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.

Instead of downloading just Kaazing Gateway, try a template instead.

Each template includes the Gateway and contains a sample application.

You can run the application, see the source code to learn how it works, and experiment by modifying it.

Intended for developers, it's a quick way to accelerate your first application.

TemplateDescription
Simple Chat AppA simple customer-agent chat application

KWIC

Kaazing WebSocket Intercloud Connect

Getting started

KWIC creates a secure bridge between two machines where one machine is behind a firewall. Typically this might be an application in the cloud that wants to connect to a server on-premise, behind the firewall.

In order to get started, it's easiest to use two separate machines:

  • Designate one as the "cloud" instance, and the other as the "on-premise" instance.
  • Have terminal windows open to them side-by-side and follow the directions below.
  • They don't actually have to run in the cloud or on-premise, they can run anywhere, even the same environment. They are just named "cloud" and "on-premise" for clarity.

See the setup guide in the KWIC documentation for more detailed instructions. Or see the kwic.docker.tutorials repo on GitHub for reference template configurations.

  1. Download KWIC to the cloud machine and also to the on-premise machine.

  2. In side-by-side terminals, run the following command on each machine:

    Copy
    ./kwic.setup
  3. Once configured, start it by installing it as a service in the previous step, or running the following from the command line:

    Copy
    ./bin/kwic.start
  4. Now you can test end-to-end connectivity. See Verifying KWIC Deployment in the documentation for instructions on how to do that.

Copy
docker run --rm --name kwic -h example.com -p 8000:8000 kaazing/kwic