Basic deployment scenarios using Remedy Single Sign-On

This topic describes the basic deployment senarios that are possible using BMC Atrium Orchestrator (BAO) with Remedy Single Sign-On (Remedy SSO or RSSO).

These simple scenarios do not include APs and LAPs, but they can be added to your configurations.

Related topics
Installing and upgrading topics
 Where to find more information

Installing

Upgrading

Scenario numberComponents in the configurationDescriptionImage
1.

Repository with embedded Remedy SSO, and a CDP

  • Remedy SSO is embedded on the repository.
  • The repository and CDP communicate with the embedded Remedy SSO.
  • The repository is configured to use an embedded Remedy SSO.
  • The CDP is configured to use an external Remedy SSO.
  • There is no HA for the CDP.
2.Repository, external Remedy SSO, and a CDP

  • Stand-alone Remedy SSO, with an embedded database.

    Note

    This requires installing Tomcat and Java before installing Remedy SSO.

  • The repository and CDP communicate with the external Remedy SSO.
  • The repository and CDP are configured to use an external Remedy SSO.
  • There is no HA for the CDP.
3.Repository, external Remedy SSO with an external database, and a CDP

  • Stand-alone Remedy SSO uses an external Oracle or MS SQL database.

    Note

    This requires installing Tomcat, Java, and Oracle/MSSQL before installing Remedy SSO.

     

  • The repository and CDP communicate with the external Remedy SSO.
  • The repository and CDP are configured to use an external Remedy SSO.
  • There is no HA for the CDP.
4.Repository with embedded Remedy SSO, a CDP, and an HA-CDP
  • Remedy SSO is embedded on the repository.
  • The repository, CDP, and HA-CDP communicate with the embedded Remedy SSO.
  • The repository is configured to use an embedded Remedy SSO.
  • The CDP and HA-CDP are configured to use an external Remedy SSO.
  • There is no need for enterprise service bus (EeSB) setup. However, there is no high availability (HA) for Remedy SSO.
  • This configuration is is an extension of the basic (scenario 1) configuration.
  • This configuration is similar to a BAO 7.6.03 setup with Access Manager (AM).
5.Repository, external Remedy SSO, a CDP, and an HA-CDP

  • Stand-alone Remedy SSO, with an embedded database.

    Note

    This requires installing Tomcat and Java before installing Remedy SSO.

  • The repository, CDP, and HA-CDP communicate with the external Remedy SSO.
  • The repository, CDP, and HA-CDP are configured to use an external Remedy SSO.
  • There is no need for ESB setup. However, there is no HA for Remedy SSO.
  • This configuration is is an extension of the basic (scenario 2) configuration.
  • This configuration is similar to a BAO 7.6.03 setup with AM.
6.Repository, external HA-Remedy SSO with an external DB, a CDP, and an HA-CDP

  • Stand-alone Remedy SSO instances use an external Oracle or MS SQL database and are installed in two or more Tomcat servers in a cluster.

    Note

    This requires installing Tomcat, Java, and Oracle/MSSQL before installing Remedy SSO.

  •  A load balancer distributes the load to RSSO servers in the cluster.
  • The repository, CDP, and HA-CDP communicate with the external Remedy SSO via the load balancer.
  • The repository, CDP, and HA-CDP are configured to use an external Remedy SSO.
  • This configuration is similar to a BAO 7.6.03 setup with HA-AM or BAO 7.7.x, 7.8.x with HA-Atrium Single Sign-ON (ASSO).
7.Repository with embedded Remedy SSO, and a CDP with embedded Remedy SSO.
  • A Remedy SSO instance is embedded on the repository and on the CDP.

  • Offers HA for Remedy SSO using the BAO-specific ESB.

    This is available using a Remedy SSO patch downloaded from the BAO EPD site (see 7.9.01: Service Pack 1 for details).

  • Data replication using ESB only applies for local users, roles, and role mappings.
  • The repository and CDP communicate with the embedded Remedy SSO instances and the embedded Remedy SSO instances communicate with each other.
  • The repository and the CDP are configured to use an embedded Remedy SSO.
  • There is no HA for the CDP.
8.Repository with embedded Remedy SSO, a CDP with embedded Remedy SSO, and an HA-CDP with embedded Remedy SSO.

  • A Remedy SSO instance is embedded on the repository, the CDP, and on the HA-CDP .

  • Offers HA for Remedy SSO using the BAO-specific ESB.

    This is available using a Remedy SSO patch downloaded from the BAO EPD site (see 7.9.01: Service Pack 1 for details).

  • Data replication using ESB only applies for local users, roles, and role mappings.
  • The repository, CDP, and HA-CDP communicate with the embedded Remedy SSO instances and the embedded Remedy SSO instances communicate with each other.
  • The repository, CDP, and HA-CDP are configured to use an embedded Remedy SSO.