1.

ocsinventory_ng.png doc:connectors:ocsinventory_ng:help

1.1. Description

This connector will search your OCS database for the computername and display the results.

1.2. Installation

Simple install the connector via settings->connectors.

1.3. Configuration

You can reach the configuration in the main settings module in the connectors section. There is a "Configuration" link behind the conncetor if the connector is installed.
ocsinventory_ng_config.png
  • Hostname the hostname where ocsinventory server is located.
  • Username the user to access the ocsinventory server.
  • Password the password for the user to access the ocsinventory server.
  • The hostname will be used to generate the links to access the soap interface:
  • http://HOSTNAME/Apache/Ocsinventory/Interface
  • http://HOSTNAME/ocsinterface

  • For more informations check the documentation of OCS:
  • http://wiki.ocsinventory-ng.org/index.php/Developers:Web_services
  • http://www.ocsinventory-ng.org/index.php?mact=News,cntnt01,detail,0&cntnt01articleid=98&cntnt01returnid=80

  • 1.4. Usage

    After configure your os inventory server will be searched for this hostname.

    2.

    rt.png doc:connectors:rt:help

    2.1. Description

    Connect your RT http://bestpractical.com/rt/ database. This connector will search your RT database for the current computername to display all requests.

    2.2. Installation

    Simple install the connector via settings->connectors.

    2.3. Configuration

    You can reach the configuration in the main settings module in the connectors section. There is a "Configuration" link behind the conncetor if the connector is installed.
    rt_config.png
  • Database user the user to access the rt database.
  • Database password the password for the database user to access the rt database.
  • Database host the hostname where the rt database is located.
  • Link to rt host link to your request tracker host. This link will be used to generate links to the tickets.

  • 2.4. Usage

    After configure you should see all tickets found in the rt database:
    rt_view.png
    You can click on the Ticket ID or the Subject to go directly to the ticket.

    3.

    dns_ldap.png doc:connectors:dns_ldap:help

    3.1. Description

    Manage DNS entries for the systems.

    3.2. Installation

    Simple install the connector via settings->connectors. You will need also the dns_ldap module installed.

    4.

    remotecmd.png doc:connectors:remotecmd:help

    4.1. Description

    Specify and run remote commands. You can run remote commands on ssh enabled hosts (module ssh_client needed) and on windows machines.

    4.2. Installation

    Simple install the connector via settings->connectors. You will need also the ssh_client and computer module installed.

    4.3. Configuration

    In the main configuration you have to set the path to psexec.exe on windows systems. On Linux set the path to winexe.
    remotecmd_pathsettings.png
  • Path to winexe (on windows path to psexec.exe): Full path to winexe/psexec
  • winexe/psexec options: Options for the command psexec: use -s to run it on the system account winexe: --interactive=0 --system to run it on the system account --uninstall to remove the service after execution

  • 4.3.1. Configure credentials


    remotecmd_credentials_new.png
  • Name: Uniq name of the credentials
  • Username: The remote username to run the command
  • Password: The password for the remote user - for ssh you have to provide the username which ssh keys should be used

  • You can view, edit and delete the credentials from this view:
    remotecmd_credentials.png

    4.3.2. Configure commands

    remotecmd_commands_new.png
  • Name: Uniq name of the command
  • Type: Choose if this is a ssh or winexe/psexec command
  • Default credentilas: Choose the default credentials to use with this command
  • Command: The contents of the command

  • Here is an example to use the scanwinupdates.js to scan hosts for updates:
    @echo off
    IF EXIST z: net use z: /DELETE
    net use z: \\ntinstall\install secretpassword /USER:DOMAIN\user
    cscript /nologo z:\bin\scanwinupdates.js > z:\updates\scans\%COMPUTERNAME%.xml
    net use z: /DELETE
    

    You can view, edit and delete the commands from this view:
    remotecmd_commands.png

    4.3.3. Logs

    You can view and delete the logs from this view.
    remotecmd_logs.png

    4.4. Usage

    4.4.1. Run command from the connector

    Simple choose the command and press "run". This will execute the selected command with the default credentials for this command. If you want to use your own credentials choose the entry "Use own credentials" and set your username and your password. If you want to run an ssh command with your own credentials you have to set the username to the remote users name (e.g. root) - you dont need to specify a password because the ssh command will use your ssh_keys.
    remotecmd_run.png

    4.4.2. Run commands via cron / script

    Here is an example script which runs commandid 3 with the default credentials on host: host.example.com
    #!/usr/bin/php5 -f
    <?php
    //global settings
    $INCexternal="/var/www/install/uranos-svnroot/www/include/INCexternal.php";
    //require system
    require_once ($INCexternal);
    ini_set ('display_errors',true); ini_set ('display_startup_errors',true); error_reporting(E_ALL^E_NOTICE);
    if (!require_connector_file('remotecmd','connector.php')) { exit; } $host='host.example.com'; $out=remotecmd_run($host,3); echo "* command executed on host $host:n"; echo $out['command']; echo "n"; if ($ret['stat']==0) { echo "* command run with exit state 0n"; } else { echo "* command failed with exit state ".$ret['stat']."n"; } echo "* Output:n"; if (is_array($out['out'])) { foreach ($out['out'] as $o) { echo $o."n"; } } ?>

    Here is an example to run a command on each host in group "example" with username and password:
    #!/usr/bin/php5 -f
    <?php
    //global settings
    $INCexternal="/var/www/install/uranos-svnroot/www/include/INCexternal.php";
    //require system
    require_once ($INCexternal);
    //required for the getGROUPCOMPUTERS
    $INCuser="/var/www/install/uranos-svnroot/www/include/APIuser.php";
    require_once ($INCuser);
    ini_set ('display_errors',true);
    ini_set ('display_startup_errors',true);
    error_reporting(E_ALL^E_NOTICE);
    if (!require_connector_file('remotecmd','connector.php')) { exit; } //Select hosts the groupid is the id of the group $groupid=2; $examplehosts=getGROUPCOMPUTERS($groupid); if (is_array($examplehosts['entries'])) { foreach ($examplehosts['entries'] as $h) { $host=$h['computername']; $out=remotecmd_run($host,3,"Adminsitrator","seCret"); echo "* command executed on host $host:n"; echo $out['command']; echo "n"; if ($ret['stat']==0) { echo "* command run with exit state 0n"; } else { echo "* command failed with exit state ".$ret['stat']."n"; } echo "* Output:n"; if (is_array($out['out'])) { foreach ($out['out'] as $o) { echo $o."n"; } } } } ?>

    5.

    rsyslog.png doc:connectors:rsyslog:help

    5.1. Description

    If you install this connector you will be able to see syslog messages for the system and are able to configure the client.

    5.2. Installation

    Simple install the connector via settings->connectors. This connector requires the rsyslog module.

    5.3. Statistic

    rsyslog-connector-statistic.png
    Here you see a statistical view about all assigned tables for the client. From here you can jump to the table or directly to the filtered messages behind the lines. You can set the timespan at the top.

    5.4. Configuration

    rsyslog-connector-configuration.png
    Here you can configure the client filter and the client to server/db assignement.
  • 1 Add the client configuration to a server and assign it to a table
  • 2 Write the client configuration to the specified file, currently only rsyslog config is supported, the file will be overwritten on the client
  • 3 See the filename and the config which will be created on the client
  • 4 See and delete the assignemnt to a server, from here there is a link to write the server config which is needed if you assign a client to a server
  • 5 The main Client configuration, set the filters you need the init script and the filename which will be written on the client. The filer IP and filer hostname will be ignored for the client config and is only set on the server

  • 5.5. Commands

    rsyslog-connector-commands.png
    Here you can run the following commands on the client: start, stop, reload and restart. If you access this page the command status will be passed to the init script.

    6.

    dhcp_ldap.png doc:connectors:dhcp_ldap:help

    6.1. Description

    Manage IP addresses for each macaddress from the system.

    6.2. Installation

    Simple install the connector via settings->connectors. You will need also the dhcp_ldap module installed.

    6.3. Configuration

    Please check the settings of the dhcp_ldap module.

    6.4. Usage

    You can add an IP address for each macaddress - if you need also with specified options:
    dhcp_ldap_connector.png

    7. Inventory

    fusioninventory.png Inventory

    7.1. Description

    View your inventory for this system.

    7.2. Installation

    Simple install the connector via settings->connectors. You will need also the fusioninventory module installed.

    7.3. Configuration

    Please check the settings of the fusioninventory module.

    7.4. Usage

    If the hostname is found you can assign one or more fusioninventory hardware-id[s] to this host. You have a link to each section on the top of this connector:
    fusioninventory_connector.png
    In the sections you see the keys and values:
    fusioninventory_connector_view.png

    8.

    cron.png doc:connectors:cron:help

    8.1. Description

    If you install this connector you will be able to add cron scripts to each system.

    8.2. Installation

    Simple install the connector via settings->connectors. This connector requires the cron module.

    8.3. Configuration

    See the cron module configuration.

    8.4. Usage

    9.

    systemnetwork.png doc:connectors:systemnetwork:help

    9.1. Description

    If you install this connector you will be able to see the arp entries and network infos from the switch.

    9.2. Installation

    Simple install the connector via settings->connectors. You also need the cron and the switch module to view all infos.

    9.3. Configuration

    You can reach the configuration for cron via the module configuration. The cron module is used to add the entries from the arpwatch database. The switch module will give you the availability to locate this host on the switchport and if configured you will see the room where this host is currently attatched.

    9.4. Usage

    After configure should view the last entries from the arp. This view will be generated by searching the systems_arp table for each mac address assigned to this host:
    systemnetwork_arp.png
    This is the view of a network port where one macaddress is found:
    systemnetwork_switch.png

    10.

    radius_ldap.png doc:connectors:radius_ldap:help

    10.1. Description

    Assign a VLAN to each mac address from each system.

    10.2. Installation

    Simple install the connector via settings->connectors. You will need also the radius_ldap module installed.

    11.

    bugzilla.png doc:connectors:bugzilla:help

    11.1. Description

    Connect your BUGZilla database. This connector will search your bugzilla database for the current computername to display all requests.

    11.2. Installation

    Simple install the connector via settings->connectors.

    11.3. Configuration

    You can reach the configuration in the main settings module in the connectors section. There is a "Configuration" link behind the conncetor if the connector is installed.
    bugzilla_config.png
  • Database user the user to access the bugzilla database.
  • Database password the password for the database user to access the bugzilla database.
  • Database host the hostname where the bugzilla database is located.
  • Link to bugzilla host link to your bugzilla host. This link will be used to generate links to the tickets.
  • Comma seperated list of fields to search define which fileds should be searched for the computer name.

  • 11.4. Usage

    After configure you should see all tickets matching defined searchfileds:
    bugzilla_view.png
    You can click on the Ticket ID or the Subject to go directly to the ticket.

    12.

    checklist.png doc:connectors:checklist:help

    12.1. Description

    Generate your own checklists. This can be assigned to each system and be processed from different users.

    12.2. Installation

    Simple install the connector via settings->connectors.

    12.3. Configuration

    You can reach the configuration in the main settings module in the connectors section. There is a "Configuration" link behind the conncetor if the connector is installed.
    Add a new check-list:
    checklist_new.png
  • Name: Chooce a name for the check-list.
  • Comment: Add a comment for the check-list.

  • checklist_edit_content_1.png
  • Edit content to edit and add parts to the check-list.

  • checklist_edit_content_2.png
  • Add new ckeckfield to add a new part to the check-list.

  • You can also edit single parts of the check-list:
    checklist_edit_content_3.png

    12.4. Usage

    In the computer view you have to chooce the Checklists connnector:
    checklist_add.png
    You can add more than one checklist to an computer. You only can delete the already assigned check-list if you have the permissions to do that. After adding a check list you can run the checks by clicking the *edit* button behind the assigned check-list.
    checklist_check_1.png
    Add your comments and check the part of the check-list behind the comment field to approve this part of the check-list.
    checklist_check_2.png
    After that you see the user and the time when this part of the check-list was approved:
    checklist_check_3.png

    13.

    comments.png doc:connectors:comments:help

    13.1. Description

    If you install this connector you will be able to add comments to each system.

    13.2. Installation

    Simple install the connector via settings->connectors.

    13.3. Configuration

    There is no need for a configuration.

    13.4. Usage

    In the computer view you have to chooce the Comments connnector. After that you can add a new comment:
    comments_1.png
    You see all comments and comments of comments in a date ordered view:
    comments_2.png
    You can comment, edit and delete a comment.

    14.

    ldaphosts.png doc:connectors:ldaphosts:help

    14.1. Description

    This connector will search your LDAP database for the computername and display the results.

    14.2. Installation

    Simple install the connector via settings->connectors.

    14.3. Configuration

    You can reach the configuration in the main settings module in the connectors section. There is a "Configuration" link behind the conncetor if the connector is installed.
    ldaphosts_config.png
  • User the user DN to connect to the ldapserver, leave empty if anonymouse bind is wanted.
  • Password the password for the user DN.
  • Host the hostname of the ldap server.
  • BaseDN the base DN, the search will be performed in the base of this DN.
  • Port the port of the ldap server.
  • Entry name the attr name for the DN to search, e.g. cn.
  • Search samba host the base DN for search samba host entries.

  • 14.4. Usage

    After configure your ldap server will be searched for the hostname.
    Here is an example of an ipHost:
    ldaphosts_entry.png
    Here is an example of an Samba host:
    ldaphosts_entry_samba.png