StreamServe Design Center GUI Reference

Transcription

1 StreamServe Design Center GUI Reference Reference Guide SP2 Rev A

2 StreamServe Design Center GUI Reference Reference Guide SP2 Rev A 2007 StreamServe, Inc. StreamServe is a trademark of StreamServe, Inc. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of StreamServe, Inc. Information in this document is subject to change without notice. StreamServe Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. All registered names, product names and trademarks of other companies mentioned in this documentation are used for identification purposes only and are acknowledged as property of the respective company. Companies, names and data used in examples in this document are fictitious unless otherwise noted. StreamServe, Inc. offers no guarantees and assumes no responsibility or liability of any type with respect to third party products and services, including any liability resulting from incompatibility between the third party products and services and the products and services offered by StreamServe, Inc. By using StreamServe and the third party products mentioned in this document, you agree that you will not hold StreamServe, Inc. responsible or liable with respect to the third party products and services or seek to do so. The trademarks, logos, and service marks in this document are the property of StreamServe, Inc. or other third parties. You are not permitted to use the marks without the prior written consent of StreamServe, Inc. or the third party that owns the marks. Use of the StreamServe product with third party products not mentioned in this document is entirely at your own risk, also as regards the StreamServe products. StreamServe Web Site

3 3 Contents Main window...7 Menus and menu commands...7 File menu... 7 Edit menu... 8 Tools menu... 8 Platform menu... 9 Message menu... 9 Runtime menu... 9 Resources menu Sub-windows and dialog boxes...11 Customize dialog box Design Center Settings dialog box Colors dialog box View Information window Search Results window Project window...15 Project Settings dialog box...17 Unpack Project dialog box Input Connector Settings dialog box...19 Connector Settings tab ADO input connector settings Device input connector settings Directory input connector settings IN input connector settings Exchange input connector settings FTP input connector settings HTTP(S) input connector settings HTTP(S) Poll input connector settings Internal input connector settings Java input connector settings Java RMI input connector settings JMS Queue input connector settings JMS Subscribe input connector settings MSMQ input connector settings Named Pipe input connector settings Netware Bindery input connector settings Netware NDS input connector settings Serial input connector settings Service Channel (COM) input connector settings Service Channel (HTTP) input connector settings SMS Provider input connector settings Status Messenger input connector settings... 39

4 4 StdIn input connector settings TCP/IP input connector settings WebSphere MQ input connector settings HTTP Access tab Queue Settings tab Filter Chain Settings tab General Settings tab Output Connector Settings dialog box...47 Codepage Settings tab Device Driver Settings tab Symbol Set tab Filter Chain Settings tab Queue Settings tab Connector Settings tab ADO output connector settings Command output connector settings Dazel output connector settings Exchange output connector settings Fax Connect output connector settings File output connector settings FTP output connector settings Generic Archive output connector settings HTML output connector settings HTTP Response output connector settings HTTP(S) Submit output connector settings Internal output connector settings IXOS Archive in R3 output connector settings Java output connector settings Java Response output connector settings Java RMI output connector settings JMS Publish output connector settings JMS Queue output connector settings JMS Response output connector settings Job Resource output connector settings Lotus Notes output connector settings MAPI output connector settings MAPI for MailOUT output connector settings MSMQ output connector settings Netware Bindery output connector settings Netware NDS output connector settings Null Connector output connector settings Pipe output connector settings RePRINT output connector settings Service Channel Response (COM) output connector settings Service Channel Response (HTTP) output connector settings Service Channel Submit (COM) output connector settings Service Channel Submit (HTTP) output connector settings SMS output connector settings SMS Provider output connector settings SMTP output connector settings SMTP (MIME) output connector settings SMTP (MIME) for MailOUT output connector settings... 86

5 5 SNMP trap output connector settings Spool output connector settings StdOut output connector settings StreamServe External Viewer output connector settings TCP/IP output connector settings TFS output connector settings TFS for MailOUT output connector settings Topcall output connector settings WebSphere MQ output connector settings WinFaxAdapter output connector settings XTrade output connector settings General Settings tab Configure Platform dialog box...96 Job ID tab Dynamic Resources tab Default Repository tab Job Status tab Recording Mode tab Log File tab Custom tab Gateway tab Service Broker tab Notifications tab File Cache tab Configure Platform Export dialog box Paths tab Arguments tab Manage Queues dialog box Scheduler Configuration dialog box Message window Event Settings dialog box Agent Settings tab Event Order tab Runtime configuration window Runtime Input Connector Settings dialog box Input Analyzer tab General tab Runtime Event Settings dialog box General tab Code Page tab Runtime Process Settings dialog box Rule tab General tab Attach Process tab RePRINT tab Connector Selection Method dialog box...127

6 6 Edit Output Connector Settings dialog box Runtime Output dialog box Device Driver Settings tab Device symbol set tab Document Trigger tab Connector tab Process Sort Definition tab Sort Definition dialog box Resource set window Resource Folder Settings dialog box Resource Folder Export Settings dialog box Resource selection browser Filter Chain editor Input connector filters Bypass Filter Codepage Filter Decompression Filter External Filter File Filter Internal Filter Job Filter Output connector filters Compression filter

7 7 Main window Menus and menu commands File menu New Open Close Save Save All Save As Open Project Save Project Close Project Create new Platform, Message, Runtime configuration, resource set, or Project. Open a Platform, Message, Runtime configuration, or resource set. Close the active window (Platform, Message, Runtime configuration, or resource set). Save the active window. Save all open windows. Also saves the open Project and everything within. Save active window with a new name. Open a Project. Save the active Project, including all Platforms etc. Close the Project. Obtain Write Lock Lock the selected component in the Project. Write lock = only you can edit the component. Release Write Lock Reload Component Add to Project Remove from Project Pack Project Unpack Project Recent Files Unlock the selected component in the Project. Revert to the latest saved version of the selected component in the Project. Add a Platform, Message, Runtime configuration, or resource set to the Project. Select an item in the Project and remove it from the Project. Pack the Project and save it as a package file. Unpack a packed Project. Open recent files.

8 8 Menus and menu commands Main window Recent Projects Exit Open recent Projects. Exit the Design Center. Edit menu Find Open Close Script Go to source Add Resource Set Remove Resource Set Settings File Properties Search and find. Select an Event or Process and open the corresponding tool. Select an Event or Process and close the corresponding tool. Add script to selected item. Select an item in the Runtime configuration view, and go to the corresponding Message or Platform view. For example, if you select an Event in the Runtime configuration, the corresponding Message will be opened, with the Event high-lighted. Add resource set to selected item. Remove resource set from selected item. Edit settings for the selected item. Display the path to the selected object. Tools menu Customize Design Center Settings Select Color Scheme Select Note Font Select Note Alignment Edit toolbar, toolbar buttons etc. See Customize dialog box on page 11. Edit default Design Center settings. See Design Center Settings dialog box on page 11. Select a color scheme for the Design Center GUI. See Colors dialog box on page 12. Select font for the notes you enter in the View Information window. Select alignment for the notes you enter in the View Information window.

9 Menus and menu commands 9 Main window Export wizard Export now Autocreate Message Edit Project Template Information Export the Project using the export wizard. Export the Project directly. Auto-create a Message based on an SXD file (Event) and a PLT file (Process). Browse to a Design Center template or package and edit the category and description. Platform menu This menu is related to the active Platform view. If no Platform view is active, this menu is not available. New input connector New output connector Manage Queues Configure Platform Configure Export Add an input connector. Add an output connector. Open the Manage Queues dialog box. Open the Configure Platform dialog box. Open the Configure Platform Export dialog box. Message menu This menu is related to the active Message view. If no Message view is active, this menu is not available. Add Event Add Process Add an Event. Add a Process. Runtime menu This menu is related to the active Runtime configuration view. If no Runtime configuration view is active, this menu is not available. Edit Platform New Job Add Message New Postprocessor Open the corresponding Platform view. Create a new job. Add a Message to the selected job. Create a new Post-processor.

10 10 Menus and menu commands Main window Add Process Link Collapse all Jobs & Post-processors Expand all Jobs & Post-processors Export Runtime wizard Export Runtime now Extract documentation Add a process link to the Post-processor. Show the Job containers and Post-processors as named boxes. Hide all connection lines. Show all connection lines from all Job containers and Post-processors. Export the Project using the export wizard. Export the Project directly. Create a Word document with details about the Runtime configuration (components, settings, notes, etc.). Resources menu This menu is related to the active resource set view. If no resource set view is active, this menu is not available. New Resource Add Resource Import Start Editor Stop Editor Update from origin Extract to file Create a new resource file using a resource editor. The resource file is automatically linked to the resource set. Link an existing resource file to the resource set. Create a new resource file by importing a source file. The resource file is automatically linked to the resource set. Edit the selected resource file. Stop and close the editor for the selected resource file. If the resource file is created by importing a source file, you can edit the source file and use Update from origin to update the resource file. Extract the embedded file in the selected resource file.

11 Sub-windows and dialog boxes 11 Main window Sub-windows and dialog boxes Customize dialog box Customizing the toolbars in the main window. Toolbars tab Used for enabling/disabling toolbars and tooltips, and for modifying the appearance of the toolbars. Command tab Used for displaying information about the toolbar buttons. Design Center Settings dialog box Default application settings and product registration. Application settings Remember window layout when closing Design Center Default code page Use Platform, Message, and Runtime identifier colors in views Enable wizard window at startup Highlight Runtime links for selected items Inherit resource sets Add new views to active project Add new view dependencies to active project Open views as they were the last time you closed the Design Center. Select a default code page for all objects in the Design Center. For example, when you add a code page filter to a filter chain, the selected code page will be used by default. Enable identifier colors (bar at the bottom of the view). Display the shortcut window (Open Project, etc.) when you launch the Design Center. In the Runtime configuration, high-light all lines connected to a selected Job container, Message, Process, or connector. Inherit the resource sets connected to added objects. For example, let the Runtime configuration inherit the resource sets connected to the added Messages. Add new views, created using File > New, to the active Project. Add dependencies for new views, created using File > New, to the active Project.

12 12 Sub-windows and dialog boxes Main window Application settings Try to obtain write lock when opening views Always obtain write lock for all components when opening Project Template location If selected, the Design Center will attempt to lock the view so it can be edited. Write lock = only you can edit the view. Set components to read-only or editable when opening the views. Write lock = only you can edit the view. The directory that contains the Design Center Project templates. Colors dialog box Selecting a color scheme for the Design Center GUI. View Information window Viewing information related to the active Platform, Message, Runtime Configuration, or resource set view. Active view and Selected item Displays the active view, and the selected item in the view. Note Used for adding and editing notes related to the selected item.

13 Sub-windows and dialog boxes 13 Main window Dependencies Shows dependencies for the active view. You can right-click an item and select a menu command. Menu commands Set as Default Resource Set Activate Add Resource Sets Remove Resource Set Set as default resource set for the active view. Activate the corresponding view. Add resource sets to the active view. Remove the selected resource set from the active view. Search Results window Displaying search results (Edit > Find). Double-click an item to go to the corresponding item. Columns View Location Dependency Description The view (Platform, etc.) where the item was found. The location of the item. N/A Description of the item

14 14 Sub-windows and dialog boxes Main window

15 15 Project window Structuring and managing components in a StreamServe Project. The Project tree contains the top node, representing the Project, and separate folders for Platforms, Messages, Runtime configuration, and resource sets. Shortcut menu commands New Open Project Recent Projects Save Project Save As Close Project Pack Project Unpack Project Obtain Write Lock Release Write Lock Reload Component Add to Project Export wizard Export now Rename Create new Platform, Message, Runtime configuration, resource set, or Project. Open a Project. Open recent Projects. Save the active Project, including all Platforms etc. Save the Project with a new name. Close the Project. Pack the Project and save it as a package file. Unpack a packed Project. Lock the selected component. Write lock = only you can edit the component. Unlock the selected component. Revert to the latest saved version of the selected component. Add a Platform, Message, Runtime configuration, or resource set to the Project. Export the Project using the export wizard. Export the Project directly. Rename the selected component.

16 16 Project window Shortcut menu commands Settings File Properties Remove from Project Open the Project Settings dialog box and edit the Project settings. Display the path to the selected object. Remove the selected component from the Project. Open/Activate View Open the view containing the selected component.

17 Project Settings dialog box 17 Project window Project Settings dialog box Modifying Project settings. Project settings Project name Default code page Default Resource Set Project folder/ directory The name of the Project. The default code page for all items within the Project. Overrides the default code page defined in the Design Center Settings dialog box. The name of the default resource set. The path to the folder where to save your Project files.

18 18 Unpack Project dialog box Project window Unpack Project dialog box Simple mode Unpacking and storing all unpacked files in a specified folder. Options Project Location The path to the folder where to store the Project files. Advanced mode Selecting which files to unpack, and where to store the unpacked files. Options Components in package Location for selected components Lists all components that can be unpacked. Select the components to unpack. The path to the folder where to store the selected components.

19 19 Input Connector Settings dialog box Configuring input connectors. Connector icon Connector Settings tab HTTP Access tab Queue icon Queue Settings tab Filter Chain icon Filter Chain Settings tab General icon General Settings tab Connector Settings tab Configuring input connectors. Settings Connector Connector specific Type of input connector. Connector specific settings.

20 20 Input Connector Settings dialog box Settings Time-out Polling interval The maximum time (seconds) the connector will wait for input before it shuts down the connection. The time-out counter starts over again as soon as the connector receives input. If, when, and how often to poll the data source for information. ADO input connector settings Extracting data from ODBC or OLE DB enabled database tables. Windows. DataSource CustomData Source UserName Password SQLCommand EventName Mode The ODBC data source to connect to. A custom data source to connect to, for example an external ODBC or OLE DB data source. This will override the DataSource specified above. For example: driver={sql Server}; server=my_server;uid=;pwd=;database=my_db; User name for accessing the data source. Overrides any other user names specified for the data source. Password for accessing the data source. Overrides any other passwords specified for the data source. SQL command to be carried out on the data source. For example: select * from my_table The Event that receives input from this connector. Move (with delete) Delete the record from the database table after reading. Copy (no delete) Copy the record from the database.

