In todays time of virtual machines the easiest and simplest way of getting a backup is doing a snapshot. I usually recommend it everytime bigger changes such as upgrades are done. But not always there is the option to get a timely snapshot and therefore other means of backups are necessary. One “quick and dirty” way is copying all necessary files to a backup folder.
In a standard Connections environment (all Components in a /IBM directory) this usally means backing up two directories:
- the database directory (/DB2) if DB2 is installed locally
- the complete aforemeantioned /IBM directory (at least the /WebSphere and /LotusConnections directories under it)
Since IBM Connections 3 the IBM Installation Manager is used for installing the solution and its upgrades. Now I ran into a problem during an upgrade to 3.0.1 (always check the the remote desktop is started using the /console setting 😉 ) and hat copy back the recovered folders. Unfortunately the Installation Manager copies files some files in a separate directory no matter what you said when installing. And these files contain the information which upgrades have already been installed. So the IBM Installation Manager was still believing 3.0.1 was installed even though it did not and I copied back the “old” 3.0.0 environment. Having not enough time to play around I went the way of deinstalling Connections completely and reinstalling it.
So when you do a backup, make sure to add the following folder, too:
- C:\ProgamData\IBM\Installation Manager
Whenever WebSphere Application Server settings are changed in the Deployment Manager, these changes are not pushed down to all nodes automatically by default. Therefore a manual synchronization must be triggered to get these changes pushed to all cluster members. This can be automated by doing the following steps:
In the Integrated Solution Console (ICS) open System administration on the left hand menu and the click on Console Preferences.
Now you can set the checkmark on the right side at Synchronize changes with Nodes.
Once you click on “Apply” all changes in the ICS will be pushed down to all available cluster members whenever “save” is clicked.
IBM Connections is being installed in a WebSphere Cluster. After rebooting a server there are different ways of restarting each application server and application. One way is starting each feature as its own service task or, and this is what this blog entry is about, you just start the node and the node itself will check the application status and detect that the applications are not running and will start them on its own.
To configure this you need to log into the WAS Integrated Solutions Console with the WebSphere Application Server admin user and select Servers => Server Types => WebSphere application servers:
Now you select the first server and click on Configuration and then click on Monitoring policy.
Now we need to change the Node restart state to RUNNING.
Finally we save the changes and repeat these steps for each server. After doing a Sync to all notes if necessary we can restart the node agent and all changes are active. Now the applications are monitored and started automatically if they are not running after an reboot / restart.