Installation and Initial Configuration
This chapter describes the installation and initial configuration for high availability.
Installation
For a detailed description of the installation procedure, see the DirX Identity Installation Guide. This chapter lists just the items you should address when installing the features for high availability.
Choose Licensed Feature Set dialog:
Make sure that you select High Availability in addition to Business Suite. You can also select Professional Suite and / or Password Management, but neither one of these packages is needed for High Availability.
Choose Install Set dialog:
If you selected High Availability in the previous step, you can now select High Availability here, which allows you to select from this item:
-
Server Admin – select this item to install the Server Admin Web application (and Java-based supervisor) that can be deployed with each IdS-J server. You should always select this item because it gives you an overview of the state of all Java- and C++-based servers.
Initial Configuration
After installation, you need to configure your deployment using the Initial Configuration wizard. This section just mentions the parts relevant for High Availability. For complete details on this task, see the DirX Identity Installation Guide, chapter Configuration.
System-wide Configuration dialog:
Enable High Availability for the system by checking the appropriate check box.
Configuration Options dialog:
Server Admin (including Supervisor-J) Configuration – select this item to deploy the Server Admin Web application to the IdS-J server you select in a subsequent step. Make sure that the Server Admin is deployed for each deployed IdS-J server.
Java-based Server:
For High Availability, set the message repository for the embedded message broker to a network device that can be accessed by the other Java-based servers – at least the one that is monitoring it.
In this case, the server typically needs to run as a domain account that has enough access rights to create files. The local system account is typically not sufficient. For Windows platforms you have to set that account in the Windows Services application.
As an alternative, you can set the repository with DirX Identity Manager: select the server in the Configuration folder and enter the correct path. Then re-start the services of both this server and the monitoring one to activate this.
To deploy additional Java-based servers, run the Configuration wizard again.
In the dialog Java based Server create a new server by selecting <Create a new Java server> in the field Server to update or create.
Select the host on which you run the wizard and in the Java-based Server Ports and SSL dialog especially set appropriate values for the ports and port ranges: Make sure they do not overlap with the settings of the other servers on the same host.
In case you need to connect using SSL, provide the necessary key and trust stores. For simplicity, you can re-use the certificate and key of the other servers: In the configuration wizard set the location to the sub-folder private of this server and copy them afterwards.