21 Input Connector Settings dialog box 21 RowLevel Create SXD Objects as blocks Each ADO record will be submitted as a block, one block per record. Objects as events Each ADO record will be submitted as an Event, one Event per record. Objects as jobs Each ADO record will be submitted as a job, one job per record. If you use the Communication Server to create an SXD file, enter a name and a path for where you want to save this SXD file. Device input connector settings Scanning a UNIX FIFO for incoming jobs. A FIFO is a First-In-First-Out queue. UNIX. Device File path to the FIFO, for example:./fifos/my_fifo Directory input connector settings Retrieving files from a named directory. The source application writes data to this directory, and the Communication Server retrieves the data. Windows and UNIX. Match criterion The path to the directory, for example: scandir/*.txt Use an absolute path, or a path relative to the export directory.

22 22 Input Connector Settings dialog box Sort by How to sort files when reading from the directory. Two or more files with the same value (for example the same file extension) will be sorted by file name in ascending alphabetical order. Load balancing: networksafe: Several Directory connectors can scan the same directory for the same type of files. All involved Communication Servers must be located on the same machine. Match Criterion must be identical for all connectors. The Communication Server may go down if the directory, from which the files are retrieved, is located on a remote machine, and the network goes down. To avoid this you can enter networksafe in the connector s Custom settings field. IN input connector settings Retrieving input sent via . Windows and UNIX. Mailbox type Port Mail server name Mail folder User name Password Read mail text Read attachment file The type of mailbox on the mail server. The port the Communication Server will use to communicate with the mail server. The mail server s IP address or host name. Applicable only to IMAP. Mail folder to scan for input. Leave this empty if you want to select the Inbox. User name for accessing the mailbox. If several Communication Server instances retrieve input from the same mail server, each instance must use a unique user name. Password for accessing the mailbox. Select whether or not to process the body. Specify the attachments to be processed by the Communication Server. See Example 1 below.

23 Input Connector Settings dialog box 23 Mail read filter Read filter parameters Delete mail Mail delete filter Delete filter parameters Save attachment Attachment directory Read All Retrieve all s in the mailbox. Advanced Use the read filter parameters below to specify which s to retrieve. You can use wildcards. See Example 2 below. From Retrieve s with specific From addresses. To Retrieve s with specific To addresses. Cc Retrieve s with specific Cc addresses. Date Use a timeframe to specify which s to retrieve. The timeframe corresponds to the date and time the was received. Use YYYY-MM-DD as format. Subject Retrieve s with specific subjects. Reply to Retrieve s with specific Reply to addresses. Signed Select to reject unsigned s. Encrypted Select to reject un-encrypted s. Delete s from the mailbox after they have been retrieved by the Communication Server. Delete Processed Delete all s that have been retrieved and processed. Delete all Delete all s that have been retrieved. Advanced Use the delete filter parameters below to specify which s to delete. You can use wildcards. See Example 3 below. Delete From Delete s with specific From addresses. Delete To Delete s with specific To addresses. Delete Cc Delete s with specific Cc addresses. Delete Date Use a timeframe to specify which s to delete. The timeframe corresponds to the date and time the was received. Use YYYY-MM-DD as format. Delete Subject Delete s with specific subjects. Delete Reply to Delete s with specific Reply to addresses Save attachments to disk. The directory where to save attachments.

24 24 Input Connector Settings dialog box Example 1 Specifying whether to read attachments An contains the attachments INVOICE_101.xml, INVOICE_101.txt and COPY_101.xml. If Read Attachment File is *.xml, the attachments INVOICE_101.xml and COPY_101.xml will be retrieved by the Communication Server. If Read Attachment File is INVOICE*.xml, only INVOICE_101.xml will be retrieved by the Communication Server. Example 2 Specifying which s to retrieve Date: ** s dated January 2002 will be retrieved. Example 3 Specifying which s to delete Delete Date: ** s dated January 2002 will be deleted. GetConnectorValue attributes You can use the scripting function GetConnectorValue to fetch IN attributes. Attribute From To Cc Reply To Subject Date Body encoding Body type Attachment encoding Attachment type GetConnectorValue("<attribute>") GetConnectorValue("From") GetConnectorValue("To") GetConnectorValue("Cc") GetConnectorValue("Reply To") GetConnectorValue("Subject") GetConnectorValue("Date") GetConnectorValue("Encoding") GetConnectorValue("Type") GetConnectorValue("AttEncoding<n>") where <n> is the attachment number. GetConnectorValue("AttType<n>") where <n> is the attachment number.

25 Input Connector Settings dialog box 25 Attribute AttCount GetConnectorValue("<attribute>") GetConnectorValue("AttCount") Returns the number of attachments in the current that have been saved to disk. Exchange input connector settings Reading objects in Microsoft Exchange Server folders. For example, read s and attachments from Microsoft Outlook Public Folders. Windows. Server MailBox Folder EventName Mode DataType RowLevel The Microsoft Exchange Server. For example: laxnt04 The user account on the Microsoft Exchange Server. For example: streamserve The folder to be read. For example: Mailbox - Brown, Jane\Inbox The folder name can be language sensitive. In that case, you must write the folder name on the local language. For example: Postlåda - Brown, Jane\Inkorg The Event that receives input from this connector. Move (with delete) Deletes the object from the Microsoft Exchange Server after reading it. Copy (no delete) Copies the object from the Microsoft Exchange Server. CDOObject All fields in a retrieved object will be entered as fields in a StreamServe XML-data structure. File The first attachment of each object will be streamed through the Communication Server. Objects as blocks Each object will be sent to the Communication Server as a block, one block per object. Objects as events Each object will be sent to the Communication Server as an Event, one Event per object. Objects as jobs Each object will be sent to the Communication Server as a job, one job per object.

26 26 Input Connector Settings dialog box Create SXD If you want the Communication Server to create an SXD file, enter a name and a path for where you want to save this SXD file. FTP input connector settings Comments: Retrieving files from an FTP server. After a file is retrieved, it is deleted from the FTP server. If you need more than one connector (input or output) per user account, this must be defined on the FTP server. On the FTP server, the number of concurrent connections must be equal to, or higher than, the number of FTP connectors (input and output) set up for a user account. Windows and UNIX. Host Port User name Password Remote path The FTP server, for example rtu.baldwin.com The port on the FTP server. The user name for accessing the FTP server. The password for accessing the FTP server. The directory to be accessed on the FTP server. If you leave this blank, the root directory will be set as remote path. For example: /invoices/pdfout/area2 Whether to use slash or back-slash is determined by the FTP server software. File match criterion The match criterion for the files to be retrieved, for example *.pdf

27 Input Connector Settings dialog box 27 Passive mode Transfer mode Select whether or not to enable Passive Mode. FTP in Passive mode is used when communicating through firewalls. It opens a control connection to the FTP server, tells the FTP server to expect a control connection and a second connection. Then it opens the data connection to the FTP server itself on a randomly chosen highnumbered port. Note: This works with most firewalls unless the firewall restricts outgoing connections on high-numbered ports. ASCII ASCII, Type A, transfer method. Control and formatting data is converted to local equivalents. Binary FTP Image, Type I, transfer method. The file is transferred without any changes. HTTP(S) input connector settings Enabling the Communication Server to function as an HTTP server. Windows and UNIX. Security configuration Version SSL version Address HTTPS only. The security configuration to connect to this connector. The security configuration must be included in a resource set connected to the Platform. See the Encryption and authentication documentation for more information. The HTTP version to use. Auto means that the version is determined by the client. HTTPS only. The SSL version to use. Server and clients must use the same SSL version. An alternative network address for this Communication Server if you do not want to use the default network address for the workstation. For example, the IP address to a specific network card.

28 28 Input Connector Settings dialog box Port Input threads Idle time-out Time-out Response time-out Authentication Publish directory The port this connector listens to for HTTP requests. Several HTTP(S) connectors cannot share the same port. You must use a unique port for each connector. The maximum number of concurrent connections. When all connections are busy, and a new client tries to connect to the Communication Server, the connection may fail. Note: Increasing the number can decrease performance. This time-out (milliseconds) is applied when the Communication Server has finished processing a request, and no more data related to the request will be received or sent. It specifies the maximum time the connection will remain open, and enables the client to send a new request without having to set up a new connection. This time-out (milliseconds) is applied when the Communication Server sends or receives data, and its purpose is to close dead connections. If no data is sent or received during the time specified, the connection will be closed. This time-out (milliseconds) is applied when the Communication Server has received all data from the client. It specifies the maximum time the client is expected to wait for a response. The client can use an HTTP header field to override this time-out. To enable this, you must use the keyword HTTPResponseTimeOut. With this keyword you can also specify a file to return to the client when the time-out occurs. See Custom keywords below. If the client does not expect any response from the Communication Server, you should set this time-out to 0. In this case the Communication Server will immediately return 200 OK, and optionally a file using HTTPResponseTimeOut, to inform the client that the request has succeeded. None Do not use authentication. Basic Send authentication parameters as clear text. This is the only scheme supported in HTTP/1.0. Digest Send authentication parameters as a checksum over the network. Requires HTTP/1.1. See RFC The root directory for stored files.

29 Input Connector Settings dialog box 29 Publish extension file Job resource URI An alias table where you associate file formats to content-types (RFC 2045). This table must be available in a Resource Set connected to the Platform. The Communication Server accepts html, htm, gif, jpg, txt, zip by default. To use other formats, you must specify a publish extension file. The Job resource URI identifies an output file stored via a Job Resource output connector. For example: /jr You can configure the Communication Server to automatically return processed output to the client. In most cases you will use an HTTP Response output connector to handle the response. There are also scenarios where a client expects the response, for example a pdf file, to be presented in a web browser via an ActiveX plug-in. To make this work, the response must be temporarily stored using a Job Resource output connector. Custom keywords This table describes a number of keywords that you can add to the Custom tab. Keyword HTTPExtJobIdField "ID_name"; HTTPMaxContentLength limit; Description Retrieves the external ID from an application that sends input to the Communication Server. The application that sends the input must include the external ID as HTTP header information (ID_name:ID_value). Limits the size (in bytes) of the body in an HTTP request. If a request contains a body that exceeds this limit, an error response will be returned.

30 30 Input Connector Settings dialog box Keyword HTTPResponseTimeOut "timeout" "path" "custom" END; Description Specifies what the Communication Server should do when a response time-out occurs. timeout: A time-out set by the client to override the response time-out. For example, the client header field x-timeout:60000 sets the response time-out to one minute. To enable the client to set the response time-out, you must use HTTPResponseTimeOut: HTTPResponseTimeOut "x-timeout" "" "" END; Leave this argument empty if you do not want to allow clients to set the response time-out. path: A file with information to send in the response when the timeout occurs. For example: HTTPResponseTimeOut "" "/Messages/timeout.txt" "" END; custom: Custom fields (name:value) added to the response header. For example: HTTPResponseTimeOut "" "timeout.txt" "contenttype:text/plain" END; You can separate several name:value pairs with <0d><0a>. HTTP(S) Poll input connector settings Enabling the Communication Server to function as an HTTP client that polls an HTTP server. Windows and UNIX. CA certificate HTTPS only. A CA root certificate that confirms the identity of the SSL server. The certificate must be included in a resource set connected to the Platform.

31 Input Connector Settings dialog box 31 Method URL Content-type File to POST Time-out Version SSL Version Specify the method the client will use when polling the HTTP server. HEAD Requests a HEAD header from the HTTP server. If the Last-Modified entity-header field has changed, the Communication Server will fetch and process the data. If there is no Last-Modified field in the header, the connector will switch to the GET method instead. If the Last-Modified field is not updated correctly this method will fail. GET Downloads the data once during each poll interval, and calculates a checksum to see if the data has been updated. The Communication Server will process the data only if the checksum has changed. POST POSTs a file to the HTTP server, downloads the response and calculates a checksum. The Communication Server will process the data only if the checksum has changed. The URL to the HTTP server. If the Method is POST The content-type of the file to be posted. If the Method is HEAD or GET The media types the client accepts in the response. For example: text/*, text/xml, text/xml;level=1, */* All formats will be accepted if this field is empty. The file to be posted. The maximum time (milliseconds) to wait before aborting a transfer. The HTTP version to use. HTTPS only. The SSL version to use. Server and clients must use the same SSL version.

32 32 Input Connector Settings dialog box Authentication Realm User name Password Cache file None Do not use authentication. Basic Send authentication parameters as clear text. This is the only scheme supported in HTTP/1.0. Digest Send authentication parameters as a checksum over the network. Requires HTTP/1.1. Only if authentication is required. The realm. Only if authentication is required. User name to access the realm. Only if authentication is required. Password to access the realm. Cache file that stores communication checksums between Communication Server start/stop. Internal input connector settings Comment: Enabling the Communication Server to pass on data internally. For example to loop back output for further processing. If you have an internal loop via an Internal input connector and an Internal output connector, you must specify a UTF- 8 code page for both connectors. Windows and UNIX. There are no properties for this type of connector. Java input connector settings Custom Java input connector. See the StreamServe EIF SDK documentation. Windows and UNIX.

33 Input Connector Settings dialog box 33 Java RMI input connector settings Custom Java input connector. See the StreamServe EIF SDK documentation. Windows and UNIX. JMS Queue input connector settings Enabling the Communication Server to receive messages from a named queue in a point-to-point messaging system. For more information about JMS, see Windows and UNIX. Context Queue Factory User Name Password Queue Selector The JNDI context. If you leave this empty, the initial context will be used. The JNDI lookup name for the queue connection factory. This setting is mandatory. A JMS client uses a connection factory to create a connection to the JMS provider. User name to access the JMS provider. Password to access the JMS provider. The JNDI lookup name for the queue. This setting is mandatory. If the JMS client needs to filter the messages it receives, you can use a message selector. A message selector is a string that contains an expression. The syntax of the expression is based on a subset of the SQL92 conditional expression syntax. For example: Type = Invoice OR Type = Order will select messages where Type is set to either Invoice or Order.

34 34 Input Connector Settings dialog box JMS Subscribe input connector settings Enabling the Communication Server to receive messages from a named topic in a publish-subscribe messaging system. For more information about JMS, see Windows and UNIX. Context Topic Factory User Name Password Topic Selector Subscriber Id Unsubscribe on close The JNDI context. If you leave this empty, the initial context will be used. The JNDI lookup name for the topic connection factory. This setting is mandatory. A JMS client uses a connection factory to create a connection to the JMS provider. User name to access the JMS provider. Password to access the JMS provider. The JNDI lookup name for the topic. This setting is mandatory. If the JMS client needs to filter the messages it receives, you can use a message selector. A message selector is a string that contains an expression. The syntax of the expression is based on a subset of the SQL92 conditional expression syntax. For example: Type = Invoice OR Type = Order will select messages where Type is set to either Invoice or Order. Identifies this particular subscription service. Enables the JMS provider to postpone sending messages to this subscriber if the connection between the Communication Server and the JMS provider is lost. No messages will be lost during the time the connection is down. If you have specified a subscriber ID, you can select whether or not to unsubscribe when the Communication Server is shut down.

35 Input Connector Settings dialog box 35 MSMQ input connector settings Comments: Private and public message queues: Enabling and integrating Communication Server capabilities in Microsoft message queuing environments. If the messages that are sent to the connector are segmented, the application sending the messages must synchronize the messages as follows: The first message in the sequence must have the appspecific property set to the number of messages that will arrive in this sequence of segmented messages (the first message is excluded). The following messages must have this number decreased by one and the last message in the sequence must have the appspecific property set to 0. All messages, except the first one, must have their correlation ID property set to the message ID of the first message. Public message queues are published in the Active Directory. Private message queues are not published in the Active Directory. They are accessible only by Message Queuing applications that know the full path name or format name of the message queue. Windows. Queue Manager Queue Name Private The server on which the MS Message Queue resides. The MS Message Queue from which to retrieve data. This MS Message Queue must belong to the Queue Manager. Select to access a Private message queue. The Private message queue can be accessed even if the queue manager is off-line.

36 36 Input Connector Settings dialog box Transaction Type MQ_NO_TRANSACTION All messages will be read without transaction support. MQ_INTERNAL_TRANSACTION Messages that are not successfully processed will be rolled-back, and the Communication Server will try to process them again. Transactional messages are only read (removed) from a connector if and when the transaction is committed. Otherwise they are returned to the connector and can be read during a subsequent transaction. Named Pipe input connector settings Handling output from a FIFO file. Windows and UNIX. Named pipe The named pipe. Netware Bindery input connector settings Retrieving data from a Novell 3.x network print queue. Windows. Server Queue name Print server Password The Novell 3.x network server. The Novell 3.x network print queue. The Novell 3.x network print server. Password to the Novell 3.x network print server. Netware NDS input connector settings Retrieving data from a Novell 4.x network print queue. Windows.

