solution manager integration with mii
TRANSCRIPT
Solution Manager Integration with MII
Enter Title (Via Document Properties)
2
TABLE OF CONTENTS
1 INTRODUCTION ............................................................................................................................... 3
2 CONFIGURATIONS .......................................................................................................................... 3 2.1 Add Java System to SLD of Solution Manager System ............................................................... 3 2.2 Add Diagnostic Agent to SLD of Solution Manager System ....................................................... 5 2.3 Load Template XML into Solution Manager System .................................................................... 5 2.4 Managed System Configuration ...................................................................................................... 6 3 CCDB Content .................................................................................................................................. 8 Steps to view CCDB content ............................................................................................................................. 9 4 Change Analysis .............................................................................................................................. 9 Navigate to view Change Analysis .................................................................................................................... 9
Enter Title (Via Document Properties)
3
1 INTRODUCTION
In MII there are several configuration options based on which user content can be built. There are chances of user content not functioning due to some changes in the configuration. In order to have a comparison of configurations at different timestamps MII can now be configured as a ‘Managed System’ in Solution Manager System upon ‘Change Analysis’ can be performed to compare configurations. The configurations of two different MII systems can also be compared using ‘Change Analysis’.
This document explains the configurations and activities that need to be performed in order to do a ‘Change Analysis’ on the MII Configurations. The following is the list of configurations upon which the Change Analysis can be performed:
System Properties
Scheduled Jobs
Data Server Permissions
Data Servers
Time Periods
Time Period Schedules
Message Listeners
Message Listener Rules
Message Listener Cleanup Rules
Localization
Links
Navigation
Globals
Unit Conversions
Custom Attributes
Credential Store
Connection Store
NWDI Properties
Alert Cleanup Rules
File Usage Statistics
Project details
Tag Catalog
2 CONFIGURATIONS
The configuration necessary in order to integrate MII with Solution Manager are as below:
2.1 Add Java System to SLD of Solution Manager System
The steps below explain how to add the Java system to the SLD where the Solution Manager system is running:
1. Login to the Netweaver Administration screen of MII system.
2. Choose Configuration Security Destinations
Enter Title (Via Document Properties)
4
3. Create a new destination with the following details:
Destination Name = SLD_Client
Destination Type = HTTP
URL = <sld url of the solution manager system>
4. Create another destination with the following details:
Destination Name = SLD_DataSupplier
Destination Type = HTTP
URL = <sld url of the solution manager system>
Check for the same configuration in Configuration Infrastructure SLD Data Supplier Configuration and click on ‘Collect and send Data’.
Enter Title (Via Document Properties)
5
2.2 Add Diagnostic Agent to SLD of Solution Manager System
The steps below explain how to add the Diagnostic agent to the Solution Manager SLD:
1. Go to SAP MMC of the MII system and stop the Diagnostic agent.
2. Open a command prompt and navigate to the script folder inside of the agent path: usr/sap/<SID_AGT>/SMDAXX/script
3. Run the smdsetup script as the follows:
Smdsetup managingconf hostname:"sapms://solman.full.qual.host.name" port:"81XX" user:"SMD_ADMIN" pwd:"XXXXXXXX"
Where xx is the instance number.
4. The command should finish successfully.
5. START the diagnostics agent from SAP MMC.
Note: Please refer Add Diagnostic Agent for more information.
2.3 Load Template XML into Solution Manager System
The steps below explain how to load the configuration template XML into the Solution Manager System: Note: The CCDB Template XML is found under ‘Tools and Archives’ in the MII Administration screen. The template XML need not be uploaded if Solution Manager System version is ‘SAP Solution Manager 7.1 SP06’ and above.
1. Login to SolMan system 2. Execute the transaction ‘solman_setup’
Enter Title (Via Document Properties)
6
3. In the web page that is opened, select the menu item ‘Solution Manager Administration’ under the Administration section.
4. Select ‘Infrastructure’ in the new window. 5. In the screen, select the option ‘Root cause analysis’ under the ‘Framework’ options button. 6. In the tab strips that are visible in the lower section of the page, select either of the views and
select the system that was registered to the Solution manager system. 7. Now under the header ‘Change Reporting Template Management’ there is a field to upload
the XML. 8. Hit the ‘Browse’ button and choose the XML file to be uploaded from the file system and hit OK. 9. A success message appears if the XML is well formed and is valid.
2.4 Managed System Configuration
The steps below explain how to configure the managed system (Only important steps illustrated):
1. Login to Solution Manager System. 2. Execute the transaction ‘solman_setup’ 3. In the web page that is opened, select the menu item ‘Managed system configuration’. 4. Select the java system and click on ‘Configure System’.
Check if the Java System is added correctly.
Check if the XMII Software component is added and marked as diagnostic relevant
Check if other details are maintained correctly
Enter Title (Via Document Properties)
7
5. In the new page that opens, there are totally 11 configuration steps of which the important are:
Step 1 (Select Product) - Select the system and click on select the system and click on ‘Display Technical Configuration’. In the new window that is opened we check whether the software components that we want to monitor are ‘Diagnostically relevant’.
Step 2 (Check Prerequisites) - Run the Prerequisites check. See if any major issues are reported. Correct them and rerun the checks.
Step 3 (Assign Diagnostics agent) – In the ‘Agent assignment’ tab select the system and move to ‘SLD Agent Candidates’ tab. Click on get agents, and after selecting the corresponding agent, click on ‘Connect’. In the Agent Assignment tab check if the agent is correctly assigned to the managed system and the status is showing as green.
Step 4 (Enter System Parameters) (Optional for MII) - Enter the System Parameters of the
managed system as shown below
Enter Title (Via Document Properties)
8
Step 5 (Enter Landscape parameters) – Under selection of landscape parameters, there is a tree displayed. Select the JAVA server. On the right side enter all the parameters that were uploaded as part of the template.
Step 6 (Create Users) - Optional for MII - Create users either manually or from SolMan with the
roles shown here.
Step 7 (Configure Automatically) – Check if the ‘Extractor Setup’ status is green.
Finally go to Step 11 and click on ‘Finish’.
3 CCDB Content
The CCDB content is the actual configurations that are fetched by the Solution Manager system in the most recent extraction. It is also possible to view if the particular configuration has been added, modified or deleted.
Enter Title (Via Document Properties)
9
3.1 Steps to view CCDB content
1. Login to Solution Manager system 2. Execute the transaction code ‘ccdb’ 3. In the new window that opens select ‘Technical systems’. 4. Select the system by using the filtering options available. 5. This displays the list of configurations available for the system. 6. Click on a particular configuration and click on ‘Store details’. 7. Select the ‘Content’ tab and the contents will be visible in the panel below.
4 Change Analysis
The change analysis of the Solution manager system provides the ability to compare two different snap shots of the configurations of the same system at different time stamps or snap shots of configurations of two systems with the same version of software components. Navigate to view Change Analysis
Enter Title (Via Document Properties)
10
1. Login to Solution Manager system 2. Execute the transaction code ‘solman_workcenter’. 3. Select the tab ‘Root cause analysis’. 4. Select the option ‘End-to-End analysis’. 5. Select the system by using the filtering options available. 6. In the buttons available select ‘Change analysis’. 7. This displays a bar chart based the number of configurations extracted. 8. There are also options available to check what configuration changes have happened by clicking the
number of changes shown below in a table.
Enter Title (Via Document Properties)
11
© 2012 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP
products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany
and other countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP
company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL
Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional
warranty.
www.sap.com