This portal is to open public enhancement requests against IBM Z Software 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Closing this requirement. Customer agreed to submit an RFE for Installation Manager instead.
b.i.
Could you please identify which brand, family, product and component to use to submit an RFE for Installation Manager?
c.
If I delete the Installation Kit, how do I apply new PTFs? Similarly, the documentation makes it appear that even in a shared DASD environment, Installation Kits are required for each SOAP Gateway task.
Here is some details to USAA questions. Please refer to "IBM Response" comments below to USAA questions.
a. Being capable to perform receive, apply and accept via SMP/E requires Java to already be installed on the system
IBM response: This is required due to Installation Manager. When applied, the Installation Manager kit is unzipped using java. USAA should open an RFE against Installation Manager for this requirement (see below).
b. SMP/E lays down files for Installation Manager, which comes with its own version, and the manual occasionally states that IM must use this version of Java.
i. This Java version was also, of course, in SMP/E.
IBM response: This is correct, Installation Manager contains its own JRE and requires Java6. We have heard from the IM team that they are working to moving to Java7. There have been discussion about allowing users to configure the java instance to use with Installation Manager but there is not enough customer interest for this feature. Customers should open an RFE against Installation Manager for this requirement.
c. Installation Manager is used to create an Installation Kit for EACH install of Soap Gateway
IBM Response: SMP/E lays down the Installation Kit for Installation Manager. The installation kit is used to install Installation Manager on the System. Once Installation Manager is installed, the Installation Kit can be discarded. Installation Manager uses the SOAP Gateway repository to install an instance of SOAP Gateway.
Only one instance of Installation Manager is needed for multiple instances of SOAP Gateway if they are being installed in a shared DASD. If they are not shared, a new instance of Installation Manager is needed for new instances of SOAP Gateway.
d. Soap Gateway has a third version, and again, the manual implies that this copy of Java must be used.
ii. Each copy of this Java version was, of course, in the individual Kit, though shared in IM and SMP/E
IBM Response: There should only be 3 copies of Java that are retained. 1 that is already on the system, 1 from the Installation Manager, and 1 for SOAP Gateway. SOAP Gateway can use the Java on the system as long as its the same major version from IBM.