Instance-based Provisioning
You can create a Microgateway package from an existing installation and copy it to multiple target machines. A Microgateway instance package is a self-contained zip file that contains all artifacts for running a Microgateway. The contents of the zip file are:
JRE
Microgateway server
Microgateway cli
Configuration files
One or more API Gateway export archives
After copying the zip file , you have to extract the zip file contents and run the commandline scripts of the Microgateway CLI to start the Microgateway. A package is configured based on a Microgateway configuration file. The configuration file either points to an API Gateway or to one or more API Gateway export archives for asset promotion. The asset promotion is performed when you start the Microgateway within the package.
The figure illustrates creating a Microgateway package from an existing installation and copying it to multiple target machines.
Creating a Microgateway Instance
For the package-based provisioning the Microgateway CLI provides the createInstance command. The command creates a Microgateway package that can be transferred to any target environment. The command has the following parameters:
config: optional
Microgateway configuration file
instance: optional name of the
Microgateway package. The default value is MicrogatewayInstance.zip
Instance-based Provisioning Flow
A sample sequence for executing an instance-based provisioning is as follows:
1. Create API Gateway archives and set the configuration file accordingly.
2. Create a Microgateway instance.
microgateway.bat createInstance --config config.yml
--instance c:\temp\Microgateway.zip -os win
The provided config.yml is added to the MyMicrogateway.zip and overwrites any already given configuration file.
3. Copy the Microgateway instance to the target environment.
4. Extract the contents of the zip file using the unzip command and start the Microgateway instance.
unzip MyMicrogateway.zip .
./microgateway.bat start --config config.yml
The unzip operation creates the sub-folders of the Microgateway. The start command picks up the config file from the default location (config/config.yml). Ensure that on the following files the execute-bit is set by applying the chmod command (linux-only):
microgateway.sh
microgateway-jre-linux/bin/java