37 Input Connector Settings dialog box 37 Queue The Novell 4.x network print queue. Serial input connector settings Receiving input via a serial port. Windows and UNIX. Port Bits per second Data bits Parity Stop bits Flow control The port to be used. Data transfer speed. The number of data bits. How to handle parity. The number of stop bits to be transmitted per byte. How to handle flow control. Service Channel (COM) input connector settings Comment: Publishing a service in a Service Broker. Clients can access the service via COM. There is also a Service Channel Response (COM) input connector (without Response ) that must be used when a response is required from the Communication Server. This connector is configured the same way. Windows. Service description The name of the service as it will be published in the Service Broker. This name will be used in the client requests. Maximum lock time The maximum time (seconds) a client can lock the service. When this time has passed, the Service Broker will make the service available to other clients.

38 38 Input Connector Settings dialog box Maximum idle lock time The maximum time (milliseconds) a client can lock the service without using it. When this time has passed, the Service Broker will make the service available to other clients. Service Channel (HTTP) input connector settings Publishing a service in a Service Broker. Clients can access the service via http. Windows and UNIX. Service description The name of the service as it will be published in the Service Broker. This name will be used in the client requests. You can define several names, separated by comma, for the same service. Version The version of the service. There can be several versions of the same service. A client can request a specific version of a service. If the client does not request a specific version, it will get the highest available version of the service. SMS Provider input connector settings Receiving SMS messages via an external service provider (Telia). Windows and UNIX. Host Port The IP address of the Communication Server host. Must be registered with Telia. The port the Communication Server listens to for incoming SMS messages. Must be registered with Telia.

39 Input Connector Settings dialog box 39 Time-out (ms) Event name The maximum time (milliseconds) the connector will try to carry out the transaction (connect, send data, receive data) before canceling. The Event that handles SMS input. Status Messenger input connector settings Retrieving and filtering status information generated by the Communication Server. Windows and UNIX. Event name Notifications to receive The e MessageIN Event that will extract the notification data. Click the browse button to select the kind of information to be included in the status message. Notification settings Level Status Select the type of Project components for which information should be included in the status message. Note: Preproc must be combined with Event, job, or Process to give a result. Select the status of incidents or events for which information should be included in the status message.

40 40 Input Connector Settings dialog box Notification settings Options All notifications for one job in the same XML message Include all notifications generated by the same job in the same status message. If this option is cleared, each notification will generate a separate status message. You must select the corresponding SXD file for the MessageIN Event. Receive non-job related notifications (no job ID) Create status messages for information from the Communication Server that is not related to specific job IDs. For example status information for input connectors, or notifications about the Communication Server start/ stop. Receive only first notification for each job Create a status message only for the first notification generated by a job, and ignore subsequent notifications for the same job. Enable advanced features (disables Level and Status) Select to enable advanced options, as described below. External job IDs Enter the external IDs of the jobs that should generate a status message. Variables can not be used. Use commas to separate IDs. Log message IDs Enter the log message IDs that should generate a status message. Variables can not be used. Use commas to separate IDs. You will find the log message IDs in the \common\data\logmsg.txt file. Note: If you enter both an external job ID and a log message ID, a status message will be created when the log message is generated for the specified job. For example, if you enter external job IDs K12 and K13, and log message ID 1719, status messages will only be created if log message 1719 is generated for either of the two jobs.

41 Input Connector Settings dialog box 41 StdIn input connector settings The StdIn and StdOut connectors enable external applications to send data to the Communication Server via StdIn and receive output on StdOut. Windows and UNIX. There are no settings for this type of connector. TCP/IP input connector settings Receiving input on a designated IP port. Windows and UNIX. Host name Port The host. The port number. WebSphere MQ input connector settings Receiving input via an IBM WebSphere MQ message queue. See Dependencies and requirements on page 41 before you configure the connector. Windows and UNIX. Queue manager Queue name The queue manager that owns the message queue. The message queue. Dependencies and requirements The IBM WebSphere MQ environment The IBM WebSphere MQ environment must be set up on the same host as the Communication Server, and the IBM WebSphere MQ configuration must be done using IBM WebSphere MQ specific tools.

42 42 Input Connector Settings dialog box Asynchronous messaging The WebSphere MQ input connector only supports asynchronous messaging. Defining a client-connection channel You must define a client-connection channel that specifies the name of the MQI channel, the communication type, and the WebSphere MQ Server address. The name of the MQI channel must be the same as the name of the server-connection channel defined on the WebSphere MQ Server. You can define the clientconnection channel using the environment variable MQSERVER, as shown in the example below. For more information, see the IBM WebSphere MQ documentation. Example 4 Defining a client-connection channel SET MQSERVER=CHANNEL1/TCP/<WebSphere MQ server address> Startup arguments You must add -webspheremq to the argument file. Groups and Segments The Communication Server and the application that sends data to the Communication Server must handle group and segment properties in the same way. Both the Communication Server and the sending application should read groups and segments by using MQGMO_LOGICAL_ORDER to ensure that all messages are received in the same order as they were sent. The Communication Server uses MQGMO_SYNCPOINT to make sure that the message remains in the queue if the Communication Server fails to read or process the message. The Communication Server will retry to read the message until it succeeds to do so. If it continuously fails to read the message, you must remove the message from the queue. If a group of messages is sent, MQGMO_ALL_MSGS_AVAILABLE and MQGMO_WAIT are used to ensure that the Communication Server waits until all messages in the group are available. The Communication Server will also wait until all segments of a message are available. Get connector values You can use the scripting function GetConnectorValue to fetch WebSphere MQ attributes. Attribute GroupId MessageId CorrelationId Reply-To-Queue GetConnectorValue("<argument>") GetConnectorValue("IBMMQGroupId") GetConnectorValue("IBMMQMsgId") GetConnectorValue("IBMMQCorrelId") GetConnectorValue("IBMMQReplyToQ")

43 Input Connector Settings dialog box 43 Attribute Reply-To-Queue-Manager Message type Report options GetConnectorValue("<argument>") GetConnectorValue("IBMMQReplyToQMgr") GetConnectorValue("IBMMQMsgType") GetConnectorValue("IBMMQReport") HTTP Access tab Specifying HTTP access for an input connector. You can use an HTTP(S) input connector as interface for receiving input over HTTP. You can forward the input, from the HTTP input connector, to several queue enabled input connectors of different types. Settings HTTP Connector URI The HTTP or HTTPS input connector. The URI to access this connector via HTTP. Example 5 HTTP access for an Internal input connector You have one HTTP connector HTTP_IN and one Internal connector INTERNAL. The connector HTTP_IN has the following HTTP access specified: HTTP Connector: HTTP_IN URI: / The connector INTERNAL has the following HTTP access specified: HTTP Connector: HTTP_IN URI: /internal If a request is sent to the connector HTTP_IN will receive and handle the request. If a request is sent to the connector HTTP_IN will receive the request and forward it to the connector INTERNAL. Queue Settings tab Selecting a queue for the connector and, optionally, to edit the queue settings. Settings Queue The queue to select for the connector.

44 44 Input Connector Settings dialog box Settings Manage Queues Use default queuing options Store successful jobs Store failed jobs Retries Retry delay Add new queues to the Platform, edit queue settings, etc. Select whether or not to use the default queuing options. What to store when a job has been successfully sent through the queue. No Store nothing. Store information only Store information about the job. Store information and job Store information about the job, and the job itself. Allows the queue to resend the job more than once. What to store when a job has not been successfully sent through the queue. No Store nothing. Store information only Store information about the job. Store information and job Store information about the job, and the job itself. Allows the queue to resend the job more than once. Number of times the Communication Server will try to handle a failed job. The time (milliseconds) the Communication Server will wait before it tries to handle a failed job.

45 Input Connector Settings dialog box 45 Filter Chain Settings tab Specifying a filter chain for the input connector. Contents Look in Item Note Selected Filter Select Undo select Open editor Close editor Add Resource Set Create Resource Set Browse to the appropriate resource set and filter chain folder. A filter chain. All available filter chains are displayed in the items list. Notes written for the item. Right-click the item and select Edit Notes to edit the notes. Displays the selected filter chain. Enable/disable the resource filter. When enabled, only filter chain folders will be visible. Select the filter chain (copy from the Items list to the Selected list). Undo selection (remove from the Selected list). Select a filter chain in the Items list and open it in the filter chain editor. Close the filter chain editor. Add a resource set to the active Platform. Create a new resource set and add it to the active Platform.

46 46 Input Connector Settings dialog box Contents New resource Add resource Import Create a new resource file using a resource editor, and link it to the resource set. Link an existing resource file to the resource set. Create a new resource file and link it to the resource set. You create the resource file by importing and embedding a source file. General Settings tab Adding notes, and customizing the connector. Settings Note Custom Settings Keep input Job structure in output Comments and notes related to this connector. Commands and keywords. Specifies whether to process all Messages extracted from the input file (or equivalent) in the same StreamServe job, or process each extracted Message as a separate StreamServe job. This affects the usage of variables and Process output since all stored variables and Processes are removed when a StreamServe job is completed. For example, it is only possible to use variables and to sort Process output within the same StreamServe job. If selected, StreamServer processes all extracted Messages in the same StreamServe job. If not selected, StreamServer processes each extracted Message as a separate StreamServe job. This reduces the use of memory and disk space when handling large jobs, but the Process output and all stored variables are removed when the Message is completed.

47 Output Connector Settings dialog box 47 Output Connector Settings dialog box Configuring the output connector. Code page icon Codepage Settings tab Driver icon Device Driver Settings tab Symbol Set tab Filter Chain icon Filter Chain Settings tab Queue icon Queue Settings tab Connector icon Connector Settings tab General icon General Settings tab Codepage Settings tab Specifying a code page for the output. See the Code pages and Unicode support in StreamServe documentation for information. Settings Inherit code page Code page name Reorder BiDi output in visual order Use the same code page for both input and output. The output will inherit the code page specified for the input Specify a different code page for the output. This code page must cover at a minimum all the characters covered in the code page for the input. Only for Arabic and Hebrew code pages, and for UCS-2 and UTF-8. The Communication Server processes bidirectional text in logical order. If required, select this option to reorder the output to visual order.

48 48 Output Connector Settings dialog box Settings Add byte order mark Byte order Only for UCS-2 and UTF8. Select to include a byte order mark at the beginning of a UCS-2 (UTF-16) or UTF-8 encoded output file. The application that receives the output can use this byte order mark to automatically determine the encoding (UTF-8 or UTF-16 encoding scheme) and the byte order used for the data in the UTF-16 encoding scheme. Only for UCS-2. For the UTF-16 encoding schemes, each character code unit is represented by two bytes. When you select UCS-2 as code page, you must also specify the byte order. The byte order to select depends on the application that receives the output. Device Driver Settings tab Selecting the device to use. The actual output destination, for example an HP Laser Jet printer, determines which option to select. Settings Device Driver settings Alias Type of output device. Device specific settings. See the data sheet for the corresponding device. You can specify an alias for each property. Symbol Set tab When sending output to a PCL printer, there is an option to override the symbol set in the code page specified for this connector, and specify a different symbol set for the printer. Settings Override symbol... Static Lookup Variable Select to override the symbol set. Select a static symbol set. A lookup table specifies which symbol set to use. A variable specifies which symbol set to use.

49 Output Connector Settings dialog box 49 Filter Chain Settings tab Specifying a filter chain for the input connector. See Filter Chain Settings tab on page 45. Queue Settings tab Selecting a queue for the connector and, optionally, to edit the queue settings. Settings Queue Manage Queues Use default queuing options Store successful jobs Store failed jobs Retries Retry delay The queue to select for the connector. Add new queues to the Platform, edit queue settings, etc. Select whether or not to use the default queuing options. What to store when a job has been successfully sent through the queue. No Store nothing. Store information only Store information about the job. Store information and job Store information about the job, and the job itself. Allows the queue to resend the job more than once. What to store when a job has not been successfully sent through the queue. No Store nothing. Store information only Store information about the job. Store information and job Store information about the job, and the job itself. Allows the queue to resend the job more than once. Number of times the Communication Server will try to handle a failed job. The time (milliseconds) the Communication Server will wait before it tries to handle a failed job.

50 50 Output Connector Settings dialog box Connector Settings tab Configuring output connectors. Settings Connector Connector specific Type of output connector. Connector specific settings. Output mode Select to generate output per Process, Document or job. ADO output connector settings Comments: Entering data into an ODBC or OLE DB enabled database table. You must use StreamServe ODBC scripting functions if you want to update existing information in a database table, or if you want to carry out several SQL commands on the data source. Windows. DataSource CustomData Source UserName Password SQLCommand Output mode The ODBC data source to connect to. A custom data source to connect to, for example an external ODBC or OLE DB data source. This will override the DataSource specified above. For example: driver={sql Server}; server=my_server;uid=;pwd=;database=my_db; User name for accessing the data source. Overrides any other user names specified for the data source. Password for accessing the data source. Overrides any other passwords specified for the data source. SQL command to be carried out on the data source. For example: Insert into customer_table * Select to generate output per Process, Document, or job.

51 Output Connector Settings dialog box 51 Command output connector settings Enables you to use commands that specify how to handle the output. Windows and UNIX. Command Output mode Enter the path to a batch file or a script. For example: C:\project\myname.bat You can also enter a one-line command. For example: Physical "<[cmd=cat %1 > kv.$destination]>" Select to generate output per Process, Document, or job. Dazel output connector settings Writing output to a Dazel logical queue. See your Dazel documentation for details. Windows and UNIX. Dazel logical queue The Dazel logical queue, for example: qprinter Runtime specific settings FTP Type default Character set default Document format default The default file transfer mode. The default character set. The format of an incoming document.

52 52 Output Connector Settings dialog box Exchange output connector settings Writing objects to Microsoft Exchange Server folders. For example, create a calendar object and automatically enter it directly into a specified Microsoft Outlook Calendar folder. Windows. Server MailBox Folder DataType FileName Output mode The Microsoft Exchange Server. For example: laxnt04 The user account on the Microsoft Exchange Server. For example: streamserve The folder to write to. For example: Mailbox - Brown, Jane\Inbox The folder name may be language sensitive. In that case, you must write the folder name on the local language. For example: Postlåda - Brown, Jane\Inkorg CDOObject All fields in the output will be added to the folder. File The output will be added as an attachment to the folder. This mode is used to, for example, save PDF documents. Name and the path for the file to write to the folder. Select to generate output per Process, Document, or job. Fax Connect output connector settings Faxing output via different types of fax servers. You select which type of fax server to use when you select a device driver for the connector. Windows and UNIX.

53 Output Connector Settings dialog box 53 Type Command Printer Directory Output mode Command Use a DOS / UNIX command, batch file, or script to specify the output destination. Spool Send the output to a specific fax device. File Send the output to a specific directory. The fax device will retrieve the output from this directory. A command, batch file, or script. For example: C:\project\myname.bat The fax device. The output directory. Select to generate output per Process, Document, or job. File output connector settings Sending output to a file. Windows and UNIX. File Append Create directories Output mode The file. For example: C:\projects\myfile.txt You can also specify the file using the SetDestPath scripting function. Yes Output will be appended to the file. If the file does not exist, it will be created. No The file will be overwritten if it already exists. If the file does not exist, it will be created. Yes If any of the directories in the File path does not exist, it will be created. No If any of the directories in the File path does not exist, an error message will be generated. Select to generate output per Process, Document, or job.

