Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. 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 Future consideration
Workspace App Connect
Created by Guest
Created on Oct 22, 2013

Enhance the New Message Model wizard to import WSDL files from URL using same function as local WSDL files

When using the "New Message Model" wizard you have the option to create the model from an existing WSDL file. The behavior of the wizard is different if the WSDL file is accessed from the workspace or from a URL.

When accessed from the workspace you have an opportunity to specify which folder the generated WSDL and XSD files are written to. The names of the file that are generated are also generated to include the name of the WSDL file as the first portion of the file name. For example, if a WSDL file named DistributorService.wsdl is imported from the local workspace into a folder named Distributor a set of files will be created in a folder named Distributor with the names of DistributorService.wsdl, DistributorService.xsd, DistributorService_InlineSchema1.xsd, DistributorService_xsd0.xsd and DistributorService_xsd1.xsd.

When accessed from a URL the generated files are arbitrarily written to a folder named RemoteFiles. There is no control over the folder name. The file names that are generated are also handled differently. In this case the XML schema documents that are generated from INCLUDE and IMPORT directives are always named with an "xsd_" prefix rather than a prefix of the WSDL file name. For example, importing a WSDL file from a URL that references a WSDL file name of MDM will generate the following files in the RemoteFiles folder: MDM.wsdl, MDM.xsd, MDM_InlineSchema1.xsd, xsd_xsd0.xsd and xsd_xsd1.xsd.

The use of the "xsd_" prefix for all URL referenced files causes problems when you attempt to create a Message Model from more than 1 URL based web service into a single Library. Each additional Message Model that you create will overwrite the existing "xsd_" prefixed schema documents, which corrupts the existing Message Models.

Using a separate Library to hold Message Models will alleviate the problem in the Toolkit, but does not fully resolve the issue. If more than 1 Message Model that is built from a URL based WSDL is deployed to the same Execution Group there will still be a clash due to the sharing of the RemoteFiles folder in the runtime.

The "New Message Model" wizard needs to be modified to allow URL based WSDL's to store their generated files in separate folders, the same as workspace based WSDL files.

Idea priority High
RFE ID 40726
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |
    Sep 13, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. Despite the relatively modest number of votes which have been accrued for this RFE over a long time period, we do see value in the request. Whilst this is not an area currently being prioritised (the current popularity of REST APIs has limited investment in web services areas of the product), we will continue to monitor this RFE. Status is updated to Uncommitted Candidate.

  • Guest
    Reply
    |
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Reply
    |
    Oct 22, 2013

    Attachment (Description): Project Interchange file to support Use Case.