Friday, November 14, 2008

Centralized Installation Manager (CIM)

Performing a WebSphere installation and configuration and/or applying maintenance is relatively easy (OK, don't shoot me, I said "relatively"). But having to repeat that over and over again on many different remote machines throughout an organization is both time-consuming and error-prone. To address this problem WebSphere Virtual Enterprise (previously eXtended Deployment XD) v6.1 created and shipped a "Centralized Installation Manager" (CIM), and it worked so well that it is now even included in WebSphere v7 Network Deployment (ND).

The CIM program can be installed into a v7 ND Deployment Manager, and then can easily install and maintain the workstations in a WebSphere cell. An administrator can remotely install or uninstall product packages and maintenance to specific nodes directly from the administrative console without having to repetitively log in and perform these tasks on each individual remote machine. CIM operations can be done through its Graphical User Interface or can be scripted for full automation. Since CIM only previously shipped with XD-6.1, almost no "ND" WebSphere customers currently know about it. For details about CIM and how you can leverage to simplify and automate your enterprise servers please see the WebSphere v7 InfoCenter CIM information. If you are an ND cell administrator then CIM is something you need to seriously consider, it is certainly a way to significantly simply your day-to-day operations.

9 comments:

whale said...

According to the URL in the blog entry:
'The CIM does not replace the standard installer and the Update Installer for WebSphere Software used to install and update the WebSphere Application Server product. Rather, the CIM pushes the product binary files or maintenance to the remote targets and invokes the standard installer or update installer tool to perform the installation or update on the targets.'

In my experience WAS requires the latest UpdateInstaller for each Fixpack installed. I take that the installation of the UpdateInstaller is still a manual task and must be completed on every server in the cell?

Thanks

Barry Searle said...

In WebSphere v6.x this was (sadly) usually true. In v7.0 we are trying to totally avoid this (and so far have not required an upgrade). IF a FixPack (or interimFix) needs a newer UPDI, then CIM will warn and stop if it is not available in CIM, but if the newer UPDI is available in CIM then CIM will ask permission to do updates, and then update the remote UPDI as part of the fix distribution Nice and easy!

Scott said...

Can CIM handle fixpack for IHS and Plugin? I cannot seem to figure that one out.

Barry Searle said...

Sorry, but C.I.M. does not handle IHS (IBM Http Server) nor Plugin configurator. C.I.M.'s focus is remote installing and servicing WebSphere Application Servers.

Lloyd Mwaluku said...

is there any need to stop all the application servers at the remote host when updating/Installing fix packs?

Leho Nigul said...

CIM will stop all application servers and the node agent on the remote node when installing fix packs. CIM will restart the node agent and users will need to manually restart their application servers after the update.

Thiyagu said...

please integrate HTTP server and plugin

Anonymous said...

What if the target Websphere Application Server Nodes (Cells) are greyed out in the CIM>Available Installations?

Does that mean CIM only works in the same cell? The guide https://www.blogger.com/comment.g?blogID=1417695962027703953&postID=8684563481238896119 (page 18, Using CIM to manage your environment) states you can use CIM to magee targets outside the cell.

Thanks

Leho Nigul said...

Currently, CIM function is limited to the boundaries of the cell.