54 54 Output Connector Settings dialog box FTP output connector settings Comments: Writing files to an FTP server. If you need more than one connector (input or output) per user account, this must be defined on the FTP server. On the FTP server, the number of concurrent connections must be equal to, or higher than, the number of FTP connectors (input and output) set up for a user account. Windows and UNIX. Host Port User name Password Remote path File Passive mode Transfer mode Output mode The FTP server, for example rtu.baldwin.com The port on the FTP server. The user name for accessing the FTP server. The password for accessing the FTP server. The directory to be accessed on the FTP server. If you leave this blank, the root directory will be set as remote path. For example: /invoices/pdfout/area2 Whether to use slash or back-slash is determined by the FTP server software. The file name, including file extension, to be written to the FTP server. Select whether or not to enable Passive Mode. FTP in Passive mode is used when communicating through firewalls. It opens a control connection to the FTP server, tells the FTP server to expect a control connection and a second connection. Then it opens the data connection to the FTP server itself on a randomly chosen highnumbered port. Note: This works with most firewalls unless the firewall restricts outgoing connections on high-numbered ports. ASCII ASCII, Type A, transfer method. Control and formatting data is converted to local equivalents. Binary FTP Image, Type I, transfer method. The file is transferred without any changes. Select to generate output per Process, Document, or job.

55 Output Connector Settings dialog box 55 Runtime specific settings If you select the <Default> options for Passive Mode and Transfer Mode, the Platform settings will be used. Generic Archive output connector settings Archiving output in external archiving systems. Windows and UNIX Index directory Output mode A directory where the output will be stored temporarily before it is sent to the archiving system. There will automatically be one sub directory per job. Select to generate output per Process, Document, or job. Runtime specific settings Index Entry Index Line Separator Index Command Remove Job Directory Characters used to separate the Archive Attributes within an index line. Characters used to separate index lines. This command is executed when all files have been added to the Index Directory. For example: programname -st %l -dt % where programname uses the index file (%1) in the Index Directory (%) for further processing. Select to remove the job directory (within the Index Directory) after successful completion of the Index Command.

56 56 Output Connector Settings dialog box Runtime specific settings Archive Attributes The archive attributes consist of an attribute name and a value. The value can be a static text or a variable. By default, there is an attribute for the Process output file name. You must manually add any other attributes. The order in which the attributes are listed is important since the Communication Server will output the attributes in this order. You can enter the attribute name <idxcodepage> and the appropriate code page as attribute value to specify a code page for the index file. The attribute name must include the < and > characters. HTML output connector settings Generating output spool files in static HTML using stylesheets. The output is sent to the directory specified in the connector settings. You must use the HTML driver and configure the settings at Job Begin in the Runtime configuration. Windows and UNIX. HTML destination The path to the HTML output. For example: HTMLOUT/stones.html If the output contains more than one HTML file, a number will be added to the file name. For example: stones-1.html stones-2.html HTTP Response output connector settings Enabling the Communication Server to respond to an HTTP request. Windows and UNIX.

57 Output Connector Settings dialog box 57 Content-type Output mode The content-type of the output. For example: text/html; charset="ascii" Select to generate output per Process, Document or job. Runtime specific settings Custom header A user defined header that will be included in the response. Use the following syntax: <Name>:<Value> You can separate <Name>:<Value> pairs with <0d><0a>. HTTP(S) Submit output connector settings Enabling the Communication Server to function as an HTTP client submitting output to an HTTP server. Windows and UNIX. Use security configuration CA certificate Security configuration HTTPS only. Select this option if you want to connect a security configuration to this connector. HTTPS only. A CA root certificate that confirms the identity of the SSL server. The certificate must be included in a resource set connected to the Platform. You can also specify the CA root certificate in a security configuration that you connect to this connector. HTTPS only. The security configuration to connect to this connector. The security configuration must be included in a resource set connected to the Platform. See the Encryption and authentication documentation for more information.

58 58 Output Connector Settings dialog box Method URL Content-type Time-out Version SSL version Authentication Realm User name Password Cache file Output mode Specify the method the client will use when submitting output to the HTTP server. POST Send output to the HTTP server for further processing. PUT Send output to the HTTP server. For example, if output is a web page, select PUT to put it on a web server. Requires scripting and specific access rights to the server. The URL to the HTTP server. The content-type of the output to send to the HTTP server. For example: text/html; charset="ascii" The maximum time (milliseconds) the Communication Server waits before cancelling a transfer. The HTTP version to use. HTTPS only. The SSL version to use. Server and clients must use the same SSL version. None Do not use authentication. Basic Send authentication parameters as clear text. This is the only scheme supported in HTTP/1.0. Digest Send authentication parameters as a checksum over the network. Requires HTTP/1.1. Only if authentication is required. The name of the realm. Only if authentication is required. The user name to access the realm. Only if authentication is required. The password to access the realm. The cache file that stores communication checksums between Communication Server start/stop. Select to generate output per Process, Document or job.

59 Output Connector Settings dialog box 59 Runtime specific settings Custom header Response place connector Response custom header On failure file On failure place connector On failure content type On failure custom header A user defined header that will be added to the HTTP output. Use the following syntax: <Name>:<Value> You can separate <Name>:<Value> pairs with <0d><0a>. The connector that will receive the response from the HTTP server. To use the response, you must specify the connector that will receive the response. This is either an HTTP Response output connector, or any type of queue enabled input connector. A user defined header that will be added to the response from the HTTP server. The path to a file that the Communication can send when it fails to send output to the HTTP server. The connector that will pick up the failure file. This is either an HTTP Response output connector, or any type of queue enabled input connector. For example, if the Communication Server receives input from a client, and sends output to an HTTP server, an error message (the failure file) can be sent back to the client using an HTTP Response connector. The content-type of the failure file. A user defined header that will be added to the failure file. Internal output connector settings Enabling the Communication Server to loop back output for further processing. Data is looped back to an Internal input connector. Comments: Data sent from the Internal output connector must not contain any formatting information. If you have an internal loop via an Internal input connector and an Internal output connector, you must specify a UTF-8 code page for both connectors. Windows and UNIX.

60 60 Output Connector Settings dialog box Destination (input connector name) The Internal input connector to send data to. IXOS Archive in R3 output connector settings Comments: Writing output to an IXOS transfer directory. IXOS is a document management system for SAP/R3 users. You must be familiar with IXOS and the terminology used by IXOS. See Windows and UNIX. IXOS transfer directory Meta documents Max. no of documents in meta Fixed directory name Output mode The path to the IXOS transfer directory. For example: \\project\myfolder\ixosfiles Yes Enable the use of Meta Documents. Use Max Documents in Meta below to specify the maximum number of documents to be stored in each Meta document. When the maximum number of documents have been added, a new meta file is created, i.e. a new document directory is created. No Disable the use of Meta Documents. The maximum number of documents in each Meta Document directory. Yes The Communication Server will use a fixed directory specified in the Runtime configuration. No The Communication Server will generate unique directories with a maximum of 1000 documents in each directory. Select to generate output per Process, Document, or job. Runtime specific settings IXATTR file lines and Commands file lines These lines will be stored in a file. All variables specified in the lines will be checked, and their values will be used when the file is created. You can add, delete, or edit the lines, and you can also rearrange the order of the lines.

61 Output Connector Settings dialog box 61 Runtime specific settings Autodetect Document Type Document Type Directory Name Component Name When selected, the Communication Server will refer to the driver being used to format the document. This document type will be used regardless of the driver type. The Fixed Directory. The name to be inserted in the Commands file. Java output connector settings Custom Java output connector. See the StreamServe EIF SDK documentation. Windows and UNIX. Java Response output connector settings Custom Java output connector. See the StreamServe EIF SDK documentation. Windows and UNIX. Java RMI output connector settings Custom Java output connector. See the StreamServe EIF SDK documentation. Windows and UNIX. JMS Publish output connector settings Enabling the Communication Server to deliver messages to a named topic in a publish-subscribe messaging system. For more information about JMS, see

62 62 Output Connector Settings dialog box Windows and UNIX. Context Topic Factory User Name Password Topic Custom Properties Message Format Delivery Mode Priority Time to live The JNDI context. If you leave this empty, the initial context will be used. The JNDI lookup name for the topic connection factory. This setting is mandatory. A JMS client uses a connection factory to create a connection to the JMS provider. User name to access the JMS provider. Password to access the JMS provider. The JNDI lookup name for the topic. This setting is mandatory. Custom message properties. Can be used for selecting messages, or for providing information about contents or message types. For example, set a custom header to "color= blue ". BytesMessage Send the message as bytes. The recipient must know how to interpret the information. Use this option if you specify a driver for the connector. TextMessage Send the message as text. Use this option when sending XML or text formatted output. Default Keep the settings defined in the deployment process. Persistent Output will be delivered even if power is lost. Non persistent Output will be delivered faster. Delivery is not guaranteed if power is lost. JMS priority. 0 is lowest priority, and 9 is highest priority. If you do not specify a priority level, the default level is 4. A JMS provider tries to deliver messages with high before messages with low priority, but will not necessarily deliver the messages in the order of priority. By default, a message will live forever. You can use this parameter to specify an expiration time (milliseconds).

63 Output Connector Settings dialog box 63 Type Reply To Correlation Id Output mode This is a JMSType header field. You can, for example, specify the type of message when using the message format BytesMessage. Receivers can use the JMSType header field to determine whether or not they can interpret this kind of message. The JNDI lookup name of the queue or topic to which the message receiver should send a response message. Specify this only if you expect the message receiver to reply to the delivered message. A correlation id for the message. Can be used to link one message to another, for example to link a response message to the corresponding request message. It is possible to fetch the correlation ID for incoming JMS messages using the scripting function GetExtJobId(). Select to generate output per Process, Document, or job. JMS Queue output connector settings Enabling the Communication Server to deliver messages to a named queue in a point-to-point messaging system. For more information about JMS, see Windows and UNIX. Context Queue Factory User Name Password Queue The JNDI context. If you leave this empty, the initial context will be used. The JNDI lookup name for the queue connection factory. This setting is mandatory. A JMS client uses a connection factory to create a connection to the JMS provider. User name to access the JMS provider. Password to access the JMS provider. The JNDI lookup name for the queue. This setting is mandatory.

64 64 Output Connector Settings dialog box Custom Properties Message Format Delivery Mode Priority Time to live Type Reply To Correlation Id Output mode Custom message properties. Can be used for selecting messages, or for providing information about contents or message types. For example, set a custom header to "color= blue ". BytesMessage Send the message as bytes. The recipient must know how to interpret the information. Use this option if you specify a driver for the connector. TextMessage Send the message as text. Use this option when sending XML or text formatted output. Default Keep the settings defined in the deployment process. Persistent Output will be delivered even if power is lost. Non persistent Output will be delivered faster. Delivery is not guaranteed if power is lost. JMS priority. 0 is lowest priority, and 9 is highest priority. If you do not specify a priority level, the default level is 4. A JMS provider tries to deliver messages with high before messages with low priority, but will not necessarily deliver the messages in the order of priority. By default, a message will live forever. You can use this parameter to specify an expiration time (milliseconds). This is a JMSType header field. You can, for example, specify the type of message when using the message format BytesMessage. Receivers can use the JMSType header field to determine whether or not they can interpret this kind of message. The JNDI lookup name of the queue or topic to which the message receiver should send a response message. Specify this only if you expect the message receiver to reply to the delivered message. A correlation id for the message. Can be used to link one message to another, for example to link a response message to the corresponding request message. It is possible to fetch the correlation ID for incoming JMS messages using the scripting function GetExtJobId(). Select to generate output per Process, Document, or job.

65 Output Connector Settings dialog box 65 JMS Response output connector settings Enabling the Communication Server to send a response to a received message. The received message must include information about which queue or topic to send the response to. For more information about JMS, see Windows and UNIX. Queue Factory Queue User Name Queue Password Topic Factory Topic User Name Topic Password Custom Properties Message Format Delivery Mode The JNDI lookup name for the queue connection factory. A JMS client uses a connection factory to create a connection to the JMS provider. User name to access the (queue) JMS provider. Password to access the (queue) JMS provider. The JNDI lookup name for the topic connection factory. User name to access the (topic) JMS provider. Password to access the (topic) JMS provider. Custom message properties. Can be used for selecting messages, or for providing information about contents or message types. For example, set a custom header to "color= blue ". BytesMessage Send the message as bytes. The recipient must know how to interpret the information. Use this option if you specify a driver for the connector. TextMessage Send the message as text. Use this option when sending XML or text formatted output. Default Keep the settings defined in the deployment process. Persistent Output will be delivered even if power is lost. Non persistent Output will be delivered faster. Delivery is not guaranteed if power is lost.

66 66 Output Connector Settings dialog box Priority Time to live Type Reply To Correlation Id Output mode JMS priority. 0 is lowest priority, and 9 is highest priority. If you do not specify a priority level, the default level is 4. A JMS provider tries to deliver messages with high before messages with low priority, but will not necessarily deliver the messages in the order of priority. By default, a message will live forever. You can use this parameter to specify an expiration time (milliseconds). This is a JMSType header field. You can, for example, specify the type of message when using the message format BytesMessage. Receivers can use the JMSType header field to determine whether or not they can interpret this kind of message. The JNDI lookup name of the queue or topic to which the message receiver should send a response message. Specify this only if you expect the message receiver to reply to the delivered message. A correlation id for the message. Can be used to link one message to another, for example to link a response message to the corresponding request message. It is possible to fetch the correlation ID for incoming JMS messages using the scripting function GetExtJobId(). Select to generate output per Process, Document, or job. Job Resource output connector settings Comments: Temporarily storing data as a job resource that will be added to processed data later on. For example, you can use the EMF Print processor to convert EMF files into LXF overlays. The LXF overlay is sent to a Job Resource output connector. The LXF overlay can then be called from a PageOUT Process and be added to the processed output. The following script functions are related to this connector: OutputLXFJobResource() DeleteJobResource() GetJobResourceIndex() GetJobResourceURI() Windows and UNIX.

67 Output Connector Settings dialog box 67 Name Content-type Custom header Expire by time Duration Time unit Expire by access Access count Expire with job Output mode A name used together with scripting functions to identify a specific job resource. Used only with HTTP(S) input and HTTP Response output connectors. The content-type of the job resource. For example: text/html; charset="ascii" Used only with HTTP(S) input and HTTP Response output connectors. A user defined header that will be added to the job resource. Use the following syntax: <Name>:<Value> You can separate <Name>:<Value> pairs with <0d><0a>. Yes Define a life-time for the job resource. No Do not define a life-time for the job resource. Renew Restart the life-time counter when the resource has been accessed. Duration and Time unit sets the life time. Duration and Time unit sets the life time. Yes Limit the number of times a resource can be accessed before it is deleted. No Do not limit the number of times a resource can be accessed. The number of times the resource can be accessed. All resource operations within the same job are considered as one access. Yes Delete the resource when the job is completed. No Do not delete the resource when the job is completed. Select to generate output per Process, Document, or job. Lotus Notes output connector settings Note: If you run the Communication Server and a Lotus Notes client version 6.x or 7.0 on a Windows 2003 Server, you must install Citrix to use the Lotus Notes output connector.

