General Settings → Component Servers
In the Component Servers tab, you define the distribution of the SBM server components and enter server connection information for each of your servers. You typically configure the Component Servers tab in wizard mode after you install SBM.
Initially, the Component Servers tab contains a single server: Server 1 (this machine). By default, all of the SBM SBM server components are listed on this server. You can define additional servers by dragging and dropping SBM components into the space below Server 1. Alternatively, right-click any component and select the option Move to new server.
For distributed installations, use the drag and drop or Move to new server options to define which components are enabled on each server. The SBM installer installs all the SBM components on your servers; therefore, you must use the Component Servers tab to configure which components are enabled on each server.
To configure a distributed installation:
When you drag a component to another server, that component is no longer configurable on the local server with the exception of the Notification Server and Mail Client components—these components can be installed and configured on multiple servers within the same environment. Note that when you attempt to drag either component, you are prompted to Copy it (which keeps a local copy and designates another copy on a separate server) or Move it (which removes the configuration from this server in favor of a remote server).
You might choose the Move option if you want to configure and run the Mail Client on a separate server from the Notification Server. You might choose the Copy option if you are defining your entire component distribution and you know that you want the Notification Server installed on two servers for failover purposes.
After you finish distributing the server components, enter connection information for your local server and any additional servers you defined.
For each server that you define, provide the following information:
|Host||Enter the server host name.|
|Use HTTP on port||
Select this check box to configure all SBM URLs to use HTTP. The current HTTP ports that are used by IIS and Tomcat appear for informational purposes.
If you select this option, all SBM components on this server are only accessible using HTTP. Select only the HTTP check box to force all traffic to use HTTP.
If you set the Require Secure Channel property on the gsoap extension in IIS, you must ensure that Use HTTP is not selected.
|Use HTTPS on port||
Select this check box to configure all SBM URLs to use HTTPS. The current HTTPS ports that are used by IIS and Tomcat appear for informational purposes. This option is not available until you provide an HTTPS port on the IIS Server or Tomcat Server tab.
If you select this option, all SBM components on this server are only accessible using HTTPS. Select only the HTTPS check box to force all traffic to use HTTPS.
|Use IIS to proxy all server requests||Select this check box to have IIS proxy all
server requests in
This forces all
traffic through IIS on port 443 and disables all Tomcat HTTP connectors (8085,
8243, 8343, 8443). Note that if you enable this feature, you must update the
following to use port 443:
After you have updated your target servers and endpoints, you must re-deploy your process apps.
Important: In addition, you must ensure that the WebDav module in IIS has been removed under Common HTTP Features. This module blocks important HTTP requests that are used by SBM when IIS is used to proxy server requests.
|Join Tomcat cluster as a node||Select this check box to add this server as a node to a Tomcat cluster. For details, see Clustering Tomcat Server Components.|
|TCP port||If SBM Logging Services is on a separate server, enter the TCP port for the Active Diagnostics database (powered by MongoDB). The default port value is 27017.|
Select this check box to configure the external host name and HTTP or HTTPS settings for this server if it is located outside your company's firewall.
Important: If this server is located outside the firewall, you must enter the External host name in order for users to access the server. The host name that you enter is the same host name that your users will use to access the server externally.
Because the host name and port values for the firewall cannot be detected by SBM Configurator, you must enter valid port numbers manually. The port values that you enter here are dependent on your current firewall settings. Consult your firewall administrator to determine the port values that should be used in combination with the external server host name.
These port values are completely independent from the port values that you enter on the following IIS Server and Tomcat Server tabs in SBM Configurator.
If you select both the HTTP and HTTPS check boxes, this preserves the current HTTP or HTTPS configuration of all the URLs in your installation and no changes are made to their current configuration (except for port values you might have set after selecting Beyond firewall). Select both check boxes if you have previously manually configured some URLs to use HTTP and some URLs to use HTTPS. By default, both options are selected if you are installing and configuring SBM for the first time.
After you click Apply, SBM Configurator verifies the connection information for your local server. If SBM Configurator is unable to reconcile the host name or IP address that you provided with the host name or IP address of the local machine, SBM Configurator prompts you to select which host name represents your local server. Alternatively, you can click the Select local host link that appears to specify which machine is the local host.
For example, if you have a distributed installation that uses a load balancer, the host name you enter that corresponds to the load balancer will not match the host name or internal IP address of the local server. In that case, you must confirm which host name represents your local server. In this scenario, you must specify which host name represents the local machine.
Copyright © 2007–2016 Serena Software, Inc. All rights reserved.