Skip to Content

MOPZ Step 3 - Download Files

  • Step Description

Download final generated Stack. xml. Download Archive Files from Download Basket or SLM.

1 Download archive files from Download Basket.

2 Download archive files from SLM.  For detailed information for SLM, you can navigate to link: Maintenance Optimizer Portal  (on webpage bottom,  find 'Software Lifecycle Manager (SLM)' information)

1 2 3
  • Message

for all SLM configrations issues, please check the note 1709002 - MOpz: Use SLM with HTTP first.

you don't need to go through the complicated HTTPS configuration




 

  • Warning: <download object key> is not pushed into download basket due to authorization failure.

Warning message occured in MOpz log,



Or after download archive files, some of them are missing in download basket or SLM.

Root Cause & Solution

Check if the SP exists in service market place.

Click https://service.sap.com/~form/handler?_APP=00200682500000001144&_EVENT=DISPLAY&_DOC_KEY=012002523100021742452012D , change the object key number 012002523100021742452012D to the <download object key> in the warning log.

If it exists, then please create internal message to XX-INT-NAAS-MAKE. If it dose not exists, then create internal message to XX-SER-SAPSMP.



    



  • Q&A for SLM

    for all SLM configrations issues, please check the note 1709002 - MOpz: Use SLM with HTTP first.

    you don't need to go through the complicated HTTPS configuration

    


Q1: You get into MOpz configuration assistant, and try to configure SLM, while a window is popped up to request logon data of SLM web service. Why?


1. check and unlock the user.
2. enable the intended https port. The ports of Java server are automatically assigned as HTTP: 5<InstanceNr>00, HTTPS: 5<InstanceNr>01, P4: 5<InstanceNr>04, Telnet: 5<InstanceNr>08. Refer to customer message 0120061532 0002241891 2010.
3. If not solved, you can forward this to BC-MID-RFC or BC-MID-ICF as approriate.

  • Q&A for stack.xml

    Sap note 1496765 - Maintenance Optimizer: FAQ for Stack Delta Files



Q1: Why the start system information (in stack.xml, it is called <target-system>-<initial state>) is included in stack.xml?

This is becuase during deployment, we must make sure that the object system is not changed from we run MOpz till the deployment. If object system is changed, MOpz needs to be re-run.

Q2: When user upgrade Netweaver, why the system considers the upgrade as EHP installation? Why no dvd section in stack.xml?

Upgrade mode for Netweaver is calculated specially. For example, if you want to upgrade NW7.2 to NW7.31, if it is abap technical system, the mode is Upgrade. If it is Java or dual stack, the mode is EHP Implement.

Q3: User select XI Content, Java Virtual Machine, NWDI in MOpz, but why the components is not in the generated stack.xml?

This is design. Because XI Content, Java Virtual Machine and NWDI can only be installed manually with tools which does not depend on Stack.xml. In addition, when user only select XI technical usage during EHP installation without other technical usage, the product version will not be updated (because no required inst).

Q4: When delta add-on component version can be listed in stack.xml?

refer to the note 1770071 - MOPZ: Generating Add-on to the Stack XML

   Q5: If there is no Delta exists for a SCV (means the SCV is kept in the system after update without changing SP), why sometimes the SCV is listed in <sp-stack> tab without SP or archive file in stack.xml file?

  The SCV without according SP or archive is the SCV which is kept from start system to target system. Such SCV is listed in <sp-stack> in stack.xml. The purpose is, user can check which SCV retains in system via stack.xml.

Former Member

No comments