In this blogpost the focus is on setting up a pre-configured SAPMC so that administrators can monitor and administrate multiple AS Java infrastructures.
Why SAP MC Java Applet and not SAP MMC Snap-In for Windows?The SAP MMC Snap-In for Windows could be an alternative to the SAP MC. In this case the Java Applet ist prefered because of the following reasons:
- it does not need administrative rights on Windows Clients (the MMC Snap-In needs them for installation and console start)
- it is platform independent
Step 1: Switching from browser based Applet to local application
- Copy the SAPMC content from a Netweaver Application Server Java to your local file system or to a network share (using a network share will give you the opportunity to use a centralized console together with your colleagues).
- You'll find SAPMC Folder in: /usr/sap/<SID>/J00/exe/servicehttp/sapmc/
- Edit codebase-Attribute in sapmc.jnlp:
- Change it from: codebase="http://hostname" to your local or network path, e.g.: codebase="file:///C:\temp\SAPMC"
- Be careful: You need 3 Slashes "///" (Two for file protcol and one for starting a file path)
- Save the file and open it. An empty SAPMC will start on your local client. In this case (march 2017) it is version 7490, 18, 26, 7524
Step 2: Configure and export system infrastructures
- Configure a System landscape ("File"->"New") and save it as "landscape file":
Step 3: Implement one or multiple "landscape files" in SAPMC
- Edit <aplication-desc> attributes in sapmc.jnlp:
- Implement each landscape file with <argument> tag:
- Be careful:
- Your file path has to start with a Slash "/"
- Blanks in your file path have to be replaced with "%20"
- Backslashes "\" from Windows file paths have to be replaced with Slashes "/" (that differs from the codebase path in step 1)
- Save the file and open it (don't wonder, it could take some time until the systems appear in the console window)