-
Notifications
You must be signed in to change notification settings - Fork 2
Quick Start
All that is really needed to use the toolkit is the "FatJAR" which contains all the classes and calling it with:
java -jar CoyoteDXAll.jar <CfgFileName>
There comes a time when the operator wants to use other components from other JAR files in more sophisticated arrangements. This is when managing the class path starts to be come an issue.
To address this, a set of scripts have been developed to handle the dynamic building of the class path and calling the components in a consistent manner. The result is a simple installation footprint which allows developers to contribute their own components in a standardized deployment.
To make creating this standardized deployment configuration easy, an installer has been created to make setting up everything take less then a minute.
Many have found it easier to install Coyote DX in its own directory like other software tools and use scripts to call the components in a consistent manner. To do this quickly and easily, use the installer to set everything in its own directory and use scripts to call the runtime environment and setup the class path.
It is assumed that at a minimum you have Java 7 installed on your system and it is on your execution path.
Go to this project's release section and look for the latest release. In it you should find the Installer for that release.
Running the installer on windowing systems should involve only double-clicking the JAR to begin the installation process. From a terminal, use java -jar CoyoteDXInstall.jar -console
to run the installer in text mode.
Although not strictly necessary, it is convenient to add the bin
directory of the install to the systems execution path. That way is is possible to run cdx
from anywhere in the system without having to specify a complete path to the launch script. You could also alias the command if your platform and command interpreter supports it.
Just delete the directory. That's it; nothing else.
The installer only creates directories and copies files to them. No updates are made to execution paths, registries or anything else. This is a package of simple Java components and a few scripts to make calling them more convenient and not an application requiring complex setup.
If you updated your execution path to make running cdx
simpler, then you may want to undo what you did to make that happen, but that is completely up to you.
- Concepts
- Features
- Transform Engine
- Quick Start
- Configuration
- Secrets Vault
-
Readers
- List of Readers
- Custom Readers
-
Writers
- List of Writers
- Custom Writers
-
Filters
- Accept
- Reject
- Custom Filters
-
Tasks
- List of Tasks
- Custom Tasks
-
Validators
- List of Validators
- Custom Validators
-
Listeners
- List of Listeners
- Custom Listeners
-
Transforms
- List of Transforms
- Custom Transforms
- Mappers
- Context
- Databases
- Templates
- Logging
- Encryption
- Usage
- Expressions
- Examples