Skip to Content
avatar image
Former Member

Deployment error of MII 12.1 SP 5

All,

I have installed and updated NW 7.01 CE to SPS 9. I have also successfully deployed the initial MII 12.1 on this same server. During the 12.1 SP 5 update, JSPM reports an error. I have combed through the JSPM log file, and found the following entry:

Client path '/usr/sap/trans/EPS/in/XMII05P_2-20004625.SCA --> xappsxmiijraapp.sda'

Sdu info :name 'xappsxmiijraapp', vendor 'sap.com', location 'MAIN_xM121PAT_C', version '7609147', software type ('J2EE', sub type ''),

dependencies :[none]

Deploy status is 'Aborted'

Description:'1.

Exception.-> Policy configuration "eis/XMIIRFC08" does not exist in security context "SAP-J2EE-Engine" for connector "eis/XMIIRFC08" in application "null".'.

I'm new to MII so I don't know what this error is refering to, or where to look, and how to fix it. The 12.1 configuration guide (dated 10/19/09) only has about 4 or 5 steps, none of which refers to this object.

Any ideas? Thanks in advance.

Jose

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Apr 13, 2010 at 11:14 PM

    Arnaud Liotta,

    Thanks for reply and sorry for the late response, I didn't get an email notification that the thread had been updated. I reinstalled NW CE 711, and updated the Support Stack to SPS 4. I then deployed MII 12.1 as I had before. Up to this point all was successful. I then again tried to deploy SP 5 Patch 2 for 12.1, but I got the same error message as before:

    "Relative path '/usr/sap/trans/EPS/in/XMII05P_2... --> xappsxmiijrapp.sda'

    Deploy status is 'Aborted'

    Description:'1. Exception.

    -> Policy configuration"eis/XMIIRFC08" does not exist in security context "SAP-J2EE-Engin" for connector "eis/XMIIRFC08" in application "null".'.

    Any ideas?

    Thanks in advance,

    Jose

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Jose,

      For the NW stack it should be NW EHP1 SP 3 with the latest patch; not SP 4.

      As far as I've seen SP 4 is causing issues. You certainly have dependencies between software components in SP3 and MII which are causing trouble with SP4.

      At the same time, are you able to log on MII, launch the MII Workbench, run a query, do some stuff?

      Directly regarding your issue, actually, I'm not sure it'll be fixed with going back to SP3... it seems for me like a bad security configuration for the IDOC listener within the patch.

      One more thing, in the marketplace there is only 1 patch available. The second patch may have been suppressed for now...

      Cheers,

      Arnaud

  • avatar image
    Former Member
    Apr 13, 2010 at 02:28 AM

    Hi Jose,

    MII 12.1 has to be deployed on NW CE EHP1 SP3... which is 7.11.

    You'll find the Installation guide in the market place under

    Release and Upgrade Info

    Installation and Upgrade guides

    Business Suite Applications

    SAP Manufacturing

    MII

    at the same place that you found the configuration guide.

    What do you expect to find in the configuration guide?

    Cheers,

    Arnaud

    Edited by: Arnaud Liotta on Apr 13, 2010 10:31 AM

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 14, 2010 at 02:13 AM

    You are absolutely right Arnold!

    The issue has to do with the dependencies between NW 7.11 SP03 and MII 12.1 SP 5. Here is the official response from SAP:

    "SAP MII 12.1SP05 MUST be installed with the latest SAP NetWeaver 7.11 EPH1 SP03. Since We have found some issues in the security area during running NW sp4 with MII, for the time being I would suggest you to deploy MII SP5 on NW sp3. Surely this is not long term issue, because we are currently testing MII with NW sp4, in next 2 to 3 months we will also support higher releases of NW." ~ SAP Support

    Thanks again for your help.

    Jose

    Add comment
    10|10000 characters needed characters exceeded