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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Duration Schedule SLC-Generated Message -CSLC043E does not contain detailed information
We have designed one Work flow SLC with Metadata Rule and actions to work on events posted by ITXA. There is also one rule created based on message id: CSLC043E , Event Type: SLC Notification to trigger an alert if Workflow/Milestone/Step/Process ...
Non SuperUser Node Discovery Permission
Currently the only role within Control Center that can run a Node Discovery is the superuser role. We need this to be a permisson that can be set to other roles.
Requesting archiving for partitioned database
System Settings, database has archiving functionality for non-partitioned databases. We are requesting a similar utility be designed for partitioned databases.
SNMP Trap DateTime format issue
SNMP trap datetime format generated from Sterling Control Center always in UTC format irrespective of datetime config. in SCC settings while requirement is to generate the datetime format in ETC OR as per the configuration presents in the ICC sett...
assign/choose a TLS protocol level from within configCC.sh
o I would like to see the ability to assign/choose a TLS protocol level from within configCC.sh during secure setup of secure ports (Apache and Jetty setup), such as TLSv1.2 to replace the default of TLSv1.0
Cognos reporting does not return MQ return codes - Refer PMR 34702,442,000
When we run Cognos report, we filter based on Event Return Code under MQMFT FIle Transfer Report, it never comes with return codes as 40.We can see the return codes coming as 0,1,2 and 8 instead of standard MQ FTE return codes like 20,40 etc.
Configuracion Oracle RAC
Problem Description: We need to configure Oracle balancer RAC for Control Center. The following configuration is working at SQL developer and Sterling B2Bi jdbc:oracle:thin:@(DESCRIPTION_LIST=(LOAD_BALANCE=OFF)(FAILOVER=ON) (DESCRIPTION=(CONNECT_T...
Control Center (6.0): Control Center Reports URL Address
When a report is run from Control Center, another window is open and in the address bar of the window is the host name of the server where Control Center is running. Depending on the environment, this page may not display unless a user changes the...
AUTH NTLM authentication
Currently the IBM Control Center supports SMTP AUTH LOGIN only with, and our environment is set up for the authentication method of your SMTP server is NTLM auth. We need the control center IBM's application has 2 methods for authentication via SMTP.
SEAS needs ability for 2 factor authentication via RADIUS protocol
Need ability to have 2 factor authentication when connecting to applications using SEAS for authentication. Using RADIUS protocol to allow for token authentication would be the preferable method.
Do not place IBM confidential, company confidential, or personal information into any field.