When changes become effective

 

Changes to the certificates in the key database file and to the key repository attribute become effective:

• When a new outbound single channel process first runs an SSL channel.

• When a new inbound TCP/IP single channel process first receives a request to start an SSL channel.

• When the MQSC command REFRESH SECURITY TYPE(SSL) is issued to refresh the WMQ SSL environment.

• For channels that run as threads of a process pooling process (amqrmppa), when the process pooling process is started or restarted and first runs an SSL channel. If the process pooling process has already run an SSL channel, and you want the change to become effective immediately, run the MQSC command REFRESH SECURITY TYPE(SSL).

• For channels that run as threads of the channel initiator, when the channel initiator is started or restarted and first runs an SSL channel. If the channel initiator process has already run an SSL channel, and you want the change to become effective immediately, run the MQSC command REFRESH SECURITY TYPE(SSL).

• For channels that run as threads of a TCP/IP listener, when the listener is started or restarted and first receives a request to start an SSL channel. If the listener has already run an SSL channel, and you want the change to become effective immediately, run the MQSC command REFRESH SECURITY TYPE(SSL).

We can also refresh the WebSphere MQ SSL environment using the WebSphere MQ Explorer or PCF commands.

 

Parent topic:

Working with a key repository

sy12240_