Install > SA Core post-installation tasks > SA configuration

SA configuration

After you have installed the first SA Core, whether as part of a single host or Multimaster Mesh installation, the SA Core Components will be running and you will be able to log in to that core’s SA Client. You can now configure SA so that end users can start managing servers in their operational environment.

The following sections provide a general outline of the SA configuration tasks you will need to do and pointers to the HPE documentation that contains the detailed instructions needed to complete the tasks.

Customized SA Core configuration files

After installing this release, you will be able modify certain SA Core configuration files and preserve those modification during subsequent core upgrades.

SA preserves configuration files for the following components:

  • Data Access Engine (spin)
  • Web Services Data Access Engine (twist)
  • Component of the Global File System (spoke)
  • Software Repository (word)
  • Command Center (occ)
  • Deployment Automation (da)
  • Component of the Global File System (hub)
  • Command Engine (way)
  • Model Repository Multimaster component (vault)
  • Gateways (opswgw)

To preserve your modifications, SA creates an empty configuration file named with _custom appended to the name of the source file, for example:

  • <component_name>_custom.conf
  • <component_name>_custom.properties
  • <component_name>_custom.args

You can modify these files to override default component configuration specifications, for example:

  • twist_custom.conf is created for twist.conf
  • psrvr_custom.properties is created for psvr.properties
  • waybot_custom.args is created for waybot.args

Configuration files created during SA installation

During upgrade, the installer may revert the configuration files to the default values.To preserve your customizations, you should save them in the custom configuration files of the components. You can find the list below:

  • /etc/opt/opsware/spin/spin_custom.args
  • /etc/opt/opsware/twist/twist_custom.conf
  • /etc/opt/opsware/spoke/spoke_custom.conf
  • /etc/opt/opsware/mm_wordbot/mm_wordbot_custom.args
  • /etc/opt/opsware/occ/psrvr_custom.properties
  • /etc/opt/opsware/da/da_custom.conf
  • /etc/opt/opsware/hub/hub_custom.conf
  • /etc/opt/opsware/waybot/waybot_custom.args
  • /etc/opt/opsware/vault/vault_custom.conf
  • /etc/opt/opsware/opswgw-<gateway_name>/opswgw.custom

Configuring e-mail alerts

You can configure SA to send e-mail alerts to the SA administrator (or other designated users) when certain conditions are met, such as Managed Server error conditions or Multimaster Mesh conflicts. To do so, your e-mail administrator must configure the SA Core and Managed Servers as Sendmail clients. You should configure e-mail alerts in the SA Client when you install Server Agents on your managed servers.

Setting up SA groups and users

You must assign the necessary access rights and permissions to SA administrators, users, and user groups. For example, to log in to the SA Client, you specify a user name and password. Each user belongs to a user group, and each user group has a set of permissions that control access to features (actions), managed servers, and folders.

Creating SA customers

When you installed the First Core, whether Single Core or Multimaster, you specified a single default SA customer.

Defining software management policies

Software policies allow you to install software and configure applications simultaneously. A software policy can contain packages, RPM packages, patches, application configurations, and other software policies. After creating a software policy, you can attach it to servers or groups of servers. When you remediate a server or group of servers, the patches, packages, RPM packages, and application configurations specified in the attached policy are automatically installed and applied.

Deploying Server Agents on unmanaged servers

After you install a Server Agent on an unmanaged server, it can be managed by Server Automation.

Preparing SA for SA Provisioning

SA Provisioning is a feature that allows you to remotely install and uninstall operating systems (and related configurations, packages, and applications) on your servers. During SA Provisioning, a Server Agent is also installed, allowing the server to be immediately managed.

Preparing SA for patch management

The Patch Management for Windows feature enables you to identify, install, and remove Microsoft® Windows patches. With the SA Client user interface, you can identify and install patches for the Windows 2000, Windows 2003, and Windows NT4.0 operating systems. These patches include Service Packs, Update Rollups, and hotfixes. This feature also supports patching on 64 bit for Windows 2003 operating systems and for 32 bit for Windows XP operating systems.

SA monitoring

SA provides several methods that you can use to ensure that your system is performing correctly:

  • Agent reachability tests: to determine the current reachability of a specific Agent, you can run a Communication Test in the SA Client to find those servers that have unreachable agents.
  • System Diagnostic tests: several system diagnostics tests are available in the SA Client that can help you determine that your SA installation is operating correctly and help you troubleshoot when there are problems.
  • Core Component logs: SA components have logs that can help you troubleshoot problems.

Send Help Center feedback