Difference between revisions of "Site Integration Services"

From Hornbill
Jump to navigation Jump to search
 
(125 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{bluebanner|[[Main_Page|Home]] > [[Administration]] > [[IT Operations Management|ITOM]] > Site Integrations Services|[[:Category:ITOM|Index]]}}
 
{{bluebanner|[[Main_Page|Home]] > [[Administration]] > [[IT Operations Management|ITOM]] > Site Integrations Services|[[:Category:ITOM|Index]]}}
 
{{IntroAndLinks|
 
{{IntroAndLinks|
−
Hornbill's Site Integration Service (SIS) is a package that needs to be installed on a server within your organization. It runs as a standard Windows NT Service and once paired with your Hornbill instance, monitors the ITOM Job Queue for any jobs that it needs to execute. The SIS polls the paired Hornbill instance every 5 seconds, acting as the heartbeat to the cloud.  
+
Hornbill's Site Integration Service (SIS) is a Windows NT Server service installed on a server behind an organisation's firewall. It runs as a standard Windows NT Service and, once paired with a Hornbill instance, monitors the ITOM Job Queue. The SIS connects to the instance order to retrieve jobs that have been placed on the job queue for execution.<br>
 
<br>
 
<br>
 +
Should jobs be detected during a polling interval, the SIS pulls all information from the paired instance regarding the jobs required to be undertaken on specified devices on the network. There are currently two types of job available; Computer Discovery and IT Automation. Automation jobs are powered via pre-built packages provided by Hornbill or can be custom-built using the ITOM Package Creator.<br>
 
<br>
 
<br>
−
The SIS is self updating and is accessible via a web page, which allows for the initial pairing and display of the current status of the service.  
+
A web interface is provided, which allows for the initial pairing and display of the service's current status. The service is self-updating and will detect if a new version has been made available within the cloud and, if so, download and install it automatically.  All communications with the cloud will always be initiated locally from the SIS to the cloud and never from the cloud.
 
<br>
 
<br>
−
<br>
+
|* [[IT Operations Management]]
−
Should jobs be detected during a polling interval, the SIS pulls all information from the paired instance with regards to the jobs that are required to be undertaken on specified devices on the network. There are currently two types of job that can be initiated; Computer Discovery and IT Automation. Automation jobs are powered via pre-built packages provided by Hornbill or can be custom-built using the ITOM Package Creator.
 
−
|
 
−
* [[IT Operations Management]]
 
 
}}
 
}}
  
 
==Technical Considerations==
 
==Technical Considerations==
 
===System Requirements===
 
===System Requirements===
−
* OS: Windows Server 2012, 2012 R2, 2016 or 2019
+
* OS: Windows Server '''2012, 2012 R2, 2016, 2019 or 2022'''
−
* RAM: 4GB
+
* RAM: '''4GB'''
−
* Free Disk: 10GB
+
* Free Disk: '''10GB'''
 
* CPU load is minimal
 
* CPU load is minimal
 
* Can be run on virtual as well as physical machines.
 
* Can be run on virtual as well as physical machines.
  
 
===Connectivity===
 
===Connectivity===
−
* The SIS communicates with your Hornbill instance using HTTPS.
+
* The SIS communicates with a Hornbill instance using the secure HTTPS protocol.
−
* Your Hornbill instance will only respond to pings from a paired SIS.
+
* Hornbill instances will only respond to a successfully paired SIS.
−
* Proxies are not yet supported by the SIS.
+
{{infobox|Currently, support for communications via a proxy service is not available.}}
 +
 
 +
===Discovery and Package Deployment===
 +
The SIS is capable of discovering the following devices:
 +
* Windows 32/64bit Computers
 +
*: Currently supported by Microsoft
 +
* Unix/Linux/Mac Computers running ssh
 +
 
 +
Depending on the content of the deployment package, there may be additional OS requirements.
  
