Eltezam HRSD Mock

Incoming requests

0 in the last minute

Success

–

Failed

0 rejected · 0 errors

In progress

waiting on a delay

Today by hour

Success Rejected (INVALID) Error (FAILED)

By operation

Operation	Processor service	Total	Success	Rejected	Errors	Success rate	Last request

Today's requests (latest 200 shown; filters search the whole day)

Time	Operation	Employee ID	National / Iqama	Sub agency	Answer	Result	Rule	ms

Point EltezamProcessor at this mock

Set these properties for the processor (in the config server, or as environment variables), then restart it:

The processor's SOAP client downloads the WSDL from eltezam.url and sends every call to the address written inside it. If the processor reaches this mock on a different host than your browser does (for example inside Docker), set mock.public-url on the mock to the URL the processor uses.

Endpoints

WSDL
SOAP service
Rules API	`GET / PUT /api/config`
Stats API	`GET /api/stats` · `GET /api/requests` · `DELETE /api/stats`
Database	H2 console · JDBC URL `jdbc:h2:mem:eltezam-mock` · user `sa`, no password

Where the data lives

Rules and requests are kept in an embedded in-memory H2 database. Nothing is written to disk:

The dashboard covers today only. Requests from earlier days are deleted at midnight.
Only the latest calls keep their request and response XML. Older calls of the day keep just their summary.
Restarting the mock clears everything, including the rules, and the answer goes back to Success.

What each answer does in the processor

Answer	Recorded by EltezamProcessor as