Video: Introduction to creating a collective
The following transcript is for the "Introduction to creating a Liberty collective" video, which demonstrates how to create a collective of one controller and one member. This transcript is the video storyboard. Audio describes narration and captions. Onscreen Action describes the content shown in the video.
Introduction
to creating a Liberty collective
Scene | Audio | Onscreen Action |
---|---|---|
1 | Hi, I'm Mike Thompson, a developer with WebSphere Liberty. I'm going to take you today through a brief introduction of Liberty's new administrative domain known as the collective. | Show the developer talking on camera. |
2 | Starting with a Liberty Network Deployment install, we're going to create a simple collective. This can be done in about eight steps. The first step is creating a server to be the administrative server. I'm going to call that myController. | Show command window open at wlp/bin,
run server create myController, and then show message
|
3 | Once the server myController is created, we then need to establish the collective configuration necessary for the server to act as a controller. As part of that configuration, we're going to specify a keystore password. The keystore password is not predefined. We do not ship predefined user names or passwords. So, using the keystore password demoPassword will establish the configuration for a collective controller. | Show command window open at wlp/bin, and
then run the command:
|
4 | This takes about three seconds and essentially establishes some SSL certificates. We need to copy the configuration printed to the screen and update the server configuration file. | Show messages generated by the command, with
the following messages marked for copying:
|
5 | We can do that using Notepad because this is very simple XML and we can essentially paste it right into the contents of the server.xml. | Show a Notepad editor open on the myController server.xml file, and then the copied messages pasted into the server.xml file before the ending tag, </server>. |
6 | In addition to pasting it in, we do need to specify an administrative name. So, I'm going to use admin, with adminpwd as the password. | In editor, set user name and password:
|
7 | Once the server is configured, we can start it. | Show command window open at wlp/bin,
run server start myController, and then show message:
|
8 | Now that the collective controller is running, I can create a server to join to the collective. I'm going to create a server called myMember and I'll join this server into the collective. This operation can be done using the collective join command. And, what needs to be specified is the host and port that the collective controller is listening on the HTTPS port, the administrative user name and password, and a keystore password. This password can be the same or different from the password used when we created the collective controller. | Show command window open at wlp/bin,
run server create myMember, and show message
Then
run collective join myMember --host=localhost --port=9443
--user=admin --password=adminpwd --keystorePassword=demoPassword. |
9 | Because this is connecting over SSL to the collective controller, it will prompt us for SSL trust. The certificate presented here is from the collective controller, which we recognize. We will accept the certificate and what will happen in the background is that the collective controller will establish some SSL certificates that will be handed back and laid down in the file system for this particular member. | Show messages generated by the collective join command. The messages show that the Issuer DN is controllerRoot. After the message Do you want to accept the above certificate chain? (y/n), enter y to accept the certificate. |
10 | We copy the configuration, just like we did
for the controller, and we update the member's configuration file. Important: The generated
configuration has a hostAuthInfo element that was
added to the product after the video was made. Complete the hostAuthInfo element
in either of two ways:
|
Show messages generated about keystore and truststore
references, with the following messages marked for copying:
|
11 | We can do that also using Notepad. | Show the command to open a Notepad editor, notepad usr/servers/myMember/server.xml, show a Notepad editor open on the myMember server.xml file, and then the copied messages pasted into the server.xml file before the ending tag, </server>. |
12 | Once updated, the member server can be started
and the member server will start publishing its information into the
controller. And that's it. You now have a very basic collective. To add more members, you just repeat the join operation on any servers that you want to create. It's that easy. The members are added and the collective grows. |
Show command window open at wlp/bin,
run server start myMember, and then show messages:
|
For more information, see Configuring a Liberty collective.