Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
310 views

Upgrade Postgres from IDM 4.0.2 to IDM 4.5.4


Hello,

I am upgrading an IDM solution running on SLES, from version 4.0.2 to
4.5.4. The customer would very much like to keep their running
workflows.

The IDM 4.0.2 solution is running on JBoss, and IDM 4.5 runs on Tomcat.
So a new installation is needed.

I have exported the Postgres database with PGAdmin -> Chose backup and
then plain and insert as options.

I then uninstalled IDM from the UA server, with the uninstaller.

Then i installed the Tomcat and Postgres from the IDM 4.5 media.

Then I imported the backup from the old Postgres database, like so:

/opt/netiq/idm/apps/postgres/bin/psql -h x.x.x.x -d dbname -U
adminusername -f idmuserappdbplaininsert

This gives a lot of errors, like below:


Code:
--------------------

psql.bin:idmuserappdbplaininsert:14670: ERROR: constraint "fk_hndls_rgstry" for relation "portalportlethandles" already exists
psql.bin:idmuserappdbplaininsert:14680: ERROR: constraint "fk_perms_accessrts" for relation "securitypermissions" already exists
psql.bin:idmuserappdbplaininsert:14690: ERROR: constraint "fk_process_model" for relation "afprocess" already exists
psql.bin:idmuserappdbplaininsert:14700: ERROR: constraint "fk_prodreg_prod" for relation "portalproducerregistry" already exists
psql.bin:idmuserappdbplaininsert:14710: ERROR: constraint "fk_prv_cd_lbl" for relation "provisioning_code_map_label" already exist

--------------------


Now I don't know if that is bad, but I would think so. I would think
that some tables have been changed in the new Postgres version, and the
like.

After installing the actual UA and upgrading it all to IDM 4.5.4 and log
into /IDMProv and look at the running workflows, they are actually
there, but if I click one of them, the actual form is gone.

Now I don't know if this approach is correct, but from what i read,
there is no real supported way of getting keeping your running
workflows. You are supposed to just start new ones, when the new server
is up. The problem is that the customer has many, many, many workflows.

Has anyone successfully done something like this, and how?

Thanks in advance,

Jacob.


--
jacmarpet
------------------------------------------------------------------------
jacmarpet's Profile: https://forums.netiq.com/member.php?userid=415
View this thread: https://forums.netiq.com/showthread.php?t=56431

Labels (1)
0 Likes
1 Reply
Micro Focus Expert
Micro Focus Expert

On 8/15/16 6:18 AM, jacmarpet wrote:
>
> Hello,
>
> I am upgrading an IDM solution running on SLES, from version 4.0.2 to
> 4.5.4. The customer would very much like to keep their running
> workflows.
>
> The IDM 4.0.2 solution is running on JBoss, and IDM 4.5 runs on Tomcat.
> So a new installation is needed.
>
> I have exported the Postgres database with PGAdmin -> Chose backup and
> then plain and insert as options.
>
> I then uninstalled IDM from the UA server, with the uninstaller.
>
> Then i installed the Tomcat and Postgres from the IDM 4.5 media.
>
> Then I imported the backup from the old Postgres database, like so:
>
> /opt/netiq/idm/apps/postgres/bin/psql -h x.x.x.x -d dbname -U
> adminusername -f idmuserappdbplaininsert
>
> This gives a lot of errors, like below:
>
>
> Code:
> --------------------
>
> psql.bin:idmuserappdbplaininsert:14670: ERROR: constraint "fk_hndls_rgstry" for relation "portalportlethandles" already exists
> psql.bin:idmuserappdbplaininsert:14680: ERROR: constraint "fk_perms_accessrts" for relation "securitypermissions" already exists
> psql.bin:idmuserappdbplaininsert:14690: ERROR: constraint "fk_process_model" for relation "afprocess" already exists
> psql.bin:idmuserappdbplaininsert:14700: ERROR: constraint "fk_prodreg_prod" for relation "portalproducerregistry" already exists
> psql.bin:idmuserappdbplaininsert:14710: ERROR: constraint "fk_prv_cd_lbl" for relation "provisioning_code_map_label" already exist
>
> --------------------
>
>
> Now I don't know if that is bad, but I would think so. I would think
> that some tables have been changed in the new Postgres version, and the
> like.
>
> After installing the actual UA and upgrading it all to IDM 4.5.4 and log
> into /IDMProv and look at the running workflows, they are actually
> there, but if I click one of them, the actual form is gone.
>
> Now I don't know if this approach is correct, but from what i read,
> there is no real supported way of getting keeping your running
> workflows. You are supposed to just start new ones, when the new server
> is up. The problem is that the customer has many, many, many workflows.
>
> Has anyone successfully done something like this, and how?
>
> Thanks in advance,
>
> Jacob.
>
>

Greetings,
there have been a number of threads about the process to use when
upgrading from 4.0.2 to 4.5.

From your write-up, I not sure if you did the following:

1) Exported the idmuserappdb from the old PostgreSQL
2) Uninstalled PostgreSQL server
3) Installed the New PostgreSQL server
4) Imported the exported "idmuserappdb" into the new PostgreSQL server
5) Ran the Identity Applications installer and selected "existing" in
regards to the database.



--
Sincerely,
Steven Williams
Lead Software Engineer
Micro Focus
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.