68 68 Output Connector Settings dialog box Writing output to a Lotus Notes database on a Lotus Domino server. Windows. Notes Server Output mode The Lotus Domino server to connect to. For example: windows_server05/my_domino_server where windows_server05 is the computer hosting the Lotus Domino server. Select to generate output per Process, Document, or job. Runtime specific settings Notes Database The Lotus Notes database on the Lotus Domino server specified in the Notes Server setting. The Lotus Notes database stores the output from the Communication Server as an attachment to a Note. For example: custmsgs.nsf Note: The specified database must allow write access for the user specified in the Lotus ID file. Only a Lotus Domino administrator can enable read or write access to the Lotus Notes database.

69 Output Connector Settings dialog box 69 Runtime specific settings Password The password for unlocking the Lotus ID file which authenticates access to a Lotus Notes database. The Communication Server searches for the Lotus ID file named ssdominouser.id in the export directory of the StreamServe Project. If the Lotus ID file is not found, or if the password fails to unlock it, the Communication Server tries to use the previously used Lotus ID file that ssnotes.ini has a reference to. If you connect to the database via a Lotus Domino server, without access to a Lotus Notes client installation, you must: Obtain a suitable Lotus ID file. Ensure that the Lotus ID file is recertified and contains a valid password. Rename the Lotus ID file to ssdominouser.id Store the Lotus ID file in the export directory of the Project. Ask your Lotus Domino administrator for assistance. Default Form File name Compress The Lotus Notes form to be used. To create a Lotus Notes form on the Lotus Domino server, you must use the Domino Designer client. The name of the file created by the Communication Server and attached to the Note. For example: $docname.pdf Note: The Temporary directory property must be specified with a full path for the StreamServe service running the Project. Select to compress the file attached to the Note when sending it to the Domino Server.

70 70 Output Connector Settings dialog box Runtime specific settings Indexes In addition to the attached file produced by the Communication Server, you can add data about the attachments to the corresponding Note. This is useful if you want data about the attachment to be easily accessible by the Lotus Notes client or the Lotus Notes Fetch wizard, without having to open the attachment. To add this data for a Note, you must enter the items that will be included in the Note and a variable for each item. Index Name The Note item name. Data Type The type of the item data. Variable A StreamServe variable. The value of the variable is stored in the Note. To specify the number of, and delay between attempts to open the Lotus Notes database send a Note to the Domino Server via a Lotus Notes output connector, you can specify the following additional runtime parameters on the Custom tab. Parameter lotusdbopenretrydelay <open_delay> lotusdbopenmaxretries <open_retries> lotusconnretrydelay <send_delay> lotusconnmaxretries <send_retries> Description The time to wait in milliseconds between attempts to open the Lotus Notes database. The default value is For example: lotusdbopenretrydelay 2000 The number of times to attempt to open the Lotus Notes database. The default value is 10. For example: lotusdbopenmaxretries 5 The time to wait in milliseconds between attempts to send a Lotus Note to the Lotus Domino server via a Lotus Notes output connector. The default value is For example: lotusconnretrydelay The number of times to attempt to send a Note to the Lotus Domino server via a Lotus Notes output connector. The default value is 10. For example: lotusconnmaxretries 20

71 Output Connector Settings dialog box 71 MAPI output connector settings Comments: Sending output via MAPI . In the Control Center, the logon options for the Communication Server service must not be set to System account. Use the logon option This account and specify an account with permissions to use the Windows Messaging Profile specified for the MAPI connector. To change the logon options, right-click the service in the Control Center and select Service Startup. Windows Default profile Number of retries Retry interval Output mode The Windows Messaging Profile that will be used by default. A Windows Messaging Profile identifies a specific user and the mail server. To find the profiles available, open the Mail setup dialog box from the Control Panel and click Show Profiles. The address that will be used is the address specified as the From address in the user s profile. To be able to use alternative From addresses, you must set up a profile for each address. You do this in the runtime configuration of the connector. The number of times to try to reconnect if the mail server does not respond. The interval (seconds) between retries. Select to generate output per Process, Document, or job. Runtime specific settings Edit Mail Ignore missing attachments Attachment name Convert PCL to PDF Opens the editor. Select whether or not you want the Communication Server to try to send an with missing attachments. The name of the attachment that contains the output from the Process. For example: $custno.pdf Select whether or not to convert PCL attachments to PDF.

72 72 Output Connector Settings dialog box Runtime specific settings Compress Code page Profile name Select whether or not to compress the attachments. Code page for the . A Windows Messaging Profile identifies a specific user. The address that will be used is the address specified in the From address in the user s profile no matter what you entered in the From field when you created the . To be able to use alternative From addresses, you must set up a profile for each address. Use default Profile of Connector Use the profile specified in the Platform. Static Use an alternative profile. Variable Use a variable to determine the alternative profile. Lookup Use a lookup table to determine the alternative profile. Edit Mail settings To, Cc, Bcc, and Subject Request receipt Attachments Standard attributes. Request a read receipt from the recipient. A notification is received when the recipient reads the provided that this functionality is supported by the servers and clients. Attached files (not Process output). Use the Add/ Edit buttons to specify the Mail Attachment settings. Mail Attachment settings Attachment Attachment name Convert attachment from PCL to PDF Compress attachment The path to the file to attach. The name of the attachment, for example pricelist.pdf. Leave this empty if you want the attachment name to be the same as the name of the source file. Select whether or not to convert PCL attachments to PDF. Select whether or not to compress the attachments.

73 Output Connector Settings dialog box 73 MAPI for MailOUT output connector settings Comments: Sending output via MailOUT and MAPI . In the Control Center, the logon options for the Communication Server service must not be set to System account. Use the logon option This account and specify an account with permissions to use the Windows Messaging Profile specified for the MAPI connector. To change the logon options, right-click the service in the Control Center and select Service Startup. Windows. Default Profile Number of retries Retry interval The Windows Messaging Profile that will be used by default. A Windows Messaging Profile identifies a specific user and the mail server. To find the profiles available, open the Mail setup dialog box from the Control Panel and click Show Profiles. The address that will be used is the address specified as the From address in the user s profile. To be able to use alternative From addresses, you must set up a profile for each address. You do this in the runtime configuration of the connector. Number of times to try to reconnect if the mail server does not respond. Interval (seconds) between retries.

74 74 Output Connector Settings dialog box Runtime specific settings Profile Name A Windows Messaging Profile identifies a specific user. The address that will be used is the address specified in the From address in the user s profile no matter what you entered in the From field when you created the . To be able to use alternative From addresses, you must set up a profile for each address. Use default Profile of Connector Use the profile specified in the Platform. Static Use an alternative profile. Variable Use a variable to determine the alternative profile. Lookup Use a lookup table to determine the alternative profile. MSMQ output connector settings Private and public message queues: Enabling and integrating Communication Server capabilities in Microsoft message queuing environments. Public message queues are published in the Active Directory. Private message queues are not published in the Active Directory. They are accessible only by Message Queuing applications that know the full path name or format name of the message queue. Windows. Queue Manager Queue Name Private The server on which the MS Message Queue resides. The MS Message Queue to which to write data. This MS Message Queue must belong to the Queue Manager. Select to access a Private message queue. A private message queue can be accessed even if the queue manager is off-line.

75 Output Connector Settings dialog box 75 Max Message Size Output mode The maximum size for an MSMQ message is 4 MB. This is also the default message size if no other value is specified. If the data sent from the Communication Server exceeds this size, it will be split into several messages. These messages will be synchronized as follows: The first message in the sequence will have the appspecific property set to the number of messages that will arrive in this sequence of segmented messages (the first message is excluded). The following messages will have this number decreased by one and the last message in the sequence will have the appspecific property set to 0. All messages, except the first one, will have their correlation ID property set to the message ID of the first message. Select to generate output per Process, Document, or job. Runtime specific settings Message Delivery Message Priority Message Encryption Message Journaling Express The message is not stored on disk, and cannot be recovered in case of failure. Persistent The message is stored on disk, and can be recovered in case of failure. The priority of the message. Enable message encryption. Symmetric key and asymmetric (public/private) key encryption algorithms. Encryption slows down transfer of messages. Journals provide audit trails. MQMSG_JOURNAL_NONE No journaling. MQMSG_JOURNAL Journaling enabled. MQMSG_DEADLETTER If the message is not delivered or read in time, it will be stored in a deadletter queue. MQMSG_JOURNAL MQMSG_DEADLETTER Both journaling and deadletter functionality enabled.

76 76 Output Connector Settings dialog box Runtime specific settings Max Time to Reach Queue Max Time to Receive Message Tracing Transaction Type Message Label The maximum time (seconds) for the message to reach the destination queue. If the message does not reach the destination queue within this time, and you have enabled one of the deadletter options, the message will be moved to the deadletter queue. The maximum time (seconds) to wait for the message to be read. If the message is not read within the specified time, and you have enabled one of the dead-letter options, the message will be moved to the dead-letter queue. Tracing Off No tracing of the progress of the message. Tracing On Progress of the message is traced. Note: Message route tracking must be enabled by defining a report queue for the sending party. MQ_NO_TRANSACTION The message will be sent without transactional support. MQ_INTERNAL_TRANSACTION The message will be sent within a transaction. Transactional messages are either sent together and in the order they were sent (a committed transaction), or not sent at all (an aborted transaction). Note: The receiving MSMQ queue must support transactions. A descriptive text to include in the message. Netware Bindery output connector settings Sending data to a Novell 3.x network print queue. Windows. Server Queue name Print server The Novell 3.x network server. The Novell 3.x network print queue. The Novell 3.x network print server.

77 Output Connector Settings dialog box 77 Password Password to the Novell 3.x network print server. Netware NDS output connector settings Sending data to a Novell 4.x network print queue. Windows. Queue The Novell 4.x network print queue. Null Connector output connector settings Enabling the Communication Server to send output to a dummy connector that does not direct output to any file or printer. Windows and UNIX. There are no properties for this type of connector. Pipe output connector settings Sending output to a named pipe. UNIX. Pipe The command to execute, for example cat RePRINT output connector settings Delivering documents to a RePRINT database.

78 78 Output Connector Settings dialog box Windows and UNIX. Data source User name Password Output mode The ODBC data source to connect to. For example StrsArchiveDSN User name for accessing the data source. Password for accessing the data source. Select to generate output per Process, Document, or job. Runtime specific settings Document type identifier Available document types The document type identifier. Can contain any alphanumeric character, including space. Maximum 55 characters. To store several document types, you must use a variable for the identifier. A list of available document types for the specified document type identifier. Service Channel Response (COM) output connector settings Used together with a Service Channel Response (COM) input connector. Sends the processed output back to the client via the Service Channel Response (COM) input connector. Windows. Input Connector Name Output mode The Service Channel Response (COM) input connector that received the input. Select to generate output per Process, Document, or job.

79 Output Connector Settings dialog box 79 Service Channel Response (HTTP) output connector settings Used together with a Service Channel (HTTP) input connector. Sends the processed output, via a Service Broker, back to the client. Windows and UNIX. Content-type Output mode The content-type of the output. For example: text/html Select to generate output per Process, Document, or job. Service Channel Submit (COM) output connector settings Invoking services via a Service Broker. Windows. Service Broker Host The Service Broker host. Service Description The name of the requested service. For example: Service_3 Server ID Wait for lock The server ID of a specific Communication Server. For example: \StreamServe4 Specify this only if you want to select a specific Communication Server. If you do not specify a Server ID, the Service Broker will select the appropriate Communication Server. The maximum time (milliseconds) the connector will wait to access the service.

80 80 Output Connector Settings dialog box Send Mode Output mode Direct Send data directly to the destination. Runtime settings will have no effect in this mode. To enable Runtime settings you must use one of the Buffer modes below. Buffer in memory Buffer all data in memory before sending it. Fast data transfer, but can consume a lot of memory. Buffer to disk Buffer all data on disk before sending it. Suitable for large files. Select to generate output per Process, Document, or job. Service Channel Submit (HTTP) output connector settings Invoking services via a Service Broker. Can also be used for adding documents to a service response. Windows and UNIX. Service Broker host Port The Service Broker host. The Service Broker port. Service description The name of the requested service. For example: Service_3 Server ID Version Content-type The server ID of a specific Communication Server. For example: \StreamServe4 Specify this only if you want to select a specific Communication Server. If you do not specify a Server ID, the Service Broker will select the appropriate Communication Server. The version of the service. If omitted, the highest registered version of the service will be used. The content-type of the submitted output. For example: application/pdf

81 Output Connector Settings dialog box 81 Command Response service channel Connection timeout Communication time-out Doc group ID LastDoc Output mode Specifies what to do with the output data (document). SendDocument Send the output via the Service Broker to a Communication Server. The Communication Server will process the data, and send the processed output to a printer, fax, etc.. SendReceiveDocument Send the output via the Service Broker to a Communication Server. The Communication Server will process the data, and send the processed output back in the response. AddDocument Send the output to the Service Broker. The Service Broker will add this document to a response that has the same Doc Group ID or Strs ID as this document. The service name of the Service Channel (HTTP) input connector that will receive the response. For example: response_connector The maximum time (milliseconds) to wait to connect to the Service Broker. The maximum time (milliseconds) to wait before aborting transfer/reception of data. Can be used to define which response to add documents to. The instance that issued the SendReceiveDocument request is the instance that will receive the response. The instance that issued the AddDocument request is the instance that will add the document to the above response. The document will be added to the response if either: Both instances use the same Doc Group ID. No Doc Group ID is specified, and the response and document to add have the same Strs ID. Defines whether or not the current document is the last document to add. Normally used when the client that issued the SendReceiveDocument request sets waitfordocs to -1. Select to generate output per Process, Document, or job.

82 82 Output Connector Settings dialog box SMS output connector settings Sending SMS messages via a mobile phone and an SMS Server. Windows and UNIX. URI User name Password Output mode The URI that identifies the SMS Server. For example ipp://wtregh09/smsout Must be the same URI as specified for the SMS Server (SMS spooler device) in the Control Center. User name to associate with jobs sent from this connector. N/A Select to generate output per Process, Document, or job. Runtime specific settings Name Number Service Center Retries Message Type The recipient s name. The recipient s mobile phone number, including country code. If you enter several numbers, you must separate the numbers with semi-colon(;). For example: ; Applicable only if you want to use a number other than the default service center number for the recipient(s). The time the service center should try to re-send messages that fail. The message type. SMS Provider output connector settings Sending SMS messenger via an external service provider (Telia). Windows and UNIX.

83 Output Connector Settings dialog box 83 Account Password Address CA Certificate Output mode The account number provided by Telia. The password for accessing the account. Provided by Telia. The service provider URL: The CA certificate provided by telia. Select to generate output per Process, Document, or job. Runtime specific settings Recipients The recipient s mobile phone number. If you enter several numbers, you must separate the numbers with semi-colon(;). For example: ; SMTP output connector settings Comments: Sending output to an SMTP server. The data recipient, for example another Communication Server, will in turn retrieve the information from the SMTP server. This is similar to communication via HTTP. The main difference is that the data recipient does not have to be up and running when the output is sent out. You must specify the recipients, normally one or more mail boxes, of the output sent to the SMTP server. You must use the SetDestPath script function to specify the recipients. For example: SetDestPath("[email protected];[email protected]"); SetDestPath($ ); Windows and UNIX. Mail server Return Address The IP address or host name of the SMTP server. The address to which the SMTP server will report errors.

