merkalt:bartender_automation
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| merkalt:bartender_automation [2011/04/28 18:06] – created daruma | merkalt:bartender_automation [2011/04/29 13:04] (current) – daruma | ||
|---|---|---|---|
| Line 28: | Line 28: | ||
| __Documented Integration Possibilities__ | __Documented Integration Possibilities__ | ||
| - | In addition to operating “stand-alone, | + | In addition to operating “stand-alone, |
| **Command Line Interface Option** | **Command Line Interface Option** | ||
| Line 34: | Line 34: | ||
| **ActiveX Automation** | **ActiveX Automation** | ||
| - | \\ Taking advantage of the latest in Microsoft’s ActiveX integration technology, the Enterprise Edition can easily be controlled by other software programs. Numerous functions are available, | + | \\ Taking advantage of the latest in Microsoft’s ActiveX integration technology, the Enterprise Edition can easily be controlled by other software programs. Numerous functions are available, such as loading BarTender, specifying a label format, selecting data sources and specifying network printers. Your programs can also inquire about BarTender’s current status, |
| **“Trigger” Based Integrations** | **“Trigger” Based Integrations** | ||
| Line 51: | Line 51: | ||
| **E-mail Integration** | **E-mail Integration** | ||
| \\ As an alternative to file-based triggers and label data, Commander can also detect triggers and receive label data via e-mail. | \\ As an alternative to file-based triggers and label data, Commander can also detect triggers and receive label data via e-mail. | ||
| - | |||
| - | \\ In other words, in order to realize this automation task we need Enterprize edition of BarTender and Commander utility. It seems, required BarTender features are exist only in this software combination. | ||
| __Solution__ | __Solution__ | ||
| - | There will be needed | + | In order to realize this automation task we need Enterprize edition of BarTender and Commander utility. It seems, required BarTender features are exist only in this software combination. So the following things are required for this task implementation: |
| + | |||
| + | - Enterprize edition of BarTender and Commander utility. //It will be best to obtain Commander utility documentation for possibilities exploration at first (if possible).// | ||
| + | - Remote access to your Windows server with set up IIS and PHP + BarTender software (BarTender and Commander utility). | ||
| + | |||
| + | The specialy written web service (PHP based server) | ||
| - Once merkalt site sends preview generation request, service forms request (via command line or ActiveX Automation) to BarTender to create preview image. | - Once merkalt site sends preview generation request, service forms request (via command line or ActiveX Automation) to BarTender to create preview image. | ||
| Line 66: | Line 69: | ||
| But it is should be explored if Commander import file format allows to define the name of the printer depending on design properties. Also it should allow to define template name, image and text to be inserted into this template, etc. | But it is should be explored if Commander import file format allows to define the name of the printer depending on design properties. Also it should allow to define template name, image and text to be inserted into this template, etc. | ||
| + | |||
| + | __Used BarTender Templates__ | ||
| + | |||
| + | {{: | ||
merkalt/bartender_automation.1304013966.txt.gz · Last modified: (external edit)
