Versions Compared

Old Version 24

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Gomathy Kumarakuruparan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

WSO2 Identity Server includes two main deployment patterns. These patterns take high availability into consideration and are recommended for production deployment environments. The following sections provide high level information on the recommended patterns available and point off to instructions on how to set up and configure the deployment pattern. 

...

Note
titleNotes

Note the following before you begin:

  1. Ensure high availability for the respective RDMS RDBMS and Directory Services used for each of the deployment patterns given below.

  2. In each production deployment, share the runtime deployment artifacts among nodes using a shared file system. In the deployment patterns defined below, this process is referred to as 'Artifact synchronization’.

    The Runtime deployment artifacts are:

      1. Email output event publisher
        /repository/deployment/server/eventpublishers/

      2. Secondary user stores
        /repository/deployment/server/userstores/

      3. Analytics data publishers and event streams
        /repository/deployment/server/eventpublishers/
        /repository/deployment/server/eventstreams/

      4. Workflow engine related artifacts
        /repository/deployment/server/humantasks/
        /repository/deployment/server/bpel/

Pattern 1 - HA clustered deployment of WSO2 Identity Server

This deployment can be scaled from two to N nodes based on capacity requirements. 

...

ProductPortUsage

WSO2 Identity Server		9763 HTTP servlet port
9443 HTTPS servlet port
4000 Ports to be opened with respect to clustering membership scheme used

Pattern 2 - HA clustered deployment of WSO2 Identity Server with WSO2 Identity Analytics

  • Load balancers should be configured to use sticky sessions.

  • All WSO2 Identity Server nodes should participate in a cluster. Clustering is used to invalidate local caches of nodes, by notifying over cluster messages, as cache updates happen.

  • Since WSO2 Identity Server Analytics is not mission critical, a two node cluster is recommended where only one will receive events over TCP failover, as configured in WSO2 Identity Server nodes to publish events. The other node will keep its state synced with the active node.

...