Difference between revisions of "I2Rest Advanced Setup"
Pavel.lobko (talk | contribs) |
Pavel.lobko (talk | contribs) |
||
| Line 5: | Line 5: | ||
"gates": | "gates": | ||
{ | { | ||
| − | "main" : {"url":"http://i2rest.com:22088" | + | "main" : {"url":"http://i2rest.com:22088"}, |
| − | + | "management" : {"url":"http://192.168.0.233:8080"}, | |
| − | "management" : {"url":"http://192.168.0.233:8080" | + | "session" : {"url":"http://192.168.0.233:8888/session_gate"} |
| − | |||
| − | "session" : {"url":"http://192.168.0.233:8888/session_gate" | ||
| − | |||
}, | }, | ||
"session_systems": | "session_systems": | ||
Revision as of 13:46, 5 June 2020
Take a look on how the minimal i2Rest configuration might look like.
{
"gates":
{
"main" : {"url":"http://i2rest.com:22088"},
"management" : {"url":"http://192.168.0.233:8080"},
"session" : {"url":"http://192.168.0.233:8888/session_gate"}
},
"session_systems":
[
{"name": "*LOCAL", "submit":"SBMJOB JOB(I2RESTS) USER(${user}) CMD(CALL JPCML/I2REST PARM('-session' '-url' '${surl}' '-uid' '${uid}'
'-user' '${user}' '-init' 'ADDLIBLE JPCML' '-dcm_client_id' 'MYCLIENT')) INLLIBL(KAPBASELIB QGPL)"},
{"name": "*ANONYMOUS", "submit":"SBMJOB JOB(I2RESTA) USER(${user}) CMD(CALL JPCML/I2REST PARM('-session' '-url' '${surl}' '-uid' '${uid}'
'-user' '${user}' '-init' 'ADDLIBLE JPCML' '-dcm_client_id' 'MYCLIENT')) INLLIBL(KAPBASELIB QGPL)"},
],
}
According to I2Rest Configuration Object description just two i2Rest Configuration Object fields are mandotary: gates object and main, manager and session gates object. With only this two configured fields we already can get an access to I2Rest Server capabilities.
