BineanGateway
Application connectivity
The Java gateway sends binary commareas over a local socket in DEV or HTTP to iman in managed environments. It routes requests to configured endpoints without interpreting business logic.
← Back to BENOVA
Modern connectivity for existing Ingenium workloads
Keep the COBOL business logic. Modernize how applications connect and operate.
Binean Nova Base brings together an application gateway, a worker management service and local IPC to connect existing Ingenium programs through a controlled integration model — without requiring a business-logic rewrite first.
Managed-service path. DEV can also connect directly over a socket.
-
01
ApplicationBusiness request
-
02
BineanGatewayRequest routing
-
03
imanHTTP · worker management
-
04
ingipcLocal IPC
-
05
COBOL workerIngenium processing
Three components, clear boundaries
Separate application connectivity from worker lifecycle
Each component owns one layer of the request path. Base manages invocation and execution; business logic remains in the existing COBOL programs.
iman
Service and worker management
The Rust service accepts HTTP requests, queues them within configured bounds and assigns them to ready workers. Profiles group environment, pool, deadline and worker-launch settings.
ingipc
Local IPC
The Rust bridge exchanges data between local sockets and COBOL workers. Endpoint ownership helps recover stale sockets after an uncleanly stopped managed process.
Managed path: application → BineanGateway → iman over HTTP → ingipc/socket → COBOL worker. In DEV, the gateway can call a socket directly to keep the debugging loop simple.
Controlled operations
Bounded capacity, explicit failure behavior
Base focuses on worker dispatch and clear failure semantics. Limits must be configured and qualified against the actual workload.
A bounded worker pool
Maintain a minimum number of workers, grow within a configured maximum as demand rises, then ask excess idle workers to exit cleanly.
Readiness and execution deadlines
Workers that are not ready or exceed an execution deadline are removed from assignment; the pool is restored within its configured limits.
No automatic replay of ambiguous transactions
A timeout does not prove that a transaction rolled back. If the exchange outcome is uncertain, the system does not silently resend the request to another worker.
A direct debugging path
DEV can use a direct socket connection to set COBOL breakpoints without a management service timing out and killing the worker being debugged.
Each worker processes transactions serially. A larger pool does not mean overlapping transactions on the same worker.
Start with the environment
Choose a connection path, then qualify it before expanding
Keep the existing socket path for development and add iman as a management layer where worker coordination is needed.
Development and debugging
Gateway → socket → worker
Use a direct connection to debug a COBOL worker. This avoids managed worker lifecycle behavior interfering with a breakpoint.
Managed environments
Gateway → HTTP iman → worker pool
iman accepts binary requests, selects a ready worker and supervises the pool. Multiple iman endpoints can be configured at the gateway.
Create a dedicated profile
Configure the host, COBOL program, database, socket path, worker counts and timeouts for one environment.
Run a bounded pilot
Verify readiness, binary request/response behavior, timeout handling, access controls and service shutdown.
Measure before expanding
Test load, latency, recovery and operations with the target COBOL runtime, database and platform.
Current status
Initial implementations are in place; environment acceptance comes next
Existing documentation and tests describe technical contracts and behavior; they do not replace acceptance in each organization’s production environment.
Implemented in the project
- BineanGateway supports socket and binary HTTP transport to iman.
- iman includes a CLI, profiles, HTTP dispatcher and worker lifecycle management.
- ingipc provides local IPC and socket ownership management.
- Automated tests cover selected gateway and worker paths on Windows.
Validate before adoption
- Qualify real COBOL/database startup and the complete environment configuration.
- Validate Linux on the intended deployment platform.
- Measure performance, load, recovery and timeout budgets for the workload.
- Establish TLS, OS ACLs/permissions, packaging and production operations.
No throughput, high-availability or exactly-once processing guarantee is implied. Each deployment needs its own security, performance and operational acceptance.
Start with one profile and one bounded business flow.
Review the Ingenium environment, integration surface and acceptance criteria before deciding how to run a pilot.