cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Netweaver IDM upgrade fro 7.2 to 8.0

0 Kudos
148

Hi,

I have some questions regarding the IDM7.2 to IDM 8.0 Upgrade? Has anyone followed the side box approach? Where you able to import all your customization with this approach? Did you end up creating a lot of scripts because of the customized data not moved in ? Were you able to move audit logs from old to new server with this approach? Thanks for answering.

Accepted Solutions (0)

Answers (2)

Answers (2)

todor_petrov
Contributor
0 Kudos

Hi Anam,

this blog might give you some useful insights ->

Upgrade of SAP IdM (not) for dummies

BR,

Todor

former_member358098
Participant
0 Kudos

Hello!

We were able to move completely to IDM 8.0 including all data and audits.

All your custom part should be imported as .mmc file from 7.2. This will create single package with all schema. Then you will have to decide : leave it as is and have everything transported everytime. also you will lose ability to use new provisioning framework (we are still using one from 7.2).

In our case we didn't have to create any additional scripts. If your DB is staying of the same vendor everything will be pretty easy.

Good luck to you with your migration!

0 Kudos

Thanks for responding back.

Just wanted to be clear have you used side box approach for upgrading?

If yes, My concern is as SAP stated that :

Will we be able to capture audit logs from old to new server?

As we have lot of customization, is it possible to move the customization as it is from 7.2 to 8.0

former_member358098
Participant

anam.ali

Yes, we had to use sidebox approach because we had to switch OS and DB too. As I said , if you keeping DB the same vendor and version as on 7.2, you'll only need to transfer tables you need (we used SLT). The full list of tables to be migrated if you want to keep all data :

mxi_approval,mxi_approval_pending_action,mxi_approver,mxi_AttrValueHelp,mxi_entry,mxi_link,mxi_link_audit,MXI_OLD_VALUE,mxi_root_reference,mxi_structure_root,MXI_VALUES,MXP_AUDIT,mxp_audit_extra,MXP_Audit_Variables,MXP_Ext_Audit,MXP_provision

And IdM 8.0 has exact tool in Eclipse to import all your schema (tasks, jobs, entries and so on) to 8.0 in the same way as it was in 7.2. More detailed info about transferring your customizations you can see here:

https://help.sap.com/viewer/0a8e2a6c5dc142af85b7a1774fff2cde/8.0/en-US/51dd3237abcf450395016f0af011b...

0 Kudos

Hi,

I am in proposal phase of project .Is there any document which gives the detailed step by step guide like what are the steps involved to import the identity store(prerequisites /post import activities) , repositories or job folders:

1. How long it would take to import an identity store(I am aware it depends on import file size, but approximately)

2. Do we have to import individual repositories or it should be all in one go?(how long would it take for 50 repositories to be exported or imported and what all settings need to be changed in 8.0 like making repository type from 7.2 to 8.0 and etc)

3. How do you overcome the problem of indirect assignment, as all privileges are imported as direct assignments even though they were assigned indirectly through business role in 7.2?

former_member358098
Participant
0 Kudos
anam.ali

Hello,

Personally i've not seen any detailed guides any other than

https://help.sap.com/viewer/0a8e2a6c5dc142af85b7a1774fff2cde/8.0/en-US/cf19835a87c944819270291099ff3...

1. As of import. Our MCC file size was about 12 mb and it took about 10-15 minutes to import.

2. In IDM8.0 appeared such new construction as "Repository type", this made us completely rework how we store our repositories, so we spent 1 week in trial and error to make everything work smoothly. (we have about 100 repositories). But anyway you can import them all in one go, only you have to make sure, that no value has "new line symbol", because this will cause errors.

3. We didn't have any problems with indirect assignments, because table mxi_link was part of we directly copied from our initial systems and all connections were saved exactly as they are.