CLM TLS1.2 configuration in WAS.

Anatoliy Khludov (32●6●13) | asked Sep 18 '17, 5:19 p.m.
retagged Sep 22 '17, 12:56 a.m. by Minakshi Jaint (511●3)

Hello,
I am following the steps described here: https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.4/com.ibm.jazz.install.doc/topics/t_enable_tls1.2_was.html.

The question is about step number 3 which says:
3. Click the default SSL settings link to open it and, under Additional Properties, click Quality of protection (QoP) settings.

In step 3, where it says "click the default SSL settings link and open it", after navigating to this page I can see 4 links/items listed in there (copied below).
Our server lives in Node05. Which link/item should I access and proceed with further modifications?
Should it be NodeDefaultSSLSettings for (cell):rtctestCell01:(node):rtctestNode05 in our case?
The manual is not clear on this, it doesn't specifically say which item should be modified.

<input id="SSLConfig_1" name="selectedObjectIds" type="checkbox" value="SSLConfig_1">

	CellDefaultSSLSettings	(cell):rtctestCell01
<input id="SSLConfig_1489522480875" name="selectedObjectIds" type="checkbox" value="SSLConfig_1489522480875">	NodeDefaultSSLSettings	(cell):rtctestCell01:(node):rtctestNode01
<input id="SSLConfig_1489523069918" name="selectedObjectIds" type="checkbox" value="SSLConfig_1489523069918">	NodeDefaultSSLSettings	(cell):rtctestCell01:(node):rtctestNode05
<input id="SSLConfig_1489513023705" name="selectedObjectIds" type="checkbox" value="SSLConfig_1489513023705">	XDADefaultSSLSettings	(cell):rtctestCell01

Thank you,
Anatoliy

One answer

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Donald Nong (14.5k●4●14) | answered Sep 19 '17, 1:45 a.m.

The instructions are actually very clear, if you use the WAS admin console of the server itself, without using the deployment manager - you will see only one item when you get to that stage. It's called "NodeDefaultSSLSettings". So in your case, I believe it's the third one.

Comments

Anatoliy Khludov commented Sep 19 '17, 12:15 p.m.

Donald, thank you for your answer. We use WAS ND, is there a way to log in to the the WAS admin console on the server server itself bypassing the deployment manager?

Kevin Ramer commented Sep 19 '17, 4:46 p.m.

Here's a suggestion: go to the profile directory and look at the file logs/AboutThisProfile.txt

Something like:
$ cat logs/AboutThisProfile.txt
Application server environment to create: Application server
Location: /was_profiles/idportal
Disk space required: 200 MB
Profile name: IDPORTAL
Make this profile the default: False
Node name: tdsp7l4Node02
Host name: tdsp7l4
Enable administrative security (recommended): False
Administrative console port: 9070
Administrative console secure port: 9053
HTTP transport port: 9081
HTTPS transport port: 9447
Bootstrap port: 2819
SOAP connector port: 8890
Run application server as a service: False
Create a Web server definition: False
Performance tuning setting: Standard

Then hit: http://<hostname>:<console_port>/ibm/console in browser.
<hostname> == what follows Host name:
<consol_port> == Administrative console port:

It's all about the answers!

Related questions

CLM TLS1.2 configuration in WAS.

One answer

Your answer