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
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
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.
Thank you for submitting this request but without additional details we can not proceed with this RFE.
Can you please provide the screenshots/samples so that we can reproduce the steps as defined in the ticket. For data-privacy reasons these files are only viewable by our support team and can not be shared. Specifically the steps in Number 4 - 6 as when adding/deleting new Target Service. Based on a test adding a new target service in v10.0.8 does not modify defined in the assembly.execute section. Only when that new WebService Operation is pulled from the pallet does it modify the assembly.
We do believe that you are seeing specific behavior but the Product management team is looking to replicate the behavior in v10.0.8.x to understand the use case better.
Create a new API from existing WSDL service (REST Proxy) (you can use the "HelloWorld.wsdl" present in helloworldtest_1.0.0.zip)
After the API is created add a gateway script in the policy (see V1_INITIAL.png)
Create a new copy of the API (2.0.0 in my case)
Update the local WSDL (you can use "HelloWorld_V2.wsdl" present in helloworldtest_2.0.0.zip)
In the V2 version, "Upload WSDL" (see update_wsdl.png and update_wsdl_load.png) by choosing "HelloWorld_V2.wsdl"
After the V2 is updated, You can see that the gateway script created in step 2 disappeared from the policy (see "V2_AFTER_UPDATE.png" )