Deployment scenario

The following diagram illustrates a typical HPE Service Manager Collaboration (SMC) deployment scenario:

Service Manager Collaboration cooperates with the following essential factors and Service Manager components:

  • Openfire server:

    Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache License. Service Manager Collaboration communicates with Openfire by using the widely adopted open protocol XMPP to approach all the operations, such as set up conversations, post messages, presence management, notification management and so on. The Openfire server also links Service Manager and other messaging applications, such as Microsoft Office Lync 2013.

  • Apache:

    The Openfire server must be deployed behind the Apache HTTP server (or a Windows Internet Information Services (IIS) web server) and use it as a reverse-proxy to protect the sensitive information of Openfire, such as the IP address, ports, and so on.

  • Service Manager web tier:

    Service Manager Collaboration is embedded in Service Manager web tier to access the Openfire server through Apache for instant messaging.

Besides, Service Manager Collaboration also needs the following prerequisites and configurations:

  • Light-Weight Single Sign-On (LW-SSO):

    Service Manager Collaboration uses LW-SSO to access and authenticate users. Service Manager Collaboration requires that you configure LW-SSO for the Service Manager web tier and the Openfire chat server.

For more information about how to install and configure Service Manager Collaboration, see HPE Service Manager Interactive Installation Guide.