› Output Manager › Sources › Configuring document property profiles › Configure a document properties profile

Configure a document properties profile

Perform this procedure to configure document profiles.

To configure advanced document properties, you must configure one or more of the following profiles:

Configure native header profiles

Complete this procedure to configure native header profiles.

Native headers contain information that arrives as part of the transmission protocol that is used to receive documents.
  1. Open the Document Properties Profile dialog box, if it is not open already.
  2. Next to Native header profile, click New to create a native header profile.
    You can also select a profile in the list and click Edit to make modifications.
  3. Enter the profile Name and Description.
  4. On the Native Headers tab, select one or more of the Output Manager device types whose headers should be available for mapping.
    • Email
    • FTP
    • LPD
    • Network folder
    • Socket
    • WebSphere MQ
    • Windows queue
    • BEPS devices
    The selected native headers will be available on the Document Property Mappings tab and the Document Owner Mapping tab.
  5. Configure the document property mappings.
    See Configuring Document Property Mappings.
  6. Configure the document owner mappings.
    See Configuring Document Owner Mappings.

Configure job ticket profiles

Complete this procedure to configure a job ticket profile.

Job tickets contain information about the document, and/or how the document should be treated. Tickets are logically separate from the document, and in some cases are inserted in front of the document file.
  1. Next to Job ticket profile, click New to create a job ticket profile.
    You can also select a profile in the list and click Edit to make modifications.
  2. Enter the profile Name and Description.
  3. On the Job Ticket tab, in the Type box, select one of the following job ticket types:
    XML Job Ticket An external job ticket template in an XML format. The XML tags are accessible throughout the job ticket profile configuration.
    Spool Header A group of fields that are associated with Output Manager Print Server.
    Output Statement A list of fields associated with the RJE header.
  4. If you selected XML Job Ticket, click Map job ticket, and in the Open dialog box, select one or more sample tickets to create the ticket mappings. If necessary, click Clear mappings to remove any associated job mapping.
    This option is not available for Spool Header and Output Statement tickets, as they have fixed mappings.
  5. Once one or more sample tickets have been mapped, use one of the following methods to search for the job ticket.
    Option Description
    Embedded in the document Searches for the job ticket embedded in a document. To use this option configure the following options:
    1. In the Start of job ticket recognition string box, enter the appropriate string value.
    2. In the End of job ticket recognition string box, enter the appropriate string value.
    3. Use the Remove from document check box to determine if the job ticket data should be removed from the document.
    4. When using job tickets, all lines up to and including the job ticket are deleted from the file. Select the Keep data prior check box to prevent data loss.
    In a separate file Searches for the job ticket in a separate file. To use this option, configure the following options:
    1. In the Folder to search box, click the browse button (...) to choose a folder to search or type the folder location in the box.
    2. In the Match job ticket file name using this document property list, select the appropriate property.
    3. In the Match job ticket extension using this extension box, enter the appropriate file extension.
    4. Use the Delete job ticket file after processing document to determine if the job ticket profile should be deleted after processing.
  6. In the If the job ticket is not found, take the following action list, select how to process the document if the job ticket is not found. You can choose to process the document normally, receive the document and place it in error state, or reject the document.
  7. Configure the document property mappings.
    See Configuring Document Property Mappings.
  8. Configure the document owner mappings.
    See Configuring Document Owner Mappings.

Configure job parsing profiles

Complete the following procedure to configure a job parsing profile.
  1. Next to Job parsing profile, click New to create a job parsing profile.
    You can also select a profile in the list and click Edit to make modifications.
  2. Enter the profile Name and Description.
  3. From the Job Parsing tab, select the Originating printer family from the drop-down list.
  4. Use one of the following methods to search for the printing instructions/job ticket.
    Option Description
    Embedded in the document Searches for the printing instructions/job ticket embedded in a document.
    • Use the Remove from document check box to determine if the job ticket data should be removed from the document.
    • When using job tickets, all lines up to and including the job ticket are deleted from the file. Select the Keep data prior check box to prevent data loss.
    In a separate file Searches for the printing instructions/job ticket in a separate file. To use this option, configure the following options:
    • In the Folder to search box, click the browse button (...) to choose a folder to search or type the folder location in the box.
    • In the Match job ticket file name using this document property list, select the appropriate property.
    • In the Match job ticket extension using this extension box, enter the appropriate file extension.
    • Use the Delete job ticket file after processing document to determine if the job ticket profile should be deleted after processing.
  5. In the If the job ticket is not found, take the following action list, select how to process the document if the job ticket is not found.
    You can choose to process the document normally, receive the document and place it in error state, or reject the document.
  6. Configure the document property mappings.
    See Configuring Document Property Mappings.
  7. Configure the document owner mappings.
    See Configuring Document Owner Mappings.

