Configuration management -DataPower file system - IBM Websphere

Each DataPower device contains a configuration. The device is configured using objects that are hierarchically organized into services. These services expose ports for the consumption of traffic over supporting protocols, such as File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), MQ, Java Message Service (JMS), and Network File System (NFS). Services implement functionality, such as authentication and authorization of Web services, acceleration of Extensible Stylesheet Language Transformation (XSLT), and enterprise service bus (ESB) protocol mediation.

File system directories and domains

The DataPower file system is an encrypted RAM data source separated into several named directories. Directories are used to manage configuration data, store XSLT stylesheets, capture logging events, manage cryptographic certificates and keys, and control other system functions. Configuration files are stored in the config directory, while custom data maintained by the user is stored in the local directory. The device stores most of its required files in the store: directory. For a complete description of the file syste.

DataPower file system

DataPower file system

Startup sequence for DataPower

Before discussing the methods available for configuration management, it is important to describe what happens at startup time within a DataPower device.

When a DataPower appliance first boots, it loads a startup configuration (fromconfig:///autoconfig. cfg, which can be modified using the boot config command)in the default domain. All the information in the configuration file is in command line interface (CLI) format. It is executed synchronously, one line at a time, until initialization is complete, which is why all the device-level initialization precedes any other domain statements in this file.

Therefore, at the very least, the configuration file must define the IP addresses for each Ethernet port and Domain Name System (DNS) names for resolution. After that, domain definitions and other artifacts can be set. However, we recommend that this file be kept small so that only critical values are placed within it in order to improve readability. Additional configuration files can be nested in a daisy-chain fashion as necessary to complete the configuration of the device.

Note: The lines in this file are executed in sequence, so basic properties, such as IP address, must come before anything else. Object order is significant, too. Subordinate objects, such as the match rule, must be defined prior to parental objects, such as the XML firewall. Compare this method to the SOMA/XML system where the XML files are not necessarily executed in a strict order. Using the CLI configuration files removes this dependency.

this shows a snippet from the configuration file of a business-to-business Gateway(B2BGW) object called HubOwner. The snippet defines an AS2 Front Side Handler (FSH), a HTTP FSH, and three partner profiles: two external profiles and one internal profile, among other
objects.

ASCII configuration file for B2BGW called HubOwner


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM Websphere Topics