Caché System Administration Guide - InterSystems Documentation
Caché System Administration Guide - InterSystems Documentation
Caché System Administration Guide - InterSystems Documentation
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Identifying Users<br />
is considered a “user request.” Information about implementing a SOAP session is available in SOAP<br />
Session Management in Using SOAP and Web Services with <strong>Caché</strong>.<br />
Processes started by the user start routine (^%ZSTART or the older ^ZSTU) are another special case.<br />
The process running ^%ZSTART has no parent process. Therefore, a login is performed for the user<br />
ID, User Startup, before ^%ZSTART is called. Processes started by the Job command from<br />
^%ZSTART have this user ID. If you prefer, call $<strong>System</strong>.License.Login(UserId) from ^%ZSTART<br />
to change the user ID. This procedure means that ^%ZSTART can start as many as one less than<br />
maxconn background processes and only consume one license. If, according to the license terms and<br />
conditions, these processes should have a separate license (for example if they drive a piece of laboratory<br />
equipment that requires a separate license), you are required to call $<strong>System</strong>.License.Login(UserId)<br />
to obtain a license for an appropriate user ID.<br />
Finally, it is important to understand that <strong>Caché</strong> does not distinguish background processes and count<br />
them differently. If a user process starts another process, that child process counts as one more against<br />
the user’s overall maximum limit of processes.<br />
<strong>Caché</strong> <strong>System</strong> <strong>Administration</strong> <strong>Guide</strong> 63