Creating a configuration sequence

To process a set of configuration files, create a configuration sequence that matches the files to process.

About this task

When you create a configuration sequence you define location profiles. A location profile is a directory in the DataPower file system to monitor with an assigned access profile. A configuration sequence can monitor multiple locations.
  • Each location is scanned for files that contain configuration changes and match a PCRE pattern. Only matching files are processed. By default, the sequence monitors configuration files with the cfg file extension.
  • The access profile, indicates the permissions for the file execution based only when the configuration permissions mode for the domain is specific access profile mode. When the configuration permissions mode for the domain is either domain scope mode or global access profile mode, the access profile for this location is ignored. For information, see Creating application domains.
By default the location for input files is the location for output files. To define a different location, indicate to use a different output location and identify this location. The following settings determine how to process the output files.
  • The PCRE pattern to name log files. This PCRE pattern normally has a back-reference to the input file name. For instance, when input files have the cfg file extension and the desired log file name is to replace the file extension with log, the pattern is $1.log.
  • The PCRE pattern to name status files. This PCRE pattern normally has a back-reference to the base input file name. For instance, when input files have the cfg file extension and the desired status file name is to replace the file extension with status, the pattern is $1.status.
The Capabilities (read-only) tab contains a list of capabilities that are derived from other properties or from properties that were defined by an external management systems.
  • Whether to optimize for IBM® API Connect processing
  • Whether to monitor changes for persistence
  • Whether to apply to all objects
  • Whether to mark objects as external
  • Whether to delete files after processing

Procedure

  1. In the search field, enter configuration.
  2. From the search results, click Configuration Sequence.
  3. Click Add or New.
  4. Define the basic properties: Name, administrative state, and descriptive summary.
  5. Optional: Add location profiles to monitor for files that contain configuration changes.
    1. Click Add.
    2. Select a directory.
      Although the default value is local:///, to activate the panel when you do not need an access profile, you must change to another directory and back to local:///.
    3. Optional: Specify the access profile to define the permissions to resources in the directory.
      Valid only when the configuration permissions mode for the domain is specific access profile mode. For information, see Configuring the access profile for a configuration sequence.
    4. Repeat this step to add another location profile.
  6. Optional: Change the PCRE match pattern for the configuration files in the defined location to monitor.
  7. Optional: Change the PCRE pattern to build the name of the result log file.
  8. Optional: Change the PCRE pattern to build the name of the JSON status file.
  9. Indicate whether to monitor the identified locations for new and modified files.
    By default, locations are monitored.
  10. Optional: Define the location for output files when you want a different location for input and output files.
    1. Set to use a different location.
    2. Select the location for output files.
  11. Indicate whether to delete objects that are no longer needed after configuration events.
    By default, unused objects are deleted.
  12. Optional: Specify the interval in milliseconds to wait before running this sequence again to load file changes after a file event.
  13. Click Apply to save the changes to the running configuration.
  14. Click Save Configuration or Save changes to save the changes to the persisted configuration.