Configuration (part 1)
You may find yourself wanting to configure a system programmatically. How to best go about this task depends on what you need to accomplish. For instance, if you need to apply a known configuration, you might choose to use the Configuration portion of the API seen in-use by the Snapshot Save and Load page to apply a preset configuration to portion of the system (or entire system).
Some things to consider in advance:
- Are your configuration requirements static (known in advance and can be planned for)?
- Are you configuration requirements dynamic, or come from a source such as a database or your application?
Snapshot Save and Load
If you have a scenario where you can use predefined configurations, the most powerful way to configure the server involves the NA_Configuration API, used in the Snapshot Save and Load page.
You can configure the system to fit your needs and then capture snapshots to use later. You can also control granularity by using partial snapshots.
Partial Snapshots
If you are unfamiliar with partial snapshots, a partial snapshot is simply a subset of the system configuration. For instance, you may want to capture just the serial configuration and nothing else, or perhaps you have one or two data flows that handle certain processing. You can use these smaller snapshots to apply configuration to smaller portions of the server.
Benefits
- Simple development
- Setup occurs using configuration pages that ensure you are using valid settings
- You can ensure the configuration works in advance
- You only have to apply a single configuration file, not individual settings to (potentially) many disparate entities
- Applying a configuration handles all the necessary steps for you
- No need to know the details of registry keys
Drawbacks
- Requires setup in advance
- Static
Registry Configuration
Configuring via registry is the most flexible and powerful option, but comes with some risk. We’ve referred to the registry as “a database”, but that’s an analogy; each key is freeform text. Registry use requires knowledge of,
- The list of keys necessary to configure what you need
- The legal values for the keys, including possible formatting
- How to make the entity(ies) using the keys re-read the registry and assume the configuration (uses a different part of the API)
If your development needs require dynamic values determined at runtime, or come from some external source such as a database, then registry may be the way to go.
Benefits
- Powerful
- Can be applied to just the keys necessary
Drawbacks
- Complex
- Requires knowledge of key details
- Incorrect key values can cause severe problems
Registry Help
It’s often necessary to contact NetAcquire tech support for information regarding the registry keys you need for the changes you want to make. We’re happy to help you with these requests.
In part 2 we’ll look at some toolkit programming to accomplish the two types of configuration described here.