84 84 Output Connector Settings dialog box SMTP (MIME) output connector settings Sending output via SMTP (MIME) . Windows and UNIX. Mail server Mail server user name Mail server password Alternate mail server Domain name Number of retries Retry interval Sign Encrypt Output mode The IP address or host name of the regular mail server. For example: mail.domain.com User name for accessing the SMTP mail server. Password for accessing the SMTP mail server. The IP address or host name of an alternative mail server. Used if the regular mail server does not respond. The domain from which the Communication Server sends the . For example: streamserve.com The Domain Name must be a name accepted by the mail server. A mail server is normally configured to serve a specific domain. The number of times to try to reconnect if the mail server does not respond. The interval (seconds) between the retries. Select whether or not you want the Communication Server to sign s (S/MIME). Select whether or not you want the Communication Server to encrypt s (S/MIME). Select to generate output per Process, Document, or job. Runtime specific settings Edit Mail Ignore missing attachments Attachment name Open the editor. Select whether or not you want the Communication Server to send an if an attachment is missing. The name of the attachment that contains the output from the Process. For example: $custno.pdf

85 Output Connector Settings dialog box 85 Runtime specific settings Convert PCL to PDF Compress Attachment MIME Type Predefined MIME Type Custom MIME Type Code page MIME Encoding Select whether or not to convert PCL attachments to PDF. Select whether or not to compress the attachments. The MIME type (content-type) of the attachment. Autoselect The Communication Server determines which MIME type to use. The information is retrieved from the driver that generates the attachment file. Predefined Select the MIME type from a list. Custom Specify a custom MIME type. Select the MIME type from a list. Specify a custom MIME type. Code page for the . MIME encoding for subject, body, and attachments. Default Quoted Printable for subject and body. Base64 for attachments. None No encoding for the subject. The maximum number of characters in the subject is 65. No encoding for the body. Base64 for attachments. Quoted Printable Quoted Printable for subject, body, and attachments. Base64 Base64 for subject, body, and attachments. Edit Mail settings From, To, Cc, Bcc, and Subject Reply to Display name Standard attributes. Used by the client instead of the From address when responding to an . The From address will be replaced by this name when the is delivered. This functionality must be supported in the client.

86 86 Output Connector Settings dialog box Edit Mail settings Request receipt Attachments Request a read receipt from the recipient. A notification is received when the recipient reads the provided that this functionality is supported by the servers and clients. Attached files (not Process output). Use the Add/ Edit buttons to specify the Mail Attachment settings. Mail Attachment settings Attachment Attachment name MIME Type Convert attachment from PCL to PDF Compress attachment The path to file to attach. The name of the attachment, for example pricelist.pdf. Leave this empty if you want the attachment name to be the same as the name of the source file. The MIME type (content-type) of the selected attachment. Predefined Select the MIME type from a list. Custom Specify a custom MIME type. Select whether or not to convert PCL attachments to PDF. Select whether or not to compress the attachments. SMTP (MIME) for MailOUT output connector settings Sending output from MailOUT via SMTP (MIME). Windows and UNIX. Mail server Mail server user name Mail server password The IP address or host name of the regular mail server. For example: mail.domain.com User name for accessing the SMTP mail server. Password for accessing the SMTP mail server.

87 Output Connector Settings dialog box 87 Alternate mail server Domain name Number of retries Retry interval Sign Encrypt The IP address or host name of an alternative mail server. Used if the regular mail server does not respond. The domain from which the Communication Server sends the . For example: streamserve.com The Domain Name must be a name accepted by the mail server. A mail server is normally configured to serve a specific domain. The number of times to try to reconnect if the mail server does not respond. The interval (seconds) between the retries. Select whether or not you want the Communication Server to sign s (S/MIME). Select whether or not you want the Communication Server to encrypt s (S/MIME). SNMP trap output connector settings Sending SNMP traps to Network Management Systems. Windows and UNIX. Trap destination Trap destination IP port Community string Source description The IP address or hostname of the NMS. The port on which the NMS receives SNMP traps. Password used by the Communication Server to authenticate itself to the NMS. A description of the source sending the notifications. Spool output connector settings Sending output to a printer. Windows.

88 88 Output Connector Settings dialog box To Output mode The printer to send output to. Select to generate output per Process, Document, or job. StdOut output connector settings The StdIn and StdOut connectors enable external applications to send data to StreamServe via StdIn and receive output on StdOut. Windows and UNIX. There are no settings for this type of connector. StreamServe External Viewer output connector settings Example: Sending output to a Preview Server. The Preview Server reads the file extension and opens the output file in the corresponding application (*.pdf in Acrobat Reader, etc.). The Preview Server recognizes the following formats: pdf, ps, tif, dcx, html, xml, pcl. It tries to open other formats as *.txt. You have two Processes one default Process that you connect to an output connector, and one identical preview Process that you connect to a StreamServe External Viewer connector. An Event script determines which Process to use: if($var = "Preview") callproc("previewprocess"); else callproc("defaultprocess"); Windows. Host Port The Preview Server host. The port the Preview Server listens to. The default port is 9343.

89 Output Connector Settings dialog box 89 Output mode Select to generate output per Process, Document, or job. TCP/IP output connector settings Enabling the Communication Server to send output to a TCP/IP address anywhere on the system or network. Windows and UNIX. Host The receiving host. Port The port the host listens to. The default port is Output mode Select to generate output per Process, Document, or job. TFS output connector settings Sending output via TFS. Windows and UNIX. TFS installation directory Output mode The TFS installation directory. Select to generate output per Process, Document, or job. Runtime specific settings Edit Mail Ignore missing attachments Attachment name Convert PCL to PDF Compress Open the editor. Select whether or not you want the Communication Server to send an if an attachment is missing. The name of the attachment that contains the output from the Process. For example: $custno.pdf Select whether or not to convert PCL attachments to PDF. Select whether or not to compress the attachments.

90 90 Output Connector Settings dialog box Runtime specific settings Code page Code page for the . Edit Mail settings From, To, Cc, and Subject Attachments Standard attributes. Attached files (not Process output). Use the Add, Edit buttons and specify the Mail Attachment settings. Mail Attachment settings Attachment Attachment name Convert attachment from PCL to PDF Compress attachment The path to the file to attach. The name of the attachment, for example pricelist.pdf. Leave this empty if you want the attachment name to be the same as the name of the source file. Select whether or not to convert PCL attachments to PDF. Select whether or not to compress the attachments. TFS for MailOUT output connector settings Sending output from MailOUT via TFS. Windows and UNIX. TFS installation directory The TFS installation directory. Topcall output connector settings Enabling the Communication Server to send fax and output via TOPCALL. Windows and UNIX.

91 Output Connector Settings dialog box 91 TOPCALL To Directory TOPCALL Attachment Directory The destination for address information. The destination for the Communication Server output files. WebSphere MQ output connector settings Sending output via an IBM WebSphere message queue. See Dependencies and requirements on page 93 before you configure the connector. Windows and UNIX. Queue manager Queue name Message persistence Max. message size Allow queue manager segmentation Allow application segmentation The queue manager that owns the message queue. The message queue to which to write data. AS_Q_DEF use the same message persistency as the default specified for the queue used. Yes write the message to disk. The message will be recoverable in case of system failure. No process the message in memory. This will improve performance at the expense of security. The maximum message size that the Communication Server can send without message segmentation (platform dependent). Default is 4Mb. Yes enable the Queue Manager to segment the message. This could be necessary if the message is routed between different platforms and the message exceeds Max message size on a specific platform. No the Queue Manager will not segment the message. Yes if data content is larger than the maximum message size, the Communication Server will divide the data into several smaller messages. No if data content is larger than the maximum message size, no data is sent to the message queue and an error message is written to the log.

92 92 Output Connector Settings dialog box Message format Output mode String enable the Queue Manager to convert the message data to the character format used on the platform that receives the message. None disable the message data conversion. If a code page is specified, the data will be converted to this code page regardless of the Message Format setting. Select to generate output per Process, Document, or job. Runtime specific settings Message type Message ID Correlation ID Select a message type so that the receiving application can determine how to handle the message. Request an answer to the message is expected. If selected, you must set the ReplyToQ and ReplyToQMgr properties on the Custom tab. See Custom options below. Reply the message is a reply to a request message. Datagram no answer to the message is expected. Report a receiving application or a Queue Manager can report the message status to the sending application, depending on how the report properties on the received message have been set. Enter a message id to enable sending and receiving applications to correlate messages. Maximum length is 24 characters. Enter a correlation ID for example if you are sending a reply message, and want the receiver to know which message you reply to. Use the Message Id from the request. The maximum length is determined by the environment variable MQ_CORREL_ID_LENGTH. The recommended value is 24. You can specify the following additional runtime parameters on the Custom tab. Parameter Report Option Description Refer to the WebSphere MQ documentation for information about available Report Options. Must be long integer format (hexadecimal or decimal). For example: QueueOption "Report Option" "0x101c000"

93 Output Connector Settings dialog box 93 Parameter ReplyToQ ReplyToQMgr Description The queue to reply to if a request message is sent or if any report options are set. For example: QueueOption "ReplyToQ" "pdfq" The queue manager that the reply queue in the ReplyToQ field belongs to. For example: QueueOption "ReplyToQMgr" "QM_Strs" Dependencies and requirements The IBM WebSphere MQ environment The IBM WebSphere MQ environment must be installed on the same host as the Communication Server, and the IBM WebSphere MQ configuration must be done using IBM WebSphere MQ specific tools. Asynchronous messaging The WebSphere MQ output connector only supports asynchronous messaging. Defining a client-connection channel You must define a client-connection channel that specifies the name of the MQI channel, the communication type, and the WebSphere MQ Server address. The name of the MQI channel must be the same as the name of the server-connection channel defined on the WebSphere MQ Server. You can define the clientconnection channel using the environment variable MQSERVER, as shown in the example below. For more information, see the IBM WebSphere MQ documentation. Example 6 Defining client-connection channel SET MQSERVER=CHANNEL1/TCP/<WebSphere MQ server address> Startup arguments You must add -webspheremq to the argument file. WinFaxAdapter output connector settings Enabling the Communication Server to send fax via WinFax. Windows.

94 94 Output Connector Settings dialog box Temporary File Path Attachment Expire by Days Days Output mode The destination for the output files from the Communication Server. Enable deletion of output files. Number of days the output files are stored in the output directory. Select to generate output per Process, Document, or job. XTrade output connector settings Enabling the Communication Server to act as an XTrade client and send output to an XTrade server. XTrade is a product for integrating business processes and information systems. XTrade makes it possible for different information systems on different platforms to communicate with each other. See Windows and UNIX. XTrade server Default contract Client name Acknowledge DN Acknowledge PN The IP address or host name of the XTrade server. The default contract name. The IP address or host name of the host on which the Communication Server is installed. Enable DN acknowledgements. The DN acknowledgement is sent when the receiving XTrade server has received the message. If enabled, StreamServe will wait until the Acknowledge Timeout has expired before marking the output as successfully sent. Enable PN acknowledgements. The PN acknowledgement is sent when the receiving client has received the message. If enabled, StreamServe will wait until the Acknowledge Timeout has expired before marking the output as successfully sent.

95 Output Connector Settings dialog box 95 Acknowledge timeout (s) Use EDI-MGR header Output mode The number of seconds the Communication Server waits for DN and PN acknowledgements from the XTrade server. Only applicable when the output is created for E- Faktura, a Swedish electronic invoice format. Select Yes if you want to insert an EDI-MGR Header in each message. You specify EDI-MGR Header fields in the Runtime settings. Select to generate output per Process, Document, or job. Runtime specific settings Contract EDI-MGR Sender Code EDI-MGR Receiver Code EDI-MGR Message Type The contract name. Overrides Default Contract in the Platform. The Sender Code to use. The Sender Code is normally an EAN code. The Receiver Code to use. The Receiver Code is normally an EAN code. The message type. General Settings tab Downloading resource files to printers, adding notes, and adding custom commands and keywords. Settings Download File Enable download Note Custom Settings The resource file, e.g. an overlay file, to download to the printer. Select to download the file for each page. Otherwise the file is downloaded only for the first page. Add comments and notes to the current connector. Enter custom keywords or commands.

96 96 Configure Platform dialog box Configure Platform dialog box Specifying interfaces to different types of repositories, services, etc. Job ID tab Dynamic Resources tab Default Repository tab Job Status tab Recording Mode tab Log File tab Custom tab Gateway tab Service Broker tab Notifications tab File Cache tab Job ID tab Configuring the Job ID repository. The repository stores job identifiers that can be used as search criteria in the Job Gateway. Settings Use Job ID repository Alias/Path Server Enable the Job ID repository. An alias or path that points to the location of the repository. The repository is created the first time you run the Project. Path An absolute path, or a path relative to <installation_directory>/server. %(PlatformName) The suggested path is %(PlatformName)/ <repository>. The string %(PlatformName) will be replaced with the name of the Platform. For example: C:/Strs41/Server/PLT22/jobid Alias You can use the Repository Tool to create aliases for repositories. The repository server host. For example, localhost, , wkbg01, etc.

97 Configure Platform dialog box 97 Settings Authentication required User name Password Select if the repository server requires authentication. User name to access the repository. Password to access the repository. Reconnection to repository server On the Custom tab, you can use the keyword DefaultRepositoryFailover to specify how the Communication Server should reconnect to the repository server in case of a network failure. Syntax: where: DefaultRepositoryFailover <n1> <n2> <n3>; <n1> specifies the number of reconnection attempts. If set to -1, the Communication Server will try to reconnect until a connection is successfully established. <n2> specifies the time (seconds) between reconnection attempts. <n3> specifies whether or not the Communication Server will shut down after the last unsuccessful reconnection attempt: If set to 0, the Communication Server will not shut down. If set to any other value, the Communication Server will shut down. Dynamic Resources tab Configuring the Dynamic Resources repository. This repository is used by PreformatIN for storing dynamic overlays. Settings Use Dynamic Resources repository Inherit Default Repository settings Enable the Dynamic Resources repository. Use the settings defined on the Default Repository tab.

98 98 Configure Platform dialog box Settings Alias/Path An alias or path that points to the location of the repository. The repository is created the first time you run the Project. Path for Server mode repositories An absolute path, or a path relative to <installation_directory>/server Path for LOCAL mode repositories An absolute path, or a path relative to <Export_directory>/data/data %(PlatformName) The suggested path is %(PlatformName)/ <repository>. The string %(PlatformName) will be replaced with the name of the Platform. For example: C:/Strs41/Server/PLT22/DynamicResources Alias You can use the Repository Tool to create aliases for repositories. Use repository server Run the repository in server mode. This mode enables: Remote clients to access the repository. Multiple clients to access the repository at a time. If not selected, the repository will be run in LOCAL mode. Server Authentication required User name Password The repository server host. For example, localhost, , wkbg01, etc. Select if the repository server requires authentication. User name to access the repository. Password to access the repository. Default Repository tab Configuring repository settings that can be inherited when configuring other repositories. Settings Define a default repository Enable the default repository.

