Download:
Client SDKs
NPM
npm install kaazing-enterprise-client
Bower
bower install kaazing-enterprise-client
CDN
<script src="//cdn.kaazing.com/releases/enterprise.javascript.client/4.2.0/WebSocket.js"></script>
<script src="//cdn.kaazing.com/releases/enterprise.javascript.client/4.2.0/AmqpClient.js"></script>
<script src="//cdn.kaazing.com/releases/enterprise.javascript.client/4.2.0/JmsClient.js"></script>
Maven
Maven dependency for Kaazing JMS Java Client (Hosted on Maven Central Repository)
<dependency>
<groupId>com.kaazing</groupId>
<artifactId>enterprise.java.client</artifactId>
<version>4.2.6</version>
</dependency>
Maven dependency for Kaazing WebSocket Java Client (Hosted on Maven Central Repository)
<dependency>
<groupId>org.kaazing</groupId>
<artifactId>gateway.client.java</artifactId>
<version>5.1.0.4</version>
</dependency>
Note: The version numbers in Maven Central Repository will be different than those here. Although the version numbers are different, it is still the same client.
Gradle
Kaazing JMS Java Client
dependencies {
...
compile 'com.kaazing:enterprise.java.client:4.2.6'
}
Kaazing WebSocket Java Client
dependencies {
...
compile 'org.kaazing:enterprise.java.client:5.1.0.4'
}
Maven
<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:
<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
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:
repositories {
mavenCentral()
maven {
url "https://repository.kaazing.com/maven/"
}
}
NuGet
Install-Package Kaazing.Enterprise
Download
Kaazing Gateway
Download
kaazing-enterprise-gateway-5.8.15.tar.gz (Linux/Unix/Mac)
kaazing-enterprise-gateway-5.8.15.zip (Windows)
Start the gateway:
./bin/gateway.start
Then use a browser and open http://localhost:8000
Other start commands
Start the gateway using the pre-packaged AMQP broker:
./bin/gateway.start --broker amqp
Start the gateway using the pre-packaged JMS broker:
./bin/gateway.start --broker jms
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.
Template | Description |
---|---|
Simple Chat App | A simple customer-agent chat application |
KWIC
Kaazing WebSocket Intercloud Connect
Download
Linux: | kwic-5.9.29-linux.tar.gz | 225 MB | |
Mac: | kwic-5.9.29-macos.tar.gz | 218 MB | |
Windows: | kwic-5.9.29-windows.zip | 227 MB |
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.
Download KWIC to the cloud machine and also to the on-premise machine.
In side-by-side terminals, run the following command on each machine:
Copy./kwic.setup
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
Now you can test end-to-end connectivity. See Verifying KWIC Deployment in the documentation for instructions on how to do that.
docker run --rm --name kwic -h example.com -p 8000:8000 kaazing/kwic