This demo shows how to use both Service Administration and Service Monitoring interfaces which are provided by Admin Service.
The files in this demo are as described in Files and Directories.
The demo assumes that you have installed following components:
Mgmt-Services mgmt_services.jar on the server side mgmt_services_client.jar used by this demo (client side) Security-Providers security_providers.jar providing https server transport on the server side security_services_client.jar providing https client transport, which is used by this demo.
Here is a short description how the demo works:
First is used Service Administration interface to obtain all service instances which are known to SESJ runtime.
Then service endpoints for these service instances are determined.
Service monitoring interface is used to enable data throughput monitor on Admin Service.
Then the monitoring log is got from the server.
Finally is data throughput monitor removed.
Be sure that you've started SESJ.
You can use our build script.
Linux: ./run.sh make or ./runant.sh make Windows: run.bat make or runant.bat make
Run runant.sh (bat) script for more targets.
Linux: ./run.sh run_client <username> <password> or ./runant.sh run_client <username> <password> Windows: ./run.bat run_client <username> <password> or ./runant.bat run_client <username> <password>
![]() | Note |
---|---|
When SESJ is running in secure mode, Admin service is protected by HttpBasic authentication mechanism. Your credentials are sent to the server during HttpBasic handshake, so you should have installed SESJ's https transport. To be more tolerant, on https transport fail this demo uses http transport - which is UNSECURE! |
For authentication are used admin/changeit credentials (SESJ installation defaults). If you want to supply your credentials put them as demo's parameters.