Post-Installation Configurations

Contents
casp941
Contents
Set OneClick Client Restrictions
Client access to
includes access to OneClick web server installations. When the OneClick clients use the OneClick web server for connections, adding them to Host Security is not necessary.
You can configure host security for the OneClick web server using Remote Address Filter and Remote Host Filter in Apache Tomcat. See http://tomcat.apache.org for details.
Follow these steps:
  1. Navigate to <
    $SPECROOT
    >/tomcat/webapps/spectrum/META-INF.
  2. Open the context.xml file in this directory, using an XML editor.
  3. Locate the following line:
    <Context path="/spectrum" docBase="spectrum">
    Enter the following lines under this line:
    <Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="" deny=""/>
  4. Enter IP addresses as values for the deny parameter to specify users in which you want to restrict OneClick access. For example, you can allow all users for a given IP address range, but you can exclude one or more specific users.
  5. Optionally, enter IP addresses as values for the allow parameter to specify specific IP addresses in which you want to give OneClick access. For example, you can enter 10.254.*.* to include all IP addresses in your network that are in the “10.254” IP address range.
  6. Save and exit the file.
    OneClick client restrictions are set.
Set Up Client Access to
in a Distributed Environment
If you selected a Main Location Server other than the host system during installation, enter the name of the host system in the .hostrc file of the Main Location Server.
The installation automatically enters the name of the Main Location Server in the .hostrc file of the host system.
Follow these steps:
  1. Start the SPECTRUM Control Panel on the system that is designated as the Main Location Server.
  2. Select Configure, Host Security.
  3. Add the name of the host system to the Server List and click OK.
    The client access to
    is set up.
Change the OneClick Web Server Port
Change the default server shutdown port for the OneClick web server when:
  • Your OneClick web server contains multiple instances of Apache Tomcat.
  • Those instances of Apache Tomcat are using the default server shutdown port (8005).
Apache Tomcat cannot start on a system with another instance running on it.
Follow these steps:
  1. Navigate to the following directory:
    <$SPECROOT>/tomcat/conf
  2. Open the server.xml file, using a text editor.
  3. Navigate to the following line:
    - <Server port="8005" shutdown="SHUTDOWN" debug="0">
  4. Change the server port value to the new server shutdown port number. For example, port="8099"
  5. Restart Apache Tomcat, as follows:
    • On Windows:
      • Select All Programs, Administrative Tools, Services from the Start menu.
      • Select SpectrumTomcat from the list.
      • Click Restart the service in the left pane.
    • On Solaris and Linux:
      • Navigate to the following path:
      <$SPECROOT>/tomcat/webapps/spectrum restart.sh
      • Enter the following command:
    The web server port is changed.
Configure the Windows Server Scheduled Tasks Service
You can configure the Windows Server 2008 or Windows Server 2012 Scheduled Tasks service to work with the
Scheduler.
Follow these steps:
  1. Click Start, Administrative Tools.
  2. Select Task Scheduler.
  3. Select Action, AT Service Account Configuration.
  4. Select the option Another user account and select Change user.
  5. Enter a user name (including the domain, if applicable) of a valid
    user (for example, WORKGROUP\jsmith).
    By default, this dialog contains the current user. If the default is the
    user, no change is necessary. Scheduled tasks are run on behalf of the designated user.
  6. Enter the user password in the Password and Confirm Password fields and click OK.
  7. Click OK in the AT Service Configuration dialog.
    The Windows Scheduled Tasks service is configured.
Landscape Polling Interval Configuration in Fault-Tolerant Environments
In fault-tolerant
environments, OneClick checks the status of the
SpectroSERVER
by polling each landscape at 10-second intervals by default. Frequent polling shortens the failover time to the secondary
SpectroSERVER
when the primary
SpectroSERVER
goes down. This polling also avoids missing any
SpectroSERVER
restarts.
You can increase the landscape polling interval for better performance. You can configure the interval by editing the value of domainPollingInterval in the context.xml file on the OneClick web server. The value of domainPollingInterval is the seconds between polls to the
SpectroSERVER
to determine its status.
To increase the polling interval, edit the domainPollingInterval value in the context.xml file (located in the <
$SPECROOT
>/tomcat/webapps/spectrum/META-INF directory). For example, to change the landscape polling interval to 60 seconds, change the value of domainPollingInterval from 10 to 60.
For the changes to take effect, stop and restart the OneClick web server.