99 Configure Platform dialog box 99 Settings Alias/Path An alias or path that points to the location of the repository. Path for Server mode repositories An absolute path, or a path relative to <installation_directory>/server Path for LOCAL mode repositories An absolute path, or a path relative to <Export_directory>/data/data %(PlatformName) The suggested path is %(PlatformName)/ <repository>. The string %(PlatformName) will be replaced with the name of the Platform. For example: C:/Strs41/Server/PLT22/default_rep Alias You can use the Repository Tool to create aliases for repositories. Use repository server Run the repository in server mode. This mode enables: Remote clients to access the repository. Multiple clients to access the repository at a time. If not selected, the repository will be run in LOCAL mode. Server Authentication required User name Password The repository server host. For example, localhost, , wkbg01, etc. Select if the repository server requires authentication. User name to access the repository. Password to access the repository. Job Status tab Specifying how to track, report, and store status information. Settings Track status Select whether or not to track job status.

100 100 Configure Platform dialog box Settings Report status Purge status Interval Time unit Purge ID Interval Time unit Storage type Specify when generate a status report. When input is received This type of status report only guarantees that the Communication Server has received input. No failures at a later stage will be reported. When output is queued This type of status report is generated when the Communication Server has processed the input data, and sent the output to an output queue. When delivered from the output queue This type of status report is generated when the Communication Server has delivered the output from the output queue. Select whether or not to purge the status storage. The status storage keeps track of all queue items that belong to the same Strs ID. Keep the status information until all concerned applications have received this information. Also, make sure this information is available if you intend to use the KeepJob keyword to continue with the same Strs ID for different input jobs with the same external ID. Interval for Purge status. Time unit for the purge interval. Select whether or not to delete all queue items, with the same Strs ID, when the status of the entire Strs ID job is set to completed. Interval for Purge ID. Time unit for the purge interval. Select whether to store status and job ID information on disk or in memory. If you select to store this information in memory, the information will be lost when the Communication Server goes down. Status repository settings The Status repository keeps track of all entities that belong to the same StrsId.

101 Configure Platform dialog box 101 Settings Alias/Path Use repository server Server Authentication required User name Password An alias or path that points to the location of the repository. The repository is created the first time you run the Project. Path for Server mode repositories An absolute path, or a path relative to <installation_directory>/server Path for LOCAL mode repositories An absolute path, or a path relative to <Export_directory>/data/data %(PlatformName) The suggested path is %(PlatformName)/<repository>. The string %(PlatformName) will be replaced with the name of the Platform. For example: C:/Strs41/Server/PLT22/StatRep Alias You can use the Repository Tool to create aliases for repositories. Run the repository in server mode. This mode enables: Remote clients to access the repository. Multiple clients to access the repository at a time. If not selected, the repository will be run in LOCAL mode. The repository server host. For example, localhost, , wkbg01, etc. Select if the repository server requires authentication. User name to access the repository. Password to access the repository. Names repository settings The Names repository maps StrsIDs to external job IDs

102 102 Configure Platform dialog box Settings Alias/Path Use repository server Server Authentication required User name Password An alias or path that points to the location of the repository. The repository is created the first time you run the Project. Path for Server mode repositories An absolute path, or a path relative to <installation_directory>/server Path for LOCAL mode repositories An absolute path, or a path relative to <Export_directory>/data/data %(PlatformName) The suggested path is %(PlatformName)/<repository>. The string %(PlatformName) will be replaced with the name of the Platform. For example: C:/Strs41/Server/PLT22/NamesRep Alias You can use the Repository Tool to create aliases for repositories. Run the repository in server mode. This mode enables: Remote clients to access the repository. Multiple clients to access the repository at a time. If not selected, the repository will be run in LOCAL mode. The repository server host. For example, localhost, , wkbg01, etc. Select if the repository server requires authentication. User name to access the repository. Password to access the repository. Recording Mode tab Generation of grab files. In record only mode the Communication Server uses input data from a designated input connector to produce grab files. Settings Activate recording mode Lines Run the Communication Server in record only mode. Number of lines in the input data to record.

103 Configure Platform dialog box 103 Settings Columns Input connector Number of columns in the input data to record. The designated input connector. Log File tab Truncation of the Communication Server s log file. Settings Age restrictions Maximum age Create new log file at Size restrictions Maximum size Move old log files to Select if you want the Communication Server to start writing to a new log file after a specific number of days. The maximum number of days the Communication Server will write to the same log file. The time of the day when the Communication Server will start writing to a new log file. Select if you want the Communication Server to start writing to a new log file when the current log file reaches its maximum size. The log file s maximum size (MB). To store old log files, you must specify a directory. Custom tab Gateway tab Adding custom commands and keywords to the Platform. The Communication Server can have functionality that is not implemented in the Design Center. You can add commands and keywords to the Platform in order to use this functionality. Specifying job gateway settings. Settings Allow remote client to connect to gateway Protocol Allow clients to access the queue repositories. HTTP or HTTPS.

104 104 Configure Platform dialog box Settings TCP/IP Port Gateway URL Password The port on the Communication Server host assigned to the job gateway. This is the same port as that defined when configuring the job gateway. This port must be unique for each Communication Server running on the same host. Information for the Control Center about which URL to use to access the job gateway. Use the following syntax: jobgateway/access For example: The password to access the queue repositories. This is the same password as that defined when configuring the job gateway. Service Broker tab Configuring how to connect to a Service Broker. This is described in the Service Broker documentation. Notifications tab Enabling notifications, and configuring publishing and storage of notifications. Note: Notifications cannot be handled correctly in a shared queue environment. Settings Use notifications Store notifications Enable the Communication Server to generate notifications. Store notifications in the notifications repository. Notification interval Interval (ms) between notifications. Unlimited number of jobs Maximum number of stored jobs Publish service Do not limit the size of the repository. The maximum number of stored jobs. When the limit is reached, the oldest notifications (job) will be removed. Select if you want to display the notifications in the Control Center.

105 Configure Platform dialog box 105 Settings Authentication required User name Password Select if the repository server requires authentication. User name to access the repository. Password to access the repository. File Cache tab Caching XML and DTD documents. This is described in the XMLIN documentation.

106 106 Configure Platform Export dialog box Configure Platform Export dialog box Specifying the Java User Class path, and for specifying arguments in the startup argument file. Paths tab Arguments tab Paths tab Specifying the argument file and the Java User Class path. Settings Java User Class Path Absolute path to the Java User Class directory where the Java User Classes are located. Arguments tab Specifying arguments in the startup argument file that will be generated when you export the Project. Settings Name/Value list Edit Custom Preview Select and configure the applicable startup arguments. Add custom arguments at the beginning or end of the argument file. Preview the argument file.

107 Manage Queues dialog box 107 Manage Queues dialog box Configuring queues. Shortcut menu in list Add Delete Rename Set as Default Input Queue Set as Default Output Queue Add a new queue. Same as the Add button. Delete a queue. Same as the Delete button. Rename the selected queue. Select a queue as the default input queue. Select a queue as the default output queue. Queue type Repository Indexed file Select to use repository queues. Select to use indexed file queues. Tabs Location tab Queuing tab Advanced tab Recovery tab. Custom tab

108 108 Manage Queues dialog box Location tab Settings (Repository queue) Inherit Default Repository settings Alias/Path Use repository server Use the Default Repository settings defined in the Configure Platform dialog box. An alias or path that points to the location of the repository. The repository is created the first time you run the Project. Path for Server mode repositories An absolute path, or a path relative to <installation_directory>/server Path for LOCAL mode repositories An absolute path, or a path relative to <Export_directory>/data/data/queues %(PlatformName) The suggested path is %(PlatformName)/<repository>. The string %(PlatformName) will be replaced with the name of the Platform. For example: C:/Strs41/Server/PLT22/InQ Alias You can use the Repository Tool to create aliases for repositories. Run the repository in server mode. This mode enables: Remote clients to access the repository. Multiple clients to access the repository at a time. If not selected, the repository will be run in LOCAL mode. Server Username Password The repository server host. For example, localhost, , wkbg01, etc. Username to access the queue repository. Password to access the queue repository. Settings (Indexed file queue) File name Alias/Path The queue file. Path to the directory in which the queue file is located.

109 Manage Queues dialog box 109 Queuing tab Settings Store successful jobs Store failed jobs Retries Retry delay Unlimited number of stored jobs Maximum number of stored jobs What to store when a job has been successfully sent through the queue. No Store nothing. Store information only Store information about the job. Store information and job Store information about the job, and the job itself. Allows the queue to resend the job more than once. What to store when a job has not been successfully sent through the queue. No Store nothing. Store information only Store information about the job. Store information and job Store information about the job, and the job itself. Allows the queue to resend the job more than once. Number of times the Communication Server will try to reprocess a failed job. Time (milliseconds) the Communication Server will wait before it tries to reprocess a failed job. Do not limit the number of stored jobs. The maximum number of stored jobs. When the limit is reached, the oldest job will be overwritten.

110 110 Manage Queues dialog box Recovery tab. Settings (Repository queue) Lost job behavior Delay before retry or aborts On lost repository server connection Used for specifying how to handle a running job if the Communication Server goes down. Only available for repository queues running in server mode (Use repository server and Server properties on the Settings tab). Used in a shared queue environment with multiple Communication Servers. Retry If the original Communication Server comes up before the time specified in Delay before retry or aborts, the original Communication Server will continue to process the job. If the time specified in Delay before retry or aborts has elapsed, the job will be reprocessed, either the original or a different Communication Server (original or other). Abort If the original Communication Server comes up before the time specified in Delay before retry or aborts, the original Communication Server will continue to process the job. If the time specified in Delay before retry or aborts has elapsed, the job will be aborted. Time (seconds) before Retry or Abort. Only available to repository queues running in server mode (Use repository server and Server properties on the Settings tab). Used for specifying how the Communication Server should reconnect to a repository queue in case of failure. The Communication Server can reconnect either to a backup repository server, or to the original repository server if it comes up again. Do not attempt recovery The Communication Server will not try to reconnect to the repository server. Attempt recovery forever The Communication Server will try to reconnect to the repository server (original or backup) until a connection has been successfully established. Attempt recovery a limited number of times The Communication Server will make <x> number of Reconnection attempts to the repository server (original or backup).

111 Manage Queues dialog box 111 Settings (Repository queue) Reconnection attempts Time between attempts Used with Attempt recovery a limited number of times to specify the number of reconnection attempts to the repository server. If the Communication Server fails to reconnect after the last attempt, it will shut down. Time (seconds) between reconnection attempts.

112 112 Manage Queues dialog box Advanced tab Settings Threads Process jobs Schedule spooling Spooling interval Spool for a limited time Days Hours Minutes Seconds Stop if the queue is empty The maximum number of job threads you want the queue to use. The Communication Server can operate several queued jobs at the same time. The scenario where this is an advantage is when a large job is followed by a small job. With one single thread, the small job must wait for the large job to be completed. Note: Each thread consumes system resources. On arrival Process jobs as soon as possible. When parent completed Hold all job children in the queue until the parent job is successfully processed. If the parent job fails, all its children will be removed. Schedule the output from the queue. For example, if an output queue contains jobs that will be faxed, you can put the jobs on hold and wait for low peak hours. Specify spooling intervals. Limit the spooling interval. Number of days for the limit. Number of hours for the limit. Number of minutes for the limit. Number of seconds for the limit. Stop spooling if the queue is empty. Custom tab Used for adding custom commands and keywords. The Communication Server can have functionality that is not implemented in the Design Center. You can add commands and keywords to the queue in order to use this functionality.

113 Scheduler Configuration dialog box 113 Scheduler Configuration dialog box Scheduling events such as polling intervals, spooling of queues, etc. Intervals Add one or more intervals, and specify amount and unit for each interval. Apply selected Select an interval in the Intervals area, and specify when to apply this interval. No entries in this area is the same as always. Apply all You can optionally specify when to apply the settings above.

114 114 Scheduler Configuration dialog box

115 115 Message window Shortcut menu commands Add Event Add Process Add Resource Sets Remove Resource Set File Properties Add an Event. Add a Process. Add one or more resource set to the Message. Remove the selected resource set from the Message. Display the path to the Message file. Event Settings dialog box Configuring agent settings and Event order for an Event. Agent Settings tab Event Order tab Agent Settings tab Specifying agent settings per input type. Used with XMLIN and StreamIN Events. Agent (StreamIN) Only for Connectivity Packs. See the corresponding documentation.

116 116 Event Settings dialog box Message window FieldIN (StreamIN) Description resource Description ID The description file resource. The ID of the description file. Specified by the FIELDIN keyword in the first line in the description file (case sensitive). RecordIN (StreamIN) Description resource Description ID The description file resource. The ID of the description file. Specified by the STREAMIN keyword in the first line in the description file (case sensitive). StrsXML and XML (StreamIN) Only for Projects created in StreamServe and older versions. See the corresponding documentation. XMLIN Collect entire documents Validation level XSD mapping table XML error connector Expand external entities Select to collect entire documents. The collection methods are described in the XMLIN documentation. Select how to validate XML input. Described in the XMLIN documentation. A table resource containing namespace to schema location mappings. Used when validating input against an XSD. A connector that will handle output in case of a validation error. Incoming XML documents can have references to external XML documents. You can include the external documents in the Event.

117 Event Settings dialog box 117 Message window Event Order tab Specifying the order of Events when merging Events. Event Order options First Repeating Last Always starts a new Message. Comments If there is no following Event, or if the following Event is also set to First, this will be the only Event in the Message. Appends the Event to the Message. Comments If there is no previous Event, this Event will be the first Event in the Message. If there is no following Event, this will be the last Event in the Message. Appends the Event and ends the Message. Comments If there is no previous Event, this will be the only Event in the Message.

118 118 Event Settings dialog box Message window

119 119 Runtime configuration window Runtime Input Connector Settings dialog box Specifying Runtime settings for input connectors. Input Analyzer tab General tab Input Analyzer tab Managing the Input Types handled by the connector.

120 120 Runtime Input Connector Settings dialog box Runtime configuration window Settings Input Type Handle XML-based input before StreamIN Filter Chain Edit parameter View Events Add Filter Chain Move Lists all input types the connector is expected to receive. The list is automatically updated when the connector is connected to a new input type (Event). There are three groups of input types: Group 1 XML formats. Group 2 FieldIN, RecordIN, and Input Analyzer enabled Agents. Group 3 PageIN. PageIN must always be the last item in the list, but you can select whether to have Group 1 or Group 2 as the first group in the list. Select whether to have Group 1 or Group 2 as the first group in the list. The name of the filter chain (if any) used for the corresponding input type. For Connectivity Packs. See the corresponding documentation. Select an input type and list the names of all corresponding Events. Select an input type and add a filter chain. Select an input type and move it up or down. General tab Adding notes, and customizing the connector. Settings Note Custom Settings Comments and notes related to this connector. Commands and keywords.

