Get empowered with IBM Power
I am giving two presentations at this year’s #OCEANTechCon22, in person, on Friday July 22.
I hope I will see some of you there! If you are there feel free to come over & say “Hi”.
💙#IBMi #rpgpgm #IBMChampion pic.twitter.com/Cl8ZB0kJ84
– Simon Hutchinson (@RPGPGM)05:29 – Jul 07, 2022
At the @arcad_software 30th anniversary event. A very good crowd of people doing #ibmi modernization. pic.twitter.com/wpYReC7qHq
– Steve Will (@Steve_Will_IBMi)03:49 – Jul 07, 2022
When configuring your ADMINx/Integrated Application Server/Integrated Web Service application servers for TLS communications, you have the option of specifying what keystore type you wish to use in the configuration. This can be a specific keystore path and type or the Digital Certificate Manager *SYSTEM certificate store. This document will discuss how to configure your application server using a specific keystore path and type. For detailed information on how to configure the application server with the Digital Certificate Manager *SYSTEM certificate store, please refer to the URL, https://www.ibm.com/support/pages/node/667835.
When configuring the ADMIN1, ADMIN2, ADMIN3, ADMIN5, Integrated Application Servers (IAS), or Integrated Web Services (IWS) application servers for TLS communications, you have the option of specifying a keystore other than Digital Certificate Manager. When selecting a specific keystore to use with your application server instance, you also have the option of using a certificate from a Digital Certificate Manager certificate store instead of using the default self-signed certificate. This document discusses how to import the desired certificate from a Digital Certificate Manager certificate store and configure your application server to use it. We will also discuss how to maintain this configuration moving forward.
SF99723: SF99723 730 Performance Tools
