AIX Runtime Expert profiles

AIX® Runtime Expert profiles are used to set values on a running system, extract values for a running system, and compare values against a running system or against another profile.

A profile describes one or more runtime configuration controls and their settings for the targeted functional area. A profile can represent a full set of controls or a subset of controls and their values. Configuration profiles are standard XML files. Using AIX Runtime Expert you can manage profiles and apply them on the defined system.

A profile can contain configuration parameters and tuning parameters without any values, like sample profiles. The purpose of a profile without any parameters is to extract the current systems values from the specified profile. Profiles containing at least one parameter without any values have the following limitations:
  • Using the artexset command fails with an error.
  • Using the artexdiff command returns a warning message for each parameter that has no value.
The value of a parameter in a profile can contain the following:
  • No value
  • A blob value, which is a base64 encoded binary data as an in-line text file. The blob value is used to replace existing files, like /etc/motd or /etc/hosts.
  • A non-blob value, which is a value assigned to system configuration parameters, like an integer or string.

In the /etc/security/artex/samples directory you can view existing sample profiles. The sample profiles only contain parameter names that are supported by the default settings installed with AIX Runtime Expert. The parameters in the sample profiles do not have any values. Sample profiles are read only files. Use the sample profiles as a template to create new configuration profiles. You cannot apply existing samples to a running system.

The following examples are some of the base configuration commands that can be controlled through configuration profiles:

  • Network configuration
    • no
    • mktcpip
  • Kernel configuration
    • ioo
    • schedo
  • RAS configuration
    • alog
  • Security configuration
    • setsecattr


The following example displays a configuration profile for different catalogs and sub-catalogs with assigned values for different parameters. You could edit this profile with any XML editor or use the vi command and change the existing values for the defined parameters.

<?xml version="1.0" encoding="UTF-8" ?>
<Profile origin="get" version="1.0" date="2009-04-25T15:33:37Z">
<Catalog id="vmoParam">
<Parameter name="kernel_heap_psize" value="0" applyType="nextboot" reboot="true" /> 
<Parameter name="maxfree" value="1088" /> 
<Catalog id="noParam">
<SubCat id="tcp_network">
<Parameter name="tcp_recvspace" value="16384" /> 
<Parameter name="tcp_sendspace" value="16384" /> 
<SubCat id="general_network">
<Parameter name="use_sndbufpool" value="1" applyType="nextboot" reboot="true" /> 
<Catalog id="lvmoParam">
<Parameter name="max_vg_pbuf_count" value="0">
<Target class="vg" instance="rootvg" /> 
<Parameter name="pv_pbuf_count" value="512">
<Target class="vg" instance="rootvg" />