• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (6)

1 localhost commented Trackback

Hi Guy,

Have you done any testing to see how well this works in a VM environment? It would seem to me to be ideal for this kind of deployment.
Are there any plans to provide a similar standalone lightweight installer for Linux / Unix? I don't have any problems with the current approach, which isn't arduous, this is more out of idle curiousity.

2 localhost commented Trackback

Hi Spokey,Yes it runs fine in a VM image. In a sense though, if you deploy your application as a virtual machine, wouldn't you install IDS at VM setup time and then just distribute the VM with everything fully set up? I.e. is there any need for a deployment tool when using virtualization? Or do you see this as a way to deploy IDS in a data center that is already using virtualization?

We are looking at a similar approach for all platforms. The Windows version evolved out of necessity due to the complexity of setting up the right Registry keys, services etc. We have some simple deployment scripts that work on UNIX, ultimately we'd like to use both and make a common lightweight deployment tool.
We're hoping the IIUG tool will get a few people trying it, telling us what they'd like to see and how to make it better.

3 localhost commented Trackback

I am really just asking for completeness. I just want to be able to say to business partners that I work with that either approach is viable. There may, for example, be some data centre or hosting centre which is fussy about running images they didn't create.

4 localhost commented Trackback

> There may, for example, be some data centre or hosting > centre which is fussy about running images they > didn't create.That's valid, and I agree it would be a good solution. Particularly deploying to a whole batch of virtualized machines via a shared drive for example.

5 localhost commented Permalink

Hi Guy,

recently I had to move an existing installation to a new PC. As I had to return the old one when the new one came in could not connect the both. So I robocopied the whole %INFORMIXDIR% somewhere else beforehand. Before I found the time to recreate the installation I found this tool (thanks to RSS). I have some experience in moving Informix installations this way and I did it before with the help of regedit export/merge, a text editor and sc. This involved quite a bit of manual work and I tried lwt_install.
I tried to get everything at once and asked lwt_install to perform the robocopy step for me:
lwt_install -unzip "robocopy \\backupserver\infback c:\informix /E" - port 12345 -p ...
Apparently it does merely nothing. Did I miss something?
Besides this issue, it created the necessary registry entries and the services as expected.
Do you plan to extend lwt_install to create users and groups?

6 localhost commented Trackback

Hi Christian,

Thanks for trying it. There is code in there to create users and groups. We're looking into it now. Could you possibly email me with the Windows OS version you're using, and whether you're installing on a domain controlller or any other factors?guyb -at- us.ibm.comI hope we'll be about to get a fix to you, and then upload it to IIUG.Thanks

Add a Comment Add a Comment