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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
When using ICAP integration on SSP there are a lot of files with the .unscanned renaming due to the volume of the files or any other of the highly possible scenarios in which the file is sent to the backend without being scanned. Due to the type of transactionality the SSP-ICAP integration is rarely used so it is necessary to have something additional on the backend to fulfill the AV requirement.
It would be highly useful to have both an OOTB functionality on SFG to call ICAP for specific nomenclature (and not proceed with the routing in case of negative response) and an adapter to be able to call ICAP whenever required on a business process (ie. on GET operations) instead of having to use JavaTask to do so.
What is your industry?
How will this idea be used?
This will allow to have an end-to-end solution to be able to scan any kind of file since right know we only have this possibility on small files that come from specific protocols.
Any kind of file could be analysed on the backend without having such concerns that SSP has on the performance required for TCP/IP communications.
Do not place IBM confidential, company confidential, or personal information into any field.