Improve documentation and options for installing GKLM with an existing db2
For the manuals team to update the documentation on the steps and restrictions to re-use a db2 install. At present the manual says it can be done but not how to do it.
Correct the statement for 220.127.116.11 that Db2 standard edition is installed, GKLM installs the 11.5.6 community edition of db2.
For the packaging team to include an example response file for re-using a db2 install. These will make GKLM a better product.
For the installation team add an option to "record" the IM steps to generate a response file. It is hard to research how to do this and then manually implement the option.
Customer at times do want to use an existing db2 eg they have an automated install for Db2 that follows their in-house standards. By re-using this install it will make life a little easier for the DBA's as when they check this system the db2 files and config are in the same locations as all their other servers. It would also speed up the configuring of GKLM into a production ready state as the Db2 system would already be setup in a production ready way.
GKLM reuses the existing "instance" of Db2, it does not create a new "instance" therefore in DB2 terms there is no sense to change the DBM TCPIP Service Name (port) in Db2 for the instance. This is current forced by the install GUI. When a user checks the "existing db2 option" this port check should not take place. Port checking does make sense for other types of installs. Within Db2 shops the port number used is normally a standard across the shop and firewalls are pre-opened ready for Db2 use. So the installer should be happy to accept the already in place port number.
Also many shops will no longer allow TCPIP connections to Db2 instances, the best practice today within DB2 is to use the Db2 SSL listener not the Db2 TCPIP listener, so GKLM should be moving to this approach when setting up the Db2 instance.