Building generic ODL functions  Using the test drive

Chapter 3: Building Production Objects

Defining production object options

  1. In the TRAN-IDE window, select View | Production Objects or click the Pro-Obj icon. Double-click an existing object in the Production Objects list. The Production Objection Information window opens.

  2. Select Production Object | Options from the menu bar. The Production Object Options window opens.

  3. Complete these fields and options:

    Field (key)

    Description

    Static Scope

    All production objects are static by default. To call a production object with the produce() method from within an ODL function in another module, or to use the production object as part of a filter object, unselect this option to make the production object global.

    Recycle Output As A New Transaction

    Recycle the output of the current production object as input. To have the production object only recycle its output transaction and not send it to a destination as well, map the production object to the NullDest destination.

    Input NDO Serialization

    When processing tree input, select the appropriate input NDO serialization.

    • NCF: Self-describing – the default.

    • NCF: Non-self-describing – select this option if you are generating a format description based on an NCM file generated by Formatter, then enter the file name.

    • XML – select this option if your input message is in an XML format.

    Output NDO Serialization

    When processing tree output, you must select the appropriate output NDO serialization.

    • NCF: Self-describing – the default.

    • NCF: Non-self-describing – select this option if your output will be used by Formatter.

    • XML – select this option if your output requires an XML format.

    Error Options

    Specify actions that e-Biz Impact should perform when a transaction encounters a processing error through this production object. You can use the tranHalt() and tranCancel() built-in filter functions to override the option settings.

    Error Rule

    The name of the rule object to run after executing the production object error function. Use this rule object to execute any other actions you want to perform when a transaction encounters a processing error through this production object. For example, you could examine datalink and input fields and write the contents to a file or e-mail them.

    This rule object can add more data to the production object output blob, but it cannot change or delete any data currently in the blob. This rule object can use the tranHalt() or tranCancel() built-in filter function to determine which actions e-Biz Impact should take, but it cannot force continued processing of the transaction.

    Halt Processing To AIM

    Same as the destination returning a zero or negative value. Places the transaction in the unprocessable log file, halts the destination, and prevents it from receiving any further transactions until this unprocessable transaction is repaired and resent to the destination. By default, e-Biz Impact performs the halt actions whenever a transaction encounters a processing error through a production object.

    Cancel & Keep Going

    Same as the destination returning a -999. Places the transaction in the unprocessable logfile and allows the destination to continue to receive new transactions.

    Skip & Keep Going

    Skips the entire transaction and continues to receive new transactions. Places the transaction in the unprocessable log file.

    Defaults

    The options available identify a default separator to append to all rule object and/or rule component object output.

    Rule Separator

    Select this option to have e-Biz Impact append a separator to the output of every rule object. To use a literal value as the default separator, select the Literal option and enter the desired value into the adjacent entry field. To use the contents of an input field as the default separator, select FldObj, then select the desired input field from the drop-down list.

    If you do not want an individual rule object to use the default separator, select No Default Separator in the Current Production Rule window when defining the rule object.

    Rule Component Separator

    Select this option to have e-Biz Impact append a separator to the output of every rule component object. To use a literal value as the default separator, select the Literal option and enter the desired value into the adjacent entry field. To use the contents of an Input Field as the default separator, select the FldObj option, then select the desired input field from the drop-down list.

    If you do not want an individual rule object to use the default separator, select No Default Separator in the Rule Component Information window when defining the rule component object.

    Pre Filters

    Define one or more filter objects to run against the input transaction. These filters are the first action taken on a transaction when e-Biz Impact presents them to a production object and are run before input field parsing or any qualification takes place.

    Use this option to run a filter on an entire transaction; for example, converting the transaction data to upper or lowercase or changing all pipe “|” symbols to dollar signs “$”.

    NoteThis filter does not change the actual transaction logged by the SFM; it affects only the copy of that transaction presented to this production object.

  4. Click OK to save the entries and close the window. To exit the window without changing or accepting new entries, click Cancel.





Copyright © 2005. Sybase Inc. All rights reserved. Using the test drive

View this book as PDF