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
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,
Post an idea
Upvote ideas that matter most to you
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.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
MessageBus XML gateway: Custom HTTPHeaders property
The MessageBus XML gateway should offer a Property for usage in HTTP Transport (in httpTransport.properties) which allows custom HTTP header fields to be defined, which then get sent out in the outgoing HTTP requests.
So, What is asked is: A property "customHttpHeaders" which can be used (e.g.: set to "accept:text/plain,Content-Type:application/json-patch+json" in httpTransport.properties file, so that the custom header fields get included in the outgoing HTTP requests.
Some 3rd Party systems which should be integrated using the XML gateway may only accept HTTP requests when certain headers are present.
In the related Support case we are sending HTTP requests to a Service Insights REST API with JSON payload. The REST endpoint does not accept the incoming HTTP requests without specific headers.
Currently we have implemented a workaround by sending the HTTP requests to an intermediate HTTP server, which sets the headers and passes the request on to the REST endpoint. This workaround (and additional layer of complexity) can be saved if only the gateway allowed to set custom HTTP headers.
Also the functionality seems to be present in WebSocket transport type of the Message Bus probe, so shouldnt be to complicated to implement.
Do not place IBM confidential, company confidential, or personal information into any field.