Skip to Content
avatar image
Former Member

Possible SAP IdM installation scenarios (mixed types)

Dear community,

We tried to install an IdM-system with the following server config:

Server 1 (Windows 2008 R2):

MC, RC, VDS

Server 2 (Solaris - Netweaver 7.0):

IDM - UI

Server 3 (MSQL 2008):

IDM - DB

Because of the Netweaver Version 7.0 on "Server 2" we cannot use IDM Version 7.2.

Is it possible to:

1. Run IDM 7.2 on a Netweaver Version 7.0

2. Run IDM < 7.2 on Windows Server 2008 (We encountered problem with the installation script "mxmc.install" - VB-Script)

3. Run our whole IDM System in mixed mode like:

MC, RC, VDS, DB (7.2), UI (<7.2)

Thanks in advance.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    Apr 25, 2012 at 02:55 PM

    1. Run IDM 7.2 on a Netweaver Version 7.0

    Yes, I believe so. I know it does work on 7.01.

    2. Run IDM < 7.2 on Windows Server 2008 (We encountered problem with the installation script "mxmc.install" - VB-Script)

    Yes, you can. There are some issues with the script. Look at my blog entry for some tips on getting around this.

    3. Run our whole IDM System in mixed mode like:

    MC, RC, VDS, DB (7.2), UI (<7.2)

    Yes. I believe if you look in the central note for 7.2 it will recommend not installing IDM on the same server as your NetWeaver server, but I think it's ok for DEV type environments.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 26, 2012 at 12:45 PM

    Thank your for your reply. We are not totally sure about the right scenario. Maybe we'll try the first scenario. Does anybody else have some experience about major problems or the right procedure of implementing an IDM system?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      We don't know what the exact problem is. The script could not process the entered passwords. We assume that there is problem with special characters, but we could not figure it out. Afterwards, we've tried to execute the SQL statements manually via the SQL Server Management studio and it worked.