Hi Sergiy,
i looked at SAP Note 1294013 and followed the solution laid out within.
----
Solution
In MII 12.1, the Xalan library no longer come shipped with the product. The Xalan library can be downloaded from the Apache website at http://xml.apache.org/xalan-j/index.html. Version 2.7 was used for testing and can be obtained from the Apache archive directory
http://archive.apache.org/dist/xml/xalan-j/binaries/.
The files are placed in the lib/endorsed folder for the JDK that the Netweaver server is using. For example, if you have a Windows machine running NW, the files would be placed in the following directory:
C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\jre\lib\endorsed. If the endorsed directory is not there, create it under the lib folder and place the following files there:
- serializer.jar
- xalan.jar
- xercesImpl.jar
- xml-apis.jar
- xsltc.jar
In order for NW and MII to pick up these new jar files the NW instance will need to be restarted.
----
This resulted in:
Then we followed the SAP Note 982552
---
Solution
For internal usage technical configuration can be performed even though the precondition check has failed. This can be done by enabling the "developer mode".
- create a role "CTC_DEVELOPER" in the UME
- assign this role to the user that performs technical configuration
When running the Configuration Wizard next time a button "continue in developer mode" appears. By pressing this button the Configuration Wizard is started in developer mode.
Important: Performing technical configuration in developer mode may lead to errors during the configuration process and to inconsistencies in the system.
---
This resulted in:
I'm reluctant to proceed because i'm not sure about the risks involved. :-)
Regards,
Markus