Integration Platform Technologies: Siebel Enterprise Application Integration > Siebel EAI and File Attachments > Using MIME Messages to Exchange Attachments >

Creating Workflow Examples


Depending on whether you are preparing for an outbound or an inbound attachment exchange, design different workflows as described in the following two procedures.

For more information on creating workflows, see Siebel Business Process Framework: Workflow Guide.

Outbound Workflow

To process the attachment for an outbound request you must create a workflow to query the database, convert the integration object and its attachments into a MIME hierarchy, and then create a MIME document to send to the File Transport business service.

To create an outbound workflow

  1. In Siebel Tools, select the Workflow Process object in the Object Explorer.
  2. Right-click, then choose New Record.
  3. Give the new workflow a name and associate it with a locked project.
  4. Right-click, and then choose Edit Workflow Process.

    The Workflow Process Designer appears.

  5. Create a workflow consisting of Start, End, and four Business Services. Set up each Business Service according to the task it must accomplish.
  6. Define your process properties.

    Set process properties when you need global properties for the entire workflow.

    Name
    Data Type
    Default String

    SiebelMessage

    Hierarchy

    Leave blank.

    Error Message

    String

    Leave blank.

    Error Code

    String

    Leave blank.

    Object Id

    String

    Leave blank.

    Process Instance Id

    String

    Leave blank.

    Siebel Operation Object Id

    String

    Leave blank.

    MIMEHierarchy

    Hierarchy

    Leave blank.

    SearchSpec

    String

    [Account.Name] = 'Sample Account'

    <Value>

    String

    Default output is binary.

  7. The first business service queries the Account information from the database using the EAI Siebel Adapter business service with the Query method. This step requires the following input and output arguments.
    Input Argument
    Type
    Value
    Property Name
    Property Data Type

    Output Integration
    Object Name

    Literal

    Sample Account

    Not applicable

    Not applicable

    SearchSpec

    Process Property

    Not applicable

    SearchSpec

    String

    Property Name
    Type
    Output Argument

    SiebelMessage

    Output Argument

    Siebel Message

    NOTE:  For more information on using the EAI Siebel Adapter, see EAI Siebel Adapter Business Service.

  8. The second business service in the workflow converts the Account integration object and its attachments to a MIME hierarchy using the EAI MIME Hierarchy Converter business service with the SiebelMessage to MIME Hierarchy method. This step requires the following input and output arguments.
    Input Argument
    Type
    Property Name
    Property Data Type

    Siebel Message

    Process Property

    SiebelMessage

    Hierarchy

    Property Name
    Type
    Output Argument

    MIMEHierarchy

    Output Argument

    MIME Hierarchy

    NOTE:  For more information on the EAI MIME Hierarchy Converter, see About the EAI MIME Hierarchy Converter.

  9. The third business service of the workflow converts the MIME hierarchy to a document to be sent to File Transport business service. This step uses the EAI MIME Doc Converter business service with the MIME Hierarchy To MIME Doc method. This step requires the following input and output arguments.
    Input Argument
    Type
    Property Name
    Property Data Type

    MIME Hierarchy

    Process Property

    MIMEHierarchy

    Hierarchy

    Property Name
    Type
    Output Argument

    <Value>

    Output Argument

    MIME Message

    NOTE:  For more information on the EAI MIME Doc Converter, see About the EAI MIME Doc Converter.

  10. For the final step, set up the last business service of the workflow to write the information into a file using the EAI File Transport business service with the Send method. This step requires the following input arguments.
    Input Argument
    Type
    Value
    Property Name
    Property Data Type

    Message Text

    Process Property

    Not applicable

    <Value>

    String

    File Name

    Literal

    c:\temp\account.txt

    Not applicable

    Not applicable

    NOTE:  For information on File Transport, see Transports and Interfaces: Siebel Enterprise Application Integration.

Inbound Workflow Example

To process the attachment for an inbound request, you must create a workflow to read the content from a file, convert the information into a Siebel Message, and send to the EAI Siebel Adapter to update the database accordingly.

NOTE:  When passing the process property value for a workflow from an external application (or another business service) as the input property set, the corresponding property name in the input property set must be same name as the process property and is case sensitive.

To create an inbound workflow

  1. In Siebel Tools, select the Workflow Process object in the Object Explorer.
  2. Right-click, and then choose New Record.
  3. Give the new workflow a name and associate it with a locked project.
  4. Right-click, then choose Edit Workflow Process.

    The Workflow Process Designer appears.

  5. Create a workflow consisting of Start, End and four Business Services. Set up each Business Service according to the task it must accomplish.
  6. Define your process properties.

    Set process properties when you need global properties for the entire workflow:

    Name
    Data Type

    SiebelMessage

    Hierarchy

    Error Message

    String

    Error Code

    String

    Object Id

    String

    Siebel Operation Object Id

    String

    MIMEHierarchy

    Hierarchy

    MIMEMsg

    Binary

  7. The first business service in the workflow reads the Account information from a file using the EAI File Transport business service with Receive method. This step requires the following input and output arguments.
    Input Argument
    Type
    Value

    File Name

    Literal

    c:\temp\account.txt

    Property Name
    Type
    Output Argument

    <Value>

    Output Argument

    Message Text

    NOTE:  For information on File Transport, see Transports and Interfaces: Siebel Enterprise Application Integration.

  8. The second business service of the workflow converts the Account information to a MIME hierarchy using the EAI MIME Doc Converter business service with the MIME Doc to MIME Hierarchy method. This step requires the following input and output arguments.
    Input Argument
    Type
    Property Name
    Property Data Type

    MIME Message

    Process Property

    <Value>

    Binary

    Property Name
    Type
    Output Argument

    MIMEHierarchy

    Output Argument

    MIME Hierarchy

  9. The third business service of the workflow converts the MIME hierarchy to a document, and sends it to the EAI Siebel Adapter business service. This step uses the EAI MIME Hierarchy Converter business service with the MIME Hierarchy to Siebel Message method. This step requires the following input and output arguments.
    Input Argument
    Type
    Property Name
    Property Data Type

    MIME Hierarchy

    Process Property

    MIMEHierarchy

    Hierarchy

    Property Name
    Type
    Output Argument

    SiebelMessage

    Output Argument

    Siebel Message

  10. The last step of the workflow writes the information into the database using the EAI Siebel Adapter business service with the Insert or Update method. This step requires the following input argument.
    Input Argument
    Type
    Property Name
    Property Data Type

    Siebel Message

    Process Property

    SiebelMessage

    Hierarchy

Integration Platform Technologies: Siebel Enterprise Application Integration Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.