Configure headers from data profiles

Complete the following procedure to configure a headers from data profile.

Headers from data profiles consist of information that Output Manager can extract from specified location within the actual document data. Output Manager can extract data from documents in various formats including ASCII, ASCII with ASA, S/370, and VBM.
  1. Next to Headers from data profile, click New to create a headers from data profile.
    You can also select a profile in the list and click Edit to make modifications.
  2. Enter the profile Name and Description.
  3. From the Headers from Data tab, select the Data format.
    You can choose ASCII, ASCII with ASA, S/370, or VBM.
  4. In the Code page list, select the code page for the document.
  5. Specify the Extraction method, you can choose one of the following:
    Option Description
    Line-based Searches for the header based on a particular line.
    Record-based Searches for the header based on a particular record, regardless of page breaks.
  6. In the Headers to extract grid, click in the grid to enter the headers to extract.
    These variables will appear on the Document Property Mappings tab and Document Owner Mapping tab.
  7. Enter the following information in each column.
    Option Description
    Line-based
    • Name column — Specifies the header field for the data to be placed in.
    • Page column — Specifies the page where data extraction will begin.
    • Line column — Specifies the line number in the file that contains the data.
    • Column column — Specifies the column where data extraction will begin. For ASCII with ASA carriage control files, the first column is not counted (in other words, the second column is treated as the first column).
    • Length column — Specifies how many characters to extract.
    Record-based
    • Name column — Specifies the header field for the data to be placed in.
    • Record column — Specifies the record number in the file that contains the data.
    • Position column — Specifies the position where the header data will begin.
    • Length column — Specifies how many characters to extract.
  8. Configure the document property mappings.
    See Configuring Document Property Mappings.
  9. Configure the document owner mappings.
    See Configuring Document Owner Mappings.

Configure document property mappings

Complete this procedure to configure the document property mappings for the extraction profile.
  1. Click the Document Property Mappings tab.
  2. To enable a document property mapping, click the Map Values check box for the appropriate property.
  3. Click in the External Field column, to select the mapping from the list shown.
    If necessary, you can use the look up table to adjust the values.
  4. Click in the Unmapped Value Action column to select what happens when there is a missing look up table entry.
    You can choose to skip the property mapping entirely, assign the external value as-is, or assign the unmapped value default.
  5. Click in the Unmapped Value Default column to specify a default value.

Configure document owner mappings

Complete this procedure to specify how the document owner is set.
  1. Click the Document Owner Mapping tab.
  2. Choose one of the following options for setting the document owner.
    Option Description
    Use the Windows user id (if available) Sets the document owner to the Windows user ID. This can be used with the following source types: Windows queue, network folder, and Web file upload.
    Map to the following external field Sets the document owner to external field selected in the drop-down list.
    For Job Ticket tab profiles, the ticket information fields are expressed as XPath statements. XPath statements show the structure of the ticket information. It allows the ability to specify a specific instance of a field if that particular information field occurs more than once in a documents metadata. If a particular external field is not listed in the list, the XPath statement can be directly entered.

    For Headers from Data tab profiles, this list will be populated with the headers specified.
  3. If you chose to map to an external field, use one of the following methods to map the field.
    Method Description
    Use the external value as the OM user name Uses external document property information as the Output Manager user name. Note, when the document is first received by the source the document has existing properties. These properties are called external document property values.
    Use the following lookup profile This is not currently implemented. When implemented, you will be able to use a lookup table to map Personal Identification Numbers to user names.
    Use the following value mappings Uses the values entered in the table for the external document property value. Click directly in the table to enter the mapping values. When the external document property has one of the values listed in the External Field Value column, the value in the Property Value column will be used.
  4. If desired, under If unable to determine the document owner, assign the following user, click the ellipsis button to assign a document owner from the User and Group Selection dialog box.
    This user will be assigned if the document owner cannot be determined using the above mapping settings.
  5. Click OK.