SmartCloud enterprise+ Tip: Use Tsam and Cygwin to install IIS on Windows

When you try to install software on the IBM SmartCloud enterprise+, you may experience some potential problems. With this in mind, you need to consider the following alternative installation method, which uses Internet information Services Version 6 as an example.

The environment used in this article includes:

Internet Information Services (IIS) V6 32-bit

Using Microsoft Windows 2003/2008 Server as a virtual machine on the WMware Esxbox

Cygwin (installed on the Windows VM by default)

SmartCloud enterprise+

Rapid Deployment Services (RDS)

Simple Package Installer (SPIN)

Aix

Tivoli Service Automation Manager (and the installed Tivoli Process Automation Engine (TPAE), Tivoli service Request Manager (TSRM), and T Ivoli Provisioning Manager (TPM))

Windows 2003 or 2008 Server as a virtual machine on VMware Esxbox

Cygwin installed on the Windows VM by default

This is a typical cloud environment in which you have both a management environment and a managed environment, and the software is installed from the management environment to the managed environment (that is, from the Tivoli Service Automation Manager to the virtual machine).

Problem

We want to install a software on a Windows operating system on the IBM SmartCloud enterprise+. The software installed to demonstrate this method is Internet information Services Version 6. Install IIS using the Cygwin environment with SmartCloud-enabled quick Deployment service and simple package installer. If you are unfamiliar with these techniques, check out the closing remarks in this article first.

The legacy installation is problematic when the installation process cannot be started because some of the necessary services in the operating system cannot be started. In this case, you can see the IIS error message in the installation log, as shown in Listing 1.

Listing 1. To terminate the IIS log error message for the installation process

 V10\spinpackage\spin\tools\iis\iis_on_base.txt "failed with the below error message [4/18/2012 14:24:21] Oc_
Cleanup:executing Postinstall for the WWW component ... [4/18/2012 14:24:21] Oc_cleanup:calling runmofcomponiisfiles [4/18/2012 14:24:21] Oc_cleanup:inetstartserice (): ServiceName=W3SVC Unable To start WARNING.
err=0x424. [4/18/2012 14:24:22] oc_cleanup:!
fail! [4/18/2012 14:24:22] Oc_cleanup:postinstall of Component ' iis_www ' FAILED [4/18/2012 14:24:22] oc_cleanup:executing postinstall for the FTP com
Ponent ... [4/18/2012 14:24:22] Oc_cleanup:inetstartserice (): Servicename=msftpsvc Unable to start WARNING.
err=0x424. [4/18/2012 14:24:22] oc_cleanup:!
fail! [4/18/2012 14:24:22] Oc_cleanup:postinstall of Component ' iis_ftp ' FAILED [4/18/2012 14:24:22] oc_cleanup:processsection. [Oc_cleanup}.
Start. [4/18/2012 14:24:22] Oc_cleanup: ...
Processentry:100=5 ... [4/18/2012 14:24:22] Oc_cleanup:calling ProcessSection:SNMP_W3SVC_chk_cleanup:Start. 

The exact cause of the problem is unknown, but the problem is that some services, such as MSFTPSVC and W3SVC, are not available for use by the installer to start (these services are typically used only after the user logs on to the operating system).

Traditional methods

By default, the Tivoli service Automation Manager uses an SSH-based link to connect to a virtual machine. All Windows virtual machines in SmartCloud enterprise+ have Cygwin installed by default, so Tivoli service automation Manager logs on to the Windows VM using an SSH connection Received in Cygwin environment. This enables all operations to be performed on the Windows VM via Cygwin. The Device.execute workflow for Tivoli Service Automation Manager is often used to execute commands on the Cygwin shell. The shell calls Windows ' command prompt to perform any Windows operations. All BAT files can be executed from the Cygwin shell using the cmd \c {command}.

The Device.execute command can be used in the following ways:

Cmdtlcmtmpdir = "cmd/c" + "\" "+" mkdir "+ tempdir +" \ ""
Device.executecommand (DeviceID, Cmdtlcmtmpdir, <null>, "Default", "6000", "Ignore",
<null> <null> <null>)

DeviceID is the target virtual machine that needs to be used to execute the command.