Introduction

Installing DirX Identity for the first time requires installation of one of the supported directory servers (Directory Installation). Afterwards, the DirX Identity Installation is to be performed. It installs all necessary software. Running the DirX Identity Configuration imports and configures all necessary data into the LDAP configuration stores (Config A).

You can extend or change the configuration at any time (Reconfiguration).

Running an Update Installation is also possible if you destroyed parts of the default objects in the configuration stores.

Before running an Update Installation, check the section "Preserving Files" in the chapter "Preparing the Migration" of the DirX Identity Migration Guide for files to be preserved and create backup copies of these files.

Running the DirX Identity Configuration imports and configures all necessary data into the LDAP configuration stores (Config A).

After running an Update Installation with Configuration, check the section "Restoring Preserved Files" in the chapter "Manual Migration" of the DirX Identity Migration Guide for files to be restored and restore these files according to said section.

You can extend or change the configuration at any time (Reconfiguration).

Installing a new version of DirX Identity requires an Upgrade Installation. Run the DirX Identity Installation of the new version and then perform a DirX Identity Configuration. The DirX Identity Configuration performs automatic migration and configures all necessary new data. Check the DirX Identity Migration Guide for manual steps to be performed.

You can extend or change the configuration at any time (Reconfiguration).

If you intend to un-install DirX Identity, run the DirX Identity De-Installation. This includes the DirX Identity De-Configuration routine. After these two steps all installed software is removed from the machine.

Because you may want to use all or part of the LDAP configuration stores, this data is not touched and is therefore preserved.

Note that it is not possible to run a new installation on such a configuration store. Perform a new installation (see above) on an empty configuration store of the new DirX Identity version instead and then migrate the data from your old configuration store using the corresponding directory server tools.

The default ports you should open for firewalls are (only if you use the corresponding component):

These ports are the default ports that you can change during the DirX Identity configuration. If you change them, open these ports in your firewalls. For the IdS-J server, the n is set to 0 for S1, 1 for S2, and so on.

Check the ports of the LDAP server(s) you intend to use as the Connectivity Store and/or Provisioning Store, respectively. Open these ports on the server-side if your scenario requires remote access to these LDAP servers(s). For DirX Directory Servers, the defaults are 389 (Non SSL) or 636 (SSL), but the ports that are actually relevant depend on the LDAP configuration.

If you are running DirX Directory Server 9.0 or later on the same host as the tomcat for DirX Identity, make sure, that the secure port used for the DirX Directory REST service (default 8443) is different from the secure port (default 8443) used for the tomcat installed for DirX Identity. The port 8443 will be configured in the configuration file of the DirX Identity Business User Interface for accessing the DirX Identity REST service.

Note that two ports are now used for JMX Access. In the configuration, you set the first number in the configuration; the second is always the first port number +1 and is the JMX RMI port.

Check for additional ports for connectors and agents necessary to access target systems you intend to provision (see the service definition for the corresponding connected directories).

The C++-based Server uses the default port 1111 for the transfer of private keys from the server to an agent. This is local process intercommunication so do not open this port in your firewall.

If you defined other ports during DirX Identity configuration, adapt your firewall configuration accordingly.

Note: With a socket connection, an “ephemeral” (short-lived) port is used on the client side, which the client requests from the operating system. In Microsoft Windows, the range of these ports is usually between 49.152 and 65.536. If a port is in use, change the port number during configuration accordingly.