Tigase HTTP API

Welcome to the Tigase HTTP API users guide. The HTTP API allows you to manage, configure, chat, and send commands to Tigase server using a simple, easy-to-use interface right from your browser! We will guide you through setup, running, and going through some features of the HTTP API.

Setup & Configuration

Tigase will by default start with the http servlet active and running.

Admin Guide

• 1. HTTP API component
  • 1.1. Tigase HTTP-API Release Notes
    • 1.1.1. Tigase HTTP-API 2.3.0 Release Notes
    • 1.1.2. Tigase HTTP-API 2.2.0 Release Notes
  • 1.2. Available modules
    • 1.2.1. Admin UI module
    • 1.2.2. Index module
    • 1.2.3. REST module
    • 1.2.4. Server status module
    • 1.2.5. Setup module
    • 1.2.6. Web UI module
    • 1.2.7. DNS Web Service module
    • 1.2.8. User Status Endpoint module
  • 1.3. Common module configuration
    • 1.3.1. Enabling/disabling module
    • 1.3.2. Context path
    • 1.3.3. List of virtual hosts
    • 1.3.4. Complex example
  • 1.4. Module specific configuration
    • 1.4.1. Rest Module
    • 1.4.2. DNS Web Service module
    • 1.4.3. Enabling password reset mechanism
  • 1.5. Admin UI Guide
    • 1.5.1. A Note about REST
    • 1.5.2. General overview of the UI
    • 1.5.3. Configuration
    • 1.5.4. Example Scripts
    • 1.5.5. Notifications
    • 1.5.6. Other
    • 1.5.7. Scripts
    • 1.5.8. Statistics
    • 1.5.9. Users
  • 1.6. Tigase Web Client
    • 1.6.1. Chat
    • 1.6.2. Discovery
    • 1.6.3. Management
• 2. HTTP File Upload component
  • 2.1. Enabling HTTP File Upload Component
  • 2.2. Metadata repository
    • 2.2.1. DummyFileUploadRepository
    • 2.2.2. JDBCFileUploadRepository
  • 2.3. Storage
    • 2.3.1. DirectoryStore
  • 2.4. Logic
    • 2.4.1. URI template format
  • 2.5. File upload expiration
  • 2.6. Examples
    • 2.6.1. Complex configuration example
    • 2.6.2. Example configuration for clustering with HA
  • 2.7. S3 support for HTTP File Upload
    • 2.7.1. Enabling storage in S3
• 3. HTTP Server
  • 3.1. Implementations
    • 3.1.1. Jetty HTTP Server (default)
    • 3.1.2. Embedded HTTP server (deprecated)
  • 3.2. Configuration Properties
    • 3.2.1. Additional properties of embedded HTTP server (deprecated)
  • 3.3. Examples
    • 3.3.1. HTTPS on port 8443 with SSL certificate for example.com
    • 3.3.2. Changing port from 8080 to 8081
    • 3.3.3. Usage of Jetty HTTP server as HTTP server

Development Guide

• Rest API
  • 1. REST API
    • 1.1. Scripting introduction
    • 1.2. Usage Examples
    • 1.3. BOSH HTTP Pre-Binding