3.4.6 Setting up JP1/AJS3 - Web Console
Linking with JP1/AJS3 - Web Console allows clients to get the job operation information file by using the jprwebcollect command of JP1/AJS3 - Print Option to let JP1/AJS3 - Print Option Manager collect job operation information via JP1/AJS3 - Manager.
The following figure shows an example of the system configuration for linkage with JP1/AJS3 - Web Console.
|
|
![[Figure]](GRAPHICS/ZU030310.GIF)
For the login information for JP1/AJS3 - Manager from which the information is collected, use the jprajsmkkey command to create the authentication information file. Create the authentication information file by executing the jprajsmkkey command before executing the jprwebcollect command.
Communication between JP1/AJS3 - Print Option and JP1/AJS3 - Web Console as well as JP1/AJS3 - Web Console and JP1/AJS3 - Manager can be encrypted.
For details on the communication settings between JP1/AJS3 - Web Console and JP1/AJS3 - Manager, see the manual of JP1/AJS3.
- Setting timeout period:
-
Set the timeout period to communication between JP1/AJS3 - Print Option and JP1/AJS3 - Web Console.
For details on the settings, see jprwebcollect (Windows).
- Cautionary note:
-
-
To use this function, the versions of JP1/AJS3 - Print Option, JP1/AJS3 - Print Option Manager, JP1/AJS3 - Manager, and JP1/AJS3 - Web Console must be all 12-50 or later.
-
The amount of memory the jprwebcollect command will use is the same value as the above size in each JP1/AJS3 - Print Option, JP1/AJS3 - Print Option Manager and JP1/AJS3 - Web Console. In cases where multi-user remote operation is enabled and the jprwebcollect commands are executed concurrently from more than one session, the required amount of memory space is given by multiplying the amount needed for a single process of the command by the number of execution.
-
The max number to execute the jprwebcollect command from JP1/AJS3 - Print Option from JP1/AJS3 - Web Console concurrently is 5.
-