Deployment Guide-FujiFilm Synapse
Deployment Guide-FujiFilm Synapse
Deployment Guide-FujiFilm Synapse
Deployment Guide
Copyright Notices
Copyright © 2002-2018 KEMP Technologies, Inc. All rights reserved. KEMP Technologies and the KEMP
Technologies logo are registered trademarks of KEMP Technologies, Inc.
KEMP Technologies, Inc. reserves all ownership rights for the LoadMaster and KEMP 360 product line
including software and documentation.
Used, under license, U.S. Patent Nos. 6,473,802, 6,374,300, 8,392,563, 8,103,770, 7,831,712, 7,606,912,
7,346,695, 7,287,084 and 6,970,933
Table of Contents
1 Introduction 4
2 Template 5
6 Health Checking 14
7 Additional Features 15
References 16
1 Introduction
Synapse is Fujifilm’s Picture Archiving and Communication System (PACS). It allows filmless diagnosis
with high quality image processing. Synapse allows the archiving and distribution of vast amounts of
image information from all modalities, managing it with a single system.
Such a powerful tool requires reliable and powerful support. The KEMP LoadMaster delivers an
exceptional, cost-effective and easy to use solution which, by employing Adaptive Load Balancing,
balances requests across Synapse. Synapse consists of the following servers:
Database Server
Storage Server
When deployed as a pair, two LoadMasters give the security of High Availability (HA). HA allows two
physical or virtual machines to become one logical device. Only one of these units is ever handling traffic
at any particular moment. One unit is active and the other is a hot standby (passive). This provides
redundancy and resiliency, meaning if one LoadMaster goes down for any reason, the hot standby can
become active, therefore avoiding any downtime.
2 Template
KEMP has developed a template containing our recommended settings for this workload. You can install
this template to help when creating Virtual Services, as it automatically populates the settings. This is
quicker and easier than manually configuring each Virtual Service. If needed, changes can be made to any
of the Virtual Service settings after using the template.
Download released templates from the Templates section on the KEMP documentation page:
http://kemptechnologies.com/documentation.
For more information and steps on how to import and use templates, refer to the Virtual Services and
Templates, Feature Description on the KEMP Documentation Page.
For steps on how to manually add and configure each of the Virtual Services using the recommended
settings, refer to the steps in this document.
In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet)
Subnet Originating Requests is usually not needed. However, enabling Subnet Originating Requests
should not affect the routing in a one-armed setup.
In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real
Servers are on network B - Subnet Originating Requests should be enabled on LoadMasters with
firmware version 7.1-16 and above.
When Subnet Originating Requests is enabled, the LoadMaster will route traffic so that the Real Server
will see traffic arriving from the LoadMaster interface that is in that network/subnet not the Virtual
Service address.
When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual Services.
If the Subnet Originating Requests option is disabled globally, you can choose whether or not to enable
Subnet Originating Requests on a per-Virtual Service basis.
1. In the main menu of the LoadMaster Web User Interface (WUI), go to System Configuration >
Miscellaneous Options > Network Options.
Refer to the following sections for step-by-step instructions on creating and configuring Fujifilm Synapse
Virtual Services.
1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services > Add
New.
The Real Server Port should match the Virtual Service Port.
The Forwarding method and Weight values are set by default. These
can be changed by an administrator.
e) Repeat the steps above to add more Real Servers as needed, based on the
environment.
2. In the LoadMaster Web User Interface (WUI) main menu, go to Virtual Services > Add New.
3. Enter the same IP address in the Virtual Address text box as you did when setting up the
Synapse HTTP Virtual Service in the Configure the Synapse HTTP Virtual Service section.
TCP connections on port 104 are recognized as DICOM requests and are
forwarded to the DICOM server which the LoadMaster determines is
the most available based on processor and memory utilization.
The Real Server Port should match the Virtual Service Port.
The Forwarding method and Weight values are set by default. These
can be changed by an administrator.
e) Repeat the steps above to add more Real Servers as needed, based on the
environment.
2. In the LoadMaster Web User Interface (WUI) main menu, go to Virtual Services > Add New.
3. Enter the same IP address in the Virtual Address text box as you did when setting up the
Synapse HTTP and Synapse DICOM Virtual Services.
The Real Server Port should match the Virtual Service Port.
The Forwarding method and Weight values are set by default. These
can be changed by an administrator.
e) Repeat the steps above to add more Real Servers as needed, based on the
environment.
For more information and step by step instructions on installing and setting up Adaptive Agent please
use the following links:
6 Health Checking
By sending KEMP heartbeat checks, the LoadMaster periodically ensures that each of the servers in a
deployment is still running. As part of the KEMP heartbeat checks, on port 104 the LoadMaster opens a
TCP connection to determine if the DICOM server on the Synapse server is still responding.
The LoadMaster can also be configured to test the IIS service. The LoadMaster performs a check over
HTTP to the web server. A particular URL to be reached is identified and a value (for example, DB-OK) set
for LoadMaster to find. The LoadMaster calls the URL to determine if the database server is running
successfully. If it is, the webpage returns a message containing the value. If not, an error message is
returned. The LoadMaster can recognize this and looks for this value in every health check it performs.
7 Additional Features
Additional KEMP LoadMaster security and optimization features can be enabled for the deployment of
SAP. The deployment steps and configuration settings of these features can be found in the documents
which are listed in the References section of this document. These documents can be found on the KEMP
documentation web page: http://kemptechnologies.com/loadmaster-documentation/
Edge Security Pack (ESP) - A solution that provides edge security, SSO application integration and
flexible authentication options is critical for optimal user experience and information security policy
compliance.
Web Application Firewall (WAF) - This enables secure deployment of web applications, preventing
Layer 7 attacks while maintaining core load balancing services which ensures superior application
delivery and security.
Content Caching - The LoadMaster can cache static content that fits certain criteria (file extension,
query string, caching headers, size, and so on). As long as the file meets these criteria it can be stored
locally in the LoadMaster to avoid unnecessary requests to the Real Server to retrieve the file.
References
Unless otherwise specified, the following documents can be found at
http://kemptechnologies.com/documentation.