Package definitions
A detailed definition of packages.
- The project that defines the maps and flows.
- A base path under which the artifacts are deployed. This can be used to ensure that similarly named artifacts are kept distinct and do not overwrite each other.
- A set of flows and/or maps to be included in the package.
- A set of additional files from the project to be included in the package.
- A default flow to be executed using the flow command server if the ‘–flow’ command line option is not used.
For maps and flows, a URL can be specified. This defines the endpoint URL through which the map or flow can be accessed on the Link runtime server.
Building a package causes the maps listed in the package to be compiled.
Deploying a package compiles all the maps listed in the package and add all of the artifacts to a package file which gets deployed to the specified server. Dependent objects are also included in the package even if they are not explicitly selected. For example, if a flow references other flows and maps, the referenced flows and maps are included in the package.
The flow command server (flowcmdserver) has a command-line option '--flow' that specifies the flow to execute from the package (sqlite file). If the '--flow' command-line option is not specified, the flow command server will execute the default flow if one has been specified.