−
===Discovery and Deployment===
+
===Firewall Configuration===
−
The SIS is capable of discovering all Windows machines and deploying ITOM Packages on those 32 and 64 bit Windows operating systems currently supported by Microsoft. Depending on the content of the package, there may be additional OS requirements}}
+
A Windows firewall rule for Inbound traffic (Local subnet) that allows all TCP traffic into the SIS service executable is created on installation and named:
 +
*: '''Hornbill SIS Server - Context Callback (TCP - In)'''.
  
−
== Download the Hornbill SIS==
+
The following outbound ports between the SIS server and the cloud instance are required:
−
The Hornbill SIS package can be downloaded from Hornbill Administration via '''''Home > ITOM > Site Integration Services''''' and clicking the button labelled "Download Site Integration Server". The SIS package is downloaded as an executible (.exe).
+
*: HTTPS '''TCP 443'''
  
 +
The following ports between the SIS server and Managed Devices are required, dependant on which method is adopted to retrieve Inventory details:
 +
* WinRM - '''TCP 5985'''
 +
* DCOM - '''TCP 135'''
 +
* DCOM - Range of dynamic ports:
 +
*: '''TCP 49152-65535''' (RPC dynamic ports – Windows Vista, 2008 and above)
 +
*: '''TCP 1024-65535''' (RPC dynamic ports – Windows NT4, Windows 2000, Windows 2003)
  
 +
* Site Integration Service Discovery (Dependant on the discovery mode used)
 +
** Active Directory / LDAP
 +
*::'''TCP Port 389''' (Between the SIS and the AD Domain Controller / LDAP Server)
 +
** Secure Shell (ssh)
 +
*::'''TCP Port 22''' (Between the SIS and target devices)
 +
The following is required to support the TCP Ping test used during discovery (only required if the feature is in use):
 +
*ICMP Echo Reply
 +
 +
== Toolbar==
 
[[File:SISToolbar.png|centre|1000px]]
 
[[File:SISToolbar.png|centre|1000px]]
−
<br>
+
 
−
<br>
 
