No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FusionCloud Solution Description 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Service Management

Service Management

Any software, tools, capabilities, and even data provided to fourth parties can be regarded as services.

Services in ServiceStage are classified into following types:

  • Service Catalog: All services (including public services released by the current tenant and other tenants) that match the project type on the platform. For example, if the project type in the upper right corner of the page is R&D, and the environment type of service A is R&D and Test, then service A is displayed on the page. If the environment type of service B is Test, then service B is not displayed on the page.
  • My Order: All services that the tenant has subscribed to in the current project.
  • My Service: All services that the current tenant has published in the current project.

There are following service roles:

  • Service providers publish services to the ServiceStage service market.
  • Service users then order whatever services they like from the ServiceStage service market, instantiate the selected services, and use them.

If you intend to publish or order services, it is important that you have a basic understanding of the following concept.

Table 39-5 Basic concept




Functions are packaged as services. In ServiceStage application models, services are application-oriented. This means that applications must select services and bind services to applications before using services. In certain scenarios, services may be charged according to the pay-per-use rule.

Service instance

An instance is the concrete entity of a service. Service instances may vary with service type. Service instances may be containers or data segments. For software services, a software instance is a software entity; for tool services, a service instance is a tool entity.

Service dependency

Service dependency indicates that the service instance on which the to-be-ordered service depends must be specified. For example, if service A is dependent on service B, you must order instances of both service A and service B.

Service binding

Service bindings are records of service dependencies. Each service dependency has a binding record. It is important to distinguish depended services from the depending services. For example, if service A depends on service B, then service A is the depending service and service B is the depended service. Third-party applications can also bind service instances.

Service broker

The service broker is used to assist the platform to control life cycles of service instances.

Service console

The service console is the service console software.

Service publishing

Service providers publish services to the ServiceStage service market.

Services are classified into platform-level services and tenant-level services. Platform-level services can be ordered by all users; while tenant-level services can be ordered by users under the current tenant.

Service ordering

Ordering services means selecting the required services from the ServiceStage service market and instantiating services. Instantiated services can then be put into use.

Updated: 2019-10-23

Document ID: EDOC1100063247

Views: 74217

Downloads: 192

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next