Day 1 of the IBM Workplace Collaboration Services Class
Monday 13th February, 2006The idea of the class is load and configure
WCS 2.5 for both Messaging and Team Collaboration. The installation
itself for the instructor machine I talked about in the last posting.
Here is the class layout for Day 1
So there is no way in high heavens to make it through this all the first day. To start the class, the first thing we had the students do was launch the installation of the code we had on the machines. Recall that DB2 was already there and running. Knowing that the install in this version is very specific about file names and locations that it has to grab and unpack, meant a lot of planning time for us. Even with this done, it would take a long time for the install to finish. Cloudscape has to be created from the pack and loaded on the machine.
So if you are running a local DB2 store and doing a migration later, then both run at the same time for a while. There are some glaring questions on the amount of hardware required to run a fully operational infrastructure, but that comes in a later posting. The remainder of the day was making sure everyone was caught up and moving along in the install. Including disabling security and preparing to move to the centralized TDS on the instructor server in the room. We had two spare machines in case someone really goofed up ready to go.
The students will find out tomorrow how the machines run fully loaded even with the horsepower I stated in the last posting
|
Modules
|
| Section 1 : Introducing Administration Basics for IBM Workplace Collaboration Services 2.5 |
| Module A: Introducing Workplace Collaboration Services Architecture |
| Module B: Deploying IBM Workplace Collaboration Services |
| Module C: Administering the IBM Workplace Environment |
| Module D: Administering Users |
| Module E: Maintaining the IBM Workplace Environment |
So there is no way in high heavens to make it through this all the first day. To start the class, the first thing we had the students do was launch the installation of the code we had on the machines. Recall that DB2 was already there and running. Knowing that the install in this version is very specific about file names and locations that it has to grab and unpack, meant a lot of planning time for us. Even with this done, it would take a long time for the install to finish. Cloudscape has to be created from the pack and loaded on the machine.
So if you are running a local DB2 store and doing a migration later, then both run at the same time for a while. There are some glaring questions on the amount of hardware required to run a fully operational infrastructure, but that comes in a later posting. The remainder of the day was making sure everyone was caught up and moving along in the install. Including disabling security and preparing to move to the centralized TDS on the instructor server in the room. We had two spare machines in case someone really goofed up ready to go.
The students will find out tomorrow how the machines run fully loaded even with the horsepower I stated in the last posting
Comments [0]