−
Description of the options found in the SIS Toolbar (beginning from the left):
 
 
:{|
 
:{|
 
|- valign="top"  
 
|- valign="top"  
 +
|
 +
{{Bullet1|Refresh|A refresh of the list may be required to display any new devices discovered while you are viewing the list}}
 +
{{Bullet1|Show|Displays Connectors from the selected Group}}
 +
{{Bullet2|+ Create Group|(Selectable via the drop-down) allows for the Creation of SIS Groups'}}
 +
{{Bullet1|Paired / Not Paired|Toggle button that allows the display of '''Paired''' or '''Not Paired''' SIS}}
 
|style="width:600px"|
 
|style="width:600px"|
−
:* '''Refresh''' - A refresh of the list may be required to display any new devices discovered while you are viewing the list
+
{{Bullet1|Download Site Integration Server|Downloads the on-premise SIS Installer}}
−
:* '''Show''' - Displays Connectors from the selected Group
+
{{Bullet1|Move Selected To...|Moves the selected SIS entries to the selected Group}}
−
:* '''+ Create Group''' - (Selectable via the drop-down) allows for the Creation of SIS Groups'
+
{{Bullet1|[[File:NewPackageButton.png|23x22px]]|Add a new SIS Connector}}
−
:* '''Paired / Not Paired''' - Toggle button that allows the display of '''Paired''' or '''Not Paired''' SIS
+
{{Bullet1|Delete|Deletes the selected SIS entries}}
−
|style="width:600px"|
 
−
:* '''Download Site Integration Server''' - Downloads the on premise SIS Installer
 
−
:* '''Move Selected To...''' - Moves the selected SIS entries to the selected Group
 
−
:* [[File:NewPackageButton.png|23x22px]] - Add a new SIS Connector
 
−
:* '''Delete''' - Deletes the selected SIS entries
 
 
|}
 
|}
  
−
<br>
+
== List ==
−
 
+
[[File:SISListBlur.png|right|450px|link=https://wiki.hornbill.com/images/6/69/SISList.png]]
−
== Install the Hornbill SIS==
+
:{|
−
[[File:InstallerPage.png|300px|thumb|right|<div align="center">'''Click "Install" to begin installing the SIS'''</div>]]
+
|- valign="top"  
−
[[File:StartSisMmcService.png|300px|thumb|right|link=https://wiki.hornbill.com/images/c/ca/StartSisMmcService.png|<div align="center">'''The Site Integration Service is installed as a Windows NT Service called "ESPSisService"'''</div>]]
+
|
−
Once downloaded, the Hornbill SIS is installed as a Windows NT Service. Local administration rights will be required on the computer where the SIS is to be installed.
+
{{bullet1|Name|The name of the Connector}}
−
<br>
+
{{Bullet1|Group|The group that the Connector belongs to}}
−
<br>
+
{{Bullet1|Description|The user-provided description for the connector}}
−
<ol style="list-style-type: decimal;">
+
{{Bullet1|Service Type|Operating system architecture of the Server hosting the SIS installation}}
−
<li>Locate the downloaded executable and double click to begin</li>
+
|
−
<li>Click Install</li>
+
{{Bullet1|Service State|Toggle to enable or disable the SIS}}
−
<li>Click Ok to Confirm the Installation</li>
+
{{Bullet1|Online Status|The current status of the link to the SIS service.}}
−
<li>Close the Install dialog</li>
+
{{Bullet1|Service Build|SIS Server build version.  Any Service showing an older build may highlight that there is an issue with automatic updates for that service}}
−
<li>Open the Services MMC Console</li>
+
{{Bullet1|Last Seen On|this will display the last time there was communication between the Hornbill SIS Service and the SIS Server}}
−
<li>Start the '''EspSisService'''</li></ol>
+
|}
−
<br>
+
==Creating an SIS Service Profile on the Hornbill Instance==
−
<br>
 
−
 
 
−
== Creating a SIS Connector in your Hornbill Instance==
 
 
<ol style="list-style-type: decimal;">
 
<ol style="list-style-type: decimal;">
−
<li>Navigate to '''Hornbill Administration > Home > ITOM > Site Integration Services'''</li>
+
<li>Navigate to '''Administration > Hornbill ITOM > Site Integration Services'''</li>
−
<li>Click the [[File:NewPackageButton.png|23x22px]] button to add a new SIS Connector</li>
+
<li>Click the [[File:NewPackageButton.png|23x22px]] button to create a new SIS Connector</li>
 
<li>Enter the following details:
 
<li>Enter the following details:
 
<ol style="list-style-type: none;">
 
<ol style="list-style-type: none;">
Line 80: Line 97:
 
<blockquote>[[File:SISAuthKey.png|350x79px|Image: 350 pixels]]</blockquote>
 
<blockquote>[[File:SISAuthKey.png|350x79px|Image: 350 pixels]]</blockquote>
 
<ol start="5" style="list-style-type: decimal;">
 
<ol start="5" style="list-style-type: decimal;">
−
<li>The Authorisation Key is displayed, and should be recorded for later use</li>
+
<li>The Authorisation Code is displayed, and should be recorded for later use</li>
 
<li>See the next section for details of how to pair your SIS with your Hornbill instance</li>
 
<li>See the next section for details of how to pair your SIS with your Hornbill instance</li>
 
<li>Should you choose not to complete the pairing at this time, the connector can be found by selecting the '''Not Paired''' filter in your list of SIS Connectors</li></ol>
 
<li>Should you choose not to complete the pairing at this time, the connector can be found by selecting the '''Not Paired''' filter in your list of SIS Connectors</li></ol>
  
−
{{infobox|The Authorisation Key is valid for 1 hour. Should the SIS connector and SIS installation not be paired during this time, the key will expire and the unpaired SIS connector will be removed}}
+
{{infobox|The Authorisation Code is valid for 1 hour. Should the SIS connector and SIS installation not be paired during this time, the key will expire.  To generate a new Key, remove the SIS connector and recreate it.}}
  
−
== Pairing a SIS with your Hornbill instance ==
+
== Downloading and Installing the SIS Service ==
−
Once the ESPSisService is running, you can begin the process of pairing it to your Hornbill instance.
+
[[File:InstallerPage.png|300px|thumb|right|<div align="center">'''Click "Install" to begin installing the SIS'''</div>]]
 +
[[File:StartSisMmcService.png|300px|thumb|right|link=https://wiki.hornbill.com/images/c/ca/StartSisMmcService.png|<div align="center">'''The Site Integration Service is installed as a Windows NT Service called "ESPSisService"'''</div>]]
 +
The Hornbill SIS is installed as a Windows NT Service and will require local administration rights for installation on the target computer.
 
<br>
 
<br>
 
<br>
 
<br>
 
<ol style="list-style-type: decimal;">
 
<ol style="list-style-type: decimal;">
−
<li>Open the Browser and navigate to <nowiki>http://localhost:11117</nowiki>. If you're already there, refresh the page</li>
+
<li>Navigate to: '''Administration > Hornbill ITOM > Site Integration Services'''</li>
−
<li>After several seconds, you will be prompted for your instance id and an authorization code</li>
+
<li>Click the '''Download Site Integration Server''' button on the toolbar</li>  
−
<li>If you already have an authorization code, skip to step 10, otherwise continue with the next step.</li>
+
<li>Locate the downloaded executable (.exe), and double click to begin</li>
−
<li>To obtain an Authorization code, a new SIS connector must be added to the SIS list in '''Hornbill Administration > Home > ITOM > Site Integration Services'''</li>
+
<li>Click '''Install'''</li>
−
<li>At the top right of the list in Hornbill Administration, click the "+" button to add a new SIS connector</li>
+
<li>Click '''Ok''' to Confirm the Installation</li>
−
<li>Add an appropriate name and description and click "Add Site Integration Service Connector"</li>
+
<li>Close the Install dialog</li>
−
<li>Details of the new SIS entry will appear, including an Authorization code.</li>
+
<li>Open the '''Services mmc''' console</li>
−
<li>Copy the Authorization code</li>
+
<li>Start the '''EspSisService''' if it isn't already running</li></ol>
−
<li>Return to the SIS pairing page page <nowiki>http://localhost:11117</nowiki></li>
+
<br>
−
<li>Enter the instance ID and authorization code</li></li>
+
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
 
 +
== Pairing an SIS Server with a Hornbill Instance ==
 +
Once the '''EspSisService''' is running, the process of pairing the service with a Hornbill instance can begin, which will require an Authorization Code.  This code will have been provided while creating an SIS connector. See the section [[Site Integration Services#Creating an SIS Service Profile on the Hornbill Instance|Creating an SIS Connector on the Hornbill Instance]].
 +
<br>
 +
<ol style="list-style-type: decimal;">
 +
<li>Open the Browser and navigate to '''<nowiki>http://localhost:11117</nowiki>'''.</li>
 +
After a short pause, a prompt for the Instance Id and an Authorization Code appears
 +
<li>Enter the Instance ID and Authorization Code</li></li>
 
<li>Click the '''Pair with Instance''' button</li></ol>
 
<li>Click the '''Pair with Instance''' button</li></ol>
−
<gallery class="center">
+
<gallery mode=packed heights=200px>
−
File:ITOM_Hornbill_Site_Integration_Server_Localhost.JPG|Your Instance ID and valid authorization code are required to pair an SIS with your Hornbill instance
+
File:ITOM_Hornbill_Site_Integration_Server_Localhost.JPG|The Instance ID and valid Authorization Code are required to pair an SIS with your Hornbill instance
−
File:SISHomePage.png|Once paired, the SIS status is reviewable via <nowiki>http://localhost:11117</nowiki>
+
File:SISNewHomePage.png|Once paired, the SIS status is reviewable via <nowiki>http://localhost:11117</nowiki>
 
</gallery>
 
</gallery>
  
−
== Managing the List of Site Integration Services==
 
−
Any Site Integration Service connectors you have created can be viewed and managed in the SIS list found in '''''Hornbill Administration > Home > ITOM > Site Integration Services'''''. The list displays the following information:
 
−
:* '''Name''' - the name of the Connector (provided when first created)
 
−
:* '''Group''' - displays the group that the Connector belongs to
 
−
:* '''Description''' - displays any further detail you've provided about the connector
 
−
:* '''Service Type''' - shows the operating system architecture of the Server hosting the SIS installation (64 or 32-bit)}}
 
−
:* '''Service State''' - lets you enable or disable the SIS
 
−
:* '''Online Status''' - displays the current status.
 
−
:* '''Service Build''' - displays the SIS Server version.  Any Service showing an older build may highlight that there is an issue with automatic updates for that service
 
−
:* '''Last Seen On'''- this will display the last time there was communication between the Hornbill SIS Service and the SIS Server
 
−
<br>
 
−
<br>
 
 
== Grouping Site Integration Servers ==
 
== Grouping Site Integration Servers ==
−
The creation of groups enable SIS connectors, and thus SIS installations, to be logically grouped together. A group can consist of a single SIS. Multiple SIS installations may be necessary depending on the environment and potential load and also allows for the provision of failover protection. The number of SIS installations will be dependant on the environment and your needs.  
+
The creation of groups enables SIS connectors and SIS installations to be logically grouped; each SIS entry must belong to a single group. A "Default" group is provided with the option to create additional groups as required. Generally, the network infrastructure, load balancing and failover requirements will determine the number and grouping of SIS installations.
  
 
{{Bullet1|Load Balancing|When more than one server is placed within a group, Jobs sent to the group for processing will be processed by the next available SIS server spreading the load.}}
 
{{Bullet1|Load Balancing|When more than one server is placed within a group, Jobs sent to the group for processing will be processed by the next available SIS server spreading the load.}}
−
{{Bullet1|Failover protection|SIS servers all poll the Job queue for jobs and thus if a server fails one of the other servers its group will pick the next available job.  Any job that is currently being processed by the SIS server will fail and the status will be set to accordingly.  If the job has already been pushed to a client and executed then it will potentially be orphaned and the status in the Job queue will be set to Timed-Out.}}
+
{{Bullet1|Failover protection|SIS servers poll the Job queue for available jobs, and thus if a server fails, any other server within the same group will pick the next available job.  Any job currently being processed by the SIS server will fail, and the status set accordingly.  If the job has already been pushed to a client and executed, then it will potentially be orphaned, and the status set to Timed-Out.}}
  
 
{{infobox|If a standalone SIS server fails then all jobs aimed at that server will be left in the Job queue and will not be processed until the server is up and running again.}}
 
{{infobox|If a standalone SIS server fails then all jobs aimed at that server will be left in the Job queue and will not be processed until the server is up and running again.}}
Line 136: Line 159:
  
 
[[Category:ITOM]]
 
[[Category:ITOM]]
 +
== Removing an SIS Server Installation ==
 +
If you want to remove the SIS server from your instance. simply navigate to the SIS servers tab in the admin tool and delete the SIS server you want to remove.
 +
 +
The removal of the SIS server software from your server(s) requires manual steps in order to remove the service and all related files.
 +
# Open Windows Powershell console as an administrator
 +
# Enter the following:
 +
#:'''Stop-Service EspSisService'''
 +
#:'''sc.exe delete EspSisService'''
 +
#:'''Remove-Item "$env:ProgramFiles\Hornbill\Site Integration Server" -Recurse'''
 +
#:'''Remove-Item "$env:ProgramData\Hornbill\Site Integration Server" -Recurse'''
 +
 +
{{infobox|Care should be taken with these steps as they will perform a recursive delete on the two folders specified.  Once the service is removed don't forget to remove the SIS entry on the instance.}}

Latest revision as of 09:06, 16 November 2023

Home > Administration > ITOM > Site Integrations Services Index

Introduction

Hornbill's Site Integration Service (SIS) is a Windows NT Server service installed on a server behind an organisation's firewall. It runs as a standard Windows NT Service and, once paired with a Hornbill instance, monitors the ITOM Job Queue. The SIS connects to the instance order to retrieve jobs that have been placed on the job queue for execution.

Should jobs be detected during a polling interval, the SIS pulls all information from the paired instance regarding the jobs required to be undertaken on specified devices on the network. There are currently two types of job available; Computer Discovery and IT Automation. Automation jobs are powered via pre-built packages provided by Hornbill or can be custom-built using the ITOM Package Creator.

A web interface is provided, which allows for the initial pairing and display of the service's current status. The service is self-updating and will detect if a new version has been made available within the cloud and, if so, download and install it automatically. All communications with the cloud will always be initiated locally from the SIS to the cloud and never from the cloud.

Related Articles

Technical Considerations

System Requirements

  • OS: Windows Server 2012, 2012 R2, 2016, 2019 or 2022
  • RAM: 4GB
  • Free Disk: 10GB
  • CPU load is minimal
  • Can be run on virtual as well as physical machines.

Connectivity

  • The SIS communicates with a Hornbill instance using the secure HTTPS protocol.
  • Hornbill instances will only respond to a successfully paired SIS.
Information
Currently, support for communications via a proxy service is not available.

Discovery and Package Deployment

The SIS is capable of discovering the following devices:

  • Windows 32/64bit Computers
    Currently supported by Microsoft
  • Unix/Linux/Mac Computers running ssh

Depending on the content of the deployment package, there may be additional OS requirements.

Firewall Configuration

A Windows firewall rule for Inbound traffic (Local subnet) that allows all TCP traffic into the SIS service executable is created on installation and named:

  • Hornbill SIS Server - Context Callback (TCP - In).

The following outbound ports between the SIS server and the cloud instance are required:

  • HTTPS TCP 443

The following ports between the SIS server and Managed Devices are required, dependant on which method is adopted to retrieve Inventory details:

  • WinRM - TCP 5985
  • DCOM - TCP 135
  • DCOM - Range of dynamic ports:
    TCP 49152-65535 (RPC dynamic ports – Windows Vista, 2008 and above)
    TCP 1024-65535 (RPC dynamic ports – Windows NT4, Windows 2000, Windows 2003)
  • Site Integration Service Discovery (Dependant on the discovery mode used)
    • Active Directory / LDAP
    TCP Port 389 (Between the SIS and the AD Domain Controller / LDAP Server)
    • Secure Shell (ssh)
    TCP Port 22 (Between the SIS and target devices)

The following is required to support the TCP Ping test used during discovery (only required if the feature is in use):

  • ICMP Echo Reply

Toolbar

SISToolbar.png
  • Refresh
A refresh of the list may be required to display any new devices discovered while you are viewing the list
  • Show
Displays Connectors from the selected Group
  • + Create Group
(Selectable via the drop-down) allows for the Creation of SIS Groups'
  • Paired / Not Paired
Toggle button that allows the display of Paired or Not Paired SIS
  • Download Site Integration Server
Downloads the on-premise SIS Installer
  • Move Selected To...
Moves the selected SIS entries to the selected Group
  • NewPackageButton.png
Add a new SIS Connector
  • Delete
Deletes the selected SIS entries

List

SISListBlur.png
  • Name
The name of the Connector
  • Group
The group that the Connector belongs to
  • Description
The user-provided description for the connector
  • Service Type
Operating system architecture of the Server hosting the SIS installation
  • Service State
Toggle to enable or disable the SIS
  • Online Status
The current status of the link to the SIS service.
  • Service Build
SIS Server build version. Any Service showing an older build may highlight that there is an issue with automatic updates for that service
  • Last Seen On
this will display the last time there was communication between the Hornbill SIS Service and the SIS Server

Creating an SIS Service Profile on the Hornbill Instance

  1. Navigate to Administration > Hornbill ITOM > Site Integration Services
  2. Click the NewPackageButton.png button to create a new SIS Connector
  3. Enter the following details:
    1. Name - name used to identify the SIS server to the Hornbill Instance
    2. Group - Should be a least one default group, others can be selected via drop down if created previously
  4. Click the Create Site Integration Service button

Image: 350 pixels

  1. The Authorisation Code is displayed, and should be recorded for later use
  2. See the next section for details of how to pair your SIS with your Hornbill instance
  3. Should you choose not to complete the pairing at this time, the connector can be found by selecting the Not Paired filter in your list of SIS Connectors
Information
The Authorisation Code is valid for 1 hour. Should the SIS connector and SIS installation not be paired during this time, the key will expire. To generate a new Key, remove the SIS connector and recreate it.

Downloading and Installing the SIS Service

Click "Install" to begin installing the SIS
The Site Integration Service is installed as a Windows NT Service called "ESPSisService"

The Hornbill SIS is installed as a Windows NT Service and will require local administration rights for installation on the target computer.

  1. Navigate to: Administration > Hornbill ITOM > Site Integration Services
  2. Click the Download Site Integration Server button on the toolbar
  3. Locate the downloaded executable (.exe), and double click to begin
  4. Click Install
  5. Click Ok to Confirm the Installation
  6. Close the Install dialog
  7. Open the Services mmc console
  8. Start the EspSisService if it isn't already running











Pairing an SIS Server with a Hornbill Instance

Once the EspSisService is running, the process of pairing the service with a Hornbill instance can begin, which will require an Authorization Code. This code will have been provided while creating an SIS connector. See the section Creating an SIS Connector on the Hornbill Instance.

  1. Open the Browser and navigate to http://localhost:11117.
    2. After a short pause, a prompt for the Instance Id and an Authorization Code appears
  2. Enter the Instance ID and Authorization Code
  3. Click the Pair with Instance button

  • The Instance ID and valid Authorization Code are required to pair an SIS with your Hornbill instance

  • Once paired, the SIS status is reviewable via http://localhost:11117

Grouping Site Integration Servers

The creation of groups enables SIS connectors and SIS installations to be logically grouped; each SIS entry must belong to a single group. A "Default" group is provided with the option to create additional groups as required. Generally, the network infrastructure, load balancing and failover requirements will determine the number and grouping of SIS installations.

  • Load Balancing
When more than one server is placed within a group, Jobs sent to the group for processing will be processed by the next available SIS server spreading the load.
  • Failover protection
SIS servers poll the Job queue for available jobs, and thus if a server fails, any other server within the same group will pick the next available job. Any job currently being processed by the SIS server will fail, and the status set accordingly. If the job has already been pushed to a client and executed, then it will potentially be orphaned, and the status set to Timed-Out.
Information
If a standalone SIS server fails then all jobs aimed at that server will be left in the Job queue and will not be processed until the server is up and running again.

Creating a Group

164×139px
  1. From the ITOM page select Site Integration Services
  2. Click the Show dropdown
  3. Click +Create Group option
  4. Enter the New Group Name
  5. Click Apply


Removing an SIS Server Installation

If you want to remove the SIS server from your instance. simply navigate to the SIS servers tab in the admin tool and delete the SIS server you want to remove.

The removal of the SIS server software from your server(s) requires manual steps in order to remove the service and all related files.

  1. Open Windows Powershell console as an administrator
  2. Enter the following:
    Stop-Service EspSisService
    sc.exe delete EspSisService
    Remove-Item "$env:ProgramFiles\Hornbill\Site Integration Server" -Recurse
    Remove-Item "$env:ProgramData\Hornbill\Site Integration Server" -Recurse
Information
Care should be taken with these steps as they will perform a recursive delete on the two folders specified. Once the service is removed don't forget to remove the SIS entry on the instance.
Retrieved from "https://wiki.hornbill.com/index.php?title=Site_Integration_Services&oldid=31510"