121 Runtime Event Settings dialog box 121 Runtime configuration window Runtime Event Settings dialog box Specifying Runtime options for an Event. General tab Code Page tab General tab Specifying general options for the Event. Settings Custom Priority Select automatically Agent driven Ignore remaining data Enter commands and keywords to be applied to the Event. The priority level for the Event. The higher the number the lower the priority. Applicable only if two or more Events within a job are triggered by the same pattern. Specifies that this Event will only be activated by a NewJob scripting function. See the Scripting reference. Applicable only to Connectivity Packs. See the corresponding Connectivity Pack documentation. Specifies that this Event will search for a matching pattern in the input job., and when it finds the pattern it will skip the remaining input data. Used, for example, when transmitting the entire input job via a RedirectOUT Process. The pattern must be extracted to identify the data to be transmitted, but the actual data is sent as it is to the RedirectOUT Process. Code Page tab Specifying code page options for the Event. See the Code pages and Unicode support in StreamServe documentation for information. Code page options No change Lookup The input connector settings, or a script, specifies which code page to use. A lookup table is used to determine which code page to use.

122 122 Runtime Event Settings dialog box Runtime configuration window Code page options Variable Input order A variable is used to determine which code page to use.. Specifies the ordering of characters in bidirectional input text. Logical order keep this option if the input does not contain Arabic or Hebrew text in visual order. Visual order (Arabic and Hebrew only) select this option only if the input contains Arabic or Hebrew text in visual order. The text will be reordered to logical order.

123 Runtime Process Settings dialog box 123 Runtime configuration window Runtime Process Settings dialog box Specifying Runtime options for a Process. Rule tab General tab RePRINT tab Rule tab Creating rules for triggering a Process. A rule accepts the operators AND, OR, and NOT. Example 7 Use patterns in the Event to trigger the Process Rule: idinvoice1 AND idinvoice2 Result: The Process is run only if the Event contains both patterns idinvoice1 and idinvoice2. Example 8 Use variables in the Process to trigger the Process Rule: $page=3 OR $page=4 Result: The Process is run only if the variable $page equals 3 or 4. Example 9 Use a connector name to trigger the Process The before script $InConnector=InConnectorName(); has been added to the Event. Rule: $InConnector=Input1 Result: The Process is run only if input comes from the connector Input1. General tab Specifying general options for the Process. Standard settings Select automatically Custom settings Specifies that this Process will only be activated by a CallProc scripting function. See the Scripting reference. Enter scripts and commands to customize the Process.

124 124 Runtime Process Settings dialog box Runtime configuration window PageOUT specific settings Mirror PageOUT Mirror variable Select to mirror the object layout in PageOUT. Use a variable to decide whether or not to mirror the object layout. If no variable is specified, the layout will always be mirrored if you select Mirror PageOUT. The variable must return 0 or 1: 1 layout will be mirrored. 0 layout will not be mirrored. MessageOUT specific settings Include variables in output Select if you want to include variables specified in scripts in the output. Restrictions: You cannot include arrays in the output data. Variables specified after Process or after Message cannot be included in the output. Attach Process tab Applicable to MailOUT Processes only. Specifies Process output to attach to the . Note: To add files on disk as attachments to the , you must specify this in the MailOUT Process configuration. Click Add New Item to specify a new attachment, or select an attachment and click Edit Selected Item to edit the attachment settings. Process Attachment options (Process Attachment dialog box) Attachment name Process attachment Free attachment The name of the attachment, for example Invoice.pdf. Select this option, and use the Select Process dropdown list to specify the Process. Select this option, and use the Free Attachment field to specify the Process.

125 Runtime Process Settings dialog box 125 Runtime configuration window Process Attachment options (Process Attachment dialog box) Mime content type Convert attachment from PCL to PDF Compress the attachment The MIME content type of the attachment (only applicable to SMTP mail servers). Autoselect - the Communication Server determines which content-type to use. The information is retrieved from the driver that generates the attachment file. Predefined - select content-type from a predefine list. Custom - specify a custom content-type. Select whether or not to convert PCL attachments to PDF. Select whether or not to compress the attachments. RePRINT tab Specifying document types and indexes for RePRINT. Activation options Disabled Enabled On Failure Disable RePRINT storage for the Process. Enable RePRINT storage for the Process. A copy of the output data and an index file will be sent to the RePRINT scanning directory. Enable RePRINT storage only for Process data that could not be delivered to the output connector. Object type settings Name Indexes Index name The document type to be stored. Can contain any alphanumeric character, including space. Maximum 55 characters. A list of the indexes available for the specified document type. The name of the index to be used when searching for stored objects in the RePRINT database. Can contain any alphanumeric character. Maximum 50 characters

126 126 Runtime Process Settings dialog box Runtime configuration window Object type settings Data type Variable Numeric Any positive or negative numerical value. Text Any alphanumeric character. Date Date format. Must match the date settings allowed in the RePRINT database. A unique variable for the index.

127 Connector Selection Method dialog box 127 Runtime configuration window Connector Selection Method dialog box Selecting an output connector for the Process output. Options None Static Lookup Variable Do not send the output to any connector. Select a specific connector. The Process will always send the output to this connector. Use a lookup table to determine which connector to send the output to. Key The key variable used for selecting the connector. Table The lookup table. Default connector The default connector. The output is sent to this connector if the key variable does not match any value in the lookup table. Lookup table syntax Use the following syntax in the lookup table: key_value For example: "Mike Jones" "Jane Smith" alternative_connector Printer1 Printer2 Use a script variable to determine which connector to send the output to. Variable The script variable used for selecting the connector. Default connector The default connector. The output is sent to this connector if the variable does not match any other connector.

128 128 Edit Output Connector Settings dialog box Runtime configuration window Edit Output Connector Settings dialog box Selecting a context for the connector configuration. Options Process: name Job: name Configure Process specific connector settings. You can also configure connector settings that will be applied to the job that contains the selected Process. Configure job specific connector settings.

129 Runtime Output dialog box 129 Runtime configuration window Runtime Output dialog box Specifying Runtime options for an output connector. Job Begin icon Device Driver Settings tab Device symbol set tab Document Trigger icon Document Trigger tab Document Begin icon Device Driver Settings tab Device symbol set tab Process Begin icon Device Driver Settings tab Device symbol set tab Connector tab Document End icon Process Sort Definition tab Connector tab Job End icon Connector tab Post-processing specific You can also configure post-processing specific options. See the Document sorting and bundling documentation for information. Device Driver Settings tab Specifying device driver settings. You must select the device driver when you configure the connector in the Platform.. Settings Driver settings Alias Device specific settings. See the documentation for the corresponding device. You can specify an alias for each driver option.

130 130 Runtime Output dialog box Runtime configuration window Device symbol set tab When sending output to a PCL printer, you can specify a different symbol set for the printer than that specified in the code page settings.. Settings Override symbol... Static Lookup Variable Select to override the symbol set. Select a static symbol set. Use a lookup table to determine which symbol set to use. Use a variable to determine which symbol set to use. Document Trigger tab Defining a Document trigger for the connector and job. Settings Document Trigger variable The variable to be used as the Document trigger. Must be a variable specified in the corresponding Messages. Connector tab Configuring the runtime connector setting. Settings Connector specific Connector specific settings. Process Sort Definition tab The Communication Server creates Documents according to the Document trigger. You can use sort keys to specify the order of the pages in the Document.. Options Edit Process Sort Definition Open the Sort Definition dialog box.

131 Sort Definition dialog box 131 Runtime configuration window Sort Definition dialog box Settings Sort Key Type Sort Order A variable specified in the Messages (Event or script). Specify whether the sort key is a number or a string. Select to sort the pages in Ascending or Descending order.

132 132 Sort Definition dialog box Runtime configuration window

133 133 Resource set window Shortcut menu commands on root object and folders New Resource Add Resource Import Settings Export Settings Delete Create a new resource file using a resource editor, and link it to the resource set. Link an existing resource file to the resource set. Create a new resource file and link it to the resource set. You create the resource file by importing and embedding a source file. Specify where to store new resources files, and how to resolve name conflicts. See Resource Folder Settings dialog box on page 135. Specify export paths for custom resource types. See Resource Folder Export Settings dialog box on page 136. Delete a custom resource folder.

134 134 Resource set window Shortcut menu commands on root object and folders Rename Rename. If you rename the root folder, you also rename the resource set. You cannot rename native resource folders. Shortcut menu commands on resource objects Start Editor Stop Editor Update from origin Extract to file File Properties Open the resource editor and edit the resource. Close the resource editor. Import updated information from the source file. Applicable only to resources created using the Import command. Extract the resource to a file. Display the path to the selected object.

135 Resource Folder Settings dialog box 135 Resource set window Resource Folder Settings dialog box Specifying where to store new resources files, and how to resolve name conflicts. Options Use default storing rules Default target folder Reuse existing resource Prompt Overwrite the existing resource Resolve conflict Select to use the default rules for storing resource files. If you edit the resource file from a resource set within a Project, the default path for the resource files is the root directory for the Project. If you try to overwrite an existing resource you will be prompted. If you edit a resource file from a stand-alone resource set you will be prompted for path and name. Default folder for storing the resources. Keep the old resource file and ignore the new. Prompt when trying to overwrite an exiting resource file. Replace the old resource file with the new. Keep the old resource file and add a number to the name of the new resource.

136 136 Resource Folder Export Settings dialog box Resource set window Resource Folder Export Settings dialog box Specifying the export path for resource files in custom resource folders. Options Export to base directory Export to same directory as Do not export Export the resources to the export directory. Select a native resource type, and export the resources to the same directory. Do not export the resources.

137 Resource selection browser 137 Resource set window Resource selection browser Selecting a resource for a connector etc. You can also add and edit resources. Contents Look in Item Note Selected Filter Select Undo select Open editor Close editor Add Resource Set Browse to the appropriate resource set and resource folder. The name of a resource. All resources in the selected folder are displayed in the list. Notes written for the item. Right-click the item and select Edit Notes to edit the notes. Displays the selected resource. Enable/disable the resource filter. When the filter is disabled, all resource folders will be visible. Select the resource (copy from the Items list to the Selected list). Undo resource selection (remove from the Selected list). Select a resource in the Items list and open the resource in the resource editor. Close the resource editor. Add a resource set to the active object (Platform, Message, or resource set).

138 138 Resource selection browser Resource set window Contents Create Resource Set New resource Add resource Import Create a new resource set and add it to the active object (Platform, Message, or resource set). Create a new resource file using a resource editor, and link it to the resource set. Link an existing resource file to the resource set. Create a new resource file and link it to the resource set. You create the resource file by importing and embedding a source file.

139 139 Filter Chain editor Creating filter chain resources files. Components Flow bar Filter icons Property/Value Add one or more filters to the flow bar. The order of the filters in the chain is important. Data flows through the filters from left to right as you see them in the flow bar. Each filter is represented by a filter icon. Settings for the selected filter. Input connector filters Bypass Filter Codepage Filter Decompression Filter External Filter File Filter Internal Filter Job Filter Output connector filters Compression filter

140 140 Input connector filters Filter Chain editor Input connector filters Bypass Filter Use this filter to bypass the Communication Server. Data is sent directly from this input connector to a designated output connector. Settings Start in bypass Bypass connector Initial time-out Bypass time-out Bypass on Remove (bypass on) Bypass off Remove (bypass off) Append output to job Overlay resource Overlay select Remove (overlay select) Overlay trigger If selected, all input received between Communication Server start-up and the first Bypass off trigger will be sent to the bypass connector. The name of the output connector to bypass to. N/A Time-out (seconds). Overrides the ordinary connector time-out Sequence in input data that activates the bypass filter. For example: #bypasson. Select whether or not to remove the Bypass on sequence from output data. Sequence in input data that deactivates bypass mode. For example: #bypassoff. Select whether or not to remove the Bypass off sequence from output data. Allows the output sent to the bypass connector to be treated as a unit. For example, if the bypass connector is a File connector, the output will end up in the same file. Optional overlay to include in the output. Sequence in input data that indicates that here comes an overlay. For example: #ovl Select whether or not to remove the Overlay select sequence from output data. Sequence in input data that indicates the end of the overlay file name. For example: ##

141 Input connector filters 141 Filter Chain editor Settings Remove (overlay trigger) Select whether or not to remove the Overlay trigger sequence from output data. Example 10 Bypass sequences Settings: Bypass on = #ON and Bypass off = #OFF Input data: xyz;#onabc;def;ghi#off;jkl Bypassed data: abc;def;ghi Example 11 Overlay sequences Settings: Overlay select = #OVL and Overlay trigger = ## Input data: abc;def;#ovllogo.prn##ghi;jkl Result: The file logo.prn is sent between #OVL and ##. Codepage Filter Use this filter to specify a code page for the input connector. See the Code pages and Unicode support in StreamServe documentation for information on how to handle code page settings in StreamServe. Settings Code page Input order The code page the connector will use. Specifies the ordering of characters in bidirectional input text. Logical order keep this option if the input does not contain Arabic or Hebrew text in visual order. Visual order (Arabic and Hebrew only) select this option only if the input contains Arabic or Hebrew text in visual order. The text will be reordered to logical order.

142 142 Input connector filters Filter Chain editor Settings Byte order Only for UCS-2. For the UTF-16 encoding schemes, each character code unit is represented by two bytes. When you select UCS-2 as code page, you must also specify the byte order. Most significant byte first (Big Endian): Select when the input is encoded using the encoding schemes UTF-16BE (big endian without byte order mark) or UTF-16 (big endian with or without byte order mark) Most significant byte last (Little Endian): Select when the input is encoded using the encoding schemes UTF-16LE (little endian without byte order mark) or UTF-16 (little endian with byte order mark). Decompression Filter External Filter Use this filter to decompress compressed input data. There are no settings for this filter. This filter reads data from StdIN, processes the data, and delivers the processed data back on StdOUT. The actual filter can be any executable. Settings External The path to the executable. File Filter This filter uses a conversion table to substitute characters in input data. Settings File The conversion table. The conversion table must be available as a resource in the same resource set as the filter chain. Conversion table description Syntax input_string output_string

143 Input connector filters 143 Filter Chain editor Conversion table description Strings Hexadecimal The table applies to strings of one or more characters. You can always use hexadecimal notation within angle brackets (<hex>). Some characters tab, line feed, angle brackets, quotation marks, etc. must have hexadecimal notation. You can use multiple hex values if you separate them with comma. For example: <0D,0A> Empty rows You must comment all empty rows with // or *. Case Example The text strings are case sensitive. // Substitute ALPHA with BETA ALPHA BETA // Substitute line feed with carriage return //and line feed <0A> <0D,0A> // Substitute " with () <22> <28,29> // Substitute \ with / <5C> <2F> Internal Filter This filter handles escape codes in input data. Settings Internal HpPcl: Removes HpPcl escape codes from the input data. Esc0: removes Esc0 escape codes from data. URL: Converts URL escape codes (%20 to space etc.) in input data. Converts & (ampersand) to <0D, 0A> (carriage return - line feed). Converts + (plus sign) to (space).

144 144 Input connector filters Filter Chain editor Job Filter This filter enables the Communication Server to divide a large input job into a several small jobs. Sequences in input data specify the size of each job. Settings Job begin Job end Sequence specifying the beginning of a job. For example: [JOB BEGIN] Sequence specifying the end of a job. For example: [JOB END] Example 12 The Job filter This example displays two scenarios where one large input job is divided into smaller jobs.

145 Output connector filters 145 Filter Chain editor Output connector filters Compression filter Use this filter to compress the output from the connector. See the Code pages and Unicode support in StreamServe documentation for information on how to handle code page settings in StreamServe. Settings Use compression Compression level Select to compress the output from the connector. The level of compression.

146 146 Output connector filters Filter Chain editor