Ice Getting Started Guide

Integrate Ice rule engine in 5 minutes and start your visual business orchestration journey!

Prerequisites

Ice uses a Server + Client + Shared Storage architecture:

• Ice Server: Visual rule configuration management platform
• Ice Client: Rule execution SDK integrated into your business applications
• Shared Storage: Server and Client sync configurations through shared file directory

Requirements

• Docker: Recommended for Server deployment
• JDK: 1.8+ (JDK 17+ for SpringBoot 3.x)

Step 1: Deploy Ice Server

Option 1: Docker Deployment (Recommended)

# Pull and run
docker run -d --name ice-server \
  -p 8121:8121 \
  -v ./ice-data:/app/ice-data \
  waitmoon/ice-server:latest

Or use Docker Compose:

# docker-compose.yml
version: '3.8'
services:
  ice-server:
    image: waitmoon/ice-server:latest
    container_name: ice-server
    ports:
      - "8121:8121"
    volumes:
      - ./ice-data:/app/ice-data
    restart: unless-stopped

docker-compose up -d

Option 2: Manual Deployment

Download latest version: https://waitmoon.com/downloads/

# Extract and start
tar -xzvf ice-server-*.tar.gz
cd ice-server
sh ice.sh start

Access Management UI

After startup, visit: http://localhost:8121

Online demo: http://eg.waitmoon.com

Step 2: Integrate Ice Client SDK

Add Dependency

Configure Client

# application.yml
ice:
  app: 1                        # App ID, corresponds to Server config
  storage:
    path: ./ice-data            # Shared storage path (same as Server)
  scan: com.your.package        # Leaf node scan package

Non-SpringBoot Projects

import com.ice.core.client.IceFileClient;

// Create client
IceFileClient client = new IceFileClient(
    1,                    // app ID
    "./ice-data",         // shared storage path
    "com.your.package"    // leaf node scan package
);

// Start
client.start();
client.waitStarted();

// Destroy when done
client.destroy();

Step 3: Develop Leaf Nodes

Ice provides three types of leaf nodes:

Example: Amount Reward Node

@Data
@EqualsAndHashCode(callSuper = true)
public class AmountResult extends BaseLeafRoamResult {

    private String key;      // Configurable: user ID key
    private double value;    // Configurable: amount to send

    @Override
    protected boolean doRoamResult(IceRoam roam) {
        Integer uid = roam.getMulti(key);
        if (uid == null || value <= 0) {
            return false;
        }
        // Call business service to send amount
        return sendService.sendAmount(uid, value);
    }
}

Step 4: Configure and Execute Rules

1. Configure Rules in Server

Visit http://localhost:8121 to access the management UI:

1. Create an Application (App)
2. Create a new Rule (Ice)
3. Configure the node tree
4. Publish to make configuration effective

2. Execute in Business Code

// Create execution pack
IcePack pack = new IcePack();
pack.setIceId(1L);  // Rule ID

// Set business parameters
IceRoam roam = new IceRoam();
roam.put("uid", 12345);
roam.put("amount", 100.0);
pack.setRoam(roam);

// Execute rule
Ice.syncProcess(pack);

// Get execution result
Object result = roam.get("SEND_AMOUNT");

Storage Sharing Solutions

Local Development

# Server and Client use same path
ice:
  storage:
    path: ./ice-data

Docker Environment

# docker-compose.yml
services:
  ice-server:
    volumes:
      - ./ice-data:/app/ice-data

  your-app:
    volumes:
      - ./ice-data:/app/ice-data  # Same mount

Distributed Environment

Use NFS or cloud drives (AWS EFS, Azure Files, etc.) as shared storage.

Next Steps

• 📖 Detailed Documentation - Deep dive into node types and configuration
• 🐹 Go SDK Guide - Go language integration guide
• 🐍 Python SDK Guide - Python language integration guide
• 🏗️ Architecture Design - Understand Ice architecture
• 🎥 Video Tutorial - Configuration and development demo

FAQ

Client not loading configuration?

Check if ice.storage.path points to the same directory as Server.

Rule changes not taking effect?

Make sure you clicked "Publish" in Server. Configuration syncs to Client only after publishing.

More Questions

👉 FAQ