Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Workspace IBM File Gateway
Created by Guest
Created on Jan 14, 2020

mailbox messageid and PrimaryDocument at AWS S3 custom protocol

During  AWS S3 custom protocol, at delivery side (consumer) AWSS3 client service is not getting primary document.
          to provide  primary document to AWS S3 service, we need to define logic like below
          <assign to="PrimaryDocument" from="/ProcessData/PrimaryDocument/@SCIObjectID"></assign>,
          which is an additional step which we are giving to our B2Bi processing engine.
          where as this not the behavior for other custom protocols implementation.
          During the AWS S3 custom protocol implementation for  MessageID we are defining extra logic to put the messages into
          staging mailbox by using Mailbox Add Service to get the messageID becuase of these extra steps our flow execution will take some more additional time.

What is your industry? Non-Industry Specific
How will this idea be used?

During  AWS S3 custom protocol, at delivery side (consumer) AWSS3 client service is not getting primary document.
          to provide  primary document to AWS S3 service, we need to define logic like below
          <assign to="PrimaryDocument" from="/ProcessData/PrimaryDocument/@SCIObjectID"></assign>,
          which is an additional step which we are giving to our B2Bi processing engine.
          where as this not the behavior for other custom protocols implementation.
          During the AWS S3 custom protocol implementation for  MessageID we are defining extra logic to put the messages into
          staging mailbox by using Mailbox Add Service to get the messageID becuase of these extra steps our flow execution will take some more additional time.

16 MERGED

PrimaryDocument at AWS S3 Service

Merged
when it comes to PrimaryDocument. AWSS3 Client Service should take the PrimaryDocument just like any other services. Why AWS S3 service is not getting primary document like other services.
over 2 years ago in IBM File Gateway 1 Delivered