Functioning of HyWorks in different Deployment
This section provides information on how HyWorks function in a single and multi-organization deployments.
HyWorks in a Single Organization Deployment
With a single organization deployment, HyWorks operates in the following manner:
-
Organization creation will not be needed
-
All resources and configurations can be done on a single root (default) organization
-
License sharing is not needed, and all licenses are consumed at the root (default) organization
-
Resources are not shared
-
All information and logs are available in the root organization
-
While logging into HyWorks, client applications do not require selection of organization and all the endpoints, by default, get registered in the default root organization
HyWorks in a Multi-Organization Deployment
With multiple organization deployment, HyWorks functions in the following way:
-
Organizations must be created and configured
-
Licenses must be shared among organizations or reserved for different organizations
-
Resources configurations need to be done at each organization level
- Resources can be shared or configured to a specific organization level
-
All information and logs are specific to organizations, presented at the organization level itself
-
While logging into HyWorks, the client applications require a selection of the organization and all the endpoints will be registered at the selected organization level