![]() Always update to the latest service release.With the number of moving parts of the integration system, it is important to remember a few things when troubleshooting: The integration system has faulted and cannot recover.The integration is stopped in Integration Builder, in the Administration Console, or by the service shutting down.This is a timed integration that does not repeat.The integration may reach the stop state for a few reasons: In general, once the job is sent to the queue and the Print Scheduler sends a confirmation to the Integration Service that the job is done, the integration will return to a waiting state. Everything outside the purple Print Scheduler box is handled by the Integration Service. Once the trigger is detected, the integration gets to work, processing the data and sending it off to print. This could be a file, a record in a database, an email, something over a network, a time-based trigger, or the like. They start and wait for something to trigger them to work. You can have a maximum number of print engines equal to the number of cores in your CPU x 2. You do not need to open or close them yourself as the Print Scheduler service handles all of it for you. Are automatically closed by the Print Scheduler service if not used after 60 minutes.Will close documents if they are unused.Can process up to 5 documents at a time.Work to maintain print order (so serials and records do not get out of order on your label sheet).More will be opened if the integration load demands it Are started on demand by the Print Scheduler service.Print engines have the following properties by default Print engines are automatically started and stopped by the Print Scheduler service and are used to print the actual label. ![]() It will appear as bartend.exe on the list of running processes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |