RTCCTOOL
For each satellite system, make sure that the program RTCCTOOL is ran and the guidelines are followed in the report.
1. Log into the satellite system
2. Run transaction SE38
3. Enter program RTCCTOOL
4. Click Execute
5. Check the outcome of the report and if there are red lights make sure to address those.
6. Once the report returns with no errors, then proceed to next step.
SLD
Make sure the SLD is configured and up and running
You must register the satellite system with the Solution Manager system.
1. Log into the satellite system
2. Run transaction RZ70
3. Make sure that the Host and Service under the SLD Bridge section are pointed at Solution Manager
4. Click the Activate icon
5. Click the Execute button to start the data collection
6. Click Yes to start the job
7. Check if the system registered successfully in the Solution Manager
Change Job Created Above (SAP_SLD_DATA_COLLECT)
In the previous section a job called SAP_SLD_DATA_COLLECT) has been created that runs every 720 minutes, the job collects changes in the satellite systems and reports them back to Solution Manager. We need to change the user in this step to our BATCHID user or the DDIC user.
1. Log into satellite system
2. Run transaction code SM37
3. Enter in SAP_SLD_DATA_COLLECT as the Job Name
4. Enter a * in the username field
5. Click Execute
6. Click on the job that has a Release status
7. Click Job->Change
8. Click Step
9. Click on the step and click the change icon
10. Enter BATCHID as the User that will submit the step
11. Click Save
12. Click Save to save the job
Solution Manager Configuration
Prerequisites
Setting up SLD Job
When adding satellite system via SLD, the ABAP stack needs to read what has registered in the SLD to transfer it. Schedule this job periodically.
1. Log into Solution Manager system
2. Run transaction SMSY
3. Goto menu Goto->Setup System Landscape Maintenance
4. Click on the Schedule button
5. Click Yes to Schedule the Data Transfer
6. Set up this job hourly u2013 make sure to change the print parameters to Send to Spool Only
7. Adjust the u201CLANDSCAPE_FETCHu201D step to the BATCHID user just like the SLD section above using transaction SM37
Check that RFC Connections are Generated and Working
Before EWA reports can be configured in the solution manager it needs the RFC connections created and working to the satellite system.
1. In the Solution Manager System, run transaction code SMSY
2. Browse to the satellite system you want to configure
3. On the right section of the screen, highlight the client that you checking the RFC and click the Check RFC Connection icon
4. Click the Check RFC icon
5. Should get all green lights in the log
Adding Logical Component to Solution
This step assigns the Logical Component to the Solution
1. Run transaction SOLUTION_MANAGER
2. Click on the Solution that you are setting up the report for
3. Select Solution Landscape
4. Select Solution Landscape Maintenance
5. Select the logical component dropdown
6. Select the satellite system you are working with
- Per default, the leading role of a solution is defined as a production role. They will be highlighted by a green color in the filed. You may as well want to have systems with other system roles in your solution. In this case you will need to actually put the system in the solution.
7. Click Save
Configuring EWA Reports
The satellite system needs to be connected to Solution Manager in order to proceed.
Configure System in Solutions for EWA
1. In Solution Manager run transaction SOLUTION_MANAGER
2. Select Operations Setup
3. Select Setup EarlyWatch Alert
4. Deselect Send to SAP for all development and Test systems. Select Send to SAP for Production Systems
5. Click Save
6. Click Green Arrow Back
7. Click the Operations tab
8. Check if a new EWA session has been created.
You can access detailed session information by double clicking on the session. The red flag means this session is overdue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.