bootstrap.properties file

Edit online

Two bootstrap.properties files contain the configuration attributes for the Copy Services Manager servers. One bootstrap properties file sets the configuration for the management server and another for the authentication server.

The bootstrap.properties file is in the following locations on distributed systems:

Management server: install_dir\liberty\wlp\usr\servers\csmServer\bootstrap.properties
Authentication server: install_dir\liberty\wlp\usr\servers\csmAuth\bootstrap.properties

The bootstrap.properties file is in the following locations on z/OS® systems:

Management server: path_prefix/opt/IBM/CSM/wlp/usr/servers/csmServer/bootstrap.properties
Authentication server: path_prefix/opt/IBM/CSM/wlp/usr/servers/csmAuth/bootstrap.properties

The file contains the following properties:

https_port_var: Specifies the GUI port (for csmServer) or the authentication port (for csmAuth). The port number is set during installation. However, you can modify this property value to change the port number after installation.
keystore_id: Specifies a unique configuration ID.
keystore_location_prefix: Simplifies specification of the key ring URL for z/OS. The default value is blank for file-based keystores.
keystore_location: Specifies an absolute or relative path to the keystore file. If a relative path is provided (for example, key.jks), the server attempts to locate the file in the csmServer/resources/security directory.
keystore_password: Specifies the password that is used to load the keystore file. The value can be stored in cleartext or encoded form. An encoded password string is preceded with {xor}.
keystore_type: Specifies a keystore type that is supported by the target SDK. The default value is JKS.
keystore_fileBased: Specifies whether the keystore is based on a file. The default value is true.
keystore_readOnly: Specifies whether the keystore is to be used by the server for read operations only. The default value is false. The value false indicates that the server can write to the keystore.
ssl_protocol: Specifies the SSL handshake protocol that is used on the HTTPS port for that server. The value is determined by the Java™ release and can default to the minimum value (for instance, TLSv1.2) automatically during upgrade.

Note: You must restart the server for your modifications of the bootstrap properties file to take effect in the server configuration.

The default contents of each bootstrap.properties file is displayed in the following example.


###############################################################################
#This section is for the HTTPS settings of the IBM Copy Services Manager GUI. #
###############################################################################
https_port_var=9559
ssl_protocol=TLSv1.2

###############################################################################
#This section is for the keystore certificate information.  This can be       #
#changed to match your environment.                                           #
#                                                                             #
#Note that keystore_location is relative to csmServer/resources/security      #
#The keystore_location_prefix is typically left blank for file based          #
#keystores.                                                                   #
###############################################################################
keystore_id=keystore
keystore_location_prefix=
keystore_location=key.jks
keystore_password={xor}HjktbwhvMzkMOi0pOi0=
keystore_type=JKS
keystore_fileBased=true
keystore_readOnly=false

###############################################################################
#This section is a sample JCERACFKS certificate keystore configuration that   #
#can be uncommented and modified to match your environment.                   #
#                                                                             #
#The location must be a safkeyring url syntax with the first qualifier as the #
#IWNSRV and keyring owner and the second qualifier as the keyring name.  The  #
#safkeyring url syntax is important, in order to pass it propertly into       #
#server.xml, it is split across two properties values.  The                   #
#keystore_location_prefix is set to "safkeyring:" while the keystore_location #
#is the rest of the safkeyring url.                                           #
#                                                                             #
#The keystore id and password will be used to create a local keystore with    #
#the specified ID and password holding the cached certificate for the GUI.    #
###############################################################################
#keystore_id=keystore
#keystore_location_prefix=safkeyring:
#keystore_location=//CSMUSER/GUIKEYRING
#keystore_password=password
#keystore_type=JCERACFKS
#keystore_fileBased=false
#keystore_readOnly=true