Post-deployment tasks
You must verify the accessibility of the services.
- For each service deployed with the global package, verify that the service is accessible.
- For REST services, verify the functionality in in the context of the applicable suite.
Optional: Customizing BaaS services deployed in editable global packages
A BaaS service deployed with an editable package can optionally be downloaded, edited, and deployed as a new service version in the development client Infor OS BaaS SDK. This requires IONAPI-BaaS-Developer role. For more information, see Infor Backend as a Service Developer Guide.
Upgrade strategy for BaaS resources in global packages
During deployment of a newer version of a global package, the version number in the BaaS service manifest is always evaluated.
The version number in the service manifest has three components: major, minor, and patch, for example 1.0.0. When a service is initially deployed from a global package, the patch version is always 0, for example 1.0.0.
Upgrading BaaS resources in editable global packages
For services originally deployed from editable global packages, local customizations can be applied to the service source code and deployed as a new version, for example 1.0.1. If a newer global package contains a BaaS service with a higher version number, for example 1.2.0, the deployed service is updated to that version. Local changes made in version 1.0.1 must be evaluated and manually merged into the newer version, if applicable, before deploying the customized service as a new version, for example 1.2.1.
If the newer global package contains a BaaS service with the same version, for example 1.0.0, the 1.0.0 version is deployed again, and the customized version (1.0.1) must be deployed once more.