Site Integration Services: Difference between revisions
Line 23: | Line 23: | ||
* The SIS communicates with a Hornbill instance using the secure HTTPS protocol. | * The SIS communicates with a Hornbill instance using the secure HTTPS protocol. | ||
* Hornbill instances will only respond to a successfully paired SIS. | * Hornbill instances will only respond to a successfully paired SIS. | ||
{{infobox|Currently support for communications via a proxy service is not available.}} | |||
===Discovery and Deployment=== | ===Discovery and Deployment=== |
Revision as of 16:22, 9 July 2020
Home > Administration > ITOM > Site Integrations Services | Index |
IntroductionHornbill'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.
|
|
Technical Considerations
System Requirements
- OS: Windows Server 2012, 2012 R2, 2016 or 2019
- 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.
- Currently support for communications via a proxy service is not available.
Discovery and Deployment
The SIS is capable of discovering the following devices:
- Windows 32/64bit Computers
- Currently supported by Microsoft
- Linux Computers running ssh
- Mac Computes running ssh
Depending on the content of the deployment package, there may be additional OS requirements
Firewall Configuration
The service will require additional ports to be open for discovery operations and may also need further ports depending on the packages used. For package-specific details, refer to the package documentation.
The following outbound ports between the SIS service and the cloud instance are required:
- Outbound HTTPS port 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
- TCP Port 389 (Between the SIS and the AD Domain Controller)
- LDAP
- TCP Port 389 (Between the SIS and LDAP Server)
Site Integration Services List
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
Site Intergartion Services Toolbar
- 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
- Delete
- Deletes the selected SIS entries
Downloading and Installing Hornbill's SIS
The Hornbill SIS is installed as a Windows NT Service and will require local administration rights for installation on the target computer.
- Navigate to the following Hornbill Administration page: Home > ITOM > Site Integration Services
- Click the "Download Site Integration Server" button on the toolbar
- Locate the downloaded executable (.exe), and double click to begin
- Click Install
- Click Ok to Confirm the Installation
- Close the Install dialog
- Open the Services MMC Console
- Start the EspSisService
Creating a SIS Connector on a Hornbill Instance
- Navigate to Hornbill Administration > Home > ITOM > Site Integration Services
- Click the button to create a new SIS Connector
- Enter the following details:
- Name - name used to identify the SIS server to the Hornbill Instance
- Group - Should be a least one default group, others can be selected via drop down if created previously
- Click the Create Site Integration Service button
- The Authorisation Key is displayed, and should be recorded for later use
- See the next section for details of how to pair your SIS with your Hornbill instance
- 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
- 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. To generate a new Key, remove the SIS connector and recreate it.
Pairing a SIS Server with a Hornbill Instance
Once the ESPSisService is running, the process of pairing it to a Hornbill instance can begin. An Authorization code will be required before continuing, obtained by the creation of an SIS connector, see the section Creating a SIS Connector on a Hornbill Instance for further details.
- Open the Browser and navigate to http://localhost:11117. After a short pause, a prompt for the Instance Id and an Authorization Code appears
- Enter the Instance ID and Authorization Code
- Click the Pair with Instance button
- SISHomePage.png
Once paired, the SIS status is reviewable via http://localhost:11117
Grouping Site Integration Servers
The creation of groups enable SIS connectors, and thus SIS installations, to be logically grouped together. All SIS entries must be a member of a single group, one of which will already exist, named "Default". The default group can be renamed, and additional groups created as required. Generally, the network infrastructure, load balancing and failover requirements will determine the number and grouping of SIS installations that may be necessary.
- 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 that is currently being processed by the SIS server will fail and the status will be set 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.
- 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
- From the ITOM page select Site Integration Services
- Click the Show dropdown
- Click +Create Group option
- Enter the New Group Name
- Click Apply