November Archives October 2012 August 2013 July 2012 June 2012 May 2012 April 2011 March 2011 March

NET Active Directory ADSI Lord AIK CIM desktop BIOS ESX ESXi Event forwarding FSRM FTSRGIT Rings IAS Impersonation Group Policy IPSec iSCSI Java JNI LDAP Linux NTFS MDT NPS openwsman Performance PowerShell PXE RD RRAS VPN Storage Server for VMware vSphere vCenter VDR WDS WLAN WinRM Windows WMI WS Management WSUS
November Archives October 2012 August 2013 July 2012 June 2012 May 2012 April 2011 March 2011 March 2011 March 2011 March 2011 September 2010 August 2010 July 2010 June 2010 May 2010 April 2010 March 2010 September 2009 August 2009 July 2009 May 2009 April 2009 March 2009 2009
The context dedouanement of the current IRF was the topic of configuration management, which I WMI and WS-Management took part. The WS-Management by first tested using WinRM, but is not it a platform-independent standard real test if you really use two different platforms:-) So I started to set up the test system dedouanement is an open-source Linux server openwsman the WS-Management implementation. [Note for Linux is much less valuable than Windows, so you can make a couple of things could be easier to do it].
The first challenge to the right meant that few actually have a stable distribution package out of it. Search Snétberger Suse RPM on there at rpmfind dedouanement to Fedora's package in Ubuntu, there is already something (though only part of the server, the command-line tool wsmancli put up, and 2.0, rather than 2.1) , but I could not find anything from CentOS. (Maybe that would be good to fedoras, but I only found out later. Anyway I can, hopefully it goes to other types of systems based on it.) So I can install source :)
The SourceForge download the source, currently 2.1 current. These can be downloaded from the links below: # wget # wget http://fastbull.dl.sourceforge.net/sourceforge/openwsman/wsmancli-2.1.0.tar.bz2 http://freefr.dl.sourceforge.net/sourceforge/openwsman /openwsman-2.1.0.tar.bz2
Please read the README, describing in (:) mostly the process of installation and configuration. The installation dedouanement of the usual ./configure, make, make install triples can be carried out. The ./configure's is an important parameter, which is the -sysconfdir. With this you can specify that it be placed under the / etc configuration file and not the default / usr / local / etc on. I just do not use it, but I run with the default settings. ./configure # # Make # make install
As it says in the README also a number of other packages are needed to openwsman. Idemásolom what ./configure complaining about this and what packages are needed: configure: error: No Acceptable C compiler found in $ PATH -> gcc checking for XML ... configure: error: Package Requirements (libxml-2.0) Were not met -> libxml2-devel configure: error: the curl-config script installed by libcurl dedouanement could not be found. dedouanement libcurl is required for tests. -> Curl-devel
The translation dedouanement will still complain then that g ++ command can not find this package gcc-c ++ need. So they must be installed using yum: # yum install gcc # yum install gcc-c ++ # yum install dedouanement libxml2-devel # yum install curl-devel
The translation was taking a while, but if all goes well, then there is no error, and can be installed using make install. Written an important thing during installation (which dedouanement I did not even notice at first, after some searching, and have saved :): Libraries have been installed in / usr / local / lib / openwsman / If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either has use libtool, dedouanement and specify the full pathname of the library, or use the `-LLIBDIR 'flag During linking and do at-least one of the Following: - add LIBDIR to the` LD_LIBRARY_PATH' During execution environment variable - add LIBDIR to the `LD_RUN_PATH 'environment variable During linking dedouanement - use the` -Wl - RPATH -Wl, LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf '
Yes, the later wsman example. openwsman will not find the shared libraries (shared libraries). In setting the LD_LIBRARY_PATH or help each time / user, or once and for all solve the /etc/ld.so.conf editing: # echo "/ usr / local / lib" >> dedouanement /etc/ld.so.conf # ldconfig Compile and install third wsmancli
After installing the foregoing, the wsmancli easy. I had a pitfall, pkg-config not found the openwsman is: No package 'openwsman' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
When installed, you can watch wsman -help help to start or not. (Note:. Bit strange the name of the downloaded file name wsmancli, wsman the command name, and the names of the websites link to it :) openwsman CLI configuration of 4 openwsmand
In order that we can test in local machine that works all the openwsmand and the wsman, ELOS