24.2 Understanding the Installation Process for PostgreSQL and Tomcat

You can choose to install one or both of the applications. For example, you might not need PostgreSQL because you already have a supported version of the application on the server. The following considerations apply to the individual installations:

PostgreSQL

The installation process installs the database for the identity applications and creates an administrative user called idmadmin to own the database. However, the installation does not create the schema in the database for the identity applications. Schema information gets added when you install the identity applications.

If you already have a supported version of PostgreSQL running on the server, the installation program prompts you for the password for the default postgres user. The program then creates the idmadmin user and assigns it the same password as for postgres.

At the end of the process, the installation program starts the database instance. The instance must be running when you install other Identity Manager components that use the database, such as the User Application.

You are not required to use PostgreSQL for the database for identity applications.

Tomcat

The installation process creates the IDM Apps Tomcat Service. To support the Tomcat application server, the installation program also installs Apache ActiveMQ and Oracle JRE. These items help Tomcat send email notifications.

The installation program does not start Tomcat upon completion. The application server must be stopped before you install other Identity Manager components, such as Identity Reporting.