Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

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

...

Note
titleNotes

Note the following before you begin:

  1. Metrics is engaged with the product just to capture JVM metrics. At the moment no identity specific metrics that can be used to figure out the runtime behavior of Identity Server are exposed.
    Therefore, the metrics related datasource is not being considered and will be skipped in the production deployment patterns given below.

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

  3. In each production deployment, share the runtime deployment artifacts among nodes using a shared file system or a synchronization mechanism like rsync.
    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/

...

  • Load balancer 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. 

The UserStore is the user base. It can be one of the following: 

...

Tip
titleSet Up Deployment Pattern 1

To set up and configure clustered deployment of WSO2 Identity Server according to clustering pattern 1, see Setting Up Deployment Pattern 1 /wiki/spaces/IS530/pages/25560356.


Open ports

ProductPortUsage

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

...

  • 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.

...