solicasting.blogg.se - Activetcl 8.4

#ACTIVETCL 8.4 INSTALL#
#ACTIVETCL 8.4 PASSWORD#
#ACTIVETCL 8.4 WINDOWS#

Maybe we can check out other incarnations of Expect like DejaGNU.

#ACTIVETCL 8.4 WINDOWS#

I have only got it to work with Windows Server 2008 R2.

For some reason, ActiveTcl does not play nicely with Windows Server 2012, it always fails recognize the text that it is expecting, so it times out and moves to the next command.

#ACTIVETCL 8.4 INSTALL#

If your Orchestrator machine is behind a proxy or cannot reach the internet (which is required to install the “Expect” functionality within ActiveTcl), please install version 8.4.x of ActiveTcl then on top of it install the latest version, as version 8.4.x ships with “Expect” functionality pre-installed (make sure you select “Merge repository” option with installing 8.6.x on top of 8.4.x).

This scenario has not been tested for a highly available Orchestrator implementation, but in order for it to work, all temp files must be saved in a shared location, and all the prerequisite tools must be installed with same configuration on all Runbook servers.

SSH/Telnet passwords will be sent and saved in clear text unless you specify a key file for authentication.

Bitvise WinSSHD In case you do not have a Unix/Linux machine to test with, you can use this virtual SSH server on any windows machine.

PuTTY (must be the installer version to make sure you have installed plink as well).

ActiveState ActiveTcl (must be 32-bit version to support “Expect”).Instead, we will call Tcl and instruct it to call PuTTY with the required command and parameters. However, in order to add the “Expect Script” functionality to our flows, we will not directly call (PuTTY) from our workflows. So bear with me a little longer with this introduction, it will make things easier afterwards.īehind the scenes, System Center Orchestrator user plink (PuTTY) to execute SSH Commands using the “Run SSH Command” activity, so we will do the same, since PuTTY is a very dependable SSH/Telnet client, you could use any incarnation of OpenSSH if you prefer. While Tcl as a concept is a little beyond the scope of this article, we must understand some basic concepts about the role Tcl plays in our little scenario.

While the “Expect Script ” methodology is not very well documented, it is available in many incarnations, one of which exists as a feature in a tool called “ActiveTcl”.ĪctiveTcl is a “Tool Command Language”, which is some sort of a scripting language that is dedicated to controlling and commanding other tools. This expect script for example would reply to a couple of prompts asking the user for first and last name within the script. Other technologies, like for example HP’s Operations Orchestration, has introduced the use of what is known as “Expect Scripts”, which would simply guide the shell into sending different commands once it has recognized certain text or regular expression in the StdOut of the shell.įor example it would go something like this:

#ACTIVETCL 8.4 PASSWORD#

Or maybe, the script is expected to ask for a username and password to connect to a FTP server, how then would you supply these inputs, without actually changing the script itself? While this is great for executing straight forward commands and scripts, it lacks the ability to interact with the shell and maybe execute different options or commands based on how this script actually goes. System Center Orchestrator ships with an activity called “Run SSH Command”, which is great for executing a single command, or a script file to a Unix/Linux machine. One of these gaps that needs to be filled is automating SSH, Telnet, and Batch scripts. As promising as System Center Orchestrator is with all the Integration Packs that are being developed every day, there still are some gaps to fill to be able to compete in specific scenarios in the real world.