Upload
biovia
View
334
Download
3
Tags:
Embed Size (px)
DESCRIPTION
AEP 9.0 will see several changes to the core infrastructure which will require changes to the way the server is managed as well as new deployment options that may affect the ways that protocol developers deliver content to their users. We will cover the addition of Tomcat as a new side by side service with Apache, new administration features: exporting and importing server configurations, maintenance mode, and new deployment options: HTTPS and HTTP only modes, deploying behind reverse proxies, and HTTP load balancing.
Citation preview
(ATS4-PLAT01) Core Architecture Changes in AEP 90 and Their Impact
on Administrators Steven Bush
RampD AEP Core Infrastructure
stevenbushaccelryscom
Platforms
bull Except where noted the information within this presentation applies to both Windows and Linux installations
bull Starting in 90 AEP server installations are now 64-bit only
Services
bull 85 and earlier ndash 32 and 64 bit ndash Apache
bull 90 ndash 64 bit only ndash Apache
bull Manages running jobs bull Other services including access to protocol database and files
ndash Tomcat bull Back end service provider
ndash Security filter ndash Internal configuration and system database ndash Periodic cleanup tasks ndash Other scheduled tasks
ndash AEPManager (Windows) bull Responsible for managing the other services
Tomcat Cleanup tasks
bull Remove stale job directories ndash Expired and invalid jobs
bull Queue processing ndash When max running jobs is reached
bull Remove stale lck files ndash ltInstallDirgttemplck
bull Each running job creates a file with basic information bull Running jobs reports when to queue based on lck file count bull If the job process crashes the lck file remains
bull Clean up vartmp files (Linux) ndash Used for OS synchronization files (mutexes conditions pipes)
Managing the services (Windows)
bull AEPManager service ndash Starts and shuts down Tomcat and Apache
ndash Monitors status of each service to restart when necessary
ndash Right click ldquoMy Computerrdquo choose ldquoManagerdquo Navigate to Services StartStop AEPManager
bull Modified ApacheMonitorexe ndash Based on Apache Foundation apachemonitorexe
ndash Shows all installed Apache services
ndash Combines all services within same AEP install directory
ndash 85 and earlier use apachemonitorexe that ships in apache folder
Managing the services (Windows)
bull Services Administration Panel
bull Processes and Memory
ndash Task Manager
ndash Process Explorer bull Improved Task Manager
bull httptechnetmicrosoftcomen-USsysinternals
Managing the services (Linux)
bull startserver stopserver scripts still used
ndash Starts and stops both Apache and Tomcat
ndash etcrcd used for autostart services bull Installed by root installation script (scirootinstall)
bull ps and top
bull ldquofree ndashmrdquo to check memory (-m = Megabytes)
ndash read ldquo-+ bufferscacherdquo line for real results
Launch Performance
Example which reads 500 molecules and returns a bit of JSON text Elapsed TimeThroughput vs Number of Simultaneous Clients
ExportingImporting Configurations
bull Export configuration from administration portal
ndash Clone server configurations
ndash Set up new nodes for load balancing configuration
Maintenance Mode
bull Disable launching jobs without shutting down the server
ndash Professional UI can still be used to build protocols
ndash Admin portal is still accessible
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Platforms
bull Except where noted the information within this presentation applies to both Windows and Linux installations
bull Starting in 90 AEP server installations are now 64-bit only
Services
bull 85 and earlier ndash 32 and 64 bit ndash Apache
bull 90 ndash 64 bit only ndash Apache
bull Manages running jobs bull Other services including access to protocol database and files
ndash Tomcat bull Back end service provider
ndash Security filter ndash Internal configuration and system database ndash Periodic cleanup tasks ndash Other scheduled tasks
ndash AEPManager (Windows) bull Responsible for managing the other services
Tomcat Cleanup tasks
bull Remove stale job directories ndash Expired and invalid jobs
bull Queue processing ndash When max running jobs is reached
bull Remove stale lck files ndash ltInstallDirgttemplck
bull Each running job creates a file with basic information bull Running jobs reports when to queue based on lck file count bull If the job process crashes the lck file remains
bull Clean up vartmp files (Linux) ndash Used for OS synchronization files (mutexes conditions pipes)
Managing the services (Windows)
bull AEPManager service ndash Starts and shuts down Tomcat and Apache
ndash Monitors status of each service to restart when necessary
ndash Right click ldquoMy Computerrdquo choose ldquoManagerdquo Navigate to Services StartStop AEPManager
bull Modified ApacheMonitorexe ndash Based on Apache Foundation apachemonitorexe
ndash Shows all installed Apache services
ndash Combines all services within same AEP install directory
ndash 85 and earlier use apachemonitorexe that ships in apache folder
Managing the services (Windows)
bull Services Administration Panel
bull Processes and Memory
ndash Task Manager
ndash Process Explorer bull Improved Task Manager
bull httptechnetmicrosoftcomen-USsysinternals
Managing the services (Linux)
bull startserver stopserver scripts still used
ndash Starts and stops both Apache and Tomcat
ndash etcrcd used for autostart services bull Installed by root installation script (scirootinstall)
bull ps and top
bull ldquofree ndashmrdquo to check memory (-m = Megabytes)
ndash read ldquo-+ bufferscacherdquo line for real results
Launch Performance
Example which reads 500 molecules and returns a bit of JSON text Elapsed TimeThroughput vs Number of Simultaneous Clients
ExportingImporting Configurations
bull Export configuration from administration portal
ndash Clone server configurations
ndash Set up new nodes for load balancing configuration
Maintenance Mode
bull Disable launching jobs without shutting down the server
ndash Professional UI can still be used to build protocols
ndash Admin portal is still accessible
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Services
bull 85 and earlier ndash 32 and 64 bit ndash Apache
bull 90 ndash 64 bit only ndash Apache
bull Manages running jobs bull Other services including access to protocol database and files
ndash Tomcat bull Back end service provider
ndash Security filter ndash Internal configuration and system database ndash Periodic cleanup tasks ndash Other scheduled tasks
ndash AEPManager (Windows) bull Responsible for managing the other services
Tomcat Cleanup tasks
bull Remove stale job directories ndash Expired and invalid jobs
bull Queue processing ndash When max running jobs is reached
bull Remove stale lck files ndash ltInstallDirgttemplck
bull Each running job creates a file with basic information bull Running jobs reports when to queue based on lck file count bull If the job process crashes the lck file remains
bull Clean up vartmp files (Linux) ndash Used for OS synchronization files (mutexes conditions pipes)
Managing the services (Windows)
bull AEPManager service ndash Starts and shuts down Tomcat and Apache
ndash Monitors status of each service to restart when necessary
ndash Right click ldquoMy Computerrdquo choose ldquoManagerdquo Navigate to Services StartStop AEPManager
bull Modified ApacheMonitorexe ndash Based on Apache Foundation apachemonitorexe
ndash Shows all installed Apache services
ndash Combines all services within same AEP install directory
ndash 85 and earlier use apachemonitorexe that ships in apache folder
Managing the services (Windows)
bull Services Administration Panel
bull Processes and Memory
ndash Task Manager
ndash Process Explorer bull Improved Task Manager
bull httptechnetmicrosoftcomen-USsysinternals
Managing the services (Linux)
bull startserver stopserver scripts still used
ndash Starts and stops both Apache and Tomcat
ndash etcrcd used for autostart services bull Installed by root installation script (scirootinstall)
bull ps and top
bull ldquofree ndashmrdquo to check memory (-m = Megabytes)
ndash read ldquo-+ bufferscacherdquo line for real results
Launch Performance
Example which reads 500 molecules and returns a bit of JSON text Elapsed TimeThroughput vs Number of Simultaneous Clients
ExportingImporting Configurations
bull Export configuration from administration portal
ndash Clone server configurations
ndash Set up new nodes for load balancing configuration
Maintenance Mode
bull Disable launching jobs without shutting down the server
ndash Professional UI can still be used to build protocols
ndash Admin portal is still accessible
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Tomcat Cleanup tasks
bull Remove stale job directories ndash Expired and invalid jobs
bull Queue processing ndash When max running jobs is reached
bull Remove stale lck files ndash ltInstallDirgttemplck
bull Each running job creates a file with basic information bull Running jobs reports when to queue based on lck file count bull If the job process crashes the lck file remains
bull Clean up vartmp files (Linux) ndash Used for OS synchronization files (mutexes conditions pipes)
Managing the services (Windows)
bull AEPManager service ndash Starts and shuts down Tomcat and Apache
ndash Monitors status of each service to restart when necessary
ndash Right click ldquoMy Computerrdquo choose ldquoManagerdquo Navigate to Services StartStop AEPManager
bull Modified ApacheMonitorexe ndash Based on Apache Foundation apachemonitorexe
ndash Shows all installed Apache services
ndash Combines all services within same AEP install directory
ndash 85 and earlier use apachemonitorexe that ships in apache folder
Managing the services (Windows)
bull Services Administration Panel
bull Processes and Memory
ndash Task Manager
ndash Process Explorer bull Improved Task Manager
bull httptechnetmicrosoftcomen-USsysinternals
Managing the services (Linux)
bull startserver stopserver scripts still used
ndash Starts and stops both Apache and Tomcat
ndash etcrcd used for autostart services bull Installed by root installation script (scirootinstall)
bull ps and top
bull ldquofree ndashmrdquo to check memory (-m = Megabytes)
ndash read ldquo-+ bufferscacherdquo line for real results
Launch Performance
Example which reads 500 molecules and returns a bit of JSON text Elapsed TimeThroughput vs Number of Simultaneous Clients
ExportingImporting Configurations
bull Export configuration from administration portal
ndash Clone server configurations
ndash Set up new nodes for load balancing configuration
Maintenance Mode
bull Disable launching jobs without shutting down the server
ndash Professional UI can still be used to build protocols
ndash Admin portal is still accessible
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Managing the services (Windows)
bull AEPManager service ndash Starts and shuts down Tomcat and Apache
ndash Monitors status of each service to restart when necessary
ndash Right click ldquoMy Computerrdquo choose ldquoManagerdquo Navigate to Services StartStop AEPManager
bull Modified ApacheMonitorexe ndash Based on Apache Foundation apachemonitorexe
ndash Shows all installed Apache services
ndash Combines all services within same AEP install directory
ndash 85 and earlier use apachemonitorexe that ships in apache folder
Managing the services (Windows)
bull Services Administration Panel
bull Processes and Memory
ndash Task Manager
ndash Process Explorer bull Improved Task Manager
bull httptechnetmicrosoftcomen-USsysinternals
Managing the services (Linux)
bull startserver stopserver scripts still used
ndash Starts and stops both Apache and Tomcat
ndash etcrcd used for autostart services bull Installed by root installation script (scirootinstall)
bull ps and top
bull ldquofree ndashmrdquo to check memory (-m = Megabytes)
ndash read ldquo-+ bufferscacherdquo line for real results
Launch Performance
Example which reads 500 molecules and returns a bit of JSON text Elapsed TimeThroughput vs Number of Simultaneous Clients
ExportingImporting Configurations
bull Export configuration from administration portal
ndash Clone server configurations
ndash Set up new nodes for load balancing configuration
Maintenance Mode
bull Disable launching jobs without shutting down the server
ndash Professional UI can still be used to build protocols
ndash Admin portal is still accessible
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Managing the services (Windows)
bull Services Administration Panel
bull Processes and Memory
ndash Task Manager
ndash Process Explorer bull Improved Task Manager
bull httptechnetmicrosoftcomen-USsysinternals
Managing the services (Linux)
bull startserver stopserver scripts still used
ndash Starts and stops both Apache and Tomcat
ndash etcrcd used for autostart services bull Installed by root installation script (scirootinstall)
bull ps and top
bull ldquofree ndashmrdquo to check memory (-m = Megabytes)
ndash read ldquo-+ bufferscacherdquo line for real results
Launch Performance
Example which reads 500 molecules and returns a bit of JSON text Elapsed TimeThroughput vs Number of Simultaneous Clients
ExportingImporting Configurations
bull Export configuration from administration portal
ndash Clone server configurations
ndash Set up new nodes for load balancing configuration
Maintenance Mode
bull Disable launching jobs without shutting down the server
ndash Professional UI can still be used to build protocols
ndash Admin portal is still accessible
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Managing the services (Linux)
bull startserver stopserver scripts still used
ndash Starts and stops both Apache and Tomcat
ndash etcrcd used for autostart services bull Installed by root installation script (scirootinstall)
bull ps and top
bull ldquofree ndashmrdquo to check memory (-m = Megabytes)
ndash read ldquo-+ bufferscacherdquo line for real results
Launch Performance
Example which reads 500 molecules and returns a bit of JSON text Elapsed TimeThroughput vs Number of Simultaneous Clients
ExportingImporting Configurations
bull Export configuration from administration portal
ndash Clone server configurations
ndash Set up new nodes for load balancing configuration
Maintenance Mode
bull Disable launching jobs without shutting down the server
ndash Professional UI can still be used to build protocols
ndash Admin portal is still accessible
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Launch Performance
Example which reads 500 molecules and returns a bit of JSON text Elapsed TimeThroughput vs Number of Simultaneous Clients
ExportingImporting Configurations
bull Export configuration from administration portal
ndash Clone server configurations
ndash Set up new nodes for load balancing configuration
Maintenance Mode
bull Disable launching jobs without shutting down the server
ndash Professional UI can still be used to build protocols
ndash Admin portal is still accessible
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
ExportingImporting Configurations
bull Export configuration from administration portal
ndash Clone server configurations
ndash Set up new nodes for load balancing configuration
Maintenance Mode
bull Disable launching jobs without shutting down the server
ndash Professional UI can still be used to build protocols
ndash Admin portal is still accessible
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Maintenance Mode
bull Disable launching jobs without shutting down the server
ndash Professional UI can still be used to build protocols
ndash Admin portal is still accessible
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
New Deployment Options
85 90
Single Server Yes Yes
Windows 3264 bit 64 bit
Linux 3264 bit 64 bit
Private Cluster Linux Linux
Public Cluster Linux Linux
Grid Engine Linux Linux
SSL OnlyHTTP Only No Yes
Port Forwarded No Yes
Load Balanced Web Farm No Yes
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
New GlobalsURL creation
bull Should no longer build URLs from server name and port ndash Will not work with reverse proxies and single port setups
ndash Had problems on clusters and grids
bull Use ServerRoot and ServerSSLRoot instead ndash Reflects configuration of server
bull SSLHTTP only
bull Reverse proxyport forwarded
bull Load balanced
bull Clusters and grids
bull Old globals will continue to work for basic configurations
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
New GlobalsURL Creation
85 90
HTTP URLs http$(ServerName)$(ServerPort)myFile $(ServerRoot)myfile
HTTPS URLs https$(ServerName)$(ServerSSLPort)myFile $(ServerSSLRoot)myfile
Internal HTTP URLs Same as client pilot_settingsROOT
Internal HTTPS URLs Same as client pilot_settingsSSLROOT
Internal Server Name Same as client pilot_settingsInternalServerName
Shared Data Directory ScitegicRoot SharedPublicDir
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Protocol Links
bull httpltservergtltportgtauthlaunchjob
ndash Faster launch times
ndash Improved features bull streaming results
bull Integrated authentication
ndash runjobpl links map to launchjob with _compat=1 flag
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
SSL and HTTP Only Modes
bull Setting found in Admin Portal
ndash Server ConfigurationServer Port Usage
bull Changes all outgoing URLs to point to correct endpoint
ndash In SSL only mode ServerRoot becomes https
ndash In HTTP only mode ServerSSLRoot becomes http
bull Does not turn off second port by default
ndash To disable listening on the unused port contact support
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Reverse Proxy
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Reverse Proxy
bull Deploy behind a port forwarding server
ndash Deployment into DMZs
ndash Multiple subnet deployments bull Some clients outside firewall others inside
bull ldquoSSL terminationrdquo option
ndash Connection to reverse proxy is via SSL
ndash From proxy to AEP server is HTTP only
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Reverse Proxy Configuration
bull Configure in Admin portal
ndash SetupReverse Proxy and Load Balancing
ndash Set the default server name for your reverse proxy (eg firewallmydomainnet) bull Add aliases that might be used as well (eg
10123firewallothernamemydomainnet)
ndash Set the port numbers that are available for your reverse proxy bull Leave HTTP or SSL blank if not used
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Reverse Proxy Configuration
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Load Balanced
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Load Balanced vs Cluster vs Grid
bull Load Balanced (Windows or Linux) ndash Large numbers of simultaneous users ndash Individual web requests are distributed ndash Parallel subprotocols are not distributed ndash Ideal for short running web based applications that require simultaneous user scalability or failover ndash Cannot be used for ad-hoc use
bull Cluster (Linux) ndash Large numbers of long running jobs ndash Running jobs are distributed ndash Parallel subprotocols are distributed ndash Ideal for long running jobs with large parallelization needs ndash Useful for ad-hoc use
bull Grid (Linux) ndash Similar to cluster ndash Load is controlled by third party grid software (eg OGE LSF PBS) ndash Slowest launch times ndash Ideal for large numbers of very long running jobs and taking advantage of existing grid systems ndash Possibly slow for ad-hoc use
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Load Balancer Requirements
bull Install behind any off the shelf load balancer
ndash The AEP server itself does not require affinity but some applications may choose to impose this limitation
ndash One requirement for the load balancer Must preserve the HTTP ldquoHostrdquo header
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Load Balanced Benefits
bull Throughput
ndash Huge improvement under high usage
bull Performance
ndash No difference under low usage versus single servers
ndash Moderate improvement under high usage
bull High Availability
ndash If a node goes down other nodes continue functioning
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Load Balanced Performance
Example which reads 500 molecules and returns a bit of JSON text tested against 1-3 nodes Elapsed TimeThroughput vs Number of Simultaneous Clients
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Load Balanced Restrictions
bull Protocol Database is read only ndash Deploy protocols and components using packages ndash Can not build models ndash Intended for applications that rarely change
bull Parallel subprotocols do not distribute across nodes ndash Set ldquoServerrdquo to the name of the load balancer instead of ldquolocalhostrdquo
bull Admin Portal connected through the load balancer can only show running jobs ndash Connect to individual nodes for full portal access ndash Use ldquoExportImportrdquo to update each node
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Load Balanced Shared Data
bull ldquoFolder Locationsrdquo in Admin portal
bull Jobs directory
bull Users directory
bull Shared Public directory
ndash Use SharedPublicDir instead of ScitegicRoot bull On a single server system both are equal
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
Load Balanced Configuration
bull SetupReverse Proxy and Load Balancing
ndash Follow same setup as for reverse proxy
ndash Check box for ldquoLoad Balancedrdquo
bull SetupFolder Locations
ndash Jobs directory
ndash Users directory
ndash Shared Public directory bull Use SharedPublicDir instead of ScitegicRoot
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision
The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision